Privacy policy.

Your conversations should stay between you and the people you talk to. This is what UIMessage can and can't see, what we keep and for how long, who helps us run the service, and the choices you have.

It covers the UIMessage apps for iPhone, iPad, Mac and Android, UIMessage Web at web.uimessage.com, and this website. UIMessage is made by IntrSI (“we”, “us”); you can reach us at hello@uimessage.com.

Last updated: November 11, 2026

1. The short version

  • Your messages, calls, photos, videos, voice notes, documents, stickers, GIFs, statuses and the locations you share are end-to-end encrypted. Only the people in the chat or on the call can read, see or hear them. We can’t, and neither can anyone else.
  • Our servers pass encrypted messages on and delete each one as soon as the devices it was sent to have saved it. A message that can’t be delivered is deleted after 30 days. Your chat history is kept on your own devices.
  • To run UIMessage we handle some information we can read: your phone number and profile, which of your contacts use UIMessage, your groups and their members, your devices, and records of who messaged or called whom and when. We keep each only as long as section 8 says.
  • We don’t sell your information, share it for advertising or track you across other apps and websites. The apps contain no advertising, analytics or crash-reporting code.

2. What’s end-to-end encrypted

End-to-end encrypted means the content is locked on your device with keys that only the devices in the conversation hold, and unlocked only on those devices. Our servers store and pass on the locked copy and have no key to open it. That covers:

  • messages: text, replies, reactions, edits, deletions, link previews, and the lines a group shows when it changes;
  • photos, videos, voice notes, documents, stickers and GIFs;
  • statuses: their photos, videos and captions;
  • locations and live locations;
  • voice and video calls and screen sharing, one-to-one and in groups;
  • the chat history your phone sends to a Mac, iPad or browser you link to it.

Every device makes its own keys, and its private keys never leave it. Your phone vouches for each device you link by signing your account's list of devices. Each pair of devices talks through its own session, set up with a post-quantum key agreement (X25519 with ML-KEM-768) and continued with the Double Ratchet, so the keys keep changing and a key stolen later can't unlock earlier messages. Groups use sender keys, given only to the members in the group's own signed membership record. Every photo, video and file has a key of its own, sent inside the encrypted message, and calls get theirs the same way. To make sure nobody is in the middle, compare your safety number with a contact: open the chat, tap their name, then Encryption. The details are in How UIMessage's encryption works.

3. Information we can read, and why

Some information has to be readable by our servers for UIMessage to work: to sign you in, deliver messages to the right devices, apply your privacy settings and keep people safe. This is all of it.

Your phone number
Your account is your phone number. We use it to sign you in, and so people who have your number can find you on UIMessage. Sign-in codes are sent to it by text message.
Your profile
Your name, your “about” line, your profile photo and your mascot, shown to others as your privacy settings allow, and your country and language. Profile photos and group photos are kept so they can be shown, so they aren’t end-to-end encrypted.
Your settings
Your privacy settings (who sees your photo, about, last seen and online status, and who can add you to groups) with their exceptions, the accounts you block, and, if you turn on two-step verification, a protected hash of your PIN, never the PIN itself.
Your contacts
If you allow it, the app sends the phone numbers in your address book to our server, as they are, to find which belong to UIMessage accounts. The server answers and keeps nothing from that check. The numbers that are on UIMessage are then saved to your account’s contact list, so your privacy settings can tell your contacts apart and your other devices show the same list. The names in your address book never leave your device.
Your groups
A group’s name, description, photo, members, roles, settings and join requests, and for 7 days a record of each change and who made it. An invite link carries a secret our server never sees.
Messages on their way
While a message waits to be delivered: its encrypted copy, who sent it, to which devices, when, and its size, rounded up in steps of 160 bytes. Each copy is deleted once its device has saved it. For 30 days we also keep a short record of each message sent (its id, sender, chat, type and time) to keep your devices in step, and where you’ve read each chat up to, for unread counts.
Statuses
The encrypted status, who can see it, and who viewed and liked it, until the status ends 24 hours after you post it.
Photos, videos and files
Their encrypted copies and their size, so the people they were sent to can download them, until the sender deletes them for everyone and at most 31 days after they were sent.
Calls
Who called whom, when and from which device, kept for a day after the call, and your call history, kept for 7 days (your devices keep their own). During a call, our relay and group-call servers handle your device’s network address to connect it. In a one-to-one call with someone in your contacts, the two devices may connect directly, so each can see the other’s network address; a call with anyone else goes through our relay.
Your devices
For each device you sign in or link: its name as the system reports it, its type, app version and language, the country it was set up in, when it was last active, the network address it last used and the one it was linked from, and its notification token. The Devices screen shows each device’s approximate region and country, which our own server looks up from its network address (IP geolocation by DB-IP) and doesn’t store.
Sign-in and security
Each sign-in attempt (the number, the result, the network address and the app’s or browser’s user agent), each sign-in code (as a hash only), your sign-in sessions, and who looked up whom by Spark code.
Reports and reviews
When you report someone: what you picked and wrote, and, unless you turn it off, the last five messages that person sent in the chat (text and captions only), which your device seals so that only our review team can open them. When you ask us to review a decision about your account: what you write. Our team reads reports and review requests, so they aren’t end-to-end encrypted.
Decisions about accounts
If we put an account under review, restrict it or ban it: the decision, its reason and dates, and our notes.
Online and last seen
Whether you’re online and when you were last seen, shown to others as your settings allow.
Requests to our servers
Our servers log each request from the apps, as they do for UIMessage Web and this website (section 7): its network address, its time, what it asked for and the app’s user agent. We use the logs for security and to fix problems, and delete them after 14 days. World’s map, on iPhone, iPad and Mac, comes from our server a piece at a time, so these logs show which part of the map a device asked for.

