Data processing addendum
How TextSend processes personal data on your behalf as your processor, and what it commits to while doing so.
1. About this addendum
This addendum describes the processing relationship between a TextSend customer and TextSend.
2. Roles
- You, the customer, are the data controller. You decide what personal data (your end customers' phone numbers, message content) you send through TextSend and for what purpose, and you are responsible for the lawful basis for that processing. See the terms of service for your responsibilities.
- TextSend is the data processor. TextSend processes personal data only to provide the contracted service (routing, transcript delivery, delivery-status reporting, and opt-out enforcement) on your documented instructions. It does not process that data for any independent purpose of its own.
3. Scope and purpose of processing
| Element | Description |
|---|---|
| Subject matter | SMS/MMS relay and routing between your Twilio account and Zendesk tickets |
| Duration | For the life of your subscription, plus the retention and deletion bounds after termination set out below |
| Nature and purpose | Routing, delivery-status reporting, opt-out enforcement, and account diagnostics |
| Categories of data subjects | Your end customers (message senders and recipients) and your Zendesk agents |
| Categories of personal data | Phone numbers; message content (transient only); Zendesk agent identity claims used for authorization; billing and subscription state |
TextSend processes only these categories of personal data, and only for these purposes. TextSend processes personal data only on your documented instructions, meaning providing the TextSend service as you have configured it, except where applicable law requires otherwise.
4. Security measures
TextSend implements the following measures. The security page is the kept-current version of this list.
- TLS 1.2 or later in transit; encryption at rest supplied by the hosting environment.
- Twilio and Zendesk credentials held only in the backend's secret store, reachable by the backend alone, never returned to the browser, and deleted when deletion starts: usually about a week (7 to 8 days) after the app is removed, always within 30 days of removal.
- Every stored record is isolated by tenant; a read that crosses customers raises an error rather than silently leaking data.
- Mandatory Twilio webhook signature validation, and server-side authorization against a verified identity on every other backend request.
- Redaction guards at the storage and telemetry layers, backing a design that keeps message bodies, credentials, full media URLs, and unredacted phone numbers out of storage and logs. The storage guard refuses a value that is, as a whole, a phone number in international (+) format or a URL with a path; text your admins type into a saved SMS template is not checked beyond that.
- Dependency, secret, and static-analysis scanning before every deployment.
5. Confidentiality
TextSend ensures that personnel and systems that access personal data are bound by confidentiality obligations. This is enforced technically, by the identity verification and tenant-isolation controls described on the security page, rather than by policy alone.
6. Sub-processors
TextSend's current sub-processors are Amazon Web Services (hosting, database, and storage) and Zendesk (Marketplace distribution and checkout). Payments go through Stripe, which acts as an independent controller of payment data rather than as a TextSend sub-processor. Twilio is your own contracted vendor, not a TextSend sub-processor. The sub-processors page has the full detail.
TextSend will not engage a sub-processor without disclosing it on that page. TextSend will email you at least 30 days before a new sub-processor begins processing your personal data, and will update the sub-processors page at the same time.
7. Assistance and audits
- TextSend will assist you in responding to data subject requests, to the extent TextSend holds the relevant data. See the privacy policy for how such requests are handled.
- TextSend will make available, on reasonable request, the information necessary to demonstrate compliance with this addendum, including its security, data-handling, and threat-model documentation and the results of its pre-deployment scanning.
- Audits under this addendum take the form of that documentation review, which you may request once a year. No third-party audit or penetration test is offered beyond it.
- An external security review has not yet taken place.
8. Breach notification
TextSend will notify you without undue delay, and within 72 hours of confirming a breach affecting your personal data. The notice will describe the nature of the breach, the data categories affected, and the remediation steps taken or planned. TextSend's internal incident procedures for credential exposure and cross-customer data risk feed this notification.
9. Retention
Message bodies are not retained by TextSend beyond the duration of processing; the permanent copy lives in your own Zendesk instance, which you control. Other bounds:
- MMS media: 24 hours.
- Credentials: deleted when deletion starts, usually about a week (7 to 8 days) after the app is removed and always within 30 days of removal.
- Phone numbers and routing metadata: within 30 days after deletion starts.
- Saved SMS templates: until an admin deletes them; after the app is removed, within 30 days after deletion starts.
- Message status and IDs: 90 days by default.
- Audit events: 12 months, without message body.
- Backups: database snapshots within 54 hours, database copies within 6 days (no message bodies, media or credentials); every backup copy of a removed account's metadata within 30 days after deletion starts.
10. Deletion and return
- On termination (uninstall): deletion usually starts about a week (7 to 8 days) after the app is removed, and always within 30 days of removal: TextSend checks daily and starts 7 days after it first sees the app missing. When deletion starts, TextSend deletes your Twilio and Zendesk credentials and stops all processing. The remaining account metadata is purged within 30 days after deletion starts.
- TextSend does not offer a bulk data return or export mechanism. The message content itself already lives in your own Zendesk instance, which you keep and control independently of uninstalling TextSend.
11. International transfers
TextSend processes and stores your personal data in the United States, on Amazon Web Services in the us-east-1 (N. Virginia) region. Personal data you send through TextSend from outside the United States is transferred there.
12. Governing law and entity
This addendum is between you and Ampliat LLC. Legal notices to TextSend go by email to support@textsend.app.
This addendum is governed by the laws of Pennsylvania, and the courts of Pennsylvania have jurisdiction over any dispute arising from it.