Privacy Policy

Elpis processes the information required for account access, payment controls, verification and billing:

• Account — your name, email address, a salted hash of your password (never the password), and your role.
• Wallet — the Ethereum address you sign in with or link, if you use one.
• Treasury data — the accounts, policies, obligations, counterparties and payment actions you create, and the append-only ledger of what happened.
• Security — an encrypted second-factor secret and hashed recovery codes, if you enable 2FA; hashed API keys, if you create them; and your IP address, used only to rate-limit abuse.
• Usage — a count of API calls per organisation per month, for the metered pricing described in the pricing model.

Payments, escrows and their transaction hashes are recorded on a public blockchain. That data is public by design and outside anyone’s control, including ours. Treat wallet addresses and transactions as public information.

Data is stored in Cloudflare (Workers and D1) as our infrastructure provider. If the operator configures a transactional email provider, your email address is shared with it to deliver account mail. If the operator configures a language-model provider, only the text of written policy is sent to it — never keys, balances, or transaction data. We do not sell your data, and we do not use it for advertising.

We set one httpOnly session cookie, and a short-lived cookie during two-factor sign-in. Your light/dark theme choice is kept in your browser’s local storage. There are no advertising or cross-site tracking cookies.

The ledger is append-only and is retained so that the record of what happened remains intact. Sessions, rate-limit buckets, expired sign-in nonces, and expired email-verification tokens are deleted automatically. Account closure removes or anonymizes data where supported, subject to operational, legal, security, billing and audit-record retention requirements. Public blockchain transactions cannot be erased through account closure.

You may access, export, correct, or delete your data, and object to its processing, subject to the retention of the ledger noted above. To exercise these, contact us. You can request account closure through the supported workflow or contact us.

Passwords are stored only as salted PBKDF2 hashes and compared in constant time. Sessions are HMAC-signed httpOnly cookies. Secrets are held as encrypted provider secrets, never in code. A self-custodied treasury’s keys are held only by your own wallet, never by us. No system is perfect, and we describe the known limitations honestly in our security documentation.

Privacy questions: privacy@devilabs.dev. See also the Terms of Service.