BLAST
Privacy Policy
Blast. Last updated 12 October 2026.
Blast does not store your data, and keeps none of your content on a server of its own. What you save and what you send live in your iCloud account and in the iCloud accounts of the people you send them to. We cannot read them. This policy explains the few things that do leave your device, why they leave, and what you can do about them.
Who we are
Blast is an iOS app for saving links into bundles and sending them to people you know. In this policy, "we" and "us" mean the developer of Blast, and "you" mean the person using it. If you are in the EEA or the UK, we are the data controller for the small amount of information described below.
The short version
- We do not run a server that holds your content. Your bundles, saved links, messages, voice notes, pictures and stickers are stored in your iCloud, under your Apple Account, using Apple's CloudKit.
- We do not use analytics, advertising, attribution or crash reporting services. The only third party SDK in the app is RevenueCat, for Blast+ subscriptions. We keep a few anonymous daily totals, such as how many bundles were sent that day, with nothing that identifies you (see "Daily totals" below).
- We do not track you across other apps or websites, and we do not sell or share personal information.
- One thing is public by design: your username, so that friends can find you. Nothing else is.
- Sign in with Apple is the only way to sign in, and we ask it for your name only. We never ask Apple for your email address.
What Blast handles, and where it goes
| What | Where it is kept | Who can see it |
|---|---|---|
| Saved links, bundles, folder designs, your profile picture and name | Your device, and your own private iCloud database | You. Apple holds the encrypted store on your behalf. |
| Bundles you blast, messages, voice notes, GIFs, stickers and reactions | A shared iCloud area for that conversation | You and the people in that conversation. |
| Your username, an opaque account identifier and a one way hash of your Apple user ID | The app's public iCloud database | Anyone using Blast who searches for that username. We can see these records too. |
| Your display name next to that username | The same public record, only if you are discoverable | Anyone searching, until you turn discovery off. |
| Online status and how far you have read | The shared area of each conversation | The people in that conversation, unless you hide it in Settings. |
Sign in with Apple
Signing in gives Blast an opaque identifier for your Apple Account and, if you allow it, your name. We ask Apple for the name only. We never request your email address, so we never receive one, real or relayed. Your name is used to label what you send, so that your friends see who a bundle came from. Apple's own handling of Sign in with Apple is covered by Apple's privacy policy.
Your username
A username exists so that someone who knows your handle can send you a connection request. It is held in the app's public CloudKit database as one record per handle, containing the handle itself, an opaque CloudKit account identifier, a salted one way hash of your Apple user ID, the time it was claimed, and your display name if you have chosen to be discoverable. The hash is what lets the app recognise your own handle after you move to a new device. It cannot be turned back into your Apple ID.
This is the only part of Blast that is visible to people you have not connected with, and, together with reports (below), the only part we can read from the CloudKit dashboard. If you turn discovery off, your display name is removed from the record and only the handle remains.
What you save, and what you send
Saved links, bundles and their designs sit in your device's local store and in your own private iCloud database. Apple holds that data for you under your Apple Account. We have no access to it.
When you blast a bundle or send a message, it is written into a shared iCloud area for that conversation, which only you and the people you invited can open. That includes message text, voice notes, GIFs, stickers, reactions and the bundles themselves. Photos and videos from your library cannot be sent in a chat. Deleting a message for everyone removes it from that shared area, although anyone who already read it may have seen it, and a copy may remain on their device until their app next syncs.
Notifications
If you allow notifications, your device's push address (a token Apple issues so notifications can reach this copy of the app) is written into each of your conversations, where only the people in that conversation can read it. When you mute a conversation, your push address is removed from it.
When someone sends you a blast or a message, their app asks Blast's notification relay to wake your device. The relay receives your push address, the sender's display name and whether it is a blast or a message, and passes a notification reading "New blast from" or "New message from" and the sender's name to Apple's Push Notification service. It receives no message text, no bundle, no link and no picture. It keeps nothing: no log of who notified whom, and no copy of any push address. The relay runs on Cloudflare, which sees the request's IP address in the ordinary way. To stop the relay being used by anything but Blast, each request carries a token from Apple's DeviceCheck service, which the relay checks with Apple; it identifies the app on a genuine device, not you. To stop anyone flooding a device with notifications, Cloudflare's rate limiter counts requests for a short time by IP address and by a one-way hash of each push address. Those counters belong to Cloudflare's service, expire within minutes, and are never read by us.
Any other notification, and the fuller wording once the app has synced, is composed on your own device from data the app already has.
Daily totals
So we can see whether Blast is working and how much it is used, the relay keeps a handful of running totals for each day: how many bundles were blasted, how many new accounts were made and deleted, how many notifications were delivered or failed, how many pictures the content filter refused, and how many times the app crashed. Each total is just a date, the kind of thing counted and a number. When your app adds to one, it sends only the kind and the number, with the same DeviceCheck token described above. No name, username, account identifier, push address, IP address, content or picture is stored with them, so a total cannot be traced back to you or to any device. Only we can read them.
Reports
If you report someone, Blast files the report in the app's public iCloud database, in a record that only you and we can read. It holds the reason you chose, anything you wrote, the name the person shows, an opaque identifier for their account and one for yours. So that we can check the report, it also includes up to the last five messages that person sent you in that conversation: their text, the address of any GIF or sticker, and a small, low resolution copy of any picture. Voice notes are described but not included, and nothing you wrote is included. The Report screen tells you this before you send. The person you report is not told. We use reports only to review them and to act on accounts that break the rules, and we delete them once they are dealt with.
Blast+ subscriptions
Subscriptions are sold by Apple through the App Store. Payment details are handled by Apple and never reach us or the app.
Blast uses RevenueCat to make and restore purchases and to keep track of subscriptions. RevenueCat receives your App Store purchase records (which plan, when it started and renews, trials and refunds), a random identifier it creates for this installation, and basic details about the device and app such as the iOS version, app version, country and language, along with your IP address in the ordinary way. It does not receive your name, your Apple Account, your username or anything you save or send, and we do not link the identifier to your Blast account. We see those subscription records in RevenueCat's dashboard. RevenueCat's handling of this is covered by RevenueCat's privacy policy.
Blast does not store your data
Blast is not in charge of storing any of your data. Everything you save and everything you send is stored in iCloud, under your Apple Account and the Apple Accounts of the people you send it to. We do not keep a copy anywhere.
That means we cannot back up your data and we cannot restore it. Content can be lost if you or someone in a conversation deletes it, if your iCloud storage is full, if iCloud is turned off for Blast, if you sign out of your Apple Account, if you delete your account, or if Apple's service has a problem. Link previews, GIFs and stickers load from the websites and services that host them, and they can disappear if those sites remove them. Blast is not a backup service, so keep your own copy of anything you cannot afford to lose. Our Terms of Use say more about this.
When something leaves your device to a third party
Websites you save from
When you save a link, Blast fetches that page directly from the website in order to read its title and preview picture. That request goes to the site itself, from your device, and the site sees it in the ordinary way a visit is seen, including your IP address. We do not receive anything from it. Nothing about what you save is sent to us.
A bundle carries each link's preview as a small picture and the address of the full one. When you receive a bundle, or restore your library on a new device, Blast fetches the full preview picture from that address, or from the page itself, in the same ordinary way. Keeping the picture where it already lives means it does not take up space in anyone's iCloud.
GIF search
If you search for a GIF or sticker, the words you type and your IP address go to KLIPY in order to return results, along with a random identifier made for this installation (not your name or Apple Account). KLIPY's handling of that request is covered by KLIPY's privacy policy. A GIF or sticker you send travels as its KLIPY address, so the person you send it to downloads it from KLIPY, which sees their IP address in the same ordinary way.
While you type a short message of up to three words, Blast offers matching GIFs and stickers above the keyboard. To find them, those words go to KLIPY as a search. Longer messages are never looked up. You can turn this off in Settings, under Privacy, with "Suggest GIFs while I type".
This website and invitation links
This website, blastit.space, is hosted by Cloudflare. When you open a page here, including an invitation link, Cloudflare receives the request in the ordinary way a website does, including your IP address and the address of the page, and keeps short lived logs to deliver the site and protect it from abuse. Cloudflare's handling of that is covered by Cloudflare's privacy policy. The site sets no cookies and runs no analytics, and we do not keep any record of who opens it.
An invitation link carries, inside its address, the iCloud link to the conversation it invites you to. If Blast is installed, your iPhone opens the link in the app and the website is not contacted. If it is not installed, the page only shows you how to get Blast, and it does not read, store or send on the invitation.
Apple
Blast is built on Apple's own frameworks: CloudKit for storage and sharing, Sign in with Apple for accounts, StoreKit for the App Store, and the Push Notification service for alerts. Apple processes this data as described in Apple's privacy policy.
Things Blast deliberately does not do
- No analytics, product measurement or session recording beyond the anonymous daily totals above. The only records about individual people we see are Blast+ subscription records, through RevenueCat (above).
- No advertising, and no advertising identifiers.
- No third party SDKs except RevenueCat, which handles Blast+ subscriptions. KLIPY is called directly over its web API and has no code inside the app.
- No App Tracking Transparency prompt, because there is nothing to track you with.
- No sending of your content to any artificial intelligence service. Pictures are checked for unsuitable content on your own device by models built into the app, and nothing is uploaded to do it.
- No selling or sharing of personal information, as those terms are used in United States state privacy laws.
How long things are kept
What is in your own iCloud stays until you delete it. What is in a shared conversation stays until you or the other people in it delete it, or until the conversation is left and its shared area is removed.
A username record stays while you hold the handle. When you change handles, the one you left is reserved for a short period so that nobody can take your name the moment you move off it, and is then released.
A report is kept until we have reviewed it and acted on it, and is then deleted.
A ban is kept for as long as it lasts. It records the account it applies to, the reason and when it ends, and is removed when it is lifted. A timed ban stops applying on its own when it ends.
What you can do
- See and change what you hold. Everything Blast has about you is in the app itself. Items, bundles, conversations and your profile can all be edited or deleted in place.
- Hide your online status in Settings, and turn off discovery so your display name is not attached to your handle.
- Delete your account. In Blast, open Profile and tap Delete account. It deletes your library, your bundles, your conversations and the messages you sent, your username and your connection requests from iCloud, and then everything on your device. Apple then shows its Sign in with Apple sheet once more, and the one-time code it returns is passed to Blast's relay, which uses it to tell Apple to revoke Blast's access to your Apple Account. The relay keeps nothing from this. It cannot be undone, and we cannot get anything back afterwards. Reports you made about other people are kept until we have reviewed them.
If you are in the EEA or the UK, you have the right to access, correct, delete, restrict and object to the processing of your personal data, and to lodge a complaint with your data protection authority. Our legal basis for the username record is our legitimate interest in letting people find each other, and for the rest it is the performance of our agreement with you. If you are in California, you have the right to know, delete, correct and opt out. There is nothing to opt out of, because we neither sell nor share personal information.
Children
Blast is not for children under 13, and we do not knowingly collect personal information from anyone under 13. If we learn that a child under 13 has used Blast, we will remove what we can reach.
Where data is processed
Blast's data lives in Apple's iCloud infrastructure, which Apple operates across several countries. A GIF or sticker search reaches KLIPY, which likewise operates internationally. Where personal data leaves the EEA or the UK, those transfers rely on the mechanisms Apple and KLIPY respectively put in place.
Security
Data in transit is encrypted. Data in your private iCloud database is encrypted and reachable only by your Apple Account. Shared conversations are reachable only by their participants. No design is perfect, and nothing sent to another person can be unseen once they have read it.
Who is responsible
Blast is made by an independent developer based in the United Arab Emirates, who is responsible for the information described here.
Changes to this policy
If this policy changes in a way that matters, we will change the date at the top and, where the change is significant, say so in the app. Continuing to use Blast after a change means you accept the new version.