Privacy Policy

The short version:
we can’t read your messages.

Not because we promise not to — because the system is built so that we never hold the keys. This page describes what data exists, where it lives, and what we could hand over if someone compelled us to.

Last updated · October 2026

/01

What we never collect

  • Your phone number — we never ask for one
  • Your email address — we never ask for one
  • Your name, contacts, photos or address book
  • The content of any message — unless you attach it to an abuse report yourself
  • Your contact graph — who you talk to, or how often
  • Your location, advertising ID or device fingerprint

There is no signup form. Your identity is an Ed25519 keypairgenerated on your device the first time you open the app; your Stonechat ID is a hash commitment to the public half of it. It reveals nothing about you, and we have no way to connect it to a human being.

/02

Where data lives

Your phone

Everything that matters

Your private keys, your contacts and your entire message history — encrypted at rest. Never uploaded, never backed up to us. Uninstall the app and it is gone for good.

Your relay (mailbox)

Sealed envelopes, briefly

End-to-end encrypted envelopes waiting for delivery, plus your published prekeys. The moment your phone acknowledges receipt, the envelope is deleted. It never holds plaintext.

The directory (hub)

Four fields

Your Stonechat ID, your public key, your relay’s address, and a hash of your auth token — plus the date the account was created. No contact list, no message data, no log of who you talk to.

The push gateway

A device token

Your Apple or Google push token, so your mailbox can wake your phone. The wake-up is content-free — no sender, no preview, no message. The gateway never learns your Stonechat ID.

/03

If we host your mailbox

Stonechat is invite-only for now, and nothing is sold. A mailbox we host needs an invite code, which we hand out ourselves. We don’t ask for a name, an email address or a payment method to issue one.

On our side, an invitation record stores a hash of the code and the Stonechat ID that entered it, so the hub can tell that your ID is invited. Being blunt about the consequence: if we know who we gave a code to, that record can link you to a Stonechat ID. It still says nothing about your messages, your contacts or your conversations — but it is the one place where something about the real world and a Stonechat ID can sit in the same row.

If that link is unacceptable to you, self-host. Run the relay on your own hardware, tell us nothing, and still talk to everyone on the network. That option exists precisely so this paragraph has an answer.

/04

Tracking and analytics

The app contains no analytics SDK, no advertising SDK, no crash-reporting SDK and no third-party trackers. We do not collect usage events, we do not build profiles, and we have nothing to sell to anyone — data brokers included.

The one third-party component in the app is Apple’s and Google’s push infrastructure, which is what makes a notification physically possible on a phone. It carries a content-free wake-up signal and nothing else.

If we ever add product metrics, they will be first-party, aggregate, coarsened to a calendar day, and described on this page before they ship — never message content, never identities, never who talks to whom.

/05

If you report someone

The app lets you report another user to the hub that hosts them. This is the single exception to everything above, and it only ever happens because you chose it.

A report always carries the reported person’s Stonechat ID, a category, your own Stonechat ID, and whatever you type into the box. It carries no message contentunless you switch on “attach the last messages they sent you” — a control that is off by default and shows you the exact lines before you send them. Photos, files and voice messages are never uploaded; an attachment appears only as a note that one was sent.

We keep reports for 180 days and then delete them. Attached messages are deleted sooner — as soon as a human has read the report and decided what to do. What survives is the decision, not the evidence.

Acting on a report means taking a mailbox away or refusing someone a new one. It never means reading a conversation, because we still cannot: a report shows us only what the reporter chose to show us, and nothing at all about anyone else.

/06

Legal requests

If we receive a valid legal order, we can only produce what we actually hold: the directory fields listed above, for invited users the invitation record described in section 03, and any abuse report still inside its retention window (section 05). We cannot produce message content, message history, or a contact graph, because none of it exists on our infrastructure in a readable form.

Undelivered envelopes on a relay are ciphertext sealed for one recipient’s key. A full compromise of every machine we operate yields exactly that: ciphertext.

/07

Deletion and your rights

Deleting the app deletes your history — it only ever existed on your device. To remove your directory entry and destroy your mailbox, use the in-app control or write to support [at] stonechat.app from the app. Destruction is immediate and irreversible; there is no soft-delete and no archive to restore from.

Under GDPR you have rights of access, rectification, erasure and portability. They are unusually easy to satisfy here, because the complete set of personal data we hold about a self-hosting user is the four fields in section 02.

Stonechat is not directed at anyone under 16 — the minimum age in ourTerms of Service — and we have no way to collect the kind of data that age-targeting would require.

/08

The legal basics

Data protection law — the GDPR in the EU, and its UK equivalent — asks every service to say why it is allowed to handle each piece of personal data, how long it keeps it, and who else touches it. Here is that, for everything described above.

  • Directory entry (section 02)Needed to provide the service — Art. 6(1)(b)Until you delete your account.
  • Your mailbox: sealed envelopes, prekeys, push tokenNeeded to provide the service — Art. 6(1)(b)Envelopes until your phone acknowledges them; the mailbox until you delete it, or 14 days after your invitation ends.
  • Invitation record (section 03)Needed to provide the service — Art. 6(1)(b)While the invitation lasts. When you delete your account it is unlinked from your Stonechat ID.
  • Reports you file, or that are filed about you (section 05)Our legitimate interest in keeping the service free of abuse, and our legal duties — Art. 6(1)(f), 6(1)(c)180 days; attached messages only until a person has reviewed the report.
  • Enforcement records: a ban, or a mailbox destroyed for abuseOur legitimate interest in keeping abusers off the service — Art. 6(1)(f)As long as the abuse case needs them.
  • Emails to support@ and abuse@Our legitimate interest in answering you — Art. 6(1)(f)As long as needed to answer and follow up.

Server logs. Our hub, payment service and relays do not write your IP address to their logs. Request limits that stop abuse are counted in memory and forgotten within minutes. Our website’s host keeps its standard web-server logs of visits to stonechat.app.

Who else is involved. Google Cloud runs our servers (the directory and invitation service in the United States; mailboxes in the country you choose). Apple and Google deliver the content-free push signal. Our website host serves stonechat.app, and our email provider carries anything you send to support@ or abuse@. Google Cloud and those hosts handle data only on our behalf; Apple and Google also act under their own privacy terms.

Data outside the EU and UK. Gazelle Labs LLC is a US company and the directory runs in the United States, so the fields in section 02 are processed there. Where our providers move personal data out of the EU or UK on our behalf, they do so under the EU–US Data Privacy Framework or the European Commission’s standard contractual clauses (and the UK equivalents).

EU and UK representative. We have not yet appointed a representative in the EU or UK under Article 27. Until we do, contact us directly at support [at] stonechat.app; this page will name them once appointed.

Complaints. If you think we handle your data unlawfully, tell us first and we will try to fix it — but you always have the right to complain to the data protection authority where you live or work (in the UK, the ICO).

/09

Who we are

Stonechat is operated by Gazelle Labs LLC, a limited liability company registered in Wyoming, United States. For the fields described in section 02 — the only personal data that reaches our infrastructure — Gazelle Labs LLC is the data controller. The rules for using the service itself are in ourTerms of Service.

Privacy questions, access and erasure requests:support [at] stonechat.app. To report a relay being used to harass, spam or host illegal content:abuse [at] stonechat.app, which is monitored continuously. To report another user, the report option inside the app reaches the same desk and carries the context described in section 05.

Questions about any of this?

Ask a specific question and you’ll get a specific answer.