Legal

Data Processing Addendum

Last updated 4 October 2026. This DPA is between the customer (Controller) and Bedrock AI LLC d/b/a AnswerTide ("AnswerTide," the Processor).

Scope

The Processor hosts the AnswerTide service and processes visitor conversations, citations, handoff transcripts, and account data on the Controller's behalf to provide the service described in the Terms.

Instructions

The Processor processes personal data only on documented instructions from the Controller: providing the widget, answering from the Controller's index, handoff, billing, and security. The Processor will not sell that data or use it to train a general model.

Security

Tenant isolation is enforced with Postgres row-level security. The widget request path does not use a service-role key. Crawled content is treated as untrusted input. Action endpoints are guarded against SSRF. How long each kind of data is kept, and how it is deleted, is published at /retention; further measures are described at /security.

Subprocessors

The current list is published at /subprocessors and reproduced in Annex 1. Integrations that the Controller connects to its own accounts are listed in Annex 2. The Processor will post updates there before a new subprocessor processes customer personal data. Annex 3 lists the data subjects and categories of personal data.

Assistance, deletion, and audit

The Processor will assist with data-subject requests that the Controller cannot fulfill from the dashboard, delete or return personal data on request at the end of the service (demos are already hard-deleted at 7 days or on request), and make available information reasonably necessary to demonstrate this DPA.

International transfers

Infrastructure is hosted in the United States. If the Controller is subject to GDPR or similar law, the parties will execute standard contractual clauses on request. AnswerTide outbound email is US-only; this DPA does not change that.

Annex 1: Subprocessors

As of 4 October 2026. “Planned” providers are built but switched off and receive no customer personal data.

• Fly.io (In use): Application hosting. Data: All service data in transit and in memory. Region: United States.
• Supabase (In use): Postgres, Auth, pgvector. Data: Account data, indexed content, conversations, handoff transcripts. Region: United States.
• Anthropic (In use): Answer generation, and the AI Answer Check comparison in a Docs Answer Audit (inference only). Data: Visitor questions and retrieved excerpts of your content; for an audit, the AI Answer Check answers and excerpts of the audited public pages. Region: United States.
• Voyage AI (In use): Embeddings and rerank. Data: Your indexed content and visitor questions. Region: United States.
• OpenAI (In use): Browser voice (Talk) speech sessions, only when a customer turns voice on; the AI Answer Check in a Docs Answer Audit (inference only). Data: Visitor voice audio and its transcript, and the cited answer text AnswerTide sends to the session; for an audit, fixed questions naming the audited domain (no page text, email or personal data). Region: United States.
• Cloudflare (In use): Connection setup (STUN) for browser voice, only when a customer turns voice on. Data: The visitor's network address while the voice connection is set up; no audio, text or account data. Region: Global network.
• Stripe (In use): Payments and Customer Portal. Data: Billing contact and payment details. Region: United States.
• Resend (In use): Transactional email, when configured. Data: Recipient email addresses and message content, including handoff transcripts. Region: United States.
• Resend (inbound email) (Planned): Receiving email for the Inbox agent, and sending its replies from a business's own domain. Data: Emails your customers send to your forwarding address, and the replies sent back. Region: United States.
• Twilio (Planned): Phone numbers, inbound calls and voicemail for the Receptionist. Data: Caller phone numbers, call details, voicemail audio and its transcript. Region: United States.

Annex 2: Integrations the Controller connects

Used only when the Controller connects its own account with the provider; data goes to or comes from that account.

• HubSpot (Planned): CRM: contacts, notes and deals for leads. Data: Lead name, email, phone and company, a conversation or booking note, quote amounts.
• Zendesk (Planned): Helpdesk tickets for handoffs, and ticket status and notes read back. Data: Visitor email, the question, the transcript, pages visited and cited sources.
• Freshdesk (Planned): Helpdesk tickets for handoffs. Data: Visitor email, the question, the transcript, pages visited and cited sources.
• Help Scout (Planned): Helpdesk tickets for handoffs. Data: Visitor email, the question, the transcript, pages visited and cited sources.
• Intercom (Planned): Helpdesk tickets for handoffs. Data: Visitor email, the question, the transcript, pages visited and cited sources.
• Slack (app) (Planned): Handoff messages in your workspace, and your team's replies in the thread. Data: The visitor's question, email and transcript; your team's replies.
• Notion (Planned): Knowledge source: pages you pick are imported (read only). Data: The text of the pages you pick.
• GitHub (Planned): Knowledge source: public repositories you pick are imported (read only). Data: The text of the files you pick.
• Google (Planned): Google Docs as a knowledge source (read only), and Google Calendar for booking. Data: The text of the documents you pick; your calendar's free and busy times, and the events booked, with the visitor's name and email.
• Microsoft (Planned): Outlook calendar for booking, through Microsoft Graph. Data: Your calendar's free and busy times, and the events booked, with the visitor's name and email.
• Calendly (Planned): Booking through your Calendly page, and bookings read back. Data: Invitee name and email and the event booked.
• Shopify (Planned): Store app that adds the assistant to your store. Data: Your store's address and an access token; the app writes only the assistant's public key and reads no customer data.
• Zapier (Planned): Sends the events you subscribe a Zap to. Data: Leads, handoffs with their transcript, bookings and unanswered questions you subscribe to.

Annex 3: Data subjects and categories of personal data

Data subjects

• Visitors and customers of the Controller who use the assistant on its website, its help-center search, or (when switched on) its phone line or email address
• The Controller's team members who use the dashboard
• People whose details the Controller's team adds or sends to a connected integration

Categories of personal data

• Account data: team members' names, email addresses, roles and sign-in records
• Conversations: visitors' questions, the answers, the sources cited, feedback, and a random visitor ID
• Contact details visitors give: email address, and name, phone number or company when a form asks for them
• Handoff transcripts: the conversation sent to the Controller's team when a visitor asks for a person
• Voice: browser voice audio and its transcript when the Controller turns voice on; caller phone numbers, voicemail audio and transcripts once the phone line is switched on
• Email: emails received and replies sent through the Inbox agent, once it is switched on
• Content the Controller imports: text of its public pages, uploaded files and connected documents, which may contain personal data the Controller published
• Booking and CRM data: names, email addresses and booked times sent to a connected calendar or CRM
• Billing: billing contact; payment details are held by the payment processor
• Security and abuse records: audit log entries and one-way hashes of IP addresses used to limit abuse

Special categories: the service is not intended for them and is not for protected health information. See /healthcare for no-patient-details mode.

Signatures

When the parties sign a copy of this DPA, the signature blocks read:

Contact

privacy@answertide.com