Windpost
Language: English

Legal

Privacy policy

Version 3.6 · 17 November 2026 · under legal review

A lawyer is still reviewing this page. It describes the app and our server as they are on the date above, and says so plainly where something is built but not yet in the app you can install. Where the review may change something, the text says so. If it changes what we keep or for how long, we will update this page and tell you in the app before the change takes effect.

1. Who we are

Windpost is a private messenger for families and the people closest to a family. It is made by Crowner Technology Inc., a Canadian company (“we”, “us”), which is responsible for the personal information described here.

Under review: the name of our privacy officer will be added here.

2. The short version

  • Everything you say, send or share in Windpost is end-to-end encrypted. Only the phones in the conversation can read it. We cannot.
  • Our server, which we call the relay, passes sealed messages between phones. It holds what it cannot read only until the phones it is for have it, and for 30 days at most for a phone that does not come back. Then it deletes it.
  • We do not ask for your name, phone number or email address. Names and pictures travel sealed, between phones.
  • The relay does keep some facts it needs to work: which accounts exist, who is connected to whom, who is in which family, and when things were sent. Section 4 lists every one, and how long it stays.
  • In the tester apps, for a one-to-one chat between two phones that both have it, the relay no longer knows who sent a message, only who it is for (sealed sender, section 4). Families and groups that move to the new encryption are known to the relay only by a random address: not who is in them.
  • Windpost can show that a call or a voice message really came from your family member’s own phone (PhysicLink, section 14). Faces and voices are judged on the phones and never reach us; a phone’s integrity evidence goes to our verification service and to Google or Apple.
  • No ads, no analytics, no tracking. We do not sell or share your information.
  • Windpost is for adults only. Nobody under 18 may have an account.
  • Windpost is not an emergency service. If someone is in danger, call your local emergency number.

3. What we cannot see

Your account is a key made on your phone. The relay knows it by a random number and its public keys, never the private key. Your messages, photos, videos, voice messages and documents are kept on your phone, in Windpost’s own sealed store, and on the phones of the people you sent them to.

Because of end-to-end encryption, we cannot see: what you write, say or send; the names of your contacts, families, groups, circles or albums; your name or profile picture; your location, including Help me and SOS; what is said or shown in a call; what is in your backup; faces, hello videos and voices; or anything in My documents, which never leaves your phone unless you send or export it.

The one exception is a report: if you report something, you choose to show it to us (section 9 and section 16).

4. What the relay holds, and for how long

The relay runs on servers we rent in Toronto, Canada. Its database holds the following, and nothing else.

WhatWhat exactlyHow long
Your accountA random account id and your public keys. When the account was made and last signed in. That it is for an adult. The release of Windpost it last signed in with (a number; see below). Its support code, ten characters shown in your About page, which you can read out to support. Your call settings, and whether notifications may say what is waiting (the kind of message; on Android also which chat and how many). Account status, when one applies: suspended by us (when, and why), a legal-hold mark (nothing of the account is deleted while a court order or similar requires it), a date for a deletion that has been asked for, and if we closed it after a report: when, and why. After an export for a court: whether you were told in the app, and when your app first showed the notice, or that the order did not allow us to tell you and why.While the account exists. Deleted with your account (section 10). An account that has not signed in for 24 months is deleted the same way, after one notification 30 days before; for that we also keep when the warning went, until the next sign-in. A closed account holds no keys or routes, and its record of when and why is deleted, with the account, one year after it was closed, unless a legal hold requires longer (then until the hold ends). The 24 months are under review.
One-time keysPublic keys your phone publishes so others can start a sealed conversation.Each is deleted when used.
ContactsFor each connection: the two account ids, when it was made, whether each side allows photos and documents, a block, an optional time limit, and whether a shared family made it.

For a contact whose two phones have moved to sealed sender (tester apps), the relay holds no record of the two of you together. Instead, each of you holds a permission the other gave: under your own account the relay keeps a random id and a public key for each permission you gave, and your settings for it (photos and documents allowed, blocked, a time limit, muted until), but not who holds it. A permission you gave for a “Send it to me safely” link is kept the same way, and so is one you gave a family that has moved to the new encryption, so that its posts can wake you.
Until either side disconnects, the time limit ends, or the two no longer share a family. A block is kept, so it stays permanent.

A permission: until you disconnect, or your phone ends the contact because its time limit is reached or the family that made it no longer joins you; at the latest, until your account is deleted. A block on it is kept, as above. A mute on it goes when its time runs out.
InvitationsThe code, who made it, when, when it expires, and who used it. A family invitation also holds a sealed preview whose key is in the link and never reaches us.

A code made by a tester app with sealed sender (22 characters): who made it, when, when it expires, how many times it may be used and how many times it was, a label you typed (60 characters at most), and a value derived from half the code (its hash). Not the code, and not who used it. A family’s code also holds the family’s preview, sealed under a key only the code carries. An answer to a code waits for its maker’s phone with no sender on it.
Until it expires (one to one: 24 hours unless you chose otherwise; family: 72 hours; an event code: the event’s close) or is taken back.
Families, groups and circlesThe id and kind of each family, group, event album or document collection, who made it and when; each circle’s keeping rule and key generation; for each member: account id, role, invited or in, who added them, when they joined, and the first key generation they may hold. No names. A co-host of a document collection sees only documents sent after joining.

