Draft pending legal review. This page describes how Deepsight protects your data. Items marked (at launch) come with our hosted service and are not yet live. Text in [square brackets] is still to be confirmed.
Read-only by design
Deepsight asks your accounting system (Zoho Books, Xero or SAP Business One) only for read access. It never posts, changes or deletes anything in your books. For SAP Business One we ask for a dedicated read-only user, not a superuser, and Deepsight refuses to send anything other than read requests.
You can withdraw access at any time in your accounting system or in Deepsight.
Signing in
- Two-step sign-in is mandatory for every user. A password alone never opens a company’s figures. The second step is an authenticator app or a passkey (Face ID, fingerprint, Windows Hello or a hardware key). We do not use text messages, which can be intercepted.
- Passwords must be at least 12 characters, cannot be one of the commonest passwords, and are stored only as a one-way scrypt hash.
- Recovery codes are shown once and stored only as hashes.
- Five wrong passwords or codes pause sign-in for 15 minutes, and the person is emailed.
- Sessions end after 30 minutes without activity, and after 12 hours in all. You can see where you are signed in and sign out other devices on your My security page.
- Sensitive actions ask for a fresh code: approving or unlocking a report, adding a connection, changing AI settings and managing people.
- After two-step sign-in is reset, approvals and other sensitive actions are paused for 24 hours, and the person is told, so a stolen reset cannot be used straight away.
Keeping each customer’s data separate
- Every customer’s data is separated inside the database with PostgreSQL row-level security, so a query can only ever see the rows of the customer it is working for. Tests check this on every change.
- Within a customer, each person sees only the companies an administrator allows. Pages, exports and Ask Deepsight check that access on every request.
Protecting your data
- Connection credentials (the tokens that let Deepsight read your accounting system) are encrypted with AES-256-GCM. The key is kept apart from the data, in a key vault (at launch), and unencrypted credentials are refused.
- Two-step sign-in secrets are encrypted the same way.
- In transit: all connections to Deepsight and to accounting systems use TLS 1.2 or later (at launch).
- At rest: the database and file storage are encrypted, hosted on Microsoft Azure in South Africa North (Johannesburg) (at launch).
- Evidence (the accounting system’s original responses and uploaded statements) is stored by its fingerprint, so it cannot be changed without detection.
- The web app sends strict browser security headers (a Content-Security-Policy that forbids inline scripts, no framing by other sites), refuses cross-site form posts, and keeps its sign-in cookie out of reach of page scripts.
AI features
- Ask Deepsight, reading scanned statements and suggested matches are off for every company until an administrator switches them on. Each change is recorded with who made it, when and the wording they saw.
- Only what a question needs is sent to our AI provider, Anthropic: small result tables Deepsight has calculated, never whole ledgers. Customer and supplier names are replaced by labels such as “Customer 1”.
- Your data is not used to train AI models.
- The AI never calculates figures. Deepsight checks every figure in an answer against its own stored results before showing it.
The Privacy notice sets out exactly what is sent.
Our staff
- Our staff use a separate staff console with its own sign-in, mandatory authenticator app and shorter sessions. Every staff action asks for a fresh code.
- The staff console cannot read your figures. Its database login has no rights on customer tables; it sees account status, people and read results as counts and dates only.
- Support access needs your approval. If a staff member needs to see your figures, they ask; an administrator approves for a set time (72 hours by default, at most 7 days) and can end it at any time. Every page they open is recorded with the reason.
- The staff audit log cannot be edited or deleted, by anyone, including our own administrators.
- We build and test Deepsight with demonstration and synthetic data, not customer data.
Audit trail
- Approvals, locks, AI setting changes and sign-in security events are recorded with the person, time and device. You can see your own recent security activity on My security.
- [An app-wide, append-only audit log kept for at least 12 months is being added before launch.]
Testing and certifications
- An independent security test of the hosted service is planned before launch [mid to late January 2027], and will be repeated [yearly].
- Deepsight follows the Xero security standard for API consumers, which every app connecting to Xero must meet.
- Deepsight does not currently hold ISO 27001 or SOC 2 certification. We will say so here if that changes.
If something goes wrong
We have a process for handling security incidents. If a breach affects your data, we will tell you without undue delay, and in any case within [72] hours of becoming aware, and notify the Data Protection Commission of Ghana and other regulators where the law requires.
Reporting a security issue
If you think you have found a security issue in Deepsight, please email [[email protected]] with the details. Please do not access other customers’ data or disrupt the service while testing. We will acknowledge your report within [3 working days] and keep you updated.