Privacy
At HQ we hold your email, the record of your machine, and a boot key with no private half.
The short version
- No one at Odile can log in to a tenant machine.
- There is no passphrase to type.
- Support access exists only when you grant it, for as long as you grant it.
- We can stop it.
- No cookies, no trackers, no third-party requests.
What we hold at HQ
We store your email address, your payment record at Stripe, and the metadata needed to run your machine.
| What | Why | Kept |
|---|---|---|
Your email address, and the day it arrivedwaitlist.id waitlist.email waitlist.created_at waitlist.source waitlist.unsubscribed | to write to you and identify the account | until you ask us to delete it |
| The signup rate limita short sha256 of the IP address, in memory, ten minutes | to stop a bot filling the list | not on disk; gone when the process restarts |
The link in your confirmationwaitlist.token | to reopen your confirmation page | with the address |
The record of your machine: its name, address, plan, pinned release, expiry and statetenants.id tenants.slug tenants.email tenants.state tenants.server_id tenants.ipv4 tenants.plan tenants.release tenants.expires_at tenants.claimed_at tenants.installed_at tenants.last_heartbeat tenants.created_at | to build, bill, suspend and delete the machine | after the machine is destroyed |
Your boot public key and the setup-token hashtenants.ssh_public_key tenants.setup_token_hash | the only key; the installer's one use | with the machine record |
The claim token, as a hashclaims.id claims.tenant_id claims.token_hash claims.created_at claims.expires_at claims.used_at | to open the claim page once | with the machine record |
The setup token, as a hashseed_tokens.id seed_tokens.tenant_id seed_tokens.token_hash seed_tokens.instance_id seed_tokens.created_at seed_tokens.expires_at seed_tokens.used_at | to seed the installer once, on one machine | with the machine record |
The event log: signup, invite, claim, provision, install, activation, churnevents.id events.tenant_id events.waitlist_id events.kind events.detail events.created_at | the funnel and the machine's history; append-only | permanently |
Support grantsgrants.id grants.tenant_id grants.reason grants.created_at grants.expires_at grants.revoked_at | who was let in, why, and until when | with the machine record |
The control-plane record of the same machinetenant_state.slug tenant_state.state tenant_state.server_id tenant_state.hostname tenant_state.ipv4 tenant_state.plan_id tenant_state.release tenant_state.expires_at tenant_state.initramfs_host_key tenant_state.last_heartbeat tenant_state.detail tenant_state.created_at tenant_state.updated_at | the ledger the provisioner and the health checks read | with the machine record |
The machine's state transitionstenant_state_events.id tenant_state_events.slug tenant_state_events.kind tenant_state_events.from_state tenant_state_events.to_state tenant_state_events.detail tenant_state_events.created_at | the machine's history; append-only | permanently |
The heartbeat key, as a public keyheartbeat_keys.slug heartbeat_keys.public_key heartbeat_keys.registered_at | to check each heartbeat's signature | while the machine exists |
The signed heartbeatsheartbeats.id heartbeats.slug heartbeats.at heartbeats.received_at heartbeats.body heartbeats.signature | that the machine is up; disk, spend, versions and the last backup | while the machine exists |
Health alertshealth_alerts.id health_alerts.slug health_alerts.kind health_alerts.tenant health_alerts.symptom health_alerts.first_command health_alerts.detail health_alerts.first_seen_at health_alerts.last_seen_at health_alerts.resolved_at health_alerts.deliveries | a failure, and who was told | while the machine exists |
| Stripecustomer id, subscription id, subscription status | the card and the charge stay at Stripe | while the subscription is open |
| Support and abuse mailthe message, the sender's address, the time | to answer you | in the help mailbox until it is dealt with |
What lives on your machine
It is a Debian machine and you are root.
The disk is encrypted with LUKS2.
Your Odile sign-in is set on your machine at first visit and hashed there. We never see it.
| What | Why | Kept |
|---|---|---|
| The Hermes home: memory, sessions, prompts, files, skills and cron/home/odile/.hermes | the agent's work | on your disk, until you delete it |
The Odile sign-inHERMES_DASHBOARD_BASIC_AUTH_USERNAME HERMES_DASHBOARD_BASIC_AUTH_PASSWORD_HASH HERMES_DASHBOARD_BASIC_AUTH_SECRET | to open the workspace; a scrypt hash and a session secret, never the password | on the machine, until you change it |
Your machine's NEAR AI key/etc/odile/key.env | the only inference credential; one key per user, read by the agent at start | root-only on your disk |
| The backup status file/var/lib/odile/backup.json | the last successful backup, reported in the heartbeat | on your disk |
| The support log/var/log/odile-support.log | every grant session; a root shell can edit it | on your disk |
| The service journalsystemd journal | boot messages and service state | on your disk |
| The recovery filebackup password and certificate fingerprint | to restore, and to pin the certificate | kept on your machine, root only; a copy is downloaded to you on your first visit |
| The LUKS keyslotone keyslot, sealed to the measured boot | to unlock the disk | on your disk |
What leaves the machine
| What | Where | In clear |
|---|---|---|
| The nightly backup | an off-site SFTP storage box | no; the repository password is generated on the machine and only you hold it |
| Your prompts | NEAR AI's confidential cloud, inside a hardware enclave | no outside the enclave |
| The heartbeat | odile.fyi, signed by the machine | state, disk, spend, versions, the last backup |
| our own mail server at mail.odile.fyi | the message, never the disk | |
| The diag bundle, when you send it | help@odile.fyi | logs, versions, disk usage, service state; no passphrase, key, prompt or file contents |
Your prompts go from your machine to the enclave. They do not pass through Odile's servers.
Memory is encrypted by the CPU.
The machine is in Montreal, Canada.
What we never hold
- There is no passphrase to type.
Retention and deletion
- The waitlist keeps the address, the day it arrived and the link in the confirmation; deleting the address leaves the count.
- The machine record stays after the machine is destroyed; the event log is append-only and holds no credential.
The access model
- No one at Odile can log in to a tenant machine.
- No one at Odile can log in unless you grant it: no standing key, no root password, no disk passphrase.
- The boot key in the command line is a public key with no private half. It is plumbing, not a credential.
- There is no passphrase to type.
- Support access exists only when you grant it, for as long as you grant it.
- A grant is a handover, not a peek.
- We can stop it.
Logs
- Our web server keeps no access log; mail logs keep addresses, times and delivery status for four weeks.
- The signup rate limit keeps a short hash of the IP address in memory for ten minutes; it never touches disk.
- A heartbeat is a signed note from your machine: that it is up, its disk, uptime, spend and versions, the last backup and the last brief. It carries no prompt and no file.
- The grant log is written on the machine; a root shell can edit it.
odile-diagbundles logs, versions, disk usage and service state. No password, no key, no prompt history, no file contents.