What we collect
- Operator email + name. So we can reply to you. That's it.
- Audit logs. Every action you take in the operator console lands in audit. This is the product, not a side-channel.
- Agent telemetry. Heartbeat, agent version, OS family. Used to know which agents are online and which need updates.
- No analytics tracking pixels. No Google Analytics, no Segment, no third-party tags by default.
What we don't collect
- Your server contents. The agent runs on your machine; we see metadata about the actions it takes, not the files it touches.
- Your customers' data. CMS content lives in your git repo. The operator console DB does not store article bodies, page metadata, or media.
- Your databases. Same. Backups are encrypted to a public key whose private half you hold; we cannot read them.
Where it lives
The operator console database is hosted at jurisdiction TBD via provider TBD. We will fill these in publicly before pilot opens to general availability — they're left as TBD rather than invented.
Who we share it with
A short list. Adding a vendor here is a deliberate decision and the change lands in this page's "Last updated" date.
- Billing provider:
TBD— invoices, payment processing. - Email provider:
TBD— transactional + reply-to-Adam. - That's the entire list.
Data export and delete
Email hello@ordic.ai with the operator email on the account. We'll reply with a JSON export of your audit log + account metadata within seven days. To delete, ask for delete; we'll confirm by reply, then purge. Audit retention required by AUP enforcement is the only exception, and we'll tell you if that applies.
Cookies
Session cookies only, set by the operator console at /login. No third-party trackers. The public site (ordic.ai) sets none.
Changes to this policy
We post a revised "Last updated" date and email all account holders before any change that materially changes what we collect or who we share it with. Tightening (collecting less) doesn't trigger a notice; loosening always does.