Crowdpost privacy policy

Last updated: 20 November 2026

This policy explains what information Crowdpost uses, why, how long we keep it, and your rights. It covers the Crowdpost app and the website crowdpost.app.

1. Who we are

Crowdpost is made by ZEOUR LTD, a company registered in England and Wales (company number 14173485), registered office 20-22 Wenlock Road, London, N1 7GU, England ("ZEOUR", "we", "us"). We are the controller of the personal information described here.

We are registered with the UK Information Commissioner's Office (ICO) as a data controller, registration number ZC153409.

Crowdpost is offered only to people in the 27 member states of the European Union. Because ZEOUR is a UK company, both UK data protection law (the UK GDPR and the Data Protection Act 2018) and the EU GDPR apply to how we handle your information.

  • Privacy contact: privacy@crowdpost.app
  • Our data protection contact: the Crowdpost privacy team, at privacy@crowdpost.app
  • Our representative in the European Union (GDPR Article 27): Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria. See "Our EU representative" below.

Our EU representative

We value your privacy and your rights as a data subject and have therefore appointed Prighter Group with its local partners as our privacy representative and your point of contact for the following:

  • European Union

Prighter gives you an easy way to exercise your privacy-related rights (e.g. requests to access or erase personal data). If you want to contact us via our representative, Prighter or make use of your data subject rights, please visit the following website: https://app.prighter.com/portal/16385989243

You can also contact us directly at privacy@crowdpost.app.

2. The short version

  • Your messages, calls, photos, videos, voice notes, files, shared locations, profile photo and backups are end-to-end encrypted. They are locked on your phone before they leave it. We cannot read them.
  • To deliver messages we handle some information we can see, such as your username, who your friends are, when messages are sent, and your phone's notification token. Every item is listed in section 4.
  • We do not sell your information, show ads, or track you across other apps or websites. The app contains no advertising or analytics tools. It uses Apple's push service on iPhone and Google Firebase Cloud Messaging on Android only to deliver notifications (section 6). The website uses no cookies.
  • Crowdpost is only for people aged 18 or over.
  • You can delete your account at any time in Settings › Privacy & Security › Delete account, or by following crowdpost.app/delete-account.

3. What we can never read

Content you send is end-to-end encrypted. One-to-one chats use an open-source, independently audited implementation of the Double Ratchet with X25519 key agreement, which gives each message its own key; groups and rooms use keys held only by their members. The keys stay on your devices. We store and pass on only encrypted data, so we cannot read, scan or hand over:

  • the text of your messages, in chats, groups and rooms;
  • photos, videos, voice notes, documents and other attachments;
  • locations you share in a chat, and your area during a Meet-up;
  • your profile photo (only your friends receive the key to it);
  • the note attached to a message request;
  • your encrypted chat backups (the key that opens them stays on your phone and in your own iCloud Keychain or Google account, and your optional recovery key stays with you; we never receive either);
  • the content of calls.

Notification previews are unlocked on your phone, not on our servers.

Reports. A report you choose to make tells us who or which room you are reporting, why, and anything you add in your own words. You can also choose to include the person's profile picture and status line, or the group's or room's picture, as your phone shows them. These are end-to-end encrypted, so we see them only if you include them. A report never includes your messages. The one exception is a view-once photo, video, voice note or text that you report from inside its viewer: a copy of that item goes with the report, encrypted so only our moderators can open it, and it is deleted after 90 days.

4. Information we use

