Privacy Policy

Bloom Dating, Inc.Effective March 19, 2026Updated October 29, 2026

Bloom Dating, Inc. ("Bloom," "we," "us," or "our") operates the Bloom mobile application and website (together, the "Service"). This Privacy Policy explains what personal information we collect, how we use and share it, your rights regarding your information, and how to contact us.

We process some categories of information that are legally classified as "sensitive" - including information that may reveal sexual orientation, ethnicity, religion, or health, the content of your messages, and, if you choose to verify your profile, face data used for selfie verification. We take this responsibility seriously and have designed our practices to protect your privacy at every step. We encourage you to read this policy carefully.

What changed in this version (October 6, 2026). We rewrote this policy so it matches how Bloom works today. The main changes: a full Biometric Data section for optional selfie verification, including a retention and destruction schedule (Section 18); a description of the automated safety review we run on chat messages, voice messages, and photos (Section 16.6); a complete list of the service providers and AI providers that process your data (Sections 6.2 and 16.3); corrections about location (Bloom does not use your device's GPS) and device checks; how push notifications carry message previews (Section 19); and updated website analytics and retention details (Sections 8 and 9). If you already had a Bloom account before this date, these changes take effect for you 30 days after we notify you (Section 25).

Update (October 11, 2026). We clarified which automated checks apply to which photos (Sections 6.2 and 16.6), that our moderators can play a voice message that has been reported (Section 3.1), how long we keep ban records after an account is deleted (Section 9), and how a shared calendar you subscribe to from another calendar app works (Sections 6.6 and 14).

Update (October 22, 2026). If a profile photo includes the place it was taken, we now use the country and, for some countries, the state or province as a fraud-prevention signal. We never store the photo's location itself (Sections 3.2, 4, 9, 13, and 16.6). Couples can also add an optional place and date to a shared album photo. We store only the words of that tag, never coordinates (Sections 3.1, 3.2, 4, 6, 9, 13, and 14). We also changed what happens to shared Relationship Mode content when a partner deletes their account: the other person keeps the shared photo albums, and the rest of that relationship's shared content is deleted (Sections 9 and 14).

Update (October 29, 2026). If you turn off AI personalization, your messages and answers are now also left out when the other person in the conversation uses Notes suggestions, date suggestions, or Insights scans (Sections 16.2 and 16.4).

1. Who We Are

Bloom Dating, Inc. is a Delaware corporation headquartered in Utah.

Contact Information:

Email: privacy@bloom.date
Mailing Address: Bloom Dating, Inc., 10102 S Redwood Rd #95177, South Jordan, UT 84095
Website: bloom.date

For purposes of applicable data privacy laws, Bloom is the "controller" or "business" responsible for your personal information.

2. Scope of This Policy

This policy applies to all personal information we collect through:

The Bloom mobile application (iOS, Android, and web versions)
Our website at bloom.date
Communications with us (email, in-app support)

This policy does not apply to third-party websites, apps, or services linked from Bloom, even if you access them through our Service. We encourage you to review the privacy practices of any third party before sharing your information with them.

3. Information We Collect

We collect three categories of information: information you provide directly, information collected automatically, and information from third parties.

3.1 Information You Provide

Account & Profile Information

When you create an account and set up your profile, you provide:

Name, email address, date of birth, and gender
Profile photos (up to 6) and optional photo captions
Bio, height, job title, school, and hometown
Optional details you choose to add: ethnicity, religious beliefs, political views, whether you have or want children, and your drinking, smoking, cannabis, and drug use
Location: the city or ZIP code you choose (see "Location Information" in Section 3.2)
Dating preferences (age range, gender preferences, distance range)

Waitlist (Website)

Before Bloom launches, you can join our waitlist at bloom.date. When you do, we collect:

Your name and email address
Your gender (Male or Female), which helps us understand and balance the makeup of the early community before launch
Whether you are interested in Bloom for dating or for your relationship
Your ZIP code, which we use to work out your U.S. state
Your country, if you are outside the U.S. (instead of a ZIP code)
The country and state your connection comes from, inferred from your IP address at sign-up (we do not store the IP address itself), which we use with the other details above to filter out fake and automated signups
How you heard about us
Basic attribution data about how you reached the site (the referring URL and any campaign parameters in the link you followed)

We use this information to notify you when Bloom is available, to sequence our launch by geography, to understand the makeup of our early audience, and, with your consent, to send occasional updates before launch. We do not sell it. You can withdraw that consent with the unsubscribe link in any update we send, and you can ask us to delete your waitlist entry at any time by emailing privacy@bloom.date.

Communications

When you use our messaging features, we process:

Messages you send and receive with matches and partners
Date plan suggestions and responses
Any content you share in chat (text, photos, and voice messages)

Voice Messages in Chat

You can record and send short voice messages (up to 2 minutes) in your chats. When you do, we process:

The audio recording itself, which is stored in Bloom's private storage and playable only by you, the person you sent it to, and, if the message is reported, our moderators, through short-lived secure links
For chats between matched singles: an automated safety review of every voice message. The audio is transcribed to text by a speech service, and the transcript is checked against our Community Guidelines by an AI service. Messages are delivered right away and removed if the review finds a violation.
For chats in Relationship Mode: voice messages are reviewed only if you or your partner reports one.

The transcript exists only for safety review and is never shown to you, the recipient, or other users. See Section 16.6 for how automated safety review works, Section 6.2 for the providers involved, and Section 9 for retention.

Voice Onboarding Audio

If you choose the voice option to set up your profile, we process:

The audio you speak during the onboarding conversation (your voice and any background sound captured by your microphone while a voice session is active)
The text transcription of that audio, generated by a third-party voice service so the conversation can move forward
The same text transcription is then processed by AI to populate the profile fields you discussed (name, location, bio, prompt responses, etc.)

Voice onboarding is optional. You can complete your profile by text chat or by traditional forms instead, and you can switch between modes at any time. See Section 16.3 for the third-party voice and AI providers involved, and Section 9 for retention periods.

If you use the optional dictation feature during text onboarding (the microphone icon in the message field), your device's built-in speech recognition turns your speech into text. Depending on your device and its settings, Apple or Google may process that audio on the device or on their own servers under their privacy policies. Bloom receives only the resulting text; the dictation audio is never sent to Bloom's servers.

Selfie Verification (optional)

If you choose to verify your profile to earn the Verified badge, we ask you to read a written notice and give your consent first. We then process:

A short live selfie video, captured by your device's front camera during an on-screen challenge (the "liveness check"). It confirms that a real person is in front of the camera and not a photo, a replay, or a mask. The video streams directly from your device to our verification provider and is not stored by Bloom.
One still image taken from that video (the "reference image"), which we store encrypted in private storage.
A comparison of the face in your reference image with the faces in each of your profile photos, at verification and again each time you add a profile photo while you are verified. This comparison measures facial geometry, which some state laws treat as biometric data.
Scores and records for each attempt (time, outcome, the match and liveness confidence scores, and which profile photos were checked).
A record of your consent, including the version of the notice you agreed to and when.

Selfie verification is optional, and your profile works fully without it. Other users can see whether you are verified; they cannot see your reference image, your scores, or your attempt records. We never sell your face data and never use it to train AI models. Section 18 explains how we keep and destroy it.

Relationship Mode Data

When you and a partner use Relationship Mode, you provide:

Partner pairing information (invite codes)
Shared photo album content (photos uploaded by you or your partner)
Optional place and date tags on shared album photos, such as "Kyoto, Japan · October 2025," added by you or your partner (see "Location Information" in Section 3.2), and your "Tag my new photos" setting for each shared album, which only you can see
Shared calendar events (dates, anniversaries, activities)
Shared lists (restaurants, date ideas, and custom lists you create)
Date plans created with your partner
Private notes you write about your relationship

Payment Information

If you subscribe to Bloom Premium, your payment is processed by Apple (App Store), Google (Play Store), or our payment processor. We receive confirmation of your subscription status but do not store your credit card number, bank account details, or other payment credentials.

Support & Feedback

If you contact us for support, we collect the information you provide in your message, along with your email address and any attachments you send.

3.2 Information Collected Automatically

When you use the Service, we automatically collect:

Device & Technical Information

Device type, operating system, and version
App version
Device identifiers (for push notification delivery)
IP address
Browser type (for web access)

Fraud Prevention and Safety Signals

To detect and prevent fake accounts, scams, and ban evasion, we collect and analyze:

A privacy-preserving device signal: an app-scoped device identifier that we store only in a hashed, non-reversible form. This is not an advertising identifier, and we never use it for advertising or to track you across other companies' apps or websites.
The IP address associated with your account at sign-up, and the country and network operator we look up from it using a database kept on our own servers (your IP address is not sent to a third party for this lookup).
The country, and for some countries the state or province, where a profile photo was taken, if the photo includes that location. Your phone reads the location saved in the photo, keeps the exact location only in its memory, and rounds it to the nearest tenth of a degree (points on a grid about 7 miles, or 11 km, apart) before sending it. Our servers turn it into a country and region using a public map of country and state borders, and then discard it. The location is never sent to a third party or a mapping service. We store only the country and region. Our moderators see them when they review an account for fraud; other users never see them, and the app does not show them to you, though you can request them like any other information we hold about you (Section 12). We delete them when you remove that photo or delete your account. We do this only for profile photos, not for photos you share in chats or albums. The photos themselves are uploaded with their location removed.

We use these signals only for trust and safety purposes, such as preventing fraud, fake profiles, and abuse. They are first-party safety data, not advertising or cross-app tracking.

Usage Information

Features you use and actions you take (such as profiles viewed, likes sent, matches made)
Date and time of your activity
Time spent in the app

Location Information

Bloom does not read your device's live location or GPS, and does not ask for your device's location permission. We use:

The city or ZIP code you choose for your profile, together with the center point of that city or ZIP code (looked up through Google Places). We use it to show your area on your profile, to calculate distance for matching, and to suggest nearby date spots.
General location (country and, for the website, state or region) inferred from your IP address, used for fraud prevention and to plan our launch by geography.
The country and region where a profile photo was taken, if the photo includes that location, used only for fraud prevention (see "Fraud Prevention and Safety Signals" above). You can leave a photo's location out. On iPhone, the photo picker includes location unless you turn it off under Options in the picker. On Android versions whose photo picker supports it, the picker asks whether to include location when you add a profile photo, and you can change that answer in the picker; on other Android versions, the picker removes location and we receive none.
An optional place tag on a shared album photo. When you add photos to a shared album and a photo includes the place it was taken, the app can suggest a tag such as "Kyoto, Japan · October 2025." The suggestion appears only on the phone of the person adding the photo and is never more specific than a city. It starts switched off, unless you have turned on "Tag my new photos" for that album, in which case it starts switched on and the upload screen says so. Either way, before the photos are added you can switch it off or make it less specific (region or country). To name the place, your phone first rounds the photo's location to a grid about 1.4 miles (2.2 km) apart, then asks its built-in location service (Apple's on iPhone, Google's on Android) to turn that rounded point into a city, region, and country. This happens when you add a photo that includes a location, before you decide whether to keep the suggestion, so Apple or Google receives the rounded point from your phone (see Section 6.2). Bloom never receives the location, and the photo itself is uploaded with its location removed. If the suggestion is switched off when the photos are added, Bloom saves nothing. If it is on, we store only the words of the tag and its month and year (or the day, if you choose it). Either partner can also type a tag, and either partner can edit or remove a tag while you are together. Your partner can see the tag; other users cannot. For what happens to tags after a relationship ends, see Section 14.

You can change your city or ZIP code at any time in your profile.

3.3 Information From Third Parties

Social Login Providers

If you choose to create your account or sign in using a third-party social login provider, we receive limited information from that provider to authenticate you and set up your account:

Provider	Information Received
Apple (Sign in with Apple)	Name (if you choose to share it), email address (or Apple's private relay email), and a unique account identifier
Google (Sign in with Google)	Name, email address, and profile photo URL
Facebook (Continue with Facebook)	Name and email address

We use this information only to create and authenticate your Bloom account. We do not access your contacts, friends lists, posts, or any other data from these providers. You can choose to use email/password registration instead of social login.

Each provider's data practices are governed by their own privacy policies: Apple, Google, and Facebook.

4. Sensitive Personal Information

Several categories of information we collect are classified as "sensitive" under US state privacy laws. We want to be transparent about this:

Sensitive Data Category	How It Arises in Bloom
Sexual orientation	Inherently revealed by your gender and matching preferences
Racial or ethnic origin	The ethnicity you choose to add to your profile (optional)
Religious or philosophical beliefs	The religious beliefs you choose to add to your profile (optional)
Health information	Optional profile details about drug use, and anything health-related you choose to write in your profile or messages
Contents of communications	Your messages with matches and partners
Sex life or dating activity	Relationship status, dating history, date plans
Biometric information	Only if you opt in to selfie verification. We store a reference image of your face and use our provider to compare its facial geometry with your profile photos (see Sections 3.1 and 18).

Your consent matters. Before we process your sensitive personal information, we ask for your explicit opt-in consent during account setup, and we ask for a separate written consent before selfie verification. You can review your consent choices in Settings > Privacy.

Bloom does not collect precise geolocation. The location we use is the city or ZIP code you choose and the center point of that area, not your device's position. When a profile photo includes the place it was taken, the exact location is read only on your phone, rounded to a grid about 7 miles (11 km) apart before it leaves the device, and we keep only the country and region it falls in. A place tag on a shared album photo is stored as words, such as a city name, and never as coordinates; the point your phone sends to Apple or Google to suggest that name is rounded to a grid about 1.4 miles (2.2 km) apart first.

Limiting use of sensitive information. California residents have the right to limit our use of sensitive personal information to what is necessary to provide the Service. You can exercise this right in Settings > Privacy or by contacting us at privacy@bloom.date. When you exercise this right, we restrict processing of your sensitive data to core service functions only (matching, messaging, and relationship features you have activated).

5. How We Use Your Information

We use your information for the following purposes:

To Provide and Operate the Service

Create and maintain your account
Display your profile to potential matches (Single Mode)
Deliver messages between you and your matches or partner
Enable partner pairing and shared features in Relationship Mode
Process date plan suggestions and shared calendars, lists, and photos
Deliver push notifications about matches, messages, and relationship updates
Process your subscription and manage billing through our payment partners

To Improve and Personalize the Service

Suggest potential matches based on your preferences and profile
Improve our matching algorithms and features
Analyze how users interact with the Service to identify improvements
Troubleshoot bugs and technical issues
Power AI features including conversational onboarding, date suggestions, journeys, and Notes and Insights scans (see Section 16 for details and opt-out options)

To Keep You and Others Safe

Automatically review photos, chat messages between matched singles, and voice messages for Community Guidelines violations and illegal content (see Section 16.6)
Compare your selfie with your profile photos, if you choose to verify (see Section 18)
Detect and prevent fraud, fake profiles, and scam activity
Enforce our Terms of Service and Community Guidelines
Respond to reports of harassment, abuse, or policy violations
Confirm that users are 18 or older, based on the date of birth they give us
Comply with legal obligations, including the Utah Online Dating Safety Act

To Communicate With You

Respond to your support requests and inquiries
Send administrative messages about your account or the Service
With your consent, send promotional messages about new features (you can opt out at any time)

We do not use your personal information for automated decision-making that produces legal or similarly significant effects without human involvement. Automated safety review can block a photo or hide a message, and a failed photo comparison can pause your Verified badge until you verify again, but warnings, suspensions, and bans are decided with human review. If we introduce automated matching or profiling features that could have significant effects, we will provide notice and, where required by law, obtain your consent or offer an opt-out.

We share your information only in the following circumstances:

6.1 With Other Users

Single Mode: Your profile information (photos, name, age, location, bio, and lifestyle details) is visible to other users browsing profiles. Your dating preferences are used for matching but are not displayed to other users. Messages are visible only to you and the person you are communicating with.
Relationship Mode: Shared content (photos and any place and date tags on them, calendar events, lists, date plans) is visible to both you and your connected partner. Private notes are visible only to you.

6.2 With Service Providers

We use the following third-party service providers who process your information on our behalf under strict contractual obligations:

Provider	Purpose	Data Processed
Supabase (on AWS, US)	Database, authentication, file storage, real-time messaging, and the servers that run Bloom's backend code	All account data, messages, photos, voice messages, shared content
Google Firebase Cloud Messaging and Apple Push Notification service	Push notification delivery	Device tokens and notification content, which for chat messages includes the sender's first name and the first 100 characters of the message (see Section 19)
Anthropic (Claude, US)	AI features (onboarding, profile extraction, date suggestions, journey sessions, Notes and Insights scans) and automated safety review of chat messages and voice message transcripts	See Section 16.3
Amazon Web Services - Bedrock (US)	Runs Anthropic's Claude models as a backup when Anthropic is unavailable	See Section 16.3
ElevenLabs (US)	Voice transport for the optional voice onboarding mode	Microphone audio during a voice onboarding session, transcripts, and Bloom's spoken replies; your Bloom user ID to link the session
Amazon Web Services - Rekognition (US)	Optional selfie verification (liveness check and face comparison) and automated review of profile photos, shared album photos, and chat photos between matched singles for nudity, violence, and other prohibited content (Relationship Mode chat photos are not sent to Rekognition)	Selfie video, reference image, and the photos it reviews
Amazon Web Services - Transcribe and S3 (US)	Speech-to-text for automated safety review of voice messages	A temporary copy of the voice message audio, deleted when transcription finishes (with an automatic 7-day cleanup as a backstop), and the transcript
Amazon Web Services - Simple Email Service (US)	Sending account emails and waitlist updates	Email address, name, and message content
Microsoft PhotoDNA (US)	Detecting known child sexual abuse material in every uploaded photo, including Relationship Mode chat photos	Each uploaded photo
Google Places (US)	City and ZIP code lookup, and nearby date spot search	The text you type when choosing a location, and your area's center point for nearby searches
Apple / Google	In-app subscription billing	Subscription status and transaction IDs (not payment credentials)
RevenueCat (US)	Managing subscription status across Apple and Google	Your Bloom user ID and purchase records
Apple / Google / Facebook	Social login	Name, email address, account identifier (only if you use social login)
PostHog, Inc. (US)	Product analytics and feature flags in the app and on the website, and sampled session replay on the website (see Section 8)	Pseudonymous user ID, events and screens, and account traits (subscription status, single or relationship mode, state, sign-up date); for waitlist signups, a one-way hash of your email, gender, state or country, and how you heard about us
Sentry (Functional Software, Inc., US)	Error monitoring and diagnostic logs for the app, servers, and website; sampled session replay on the website	Your Bloom user ID, device and app details, diagnostic logs, and, on the website, replays with page text and inputs masked
Vercel (US)	Website hosting, website analytics and performance measurement, and bot protection on the waitlist form	IP address, browser details, pages visited, and approximate location from IP address
Ahrefs (Ahrefs Pte. Ltd., Singapore)	Website traffic analytics	Pages visited, referrer, and browser details
Google AdMob (Google LLC, US)	Non-personalized (contextual) ads for free-tier users in the app	IP address, device and app context; no advertising identifier (see Section 7)
Slack (Salesforce, US)	Internal alerts to the Bloom team	New sign-up notices with first name and city or state, and error alerts that may include a user ID

Your phone's location service. When you add a photo that includes a location to a shared album, your phone's built-in location service (Apple's on iPhone, Google's on Android) receives that location, rounded on your phone to a grid about 1.4 miles (2.2 km) apart, so the app can suggest a place tag, whether or not you keep the suggestion. Apple and Google are not Bloom's service providers for this: your phone's operating system sends the request, and Apple or Google handles it under its own privacy terms. Bloom does not receive the location.

Each service provider may use your data only to provide its service to us, under its contract or terms with us. Our AI providers process your data under API terms that do not allow them to train their models on it (see Sections 16.3 and 16.6).

6.3 For Legal Reasons

We may disclose your information if we believe in good faith that disclosure is necessary to:

Comply with applicable law, regulation, or valid legal process (such as a subpoena or court order)
Protect the safety, rights, or property of Bloom, our users, or the public
Detect, prevent, or address fraud, security, or technical issues
Enforce our Terms of Service
Report apparent child sexual exploitation to the National Center for Missing & Exploited Children (NCMEC), as federal law requires. A member of our team reviews and files each report.

Government and Law Enforcement Requests. When we receive a request from a government, law enforcement agency, or other public authority for user data, we follow these practices:

Legal review. We review every request for legal validity and confirm that it is supported by an appropriate legal basis (such as a valid subpoena, search warrant, court order, or other lawful process applicable to the request) before responding.
Data minimization. We disclose only the minimum information specifically required to satisfy the request. We do not voluntarily provide additional data beyond what the request lawfully compels.
Right to challenge. We reserve the right to challenge or refuse requests that we believe are unlawful, overbroad, vague, or inconsistent with applicable privacy laws or constitutional protections. Where appropriate, we will work with counsel to formally object to or narrow such requests.
Documentation. We maintain internal records of any government or law enforcement requests we receive and our responses, including the requesting agency, the legal basis claimed, the scope of data requested, and the action we took.

We will notify affected users of a request for their personal information when we are legally permitted to do so, unless we believe notice would create a risk of harm to a person or impede an active investigation.

6.4 Business Transfers

If Bloom is involved in a merger, acquisition, bankruptcy, or sale of assets, your information may be transferred as part of that transaction. We will notify you by email or prominent notice in the app before your information is transferred and becomes subject to a different privacy policy.

We may share your information in other ways if you give us specific, informed consent.

6.6 At Your Direction

If you subscribe to your shared calendar from another calendar app (see Section 14), we send your couple's shared calendar events to that app when it asks for them. This happens only because you set it up, and you can stop it in Settings. We are not paid for it, and it is not used for advertising.

We do not sell your personal information. We have not sold personal information in the preceding 12 months, and we do not plan to sell personal information.

We do not "share" your personal information for cross-context behavioral advertising as that term is defined under the California Consumer Privacy Act. We do not use your data to serve targeted advertising based on your activity across other websites or applications.

Free-tier users see ads from Google AdMob. Every ad request asks Google for non-personalized ads only. The Android app does not have permission to read the advertising ID, the iOS app does not ask to track you, and the Facebook SDK we use for login has app-event logging and advertising-ID collection turned off. Google still receives your IP address and basic device and app information when it serves a contextual ad.

If this changes in the future, we will update this policy, provide notice, and offer you the ability to opt out before any sale or sharing occurs.

8. Cookies and Tracking Technologies

In-App: The Bloom mobile application does not use cookies. It sends product analytics events to PostHog, tied to a pseudonymous user ID. You can turn app analytics off in Settings.

Website (bloom.date): We do not use advertising cookies or ad pixels. The website uses:

Technology	What it stores or collects	When it runs
Sign-in cookies (Supabase)	Your session after you confirm an email link	Only on account pages
PostHog analytics	A first-party cookie and browser storage entry with a random ID; page views, clicks, and waitlist signups; sampled session replay (Section 8.1)	Off if your browser sends Global Privacy Control or Do Not Track
Sentry error monitoring	Error reports; sampled session replay with page text and inputs masked	Error reports always; replay off with Global Privacy Control or Do Not Track
Vercel Analytics and Speed Insights	Page views and performance timings, without cookies	Always
Ahrefs Web Analytics	Page views and referrers, without cookies	Always
Vercel BotID	Signals from your browser to tell people from bots	Only when you submit the waitlist form
Browser storage (first-party)	Your light or dark theme choice, and the campaign link that brought you to the site (kept 90 days)	Always

PostHog traffic is routed through our own domain.

Global Privacy Control (GPC) and Do Not Track. If your browser sends either signal, we turn off PostHog and session replay for your visit, and we treat the signal as a valid opt-out of any sale or sharing of personal information and a request to limit the use of sensitive personal information. Vercel and Ahrefs analytics keep running because they do not use cookies, do not track you across other sites, and are used only to count and improve our own pages.

8.1 Session Replay

To find bugs and confusing steps on our website, we record a small, randomly chosen share of website visits. A recording rebuilds the pages you saw and what you did on them (clicks, scrolls, page changes) so our team can replay a visit and see what went wrong.

On the website (bloom.date). PostHog and Sentry each record a sample of visits. In both, whatever you type into a form field (such as your name or email on the waitlist form) is masked before it leaves your browser. PostHog recordings show the page text, which on our public pages is our own marketing and legal copy; Sentry recordings mask page text as well. We never record the admin area. Recordings do not include audio, video, or your camera.

In the Bloom app. The app does not record sessions in production today. If we turn it on, we will update this policy and give you notice first, and recordings will mask all text and blur all images.

Retention and use. PostHog recordings are kept for 30 days and Sentry recordings for up to 90 days, and then they are deleted. We use them only to fix bugs and improve the website. We do not sell them, share them with advertisers, or use them to train AI models.

Your choice. If your browser sends Global Privacy Control or Do Not Track, we do not record your visit. You can also email privacy@bloom.date and we will exclude your visits.

9. Data Retention

We retain your information only as long as necessary for the purposes described in this policy, or as required by law. Here are our retention practices by data category:

Data Category	Retention Period
Account & profile data	Until you delete your account. Deletion has a 30-day grace period (you can sign back in to restore your account), and then we delete your data.
Onboarding conversations (text or voice AI onboarding transcripts)	Deleted 90 days after the conversation finishes or is abandoned. The profile fields it produced are kept as account data. ElevenLabs may keep voice onboarding audio and transcripts for up to 30 days.
Messages and photos in chat	Until you delete your account (see Section 14 for shared data details)
Voice messages in chat	Until you delete your account. If a voice message or chat photo is removed for a safety violation, we delete it 30 days after the decision. Temporary copies at our speech provider are deleted when transcription finishes, and within 7 days at most.
Safety review records (voice message transcripts, flagged text, and photo review results)	A transcript of a voice message that was not reported and passed review is deleted after 90 days. Flagged text is kept for 30 days after a moderator resolves it. Records of content that broke our rules or was reported are kept as safety records (see the Safety & fraud records row).
Selfie verification data (reference image, comparison scores, attempt records)	See Section 18.
Biometric consent record	Kept for as long as we keep your verification data and for the period the law requires to show that you consented.
Shared photo albums (photos, photo details, and each partner's first and last name at the time the relationship ended, in Relationship Mode)	Until both partners have deleted their accounts or the retention period ends (see Section 14)
Other shared content (calendars, lists, Journeys)	Until either partner deletes their account or the retention period ends (see Section 14)
Keepsake archive	2 years after relationship ends, unless you request earlier deletion or choose to retain
Date plans and private notes	Until you delete your account. Date plans you made with a match or Relationship Mode partner, and private notes tied to that partner, are also deleted if that person deletes their account.
Push notification records (title and text of each notification we send you)	The message preview in a chat notification is removed after 30 days, and the record is deleted after 12 months
AI usage records (which feature ran and its cost, with no content)	180 days
Usage & analytics data	24 months from collection, then aggregated or deleted
Device tokens	Until you log out or the token stops working (Section 19)
Support communications	3 years from resolution
Payment/subscription records	As required by tax and financial regulations (typically 7 years for transaction records)
Consumer request records	At least 24 months, as required by California law
Consent records (sensitive data and AI consent)	Kept for as long as needed to show the consent we relied on
Album photo place and date tags	Until a partner removes the tag while you are together, or the photo is removed. A tag is deleted together with its photo. After a relationship ends, tags stay with the keepsake (see Section 14).
Profile photo country and region (fraud prevention)	Until you remove that photo from your profile or delete your account. The photo's location itself is never stored.
Safety & fraud records	Up to 5 years for enforcing bans and complying with legal obligations, except ban records, which follow the next row
Ban records (the account ID, the reason, the ban and lift dates, and a moderator's notes)	Kept while the account exists. If a banned account is deleted, we delete the moderator's notes and keep the rest for two years after the account is permanently deleted (that is, after the 30-day grace period), so we still have a record of the enforcement action if the ban is questioned, or becomes part of a complaint or a legal claim, and then delete it. This schedule does not apply to bans for fraud or child sexual exploitation, or to a ban connected to a legal claim; we keep those for as long as we need them to meet a legal obligation or defend a legal claim.

When your data is no longer needed, we delete or securely anonymize it. Anonymized data (from which you cannot be identified) may be retained indefinitely for aggregate analytics.

Fraud-ban records and account deletion. There is one narrow exception to deleting device and sign-up data. If we ban an account for fraudulent activity, we keep a minimal, non-identifying record of the device and sign-up signals tied to that account even after the account is deleted. This record contains only irreversible hashes and the fact of the ban, with no name, email, photos, or other profile information. We keep it for one reason only: to detect and prevent the banned person from returning under a new account (ban evasion). Privacy laws allow a business to keep information it needs to detect and prevent fraud and protect the security of its service, even after a deletion request, and we keep this record on that basis. Accounts deleted for any other reason leave no device or sign-up record. A ban record, if there is one, follows the Ban records row above.

Evidence of child sexual exploitation. If a photo or message is identified as apparent child sexual abuse material, we preserve it and the related records securely, separate from the rest of the Service, and report it to NCMEC as federal law requires. This evidence is kept after account deletion for as long as the law requires or allows for that purpose.

10. Data Security

We implement reasonable administrative, technical, and physical safeguards to protect your personal information, including:

Encryption of data in transit (TLS/SSL) and at rest
Access controls limiting who within our organization can access user data
Regular review of our data collection, storage, and processing practices
Secure authentication through Supabase Auth

No method of transmission over the internet or electronic storage is 100% secure. While we strive to protect your information, we cannot guarantee absolute security. If you become aware of a security vulnerability, please contact us immediately at security@bloom.date.

11. Your Privacy Rights

Depending on where you live, you may have some or all of the following rights regarding your personal information. We honor these rights for all users regardless of location, except where noted:

Right to Know / Access. You can request a copy of the personal information we hold about you, including the categories and specific pieces of information, the sources, the purposes for processing, and the categories of third parties with whom we share it.

Right to Delete. You can request that we delete your personal information, subject to certain legal exceptions (such as data needed to complete a transaction, comply with a legal obligation, or detect security incidents). See Section 14 for how deletion works with shared data.

Right to Correct. You can request that we correct inaccurate personal information. You can also correct most profile information directly in the app.

Right to Portability. You can request a copy of your personal information in a structured, commonly used, machine-readable format.

Right to Opt Out of Sale/Sharing. We do not sell or share your personal information, but if we ever do, you will have the right to opt out.

Right to Limit Sensitive Data Use. You can request that we limit our use of your sensitive personal information to what is necessary to provide the Service.

Right to Non-Discrimination. We will not discriminate against you for exercising your privacy rights. You will not receive different pricing, a different quality of service, or be denied service for making a privacy request.

Right to Appeal. If we deny your privacy request, you may appeal by contacting us at privacy@bloom.date with the subject line "Privacy Appeal." We will respond within the timeframe required by applicable law. If you are unsatisfied with our response, you may contact your state's Attorney General.

12. How to Exercise Your Rights

You can exercise your privacy rights in any of the following ways:

In-app: Settings > Privacy > Manage My Data
Email: privacy@bloom.date
Mail: Bloom Dating, Inc., 10102 S Redwood Rd #95177, South Jordan, UT 84095

We will verify your identity before processing your request. For requests made via email, we will ask you to confirm your account email address and may ask you to verify through your Bloom account. We will respond to verified requests within 45 days (or sooner where required by your state's law). If we need more time, we will notify you of the extension and the reason.

You may designate an authorized agent to make requests on your behalf. Authorized agents must provide proof of authorization (such as a signed letter or power of attorney) and we may still verify your identity directly.

13. State-Specific Disclosures

California Residents

Under the California Consumer Privacy Act (CCPA), as amended by the California Privacy Rights Act (CPRA), you have additional rights as described in Section 11 above. Here is a summary of our data practices in the format required by California law:

Categories of personal information collected in the preceding 12 months:

Identifiers (name, email, user ID, device identifiers, IP address)
Characteristics of protected classifications (age, gender, race or ethnicity, religion)
Commercial information (subscription status and purchase records)
Internet or electronic network activity (usage data and website analytics)
Geolocation data (the city or ZIP code you choose and its center point, general location from IP address, the country and region where a profile photo was taken, and place names you or your partner add to shared album photos; not precise geolocation)
Audio, electronic, or visual information (photos, voice messages, voice onboarding audio, and selfie verification video)
Biometric information (face comparison for optional selfie verification)
Inferences (matching preferences, relationship status)
Sensitive personal information (information revealing sexual orientation, racial or ethnic origin, religious beliefs, contents of communications, sex life or dating activity, and biometric information if you verify)

Sources: Directly from you; automatically from your device and browser; from social login providers if you use them; from other users (for example, your partner's shared content or a report about you).

Business purposes for collection: Providing the Service, personalization, safety, communications, and legal compliance (as detailed in Section 5).

Categories disclosed to service providers: Each category above is disclosed to the service providers listed in Section 6.2, only as needed for the purposes listed there. Separately, when you add a photo that includes a location to a shared album, your phone sends a rounded point (about 1.4 miles, or 2.2 km) to Apple or Google to suggest a place name, as described in Section 6.2; Bloom does not receive it.

Sale or sharing: We have not sold or shared (as those terms are defined under the CCPA) any personal information in the preceding 12 months.

Retention: As specified in Section 9.

California "Shine the Light" (Civil Code §1798.83): California residents may request information about disclosures to third parties for direct marketing purposes. We do not disclose personal information to third parties for their direct marketing purposes.

Virginia, Colorado, Connecticut, Texas, Oregon, Montana, Delaware, Tennessee, Maryland, Minnesota, Indiana, Iowa, Kentucky, Rhode Island, Nebraska, New Hampshire, New Jersey, and Utah Residents

Residents of these states have rights to access, correct, delete, and obtain a copy of their personal information, as well as the right to opt out of the sale of personal information, targeted advertising, and certain profiling. These rights are described in Section 11 and can be exercised as described in Section 12.

For states requiring opt-in consent for sensitive data (Virginia, Colorado, Connecticut, Texas, Oregon, Montana, Delaware, Tennessee, Maryland, Minnesota, Indiana, Kentucky, Rhode Island, Nebraska, New Hampshire, and New Jersey), we obtain your affirmative consent during account setup before processing your sensitive personal information.

For Utah and Iowa residents, we provide notice and an opt-out mechanism for sensitive data processing.

14. Shared Data Between Partners

Bloom's Relationship Mode lets you and your partner create and maintain shared content together - photos, calendars, lists, and date plans. Because this data belongs to your relationship, it requires special privacy rules.

How Shared Data Works

When you and your partner use shared features, both of you contribute to and have access to the shared content. Here is how we handle ownership and control:

Content you upload (such as a photo you add to a shared album or a calendar event you create): You can edit or remove your own uploads at any time. If you remove content you uploaded, it is removed from the shared view for both partners. Your partner will be notified that content was removed.

Content your partner uploads: You cannot delete content your partner uploaded. You can hide specific items from your personal view without affecting your partner's access.

Joint content (such as shared lists or calendar entries with contributions from both partners): Either partner can remove their own participation. The other partner retains their copy.

Messages: If you delete messages from your view, they are removed from your side only. Your partner retains their copy of the conversation.

Place and date tags on album photos: While you are together, either partner can add, edit, or remove a tag on any shared album photo. Removing a tag deletes it; nothing is kept behind it. A tag belongs to its photo and is deleted when that photo is removed.

What Happens When a Relationship Ends

When either partner ends the relationship in Bloom:

Both partners retain access to the shared data. Because you both contributed to and maintained the shared content during the relationship, both partners keep a copy of all shared photos, calendar events, lists, and date plans in their personal keepsake archive. If either of you later deletes your account, only the shared photo albums stay (see below).
Shared features (real-time syncing, adding new content) are deactivated.
Place and date tags stay on the shared album photos as part of the keepsake. Neither partner can add, edit, or remove a tag anymore.
Each partner's keepsake archive is private and accessible only to them.
Each partner can independently download, keep, or delete their archive at any time.
The keepsake archive is retained for up to 2 years. You will receive a reminder before the archive expires, giving you the opportunity to download your content or request continued retention.

What Happens When a Partner Deletes Their Account

If your partner or former partner deletes their Bloom account:

You keep your shared photo albums, including the photos and photo details they added. The albums are deleted once both of you have deleted your accounts.
The rest of that relationship's shared content (calendar events, lists, date plans, Journeys, milestones, and insights) is deleted for both of you, along with any private notes you kept in that relationship.
Their profile and profile photos are not kept. Albums from the relationship show the first and last name they had when the relationship ended.
Their own access ends with their account.

When you activate Relationship Mode and connect with a partner, both of you acknowledge that:

Photos and photo details added to a shared album stay with the other partner after your account is deleted, along with the name you had when the relationship ended
Shared content is part of the relationship history that belongs to both partners
Each partner keeps their own copy of the shared photo albums; other shared content, and the private notes kept in that relationship, are deleted if either partner deletes their account

Subscribing to Your Shared Calendar

You can add your shared Bloom calendar to another calendar app, such as Google Calendar or Apple Calendar, with a private link from Settings. If you do:

That app fetches your shared calendar events from Bloom on its own schedule, including events your partner created. Each event includes its title, notes, type, dates and times. The company that runs that app then holds a copy under its own privacy policy, not this one.
Anyone who has the link can see those events, so keep it private. You can get a new link or turn the link off in Settings at any time.
The link covers only the relationship it was created in. It stops updating if that relationship ends, and it never shows events from a later relationship.
Turning off the link, ending the relationship or deleting your account stops future updates. It does not remove copies the other app already has, and we cannot delete them for you. You can remove the subscribed calendar in that app; what that company keeps after that is governed by its own policy.

Your partner is not notified when you subscribe, and either partner can create their own link. We are not paid for this, and these events are not used for advertising.

15. Consumer Health Data

Some information we collect may be considered "consumer health data" under Washington state's My Health My Data Act (RCW 19.373) and similar laws. This includes information that could reveal sexual orientation or gender identity.

For a complete description of how we handle consumer health data, please see our separate Consumer Health Data Privacy Policy.

In summary: we collect consumer health data only with your consent, use it only to provide the Service and keep it safe, do not sell it, and will delete it upon your request. Under Washington law, the face data used for optional selfie verification is also consumer health data, and it is covered by both that policy and Section 18.

16. AI-Powered Features, Automated Decision-Making, and Profiling

16.1 Matching Algorithms

Bloom uses algorithms to suggest potential matches based on the preferences and profile information you provide. This matching process:

Uses only the preferences you set (age range, gender, distance) and profile compatibility factors
Does not produce legal effects or similarly significant effects on you
Can be influenced by adjusting your preferences in Settings
Does not use automated decision-making to approve or deny your account

16.2 AI-Powered Features

Bloom uses artificial intelligence ("AI") in these features:

Conversational onboarding: an AI conversation, by text or optional voice, that helps you build your profile. After each turn, a second AI step pulls profile fields out of the conversation.
Date suggestions: date ideas for you and a match or partner. They use both people's first names, profile prompts, city, food and drink preferences, availability, and past dates. Our "smart" suggestions also read up to the last 20 messages in your chat with that person.
Journeys: personalized relationship activities, built from your answers when you set up a journey and from what Bloom knows about you and your partner.
Notes and Insights scans (Premium): an AI pass over your recent chat with a match or partner (and, in Relationship Mode, shared items such as prompts, journeys, plans, and lists) that suggests notes for you to review.
Daily couple prompts: choosing which prompt to show a couple each day, based on first names, past prompts, and how the couple uses Bloom.

These features are optional, and you can turn off AI personalization at any time (Section 16.4). Some of them read messages and content written by the other person in the conversation, because a suggestion for two people depends on both. Turning off AI personalization also leaves your messages and answers out when the other person uses Notes suggestions, date suggestions, or Insights scans.

16.3 Third-Party AI Service Providers

AI requests are sent from Bloom's servers, never directly from your device, except for voice onboarding audio described below.

Anthropic (Claude)

Used for: text and voice onboarding, profile extraction, date suggestions, journeys, Notes and Insights scans, choosing daily couple prompts, and automated safety review of chat messages and voice message transcripts (Section 16.6).
Data sent: the content each feature needs, as described in Section 16.2 and Section 16.6. Before sending, we remove email addresses, phone numbers, card numbers, and Social Security numbers from profile extraction and from Notes and Insights scans. Onboarding, date suggestions, journeys, and safety review are sent without that step, because the content is what the feature needs.
Training and retention: under Anthropic's commercial API terms, Anthropic does not train its models on our data. Anthropic may keep inputs and outputs for a limited period for safety and abuse monitoring, as its terms describe.

Amazon Web Services (Bedrock)

Used for: a backup that runs the same Claude models when Anthropic's own service is unavailable, for profile extraction, Notes and Insights scans, and journeys.
Data sent: the same data the Anthropic request would have carried.
Training and retention: Amazon Bedrock does not store or log the content of these requests and does not use it to train models.

ElevenLabs

Used for: voice transport in the optional voice onboarding mode: turning your speech into text, speaking Bloom's replies aloud, and turn-taking. The decisions about what Bloom says are made by Anthropic through our servers.
Data sent: your microphone audio during a voice onboarding session (it streams from your device to ElevenLabs over a connection our servers set up), the transcripts, the text of Bloom's replies, and your Bloom user ID.
Training and retention: ElevenLabs does not train its models on this data under our terms, and may keep audio and transcripts for up to 30 days.
Your choice: you can use text or forms instead, and we ask for your consent before your first voice session.

16.4 Your Choices - AI Personalization

Turn off AI personalization in Settings > Privacy > AI Personalization. When it is off, we stop sending your data to AI providers for date suggestions, journeys, Notes and Insights scans, and couple prompts (a couple prompt is chosen without AI if either partner turns it off). It also leaves your messages and answers out when the other person in the conversation uses Notes suggestions, date suggestions, or Insights scans. You may still see generic suggestions.
Onboarding: AI onboarding needs AI processing to work. You can build your profile with the standard forms instead.
What this setting does not control: automated safety review (Section 16.6) runs regardless of this setting, because it protects other users.
Data already processed: turning the setting off applies from that point on.

To exercise privacy rights related to AI processing, contact privacy@bloom.date.

16.5 AI Data Processing Safeguards

No model training: our AI providers do not train their models on Bloom user data under the API terms we use.
Server-side requests: AI requests go through Bloom's servers. The one exception is voice onboarding audio, which streams from your device to ElevenLabs.
Data minimization: each feature sends the data it needs rather than your whole profile.
Human oversight: AI features make suggestions. Automated safety review can block a photo or hide a message, but account-level actions (warnings, suspensions, bans) involve human review.

16.6 Automated Safety Review

Separately from the optional AI features above, Bloom uses automated systems to keep the Service safe:

Photos. Every photo uploaded to Bloom is checked by Microsoft PhotoDNA for known child sexual abuse material. Profile photos, shared album photos, and chat photos between matched singles are also checked by Amazon Rekognition for nudity, violence, and other prohibited content. A photo that fails is blocked or removed automatically, and some are held for human review.
Chat messages between matched singles. Text messages are checked by Anthropic's Claude against our Community Guidelines. We check the first messages of every new conversation, messages from newer accounts, messages from people who were recently reported or flagged, and a random sample of other messages. A flagged message goes to our moderators, and the most serious ones (such as content involving minors) are hidden automatically until a moderator reviews them.
Voice messages. Every voice message between matched singles is transcribed by Amazon Transcribe, and the transcript is checked by Claude. A message that breaks our rules is removed. We do not analyze your voice for tone or pitch, and we do not create a voiceprint.
Fraud risk score. We combine the fraud prevention signals in Section 3.2 into a risk score for each account. A profile photo taken outside the United States raises the score a little; the state or province never changes it. A score only flags an account for one of our moderators to look at. It never limits, suspends, or bans an account on its own.
Relationship Mode. Text and voice messages between partners are reviewed only if one of you reports them. Photos you send each other in chat are checked only by PhotoDNA for known child sexual abuse material, not for nudity or other content.
Why, and your choices. We do this to enforce our Terms of Service and Community Guidelines and to protect our users, including from scams and exploitation. Because it protects other people, it is not controlled by the AI Personalization setting and cannot be turned off while you use Bloom's chat and photo features. Content is sent without removing names or contact details, because those are often what a scam or threat contains.
Human oversight and appeals. Automated review can block or remove an individual photo or message. Warnings, suspensions, and bans involve human review, and you can appeal under our Terms of Service.
No training, no advertising. Our providers do not train their models on this content, and safety review data is never used for advertising or shown to other users.

17. Children's Privacy

Bloom is intended for users who are 18 years of age or older. We do not knowingly collect personal information from anyone under 18.

Age verification: During account creation, we require you to provide your date of birth through a neutral date-entry field. If the date of birth indicates you are under 18, account creation is blocked.

If we discover a minor: If we learn that we have collected personal information from a user under 18, we will promptly deactivate the account and delete all associated personal information. If you believe a minor has created a Bloom account, please contact us immediately at privacy@bloom.date.

Parents and guardians: If you are a parent or guardian and believe your child has provided personal information to Bloom, please contact us at privacy@bloom.date and we will take steps to delete the information.

18. Biometric Data

This section is Bloom's written policy for biometric data, including our retention schedule and destruction guidelines. It applies only if you choose to verify your profile with a selfie. Everything else in Bloom works without it.

What we collect. During selfie verification (Section 3.1), our provider checks that a live person is in front of the camera and compares the face in your reference image with the faces in your profile photos. That comparison measures facial geometry. We store your reference image, the match and liveness scores, and a record of each attempt. We do not store a face template or face map ourselves, and we do not use your face data to identify you in any other context.

Why. Only to verify that the person on your profile is real and is the person in your photos, and to keep the Verified badge accurate when you add new photos.

Consent. Before your first verification, we show you a written notice of what we collect, why, and how long we keep it, and you must tick a box to agree. We keep a record of that consent, including the version of the notice. If you have not consented, verification does not start, and we do not compare new profile photos for you.

Who receives it. Amazon Web Services (Amazon Rekognition) runs the liveness check and the comparisons on our behalf. We do not sell, lease, trade, or otherwise profit from your biometric data, and we disclose it only to our verification provider, or when the law requires us to (for example, a valid warrant or subpoena), or when you ask us to.

How we protect it. Your reference image is stored encrypted in private storage that other users cannot reach. Other users see only whether you are verified, never your image or scores. Within Bloom, only the systems that run verification can read it, and staff access is limited to investigating fraud or a problem you report.

Retention schedule and destruction. We keep your reference image, scores, and attempt records while your verification is active, and destroy them at the earliest of:

30 days after you delete your account (deletion has a 30-day grace period, after which this data is permanently deleted);
30 days after you ask us to remove your verification by emailing privacy@bloom.date; or
1 year after your last use of Bloom.

Your verification stays active until one of these happens; you cannot be partly verified. A failed photo comparison can pause your Verified badge until you verify again (Section 5), but that does not change when this data is destroyed. If we stop offering selfie verification, we will destroy this data within 30 days.

If a verification attempt fails, we do not keep the image from that attempt. When you verify again, your new reference image replaces the old one.

Voice. Voice onboarding (Section 16.3) and the safety review of voice messages (Section 16.6) turn speech into text. Neither creates a voiceprint or analyzes your voice to identify you.

19. Push Notification Data

If you allow push notifications, we deliver them through Google Firebase Cloud Messaging and, on iPhone, Apple Push Notification service. This involves:

A device token (an identifier for your app installation that lets us address notifications to it)
Sending the notification's content through Google's and Apple's servers. A notification about a new chat message includes the sender's first name and the first 100 characters of the message. Notifications about voice messages and photos use fixed wording and do not include the content.
Google and Apple processing your device token and IP address to route the notification

We keep a record of each notification we send. The message preview in a chat notification is removed from that record after 30 days, and the record is deleted after 12 months. Device tokens are deleted when you log out or the token stops working. You can manage push notifications in your device settings or in Settings > Notifications within Bloom.

20. Data Breach Notification

In the event of a data breach affecting your personal information, we will:

Notify affected users in the most expedient time possible and without unreasonable delay, and within any deadline set by applicable state law
Provide details about the breach, the types of information affected, and steps you can take to protect yourself
Notify applicable state authorities and regulators as required by law

21. Dating Safety Disclosures

Your safety is important to us. In accordance with applicable state laws (including Utah Code §13-67-103), we want you to know:

Background checks: Bloom does not currently conduct criminal background screenings on its members. This means we do not verify the criminal history of any user. You should use caution when communicating with or meeting any member of an online dating service, including Bloom.

Safety resources: For detailed dating safety information - including guidance on protecting yourself from sexual assault, dating violence, and financial crimes - please see our Dating Safety page, accessible from Settings > Dating Safety within the app.

Reporting: If a user engages in behavior that makes you feel unsafe, you can report them through their profile or by contacting us at safety@bloom.date. We review all reports and take action in accordance with our Community Guidelines.

Fraud notification: If we ban a user for fraudulent activity, we will email every member who exchanged messages with that user, wherever they live, with the notice Utah law (§13-67-105) requires. We send this notice within 24 hours of the ban, or within three days when the circumstances require more time, as that law allows.

22. Third-Party Links and Services

The Service may contain links to third-party websites or services (such as restaurant booking sites suggested during date planning, or external resources in our safety disclosures). We are not responsible for the privacy practices of these third parties. We encourage you to read their privacy policies before providing them with any personal information.

23. International Users

Bloom is currently available in the United States only. Your personal information is stored and processed in the United States, except that website traffic data processed by Ahrefs (Section 6.2) is handled by a company based in Singapore. If we expand internationally, we will update this policy to address applicable international privacy laws (including the EU General Data Protection Regulation) and implement appropriate data transfer safeguards.

24. Auto-Renewal Subscription Disclosures

If you subscribe to Bloom Premium:

How auto-renewal works: Your subscription automatically renews at the end of each billing period (monthly or annually, depending on your selection) unless you cancel before the renewal date. The renewal price will be the same as your current subscription price unless we notify you of a price change in advance.

Charges: Subscription fees are charged through Apple (App Store) or Google (Play Store). The charge will appear on the payment method associated with your Apple ID or Google account.

How to cancel: You can cancel your subscription at any time. Cancellation takes effect at the end of your current billing period - you will continue to have access to Premium features until then. To cancel:

iOS: Settings > Apple ID > Subscriptions > Bloom > Cancel Subscription
Android: Google Play Store > Profile > Payments & subscriptions > Subscriptions > Bloom > Cancel Subscription
In Bloom: Settings > Subscription > Manage Subscription

Cancellation is designed to be as simple as the original sign-up process.

Free trials: If we offer a free trial, you will be clearly informed of the trial duration and the subscription price that will apply after the trial ends. We will send you a reminder before the trial converts to a paid subscription. You can cancel at any time during the trial without being charged.

Renewal reminders: For subscriptions longer than one year, we will send you a reminder 15 to 45 days before the renewal date. For free or discounted trials longer than 31 days, we will send a reminder 3 to 21 days before the trial ends.

25. Changes to This Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, legal requirements, or other factors.

How we will notify you:

For material changes (new categories of data collected, new sharing practices, or changes to your rights), we will notify you by email and/or prominent in-app notice at least 30 days before the changes take effect.
For non-material changes (clarifications, formatting, or updated contact information), we will update the "Last Updated" date at the top of this policy.

Your continued use of the Service after the effective date of a revised policy constitutes your acceptance of the changes. If you do not agree with the revised policy, you may delete your account.

26. Contact Us

If you have questions about this Privacy Policy, want to exercise your privacy rights, or have concerns about how we handle your information:

Privacy inquiries: privacy@bloom.date
Safety concerns: safety@bloom.date
Security vulnerabilities: security@bloom.date
General support: support@bloom.date
Mail: Bloom Dating, Inc., 10102 S Redwood Rd #95177, South Jordan, UT 84095

We aim to respond to all privacy-related inquiries within 10 business days and to formal privacy rights requests within 45 days (or sooner as required by your state's law).