Sub-processors & DPA
SafeHanded is designed to hold as little as possible about your users, and to be transparent about who processes it.
What SafeHanded processes
Section titled “What SafeHanded processes”- Subject data: name and email/UPN (and a phone number only where SMS is used), plus the encrypted payload — which SafeHanded can’t read. The payload is deleted on purge; the request record is kept for your audit retention period.
- Member data: the accounts of your own staff (name, email, role, and their public identity keys).
- Operational data: the audit log, settings, branding and billing details.
Plaintext credentials and decryption-capable keys are never processed — they exist only in browsers.
Data processing agreement (DPA)
Section titled “Data processing agreement (DPA)”The Data Processing Agreement forms part of the Customer Terms and applies automatically, covering UK GDPR and EU GDPR Article 28. You don’t need to sign it; a countersigned copy is available on request.
Sub-processor list
Section titled “Sub-processor list”SafeHanded publishes the list of sub-processors it relies on (hosting, payments, email delivery, SMS and anti-abuse checks) and gives 30 days’ notice before adding or replacing one. See the current list at safehanded.com/sub-processors.
Requesting documents
Section titled “Requesting documents”For a countersigned DPA or a security questionnaire, email privacy@safehanded.com.