Security, and what Divvent can and can't see

Your application holds your business's records: your customers, your jobs, your invoices. This article explains where those records live, who can reach them, and what Divvent itself sees while it runs your application for you.

The short version: Divvent does not routinely see your application's records. We work from your description of the business, from counts and health numbers, and from the history of what has been changed. Even when our team needs support access, that access does not include reading your records.

Where your application runs

Every company on Divvent has its own separate hosting account, which Divvent sets up, holds and pays for on your behalf. Your application runs there, with its own database and its own file storage. It does not share a database with any other company's application, and one company's application cannot reach another's.

Your applications and their data run in the UK/EU region. Where your data is stored is chosen once, when your company is created, and it covers every database, every file store, every nightly backup and every short-lived copy made while a platform update is checked. It is not a setting you can change later, because the data already exists where it was put. If you ever need it moved, ask us and we will agree a time with you, since the application is unavailable while it moves.

What Divvent can see

To build and run your application, our side holds:

• Your description of the business and the application made from it: its records, fields, pages, flows and permissions. This is what the AI and our team work from.
• Your changes: what you asked for, what was proposed and who approved it.
• Counts and sizes: how many requests your application served, how big its database is, how many records a backup holds.
• Health numbers: how many requests failed or were refused, which kind of error it was, and how slow the slowest screens were. See Health and Activity.
• The people on your account: their email addresses and roles.

A count is a fact about your data, not your data. "1,204 customers" is a number we can see; the names of those customers are not.

What Divvent does not see

• Your application's records. Nothing on our side opens your application's database to read a record, or even to count one. The numbers we hold are ones your application sends us, and they are limited to counts, error kinds and timings.
• Records in health reports. When your application reports a problem, the report has room for an error's kind, a count and a time, and nowhere to put a value somebody typed.
• Records in what the AI reads. When you ask for a change, the AI is sent your request and the shape of your application, never its records. The AI and your data explains this in full.

When our team needs support access

Sometimes we need to look more closely at how your application is running, for example to find out why a release is failing. That is support access, and it has rules that cannot be skipped:

1. A person on our team asks for it, for one application, with a written reason that you will be able to read.
2. They say exactly what they need to look at, chosen from a short list: health, how the application is running, releases, database updates and the resources it uses. None of these reads your records.
3. A second person on our team must approve it. Nobody can approve their own request.
4. Both people must have signed in to our own tools within the last ten minutes.
5. It ends by itself: after four hours unless set otherwise, and never more than eight.
6. You are told. When the access is approved, every owner of your account is emailed with who has it, who approved it, why, what they can see and until when.

Every step is recorded, and it appears in your application's Activity tab: the request, the approval and each reading made under it, with Divvent as who did it.

Your sign-in

Everybody who signs in to Divvent needs a second factor as well as a password: a passkey, or an authenticator app on their phone. Until someone has set one up, the only thing they can do is set one up. You also get recovery codes, in case you lose your passkey or phone. Signing in, passkeys and recovery codes explains how.

Your own application's users sign in to your application, not to Divvent. See Your users' sign-in.

Encryption and keys

• Your data is encrypted in transit and at rest by the hosting we use.
• The keys and passwords you give us for connected services, such as a payment or messaging account, are stored sealed. The parts of Divvent that face the web cannot open them.
• Secrets are never written to logs, and nothing on screen can show one back to you once it is saved.

A record of everything

Every change to your application is recorded: who asked for it, who approved it, when it was released, and any support access. You can read this history in Settings, on the Activity tab. See Health and Activity.

Report a security problem

If you think you have found a security problem in Divvent, email security@divvent.co.uk. Our disclosure policy is at divvent.co.uk/security. For anything else, see Status and incidents.

Our terms, privacy policy and data processing agreement set out these promises formally.