Privacy policy
Updated October 15, 2026
This policy describes Kinblooma, a family-sharing app operated by DOINGNOTHING, LLC (Doing Nothing LLC), and this website. Contact us at [email protected] about privacy or your information.
Information you provide
Depending on the features you use, we process your account email and authentication information, profile name, family membership, invitations and requests to join a family, and the text, photos, videos, voice messages, replies and reactions you choose to share. Support and feedback requests include the information you send us. If you tell us that something does not seem right, we keep your report: which moment or reply it is about, the reason you chose, any note you add, and the account it came from. Reports reach the Kinblooma team, and you can also write to [email protected]. If you choose to stop seeing someone’s posts, we keep a record of who you blocked so that the choice can be applied; you can see and undo it in the app. We keep a record of who is in your family space, which family members and family spaces each moment is shared with, and whose posts you have chosen not to see, so that sharing and your choices work as you set them. We never read the contacts or address book on your phone.
When you use Safe, we also process the message you choose to have looked at, and the message you choose to pass to your family. The Safe section below explains this.
On Android, if you open a family’s invitation link before the app is installed, Google Play can pass that invitation to the app the first time it opens, so you do not have to look for the link again. The app checks this once, keeps only the invitation, and does not send the rest of that information to us.
Why we use it
We use this information to sign you in, maintain your private family space, deliver shared content, manage access, address support requests and protect the service against abuse. When you use the online service, our infrastructure automatically records technical logs, including IP addresses, approximate location inferred from IP (such as city, region and country), request times and paths, account or session identifiers, app or browser information, connection fingerprints, response times and error details. These logs support service operation, troubleshooting and protection against abuse. This automatic logging is separate from any optional diagnostic details you choose to include in feedback; turning off optional feedback diagnostics does not turn off service logs.
For each family space, we also keep a count of invitations: for each kind of invitation (to someone who lives with you, to a parent, for a family space of one’s own, or to connect two family spaces), how many were sent and how many led to a connection. These counts hold no person and no content. We use them to understand how inviting is being used. They are kept for as long as that family space exists.
When you use Safe, we also keep counts, for each family space, of how often Safe was used, to keep track of each family’s checks and to see whether Safe is helping. The Safe section below says what these counts hold.
Who can receive it
Content you share is available to authorized members of the relevant family space. What you share, whether photos, videos, text or voice messages, appears in the family space you share it in. If you are a parent who was invited into more than one family space, what you share appears in every family space you are in. For everyone else, a share you post stays in your own family space. When two family spaces are connected, a reply you write under a share that both can see can be seen in both; the app tells you before you send it.
Joining a family. Where the app offers it, you can ask to join a family with a six-digit code, a link or a QR code from the person who looks after that family space. When you ask, that person sees the name you entered and decides whether to let you in. We keep the request (who asked, which family, when, and whether it came from a code or a link) so that it can be answered; a request that is not answered lapses after 24 hours. To keep invitations safe, we also keep count of how often an account tries codes and links. Once you are in, you can see what the family has already shared (the words, photos, videos, voice messages and replies) as well as what is shared from then on. In the same way, family who join after you can see what you shared earlier.
Taking someone out of a family space. Where the app offers it, the person who looks after a family space can take a member out of it. That member stops seeing the family’s content straight away, and the family’s invitation link is closed. What they shared earlier stays with the family, so the family’s memories stay whole. Their Kinblooma account is not deleted. We keep a record that this happened, so that if they ask to join again, the person looking after the family can see that before deciding.
Our infrastructure providers process information to operate the service: Supabase provides app authentication, database and private media storage. Render hosts our subscription and family-entitlement service and our media service, which checks voice messages before they are delivered. Render also hosts the service that carries out account deletion. When you open your signed-in family space, the app sends your family identifier and an authentication token to that service to check access and plan status, including when purchasing is unavailable. Cloudflare hosts and delivers this website. Email providers process messages you send to our support address. Apple and Google may also receive operating records from the store’s own purchase software; see Subscriptions and purchase records. We may disclose information when legally required or necessary to address safety incidents and protect rights.
When you use Safe, our server sends the message you asked us to look at to OpenAI, which runs the artificial intelligence model that looks at it. The Safe section below explains what is sent and how it is handled.
Family members may save or share copies outside Kinblooma. Please only share content you have permission to share. Private family access is not a guarantee that recipients will keep their own copies private.
Subscriptions and purchase records
When you purchase or restore a subscription through the App Store or Google Play, Apple or Google processes the checkout. Purchases are handled by the App Store or Google Play. The store’s own purchase software talks to Apple or Google directly and may send them its own operating records. Kinblooma does not receive these records; Apple and Google handle them under their own privacy policies. Kinblooma receives and processes the subscription product identifier, the store’s proof of purchase (a signed transaction from the App Store, or a purchase token from Google Play) and subscription status, together with the account and family identifiers needed to verify the purchase and apply the plan to the correct family space. Our subscription service verifies purchases with the store to maintain plan status, including renewals, cancellations and refunds; for Google Play it also uses subscription notifications. Purchase and verification records are stored in our service databases; verification does not immediately delete the proof of purchase. Kinblooma does not receive the card number you enter into App Store or Google Play checkout.
Photos, camera, microphone and speech
Photo access is used when you choose a photo or video to share. Camera access is used only when you choose to take a photo or record a video in the app, and the photos and videos you take there are treated the same way as the ones you choose from your phone. Microphone access is used when you record a video, when you choose to say something instead of typing, and when you record a voice message. Videos you choose to share include their sound. You can change device permissions in system settings.
Photos and videos you upload may contain embedded information, such as capture time, device details or location, depending on the file and your device settings. In version 1.1 and later, before upload the app removes the place where a photo was taken from its embedded information. This is a best effort, not a guarantee. A file the app cannot read is uploaded as it is, and other details the camera writes into the file, such as the model or software version, are not removed. Videos may still carry the place where they were recorded; videos from action cameras, dash cameras and drones often keep the route as a separate track, and that track is uploaded with the video. Embedded information that is not removed may be visible in files made available to your selected family recipients. Review the files you choose to share and remove sensitive embedded information before uploading if needed.
When you say something instead of typing, your speech is turned into text on your device, and only the words you choose to share are sent. On iPhone, a short recording is made on the phone for this. It is sent to us only if you choose to share it as a voice message; otherwise it is deleted from the phone. Availability depends on your device and language. You can review the resulting text before sending it.
Recorded voice messages are described in the next section.
Recorded voice messages
This section applies when you send a recorded voice message. Where the app offers it, on iPhone and on Android, you can record a voice message of up to two minutes and send your own voice to your family. Nothing is sent until you choose to share it; you can listen first, or remove it and record again. Where voice messages are not offered, speaking only turns your words into text on your device, as described above.
Where it is kept and how it is checked. When you send a recorded voice message, the recording is uploaded and stored with our hosting provider, Supabase, in the same private storage as your family’s photos and videos. Before it reaches your family, a machine we rent from Render fetches it and checks that it really is a short sound recording: the right kind of file, and no longer than two minutes. The temporary copy on that machine is deleted as soon as the check is done. We do not give your recordings to OpenAI or to any analytics company.
Who can hear it. A voice message goes with the share or reply it belongs to. The current members of each family space that share reaches can play it, including family who join later; the section “Who can receive it” says which family spaces a share reaches. While there is a block between you and another person, whichever of you set it, that person cannot play it. Someone who leaves a family space, or is taken out of it, can no longer play it. When a voice message is reported, the person at Kinblooma who handles reports can listen to it; the report itself does not carry the sound.
Other people’s voices. If other people can be heard in your recording, their voices are stored with it. Please record only what you have permission to share.
After you take it back. You can take a voice message back at any time; once you do, your family will no longer hear it, and clearing the file can take a little while. The sound file is deleted, but a small check record stays until you delete your account: your account identifier, the file’s name, size and type, a fingerprint of the audio (a short code, not the sound itself), its length, an internal file id, a few times (such as when it was checked), and which share or reply it was attached to.
Upload and processing records. A record of each upload and of the processing work, including the file’s name (some file names contain your account identifier), is kept for as long as your account exists.
Voices that stay with the family. Voice messages you have shared stay with the family space after you leave it, after you are taken out of it, or after the family space is closed, in the same way as photos and text.
Deleting your account. When you delete your account, your voice files and the records above are deleted with it. A few records that hold only your account identifier and file names, not the sound, are among the limited records that “Retention and deletion” says are kept for up to 30 days afterwards. If something you shared is in a report that is still open, the deletion waits until that report has been resolved.
Backups. After a recording is deleted, it may remain for a time in backups kept by our hosting provider. We are not able to tell you for how long.
Recordings that were never sent. Sometimes a recording is uploaded when you choose to share it, but the share is not completed. A recording that was uploaded but never shared is removed after 30 days.
Safe
This section applies where the app offers Safe and you use it.
Safe lets you paste a message that seems a little off into Kinblooma and ask us to look at it with you, or ask your family to take a look. Checking a message and asking family are part of family membership; a family space without membership sees a few reminders and official help numbers instead. We only look at messages you choose to give us. Like Kinblooma accounts, Safe is for adults. We do not verify anyone’s age, so please keep to this rule; see "Children and family participation".
Your clipboard. When you open the Safe tab, and when you come back to the app while the Safe tab is showing, the app checks whether something has been copied, without reading it, so it can offer to look at it with you. On other tabs it does not check. The app reads what you copied only when you tap "Yes, please", "Paste that message", or "Ask family to take a look" with nothing typed, and even then nothing is sent until you agree on the next screen.
What is sent, and to whom. When you tap "Look at it with me", the app sends the message, the app’s language and your family space to our own server, signed in as you. Our server then sends the message, with our fixed instructions, the name of the language and a limit on the length of the answer, to an artificial intelligence model run by OpenAI. Apart from what the message itself says, we do not send OpenAI your account, your name, your family space, your device or anything else that tells OpenAI who you are. The message is sent exactly as you pasted it. Whoever wrote it and whoever it mentions, any names, phone numbers, account numbers or ID numbers in it are sent too, so please delete passwords, codes and ID numbers before you paste. Before your first check, the app shows a short note about this and sends nothing until you tap "Yes, please look"; if you tap "Not now", nothing is sent. If someone asks you to look at a message and has not added what Safe said, you can also ask Safe to look at it; the same note comes first, and the message is sent the same way.
How OpenAI handles it. We send the message to OpenAI only to answer this one request. Each time, we ask OpenAI not to keep the request as a stored record in our account; this does not mean OpenAI keeps nothing. To prevent misuse, OpenAI usually keeps it for up to 30 days, longer only if the law requires or to protect its services or other people. OpenAI’s published guidance says it does not use what we send to train or improve its models unless we choose to share it with OpenAI. We have not chosen to share it. OpenAI may process the message in the United States or other countries.
What we keep, and for how long.
- The message you check: we do not keep it, and we never keep or show the AI’s own wording. You see one of three results: "This looks suspicious", "Nothing suspicious that we could see", or "We are not sure. Let’s look at it with family".
- Only you see the result of your check. Others in your family see only that the family has one check fewer left this month.
- So that a repeated request is not charged twice: who asked, the family space, a request number, a code computed from the request number, the language and the message (the message itself is not kept), and which of the three results it was. Kept for 7 days.
- Checks that could not be done because of what was pasted: who, which family space and when, kept for 7 days to limit how many can be tried.
- When you ask family to take a look: the message is kept so that everyone else in that family space can read it, except anyone with whom there is a block either way. It is removed straight away when you take the request back or leave that family space; 30 days after you close it; or, if it is never closed, 90 days after the last thing anyone did with it.
- The outline of a request, without the message: who asked, who it went to, the language, the result type if one was attached, when it was sent and opened, who said they would look or stepped back, which one-tap reply was chosen, and how it ended. Kept until 13 months after the last action, then deleted.
- When family members open your request, we note it; you see only "A family member has seen it", not who or when.
- This version sends no notifications for Safe. One kind of record remains: if a family member said “I’ll look” and then lets go before anyone has replied — or leaves the family space, is removed, is blocked from you, or deletes their account — we note, for each of the other family members you asked, that someone let go: which request, when, and who. It never holds your message. The name is removed when you withdraw or close the request, when the message is cleared, or when that person deletes their account; the record itself is deleted 13 months after the request’s last activity.
- Counts: for each family space, how many checks were used in each membership month, and how many checks and requests for help there were in each calendar month — no person, no content, no time of day. Kept for 13 months. In a family space with one person, these counts are that person’s. If you belong to two family spaces with membership, a check is counted in the one with more checks left. We use these counts only to keep track of each family’s checks and to see whether Safe is helping, for example whether a family comes back to it; nothing else is kept for this.
- Our server writes no log line with your message, your account or your family space for Safe.
When you delete your account, what Safe holds about you is deleted with it: your checks, any request you sent together with its message, and your replies. Where a record on someone else’s request named you, your name is removed. The counts kept for the family space stay, because they hold no person.
We do not use Safe data for advertising or to train any model of our own.
Help numbers near you. To show help numbers for your area, the app may send your phone’s country or region setting (for example "TW"). We use it only to choose what to show and do not keep it.
On your phone. The app remembers only that you have read the note before your first check. You can take this back at any time: tap ‘Ask me first next time’ at the foot of the Safe tab, and the note will be shown again before your next check. Taking it back does not recall messages already sent.
Safe looks carefully but cannot promise to be right every time. For anything important, talk it over with family.
Children and family participation
Kinblooma accounts are for adults. Children may participate alongside a parent or guardian using the adult’s account; they must not create or independently operate an account. Adults are responsible for the information they choose to share about children. Contact us if you believe a child has independently supplied personal information or if you want information about a child removed.
Retention and deletion
Account and family content is kept to provide the service until it is removed or deletion is requested. In version 1.1 and later, you can take back something you shared; after that your family no longer sees it. Any photo, video or voice message attached to it is cleared in the background, which can take a little while. Copies a family member has already saved stay with them. You can ask to delete your account inside the app. You can also request account deletion or removal of specific personal data using our account and data deletion page, including after uninstalling the app. Removal can take some time; the account and data deletion page says how long and what can make it wait. Once an account deletion is complete, the limited records left over from it are kept for up to 30 days and then cleared. Apart from that, limited information may need to be retained for legal obligations, security investigations or resolving disputes. Backup removal may occur separately from removal of active data. We will explain any applicable retention and remaining steps when handling your request; we do not promise immediate deletion from every backup.
If you leave a family space, you will no longer see it. What you shared there, including replies, stays available to its remaining members, so delete anything you want removed before you leave.
If you delete your account and you look after a family space, you can close it instead of handing it over. A closed family space keeps its members, who can still see what they and the other remaining members shared, but nothing new can be shared there, and no one can take it over later. What you shared is removed with your account.
Recorded voice messages and Safe keep some records for periods of their own; the sections “Recorded voice messages” and “Safe” say which records and for how long.
Your choices
You can contact us at [email protected] to request access, correction, deletion or a copy of your information, and to raise a privacy concern. Rights depend on your location. Where applicable, you may also object to processing, request restriction, withdraw consent or complain to your local data protection authority. We may verify your control of the account before acting.
International processing and security
Service providers may process information outside your country. We use access controls and private media storage to restrict access. No system can guarantee absolute security. Please do not send passwords or verification codes to support.
This website and changes
This website does not include advertising trackers or optional analytics scripts. The hosting provider processes network information needed to deliver and protect the site. We will update this page when our practices change.