Blaze Privacy Policy

Effective 13 November 2026

Blaze is a private journal for two people. Everything you write is for you and the partner you are connected to. We do not sell your data, we do not show you advertising, and we do not track you across other apps or websites.

Who this policy covers

This policy explains what Blaze ("we", "us") does with your personal information when you use the Blaze mobile app on iOS or Android. It applies to the app and to the servers behind it, and to nothing else — links out of the app lead to services with their own policies.

Blaze is published by Lowkey AI, the developer of Blaze on Google Play and the App Store, and "we" in this policy means Lowkey AI. You can reach us at lowkey9.ai@gmail.com.

For anything in this policy, or to exercise any right described in it, write to us at the address in "How to reach us" below. We are the controller of the personal data described here.

What we collect

Only what the app needs to do its job. Every item below is either something you type in yourself or something the app has to record to work at all.

Account details
Your email address, your display name, the handle you claim, and whether your email address has been confirmed. If you sign in with Google, we receive your name, email address and profile picture from Google. If you sign in with Apple (on iPhone), we receive your name and email address — or, if you choose to hide it, the private relay address Apple creates for you. Passwords are handled by Firebase Authentication and are never visible to us. Every account also confirms a date of birth when it is created, whichever way you sign in, to show that you are 18 or over; it is kept as the birthday on your profile, which your partner can see, and unlike the rest of your profile it cannot be left empty.
Your profile
Anything you choose to add: profile and cover photos, a status line, birthday, a note about yourself, hobbies, love language, dietary needs, clothing and ring sizes, and gift ideas. All of it is optional, and all of it is written for your partner to read.
What the two of you create
Journal entries with their photos and the comments the two of you leave under them, daily mood check-ins, planned dates and their details, answers to the weekly question and the daily question and the comments and reactions under them, appreciation notes, shared goals, special dates, challenges you take on, the bucket list you keep together, arcade matches and duel runs and their results, scores from the weekly quiz about each other, the photo each of you posts to the day, the song you attach to a memory and the one you name as the pair's, pokes, watch parties — what you are watching or listening to, any link you add, where the shared clock is, whether each of you has it open, and the last reaction each of you sent — listening rooms — the songs either of you adds to the queue, where the shared clock is, whether each of you is listening and whether your phone can play whole songs through Apple Music, when one of you last asked the other in, and the last reaction each of you sent — songs you gift each other, with the note you write, whether it has been unwrapped and any heart sent back — messages you send each other in the chat — words, photos, stickers, voice notes, short video clips and files you attach, with any reactions and replies — glimpses — a photo sent to be looked at once — and Read together: which article one of you invites the other to, which paragraph each of you is on while you both have it open and whether one of you is reading aloud, the paragraphs you highlight and the margin notes and reactions you leave on them, your answers to an article's questions, and the articles you save for each other or mark as read. This is the content of the app, and it is stored so that both of you can open it on any device. Read together also keeps the web pages either of you shares to read together: the link, the headline you give it (or the title the app you shared from sent along), the site's address, and who added it and when — never the page itself, which Blaze does not load. It also keeps the weekly check-in — the five ratings each of you gives and the two lines you write — your own votes on Would you try? (which only you can read; your partner sees only the cards you both said yes to), your swipes on Pick for us and the cards either of you adds to a round in your own words (your swipes only you can read; your partner sees only what you both liked and, when nothing matched, one of your yeses drawn as a lucky pick), love coupons and whether they have been cashed in, open-when letters and when each was opened, the nights each of you said goodnight, the home list of jobs with who owns each and when it was last done, savings jars with the amounts you type in (Blaze never connects to a bank or takes payments), how far each of you is through a guided program and the notes you leave on each day, where your finger is on the touch pad while it is down, and on my way / home safe: the arrival time you choose and the moment you say you are home — never your location. Spicy keeps the cards the two of you draw and each of your replies to them, readable only by the two of you, and the switch each of you sets to open the deck.
Photos and camera
Only the images and videos you pick, take or record for a journal entry, a glimpse, a chat message, a chat wallpaper, a sticker, an avatar or a cover, and only when you pick them. The chat has a camera of its own, which shows your most recent photos so you can pick one without leaving the app; nothing is read from your library until you tap it. On Android, photos and videos are chosen through the system photo picker, which hands Blaze only the ones you pick; Blaze has no access to the rest of your library. Photos and videos sent in the chat stay in the chat: the app offers no way to save one to your phone or send it anywhere else, and it asks your phone to refuse screenshots and screen recordings of the app. The photos and videos in a memory are kept the same way: they stay in the app, with no way to save one to your phone, and Blaze never adds anything to your library. Editing in the Studio (filters, crops, words, stickers, trimming a clip, music) happens on your phone, and the music is Blaze's own, carried inside the app. The camera is also used to scan your partner's connection code; those scans are read on the device and never uploaded.
Microphone
Only while you hold the record button to send a voice note in the chat, or hold the shutter in the chat's camera to record a video. The recording is stored so your partner can play it, and it goes when either of you takes the message back or when you delete your account.
Glimpses
A glimpse is stored only until it is looked at or runs out of time. Once opened, it is shown briefly and the photo is then deleted from our servers; an unopened glimpse is deleted when its timer ends. If the recipient's phone reports a screenshot attempt while a glimpse is open, the time of that attempt is recorded and shown to the sender.
Time capsules
A letter or a voice note you seal until a date you choose, stored until then like anything else you write. It is the one thing in the app that not even its author can open early: our servers refuse to record it as opened, and refuse to hand over the recording at all, until the day you named has arrived.
Pause and reconnect
If the two of you use the pause tool, what each of you writes in the "I felt… / I need…" step is stored so the other can read it once you have both finished. The history of past sessions keeps the date and how each one ended and none of the words, and what is said out loud in the repair step is never written down at all. Either of you can delete a session outright.
Your wishlist
The things you add to your own wishlist, with any link, note and rough price. The app never shows your partner the list, and never tells you which item it surfaced to them as a gift hint in the fortnight before a birthday or an anniversary — the hint is worked out on their phone and not written down anywhere. The list is stored with the rest of your pair's data, so it is the app that keeps it back from your partner rather than the database.
When you are reachable
If you set quiet hours, the days and times you chose are stored on your profile, together with any "do not disturb until" or "open until" you set, so your partner's app can tell them when you are free rather than letting a message land in a silence. Your phone also publishes the name of its time zone — "Europe/London", not a position — so your partner can see your local time and the app can count down to a visit. A zone is a band of the world, not a location. If you are apart, you can also choose your home city from a list in the app. Only that city and its map coordinates, rounded to about a kilometre, are stored on the space you share with your partner, so their app can show how far apart you are. It is a city you picked, never a reading of your phone's position, and you can remove it at any time.
Tapping phones together
If you pair on Connect in person by tapping your phones together — and only after you turn Tap on, which is when your phone asks for location — your phone sends a rough position, accurate to about a kilometre, and how long ago it felt the knock, so our server can find the one other phone tapped at the same moment in the same place. It is used for nothing else, is never added to your profile or shown to anyone, and is deleted within a few minutes. The motion sensor that feels the knock is read on your phone and its readings are never uploaded. The code on the same page carries a one-time token that stops working after ninety seconds. Tapping phones is available only on iPhone; Blaze for Android asks for no location permission.
What you're listening to
Only if you turn on Profile › Now playing, which stays off until you do. While it is on, your partner can see the song you are listening to — its title, artist and album, which music app it is playing in, how long it is and how far through it you are — or a song you choose yourself, with any link you paste. On iPhone, Blaze can see only the song playing in Apple's Music app, and only while Blaze is open, using the Apple Music permission you grant; it cannot see what other music apps are playing, so for those you can set the song yourself. Blaze does not connect to your account on any music service and receives nothing from one. Only the song showing now is kept — never a history of what you listen to — and it is deleted when the song ends (at the latest about an hour afterwards), when you hide it, pause sharing or turn it off, and when you delete your account. On Android, Blaze does not detect what you are listening to: it never sees what other apps on your phone are playing, and it asks for no notification access.
How much the two of you use it
One tally per day for your pair, counting things like messages sent, photos uploaded and capsules sealed. It is what the free plan's daily allowances are measured against, and what stops a bug or a faulty client running up a bill nobody meant to spend. It counts events; it records nothing about what was in them.
Activity and the relationship score
The time you were last active, and the running score shown on Home — a total worked out on our servers from the things the two of you do in the app, such as writing a memory or finishing a challenge. It counts actions; it does not read what you wrote.
Notifications and device
A push notification token for your device, the platform it runs on (iOS or Android), and which categories of notification you have switched on. The token is what lets us tell you that your partner wrote something; it identifies the device, not you personally.
Calendar
If you add a planned date to your calendar, the event is written to the calendar on your own device. We do not read your calendar and nothing from it reaches our servers. On Android, the event is handed to your calendar app for you to save, and Blaze asks for no calendar permission.
Support messages
If you email support from inside the app, the draft includes your account identifier, the app version and your device platform so we can reproduce what you are seeing. You can delete any of that from the draft before sending it. Your email address reaches us because you are the one sending the email. If you use Send feedback or Report a safety concern in Help & Support instead, what you write is stored with your account identifier, the app version and your device platform; only the team that runs Blaze can read it, and we keep it for as long as we need it to answer and act on it.
On your device only
A few things are kept on your phone and never sent to us: your language and appearance choices, whether you have seen the introduction, which of the week's love-language ideas you have ticked off, a local copy of your notification preferences, and photos waiting to upload while you are offline.

