Privacy Policy

Last updated: November 15, 2026

This policy explains how Mizuno Technologies LLC (“we”, “us”) handles information when you use Dextome: the website at dextome.com, the console at app.dextome.com, and the API at api.dextome.com. We wrote it to match how the service actually works. Questions: [email protected].

1. Two kinds of information

Account information is information about you as a user of Dextome: your email address, name, and how you use the service. We decide how it is used, so we are its controller.

Customer content is what you put into Dextome: documents, files, web pages you ask us to fetch, the text and embeddings we create from them, and the questions and answers sent through the service. We process customer content only to provide the service to you. You decide what goes in, so for personal information inside your content you are the controller and we act on your instructions.

2. What we collect

  • Account details: email address, and optionally your name and profile picture (taken from Google or another sign-in provider if you use one). Passwords are handled by our sign-in provider, Supabase; we never see or store them.
  • Organization details: organization and project names, member emails and roles, pending invitations, and a billing email address.
  • API keys: we store a one-way hash of each key plus its first characters and last four characters so you can recognise it. We cannot recover a lost key.
  • Your own model-provider keys (if you add an OpenAI, Anthropic or Cohere key): stored encrypted (AES-256-GCM) and never shown again after you save them.
  • Customer content: uploaded files (kept as the original file), text extracted from them and from web pages you ask us to fetch, and the embeddings (numeric representations) created from that text. For the chat API we also store each conversation's questions, answers and citations.
  • Usage data: counts of queries, answers, stored chunks, tokens and storage, used for plan limits and billing. Usage records contain counts, not the text of your queries.
  • Technical data: our application logs record request IDs, routes, response codes, timing and account identifiers. They are designed not to contain document text. Our hosting, network and sign-in providers process IP addresses and similar connection data to run and protect their services.

We do not use advertising or analytics trackers on dextome.com or in the console, and we do not buy information about you from others.

3. How we use it

  • To provide the service: store and index your content, answer your queries, and run your account.
  • To secure the service: authentication, preventing abuse, and keeping each customer's data separate.
  • To communicate with you: sign-in and password emails, team invitations, and important service notices.
  • To enforce plan limits and, once paid plans launch, to bill you.
  • To meet legal obligations and enforce our Terms of Service.

We do not sell your information, and we do not use your customer content to train AI models.

If you are in the EEA or UK, our legal bases are: performing our contract with you (providing the service), our legitimate interests (security, abuse prevention, improving reliability), and legal obligations.

4. AI model providers

Dextome sends text to AI providers to do its job. When you add content, its text is sent to OpenAI to create embeddings. When you search, your query is sent to OpenAI. When you ask for an answer, your question and the retrieved passages are sent to Anthropic (or to OpenAI, if you choose an OpenAI model). If you add your own provider key for a project, answers for that project use your key and your agreement with that provider; ingestion currently always uses our OpenAI account.

We use these providers' business API services. Under their terms, data sent through their APIs is not used to train their models by default; they may keep it for a limited period to monitor for abuse. See their policies linked below.

5. Service providers

We share information only with providers that help us run Dextome, and only what they need:

ProviderWhat forInformation involved
SupabaseDatabase (PostgreSQL) and account sign-inAccount details, document text and embeddings, conversation history, usage counts; sign-in records
CloudflareFile storage (R2), DNS and networkUploaded original files; network request data such as IP addresses
RenderApplication hosting (API, background worker, console)All data processed by the service while it runs; request logs
OpenAICreating embeddings (and answers, when you choose an OpenAI model)Document text at ingestion; search queries; questions and retrieved passages for answers
AnthropicGenerating answersQuestions and the retrieved passages used to answer them
StripeSubscriptions, payments, invoices and sales tax for paid plansBilling name, email and address, tax ID, payment details (held by Stripe, never by us), usage totals
ResendSending email (sign-in confirmations, password resets, team invitations)Recipient email address and message content

If you sign in with Google, Google shares your name, email and profile picture with us under its own policy. Stripe processes payments for paid plans: you enter card details on Stripe's pages, and we receive your billing contact details, subscription status and the last four digits of your card, never the full card number. We send Stripe your organization's usage totals so it can bill overage. We will update this list before adding a provider that handles your information.

We may also disclose information if required by law, to protect the rights and safety of our users or others, or as part of a merger or acquisition, in which case this policy continues to apply.

6. Where your data is stored

Our database and application servers are in the United States (US East). Uploaded files are stored with Cloudflare R2 in North America. If you use Dextome from outside the United States, your information is transferred to and processed in the United States.

7. How long we keep it, and deletion

  • Deleting a document immediately deletes its extracted text and embeddings. The original uploaded file currently stays in storage until your account is deleted; email us if you need specific files removed sooner and we will do it.
  • Deleting an index deletes its documents, text, embeddings and conversations.
  • Conversations created through the chat API are kept until you delete them or delete their index.
  • Usage records (counts only) are kept while your account exists.
  • Deleting your account or organization: there is no self-service button yet. Email [email protected] from your account email and we will delete your account, organization data, customer content and stored files within 30 days. Database backups are kept for up to 7 days, so deleted data can remain in backups for that long.

8. Security

Each customer's data is kept separate by our application, and every request is limited to the organization and project of the API key or signed-in user making it. Traffic is encrypted in transit (TLS). Our database and file storage providers encrypt data at rest. API keys are stored as one-way hashes and your own provider keys are encrypted. No system is perfectly secure; if a breach affects your information we will notify you as required by law. Report security issues to [email protected].

9. Cookies and local storage

  • Console: a sign-in cookie that keeps you logged in, and a cookie that remembers which project you last selected. Both are necessary for the console to work.
  • dextome.com: no cookies. Your light/dark theme choice is saved in your browser's local storage.

10. Your rights and choices

You can view and update your account details and delete your content in the console at any time. You can also ask us to access, correct, export or delete your information, or to restrict or object to how we use it, by emailing [email protected]. We will respond within 30 days and will not treat you differently for asking. If you are in the EEA or UK you can also complain to your data protection authority.

If your request is about personal information inside a customer's content (for example, a document a company uploaded), please contact that customer; we will help them respond.

California residents: we do not sell or share personal information for cross-context behavioral advertising, and we do not use sensitive personal information to infer characteristics about you.

11. Children

Dextome is a service for businesses and developers and is not directed to children under 16. We do not knowingly collect information from them; if you believe a child has given us information, contact us and we will delete it.

12. Changes to this policy

We will update this page when our practices change and change the “Last updated” date. If a change is significant, we will tell account holders by email or in the console before it takes effect.

13. Contact

Mizuno Technologies LLC
[email protected]