Your practice’s data stays your practice’s.

How Dovelumen keeps every practice apart from every other, protects what you store, and leaves you in control of it.

Every practice kept apart. On the server and in the database.

One practice per request: Before any record is read, the server works out which practice is asking from the signed-in session, never from anything the browser sends. Every query is then limited to that practice.
Enforced by the database: Every record belongs to exactly one practice, and the database refuses a link between records of two different practices. Only Dovelumen’s server holds the database’s credentials; there is no public database API.
Clients see their own: A client signs in to the portal of the practice that invited them, and sees only the projects shared with their household, at the access level the practice or household gave them.

In transit: Every page and request is served over HTTPS, with strict transport security.
At rest: The database and stored files are encrypted at rest by the hosting providers, with backups encrypted the same way.
Sign-in: Accounts are run by a dedicated identity provider: Dovelumen never stores a password, and sessions are verified on the server for every request.
Payments: Card and bank details are entered on Stripe’s forms and never reach Dovelumen’s servers.

Ownership: The practice owns its clients, projects, documents and files. Dovelumen processes them to run the service and for nothing else.
Export: Owners can export everything at any time, on any plan, including after cancelling.
Deletion: A closed practice’s data is deleted on request, and from backups as they age out.
Client money: Payments from your clients go to your own Stripe account. Dovelumen never holds them.
An audit trail: Sign-ins, invitations, role changes, signatures and payments are recorded with who did them and when.

We will answer a security questionnaire for any practice considering Dovelumen.