Deep Interactions

Legal

Privacy Policy

Effective November 9, 2026

1. About this policy

This Privacy Policy explains how Deep Interactions Inc. (“Deep Interactions,” “we,” “us,” or “our”) collects, uses, shares, and protects personal information when you use the Deep Interactions workspace, the Di agent, and our related websites and services (the “Services”). Terms that this policy does not define, such as “Your Content,” have the meaning given in our Terms of Service.

Deep Interactions is the controller of the personal information this policy describes. When the Services store data that a customer’s app collects from its own end users, the customer controls that data and we process it on the customer’s behalf, as described in Apps you build and deploy.

2. Information we collect

We collect the following information:

  • Account information. Your email address, name, profile picture, and sign-in provider. When you sign in with Google or GitHub, we receive this information from that provider. We also record which version of our Terms of Service you accepted and when.
  • Your Content. Messages you send to Di, board content, app source code, images and files you upload, and the history of changes in each space. Other members of a space also provide content, and it can include information about you.
  • Space and team information. The spaces you create or join, your role in each space, and invitations. For an ownership transfer, we can also record the organization you belong to and the evidence we used to verify it.
  • Billing information. Your plan, credit balance, purchases, invoices, and Stripe customer identifier. Stripe collects your payment card details. We do not receive full card numbers.
  • Usage information. How you use the Services, such as your Di requests, the model and sandbox resources they used, their cost, your sign-in times, and your deployments.
  • Device and technical information. Your IP address, browser type, device information, and similar data that our hosting and authentication providers record in their logs.
  • Product analytics and advertising measurement. The pages you view in the workspace, and whether you sign up, start a free trial, or subscribe, as described in Advertising measurement and Cookies and browser storage.
  • Communications. Messages you send us, such as support requests, feedback, and sales inquiries.

3. How we use information

We use personal information to:

  • provide the Services, including running Di, previewing and deploying apps, and keeping spaces in sync between members;
  • create and secure your account and authenticate you;
  • measure usage, charge credits, process payments, and prevent billing abuse;
  • provide support and respond to your requests;
  • send service emails, such as sign-in links, billing notices, and changes to our terms;
  • send product news and marketing emails, which you can unsubscribe from at any time;
  • detect, investigate, and prevent security incidents, fraud, and violations of our Terms of Service;
  • understand and improve the Services, using usage information and aggregated data;
  • measure whether our advertising leads to sign-ups, free trials, and subscriptions, as described in Advertising measurement; and
  • comply with legal obligations and enforce our rights.

We do not use Your Content to train artificial intelligence models.

If you are in the European Economic Area, the United Kingdom, or Switzerland, we rely on these legal bases:

  • Contract. To provide the Services you request, including running Di, billing, and support.
  • Legitimate interests. To secure and improve the Services, prevent fraud and abuse, measure our advertising, and send marketing to existing customers where the law permits. We balance these interests against your rights.
  • Consent. Where we ask for it, such as for certain marketing emails, and for advertising cookies where the law requires it. You can withdraw consent at any time.
  • Legal obligation. To meet tax, accounting, and other legal requirements.

5. How Di processes your content

To answer a request, Di sends the relevant parts of the space, such as messages, board content, app files, and images, to the AI model providers that power it, including Anthropic, OpenAI, and Microsoft Azure. Image generation and web research use OpenAI. Web research queries can include text from your board.

When you choose Dictate, your browser uploads that recording to Deep Interactions. We send it to OpenAI only for transcription, return the text to your draft, and do not store the recording.

Di runs commands in an isolated sandbox hosted by Vercel. The sandbox holds a working copy of the space while Di works on it.

AI model providers process this content to generate Di’s responses. Under their terms, they can retain it for a limited period to monitor abuse. Their commercial terms do not permit them to use this content to train their models.

6. How we share information

