Axiom OrderFlow / Privacy

Privacy Policy

A plain-language account of what data Axiom OrderFlow handles, who processes it, and how the public demos work. We would rather be clear than comprehensive-sounding.

Last updated: August 2026Axiom NeurophysiologySecurity overviewTerms

This is a product prototype policy. It describes what the software does today, and it is pending counsel review before any customer handling protected health information.

The short version

Four questions, answered before the document starts.

What data do you hold?

In a workspace

  • Order documents you upload and the fields extracted from them.
  • Account and workspace records: names, email addresses, roles, settings.
  • An audit trail of actions taken in the app.

What do you do with it?

Use

  • Run the service for your organization, as a processor acting on your behalf.
  • We do not sell customer data.
  • We do not use the contents of your order documents to train AI models.

Who else touches it?

Subprocessors

  • A short, named list of vendors, each engaged under its own terms.
  • Four of the six are optional and depend on configuration.
  • The full list is below, with what each one does.

What about the demos?

Demos

  • Demo environments use synthetic data only.
  • The live demo opens a temporary read-only account, swept nightly.
  • The try-it extraction runs in memory and stores nothing.

Who we are

Axiom OrderFlow is a healthcare operations product from Axiom Neurophysiology (referred to here as Axiom, or we). It helps neurodiagnostics departments intake EEG orders, review extracted fields, and manage the downstream workflow. This policy explains what data we handle and how.

Data in a customer workspace

When your organization uses Axiom OrderFlow, we process the order documents you upload and the data extracted from them, plus your account and workspace records (names, email addresses, roles, workspace settings) and an audit trail of actions taken in the app.

This data belongs to your organization. We act as a processor of it on your behalf, under your agreement with us.

Access is scoped to your organization and enforced at the database with row-level security, and that scoping is continuously tested against supported access paths. We do not sell customer data, and we do not use the contents of your order documents to train AI models.

Cookies and analytics

We use strictly necessary cookies to keep you signed in and to operate the app. We do not run third-party advertising trackers.

Who processes data on our behalf

We rely on a small set of vendors to run the service. Each is engaged under its own terms.

SubprocessorWhat it doesWhen it applies
SupabaseManaged Postgres database, authentication, and file storage.Always
VercelApplication hosting and serverless compute.Always
AnthropicAI extraction of fields from uploaded order documents. A human reviews and approves every result.Optional, by configuration
ResendTransactional and notification email.Optional, when enabled
SentryError monitoring, configured to strip request data and user context before an event is sent.Optional, when enabled
UpstashRate-limit counters for the public demo endpoints.Optional, when enabled

Before a workspace is authorized for protected health information, the applicable vendor agreements, including Business Associate Agreements where required, are completed alongside a security review. We describe that as the sequence we follow, not as agreements already in place, and we do not claim certifications we do not hold.

Patient information

The platform is restricted to de-identified or synthetic data. Demo workspaces are for synthetic data only, and that restriction is contractual and operational rather than technical.

A database constraint pins the patient-identifying mode off, but it governs the mode flag, not the contents of a field: this release does not technically prevent someone typing patient information into an order, so please do not enter or upload real PHI.

Please do not upload real PHI

Do not enter or upload real Protected Health Information into a workspace, a demo, or a demo request until that workspace has been authorized for it.

  • Unlocking that mode takes a deliberate, reviewed database change rather than a setting.
  • Authorization follows a security review and the applicable vendor agreements.
  • We describe the controls we have implemented, and we do not claim certifications we do not hold.

The public demos

Two of them: a live read-only demo, and a try it with your own order form extraction demo. Both are labeled for synthetic or blank forms only.

Live demo

  • It signs you into a temporary, disposable viewer account on a synthetic showcase workspace.
  • The account is read only, and it is swept automatically each night.
  • The workspace it opens is synthetic and separate from any customer workspace.

Try it with your own form

  • The file you provide is processed entirely in memory to show a result.
  • It stores no upload record, no file, and no extraction. The file exists only for that single request.
  • We keep basic request metadata, such as an IP-derived rate-limit counter, to prevent abuse.
axiomorderflow.com/spreadsheet
The Axiom OrderFlow Intake Tracker as it appears in the public demo workspace
The workspace the public demo opens. Synthetic demonstration data.

Data retention

Within a customer workspace, stored order PDFs follow the retention window your administrator configures. Settled orders are swept nightly, and each purge is recorded in the audit trail. The extracted data, tracker rows, and audit history are retained per your agreement.

Disposable demo accounts are deleted automatically. On termination, we return or delete customer data as described in your agreement.

Error monitoring

Error monitoring is optional and off unless configured. When it is enabled, it is set to strip request data and user context before an event is transmitted, so a diagnostic report carries the fault and not the record that triggered it.

Your choices and contact

If you are a member of a customer workspace, your workspace administrator manages your access and can offboard your account. For requests about data your organization controls, contact your administrator first.

For anything else, including questions about this policy, email info@axiomeeg.com.

Changes to this policy

We may update this policy as the product changes. The date at the top of this page reflects the current version.

Reviewing this for a hospital?

The Security overview covers access controls, audit, and the implementation sequence in more detail. Questions go to info@axiomeeg.com.

Bring your privacy reviewers early.

An operations review covers the workflow. Your IT, privacy, and security reviewers are welcome in the same conversation.

Or email info@axiomeeg.com

Privacy Policy | Axiom OrderFlow