Account security
Your Undersign account provides access to your signing requests, documents, templates, and account settings. Undersign includes several security measures to help protect your account and the information associated with it.
Authentication
Undersign supports secure authentication through:
| Security feature | How it helps |
|---|---|
| Strong password protection | Passwords are securely protected using strong encryption practices rather than being stored as plain text. |
| Google Sign-In | You can sign in using your Google account, allowing Google to handle the authentication process. |
| Secure password reset | If you forget your password, you can use the password recovery process to securely regain access to your account. |
| Secure session management | Authenticated sessions are protected to help prevent unauthorised access to your account. |
Note: Undersign currently does not provide two-factor authentication (2FA).
API Keys
API keys provide programmatic access to Undersign APIs and should be treated as sensitive credentials.
You can create, manage, deactivate, and delete API keys from Account Settings → API Keys. Store API keys securely on your server and never expose them in client-side code or public repositories.
See API Keys for more information.
Protecting your account
For better account security:
- Use a strong, unique password for your Undersign account.
- Keep your Google account secure if you use Google Sign-In.
- Never share your account password or API keys with others.
- Store API keys securely and deactivate or delete keys that are no longer needed.
- Contact support if you notice anything unusual with your account.
For sign-in or password-related issues, see Account & Login Troubleshooting.
Keep accounts attributable
Use individual accounts for each person who needs access to Undersign rather than sharing a single login. This helps keep account activity and signing requests associated with the appropriate user and makes account activity easier to review.