We share personal information only as described below:

  • Members of your spaces. Other members of a space can see its content, its conversation with Di, and its history. They can also see your name, profile picture, role, and live presence, such as your cursor position.
  • Public deployments. When a member deploys an app, anyone with its address can see the app and the content it contains.
  • Service providers. Companies that process information for us under contract: Supabase (database, authentication, and file storage), Vercel (application hosting, sandboxes, and app hosting), Anthropic, OpenAI, and Microsoft Azure (AI models), Stripe (payments), GitHub (code repositories), Netlify and Cloudflare (app hosting), Google (sign-in, tag management, and deployed-app analytics), PostHog (product analytics), and the providers that deliver our email.
  • Advertising partners. Meta, which receives the limited information described in Advertising measurement so we can measure our ads, and Snitcher, which identifies visitors to our marketing site for sales outreach. Both run only while your marketing cookie choice allows them. They process that information under their own terms.
  • Legal and safety. When we believe the law or legal process requires disclosure, or disclosure is needed to protect the rights, property, or safety of our users, the public, or Deep Interactions.
  • Business transfers. As part of a merger, acquisition, financing, or sale of assets, subject to this policy.
  • With your consent. When you ask us to share information or agree to it.

We do not sell your personal information. Sending advertising measurement information to Meta can count as “sharing” for cross-context behavioral advertising under some US state laws. You can opt out as described in Your rights and choices.

7. Service providers

These providers process personal information for the Services:

  • Supabase stores the database, authentication, and uploaded files.
  • Vercel hosts the workspace and the sandbox where Di runs.
  • Anthropic, OpenAI, and Microsoft Azure generate Di’s replies. OpenAI also generates images, runs web research, and transcribes Dictate recordings.
  • Stripe processes payments. We do not receive full card numbers.
  • GitHub hosts repositories a team chooses to connect.
  • Netlify and Cloudflare host deployed apps when a team selects that host.
  • Google provides sign-in, Tag Manager, deployed-app analytics, and service email.
  • PostHog receives product analytics unless you turn it off.
  • Meta receives advertising measurement while marketing cookies are allowed.
  • Snitcher identifies visitors to deepinteractions.ai for sales outreach while marketing cookies are allowed. It can match a visitor to a company and, where it holds a profile, a name and job. It runs only on the marketing site, never inside the workspace. Our code does not send your account email or name to Snitcher.

A service you choose to connect, such as Slack, Telegram, Miro, or Figma, is governed by that service’s terms.

8. Apps you build and deploy

Apps built with the Services can collect information from their own end users, for example through the Deep Interactions data and authentication service. The customer who owns the space controls that information, and we process it only to provide the service to that customer. End users should read the privacy notice of the app they use and send requests to its owner.

Deployed apps include Deep Interactions-managed usage analytics unless the space Owner turns them off. The deployed-app analytics terms describe what those analytics collect.

9. Advertising measurement

One cookie choice covers our marketing site, deepinteractions.ai, and the workspace. The banner on the marketing site records it, and the workspace reads the same cookie. If you are in the United Kingdom, the European Economic Area, or Switzerland, or we do not know your location, advertising measurement stays off until that choice allows it. Elsewhere it runs unless you reject it. When your browser sends Global Privacy Control, it stays off in the workspace. While advertising measurement is allowed, the workspace loads Google Tag Manager, which loads the Meta Pixel, and the marketing site loads Snitcher, which identifies a visitor for sales outreach. Snitcher can match a visitor to a company and, where it holds a profile, a name and job. Our code does not send your account email or name to Snitcher. The pixel sends Meta the pages you view and three events: completing registration, starting a free trial, and subscribing. The trial and subscription events include the plan name, price, and currency. The pixel also sets the advertising cookies described in Cookies and browser storage. We keep those advertising events for 90 days.

Our server sends the same three events to Meta’s Conversions API only while advertising measurement is allowed, so they are counted when the browser does not report them, for example when a trial converts to a paid subscription automatically. Each server event carries a one-way hash of your email address and account identifier, and, when the event follows an action in your browser, your IP address, browser type, and the pixel cookies. Meta uses this information to match the event to an ad and to count each event once. Meta does not receive your name, Your Content, your payment details, or any invite link.

If your browser sends Global Privacy Control, we treat that as a request to keep advertising measurement off in the workspace. You can change the marketing cookie choice at any time under Privacy choices on deepinteractions.ai; the workspace links there from Settings. Rejecting it stops later sharing with Meta and Snitcher. It does not erase events they have already received. To ask about deletion, email legal@deepinteractions.ai.