A family or group that has moved to the new encryption (tester apps, once every member’s phone has a release with it): the relay keeps no member list, no roles and no names for it. Each family and each circle in it is known only by a random address, the number of its current key generation, the public half of that generation’s key and of the first one, and its sealed commits (the changes to who is in it, which only members can read). While it moves, the old rows (the family, its circles and members) stay until every member’s phone has read the last old post; then they are deleted. Event albums and document collections do not move: they stay as above.
While it exists. Your membership goes when you leave or are removed; guests leave an event album at its close. A note that someone was removed: 30 days; for an event album or document collection, or when an owner or admin chose “Don’t let … back in”, while it exists (or until that is lifted).

The old rows of a family that moved: deleted once nothing of it is waiting on the relay, and 30 days after the move at most. Commits: 45 days. A moved family’s address and key generation are kept until 400 days after the family’s last use (a post, a change or a read): they hold no account and no name, and for that period the relay writes only the day of the last use, never the time.
Family and group postsMessages, names, receipts, shared lists, locations, Help me and SOS, as sealed posts: the circle, the sender’s account id, one of four kinds (message, quiet, help, SOS, so the relay knows whether to ring), the key generation, the size and the time; the account ids a post names with an @; and which members’ phones have collected it. A post sent later is held sealed with its chosen time, at most 30 days ahead.

In a family or group that has moved: the sealed post with its key generation, size and time, a value for each member device that still has to collect it (made from a secret only members hold), and a hash of a secret only the poster’s devices hold, so they can take it back. No sender, no circle, no kind and no @ list: whether a post should ring is decided by each member’s own permission (muted or not) and a mention mark that names nobody. A post sent later: its time, at most 30 days ahead, and once it has been rung.
Deleted once every member’s phone has it, and after 30 days at most. Sooner in a circle set to disappear, for a live location when the share ends, and at once when its sender deletes it. Someone who joins later is given what is said from then on, and anything still waiting for another member’s phone; the history stays on the phones of those already there. In an event album, until 30 days after the event closes. In a document collection, while it exists, so that someone who sends documents later still sees what its collector said.
Shared files in families and groupsSealed photos, videos, voice messages and documents, up to 500 MB each, in sealed pieces: the circle, the uploader’s account id, the size, the time, and which members’ phones have collected it. A video also goes with one sealed still picture of it, made on the sender’s phone, so the family’s photo frame can show it before the video is fetched; it is held and deleted like the video.

In a moved family: the sealed pieces, the family’s address, the size, the time, and a value for each member device still to collect it; not the uploader.
Deleted once every member’s phone has it, and after 30 days at most. A copy re-sent for one member: 7 days at most. An unfinished upload: 1 day. Event album photos: 30 days after the event closes, as the album says; guests can no longer fetch them once it closes.
One-to-one messagesThe sealed message and a small sealed label, the contact it belongs to, sender and recipient ids, the number of pages, when it was sent and opened, how long each page was on screen, whether it is a photo or document, whether the sender let it be kept, and whether it was sent without sound. Only if the recipient turned on “say what is waiting”: one word (photo, voice, video or document). A message sent later: its chosen time, at most 30 days ahead.

Between two phones that have moved to sealed sender: the sealed message, its recipient and the permission it came in on, not the sender and not the contact; the other facts as above. The sender’s phones ask about it by a value only they hold (a hash of a secret), to see whether it was opened or to take it back. While both of you have the chat open, a room number that joins the two live pages, for as long as they are open.
Deleted the moment it is delivered, or when its window ends. It waits up to 30 days for a phone that is off (timed messages, and a view-once message from an older version of the app, up to 24 hours). The record that it was sent goes 6 hours after it closes; then only its name’s hash is kept a week (the next row).
Names of messages sentWhen the record that a one-to-one message was sent goes, a hash of the message’s name (a value made from it that cannot be turned back), and for a message sent with sealed sender its delivery number, so that if a phone sends the same message again because it never heard the answer, the message is recognised and not delivered twice. No account, no contact, no inbox and no time of sending; only when this note is due to go.7 days, then deleted. It names no account, so it is not deleted with one; it goes on its week.
Big files in one-to-one chatsDocuments and videos up to 500 MB, in sealed pieces of 4 MB: the contact, both account ids, the total size and each piece’s size, and when it was started, last added to and finished. A big file is not padded, so the relay sees its size. Its key travels only inside the sealed message that names it.

