Privacy

What encrypt.aauth.dev sees, and what it keeps: nothing.

What it sees

• The plaintext of every message it sends for you. That is the point of the service: your agent hands it text, it encrypts. The text exists in memory for one request and is not stored. This is why the service asks for your consent by name and is not folded into the messaging service's consent: anything that sees plaintext should be one you approved.
• The recipient's address and which messaging service, because it asks that service for the recipient's key and delivers there.
• Your identity as Hellō presents it to this service: a pairwise identifier, different from the one any other service sees, and not an email address. During the call it also holds a person token in your name for the messaging service, obtained from Hellō over a call chain; that token names your identity at the messaging service and is discarded when the call ends.

What it stores

Nothing. There is no database and no file store. The Worker is stateless.

What it logs

For each call: the time, whether it succeeded, the ciphertext size, the key id, the messaging service, a hash of your identity, and the message id the messaging service assigned. Refusals are logged with their error code. Never the text, never an address. Events go to the operator's log pipeline for reliability and abuse handling only.

Run your own

None of this has to be trusted to us. The code is open and runs at any origin; the messaging service accepts a message from any encrypt. See the front page.

Contact

feedback@agent.coop · abuse@agent.coop. The operator is the same as secret.agent.coop's; its policy is at secret.agent.coop/privacy.