Privacy Policy
Last updated 14 November 2026
1. Who is responsible
For the account data this product holds about you, OroDb is the controller. For the contents of the databases a customer connects, OroDb acts as a processor on that customer's instructions and the customer is the controller; separate processor terms are required for that and are not yet in place. OroDb is operated by an individual trading as OroDb. The registered legal name and postal address are TO BE SUPPLIED and will be published here before the product is sold or listed on a marketplace.
Contact for any privacy question, including access and deletion requests: abhishekjain_aj@outlook.com.
2. This website collects nothing
orodb.com is a set of static files. There is no server-side code, no database, no contact form, no analytics, no advertising and no third-party scripts, fonts or embeds. Every font, stylesheet, script and image is served from orodb.com itself.
The site is hosted on GitHub Pages, so GitHub receives your IP address and request headers in order to serve the page, as any web host does. That is outside our control and is covered by GitHub's own privacy statement.
3. The interactive demo
The demo at orodb.com/demo.html runs entirely in your browser on invented data. It never connects to a database, a server or an API, and nothing you do in it is recorded or transmitted.
4. Browser storage
This site stores one item, orodb-theme, in your browser's local storage, to remember whether you chose light or dark. It is not a cookie, it is never sent to us, and clearing your browser data removes it. See the cookie policy.
5. The OroDb application
The application is a separate product behind a sign-in, and it does process personal data. It is not part of this website. It holds:
- account data: email address, display name, role, and the workspace you belong to;
- sign-in records in an audit log, including the IP address a sign-in came from and an approximate city and country derived from it;
- connection details for the database servers you choose to monitor, with credentials stored encrypted;
- performance telemetry read from those servers, which includes captured SQL query text, which can contain personal data if your own application embeds it in queries. Both the captured statement text and the execution plan XML are encrypted at rest, since a plan embeds the same text and its parameter values. Plans captured before 14 November 2026 are stored as plain XML and are not rewritten;
- an audit trail of actions taken in the product.
Recipients: Microsoft Azure for hosting and the database, Microsoft Entra ID if you sign in with a Microsoft account, and the email provider configured for your workspace, which is either Resend or an SMTP server you supply. Sign-in codes, invitations, alerts and scheduled reports go out through that provider.
The application publishes its own policy inside the product at /legal/privacy.
6. How long data is kept
Snapshots and captured query text are removed on the retention schedule each workspace configures. Audit records are kept for the workspace's configured period. Account records are kept while the account exists. A defined maximum retention period for each category is TO BE SUPPLIED.
7. Your rights
You can ask for a copy of your data, ask for it to be corrected, or ask for it to be deleted, by writing to abhishekjain_aj@outlook.com. There is not yet a self-service account deletion control in the product, so deletion is handled on request.
Which statutory rights apply depends on where you live. The jurisdictions this product is offered in are TO BE SUPPLIED, and this section will name the applicable laws once that is settled.
8. Security
Credentials for monitored servers are encrypted before storage. The application is served over HTTPS only, sends a Content Security Policy that does not permit inline scripts, and keeps its session cookie HTTP-only. No security measure is perfect and we do not claim otherwise.
9. Changes
If this policy changes, the date at the top changes with it. There is no automated mechanism for notifying account holders of a change, so today that would be done by hand.
10. Which document applies
This page covers orodb.com. The application publishes its own, more detailed policy at
/legal/privacy, which governs the product. Where the two differ on the product, the
application's policy is the operative one. Both are drafts pending legal review, and both use the
same contact address; the older privacy@orodb.com address in the application's policy
is being consolidated to the address above.