Between phones that have moved to sealed sender: the permission and a hash of the uploader’s secret instead of the contact and the two account ids.
Deleted when the recipient’s phone has it, or the sender deletes or stops it. An unfinished upload: 1 hour after its last piece. A finished file nobody fetched: 7 days.
Muted chatsFor each chat you muted: its id and until when. Nothing that was said. The relay writes iPhone notifications and rings Android phones, so it has to know. For a contact moved to sealed sender, the mute is a setting on the permission you gave (Contacts, above), not a chat id.Until you unmute, the time runs out, you leave, the contact ends, or the account is deleted.
Notification routesiPhone: Apple’s token for the app, and a second one if you turned on “Ring like a phone call”. Android: Google’s token, and a hashed secret for the phone’s own connection. The language notifications are written in. Whether this phone’s message notifications are off (the bell): then nothing goes through Apple or Google for a message, while calls, Help me, SOS, recovery warnings and new-device warnings still do. An iPhone’s public notification key (message previews, section 8): made on your iPhone, a new one every day, kept with that iPhone’s Apple route only while “Show messages in notifications” and message notifications are both on. The relay gives it only to your contacts and to the people in your families and groups of up to 16, so that those phones can seal a message’s first words to your iPhone; the key opens nothing on the relay.Until Apple or Google says the token is dead, or the account goes. The iPhone’s second token: until you turn “Ring like a phone call” off. Turning message notifications off deletes nothing; it changes the mark above. The public notification key: deleted with its Apple route, and when you turn “Show messages in notifications” or message notifications off.
Backups and recoveryNothing. Since 11 November 2026 the relay keeps no backups, no recovery code and no helpers’ pieces; what it held was deleted that day.See section 6.
ReportsThe one thing you chose to show us, encrypted with our own key; the reason; your account id and the reported one; which conversation or message; and when a legal demand needs it, the demand’s reference and the day it ended.30 days. Longer only if a legal demand names it, and then only until the demand ends and 90 days more; the admin page shows every such report until we have recorded that the demand has ended. A report outlives the deletion of either account for those 30 days.
Conversations on MLSOne-to-one chats use the MLS protocol once both phones run a release with it, with post-quantum keys (X-Wing). For that the relay holds public key packages your phone publishes, an address for each conversation’s group, and its sealed commits.

Once a contact has moved to sealed sender, its group’s address names neither of you, and a commit carries the sender’s device list only sealed inside the group.
A key package: deleted when used. Commits: 45 days. An idle group’s address: 90 days after its last use. Deleted with your account.
Linked devicesOnly if you link another device to your account (in the tester apps; not in the published apps yet): each device’s id, kind, public key and certificate, when it was added and the day it was last seen; the signed list of your account’s devices; a note that a device was removed; sealed mail between your own devices.

While you have more than one device, also: which of your devices have collected a message or a family post; which device opened a view-once message first; each linked device’s own notification route (Apple’s or Google’s token, its language, whether its message notifications are off); a linked iPad’s call token if it rings like a phone call; a “this wasn’t me” lock on new links; when a device was last added and which, so your other devices can warn you; and large sealed things your phone hands your new device (its history, kept media).
While the device is linked. A removal note: 30 days. Mail between your devices: 30 days. Deleted with your account.

The “this wasn’t me” lock: a day. The note of a device added: a day. History and media handed to a new device: 2 days at most, or until it has them.
Send tokensOnly with sealed sender (tester apps). A message sent this way is paid for with a token your phone was given earlier, blinded, so the relay cannot tell which account it gave it to. The relay keeps one public token key per kind per day (the same for everybody, also published in the key log, section 14) with its private half sealed under the relay’s own secret, and for each token spent a hash of its number and nothing else: no time, no account, no message. How many tokens an account asked for this hour is counted in memory for rate limits, as before.A token key: its day, and a day and an hour more (a token can still be spent in the first hour after its day). A spent token’s hash: until its key can no longer be spent, an hour after its day ends (25 hours at most). A token key’s public half stays in the key log (section 14).
PurchasesWindpost charges nothing today, so no store receipts are kept.—

What the relay does not hold: your name, phone number, email address, contact list, location, internet address, or any history of who talked to whom once the records above are gone. The front door of our server keeps no access log. Our host, Vultr, may see network traffic at its own level.

Every request also says which release of Windpost made it: a number, the same for everyone on that release, so the relay can ask a phone to update before an older release stops working. The release your phone last signed in with is written on your account, as the table says, so we can see which releases are in use and answer a support question about it.

When a phone cannot check the day’s token key against the key log (a moment after the app starts, or if the check fails), it does not use a token it cannot trust: it sends that one message, or makes that one read, signed in as itself, so the relay knows who sent that message, as before sealed sender. Nothing is kept of it beyond what the table says for any message. An answer to a code, its maker’s reply, and the opening of a pass are never sent this way; they wait.