4. What we don’t collect

  • The content of your messages, calls, photos, videos, files, statuses and shared locations, which are end-to-end encrypted.
  • The names in your address book, or the numbers in it that aren’t on UIMessage.
  • Your precise location. Locations you share travel end-to-end encrypted. The app uses your location only when you choose to share it, and in the background only while you share your live location, for the time you picked.
  • What you search for in the app: searches run on your device. Link previews are made by the sender’s device and travel inside the encrypted message, so neither we nor the people you send them to contact the linked site.
  • Advertising identifiers, analytics or crash reports: the apps contain none of them.
  • Your email address, unless you write to us.

5. How we use information

Only to run UIMessage: to create your account and sign you in, deliver messages, calls and notifications to the right devices, show your profile to the people your settings allow, keep your devices in step, prevent spam, fraud and abuse, keep the service secure, answer you when you contact us, and meet our legal obligations.

Our safety systems never look at what you say. They count how accounts are used, such as a burst of new accounts from one network, an account messaging many people it has never talked to, or many people blocking the same account, and some may limit an account for a while on their own. Every automatic action is recorded, and you can ask us to review it. The Community Guidelines explain how.

We don’t use your information for advertising or profiling, or to train AI models, and we don’t sell or rent it to anyone.

6. Who else handles information

We run UIMessage’s servers ourselves. These companies handle some information so we can deliver what you ask for:

Apple
Delivers notifications and incoming calls to iPhone and iPad, so it handles your device’s notification token. The Mac app hears of new messages and calls over its own connection to our servers instead. A message notification carries the encrypted message and the ids of its chat and sender, and your device opens it. A few notifications that aren’t messages, such as a like on your status or being added to a group, include the names involved. On Apple devices, maps and place search in location sharing use Apple Maps, so Apple receives the area shown or searched.
Google
Will deliver the Android app’s notifications through Firebase Cloud Messaging once the app receives them, handling your phone’s notification token and the same encrypted contents as Apple does. Until then the Android app uses no Firebase: new messages and calls reach it only while it’s open, as it says in Profile, under Account. We won’t use Firebase for analytics or anything else.
Twilio
Sends sign-in codes by text message and checks the code you enter, so it receives your phone number and that code.

World’s map, on iPhone, iPad and Mac, is drawn from OpenStreetMap and Overture Maps Foundation data that our own server fetches and serves: your device asks only us for it, and nothing about you goes to either.

We don’t share information with anyone else, except when the law requires it. We answer only valid legal requests, and only with information we hold, which never includes the content of messages or calls: we can’t read it.

7. UIMessage Web and this website

UIMessage Web runs in your browser, linked to your phone. It keeps its keys and your chat history in the browser’s own storage, sealed with a key the browser can’t export, and deletes all of it when you sign out. It sets no cookies; it remembers your appearance setting in the browser.

