Sub-processors

A sub-processor is a company we use to deliver CaseOrbit that, in doing so, handles data belonging to your firm or your clients. Our Privacy Policy commits to naming them, and to giving you at least thirty days' notice before we add or replace one. This is that list.

We have written what each one actually receives rather than a category. If a vendor sees the text of a matter, it says so.

Used for every firm

These receive data as part of normal operation, without any per-firm setting.

OpenRouter

Why: Routes requests to the AI models behind legal research, case prediction and case chat.

What it receives: The text of the question asked, plus the case context assembled to answer it — which can include matter facts and history. This is the most sensitive disclosure on this page and is listed first for that reason.

Stripe

Why: Takes card payments and issues refunds.

What it receives: Payment card details, the amount, and the invoice and client reference. Card numbers go to Stripe directly and are never stored by CaseOrbit.

Mailgun

Why: Sends transactional and notification email.

What it receives: Recipient email addresses and the content of the message sent — which for a deadline alert names the matter.

ClickSend

Why: Sends SMS notifications.

What it receives: Recipient phone numbers and the text of the message.

Google (Firebase Cloud Messaging)

Why: Delivers push notifications to the mobile app.

What it receives: The device token of each registered device, and the title and body of the notification sent to it — which for a deadline alert names the matter.

Microsoft Azure Blob Storage

Why: Holds the off-site copy of backups, so a failure of this host cannot lose data.

What it receives: Database backups and the stored document files, copied nightly. This is a copy of everything in the product, which is the point of it. Note that documents themselves are served from a disk on our own host — Azure sees them only as part of a backup.

Used only where enabled

These are reached only where a firm has connected them, a user has chosen them, or a visitor has consented.

Intuit (QuickBooks Online)

Why: Syncs invoices and customers into a firm's own accounting, where the firm has connected it.

What it receives: Invoice amounts, client names and billing addresses for the connecting firm only. (Opt-in per firm — currently sandbox)

Google, Microsoft, Facebook, X

Why: Lets a user sign in with an existing account, where an administrator has linked one.

What it receives: The sign-in identity only. No case data is sent, and no account is ever created from one of these — an external identity signs a person in only where it already matches an active CaseOrbit user. (Opt-in per user)

Google Analytics 4

Why: Measures use of the public marketing site.

What it receives: Marketing-site page views. It does not load at all until a visitor explicitly consents, and it is never present on a signed-in page. (Consent only)

Ahrefs Analytics

Why: Measures marketing-site traffic without cookies.

What it receives: Aggregate marketing-site page views. No cookies and no identifiers. (Marketing site only)

Disclosed in advance, not yet enabled

We list these before turning them on, so that a firm signing up knows about them from the start.

Mapbox

Why: Will turn a client's address into coordinates, so matters can be shown on a map and sorted by distance.

What it would receive: Client postal addresses, at the point one is geocoded. (Not yet enabled)

What runs on our own servers

Worth stating, because it is the part people assume goes to a vendor and does not. Document storage is a disk on our own host, not a third-party object store. Case-retrieval search runs an embedding model on that same host, so the text of a matter is turned into vectors locally and that text does not leave our infrastructure for indexing. Database backups are written to a separate physical disk on the same host before the off-site copy named above is taken.

Changes to this list

If we add or replace a sub-processor that handles your data, we will tell you at least thirty days beforehand. If you object on reasonable data-protection grounds within that period, we will work with you in good faith to find an alternative; if none is available, you may terminate the affected part of the service without penalty and receive a pro-rata refund of fees paid in advance for it.

Questions about anything on this page: privacy@caseorbit.app.