Data Processing Agreement
The processor terms for personal data in the content of OHSupport clients: scope, instructions, security measures, subprocessors, breach notice, deletion, audits and SCCs.
Last updated: October 5, 2026
1. Parties and scope
This Data Processing Agreement ("DPA") is part of the Terms of Service. The parties are you ("the customer") and Obsidian Heron, LLC ("Obsidian Heron", "we"). Obsidian Heron, LLC is a Wyoming limited liability company at 30 N Gould St Ste R, Sheridan, WY 82801. The DPA applies when OHSupport processes personal data for you.
- Roles. You are the controller of the personal data in your content. We are your processor.
- Customer personal data. This is the personal data in the conversations, contact details, messages and other data that you, your agents or your customers put in OHSupport. It also includes the personal data of your agents that the service keeps for your organization.
- Law. "Data protection law" means the GDPR, the UK GDPR, and other laws that apply to the processing.
The Privacy Policy describes the data that we control for our own purposes, for example sign-in data. This DPA does not apply to that data.
2. Details of the processing
| Item | Details |
|---|---|
| Subject | The storage, delivery and change of customer content in OHSupport, for you |
| Duration | While your organization exists, and the deletion period after it (section 9) |
| Nature | Storage, query, delivery of email and chat messages, deletion, and, if you enable it, automatic triage and draft replies with an AI model |
| Data subjects | The customers and other people who write to you, and your agents |
| Categories of data | The data that you put in your content: names, email addresses, messages, delivery status and customer data from your app. For agents: name, email address, role and sign-in data. |
| Special categories | None, unless you or your customers put them in the content. If they do, you are responsible for a lawful basis. |
3. Instructions
- We process customer personal data only on your documented instructions. These terms, your use of the agent app and the API, and your settings are your instructions.
- If the law makes other processing necessary, we tell you first, unless the law does not let us.
- If we think that an instruction breaks data protection law, we tell you.
4. Confidentiality
Each person who has access to customer personal data has an obligation of confidentiality. Only Obsidian Heron staff who need access to operate the service have it.
5. Security measures
We use these technical and organizational measures:
- Encryption in transit. All traffic to OHSupport uses HTTPS (TLS). The site sends HSTS headers.
- Encryption at rest. Cloudflare encrypts the data in D1 when it stores the data.
- Encrypted credentials. OHSupport encrypts the keys and tokens of integrations with AES-256-GCM before it stores them. Each encrypted value is bound to its owner.
- Tenant separation. Each record has a tenant id. Each request works in one tenant. A request for the data of another tenant gets
404. - Access controls. Agents have roles (owner, admin or agent). An agent can have access to some brands only. Sign-up is only by invitation. OHSupport keeps API keys only as hashes.
- Sessions and sign-in links. A session uses an HttpOnly cookie and ends after 12 hours without use. A sign-in link works for 10 minutes and one time. OHSupport keeps it only as a hash.
- Signed webhooks. OHSupport checks the signature and the time of each webhook that it receives. It signs the webhooks that it sends.
- Inbound email. A reply can join a conversation only if the sender is the contact of the conversation and passes the SPF, DKIM or DMARC check.
- Rate limits. OHSupport limits the rate of sign-in requests.
- Backups. Cloudflare D1 keeps point-in-time backups for a limited time.
- AI help. AI help is off until an owner enables it. OHSupport sends no AI text to a customer. An agent must read a draft and send it. OHSupport does not send the email address of the customer to the AI model.
The security overview gives more details. We can change these measures, but we do not make the protection of customer personal data less.
6. Subprocessors
- You give us general authorization to use subprocessors. The current list is on the subprocessors page.
- The emails that OHSupport sends for you pass through Refresh. Anthropic does an automatic review of the content of each email for Refresh. Anthropic gets the address of the recipient and the text of the email.
- If you enable AI help in Settings, Anthropic processes the subject and the text of the public messages of your conversations, the first name of the customer, your instructions and your help articles. OHSupport does not send internal notes. It gives a category, a priority, a summary and a draft reply to your agents. Anthropic does not use this data to train its models. You can switch AI help off at any time.
- We tell you 30 days before we add or replace a subprocessor. If you have a reasonable objection, you can stop the affected service. We then refund the fees that you paid in advance for it.
- Each subprocessor has a written contract with data protection obligations that are equal to this DPA. We are responsible for our subprocessors.
7. Help with the rights of data subjects
The agent app and the API let you find, change and read customer personal data. If a data subject sends a request to us about your content, we send it to you. We do not answer it ourselves, unless you tell us to. To delete or export data that you cannot reach in the agent app, send a request to privacy@ohsupport.app.
8. Personal data breach
- We tell you about a personal data breach that affects customer personal data without undue delay. The maximum delay is 72 hours after we know about the breach.
- The notice tells you what we know:
- the type of the breach
- the data and the data subjects that it affects
- the probable result, and the actions that we take
- We send the notice to the owners of the organization. We help you with your own notices to authorities and data subjects.
9. Deletion and return
- You can read your conversations and contacts at any time with the API. To get a copy of your content, send a request to us.
- OHSupport has no automatic deletion of customer content today. We keep it until you ask us to delete it, or until your organization closes.
- When you ask us to delete your content, or when your organization closes, we delete the content. We also delete the accounts of your agents that are not in another organization.
- If we close your organization for a reason other than a breach, you can ask for your content for 30 days. After that period, we delete it.
- Deleted data stays in backups until the backup period of Cloudflare D1 ends.
- We keep data longer only if the law makes it necessary. The obligations of this DPA continue for that data.
10. Audits
- We give you the information that is necessary to show that we obey this DPA, on request.
- One time each year, you can audit our compliance, or use an independent auditor. You must tell us 30 days before. You pay the cost of the audit. The auditor must accept an obligation of confidentiality.
- If a reasonable written answer or a third-party report gives the same information, we can use it in place of an audit.
11. International transfers
For transfers out of the European Economic Area, the Standard Contractual Clauses (SCCs) of Commission Implementing Decision (EU) 2021/914 apply by reference:
- Module 2 (controller to processor) when you are a controller
- Module 3 (processor to processor) when you are a processor
For the SCCs, the optional clauses do not apply. Clause 17 and Clause 18 use the law and the courts of Ireland. Annex I is section 2 of this DPA, Annex II is section 5, and Annex III is the subprocessors list.
For the United Kingdom, the UK International Data Transfer Addendum applies. For Switzerland, the SCCs apply with the changes that Swiss law makes necessary.
12. Liability and priority
The limitation of liability in the Terms of Service applies to this DPA. If this DPA and the Terms of Service do not agree about personal data, this DPA has priority. If the SCCs and this DPA do not agree, the SCCs have priority.
13. Contact
Send questions about this DPA to privacy@ohsupport.app. To get a signed copy, send an email to legal@ohsupport.app.