Information Why Lawful basis (UK and EU GDPR) How long we keep it
Account details: username and display name; the email address or phone number you sign in with or add as a recovery contact Create and secure your account, let people find you by username, send sign-in codes, help you get back in if you lose your passkey Contract Until you remove it or delete your account
Passkey data: a public key and credential ID (your fingerprint or face never leaves your phone) Sign-in without a password Contract Until you remove the passkey or delete your account
Profile: optional status line Shown to other people on your profile Contract Until you change it or delete your account
Connections: friends, message requests, blocks, and group and room memberships Decide who can reach you, deliver group and room messages, apply your blocks Contract Until removed, or until you delete your account
Delivery information: sender, recipient, conversation and time of each encrypted message; delivery and read receipts Get encrypted messages to the right phone Contract Encrypted messages are deleted from our servers once delivered, and after 30 days if never collected. A record that a notification was sent (message ID only) is kept for 7 days to avoid duplicate alerts. A record that a message was delivered (its ID, sender and recipient), which lets phones carrying copies of it stop, and a record of which sender first used each message ID for a recipient, are kept for 8 days
Group and room details: name, icon, creator; for rooms, a description, whether it is public or private, its place and radius (if set), and its opening times Show and organise groups and rooms; let people at a place find public rooms Contract Until the owner deletes it or its time window ends. A public room stops appearing in Nearby after 30 days without activity. Repeating rooms have their messages wiped at the end of each session
Room hosting: if ZEOUR invites you to host a public room, the invitation, whether you accepted or declined, whether you are its main host, and a record of every change to the room's hosts Run public rooms with named hosts, show members who hosts a room, and keep a record of who could post and when, for safety Contract (once you accept); legitimate interests (safety records) While you host. The record of host changes is kept for 12 months; if you delete your account, your ID is removed from it
App version: the version number of the Crowdpost app on your phone Offer only the features your version of the app supports Contract Replaced each time you open the app; deleted with your account
Your location when you look for rooms nearby: your phone's coordinates are sent with the search Show public rooms at your place Consent. You choose to search and can refuse location permission Not stored by Crowdpost. It may appear briefly in our hosting provider's request logs for up to 7 days
Meet-up: while you are in a Meet-up you started or joined, your approximate area (about 50 m) is sent end-to-end encrypted to the other people in it. Phones in a Meet-up may also leave sealed "seen here" notes: a rotating code plus an encrypted approximate area that only that Meet-up can open, with no names Let the people in a Meet-up find each other, including in crowds with no signal Consent — you start or join, and can pause or leave at any time We never hold your area in readable form. Sealed notes are deleted after 24 hours
Off-grid routing names: your phone's daily off-grid name and its public signing key, registered while you are online Let a nearby phone with internet prove it can hear you over Bluetooth and hand over encrypted messages waiting for you, and let our server check that a message another phone uploads for you really is yours. Your phone proves each name is its own when registering it; to limit misuse we keep an hourly count of your registrations, deleted after 2 days. That phone sees only a rotating daily name, never your account. We are not told who heard you or where Contract 8 days, then deleted automatically
Messages you upload for others: if you carry messages for others, when your phone uploads one of them our server learns that your account uploaded someone else's message, which reached your phone at some point in the last 7 days, and when. To deliver it, the server works out who wrote it and who it is for from their daily off-grid names Check the message really comes from its author (we check the author's signature), deliver it as from its author, and stop misuse with upload limits. The person who receives it is not told which phone helped. A first message to someone the writer is not connected with arrives as a message request, with the same limits as any request; anything else between people who are not connected is discarded Contract (delivering messages; carrying them is a setting you choose); legitimate interests (preventing misuse) We do not keep a record of which messages your phone uploaded. To apply the limits we keep hourly counts — of your uploads, and of uploads of each writer's messages — deleted after 2 days. Our hosting provider's request logs may briefly show that your phone made an upload, as for any request. The message itself is handled like any other message (see Delivery information)
Country checks: the countries named by your phone number's country code, your app store, your SIM and mobile network, your phone's region setting, and your internet connection at sign-in; the result (allowed, blocked or unknown); and, where a country's law requires an age check, whether one is needed and its result Crowdpost is offered only in the EU, so we check where people are signing up and using it from Legitimate interests (offering Crowdpost only where we operate) Country codes, results and their dates only; we do not keep your IP address or location for this. Kept until you delete your account
New-phone sign-ins: when your account signs in on a phone, the phone's type and name, the country of the sign-in, a device key, its notification ID, and whether the sign-in was approved, and when Protect your account: a new phone is approved from your existing phone, with your recovery key, or after a safety wait; a phone approved before is recognised Contract; legitimate interests (account security) Until you delete your account
What you agreed to: which terms and policies you accepted, their version, when, and the app version you used Keep a record of what you agreed to Contract; legitimate interests (showing what was agreed) Until you delete your account
Presence: "last seen" time and whether you show it Show your friends when you were last online. You can turn this off Legitimate interests (a feature people expect), subject to your settings Overwritten continually; deleted with your account
Notification tokens: device token, platform and device ID Send you message and call alerts Contract Until you sign out or delete your account
Public encryption keys: your public identity key and one-time keys Let others start encrypted chats with you Contract One-time keys until used or replaced. See section 7 for the key log
Encrypted media: photos, videos, voice notes and files you send, stored as scrambled data we cannot open; your profile photo and group pictures Deliver attachments to the people you send them to, and show your pictures to the people allowed to see them Contract Chats with one person: deleted from our servers 30 days after it reaches the other person's phone, or 30 days after you sent it if it never does. Groups and rooms: kept while the group or room exists, so people who join later can see it; deleted when the group or room is deleted or ends, and when a repeating room's session ends and its messages are cleared. After that the only copies are on the phones. Profile photos and group pictures stay until you change or remove them. Everything you uploaded is deleted when you delete your account
Encrypted backups Store backups you choose to make Contract Until deleted by you or the app, or until you delete your account
Reports and moderation records: who reported whom or which room, the reason, when, the reporter's explanation and any profile picture or status line they chose to include, our decision, any warning, suspension or ban, and appeals Keep Crowdpost safe, act on reports, prevent banned people from returning, and meet our legal duties Legitimate interests (safety); legal obligation where the law requires us to act or keep records 12 months after the case is closed; bans are kept for 2 years
Crash reports and app logs: a technical log with phone numbers, email addresses and keys removed, plus your phone's operating system and app version Fix faults. Sent only if you tap "Send report" or "Send log" Consent 90 days
Call connection information: when you make or answer a call over the internet, your phone's IP address and port, the other phone's IP address and port, a temporary relay sign-in, and when the relay was used and how much data passed through it Our own call relay (turn.crowdpost.app) helps the two phones find a route to each other, and carries the call only when they cannot connect directly. The call stays end-to-end encrypted: the relay passes on scrambled data it cannot unlock, so it cannot hear or see your call Contract (connecting the calls you make and answer); legitimate interests (keeping the relay secure and stopping misuse) The relay's log is deleted after no more than 8 days. The temporary sign-in stops working after 4 hours. It holds only an expiry time and a coded tag, not your account ID, name or phone number
Network information: IP address Unavoidable when your phone connects to our servers and map server Legitimate interests (running the service securely) Kept only in our providers' own security logs, for no more than 30 days; we do not keep a copy
Messages you send us: emails to support, safety or privacy Answer you and keep a record Legitimate interests; legal obligation for rights requests and complaints 2 years