Apart from the rough position described under "Tapping phones together" — sent only while you pair that way, and deleted within minutes — we do not collect your location, and nothing else in the app reads your phone's position. The only other thing that sounds like it — the name of your device's time zone, described above — is a band of the world rather than a place, and you can see it in your own settings. Blaze for Android asks for no location permission at all.

We do not use advertising identifiers, and we do not track you across other companies' apps or websites. Blaze contains no third-party advertising, analytics or crash-reporting SDKs.

Why we use it

To run the app
Signing you in, connecting you to your partner, and storing and syncing everything the two of you write so it is there on every device you use.
To notify you
Sending the push notifications you have switched on — a new memory, a date reminder, an answered question, your partner's check-in, a poke, a glimpse, a chat message. If you use Blaze on more than one phone, each one you have allowed notifications on is sent to. Every category can be turned off individually in Profile → Notifications, and all of them can be turned off in your phone's settings.
To keep accounts safe
Detecting and preventing abuse, and enforcing our Terms of Use. If you report your partner or one of their messages from the chat, the report — who filed it, who it is about, which message if any, the reason and anything you wrote — is stored where only we can read it, and your partner is not told. The same applies when you report an invitation you received. When a report is made, a copy is taken at once — the report, the message or messages it is about with their photos, clips or files, and both people's profiles as they were at that moment — and kept where only the team that runs Blaze can read it, for review. Security rules on our database confine every read and write to the account that owns the data and the partner it is shared with.
To support you
Answering the messages you send us and fixing what they report.

