Subprocessors
Last updated: October 9, 2026
SimplySigned uses the following third-party subprocessors to deliver the Services. Each infrastructure subprocessor is bound by contractual obligations to protect personal data and may only process it on our instructions. This list is referenced by our Privacy Policy and Data Processing Addendum.
Infrastructure and service subprocessors
| Subprocessor | Purpose | Location |
|---|---|---|
| Clerk | Authentication, sessions, organizations and roles | United States |
| Supabase | Database, file storage, and serverless functions (hosted on AWS) | United States |
| Expo (EAS Hosting) | Hosting of the SimplySigned application (dashboard.simplysigned.app) | United States |
| Twilio | SMS delivery of signing links and notifications (toll-free messaging) | United States |
| SendGrid (Twilio) | Transactional email delivery | United States |
| Stripe | Subscription billing and invoicing | United States |
| GitHub | Hosting of the marketing website | United States |
Customer-directed integrations
The following platforms send or receive data only when a Customer connects them, and only for that Customer's own account. They act on the Customer's instructions, not ours, and are governed by the Customer's agreement with each platform.
| Platform | Purpose |
|---|---|
| Google Ads | Conversion events for the Customer's own campaigns |
| Zapier | CRM and workflow sync configured by the Customer |
| CallRail | Inbound call and form lead ingestion configured by the Customer |
| WordPress / Gravity Forms (Customer's own website) | Inbound lead ingestion from forms the Customer operates |
Changes
We will update this page at least 14 days before adding a new infrastructure subprocessor. If we must replace a subprocessor urgently to maintain security or availability, we will update this page as soon as reasonably possible. Customers who want notice of changes can email info@simplysigned.co and ask to be added to the subprocessor notification list.