Skip to main content
Evidence-native legal mattersEarly access · invite-only
ALLEGATAIAlgodyne

Privacy Policy

Privacy Policy and data processing

What AllegatAI collects, why, where it goes, who processes it, how long it is kept and how to have it deleted. Matter content is confidential by default; this page says exactly what that means.

Effective November 10, 2026

1. Who is responsible for what

Algodyne Corporation, 131 Continental Dr, Suite 305, Newark, DE 19713, United States ("Algodyne"), operates AllegatAI.

For account and billing data (who you are and how you pay) Algodyne is the controller (in the terms of Japan’s Act on the Protection of Personal Information, the business handling personal information).

For Customer Content (matter material you or your colleagues upload or create, including the personal information of clients, witnesses, counterparties and others inside it) you are the controller and Algodyne is your processor (an entrusted party under the APPI). We process Customer Content only on your documented instructions, which are these Terms, the Privacy Policy, and your use of the Service’s settings. This page is the data processing agreement between us; if you need a separately signed copy, write to us.

2. What we collect

  • Account data: your name, email address, passkey public keys, workspace role and matter memberships.
  • Session and security data: session identifiers, IP address and browser user-agent for each session, sign-in rate-limit counters, and the audit trail of who recorded which decision in a matter.
  • Customer Content: uploaded source files (stored unchanged in object storage with their SHA-256), text extracted from them, translations, propositions, annotations, chat history with the in-product assistant, drafts and work product, and the transition log.
  • AI provider keys you add, encrypted at rest; only the last four characters are ever shown back to you.
  • Billing data: your billing email, plan, subscription status, and Stripe customer and subscription identifiers. Payment card or bank details are collected and held by Stripe and never reach our servers.
  • Operational logs: request metadata and errors needed to run and secure the Service. We do not put credentials or Customer Content in logs.

We do not use advertising or analytics trackers in the Service or on this site. Cookies are limited to the session and sign-in security cookies the Service needs to work; the browser also stores your theme and language choices locally.

3. Why we use it (purposes and legal bases)

  • To provide the Service you subscribed to: hosting your matters, running extraction and drafting, enforcing who may see what (performance of a contract; for Customer Content, your instructions).
  • To secure the Service, prevent abuse and keep the audit trail (legitimate interests; legal obligation).
  • To take payment, issue refunds and keep tax records (performance of a contract; legal obligation).
  • To answer support requests and send service notices such as security, billing, renewal and deletion notices (performance of a contract; legitimate interests).

We do not sell personal information, we do not use Customer Content to train AI models, and we do not use it for profiling or marketing.

4. Subprocessors and AI providers

We use the following service providers. Each processes data only to provide its service to us and is bound by its own terms and data-protection commitments. We will update this list before adding a provider that receives Customer Content, and give workspace administrators at least 30 days’ notice so they can object or cancel.

  • Cloudflare, Inc. (United States): hosting and execution of the Service (Workers), the relational database (D1), object storage for source files (R2), job queues, and network delivery. Holds all Customer Content and account data.
  • Stripe, Inc. and its affiliates (United States, Ireland and other locations): payment processing, subscription billing, invoices and refunds. Receives your billing email, name, plan and payment details; it never receives Customer Content.

AI providers are not our subprocessors. We do not provide AI inference to customers. AI features run only on a key you supply (Account → AI keys, for example an OpenRouter or NVIDIA key) or on the AI client you connect over MCP. Excerpts of Customer Content leave Cloudflare for an AI provider only when a person with a key of their own uses an AI feature (asking a question, extracting propositions from a source, translating or drafting). Only the text needed for that request is sent, never the whole matter and never other customers’ data. Without a key, those features are unavailable or fall back to deterministic, non-AI retrieval, and nothing is sent.

Your own key: your key is validated once with a one-token request, stored encrypted with AES-256-GCM under a key held as a Worker secret, never returned to any browser, and used only for your requests. The provider processes the content under your account and your agreement with it, as your own service provider; you are the controller of that relationship and the data sent is governed by that provider’s terms. Delete the key at any time and it is removed. Content you send to an AI client over MCP is governed by that client’s provider in the same way.

5. Where data is processed; international transfers

Algodyne is incorporated in the United States and serves customers worldwide, including in Japan. Data is stored and processed on Cloudflare’s global network, and AI requests you make with your own key are processed by your AI provider wherever it operates. We do not currently offer customer-selectable data residency.

When personal information is transferred out of Japan, the EEA, the United Kingdom or Switzerland, we rely on the transfer mechanism our providers offer for the relevant law (including standard contractual clauses and, for the APPI, the contractual safeguards required for an overseas entrusted party). On request we will tell you which mechanism covers a given provider.