Public rooms and their hosts. Public rooms are set up by ZEOUR. Each is run by one to five hosts: Crowdpost users ZEOUR invites, who become hosts only if they accept. Only hosts can post in a public room; everyone in it can read the posts and react to them. Posts appear under the room's name, and the room's details show who hosts it. Messages in rooms are end-to-end encrypted between the people in the room; ZEOUR sees a room's name, description and settings and who hosts it, moderates public rooms, and acts on reports.

We do not collect your address book, advertising identifiers, or your location in the background. People can find you by your @username, a QR code or invite link you share, or on the Nearby radar (if you allow it), never by your phone number or email address.

Automated limits. To stop spam, our servers automatically limit how many message requests and some other actions an account can make in a short time. This can briefly stop you sending; it does not close your account. We do not make decisions that have legal or similarly significant effects on you based solely on automated processing.

5. Information that stays on your phone

Your message history is kept on your phone in an encrypted database, and your keys in your phone's secure storage.

Off-grid messaging. When nearby messaging is on, your phone exchanges encrypted messages and short-lived, rotating names with nearby Crowdpost phones over Bluetooth or local Wi-Fi. To find the way, it also shares with the phones right next to it a deliberately blurred summary of which rotating names it has heard recently. This summary has no names, account details, locations or times, is not passed further, and changes every day.

Carrying messages for others is your choice. You are asked when you first turn on nearby messaging, and can change it in Settings › Nearby & off-grid. If it is on, your phone may pass on and hold for up to 7 days other people's end-to-end encrypted messages, upload them when it has internet, and collect encrypted messages for someone nearby with no signal. Your phone can never read them. It holds less when your battery is low. Uploads for people you don't know use Wi-Fi; mobile data is used only if you choose a monthly limit (Off, 20, 50 or 200 MB). Messages to or from your friends may also use mobile data, up to 20 MB per friend and 100 MB in total each day, so your friends' messages get through. Your own messages do not count towards these limits. When your phone uploads a message for someone else, our server learns that your phone uploaded someone else's message that reached your phone (see section 4, "Messages you upload for others").

