Privacy notice

In one paragraph

Just Ask Satoshi is a voice and chat product. To make it work we send your microphone audio (voice mode) or your messages (chat mode) to ElevenLabs for speech-to-text and back as synthesised speech. We do not store the raw audio. For anonymous users, we keep the text transcript for up to 30 days for debugging and accuracy review, then delete it. For signed-in users, your conversation history is stored persistently so you can return to past sessions — you can delete any conversation, or your entire history, at any time via the history drawer. We do not sell your data, run advertising, or share your information with third parties beyond the infrastructure providers listed below.

What we collect

• Microphone audio while you are in an active conversation. Streamed to ElevenLabs in real time. Not stored on our servers.
• Conversation transcripts (your words and Satoshi’s responses). For anonymous users, retained for up to 30 days for debugging and to improve answer quality, then deleted. For signed-in users, retained indefinitely as part of your history so you can come back to past conversations — deletable at any time via the in-app history drawer (per-conversation or all-at-once).
• Account identifiers (signed-in users only). When you sign in with Google we store your Google account identifier and email. When you sign in with a wallet we store the wallet address. Both come to us via Privy, the auth provider that brokers the sign-in. Deleting your account removes all of this plus your conversation history.
• A rate-limit identifier — a salted SHA-256 hash of your IP address combined with a browser fingerprint and the current UTC day. We never store the raw IP address in long-term storage. The hash exists so you get five free minutes per day rather than five per session.
• Product analytics — page views, event names (\`session_start\`, \`limit_hit\`, \`waitlist_signup\`, etc.), and latency metrics. Only collected if you accept analytics cookies.
• Error reports — when something breaks, we record what happened and a stack trace so we can fix it. Transcripts attached to error reports are scrubbed for Bitcoin addresses, extended public keys, mnemonic-shaped strings, and email addresses before they leave the server.
• Waitlist email, only if you choose to give us one. Stored as a salted hash for de-duplication; the original address is held alongside the hash so we can email you.

Third parties involved

• ElevenLabs — voice synthesis, speech-to-text, and the conversational agent itself. Their privacy notice: elevenlabs.io/privacy.
• Cloudflare Turnstile — bot mitigation in front of session-token issuance. No cognitive challenge; works in the background.
• Vercel — frontend hosting, edge functions, and CDN.
• Railway — backend API and Redis hosting.
• DigitalOcean Managed Postgres — persistent storage for signed-in users’ account records and conversation history. Connections are TLS-encrypted; data is encrypted at rest by the provider.
• Privy — auth (Google + wallet sign-in). Receives sign-in events and the identifiers you provide (email, wallet address). Their privacy notice: privy.io/privacy-policy.
• Sentry — error tracking. Only receives scrubbed payloads.
• PostHog — product analytics. Receives event names and metadata only when analytics cookies are accepted.

Cookies and similar tech

Two categories. Essential — a session token and a browser fingerprint stored in localStorage. These exist so the rate limiter can give you the right amount of conversation time. They are required for the product to function.

Analytics — PostHog and Sentry session replay. Off by default. The banner on first visit lets you accept or decline; you can change your mind by clearing your browser’s storage for this site.

Your conversation history

When you’re signed in, every voice and chat session creates a stored conversation containing the transcript of what you said and what Satoshi replied. This lets you come back to a past conversation, see what was discussed, and continue from where you left off.

You control this history end-to-end:

• Open the history drawer from the top-left of the page when signed in to see every stored conversation.
• Delete a single conversation by hovering its row and clicking DEL.
• Delete all conversations via the DELETE ALL HISTORY button at the bottom of the drawer. A second confirmation click is required to avoid accidents.
• Sign out ends your session; your stored history persists for the next time you sign in.

Deletes are real — the conversations and their messages are removed from our database immediately, with cascade delete on the SQL foreign keys. We don’t keep a soft-delete tombstone or a hidden archive. If you also want your account record itself removed (email, wallet address, sign-in history), email us at the address in the contact section; we’ll action it within 30 days.

Your rights

If you are in the EU/UK, you have the right to access, correct, or delete your data; to object to or restrict processing; and to lodge a complaint with your data-protection authority. Email us and we will action requests within 30 days. Outside the EU/UK we extend the same rights as a matter of policy.

Contact

Privacy questions and deletion requests: hello@persistence.one. Source code: github.com/persistenceOne/justasksatoshi. The system is open enough that you can verify the claims above against the code.

Changes

If we change anything material, we update the date at the top and post the previous version in the repository so you can diff them.