Data Processing Addendum
Last updated October 7, 2026
1. Definitions
Terms not defined here have the meaning given in the GDPR (Regulation (EU) 2016/679), UK GDPR, or Swiss FADP as applicable. “Personal Data,” “Controller,” “Processor,” “Sub-processor,” and “Data Subject” have those statutory meanings.
2. Subject Matter and Duration
Berchtold processes Personal Data to provide the Service for the duration of the Controller's subscription, plus a limited post-termination period for billing and legal hold purposes (see Section 14).
3. Nature and Purpose of Processing
We process Personal Data only to (a) operate the Service as contracted, (b) respond to Controller instructions, (c) comply with legal obligations, and (d) ensure the security and integrity of the platform.
4. Type of Personal Data
The categories of Personal Data we typically process include:
- Identification and contact data: names, email addresses, phone numbers, postal addresses, job titles, and account credentials (hashed).
- CRM data: birthdays, home anniversaries, relationships (for example, spouse or lender), lead sources and campaign details, notes, tasks, and logged calls, texts, emails, and meetings.
- Transaction data: properties, deal and contract terms, prices, financing, deadlines, parties to a transaction, and commission.
- Communications: email content logged from connected Gmail accounts, email sent through the Service, voice note transcripts, and website chat messages.
- Email and consent data: list subscriptions, delivery, bounces, opens and clicks, and proof of consent (the page, form, consent wording, time, IP address, and user agent).
- Website activity: a random visitor ID, pages viewed, clicks, and events on the Controller's websites.
- Social data: names and comments of people who comment on the Controller's connected social accounts.
- Billing: postal addresses, tax IDs, last 4 digits of the payment card, card brand, and expiration. Full card numbers and CVCs are never seen by Berchtold. Stripe processes them under PCI DSS Level 1.
- Usage: user IDs, email addresses, user agents, timestamps of in-app actions, rate-limit counters, and push notification subscriptions.
- Any other Personal Data the Controller chooses to upload, configure, or process through the Service.
5. Categories of Data Subjects
- The Controller's employees, agents, contractors, and outside transaction coordinators who use the Service.
- The Controller's clients, leads, and contacts, and the parties to their transactions (for example, lenders, title and escrow officers, and other agents).
- Email recipients and correspondents, form submitters, website visitors, and website chat users.
- People who comment on the Controller's social accounts.
6. Controller Obligations
The Controller represents and warrants that:
- It has a lawful basis under the GDPR (or applicable law) for every category of Personal Data it instructs us to process.
- It will not provide us with special categories of data (Article 9 GDPR) unless explicitly agreed in writing.
- Documented instructions to Berchtold include this DPA, the Terms of Service, and any later written communication to [email protected].
7. Processor Obligations
Berchtold will:
- Process Personal Data only on documented Controller instructions, except as required by applicable law (and where law requires deviation, we will notify the Controller unless the law prohibits notice).
- Ensure personnel with access to Personal Data are bound by confidentiality obligations.
- Implement the technical and organisational measures set out in Annex 2 (Security Measures).
- Assist the Controller in responding to Data Subject Rights requests (Articles 12–22 GDPR) and in conducting Data Protection Impact Assessments (Article 35 GDPR) as reasonably required.
- Make available to the Controller the information necessary to demonstrate compliance, and contribute to audits as set out in Section 12.
8. Sub-processors
The Controller authorises Berchtold's engagement of the Sub-processors listed in Annex 1. We will give the Controller at least 30 days' notice (by email or in-app announcement) of any new Sub-processor engagement. The Controller may object on reasonable grounds, in which case the parties will work in good faith to resolve the objection; failing resolution, the Controller may terminate the Service.
Berchtold remains liable for the acts and omissions of its Sub-processors in the same manner as for its own.
9. International Transfers
Berchtold is established in the United States. Personal Data of EU/EEA, UK, and Swiss Data Subjects is transferred to the United States and, where Sub-processors host data elsewhere, to those jurisdictions.
For such transfers we rely on (a) the EU Standard Contractual Clauses (Commission Implementing Decision (EU) 2021/914), Module 2 (Controller-to-Processor) or Module 3 (Processor-to-Processor) as applicable; (b) the UK International Data Transfer Addendum where the data exporter is UK-based; and (c) the equivalent Swiss FADP transfer instrument. The SCCs are deemed incorporated into this DPA by reference and prevail in the event of conflict.
10. Security Measures
See Annex 2 for the technical and organisational measures we maintain. We will not materially reduce these measures during the term of the subscription.
11. Data Subject Rights
Where the Controller cannot fulfil a Data Subject Rights request directly through the Service's self-serve tools (export/delete on Profile, member removal from Org admin), we will assist on reasonable written request to [email protected] and respond within 30 days.
12. Audits
On the Controller's written request (no more than once per 12-month period, except following a material security incident or as required by a supervisory authority), Berchtold will provide a copy of our most recent independent audit report (when available), our security questionnaire response, and answer reasonable follow-up questions. On-site audits are by mutual agreement and at the Controller's expense.
13. Data Breach Notification
We will notify the Controller without undue delay and no later than 72 hours after becoming aware of a Personal Data Breach affecting the Controller's data. Notification will include the information required by Article 33(3) GDPR to the extent known at the time of notification, with updates as the investigation progresses.
14. End of Processing
Customer Content stays available after a subscription ends, so the Controller can export it or choose a plan again. Admins can export contacts from the CRM, and we will provide other Customer Content on reasonable written request. On written request from the Controller, Berchtold will delete (or anonymise) Customer Content within 30 days, except for (a) backups, which expire within 14 days, and (b) records we are legally required to retain. These exceptions remain subject to the confidentiality and security obligations of this DPA until destroyed.
15. Liability
Each party's liability under this DPA is subject to the limitations of liability in the Terms of Service. Nothing in this DPA limits either party's liability for damages caused by infringement of the GDPR to the extent such liability cannot be limited under applicable law.
16. Conflicts
In the event of any conflict between this DPA and the Terms of Service, this DPA prevails with respect to the processing of Personal Data. In the event of any conflict between this DPA and the SCCs, the SCCs prevail.
17. Governing Law
Except where the SCCs require otherwise (in which case the law designated by the SCCs governs the SCCs), this DPA is governed by the law of the State of Missouri, United States.
Annex 1 — Sub-processors
Current Sub-processors authorised under this DPA:
- Google LLC (Google Cloud and Firebase) — Sign-in, the database, server functions, file storage, encryption keys (Cloud KMS) and the content-analysis service (Cloud Run). Vertex AI turns knowledge-base text and website chat questions into search vectors. Google Places looks up business locations. US.
- Google LLC (Gemini API) — Transcribes voice notes, reads contact details from photos and PDFs, reads brand documents you import, and answers AI Visibility audit questions. US.
- Google LLC (Google Tag Manager and Google Analytics) — Measures how people use the app. Loaded on app pages, including hosted form and email preference pages. US.
- Netlify, Inc. — Hosts the web app and the email link domain (go.berchtold.ai). US.
- Anthropic, PBC — Claude models for the assistants and agents, CRM update suggestions, the contract reader, daily deal reviews, account research, website chat and comment scoring. US.
- OpenAI, Inc. — AI Visibility audits only: questions about your business are sent to ChatGPT to see how it answers. US.
- Resend, Inc. — Sends account and billing email, and the email campaigns and one-to-one email your workspace sends. Records delivery, bounces, and, when tracking is on, opens and clicks. US.
- Stripe, Inc. — Payments, invoices, tax calculation and disputes. US and EU.
- Brave Software, Inc. — Web and news search for market research and, when account research is on, company research. US.
- DataForSEO — Search rankings, keywords and site crawls for the SEO and content features.
- Local Falcon — Local map rankings for your business locations and keywords. US.
- OpenWeather — Weather answers in the website agent chat. Receives the place asked about.
- Browser push services (Apple, Google, Mozilla and others) — Deliver the push notifications you turn on to your browser or phone. They receive the notification text.
These services process Personal Data only when the Controller or its users connect them, and are governed by their providers' terms:
- Google (Gmail, Google Drive, Google Analytics, Search Console, Google Ads) — Connected by each person or by an admin.
- Microsoft (Bing Webmaster Tools) — Search reporting.
- Meta (Facebook and Instagram) — Publishing, post performance and comments.
- X — Publishing.
- Buffer — Social post scheduling.
- Slack — Notifications to your Slack workspace.
- WordPress — Posts and media on your site.
- ActiveCampaign — Contacts, deals, notes and tags, when you connect an account.
- Mailchimp — Audiences, campaigns and reports, when you connect an account.
- iHomefinder — Reads your MLS listings and their status.
- dotloop — Loops for your deals: their details, participants and documents, when each person connects their own account. The AI reads loop contracts to suggest deal updates.
- DocuSign — In beta: envelopes sent for signature in the agent's name, their recipients and status, and the signed documents, when each person connects their own account.
- Calendly — Bookings, which become contacts, activity and appointments, when each person connects their own account.
- Handwrytten — Handwritten cards a person sends: the message and the sender's and recipient's names and mailing addresses, when they connect their own account.
- Canva — Listing designs from your brand templates, when each person connects their own account.
- Pexels — Stock photo search.
Annex 2 — Security Measures
- Encryption in transit: TLS 1.2+ for all public endpoints.
- Encryption at rest: AES-256 for Firestore documents (Google-managed keys). Integration credentials are encrypted with a separate data key for each credential, wrapped by a Cloud KMS key.
- Authentication: Firebase Authentication. Key actions, such as creating an organization or subscribing, require a verified email address.
- Authorisation: Role-based access control on every API endpoint, with built-in roles (including Admin and Agent), custom roles, and record ownership so agents see only their own records unless granted access to all. Organization and workspace membership are tracked separately.
- Audit logging: Material actions (ownership transfers, plan changes, deletions, integrations) are logged with the actor and a timestamp; in-app actions also record the user agent.
- Network: All compute runs behind provider-managed firewalls. Webhook endpoints verify signatures (Stripe, OAuth callbacks) before any state mutation.
- Backups: Daily Firestore backups retained for 14 days, plus point-in-time recovery for the last 7 days.
- Incident response: Documented procedure; customer notification within 72 hours of confirmed breach.
- Personnel: All staff with production access are bound by written confidentiality obligations.
Questions or DPA signature requests: [email protected]