When a carried message reaches the internet. When a phone carrying someone else's encrypted message gets an internet connection, it uploads the message through a Crowdpost server function that only signed-in accounts can use, so our server learns which account uploaded it. The server checks the writer's signature and stores the message as from its writer, not from the phone that carried it. When the recipient's phone confirms it has the message, we record that it was delivered: the message ID, the writer's and the recipient's account IDs, and when. We also record which writer first used each message ID for a recipient. Both records are kept for 8 days, to stop the same message being delivered twice, let phones carrying copies stop, and prevent misuse. To stop misuse we also keep hourly counts of uploads by each helping account and of each writer's messages, deleted after 2 days. Our server's logs record the outcome of each upload and the reason (for example accepted, or dropped because of a block), but no account IDs. As with any request, our hosting provider's request logs may briefly show that a phone made an upload. The message stays end-to-end encrypted: neither the phone that carried it nor we can read it. Lawful bases: contract (delivering messages) and legitimate interests (preventing duplicates and misuse).

Writing to someone your phone has not met. When you send a message without internet to someone your phone has not been near recently, your phone may add the recipient's account, sealed so that only our server can read it. Phones that help carry the message cannot read it. When a phone near you fetches a message waiting for you, our server may add the sender's account, sealed so that only your phone can read it. We use these only to deliver the message and do not store them.

Nearby radar. You choose who can see you nearby: Nobody, Friends (the default: only your friends), or Everyone. With Everyone, anyone nearby with Crowdpost can see roughly how close you are and send you a message request. Everyone switches back to Friends after 3 hours. No map position is shown.

Private rooms tied to a place. The app checks on your phone whether you are inside the room's area; your location is not sent to us for this.

Chat backups. If you turn on backup, your chat history is encrypted on your phone before it leaves it. The encrypted file is saved in your own iCloud Drive (iPhone) or Google account backup (Android), and, if it is within our size limit, an encrypted copy is also stored on our servers (section 4). The key that opens it is kept in your own iCloud Keychain or Google account (Google Block Store), so a new phone of the same kind can restore it after you approve the sign-in. To move between iPhone and Android you use an optional recovery key that only you hold. Copies in your iCloud or Google account are held by Apple or Google under your own agreement with them, not on our behalf. Deleting your account in the app also removes the backup and its key from your iCloud or Google account, where your phone can reach them.

6. Who we share information with

We share information only with providers that process it for us under contract, and only as needed to run Crowdpost.

Provider What it does Information Where
Supabase Database, sign-in, file storage, server functions Everything in section 4 (encrypted content stays encrypted) European Union (Frankfurt, Germany)
Apple Push Notification service Alerts on iPhones Notification token, encrypted message, sender and conversation IDs United States
Google Firebase Cloud Messaging Alerts on Android phones Notification token, encrypted message, sender and conversation IDs United States
GatewayAPI Sends sign-in codes by text message Phone number and code European Union (Denmark)
MochaHost (World Host Group US Inc) Hosts our email: sends sign-in codes by email and delivers reports, logs and your emails to us Email address; report and log contents; emails you send us United States
Google STUN servers Help phones find a route for a call, only when our own call relay cannot be reached IP address United States and global
Cloudflare (R2) Serves Crowdpost's own map tiles IP address and the map area requested Global network
Microsoft Azure Hosts crowdpost.app and our call relay, which ZEOUR runs on a Microsoft Azure server IP address and pages requested (website logs); the call connection information in section 4 (call content is encrypted) United Kingdom (UK South)

Push notifications. To tell your phone that something has arrived, our server sends a notification through Apple Push Notification service (iPhone) or Google Firebase Cloud Messaging (Android). Crowdpost uses Firebase only for this: the app contains no other Firebase product, such as Analytics or Crashlytics, and on iPhone it does not use Firebase at all.

  • What they receive: your phone's push token; message, conversation and sender IDs; and, where it fits, the end-to-end encrypted message, which only your phone can unlock. They never receive readable message content or names. As part of delivering it, Apple or Google also sees that a notification was sent to your phone, and when.
  • Why: to deliver message, call and SOS alerts.
  • Lawful basis: contract.
  • Where: Apple and Google may process this in the United States. Safeguards: Apple uses the European Commission's standard contractual clauses; Google LLC is certified under the EU–US Data Privacy Framework and its UK Extension.

Map data © OpenStreetMap contributors. Your phone downloads map tiles from our own map server, not from OpenStreetMap.

QR code scanning happens on your phone; camera images are not sent anywhere.

We may also share information:

  • with the police or other authorities where the law requires it, or where we believe it is necessary to prevent death or serious harm. Because of end-to-end encryption we cannot provide the content of messages, calls or media. We can only provide the limited information in section 4 that we hold;
  • to report child sexual abuse material to the competent law-enforcement authorities, where we become aware of it;
  • with professional advisers and, if ZEOUR's business is sold or reorganised, with the new owner, who must keep this policy's protections.

