How Dalgone handles your data

The browser extension holds no Odoo credentials and makes no direct Odoo calls. It only talks to the Dalgone API. The API attaches your credentials server-side and proxies every Odoo request on your behalf. Nothing sensitive lives in the extension bundle.

Your Odoo credential is encrypted at rest with AES-256-GCM envelope encryption. It is decrypted only transiently, in memory, to make the exact request you triggered; it is never returned to the browser or extension after you save it, and it is never logged.

The credential authenticates as your Odoo user, so Dalgone can do no more in Odoo than you can. Want to tighten that further? Connect a purpose-scoped Odoo user with only the rights you want Dalgone to have.

And you can revoke our access at any time, without asking us: delete the API key in your Odoo settings and our access ends instantly. The credential lives in your Odoo; you hold the off switch.

Your data is isolated from every other customer at three layers:

• A signed JWT tenant check on every request.
• Postgres row-level security on the underlying data.
• The server resolves your Odoo target from your own account record — never from anything the browser sends.

Emails you save are scrubbed, then encrypted at rest (AES-256-GCM), isolated to your tenant. Before anything is stored, a server-side scrubber removes health-like numbers, SIN/SSN patterns, and payment-card numbers. We decrypt saved emails only to show them back to you or to perform an action you invoke. We don’t sell them and we don’t train AI on them. Archived emails are kept for 90 days by default, then auto-deleted — we email you 3 days beforehand, and you can change or turn off the window, or delete anything, in Settings.

To be precise about scope: the body and subject of a saved email are encrypted at rest; the sender and date are kept in the clear so we can organize your archive; attachments stay isolated to your tenant and are deletable.

With your explicit consent, Dalgone requests exactly two Gmail scopes:

• gmail.readonly— to read the message you’re viewing and its attachments.
• gmail.send— to send the reply or forward you compose.

Google tokens are never stored on our servers; the extension holds them only in browser session storage, cleared when you close Chrome.

• It takes no admin rights on your Odoo.
• It installs no server module or add-on into your Odoo.
• It has no more access than the Odoo user you connect.
• We don’t sell your data.
• We don’t train AI models on it.

Is this “your data never leaves your machine”? No — and we won’t tell you it is. Ours is a server-side design, encrypted and access-controlled, because that’s what keeps your Odoo credentials out of the browser entirely — and what lets your whole team share one governed connection to Odoo instead of scattering keys across laptops.

Dalgone runs on Supabase (Postgres), a Fastify API on Railway, and a React site on Vercel. Odoo access is version-aware — v16–18 use the web-RPC transport, v19+ use the /json/2/ REST API.

Ask us the hard ones — where a given field lives, what’s encrypted, what we can and can’t see. We’d rather answer plainly than have you guess. Email security@dalgone.com.