Odile

Privacy

At HQ we hold your email, the record of your machine, and a boot key with no private half.

The short version

What we hold at HQ

We store your email address, your payment record at Stripe, and the metadata needed to run your machine.

Every field is named by its store and column.
WhatWhyKept
Your email address, and the day it arrivedwaitlist.id waitlist.email waitlist.created_at waitlist.source waitlist.unsubscribedto write to you and identify the accountuntil you ask us to delete it
The signup rate limita short sha256 of the IP address, in memory, ten minutesto stop a bot filling the listnot on disk; gone when the process restarts
The link in your confirmationwaitlist.tokento reopen your confirmation pagewith 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_atto build, bill, suspend and delete the machineafter the machine is destroyed
Your boot public key and the setup-token hashtenants.ssh_public_key tenants.setup_token_hashthe only key; the installer's one usewith the machine record
The claim token, as a hashclaims.id claims.tenant_id claims.token_hash claims.created_at claims.expires_at claims.used_atto open the claim page oncewith 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_atto seed the installer once, on one machinewith 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_atthe funnel and the machine's history; append-onlypermanently
Support grantsgrants.id grants.tenant_id grants.reason grants.created_at grants.expires_at grants.revoked_atwho was let in, why, and until whenwith 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_atthe ledger the provisioner and the health checks readwith 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_atthe machine's history; append-onlypermanently
The heartbeat key, as a public keyheartbeat_keys.slug heartbeat_keys.public_key heartbeat_keys.registered_atto check each heartbeat's signaturewhile the machine exists
The signed heartbeatsheartbeats.id heartbeats.slug heartbeats.at heartbeats.received_at heartbeats.body heartbeats.signaturethat the machine is up; disk, spend, versions and the last backupwhile 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.deliveriesa failure, and who was toldwhile the machine exists
Stripecustomer id, subscription id, subscription statusthe card and the charge stay at Stripewhile the subscription is open
Support and abuse mailthe message, the sender's address, the timeto answer youin 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.

WhatWhyKept
The Hermes home: memory, sessions, prompts, files, skills and cron/home/odile/.hermesthe agent's workon your disk, until you delete it
The Odile sign-inHERMES_DASHBOARD_BASIC_AUTH_USERNAME HERMES_DASHBOARD_BASIC_AUTH_PASSWORD_HASH HERMES_DASHBOARD_BASIC_AUTH_SECRETto open the workspace; a scrypt hash and a session secret, never the passwordon the machine, until you change it
Your machine's NEAR AI key/etc/odile/key.envthe only inference credential; one key per user, read by the agent at startroot-only on your disk
The backup status file/var/lib/odile/backup.jsonthe last successful backup, reported in the heartbeaton your disk
The support log/var/log/odile-support.logevery grant session; a root shell can edit iton your disk
The service journalsystemd journalboot messages and service stateon your disk
The recovery filebackup password and certificate fingerprintto restore, and to pin the certificatekept on your machine, root only; a copy is downloaded to you on your first visit
The LUKS keyslotone keyslot, sealed to the measured bootto unlock the diskon your disk

What leaves the machine

WhatWhereIn clear
The nightly backupan off-site SFTP storage boxno; the repository password is generated on the machine and only you hold it
Your promptsNEAR AI's confidential cloud, inside a hardware enclaveno outside the enclave
The heartbeatodile.fyi, signed by the machinestate, disk, spend, versions, the last backup
Mailour own mail server at mail.odile.fyithe message, never the disk
The diag bundle, when you send ithelp@odile.fyilogs, 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

Retention and deletion

The access model

Logs

Back to the list