Only in memory, never written down

  • Online now, the green dot while Windpost is on your screen: seen only by people you share a contact or family with, for 75 seconds after your app last said so. Turn off “Show when I’m online” and your phone stops saying it.
  • In this chat, and “writing…”: while you and a contact both have your chat open, the relay knows, in memory, that the two of you are in that chat together right now. That is a fact about who talks to whom, and we accept it so that a conversation can feel live; it lasts 45 seconds after your phone’s last word (“writing”, 8 seconds) and leaves no history. “Show when I’m online” turned off turns this off too.
  • Calls: who is calling whom, while it rings or lasts; a declined call for 1 minute; a missed call for 6 hours, so a phone that was off can show it. A call stays open on the relay through up to 80 seconds in which neither phone is heard from, so that a call can survive both phones losing their connection for a moment. If the relay restarts during a call, the two phones of that call can make it live there again; it is still held only in memory, and nothing more is kept.
  • Sign-in sessions, up to 12 hours; and how many things an account did this hour, for rate limits.
  • Read passes (sealed sender, tester apps): a phone asking anonymously what became of a message, or reading a family’s or a contact’s box, opens a pass with one token and shows it with each read; the relay counts reads per pass in memory, so it learns only that the reads under one pass came from one phone. A pass lasts an hour at most, and a restart forgets every pass.

Timing

The relay sees when things are sent and when they are collected. Even where it is not told who wrote to whom, someone who watched the relay could match the moment a message goes in with the moment it comes out. We accept this, as every messenger that passes messages through a server must, and we keep no record of it.

5. Location, Help me and SOS

Windpost reads your location only when you tap to send it: share where you are (once, or live for a time you choose while the app is open), Help me and SOS. Never in the background, never on a timer you did not start, and nobody can turn it on for you. It is sealed on your phone; the relay sees a sealed post and cannot tell it is a location. The relay knows a post is urgent (“help” or “sos”) so it can ring through Do Not Disturb, and limits each person to three SOS alerts an hour. On an iPhone, SOS and Help me ring with their own alarm sound. On Android, they sound through Do Not Disturb only if you give Windpost “Do Not Disturb access” in Android’s settings (section 7); messages and calls still follow Do Not Disturb, and Windpost never changes your Do Not Disturb settings. Park my car stays on your phone unless you share it.

Windpost does not call emergency services. If someone is in danger, call your local emergency number.

6. Backups

Your backups are your own files. Windpost writes them on your phone, into a folder you choose (on the phone, or a cloud drive you use), and seals each one with a password you choose; without it nobody can open the file, not us and not whoever stores it. You choose what goes in: your contacts, families and groups, your chat history, and photos, videos and documents. Windpost makes one when you ask and, if you turn it on, once a day; each new one replaces the last in that folder. Nothing of it is ever sent to our relay.

A backup brings your account back after the app was removed or on a new phone. After you delete your account it brings your history back to read, and the people to invite again; contacts and families end with the account. If you ask for a readable copy as well, it is not protected by your password: anyone who has that file can read it. You can also send a backup by email; the file stays sealed with your password.

The relay used to keep one sealed backup and a recovery code’s values; since 11 November 2026 it keeps neither, and what it held was deleted. Windpost’s store is kept out of iCloud and Android backups on purpose.

7. Things that stay on your phone

  • My documents: sealed on your phone only, opened with your phone’s fingerprint, face or screen lock (we never receive these), never on the relay and never in a backup. If you lose your phone, you lose the folder.
  • Your contacts’ names, your profile, settings, chats and calls list.
  • Scan, sign and video effects all work on the phone. A sealed signature uses a key made on your phone; we do not see the document or check who you are.
  • Export and Send to computer make copies that are not sealed: anyone who gets the file can open it, and the screen says so first. A chat’s export leaves out view-once messages and anything its sender did not let you keep.
  • Delete for everyone asks the other phones to delete a message. A copy already saved, exported or photographed is not reached.
  • Sharing into Windpost, on Android and iPhone: a photograph, video, file, link or text you share to Windpost from another app is copied into Windpost’s own space on your phone and sent, sealed, as an ordinary message, only to the person you choose, once you tap Send. Windpost reads only what you share. On an iPhone (once a coming release switches it on), Windpost’s share panel keeps what you shared in Windpost’s own protected space on the phone, out of backups, until you open Windpost; nothing is sent until you pick who gets it and tap Send, Windpost then sends it when you open it, and anything left there is removed after a day. On an iPhone, so that Share → Windpost can ask who should get a photo, Windpost keeps a small list of your chats (the names you gave them and small profile photos) in its own protected storage on the phone, which never leaves the phone and is not made while Lock Windpost is on.
  • Framing photographs: to keep people’s heads in a family’s photo frame, your phone finds where faces are in a photograph, on the phone only. It does not recognise anyone, and nothing about a face is kept, sent or reaches us; only where to place the picture is kept, in the phone’s memory.
  • Sending in the background on an iPhone: iOS may wake Windpost for a short while to send messages you wrote while offline. Nothing new is collected.

Windpost asks for the camera, microphone, photos, location while in use, notifications, local network on iPhone (Send to computer) and your phone’s fingerprint or face check, each when first needed. On Android you may also give Windpost “Do Not Disturb access”: it is optional, you give it yourself in Android’s settings, and Windpost uses it only so that SOS and Help me sound through Do Not Disturb; it never changes your Do Not Disturb settings. You can turn any of them off in your phone’s settings.