International transfers. Data sent from the UK to the European Union is covered by UK adequacy regulations, and from the EU to the UK by the European Commission's adequacy decision. Where a provider handles data outside the UK and the EU, it is protected as follows:

  • Google (Android notifications, STUN): Google LLC is certified under the EU–US Data Privacy Framework and its UK Extension.
  • Apple (iPhone notifications): the European Commission's standard contractual clauses.
  • Cloudflare (map tiles): certified under the EU–US Data Privacy Framework and its UK Extension, with standard contractual clauses as a fallback.
  • Supabase: our data is stored in the EU (Frankfurt). Any access from outside the EU, for example by Supabase's support or sub-processors, is covered by standard contractual clauses in Supabase's data processing agreement.
  • MochaHost (email, United States): we are putting the European Commission's standard contractual clauses in place with them.

You can ask us for a copy of the safeguards.

7. Key transparency log

To protect you from impersonation, Crowdpost publishes users' public identity keys in an append-only log that anyone can check. An entry contains an opaque account ID and a public key, with no name, phone number or email. The log only works if entries are never changed, so entries remain after an account is deleted. Once your other records are deleted, they cannot be linked back to you. Lawful basis: legitimate interests (security).

8. Deleting your account

You can delete your account in Settings › Privacy & Security › Delete account. When you do, we delete your account, profile, recovery contacts, friends and requests, blocks, memberships, notification tokens, passkeys, messages waiting for delivery, reports you made, and your stored media and backups. Your phone erases its Crowdpost data.

We keep:

  • key log entries (section 7);
  • crash and app logs you chose to send, with the link to your account removed, for 90 days;
  • our call relay's log, which holds IP addresses and a coded tag rather than your account, and deletes itself within 8 days;
  • delivery records and records of who first used a message ID that contain your account ID, until they expire after 8 days, and hourly limit counters that contain it, until they expire after 2 days (section 5);
  • reports other people made about you, and our moderation records, for 12 months after the case is closed; bans are kept for 2 years, so we can keep people safe and stop banned accounts returning;
  • information we must keep by law, for example in response to a legal order.

Groups and rooms you created stay for their other members without your name. Messages you already sent stay on the phones of the people you sent them to.

9. Your rights

Under EU and UK data protection law you have the right to:

  • get a copy of your information;
  • correct it;
  • have it deleted;
  • receive it in a portable format;
  • restrict or object to our use of it, including where we rely on legitimate interests;
  • withdraw consent at any time (this does not affect what we did before).

Much of this you can do in the app. For anything else, email privacy@crowdpost.app. If you are in the EU, you can also make a request through our representative, Prighter: app.prighter.com/portal/16385989243. We reply within one month, or tell you if we need up to two more months for a complex request. We may ask you to confirm it is your account.

10. Complaints

If you are unhappy with how we handle your information, please tell us first at privacy@crowdpost.app. We will acknowledge your complaint within 30 days, look into it, and tell you the outcome without undue delay.

You can also complain to the data protection authority in the EU country where you live, work or think the problem happened: edpb.europa.eu/about-edpb/about-edpb/members_en. As we are a UK company, you can also complain to the UK Information Commissioner's Office: ico.org.uk/make-a-complaint.

11. Age

Crowdpost is only for people aged 18 or over. We do not knowingly collect information about children. If you believe someone under 18 is using Crowdpost, email safety@crowdpost.app and we will act on it, including closing the account.

12. Security

As well as end-to-end encryption, the database on your phone is encrypted, our servers check access rules for every user on every table, and sign-in uses passkeys or one-time codes. No system is perfectly secure. If a breach puts you at high risk, we will tell you and the regulator as the law requires.

13. The website

crowdpost.app uses no cookies, no analytics and no tracking. If you choose a language in the language bar, your browser remembers that choice on your own device (local storage); it is not sent to us. Our web server records basic request logs (IP address, page, time and browser type) to keep the site secure, kept for 7 days. Lawful basis: legitimate interests.

14. Changes to this policy

We will post changes here with a new date. If a change matters, we will tell you in the app before it takes effect.

15. Contact

ZEOUR LTD, 20-22 Wenlock Road, London, N1 7GU, England. Email: privacy@crowdpost.app. ICO registration number: ZC153409.

EU representative (GDPR Article 27): Prighter EU Rep GmbH, Schellinggasse 3/10, 1010 Vienna, Austria.