Users in Korea (Personal Information Protection Act, Art. 28-8). Items transferred: the account data, session and security data, Customer Content and operational logs described in section 2, and, to Stripe only, billing data. Destination countries: the United States, and Ireland and other locations where Stripe operates. Recipients: Cloudflare, Inc. (hosting, database, object storage, queues and delivery) and Stripe, Inc. and its affiliates (payment and billing), as named in section 4. Time and method: transferred over TLS when you use the Service, continuously while your account is active. Purpose: to provide, secure and bill for the Service. Retention: as set out in section 7. You may refuse the transfer by not using the Service or by asking us to delete your account; write to us for the contact point for these requests.

6. Security

  • Matter and tenant isolation is enforced in the database and the application, not only in the interface: access is by matter membership, and workspace administrators control membership.
  • Source files are stored unchanged under create-once keys with their SHA-256 hash; a hash mismatch quarantines a file instead of silently repairing it.
  • Data is encrypted in transit (TLS) and encrypted at rest by Cloudflare. AI provider keys are additionally encrypted by us before they are stored.
  • Sign-in uses passkeys, magic links and email one-time codes, with a fresh passkey or email check before sensitive actions; sign-in and sensitive attempts are rate limited; state-changing requests are checked for same-origin use; API tokens are stored only as hashes.
  • Credentials never enter the transition log, and the log records every acceptance, quarantine and issuance with actor and support.
  • Access by Algodyne staff to Customer Content is limited as set out in the Terms, section 7.

If we discover a personal data breach affecting you we will notify workspace administrators without undue delay and in any case within the period the law requires, with what we know and what we are doing. Report suspected vulnerabilities to upgrade@algodyne.com.

7. Retention and deletion

  • Active workspaces: Customer Content is kept while your subscription is active, until you delete it.
  • Lapsed workspaces: when a subscription ends the workspace becomes read-only and its data is kept for 12 months so you can view and export it or resubscribe. At least 30 days before scheduled deletion we email workspace administrators.
  • On request: a workspace administrator may ask us to delete the workspace and all Customer Content at any time. We complete deletion from live systems within 30 days; copies in provider backups and database time-travel windows expire on the provider’s schedule, which is within 30 days, and are not used in the meantime.
  • Account data: kept while the account exists; deleted or anonymised with the workspace or on request, except where we must keep it (see next point).
  • Billing and tax records: kept for the period tax and accounting law requires (generally seven years) and then deleted.
  • Logs and security records: operational logs are kept only for the short retention window of Cloudflare’s logging service; the matter transition log is part of Customer Content and follows the workspace.

8. Your rights

Depending on where you live (for example under the APPI, the GDPR/UK GDPR, Korea’s Personal Information Protection Act, or California law) you may have the right to access, correct, delete, restrict or object to the use of your personal information, to receive a copy in a portable format, to withdraw consent, and to complain to a data-protection authority (in Japan, the Personal Information Protection Commission; in Korea, the Personal Information Protection Commission (PIPC)).

Write to upgrade@algodyne.com. We reply within 30 days. We may need to verify your identity. If your personal information appears inside a customer’s matter, we will refer the request to that customer, who controls the content, and help them respond.

We do not make decisions about people that produce legal or similarly significant effects solely by automated means. AI output in the Service is always reviewed and accepted by a person.

9. Children

The Service is for professionals and is not directed to children under 18.

10. Early-access waitlist

If you join the early-access waitlist on this site, Algodyne is the controller of the information you submit there. It is separate from any workspace or matter content.

  • What we collect: your email address, role, jurisdiction, practice area, matter volume, the free-text answer you write, the language you used, the UTM campaign parameters and referral code or referrer that brought you to the site, and a record of your consent (the time and the version of the consent text you accepted).
  • Why: to run the early-access programme and to contact you about access. We send a confirmation email, access invitations and programme updates; we do not use the information for advertising and we do not sell it.
  • Retention: addresses that are not confirmed through the link in the confirmation email are deleted after 14 days. Confirmed entries are kept until you unsubscribe or the programme ends, and are deleted on request.
  • Unsubscribing: every email carries a one-click unsubscribe link. You can also write to us to have your entry deleted.
  • No case material: the form is not a place for case information. Do not include case details, client names or confidential facts in any field.
  • Processors: email delivery is provided by Cloudflare, as described in section 4.

11. Changes and contact

We will post updates here with a new effective date and email workspace administrators about material changes at least 30 days ahead. Questions, requests and complaints: upgrade@algodyne.com, or Algodyne Corporation, 131 Continental Dr, Suite 305, Newark, DE 19713, United States. These are governed by the Terms of Service, including their governing-law clause.