Legal

Privacy Policy

Edith uses wallet identity and request history to make payment decisions. This page explains what the current application processes, what becomes public on Sui, and what you can control.

Last updated 3 November 2026

1. Scope

This policy covers the Edith website and API at this domain. A Sui wallet, API provider, block explorer, or other linked service has its own practices. Edith does not ask for your wallet seed phrase or private key.

2. Information Edith processes

Do not place personal data or secrets in a paid URL unless the provider needs them. URLs and some response details can become part of Edith's activity or memory records.

3. Why Edith uses it

Edith uses these records to authenticate your session, isolate one wallet's agents and history from another's, apply spending limits, prevent duplicate payment submissions, show activity, verify settlement, and decide whether a repeat request should be refused. Infrastructure may also process request metadata needed to operate and protect the service.

4. Where records go

Neon Postgres holds wallet-scoped application records, pending plans, spending state, nonces, rate limits, and the provider payment ledger. Walrus Memory holds outcome records in a namespace tied to a wallet address. Those records can include request identifiers, provider, price, result, reason, and transaction digest. Do not treat Walrus Memory as a place for secrets.

Vercel serves the site and runs the API. Tatum provides a Sui gateway for checking transfers. Sui records settled transactions. API providers receive the requests and payment proof needed to deliver their resources. These services may process network identifiers, addresses, transaction details, and service traffic under their own policies.

5. Public chain data and off-chain data

A Sui payment can make the payer address, recipient address, amount, gas use, transaction digest, and on-chain activity publicly visible. Edith cannot erase a confirmed blockchain transaction. Your agent key, session cookie, application activity, spending limits, and database records are off-chain. Walrus blob identifiers can be shared as evidence; do not assume that off-chain storage or external services provide the same privacy as a local file.

6. Your choices

You can decline a wallet signature, disconnect an agent key, sign out to clear the Edith session cookie and remembered wallet name, and clear site data in your browser. You can inspect your activity in the app. These actions do not delete previously settled Sui transactions or automatically erase server and Walrus records. There is no self-service deletion control for those records in the current app.

7. Retention and security

The session cookie is set for seven days unless you sign out earlier. The remembered wallet name remains in local storage until sign-out or browser clearing. The current application does not specify a fixed automatic deletion period for database and Walrus records. Access controls and scoped keys limit routine access, but no internet service can promise absolute security.

8. Contact and changes

This policy may change as the service changes; the date above will be updated. A private privacy contact and the operator's legal identity have not yet been supplied by the project owner. Do not post sensitive information in public GitHub issues. This policy is pending owner and legal review.