Privacy Policy

1. The short version

Your database stays on your server — the DBMind cloud never receives credentials or a database connection. What it does receive per request is the question being asked, the schema metadata of the tables you approved (table and column names, foreign keys — never the contents of excluded tables or denied columns), and the capped, sanitised result rows of the guarded query your own server executed, so the model can phrase the answer.

By default those result rows are additionally protected with field-level encryption: private text values such as names, emails and phone numbers are replaced with AES-256-GCM ciphertext tokens before they leave your server. The language model copies the tokens verbatim, your package decrypts them locally before displaying the answer, and the encryption key never leaves your server — neither DBMind nor the model provider can read those values.

2. What we store

For every gateway request we store metering metadata: token counts, latency, status, the model used, and SHA-256 hashes of the question and payload. Raw schema metadata and result rows are never persisted.

When the conversation log is enabled, we additionally store the question text and the answer the model returned so account owners can audit them from the dashboard. This log never includes the schema or the result rows, and it can be disabled at the platform level.

3. Account data

We store your name, email address and hashed password, your projects, and your billing records (plan, subscription status, payment transaction references from Qi Card). We do not store card numbers — payment details are handled by the payment provider.

4. API keys

API keys are shown once at creation and stored only as SHA-256 hashes. We record when a key was last used so you can spot stale or abused keys.

5. Cookies

The dashboard uses a session cookie and a CSRF token — both strictly necessary. The marketing site sets no tracking cookies.

6. Data retention & deletion

Usage metadata is retained for billing and abuse prevention. Deleting a project removes its keys and logs; deleting your account removes everything tied to it. Email support@dbmind.ai for a full export or erasure request.

7. Self-hosted mode

When you run the package against your own Ollama server, no data reaches DBMind at all — the SQL is written, guarded, executed and answered on your hardware. This policy then only covers your dashboard account, if you keep one.

8. Changes

We will announce material changes to this policy by email and on this page before they take effect.