8. Other companies involved

WhoWhat forWhat they get
VultrRents us the relay and our two call forwarders in Toronto, with encrypted disks, and stores the nightly copy described belowThe machines; everything on them is sealed or listed in section 4. Vultr is a US company.
AppleApp Store, TestFlight and iPhone notificationsA fixed sentence with no name and no content, such as “New message” (one more word, such as “New photograph”, only if you turned on “say what is waiting”), and a call wake-up if you turned on “Ring like a phone call”. Nothing for a message while that iPhone’s message notifications are off. Calls do not go into your iPhone’s Recents. With message previews (below), a message’s notification also carries one sealed preview, which only your iPhone can open, and a random number for that message, which means nothing outside our relay.
GoogleGoogle Play and Android notificationsAn empty wake-up with one letter. Android phones keep their own connection to the relay, and Google is asked only when it is not open, or for calls, Help me, SOS and recovery warnings, and never for a message while that phone’s message notifications are off. If you turned on “say what is waiting”, your phone is told how many messages wait in each chat over its own connection, never through Google, and names each chat from the names it keeps itself; a lock screen set to hide what notifications say shows no name. Google’s service may give the app an installation identifier. Google Play Integrity: for PhysicLink, an integrity token (section 14) that our verification service sends to Google to decode, with no account, name or content attached.
Apple App AttestApp Attest, for PhysicLinkYour iPhone’s App Attest key registration and checks (section 14), through Apple’s service; our verification service checks the result and keeps nothing.
VercelHosts this website and the invitation link pagesOrdinary web requests, which it may log under its own policy; we add no analytics. The invitation preview key is in the part of a link browsers never send.
NamecheapOur domain names and email forwardingEmails you send to our addresses

Apple and Google learn that our relay woke a device, and when. They do not learn who wrote, what was written, or which conversation it was. For a message sent without sound nothing goes through them, and for a chat you muted nothing does except calls, Help me, SOS and posts that name you. Call forwarders are our own: they carry encrypted call audio and video so neither phone learns the other’s internet address, and keep no log of who called whom.

With “Show messages in notifications” on (the default; Sounds and notifications), a notification can show who wrote and what the message says. Our relay, Apple and Google never see those words. When Windpost is running, it takes them from messages it has already opened on your phone. On Android, when a message arrives while Windpost is closed, Windpost opens it for a moment in the background, on your phone, so that its notification can show the words; it does not do this while Lock Windpost is on or “Show messages in notifications” is off, and nothing more is sent anywhere. The words stay in your phone’s own list of notifications for as long as the notification is shown, and your lock screen shows them only if your phone is set to show notification content there. On an iPhone, the words now show even when Windpost is closed, through the message previews below. View-once messages and messages not to be kept only ever say “Message”.

With Lock Windpost on, notifications say only who wrote, such as “Ege · New message”, and never what a message says. You can turn this off under Lock Windpost (“Hide message words in notifications”). Chats in Locked chats never show words.

Message previews on an iPhone. While “Show messages in notifications” and your message notifications are on, your iPhone makes a key that is used for nothing but notifications, and makes a new one every day. The private half stays in your iPhone’s keychain and never leaves the phone. The public half goes to our relay with your iPhone’s Apple notification route. When one of your contacts, or someone in a family or group of up to 16 people you are in, sends you a message, the sender’s phone uses that key to seal a short preview: the first words of the message (or “Photo”, “Voice message” and the like), with no names. The sender’s phone also signs the preview with the key that proves who sent it, inside the sealed part, so your iPhone shows the words only if they really came from that contact. A preview that is not signed, or not signed by that contact, shows only “New message”. For a contact whose messages travel without naming the sender (sealed sender), the sender’s phone asks for your notification keys the same anonymous way it delivers the message, so asking reveals nothing more than the delivery itself. Our relay passes the sealed preview to Apple inside the notification and keeps nothing of it; it cannot open it, and neither can Apple. For each such message Apple sees one sealed preview and a random number for the message. Windpost’s notification part on your iPhone opens the preview on the phone and shows the words under the name your phone gave the chat, never a name the sender chose. Chats you keep in Locked chats never show words, and if anything fails (an older app on the sender’s phone, for example) the notification says “New message”, as before. With Lock Windpost on, these words are hidden too (above). Turning off “Show messages in notifications” also hides them. Turning that switch or your message notifications off deletes the key on your iPhone, and then on the relay.

We use no analytics, no advertising, no crash reporting service, no tracking and no data brokers.

A nightly copy of the relay’s database is encrypted on the relay with a key only we hold and kept for fourteen days in Vultr’s storage in New Jersey, United States; Vultr cannot open it. It holds the records in section 4, but no message: not one-to-one messages or files, and no family or group posts or files. A post deleted from the relay is gone; no copy of it waits in the backup.

9. Reports, blocking and the law

Block ends the connection on the relay (for a contact moved to sealed sender: your permission for that contact is marked blocked, so what it sends is accepted and dropped) and deletes the conversation on your phone. The other person is not told.

