Security & your data

Where your data lives, and who can reach it.

Written for whoever has to sign this off: an IT person, a doctor, an auditor, a partner abroad. It says what is true, including the parts that are inconvenient for us.

The short version

Most business software keeps your customers, your books and your patients on the vendor's servers, and asks you to trust the vendor. Ours mostly does not: the software you buy runs on your own computer, and the records stay there. There is no shared pool your data sits in, because for those products there is no pool.

That is an architecture, not a promise, which is why the rest of this page can be specific rather than reassuring.

Where your data actually lives

This depends on which product you use, and we would rather draw the line clearly than let "your data never leaves you" cover things it does not.

Software you install

On your computer

The eleven apps you download, and the ones our engineers install for you: MediFlow, Agency OS, Meridian, Ascend.

  • Records are written to a file on your machine or your own server.
  • They keep working with the internet off.
  • We cannot read them. Not "we choose not to". There is no copy to read.
  • Licence checks verify offline against a signed key, so even activation does not need us.

Trials and cloud sync

On our server

Anything you run in the browser here: a free trial at /try, an app opened at /run, plus Cloud sync if you switch it on.

  • What you type into a browser trial is stored on our server so it is there next time.
  • Cloud sync exists precisely to hold a copy, so two computers agree.
  • This is the trade you make for convenience, and it is opt-in on every paid product.
  • Everything exports, so moving off us is always possible.

What we hold about you

Your account here is deliberately thin. It exists to know who owns which licence:

We storeWhy
NameTo address you like a person.
Email or phoneOne of the two, to reach you and to sign you in. Not both required.
Business nameOptional. For the invoice.
PasswordHashed with scrypt and a random per-account salt, compared in constant time. Never stored as text, and not recoverable by us.
Your licences and invoicesWhat you bought and when it renews.

No card details, ever. Payments are handled by the payment provider; card numbers do not pass through and are not stored here.

How the AI workers are governed

An agent that can act on your business is only safe if something bounds it. Every action one takes passes a single gate, and the rules are the same for all of them:

ClassWhat happens
ReversibleRuns. Answering a message, drafting a reply, logging a call.
IrreversibleHeld until a human types EXECUTE, or until you have signed a mandate scoping exactly what it may do unattended, scoped to a named action, a daily cap and an expiry date.
Affects a personA human decides, every time. No mandate can cover it, and there is no setting that turns this off.

Every action is written to a hash-chained record: each entry is hashed together with the one before it, so an edited history stops verifying and you can see where. That makes tampering evident. It does not make it impossible, and we will not describe it as tamper-proof.

What our billing can see

We bill for the work the agents do, which normally means a vendor has to watch the work. Ours does not. What reaches us is a signed count of which agent did which action how many times, and never what the action was about.

This is enforced rather than promised: our server rejects a usage report outright if it contains anything phone-, email- or Aadhaar-shaped, before it is stored. A report carrying a customer's number is refused, not cleaned up afterwards.

This website

ControlState
TransportHTTPS only, with HSTS. Certificates renew automatically.
Browser hardeningFraming denied, MIME sniffing off, referrers not sent, and camera, microphone and location denied to the page.
SessionsRandom 24-byte tokens, invalidated on sign-out.
AbuseSign-in and sign-up throttled per address; the wider API is rate-limited.
Licence signingEd25519. The private key exists only on the server; your copy of an app carries the public half and can verify without contacting anyone.

What we do not claim

A security page that only lists strengths is not worth reading. These are the honest limits, and you should weigh them:

  • We hold no certifications. No ISO 27001, no SOC 2. We are a small company and we have not been audited by anyone. If your procurement requires a certificate, we do not have one.
  • No third-party penetration test has been carried out. The hardening described here is our own work, reviewed by us.
  • Software on your computer is as safe as that computer. If the machine is shared, unpatched or has no disk encryption, nothing we do compensates for it. Local-first moves the responsibility to you as well as the control.
  • Browser location can be spoofed. Where our software records where someone was, treat it as a record and a deterrent, never as proof.
  • Handwriting recognition is unreliable. Where an app reads a prescription or a note, a person confirms it. We say so in the app rather than only here.

Two rules that do not move

Your records are never held over money. If a licence lapses, the AI workers stop. Reading and writing your own books does not. Non-payment is a reason to stop our work, never to lock you out of yours.

Everything exports. Leaving is a supported action, not a support ticket. Software you have bought outright keeps running whether or not you are still paying us.

Questions your auditor needs answered?

Send them. We will answer specifically, in writing, including where the answer is "we do not do that yet".

Ask us about security Terms, privacy & refunds

This page describes how the software is built. It is not a contract. The terms and privacy policy are. Where the two differ, those govern.