Trust

One account.
Each client kept apart.

One subscription, and no client ever sees another. How that is done, and what happens when you want it all back.

  • Client A
  • Client B
  • Client C
  • You, the owner reaches all three
  • An account manager reaches the two they are on
  • A freelance writer reaches one
One bill, one login, three walled workspaces.
How it holds

Six things worth knowing.

Each is a mechanism you could ask us to demonstrate. Where one is half-built it says so.

  • A role per client, not per account

    Owner, admin, account manager, member, viewer. An account manager runs the workspaces you name and no others. The browser holds no credential that can write anything: it can read six tables and write nothing.

  • Keys and tokens, encrypted. Card numbers, never held

    Provider keys and connected-account tokens, AES-256-GCM at rest, decrypted only in memory. Card details never reach us — Polar is Merchant of Record and takes the payment, the tax and the VAT.

  • A trail nobody can edit

    24 audited action types write a row each — sign-ins, role and key changes, deletions — and a trigger refuses every rewrite. Honestly: there is no screen for it yet. Ask, and we pull yours.

  • Export whenever. Leave whenever

    One click, a ZIP of every table, a manifest of every file with its own download link. Deleting is a request and 72 hours to change your mind, then an hourly job removes the account, its files and every sign-in on it.

  • Real faces, with consent on the record

    You upload a person’s reference photos against a record carrying who consented and when. No stock, and no face that did not agree to be there.

  • Watched, and scrubbed on the way out

    14 alert rules page a human — circuit-breaker trips, 5xx spikes, row-level-security violations. Errors reach telemetry scrubbed first: emails masked, secrets blanked outright.

Plainly

What is not finished.

Said plainly
The audit trail has no screen — the rows exist and cannot be edited, but you must ask us to read them. Row-level security fences your ACCOUNT from every other account; the wall between two of your own clients is the server’s check, so a bug of ours could cross it where an outsider could not. No uptime theatre and no service-level agreement at any plan. Input validation covers most of the API, not all of it. We measure which screens you open inside the product — not what you write, type or generate, and never a recording of your screen — so we can find what is broken; it is on by default and one switch in Settings turns it off.
Questions

What a client’s
lawyer asks.

Who can see a client’s work?
Only the people you put in that client’s workspace, and the server checks it on every request.
What is encrypted?
Your AI provider keys and your connected-account tokens, AES-256-GCM, decrypted only in memory. Everything else sits on the platform’s own encrypted storage — a different claim, and we will not dress it up as the same one.
Do you hold card numbers?
No — not once, not ever. Polar takes the payment as Merchant of Record.
What do you do with faces?
They make that client’s pictures and nothing else. Never training, never another account.
Can I get everything back?
Yes — a ZIP of every table plus a manifest of every file, each with its own download link. Leaving is a request and 72 hours to change your mind; an hourly job then deletes the account.