Report sends us one thing you saw, with a short reason. It is the only time we can read content, and only because you chose to show it. We keep it encrypted for 30 days, or, if a legal demand names it, until that demand ends and 90 days more. If it shows the sexual exploitation of a child, the law requires us to report it to Cybertip.ca and the US National Center for Missing & Exploited Children, with the report and the account ids. A fuller way to complain, with evidence, is described in section 16.

A report of a one-to-one message from a contact moved to sealed sender, or of a post in a family that has moved to the new encryption, carries the proof that came with it inside the encryption: your phone hands over that one message’s key, the message as it arrived, its sender’s signature and the sender’s device certificate. The relay checks them against the account’s public key and opens that one message itself, so the report records which account wrote it as a checked fact. Where your phone holds no such proof, the report is your word and the page you chose to show, as before. The relay still cannot see who sent any message that is not reported.

We answer valid legal process, sent to legal@windpost.app, and nothing without it, except where the law allows disclosure to prevent imminent harm to someone’s life. What we could hand over is only what section 4 lists on that day. For contacts moved to sealed sender and families moved to the new encryption we cannot say who sent which message, who is in a family, or who is whose contact: the relay does not hold it. What we could not, because we do not have it: the content of any message, call, photo, document or location; names; phone numbers; email addresses; contact lists; internet address logs; call history; presence history. A court can order us to preserve what we hold (a legal hold: nothing of that account is deleted until the order ends); it cannot make us produce what we never had. Our operators’ actions are recorded (section 15), and an export for a court is made from the admin page, is logged, and contains only what section 4 holds about that one account. After we give a court what we hold about an account, we tell the account holder in the app, unless the order or the law forbids it; then we record why, and tell the account holder once it no longer does. How we handle foreign requests is under review.

10. Deleting

  • Leave a family or group: your membership is deleted at once.
  • Disconnect or block a contact: the connection and anything waiting is deleted.
  • Delete a message or post you sent, for everyone.
  • Turn off “Ring like a phone call” on an iPhone: its call token is deleted. Turning message notifications off deletes no token: the relay keeps the routes, marked, so calls, Help me and SOS still reach you. Your backups are files you keep and delete yourself.
  • Delete everything (Settings) leaves every family, group and album properly, deletes the account on the relay with everything keyed to it (keys, memberships, the posts and files it still has there, the backup, the recovery code record, the helpers list and notification routes), then wipes the phone.
  • Or write to support@windpost.app. Because we hold no name or email, we will ask you to prove the account is yours, usually from the app.
  • If a court order or similar requires us to keep an account (a legal hold, section 9), deleting it closes it at once: it can do nothing and nothing reaches it, and its records are kept until the hold ends, then deleted. Windpost says “Your account is closed” whenever you delete your account, so the words themselves never tell you whether a hold exists.

What other people keep. What you send is kept on the phones of the people you sent it to, as in any messenger, and can be exported from there, except anything you did not allow to be kept, and a view-once message (only an older version of the app sends one; phones running an older version of the app may not know to leave these out). Posts you made in a family stay on the other members’ phones after you leave or delete your account. An admin can hide a photo from an album but never delete what someone else sent.

11. Adults only

Windpost is for people 18 and over. The app asks once, before it makes an account, and someone under 18 cannot continue. We do not allow child accounts; children may appear in photos adults share, but never hold an account. If we learn an account belongs to someone under 18, we close it: tell us at support@windpost.app.

12. Your rights

Wherever you live, you can ask us what we hold about your account, ask us to correct or delete it, withdraw consent, and complain to us. We answer within 30 days and do not charge you. We make no automated decisions about you.

Canada (PIPEDA; Quebec’s Law 25): you may complain to the Office of the Privacy Commissioner of Canada, or in Quebec to the Commission d’accès à l’information. European Union and United Kingdom (GDPR, UK GDPR): you may also restrict, object to and port your data, and complain to your data protection authority (in the UK, the ICO). We rely on contract to run the service you asked for, legitimate interests to keep it secure and free of abuse, consent for location you send, “say what is waiting” and online status, and legal obligation for child-safety reports and lawful orders. United States: we do not sell or share personal information or use it for targeted advertising, and will not treat you differently for asking about it.

Windpost is offered worldwide, except Russia, Belarus, France, the United Arab Emirates, Oman, Qatar and the countries under United States embargo (today Cuba, Iran, North Korea and Syria). Your information is handled in Canada and the United States: our servers are in Canada, and the nightly copy is in the United States (section 8). The list of countries, our representatives in the EU and the UK, transfer safeguards, and what Turkey’s KVKK requires are under review.

