Privacy Policy
Last updated: November 16, 2026
Whispurr is a private, local-first communication and shared-memory app built and operated by WhispurrApp, LLC ("Whispurr", "we", "us", or "our"). Whispurr does not collect data from your use of the app. Your content stays on your devices and syncs directly with the devices you authorize. If you choose to enable an optional cloud service, its provider processes limited encrypted content and service metadata as described below. Contact cards and chat invites use a small, free inbox at the same provider that holds only end-to-end encrypted chat requests (section 2.7a). Whispurr does not receive your readable conversations or media.
We built Whispurr because private relationship data deserves to be treated with extraordinary care. Our guiding principle is simple: your conversations and memories stay encrypted on authorized devices and sync peer-to-peer with the devices you choose.
1. What we don't do
- You can use the core app without an email or password. If you enable an optional cloud service, its provider keeps records needed to run that service, such as account IDs, access permissions, and stored resources. These records may use IDs instead of your name, but the provider may still be able to link them to your account.
- We do not sell your data.
- We do not use third-party advertising or tracking SDKs.
- We do not use analytics services to profile your behavior.
- We do not share your data with data brokers.
- By default, records, messages, and media remain encrypted on your devices and paired devices. Optional cloud services retain only the end-to-end encrypted ciphertext you explicitly authorize for Courier. Contact-card inboxes hold only end-to-end encrypted chat requests addressed to your cards (section 2.7a).
2. How Whispurr stores and syncs your data
2.1 Cryptographic identity, without email sign-in
Whispurr's core app does not require an email, password, or username. The first time you open the app, it generates your account's keys on your device and, separately, a 24-word recovery phrase. The phrase is not your account key and not a copy of your chats: it lets you restore the account from one of your backup devices (section 2.6), which asks you to approve the restore first. Only the device that created the phrase, or the one where you last typed it, can show it. You can make a new phrase at any time, and the old one then stops working; your other devices tell you when that happens, and a backup device asked to restore with a replaced phrase answers only that it was replaced. Linking another device never shares the phrase. We never receive your phrase or plaintext conversation keys.
2.2 Nearby Bluetooth discovery and invitations
When you open Nearby Users, your selected persona's name, color, and a small avatar preview are broadcast over Bluetooth to nearby devices. Public profile sharing stops when you close that view or put the app in the background. Nearby invitations use encrypted messages between temporary sessions; accepting an invitation creates an ordinary encrypted chat.
While that view is open, Whispurr also reads your device's motion sensors on the device to recognise when you bump phones with someone. Raw motion data never leaves your device. When a bump is felt, only a short signature of it (its timing, strength, and shape) is sent, encrypted, to the nearby Whispurr users in that session, so the two phones that bumped can recognise each other. Motion readings are not stored, and the sensors stop when you close the view.
2.3 Records (events, plans, activity logs, stories, profiles)
Records are stored in encrypted documents on your device. Each conversation's records are encrypted with AES-256-GCM under a key that only its members' devices hold, and every change is signed by the device that made it. Changes sync directly between those devices. If you explicitly enable Courier, its provider may temporarily retain encrypted changes so an offline member can receive them later; the encryption key never leaves members' devices.
Route files (GPX) you import are read on your device and saved as a route or course in the chat you choose; the file is not uploaded anywhere else. Stories are records in a chat: making one can post the photos it uses to that chat. Marking a chat as sensitive is a setting only your own devices know: it hides that chat's messages from the chat list and notifications on your devices, and other members are not told. Your persona's name, picture and colour are shared with the members of each chat that persona is in; its Context label stays on your own devices.
2.4 Photos, videos, and other media
Photos and videos are encrypted on your device with AES-256-GCM and stored as content-addressed blobs. Each item is encrypted under its own random key, which is kept only inside the encrypted conversation, so only its members' devices can decrypt it. Thumbnails, link-preview images, map snapshots, and chat and profile pictures are stored the same way, as encrypted blobs rather than inside messages. The hash advertised to the network is the hash of the ciphertext. Bytes replicate peer-to-peer by default. If you explicitly enable Courier, Courier may temporarily store an encrypted copy so a member who is offline can download it later.
2.5 Messages in your chats
Chat messages flow through the same encrypted conversation as your shared records. Message changes are encrypted end-to-end and signed by the device that wrote them. Whispurr does not use any third-party chat backend.
When you paste a web link into a message, your device loads that page once to build a preview (its title and a small image) and sends the preview with the message as an encrypted attachment. The website sees an ordinary request from your device; the people you chat with never contact it to display the preview. You can turn this off under Device Settings → Chats → Generate link previews, and no preview is loaded while Hide IP Address is on (section 2.11).
When you add a reaction by scanning its QR code or pasting its link, your device downloads the reaction from the website the link names. That website sees an ordinary request from your device, including its IP address, and is told nothing about you, your personas, or your chats. Whispurr asks you before it contacts any website other than whispurr.app. While Hide IP Address is on (section 2.11), your device does not contact the website: it asks our server at whispurr.app to download the reaction instead. Our server sees the link and your IP address, uses the link only to fetch the file, and does not store it; the website sees a request from our server, not from your device. A reaction image you use in a chat is stored and sent like other chat media: encrypted, and the people you chat with receive it from your devices and each other, never from the website.
2.5a Activity routes and location
Whispurr uses your device's location only for routes you choose to record, and when you tap Use Current Location to pick a place or add a privacy zone. Nothing about your location is collected by us or shared automatically.
- Location access is requested "While Using the App". When you open the route recorder, the map shows where you are; recording starts only when you press Start, and location stops when you pause, finish, or close the recorder. If a recording continues while the app is in the background, iOS shows its location indicator. The compass on the recording map uses your device's heading only while that screen is open and is not saved.
- Until you finish, the recorded track stays on your device, encrypted with AES-256-GCM using a key derived from your account. It is deleted once the route is saved, or when you discard it.
- Recording in a chat. A route is recorded in a chat, and members of that chat can tell a
recording is under way even when you are not sharing it live:
- Once your route has left every privacy zone, the chat shows an event for it, with a title, the time of your first point outside the zones, and that you are recording. It shows no location. Nothing appears while you are still inside a zone.
- Members of a chat ride together. If another member's ride is already under way in the chat when yours appears, your recording joins theirs instead of getting its own event, and others can join yours the same way. Everyone on a ride is listed on its event, and their messages share one thread.
- Messages, photos, files and voice clips you add while recording are sent to that event's thread when you add them, end-to-end encrypted like any other message (section 2.4). Ones you add before the event appears wait on your device, and are then sent marked with the event's start time, not the time you added them.
- Discarding a recording removes the messages it sent, and the event if nothing else was said in its thread. Members' devices remove them the next time they sync.
- Privacy zones. You can mark places such as home or work. Before a route is shared, every point inside a zone, and any line passing through one, is removed, and the distance, times, and preview image are calculated only from what remains. Zones are kept in your encrypted account data and sync only to your own devices. A gap in a shared route can still show that you paused somewhere nearby.
- The route itself is shared only when you finish and save it: to its event, to the thread of a ride another member started, or to your entry on another member's event in the chat. It travels end-to-end encrypted like other media (section 2.4), and members of that chat can see where and when it was recorded. If you trim a route, the trimmed copy replaces the shared one.
- Live sharing. When you record in a chat with other members, the Start screen shows a
"Share My Position" switch. It is on the first time you record in that chat, so that riders see each other; if
you turn it off, that choice is remembered for the chat. Joining a ride that is already shared live turns it on.
You can turn it off at any time while recording. Recording in a chat with only yourself is never shared live.
While it is on:
- Members of that chat see your route and current position as you record. Other members can join your ride and share theirs the same way, and everyone on the ride sees each other.
- Points are end-to-end encrypted and travel between chat members' devices, directly or through a relay server (section 2.11). Nothing is sent while nobody in the chat is watching. Points are never stored in the chat or on any server; a member's device holds them only while showing them, but anyone watching sees them.
- The chat keeps the ride's event (its title and start time, and an activity if one was added) and each rider's status (live, paused, finished), but no location. A notification tells members that a ride started.
- Privacy zones apply as they do to a saved route: nothing appears until you leave every zone, and inside one you show as paused. The pause, and when it happens, can still show that you are nearby. A zone you add while recording applies from then on; points already shared can't be recalled.
- What you record while live sharing is off is never shared live, even if you turn it back on.
- Live points are encrypted with a key every member of the chat holds, so someone who has left the chat may still be able to receive them if their copy of Whispurr keeps that key. Share live only in chats whose members, past and present, you trust with your location.
- Maps. Maps under routes are drawn by Apple Maps. To show a map, a device requests map images for the area on screen from Apple, so when anyone views a route on a map, Apple can learn the general area being viewed, but not the route line, its times, or who recorded it. When you finish a route, your device draws its preview image once, so the people you share it with see the preview without loading a map. Turn off Device Settings → Routes → Show map under routes to draw routes on a plain background without requesting maps from that device.
- Exporting a route as a GPX file happens only when you choose Export GPX, and the file goes wherever you send it. Importing a GPX file reads it on your device.
- Places and photo locations. When you search for a place to share, the search text and the area of the map you are looking at go to Apple Maps to find matches. A photo keeps a location only if you turn on Device Settings → Locations → Include photo locations (off by default); the location is rounded to about 11 metres and travels inside the encrypted photo.
- Course audio. Music or narration you add to a course is audio from the chat, encrypted and shared like other media (section 2.4). Download Audio fetches it from members' devices ahead of time, so a course can play without a connection.
2.5b Online status and connections
If a persona shares its online status (Persona Settings → Share online status, on by default), your devices tell the members of each of its chats when you are online and when you are typing. They also tell them how your device is connected to each other member of that chat: the kind of connection (direct, relay, nearby Wi-Fi or Bluetooth) and who runs the relay (Whispurr, n0 or another operator), never an IP address or any other network address. Members' devices use this to show who is online, when each person was last seen (worked out on the receiving device from when it last heard from them), and how members are connected in the chat's member list.
These updates are encrypted with a key derived from the chat, signed by the sending device, sent live between devices, and never stored in the chat. Someone who has left a chat may still be able to receive them if their copy of Whispurr keeps that key. Turning off Share online status stops your devices from sending them for that persona, and from receiving other members' updates.
2.6 Multi-device sync (your own devices)
An authorized device can approve linking another installation through Whispurr's device-linking flow. Linking transfers the account's operational keys, never the recovery phrase, and each device keeps its own network identity, which no other device can derive. A restore with the recovery phrase reaches only your backup devices and goes ahead only after you approve it on one of them. An unlinked device stops syncing your account, but it keeps what it already received, including the keys of the chats it took part in. Restoring from a backup never brings an unlinked device back. A backup device is a Mac or a server running Whispurr that you link to your account; it keeps an encrypted full copy of the account so it can answer a restore. Removing a backup device, or a device you say is lost, also replaces your recovery phrase, and you are shown the new one.
Vault items (saved passwords, codes and cards) are encrypted on your devices under a key that is given only to your devices with a screen. It is kept in each device's secure storage behind Face ID, Touch ID or the passcode, and is never given to a device without a screen, such as a server running Whispurr, or to any service. A recovery phrase made on a device that has the Vault can also recover it.
On iPhone and iPad, Open & Log In and Use Card hand one login, one-time code or card to Whispurr's AutoFill extension on the same device, in its encrypted keychain storage, so the system can fill it in. It is offered once and removed after it is used or after a minute (two for a card), and never leaves the device. Drafts you write in a chat sync only to your own devices until you send them.
So that people in a chat can check which devices speak for you, each of your devices adds a signed entry to every chat it opens. The entry holds that device's public network key, which chat members already see when it connects, a public key for your persona, and the time it was added. When you unlink a device, a device you keep adds a signed note to your chats saying it was removed. People in a chat can therefore see how many devices each persona has used in that chat, and when each was added or removed. Entries contain no device names or account or installation identifiers; each carries a short tag that only your own devices can compute.
2.7 Pairing in person
Nearby invitations and invitations into an existing chat are completed while both devices are open. The QR code carries your device's identifier, its relay address, and a one-time handshake token, plus its local network address unless Hide IP Address is on; it never contains your public IP address (section 2.11). After both sides confirm a shared fingerprint (shown as a sequence of emoji on both screens), each device agrees on the conversation key. From that point on, your records and chat replicate peer-to-peer between the paired devices.
A camera scene lets other phones join your chat camera as extra cameras for as long as it stays open. Its QR code carries a temporary device identifier made for that scene only, its relay address, a one-time join secret, and the name of the persona you are chatting as, plus a local network address unless Hide IP Address is on. A phone that scans it joins with its own temporary identifier and its persona's name; neither side learns the other's lasting identity, and nobody needs to share a chat. While you watch a joined camera, it sends you low-resolution preview frames, and when you take a photo or video, each joined camera captures too and sends you its copy, directly or through a relay that cannot read it (section 2.11). To fire at the same moment, joined phones and yours exchange clock readings while the scene is open. The joined phone keeps its own copy in its camera. Nothing is stored by Whispurr, and the scene ends when you close the camera.
2.7a Contact cards, chat invites, and chat requests
You can share a contact card for a persona (for example on a slide or badge), and Start a Chat shows a single-use invite card that expires after seven days. A card is a signed link or QR code containing the persona's display name, a network identifier for one of your devices (its device identifier and relay address, never its IP address), public keys, and the address of the card's inbox together with a key that lets holders add to it. It contains no avatar, recovery phrase, or chat key. Anyone who has a card can see that display name and can send you a chat request, so share cards only where you are comfortable doing so, and revoke a card in Share My Contact when you no longer want it used. A single-use invite stops working after its first use or expiry.
A chat request contains the sender's own contact card, an optional short note, and the key for a new conversation. It is encrypted end to end to your card and signed by the sender. Your device accepts or declines it; declining sends nothing back. Requests on your own single-use invites are accepted automatically, since you chose to show that invite. Chats started this way are not compared with emoji; you may verify in person later. If you choose Emojis under Invite Settings → Verification instead, Start a Chat shows a live code that lasts 15 minutes, and both of you compare the same emoji before the chat is created.
So that a request can arrive while you are offline, each card has a free inbox at the Whispurr-operated content-blind provider. Unlike Courier, it is opened automatically when you create a card, start a chat, or send your first chat request, and it involves no account or payment. The provider stores: an inbox identifier derived from a key, the inbox's public keys, encrypted requests (until your device reads them, and at most 30 days), and the push targets your devices registered for it. It never receives card keys, request contents, or the sender's identity. To limit abuse it processes request timing and size and counts requests per inbox, per sender network address, and per sender network address for each inbox; addresses are kept only as keyed one-way hashes, under a key that changes daily, in hourly counters that are deleted within about two hours. An inbox is deleted when its card is revoked, used up, or expires, or after 90 days without your devices checking it.
If notifications are enabled, each installation registers a separate push target for each persona's contact-card inboxes with the notification gateway (section 2.9), so the provider cannot tell that two personas share a device, and a new request wakes your devices. A persona's target is revoked when notifications are turned off, the persona is removed, or the app is reset. The sender can include a lock-screen preview — their display name and the start of their note — encrypted to a key derived for your card; the provider, gateway, Apple, and Cloudflare cannot read it, and your device decrypts it only if "Show message previews" is on. Otherwise you see a generic alert.
2.8 Diagnostic information
Whispurr does not use Firebase Analytics, Crashlytics, or any third-party analytics or crash-reporting service. Apple may provide diagnostics under its standard "Share with App Developers" opt-in, which you control through iOS Settings → Privacy & Security → Analytics & Improvements. Optional cloud services also maintain limited operational records for delivery, abuse prevention and storage safety, as described below; these are not behavioral analytics.
About once a day the app downloads a small signed file from whispurr.app that says which app versions are still supported and whether any feature is temporarily turned off. The request carries no account, device, or contact information, no cookies, and no identifiers; like any web request, it reaches our hosting provider from your IP address. The file can ask an outdated version to update before it connects to other devices again. It cannot unlock features, read your data, or identify you.
2.9 Optional background notifications
If you enable device notifications for a chat that uses Courier, or for contact-card requests (section 2.7a), Whispurr sends that installation's Apple Push Notification service (APNs) token to a Whispurr-operated push gateway. The gateway stores the token encrypted at rest with a random target identifier, push platform and environment, expiration, and limited delivery/rate-limit history. It receives no chat identifier, sender, plaintext message text, media, Courier mailbox, or conversation key. A wake may carry a small message-preview ciphertext encrypted with a key derived from the conversation’s own key that is unavailable to Courier, the gateway, Apple, and Cloudflare. Courier receives only an unrelated random wake channel, that opaque ciphertext, and a capability that requests a “Whispurr — New message” fallback alert; it never receives the APNs token. Apple receives the device token, generic fallback, and opaque preview ciphertext in order to deliver the alert. If “Show message previews” is enabled on the receiving device, Whispurr's notification extension authenticates and decrypts the preview locally; otherwise the generic fallback remains. Request timing, volume, ciphertext size, network address, and delivery status may be processed for routing, reliability, and abuse prevention. New registrations are counted per network address for a minute by Cloudflare's rate limiter; the gateway does not store the address. Push targets expire after 30 days unless renewed and are revoked when notifications are disabled, the app is reset, the device token is rejected, or the target expires.
2.9a Voice calls
One-to-one voice calls travel between the two participants' devices over an end-to-end encrypted peer-to-peer connection: directly when possible, or through a relay that forwards the encrypted packets and cannot decrypt them (section 2.11). With Hide IP Address on, calls over the internet always go through Whispurr's relay. Call audio is never recorded or stored, and the microphone is used only while a call is ringing out or connected. On iPhone and iPad, calls appear in the system call interface (CallKit) but are excluded from the system Recents list.
To ring a device whose app is not running, Whispurr uses the same optional notification path as messages (section 2.9) with a separate Apple VoIP push token and push target. The call invitation — a random call identifier, the caller's display name, and a ring deadline — is encrypted with a key derived from the conversation’s own key unavailable to Courier, the gateway, Apple, and Cloudflare. Courier and the gateway learn only that a call-type wake occurred, its timing, and the opaque ciphertext; Apple additionally learns that a call push was delivered to the device. Call rings expire at their deadline and are never delivered late.
2.10 Cloud resource metadata and payments
When Courier is used, Whispurr and its hosting provider can associate a pseudonymous owner with encrypted resources, sizes, request timing, and retention deadlines. These associations support delivery, expiry, and abuse prevention and are not used for advertising. Routine diagnostics exclude content labels, decryption keys and capability URLs. See the cloud service policy for Courier limits.
Before a device installs Courier, it uses Apple's App Attest to show whispurr.app that the request comes from a genuine copy of Whispurr. The device sends Apple a key it generated and a one-way hash of a one-time challenge; the request names no account, persona, or chat. whispurr.app keeps only that key's identifier, public key, and counter for that device of your account. Devices that cannot use App Attest, such as Macs, can install Courier once an iPhone or iPad in the same account has done so.
Whispurr does not currently sell subscriptions or hosted cloud backup, and its services do not process payment information. If paid services are offered later, this policy will be updated before they are activated. Whispurr's services never collect Apple passwords or card details. Cards you save in the Vault stay encrypted on your own devices (section 2.6), and their security codes are never stored.
2.11 Connections and your IP address
Your devices reach the devices you chat with over the internet, over a shared local network, or over Bluetooth. Any internet connection shows your device's IP address, which can reveal your approximate location, to whatever is at the other end of it. Whispurr never includes your public IP address in profiles, contact cards, invites, or anything else it shares or syncs. QR codes and links for pairing and device linking may include your device's local network address (for example 192.168.1.20), so that devices on the same Wi-Fi network can connect without the internet. Members who share their online status also tell each other what kind of connection they have, but never an address (section 2.5b).
Under Device Settings → Transports you choose how your devices use the internet:
- Network (the default). Your devices connect to other devices through a relay server, then try to connect directly. A direct connection is faster, but the device at the other end, and so the person you are chatting with, can see your IP address. The relays are operated by Whispurr. Your devices also use relays operated by Number Zero (n0) while Whispurr's relays are unreachable, and to reach devices that use n0's relays, such as devices running older versions of Whispurr. Your devices use no other relay, whatever relay an address shared by another device names. So that other devices can find yours, each device also publishes its device identifier and relay address, but not its IP address, to an address lookup service operated by n0, and looks other devices up there. n0's servers see the IP address that these requests come from.
- Hide IP Address. Your devices make no direct internet connections to other devices: every internet connection to the people you chat with goes through Whispurr's relay, so they never see your IP address. Your devices do not use n0's relays or address lookup, even when Whispurr's relays are unreachable; until they are back, your devices connect only to nearby devices over Bluetooth and Wi-Fi. Nearby devices may see your local network address. Link previews are not loaded, and reactions you add from a website other than whispurr.app are downloaded for you by our server (section 2.5). Other services that you use, such as Courier, contact-card inboxes, notifications, Apple Maps, and the daily version check, see your IP address as described in their sections.
- Network off. Your devices connect only to nearby devices over Bluetooth and Wi-Fi.
Whispurr's relays currently run on a server we operate in the United States. A relay forwards end-to-end encrypted traffic between devices. To do that it processes your IP address, your device identifiers, and the timing and size of that traffic, but it cannot read your records, messages, calls, or media. Whispurr's relays do not log IP addresses or device identifiers, and hold connection details only in memory while a connection is open.
3. How we use the data
We cannot read your content. The app uses your recovery phrase only on your own devices, to find your backup devices and prove that a restore is yours. Peer-to-peer relays, contact-card inboxes, and the optional Courier provider receive only encrypted bytes and the limited metadata required to route, retain, verify, and delete them.
We do not use your data to train machine-learning models, to advertise to you, or to make automated decisions about you.
4. Third-party processors
Whispurr's peer-to-peer architecture means we use very few third-party processors. None of them are used for advertising or tracking.
- Apple Inc. — distributes the app through the App Store, delivers optional remote notifications containing a generic fallback and, when present, opaque preview ciphertext through APNs, delivers optional incoming-call pushes containing only an opaque call invitation, verifies through App Attest that a device installing Courier runs a genuine copy of Whispurr (section 2.10), provides map images through Apple Maps when you view maps under routes (section 2.5a), and provides anonymous diagnostics if you opt in via iOS Settings. Apple privacy.
- Cloudflare, Inc. — hosts whispurr.app and the optional content-blind Courier provider, contact-card inboxes, and the separate notification gateway. When you use one of those services, Cloudflare processes its opaque ciphertext or encrypted APNs token and the metadata needed for storage, transfer, delivery, expiry, and abuse prevention. It may also log basic request metadata such as IP address and user agent. Cloudflare privacy.
- Number Zero (n0) — operates public relay servers, which your devices use while Whispurr's relays are unreachable or to reach devices that use n0's relays, and the address lookup service that your devices use to find each other in the default network mode (section 2.11). The relays forward encrypted traffic and cannot read your records, messages, or media; the lookup service receives device identifiers and relay addresses. Both see the IP address of the devices that connect to them. Neither is used while Hide IP Address is on.
5. Data storage and security
Records, messages, and media are stored on your device under the iOS sandbox, with Data Protection set to "Complete until first user authentication" so the underlying files are inaccessible until you unlock the phone after a reboot. Your recovery phrase and conversation capabilities are held in the iOS Keychain. Stored records and changes are encrypted with AES-256-GCM; media is encrypted before it is sent or stored. Connections between devices and relay servers are encrypted in transit.
Whispurr keeps its data out of iCloud and computer backups of your device, because the keys that open it never leave the device. To keep a copy of your account, link another device as a backup device (section 2.6); to move to a new device, restore with your recovery phrase from that backup or link the new device from an existing one.
No system can be guaranteed perfectly secure. Compromise of an authorized unlocked device or its keys can expose content available to that device; the recovery phrase is not an additional password required for every read. Protect both your devices and recovery material. Hosted cloud storage does not hold plaintext content keys.
6. Data retention and deletion
Data persists on authorized devices. Local removal and operating-system secure-store behavior are distinct; uninstalling is not a verified wipe of every credential, paired-device copy, or cloud resource. If you explicitly attach Courier to a chat, it may retain temporary encrypted changes and media, which expire under their accepted retention policy. Decryption happens on authorized devices, not at the provider. Turning Courier off for a chat, or leaving or deleting the chat, asks the provider to delete that chat's mailbox; until it can, the mailbox expires under its retention. Reset App asks whispurr.app to erase the account's Courier data at every provider when the device is the account's only active one; an account that still has other devices keeps that data for them. If erasure cannot complete, the data expires on its own. Whispurr does not offer hosted cloud backup: backups are kept on backup devices you link to your account. If you lose every copy of the necessary keys and content, we cannot reconstruct them. Every member of a chat keeps their own copy of it. Media you shared can be deleted for everyone from the chat's Storage screen; to remove anything else from another member's devices, ask them to delete the chat from within the app.
Deleting a message you sent removes its text and attachments from each member's device when that device next syncs. A notification already shown, or a copy someone saved, may remain. Each device also keeps earlier versions of a conversation in its encrypted history, so a deleted message stays recoverable from that device's encrypted files until the conversation itself is deleted there. Encrypted media bytes are removed when a device reclaims storage. Chat-list previews are computed on each device from its own copy of the chat and are never synced.
For privacy-policy questions, email privacy@whispurr.app.
7. Children
The App Store assigns Whispurr an age rating based on its content. The rating varies by country or region; it is currently 4+ in most regions, with different ratings in some. This rating does not mean that Whispurr is designed specifically for children. Parents or guardians should decide whether the app is appropriate for a child.
8. Your rights
Most information you create in Whispurr is stored on your devices and the devices you authorize. It is end-to-end encrypted, so Whispurr cannot read, retrieve, correct, export, or delete that content for you. Use the app's controls to manage content on your devices. Deleting a message you sent removes it from members' devices as they sync (section 6); other removals, such as deleting a chat on one device, may leave copies on other authorized devices.
Whispurr and its providers may process limited account and device identifiers and, if you use optional cloud services, service metadata. We do not have a support tool for looking up or editing your encrypted content. For questions about information processed by Whispurr, email privacy@whispurr.app and include your account ID and the service, if known. We may not be able to locate information using only your name or email address. Do not send your recovery phrase, encryption keys, or private conversation content. We will respond as required by applicable law.
9. International transfers
WhispurrApp, LLC is based in the United States. If you enable optional cloud services, account and device IDs, service metadata, and encrypted files may be processed by our service providers in the countries where they operate. Providers cannot decrypt your end-to-end encrypted conversations or media. Whispurr also syncs encrypted conversations, records, and media between the devices you authorize; if those devices are in different countries, that data may cross borders. Relays forward encrypted traffic between devices and process the routing information needed to deliver it (section 2.11); Whispurr's relays are currently in the United States, and n0's are in several countries. You can choose not to enable optional cloud services, but that does not prevent cross-border syncing with authorized devices in other countries. Data-protection laws may differ between these countries. For questions about providers used by an optional service, contact privacy@whispurr.app.
10. Changes to this policy
We may update this policy from time to time. When we do, we will revise the "Last updated" date at the top and, for material changes, notify you in the app. Your continued use of Whispurr after a change indicates your acceptance of the updated policy.
11. Contact us
Questions, concerns, or requests related to this policy can be sent to:
WhispurrApp, LLC
Email: privacy@whispurr.app