SECURITY
How the books are kept apart.
This is a description of what the product does today. It is not a compliance attestation.
Transport and storage
Pages are served over HTTPS. Books are stored in hosted Postgres. Disk encryption at rest is the database host's, not a second passphrase Plutaxa puts on each journal line.
One company cannot read another
Row level security uses the signed-in person and the organization. Direct table writes from the signed-in role are denied. Posting goes through checked database functions.
Revisions and the audit trail
A posted entry is not overwritten. An edit reverses the old journal entry and posts the new one, and undo walks that chain. A closed period changes only with a reason from an owner or admin. Activity is written to an audit log. Platform admin, for the operator, is separate from company roles and writes its own audit log.
Documents and tokens
Document download links are signed, expire in five minutes, and still require the signed-in company. Shopify fixture tokens are encrypted in the app with AES-GCM before they are saved. The signed-in role cannot read that ciphertext.
The assistant
Plutaxa does not train models on customer books. A question and the records needed to answer it are sent to the configured model provider, OpenAI or Workers AI, to draft a reply. The draft does not post. You approve anything that would change the books.
What this page does not claim
Plutaxa does not have a SOC 2 report, an ISO certificate, or a published penetration test. Those words are absent here on purpose.