13. Security

  • End-to-end encryption. One-to-one chats use MLS with post-quantum keys (X-Wing, which combines X25519 with ML-KEM-768) once both phones run a release with it; families and groups use MLS with post-quantum keys too, once every member’s phone has a release with it (until then, and on older releases, vodozemac: Olm and Megolm: Curve25519, Ed25519, AES-256 and HMAC-SHA-256). Keys are made and kept on your phone; on iPhone, in the Keychain on this device only.
  • Calls are end-to-end encrypted, with post-quantum keys where both phones support them.
  • In the tester apps, the connection between the app and the relay uses post-quantum TLS (X25519MLKEM768) where the phone’s own system offers it: on Android through the app’s own Conscrypt, on iPhone from iOS 26. Older iPhones and the Windows app use classical TLS (X25519).
  • The store on the phone is sealed and kept out of cloud backups. Our disks are encrypted, and reports are encrypted with a key kept apart from the database.
  • Calls always pass through our forwarders, so the other phone never learns your internet address.
  • A public key log (section 14): every account’s public keys are published in a log anyone can check, so the relay cannot quietly swap a key.
  • In the tester apps, not in the published apps yet: sealed sender, which stops the relay knowing who sent each one-to-one message: a connection becomes a permission each of you gives the other, kept under your own account with your settings for it (photos allowed, blocked, a time limit, muted) but not who holds it, and a message names only who it is for. It adds to the relay: permission keys, spent-token records and the relay’s token keys (section 4). Families and groups on MLS, which keep their member lists off the relay, are in the tester apps too (section 4). So are linked devices: another device on your account, such as a tablet, with its own keys (section 4).
  • The sender’s signature: in the tester apps, every new message and every family or group post carries its sender’s signature, sealed inside the end-to-end encryption, so a message you received can be shown to prove which account wrote it. The relay cannot see the signature and still cannot read messages; it reaches us only if you hand a message over in a complaint (section 16). Some carry no signature and stay the reporter’s word: an edited message, a big file, a photo or document sent together with the sender’s own original file, a document of several pages, anything sent from a linked device, and anything sent before the sender’s phone had this.

The relay has not yet had an independent security review, and nor has the new encryption in the tester apps described above: it is in the tester apps on our own testing. No system is perfect: if a breach affects you, we will tell you and the regulators as the law requires.

14. PhysicLink, the key log, and what they send where

PhysicLink is how Windpost shows that a call, a hello or a voice message came, live, from your family member’s own phone. It is on by default in the apps that have it, and you can turn it off in the app’s Calls settings.

  • Faces and voices are judged on the phones and never reach us. The hello video goes between the two phones of the people involved, end to end encrypted, like any message; the relay holds the sealed page until it is closed, then deletes it. When two people connect with an invitation, each can at once send the other messages, photographs, videos, voice messages and documents, and can call; there is no separate permission step. Either person can disconnect or block the other at any time. Either of you can ask the other “Is it you?” at any time: the answer is a 5-second live video, recorded only after a tap on that screen and checked on the asking phone. When the check passes fully, nobody sees the video and it is deleted. When it is only partly checked (as on many Android phones), the video is shown once to the person who asked, on that phone only, so that person can confirm it is really the other person; it is then deleted. The relay holds it sealed until it is opened, then deletes it. Any check on a face or a voice, in a hello, a Check or a call, happens on the phones, and what it keeps stays on that phone.
  • Your phone’s check: to check that a phone is the phone it says it is and has not been tampered with, it sends evidence, sealed so that the relay cannot read it, through the relay to our verification service: on Android, a Play Integrity token and a hardware attestation of its key; on iPhone, Apple’s App Attest evidence. The service signs a verdict the phones check themselves. It keeps nothing: no table of keys, no record of who asked; it writes one log line per request, with no account, key or address (the method, a short path, the status), kept 7 days. To decode an Android token it asks Google; an iPhone’s check goes through Apple. Neither is given your account or any content.
  • On a call, signed proofs and the checks that show a live, real call travel inside the end-to-end encrypted call between the phones, not through us as anything we can read.
  • A device key is made in your phone’s secure chip and used only after a fingerprint or face unlock. Its public half is shared with the people you are connected to.
  • Our systems see only the count of requests to the verification service, kept in memory; whether a badge showed green, grey or red is decided on the phones and never reaches us.

The key log is a public record of each account’s public keys and the list of its devices, kept so that anyone can check later that the relay never swapped a key. It lives in its own database on our relay, in Toronto, and a signed summary of it is published every hour (the part anyone can download holds no account information). It holds no names, no messages and no content. It is append-only: an entry in it is kept for as long as the log exists, including after an account is deleted; a closed account gets a closing entry, and only public keys and their history remain.

15. The admin page and its log

Our operators run Windpost from a private page at admin.windpost.app. Signing in needs a passkey (a device’s fingerprint or face check, never a password), and every sign-in and failed sign-in sends an alert to the owner.