Where the GDPR applies, our legal basis is performance of the contract between us for everything needed to run the app, your consent for push notifications, for access to your photos, camera, microphone and calendar, for your rough location while you tap phones to pair, and for sharing what you are listening to with your partner (Now playing) — each of which you can withdraw at any time in the app or your phone's settings — and our legitimate interest in keeping the service secure and answering your support requests.

Who can see it

Your partner
The person you are connected to can read your profile and everything shared into your joint story. That is the purpose of the app. Nobody else using Blaze can see any of it.
What your partner is not shown
A few things are deliberately held back from the person you are connected to: your wishlist, their photo of the day until you have posted yours, the title of a surprise date until the evening arrives, each other's answers in the pause tool until you have both written, and each other's answers to a Read together article's questions until you have both answered the same one. Where the database itself can enforce that, it does — a sealed time capsule cannot be opened early by anyone, its author included, and neither can its recording be fetched. Everywhere else on that list it is the app exercising restraint rather than the database refusing, because the two of you are allowed to read your shared space. We would rather write that down than let you believe otherwise.
Us
Access to stored data is limited to authorised members of the team that runs Blaze, and only where it is needed: to answer a support request you made, to investigate abuse or a safety report, or when the law requires it. We never use your content for advertising or to build a profile of you.
Google (Firebase)
Blaze runs on Google's Firebase platform — Authentication, Firestore, Cloud Storage, Cloud Functions and Cloud Messaging. Google processes this data on our instructions, under Google's own security and privacy commitments, and does not use it for its own purposes.
Google Sign-In and Sign in with Apple
Only if you choose one of them, and only to verify who you are at sign-in. Apple or Google learns that you signed in to Blaze; neither sees anything you write in it.
Apple or Google (purchases)
If you subscribe to Blaze Plus, the payment is taken by the App Store or Google Play under that store's own terms and privacy policy. We receive confirmation from the store that a subscription is active — which plan, and until when — so we can unlock it for you and the partner you are connected to. We never see your card details.
Apple or Google (checking the app is genuine)
Before it talks to our servers, Blaze asks Apple's App Attest service or Google's Play Integrity service to confirm that the copy making the request is a genuine, unmodified Blaze running on a real device, and attaches that confirmation to what it sends. It is how we keep scripts and repackaged copies of the app away from the data of people who use the real one. Apple or Google is told about the device and the app; it is told nothing about you, and nothing you have written. The page our account emails open — to confirm an address or set a new password — makes the same check through Google's reCAPTCHA, which looks at that visit in your browser; Google's privacy policy and terms apply to it.
Apple (the thirty seconds of a song)
When you tap a song the two of you have saved, Blaze plays a thirty second preview inside the app instead of handing you to Spotify, Apple Music or YouTube. To find that clip it asks Apple's public iTunes Search service for the recording, sending the song's title and artist — or, for an Apple Music link, the track's own id — and your store country. Nothing that identifies you goes with it: no account, no name, no Blaze identifier, and the request carries no sign-in of any kind. If no clip comes back, tapping the song opens the original link in the service it came from, and that service's own terms and privacy policy take over there. In a listening room the same service is asked for what you type into the room's search, with your store country and nothing else, and the clips are played straight from Apple. On iPhone, if you both choose whole songs from Apple Music, Blaze first asks your permission, then plays them through Apple's MusicKit on your own Apple Music subscription: Apple sees that as your own listening, under Apple's privacy policy. When your partner shares the song they are listening to, your phone asks the same service for that song's cover and clip, sending its title, artist and your store country. Blaze never reads your library, your playlists or your listening history. The one exception is Now playing, and only if you turn it on: on iPhone, while Blaze is open, it reads which song Apple's Music app is playing at that moment, to show your partner — see "What you're listening to".
YouTube (videos you watch together)
When a watch party is on a YouTube link, the video plays inside Blaze through YouTube's own embedded player, on each of your phones. That player is YouTube's, loaded from YouTube: it plays the video as YouTube serves it, with any ads YouTube shows, and Google receives what any embedded YouTube video sends it — the video, your device and connection, and YouTube's own cookies — under Google's privacy policy. Blaze sends it nothing about you: no account, no name, no Blaze identifier. To fill in the video's title when you paste its link, Blaze asks YouTube's public oEmbed service about that link and nothing else. A link to a plain video file plays in Blaze's own player, straight from wherever the link points. Blaze remembers the last few videos you put on in a list kept on your phone alone. A YouTube link saved as the song for the two of you plays the same way, in YouTube's own player shown on the screen, and only while that player is in view. By watching YouTube videos in Blaze you agree to the YouTube Terms of Service (https://www.youtube.com/t/terms), and Google's Privacy Policy (https://policies.google.com/privacy) governs what YouTube collects.
Websites you read together
When either of you opens a page shared on Read together, it opens in your phone's own browser view — Safari's in-app view on iPhone, a Custom Tab on Android, straight from that website, just as a link tapped in a message would. The site sees what any visit shows it — your IP address, the kind of device, and any cookies it set before — under its own privacy policy. Blaze does not load, read, copy or process the page itself, and sends the site nothing about you or your partner. What we keep is only what you share, described above: the link, its headline, the site's address, and who added it and when.
Legal requests
We will disclose information if the law compels us to, and no further than the law compels.

We do not sell your personal information, and we do not share it for cross-context behavioural advertising. There is nobody else in this list.

How it is protected

Everything in transit is encrypted with TLS. Everything stored on our servers is encrypted at rest by Google Cloud, which encrypts all Firebase data on disk by default. Every read and write is checked against security rules that confine data to the account that owns it and the partner it is shared with, and a new account is asked to confirm its email address.

Requests that reach our servers also carry a check that they came from a genuine, unmodified copy of Blaze on a real device, described under "Who can see it". It is aimed at scripts and repackaged apps rather than at you, and it tells us nothing about what you write.

Blaze does not use end-to-end encryption, which is what allows account recovery and Export Our Story to work. If that changes, this policy will say so.

No system is perfect. If a breach ever affects your data, we will tell you and the relevant regulator as the law requires.

Where it is stored

Your data is stored on Google Cloud infrastructure and may be processed in countries other than your own, including the United States. Where data leaves the European Economic Area or the United Kingdom, the transfer relies on the European Commission's Standard Contractual Clauses as incorporated into Google's data processing terms.

How long we keep it, and how to delete it

We keep your account and its content for as long as your account exists. There are four exceptions. A glimpse's photo is deleted once it has been looked at or its timer runs out, and the record of it is removed about a day later. And if you or your partner turn on disappearing messages in the chat, every message sent from then on is deleted — words, photos and files alike — once the length you chose has passed, from both of your phones and from our servers. And a song you share through Now playing is kept only while it is showing: it is deleted when it ends — at the latest about an hour afterwards — or as soon as you hide it or turn sharing off. And the rough position your phone sends when you tap phones to pair is deleted within a few minutes, whether or not a match was found. Blaze for Android neither shares what you are listening to nor pairs by tapping phones, so there only the first two apply.

You can delete your account at any time from Profile → Delete Account, inside the app. It asks you to confirm it is you, then removes your profile, disconnects you from your partner and releases your handle for someone else to claim. Our servers then delete the memories, photos, comments, questions, glimpses and other content you authored, together with your notification token. It cannot be undone, so export your story first if you want to keep a copy — Profile → Export Our Story. You can also ask for your account and its data to be deleted without using the app, by email: how, and what is deleted, is set out at https://blazecouples.com/delete-account.

One thing to be clear about: entries in a shared story belong to whoever wrote them, so deleting your account does not delete the memories your former partner wrote, nor their answers to questions you asked — a question you asked stays only if they answered it, because the answer is their writing. If you believe something associated with you has been left behind, email us and we will remove it.

Reports are kept separately. When a message, a person or an invitation is reported, or a safety concern is sent, the report and the copy of what it is about are kept for review for as long as we need them to act on the report and to meet our legal obligations — even if the original is later deleted, disappears or its author deletes their account.

Your rights

See and correct
Your profile is editable in the app at any time, in Profile → Your Profile.
Take a copy
Profile → Export Our Story produces a readable or JSON copy of your shared story, handed to your phone's share sheet so you decide where it goes.
Delete
Profile → Delete Account, as described above.
Withdraw permission
Notifications, photos, camera, microphone, calendar and location access can each be withdrawn in your phone's settings without affecting the rest of the app.

If the GDPR or UK GDPR applies to you, you also have the right to object to or restrict processing, the right to data portability, and the right to complain to your local supervisory authority. If you are in California, you have the right to know, delete and correct, and the right not to be discriminated against for exercising them — and, as stated above, we do not sell or share your personal information. Write to us and we will answer within the time the law allows, and never later than one month.

Children

Blaze is made for adults in a relationship and is not intended for children. You must be at least 18 years old to use it. Everyone must confirm their date of birth to use Blaze, whether they sign up with an email address or sign in with Google or Apple; anyone under 18 cannot create an account or use the app. We do not knowingly collect personal information from anyone under 18; if we learn we have, we delete the account and its data. If you believe a child has created an account, write to us and we will act on it. Our published child safety standards, including how to report a concern, are at https://blazecouples.com/child-safety.

Changes to this policy

If we change this policy we will update the effective date at the top and publish the new version at the address below. If a change materially affects how we handle your information, we will tell you in the app before it takes effect, so you can decide what to do about it.

How to reach us

Questions about this policy, requests about your data, or anything else: email us and a person will read it.

lowkey9.ai@gmail.com