This website sets no cookies and runs no analytics, ads or scripts from anyone else. It remembers in your browser only that you’ve seen its opening animation and closed its privacy note. Like any web server, ours log each request (the network address, the time, the page asked for and the browser’s user agent) for security and to fix problems, for UIMessage Web too, and delete the logs after 14 days.

8. How long we keep information

Encrypted messages waiting for delivery
Until every device they were sent to has saved them; at most 30 days
The short record of each message sent
30 days
Encrypted photos, videos, voice notes and files
Until the sender deletes them for everyone; at most 31 days
Profile and group photos
While in use; a replaced or removed photo is deleted at once
Statuses, with who could see, viewed and liked them
Until the status ends, 24 hours after it’s posted
Chat history sent to a newly linked device
Until that device downloads it; at most 24 hours
Call records
1 day after the call; call history 7 days
Records of group changes
7 days
Your account, profile, contacts and groups
While your account exists
Your privacy settings and blocks
While your account exists, then with its empty record
Your devices and sign-in sessions
Kept after a device signs out, to protect your account and look into abuse
Sign-in codes
7 days after they expire
Sign-in attempts
400 days; the full network address is cut to its network after 30 days
Spark code lookups
90 days; network addresses are cut after 30 days
Reports
The messages and notes sent with a report: 90 days after we close it, or 180 days after it arrived if it’s still open. The report itself: 2 years after it’s closed
Decisions about an account, and review requests
As long as we keep the account’s record
Counts our safety rules read, and their results
30 to 90 days; overall totals 400 days
Server logs
14 days
Database backups
14 days

9. Deleting your account

Delete your account on your phone, in Profile → Account → Delete account. The Mac app, UIMessage Web and linked iPads can't delete the account. If you no longer have the app, ask us.

Deleting your account signs out every device and deletes, at once: your number and profile; your two-step verification PIN; your contact list; your place in your groups; messages still waiting for you or from you; your statuses; your photos and files on our servers; and your encryption keys and Spark codes. The app deletes the chat history on your phone, and your linked devices delete theirs as they sign out.

What stays: messages you sent stay on the devices of the people you sent them to. We keep an empty record of the account, with no number, name or photo, so your chats show others that the account was deleted, and with it the account’s privacy settings and blocks, its decisions and review requests; the device and sign-in session records described above; and the sign-in attempts, report and safety records until their time runs out. An account can’t be deleted while it’s under review. If you delete an account that’s restricted or banned, we keep a keyed fingerprint of its number until the restriction ends, so signing up again doesn’t lift it.

10. Your choices and rights

  • Choose who sees your profile photo, about, last seen and online status, and who can add you to groups, in Profile → Privacy.
  • Block or report anyone from their chat.
  • See your devices, and sign any of them out, in Profile → Devices.
  • Turn on two-step verification in Profile → Account, so nobody can sign in with your number without your PIN.
  • Allow or stop access to your contacts, camera, microphone, photos, location and notifications in your device’s settings at any time. Without access to your contacts, you can still start a chat by number.
  • Delete messages, chats or your whole account.

You can also ask us for a copy of the information we hold about your account, or ask us to correct or delete it, by writing to hello@uimessage.com with the number. We check that a request comes from the number's owner before we act on it, and answer within 30 days. Where you live may give you these rights by law, for example in the European Union, the United Kingdom and California, and you can complain to your data protection authority. We don't sell or share personal information as California law uses those words.

12. Children

UIMessage is for people aged 13 or older, or older where the law of your country says so. We don't knowingly collect information from children under 13. If you think a child under 13 has an account, tell us at hello@uimessage.com.

13. Security

Besides end-to-end encryption, every connection to our servers is encrypted in transit, and the information above is kept on our own servers, out of public reach. Our team works with it only through private tools: the admin dashboard needs a passkey, shows each person only what their role needs, and records every action in a log that can’t be changed. On your devices you can lock chats and set a two-step verification PIN. No system is perfectly secure; if a breach affects you, we’ll tell you as the law requires.

14. Where information is processed

Our servers are in Canada. Apple, Google and Twilio may process the information they handle in the United States and other countries, under their own privacy commitments.

15. Changes

We’ll update this policy when UIMessage changes. The date at the top shows the current version; when a change matters, we’ll also tell you in the app.

Contact

hello@uimessage.com

UIMessage is made by IntrSI. Write to us about privacy, your information or this policy, and we'll answer within 30 days.