What an operator can see: counts of accounts and activity across the service, including hourly counts of failed sign-ins and refused connections, with no address and no account (kept in memory for two days at most); for one account: its id, support code, when it was made and last seen, the release it last used, its status (section 4), its devices and when they were added, counts of its contacts and families that the relay still knows (contacts and families that have moved to the new encryption are not counted, because the relay does not know them), reports made by or about it, and the lines of the log about it. What an operator can do to one account: suspend it (it cannot sign in or send) or restore it, sign it out everywhere, cancel its open invitation links, read what a report chose to show us, place or lift a legal hold, close it for abuse, delete it on request, and make an export for a court (only with a court’s reference and a reason, and the export is signed and logged), then tell the account holder in the app or record why the order forbids it (section 9). What an operator can do across the service: show a notice to everyone, set the minimum release, turn verification off for everyone, change the call servers, freeze an Announcements or Channel space (no posts and no joins, its members are told it is paused, nothing in it is read or deleted), and cancel a space’s invitation links. Changing the call servers, deleting an account at once, closing an account and reading what a report showed each need a fresh passkey touch for that one action.

What an operator can never see or do: read a message, a call, a photo or a document; see contacts’ names, who talks to whom beyond the counts above, faces, hellos, voices or locations; or sign in as you.

The log. Every operator action is written to a log: when, which operator, what was done, which account id (if any) and a short detail. The lines are chained by hash, so a line changed afterwards shows; the newest line’s number and short hash go in every alert to the owner and in the nightly copy’s manifest, so lines removed from the end show too.

How long. A line about an account is kept for the account’s life and one year after it ends (whether the account was deleted or closed), unless a legal hold on that account requires longer. Then the line’s words are removed; its number, its time and its hash stay, so that the chain can still be checked. Lines that name no account (an operator signing in, a change to the whole service) hold nothing about you and are kept. Under review.

16. Complaints: built, not switched on yet

This section describes a fuller way to complain. Our server has its part of it, but it is switched off and no phone can use it yet. Until it is switched on and reaches your phone, the Report in section 9 is what exists. We are describing it now so that you know what it will hold when it comes; we will update this page and say so in the app before it does.

When you use it, a complaint will hold, and only for the case:

  • The complete messages you choose to report, of every type: text, photo, video, voice message or document, as you received them, sealed to a key only our case-handling side holds. Nothing you did not choose is sent; every other message stays end-to-end encrypted.
  • Both accounts’ Windpost IDs (a short code from each account, shown to its owner), the case number, the category you chose, your statement and the date.
  • Fingerprints of the evidence (SHA-256), so your copy and the case can be shown to match, and where the sender’s signature can be checked (section 13), whether it did.
  • Who viewed what and when: every look at the evidence is logged.
  • The decisions taken on the case, and if an account was held, why, and the appeal.

A secure link for courts and lawyers, only with your approval on your own phone by fingerprint or Face ID: your phone shows what will be shared and with whom, you approve it, and the link opens a page with the report and the evidence. It expires, needs a separate access code, can be revoked by you or by us, and logs every opening.

A binding court order does not need your approval: if you cannot or will not approve, we may release what the order requires, and the case records the order. Child-safety reports go to Cybertip.ca and the US National Center for Missing & Exploited Children, through their own channels, never through a link. A person reported is not told who reported.

How long: a case and its evidence are kept until the case closes and 1 year, longer only under a legal demand (until the demand ends and 90 days; section 9).

17. Announcements and Channels: in the iPhone tester version

Announcements and Channels are in the version of Windpost that public testers can install on iPhone. They are not in the Android version yet. This section says what they hold, so that nothing changes without being written here first.

If you use them, the relay also holds:

  • A request to join: your account id and when you asked. A request nobody answers goes after 30 days at most. A refused request goes at once, and the relay remembers that it was refused for a month, so the same link cannot be used to ask again.
  • Your name card and join key: your name, sealed so that we cannot read it, and for a channel the public key your phone made for it. They are held for your whole membership, not only until an admin answers, because the admins’ list of members shows the name and the channel’s key is sealed to that key. They go when you leave, are removed, or delete your account.
  • Seen counts: how far each member’s phone has opened it. Only a number is shown, only to the admins, never who. Held while you are a member.
  • Your alert switch: whether you turned alerts on. Held while you are a member.
  • A key box for a channel: its key, sealed separately to each member, unreadable to us. Held while you are a member; the key of a generation that has moved on goes after 30 days.
  • An admin box: private replies to the admins and their answers, sealed, unreadable to us. 30 days.
  • Mute and slow mode: a mute an admin set on a member, until its time runs out; the slow-mode gap and the rule for who may add people, while the space exists.
  • Removal notes: that an admin removed someone from the space. Kept while the space exists, unless an admin later invites that person back by a link made for them alone, or the account is deleted.
  • Leave and block: that you chose it, so that no invitation from that space reaches you again. Kept until you delete your account or the space itself is gone.
  • A channel’s daily byte count: one number per channel per day, how much it sent out, with no account in it, so that a channel can be limited. Kept for about 3 days.

Photos and files posted here stay on the relay, sealed, for 30 days, so that someone who joins later can open them. Channel members cannot see each other, and channels are by invitation only, never listed or searchable. Reports (section 9) will name the channel so that we can act on it, and a channel can be frozen.

18. Changes

If we change what we collect or how long we keep it, we will update this page, give it a new version number and date, and tell you in the app before the change takes effect.