Privacy policy
In force from 9 October 2026.
This policy covers the websites reefstore.app and shoalapps.com, the Reef app and its repository, licences for paid apps, Pilot, and the hosted Shoal Messages and Shoal Push service. It does not cover Paddle, Signal, Telegram or other Matrix servers, which have their own policies. Apps you install keep their own data on your phone unless this policy says otherwise.
Who we are
The controller is Patrick Quinn, trading as Shipwright, in Ireland. Write to privacy@reefstore.app about anything in this policy. We have not appointed a data protection officer; we are not required to.
The short version
- The websites set no cookies of their own and use no analytics.
- Reef has no account and sends no usage data.
- A licence holds no name, email address or card details. Paddle, which sells our apps, handles payment.
- Pilot sends questions it cannot answer on the phone to Groq, and in full Pilot also to Jev, both in the United States. It replaces phone numbers, email and postal addresses, account numbers and (full Pilot) contact names first. Our relay keeps no content.
- Shoal Messages and Shoal Push are not open yet. The section on them says what they will keep, and for how long.
- We do not sell your data, use it for advertising or profiling, or train AI models on it.
The websites
reefstore.app and shoalapps.com are served by Cloudflare. Like any web server, Cloudflare sees your IP address and the pages you ask for, to deliver them and to protect the sites from attacks. The site Workers have logging turned off and we export no logs, so we keep no access log.
The pages set no cookies of their own, run no scripts and load nothing from other servers. The exception is the checkout page on shoalapps.com, which loads Paddle's checkout (see "Buying an app").
- Purpose: deliver the pages; keep the sites secure.
- Legal basis: our legitimate interests in running secure websites (Article 6(1)(f) GDPR).
- Retention: we keep nothing.
Reef and its repository
Reef downloads the catalogue and the packages from the Reef repository on reefstore.app (a Cloudflare Worker with its files in Cloudflare R2, EU jurisdiction). The repository sees your IP address and which files you download. It keeps no access log. Reef has no store account and sends no usage data.
If you have paid apps, Reef also asks our licence service at licences.reefstore.app for fresh licences and for the list of revoked licences (see "Licences").
- Purpose: deliver the apps you install and keep them up to date.
- Legal basis: legitimate interests (Article 6(1)(f)).
- Retention: we keep nothing.
Buying an app
Paid apps are sold on shoalapps.com by Paddle.com, our reseller and merchant of record. Paddle receives your payment details, name, email address and country, and decides how to use them, under its own privacy notice. We never see your card, and we do not keep your name or email address: Paddle does.
When the payment completes, the checkout page, or Reef, collects your licence from our licence service with a random code it made for that purchase. The code contains nothing about you.
Licences
Our licence service runs on Cloudflare Workers, with its database in Cloudflare D1 (EU jurisdiction). For each purchase it keeps:
- the licence id, the app, the plan (one-off or subscription), and the expiry, cancellation and revocation dates;
- Paddle's subscription or transaction numbers, and Paddle's customer number;
- each payment: its transaction number, amount, tax, currency and Paddle's fee;
- the claim code that delivered the licence.
The licence token on your phone holds the licence id, the app, the plan, the expiry and when it was issued: no name, email address or payment details.
- Purpose: issue licences, renew and revoke them, help with a lost licence, a refund or a chargeback, and keep our accounts.
- Legal basis: performing our contract with you (Article 6(1)(b)), and keeping accounting records the law requires (Article 6(1)(c)).
- Retention: while the licence is valid, then six years from the end of the year of the last payment, the period Irish tax law requires us to keep business records (section 886 of the Taxes Consolidation Act 1997), or longer while a tax inquiry about them is open.
Cloudflare's Workers logs record each request to the licence service: the time, the address requested (which, for a licence refresh, contains the licence id), the result, and network details of the request, which can include your IP address. Cloudflare keeps these logs for at most 7 days. We use them only to run and secure the service (legitimate interests).
Pilot
Pilot and Pilot Lite answer some questions on the phone and send the rest, through our Pilot relay, to Groq and (full Pilot only) to Jev, both in the United States. Before anything leaves the phone, phone numbers, email and postal addresses, account numbers and (full Pilot) contact names are replaced with placeholders. Our relay checks your licence, counts your requests per day, and keeps no content. It keeps the daily counts for 35 days.
What is sent, to whom, on what basis and for how long is set out in Pilot: what leaves the phone, which is part of this policy.
Shoal Messages and Shoal Push
The hosted Shoal Messages service (a Matrix account on our server, with bridges to Signal and Telegram) and Shoal Push (our push server) are not open to subscribers yet. This section says how they will handle your data. We will update it, naming our hosting provider, before the first account is created. The service will run on servers in the EU.
Encryption, and what bridged chats mean
- Chats between Matrix users are end-to-end encrypted by default. Our server stores and forwards them encrypted and cannot read them. Public or unencrypted rooms you join are not, and the server can read them while it keeps them.
- Chats you bridge from Signal or Telegram are different. To connect them to Matrix, the bridge on our server decrypts and re-encrypts each message, so it handles those messages unencrypted in memory while passing them on. Our database and backups hold bridged messages encrypted, and we do not look at them, but the protection is our security measures, not end-to-end encryption. If that is not acceptable for a chat, use the official Signal or Telegram app for it.
- Push notifications carry only which room and message are new and an unread count, never message text.
What we keep, why, and for how long
All of this is to provide the service you subscribe to: performing our contract with you (Article 6(1)(b)), except where the table says otherwise.
| Data | Retention |
|---|---|
| Account: Matrix id (random unless you choose one), password (hashed), display name, avatar, and the licence id it belongs to | Until the account is deleted (see "When you leave") |
| Devices you sign in on, and their encryption keys | Until you sign out; devices unused for 90 days are removed |
| Messages and files, with sender, room and time (encrypted in encrypted chats) | 30 days by default; room admins can choose 1 to 90 days. Files: 30 days after they were last opened; files from other servers, 7 days |
| Room details: names, members, avatars, including the names and pictures of Signal and Telegram contacts and groups shown in bridged chats | While the room exists; bridged rooms are deleted when you unlink the bridge |
| Your Signal or Telegram session (linked-device keys or login session), and the contact and group details those services send to any client, including your contacts' phone numbers | Until you unlink, the account is deleted, or the remote service ends the session |
| Bridged message content | Only in memory while it is relayed; not stored in readable form |
| Your device's IP address and app version, for security and abuse prevention (legitimate interests, Article 6(1)(f)) | 3 days |
| Push messages (room, message id, unread count) | Delivered at once; held up to 12 hours if your phone is offline |
| Error logs, which can contain a Matrix id or a room id (legitimate interests) | A small rotating log on the server, overwritten within days |
| Encrypted backups of all of the above (legitimate interests) | 7 days |
| Abuse reports and how we handled them (legitimate interests; legal obligation where one applies) | As long as needed to handle the report and any follow-up |
The servers keep no request logs.
Where it goes
- Signal and Telegram. When you link an account, our bridge connects to Signal or Telegram as your client, as their own apps do. They process what any client sends them, under their own policies. Telegram can read ordinary (cloud) chats, as with any Telegram client; secret chats are not bridged.
- Other Matrix servers. If you chat with people on other Matrix servers, those rooms are copied to their servers, which keep them under their own rules. Bridged chats are never shared with other servers.
- Hosting. Our hosting provider in the EU stores the service and its backups as our processor. We will name it here before the service opens.
When you leave
When a subscription lapses, it keeps working for 7 days. After that the account is suspended: you can still sign in and read, but not send, and your bridges stay linked so that renewing resumes the service.
When you ask us to delete your account, or when a licence is revoked (for example after a refund), we log out your Signal and Telegram sessions (they disappear from your linked devices), delete your bridged chats, your push account and the files you uploaded, and deactivate and erase your Matrix account. We keep the licence id on the deactivated account so that a revoked licence is still recognised. Backups containing your data expire within 7 days. Messages you sent to other people stay in their copies of the conversation, as with any messaging service.
Who else receives data
| Recipient | Role | What | Where |
|---|---|---|---|
| Cloudflare, Inc. | Our processor: hosting of the websites, the repository, the licence service and the Pilot relay | Requests in transit; the licence and relay databases; Workers logs | Worldwide network; databases and the repository in the EU |
| Paddle.com | Merchant of record, a separate controller | Payment and billing details | Paddle's privacy notice |
| Groq, Inc. | Our processor for Pilot | Redacted questions (see the Pilot page) | United States |
| TypeSafe AI, Inc. (Jev) | Pilot's decision service, full Pilot only | The gist of requests, with no names, contact details, links or identifiers of you or your phone (see the Pilot page) | United States |
| Cloudflare's web search and its search providers | Web searches in full Pilot | The search words | See the Pilot page |
| Signal, Telegram, other Matrix servers | Separate controllers, when you use them through Shoal Messages | What any client sends them | Their own |
| Our EU hosting provider | Our processor for Shoal Messages and Shoal Push | Everything in that section | EU |
We disclose data to public authorities only where the law requires it. We cannot hand over the content of end-to-end encrypted chats: we do not have it.
Transfers outside the EU
Cloudflare and Groq are in the United States. Our transfers to them rely on their data processing addenda, which include the European Commission's standard contractual clauses. Jev is in the United States too; Pilot sends it only the gist of a request, through our relay, with nothing that identifies you or your phone. Details, and the transfers to Signal and Telegram when you link them, are on the Pilot page and above. You can ask us for a copy of the safeguards.
Security
Encryption in transit everywhere. End-to-end encryption for Matrix chats. API keys for Groq and Jev stay on our relay and never reach your phone. The databases for licences and Pilot are in the EU and hold no names or email addresses. Shoal Messages backups are encrypted to a key kept offline. Only the operator has access to the production systems.
Do you have to give us this data?
No law requires it. You need a licence to use a paid app, and Pilot needs your licence and a device id to answer from the cloud. Without them, those services cannot work. You can use Reef and the websites without giving us anything.
Automated decisions
We make no decisions about you based solely on automated processing that have legal or similarly significant effects. Automatic checks only enforce your licence and the daily Pilot limits, and Pilot's decision model only chooses how to answer a question.
Children
Our services are not meant for children under 16, and we do not knowingly process their data.
Your rights
You can ask us for access to your personal data, and to correct, delete or restrict it, to receive it in a portable form, or object to processing based on our legitimate interests. Write to privacy@reefstore.app. We answer within one month. Because we hold no names or email addresses, please quote your licence id or your order number (it starts with txn_) so we can find your data.
You can complain to the Data Protection Commission, 21 Fitzwilliam Square South, Dublin 2, D02 RD28, Ireland (https://www.dataprotection.ie), or to the supervisory authority where you live or work.
Changes
We publish every change on this page with a new date. We announce changes that matter on the websites and, where we can, in the apps, before they take effect.
Last updated: 9 October 2026.
Source: services/privacy/privacy-policy.md in the Shipwright repository; paths and ADR numbers in the text refer to it.