10. Cookies and browser storage

Deep Interactions sets three cookies. A session cookie keeps you signed in. A device identifier, di_anon_id, links anonymous use and trial credits to your browser for one year. A choice cookie, di_consent, is shared between deepinteractions.ai and the workspace and stores your analytics and marketing choices. It lasts six months and contains no account identifier. The session cookie and di_anon_id are necessary for the Services to work. The Cookie Policy lists each cookie.

The Meta Pixel described in Advertising measurement sets two advertising cookies, _fbp and _fbc, only while marketing cookies are allowed. They identify your browser and the ad you clicked. We keep them for 90 days. Rejecting marketing cookies expires them in your browser. It does not delete copies Meta already stored.

Product analytics runs unless you turn it off under Settings, Product analytics, in the workspace, or rejected cookies on deepinteractions.ai. While it runs, PostHog receives the pages you view and a fixed list of product events, with a pseudonymous id, plus masked session replays that help us understand navigation and interaction problems. Replay masks text and input values and excludes board content, media, embedded apps and network bodies. We do not send your email address, name, prompts, uploaded files or Dictate audio. The analytics identity stays in memory. We keep product events for 13 months. Turning Product analytics off also stops session replay.

The workspace also stores a copy of your spaces and your preferences in your browser’s local database, so the Services load quickly and keep unsaved edits. Clearing site data in your browser removes this copy.

11. International transfers

Our primary database is hosted in the European Union (Ireland). Our service providers process information in the United States and other countries. When we transfer personal information from the United Kingdom or the European Economic Area to a country that does not have an adequacy decision, we use the European Commission’s standard contractual clauses. For a transfer from the United Kingdom, we use those clauses with the United Kingdom addendum. These clauses are contract terms that require the recipient to protect the information.

12. Retention

We keep your account, prompts, files, and space content for the life of the account. After we verify a closure request sent to legal@deepinteractions.ai, we delete or anonymize that personal information within 30 days. When an Owner deletes a space, we remove its content from active systems when the deletion finishes, and we delete backup copies of that content within 90 days. A Dictate recording is not kept after the transcription response returns. Model providers may keep prompts they receive for up to 30 days to monitor abuse. We do not use Your Content to train artificial intelligence models. Product analytics events are kept for 13 months. Advertising measurement events are kept for 90 days. Invoices and payment records are kept for 7 years after the charge. Security and credit-abuse logs are kept for 12 months. Each privacy choice is kept for 3 years. We keep a record longer when the law requires it for tax, accounting, or a legal claim.

13. Security

We use technical and organizational measures to protect personal information. These include encryption in transit, access controls that limit each space to its members, isolated sandboxes for Di, and restricted staff access. Authorized staff access account and space information only to provide support, manage billing, and investigate abuse or incidents.

No method of transmission or storage is completely secure, so we cannot guarantee absolute security.

14. Your rights and choices

Depending on where you live, you can have the right to access, correct, delete, or export your personal information, to object to or restrict certain processing, and to withdraw consent where we rely on it. Withdrawing consent does not affect processing that already took place.

You can delete spaces you own and unsubscribe from marketing emails through the link in each email. You can turn product analytics off under Settings, Product analytics, and change the marketing cookie choice under Privacy choices on deepinteractions.ai. To make any other request, email legal@deepinteractions.ai. We will verify your request before we act on it. Where the law allows, you can use an authorized agent.

We will not discriminate against you for exercising your privacy rights. If you are in the European Economic Area, the United Kingdom, or Switzerland, you can also complain to your local data protection authority.

15. Children

The Services are not directed to anyone under 18, and we do not knowingly collect personal information from children. If you believe a child gave us personal information, contact us and we will delete it.

16. Changes to this policy

We may update this policy. We will post the updated policy on this page with a new effective date. For material changes, we will notify you by email or in the Services before the changes take effect.

17. Contact

Send privacy questions and requests to legal@deepinteractions.ai, or write to us at the address below. We have not appointed a data protection officer. We have not appointed a representative in the United Kingdom or the European Union.

Deep Interactions Inc.
2261 Market Street STE 14515, San Francisco, CA 94114