Privacy & Data Policy

Last updated: 29 August 2026.

This is the whole of it, in plain words: your data is yours, we don't sell it, we don't share it to advertise to you, and during the beta a human may look at limited content to fix mistakes — an access we are deliberately engineering away.

1. What we hold.

Your account details (email address, name, sign-in identifiers). Everything you send Peon — emails, attachments, photos, links — and the wiki built from it. Operational records: billing ledger, usage metering, outbound-mail logs, and the ordinary technical logs any web service keeps.

2. What it's for.

Running the service you asked for: filing what you send, answering what you ask, metering what it costs, and keeping the lights on. Nothing else. No advertising, no profiling, no selling — not now, not later.

3. AI processing.

Filing and answering are done by AI models from established providers, operating under contracts that bar them from using your content to train their models. Your content goes to them only to do the work you asked for.

4. The beta clause, honestly.

While Peon is in beta, the operator may read specific conversations and filed content — mainly what you flag, and failures the system reports — to diagnose mistakes and improve the service. This access is limited, logged in the working record, and temporary: it is being narrowed release by release and will be phased out as the system earns the right to run unwatched. It is never used for anything beyond fixing and improving Peon.

5. Who else touches it.

Subprocessors only, each doing one job: Microsoft Azure (hosting and storage), Google Workspace (the mailbox), PayPal (payments — card details never touch this app), and the AI model providers above. Plus disclosure where the law compels it — in which case we'll tell you, unless the law forbids that too.

6. Where it lives, and for how long.

Your content stays until you delete it or your account. Delete your account and your wiki, filed content, and attachments go with it; ledger entries and audit logs are kept as long as accounting and security require, then go too.

7. Security.

Encrypted in transit, access restricted to what operating the service requires, secrets kept out of the codebase. We take this seriously and still won't pretend: no service can promise perfect security. See the Terms for how we handle incidents — the summary is: we tell you, plainly.

8. Your controls.

Export your wiki whenever you like. Correct anything by sending the correction. Delete your account by asking. Questions, complaints, and formal requests all go to the same place: peon@ykymf.com.

9. Changes.

Material changes get flagged at sign-in and dated above. The promise that doesn't change: your data is yours.