Privacy Policy
Effective date: June 5, 2026
Reader aid. This page explains what data Flowers collects, why we use it, how long we keep it, who processes it, and how to request access, correction, deletion, or portability. The English policy below is the canonical legal text.
Flowers is a flower collection, arrangement, and private-sharing app developed by Flower Dg (operated by Hoang Hai Long Do), with a companion gift web service at flowerisblooming.com. This Privacy Policy explains how we ("we", "our", "Flower Dg") collect, use, and protect your personal data in compliance with applicable data protection laws, including the EU General Data Protection Regulation (GDPR), the UK GDPR, the California Consumer Privacy Act (CCPA/CPRA), Brazil's Lei Geral de Proteção de Dados (LGPD), Vietnam's Decree 13/2023/ND-CP on Personal Data Protection, Canada's PIPEDA, and other applicable privacy regulations worldwide.
AI Crawlers, Scraping & Training
Flowers does not permit GPT, ChatGPT, OpenAI, Claude, Anthropic, Gemini, Google AI, Google-Extended, Perplexity, or any other AI system to scrape, copy, index, retrieve, ingest, train on, fine-tune on, summarize user-specific gift content, or reproduce our artwork, animations, code, design, text, or bundled assets without prior written permission.
This restriction applies to automated crawlers, scrapers, user-triggered AI retrieval agents, browser agents, "computer use" agents, data brokers, model-training pipelines, retrieval-augmented generation (RAG) or vector indexes, dataset builders, and any service acting on behalf of GPT, Claude, Gemini, or similar AI products. Private gift pages, preview routes, bundled media, and illustrated assets are always off-limits.
1. Data Controller
The data controller responsible for your personal data is:
Flower Dg (operated by Hoang Hai Long Do)
Email: [email protected]
2. Information We Collect
2a. Account Information (if you sign in)
When you sign in with Google or Apple, we receive:
- Google Sign-In: email address, display name, and profile photo
- Apple Sign-In: email address (or Apple's private relay email) and display name (if provided)
This information is used solely for authentication and cloud sync. We do not access your contacts, calendar, or any other data from your Google or Apple account.
2b. App Usage Data
- Focus session data: timer sessions, earned flowers, garden arrangements (pots and bouquets). Stored locally on your device and, if signed in, synced to the cloud.
- Gift data: when you send a flower gift, the bouquet snapshot and your optional note are stored only as needed to deliver and operate the gift link.
- App diagnostics: Firebase Analytics and Crashlytics collect app interaction events, app version, device/OS details, crash traces, and reliability diagnostics so we can understand failures and improve the gift flow. We do not intentionally log gift note text, recipient or sender names, gift URLs, photos, videos, voice notes, or precise location in analytics or crash diagnostics.
- Personality onboarding responses: if you complete the personality flow, your answers (color preference, shape preference, birth date, chronotype, and other preference data) are used inside the app to pick a flower and generate a short personalized reading. These responses are not sent to an external AI model provider.
2c. Couples & Warmth Data (optional)
If you pair with a partner using the Warmth feature, we collect and sync:
- Photos & videos: photos you capture or select for Locket (shared photo widget) and memories. Stored in Firebase Storage and shared with your paired partner only.
- Voice notes: short audio recordings you attach to memories. Stored in Firebase Storage and shared with your paired partner only.
- Scratchpad & doodles: text and drawings you share with your partner via the Warmth tab.
- Couple relationship data: your pairing status, partner display name, meeting date for the days-together counter, and streaks.
- Couple question answers: your responses to couple questions you and your partner choose to answer together.
All couples data is visible only to you and your paired partner. You can unpair at any time, which stops new data sharing. Previously shared content remains accessible to your former partner until deleted — we cannot retrieve copies your partner may have downloaded, screenshotted, or backed up independently. See §2h for a note on joint controllership.
2d. Purchase Information
- Subscription status: we use RevenueCat to manage mobile subscription entitlements. RevenueCat receives your anonymized app user ID and purchase receipts from Apple or Google Play to verify your subscription status. For the separate gift web service, the checkout provider shown at purchase time processes payment, recurring billing, tax, fraud screening, and receipts. We do not receive or store your payment method, credit card number, or full billing address.
2e. Device Tokens
- Push notification token: if you enable notifications, we store your device token to deliver Flower of the Day reminders and couples-feature notifications. You can disable this at any time in your device Settings.
2f. Device Permissioned Data (optional)
- Location: if you opt in to Explore, gardener, distance-to-partner, map pin, or memory-location features, we may collect approximate location and, when you choose a specific map point or use current location, precise latitude/longitude coordinates. Location data is used only to provide the feature you selected and is shared only with the paired partner or gift/memory recipient you choose.
2g. Retired Flower Identifier & External AI Photo Processing
Flowers no longer offers the optional flower/plant camera identifier feature. The mobile app, widgets, website, and backend no longer include the scanner UI, scanner route, callable scanner function, OpenRouter API call, or OpenRouter API secret. We do not transmit Google user data, user photos, gift media, or plant/flower photos to OpenRouter, Google Gemini, Anthropic, or other third-party AI model providers.
2h. Couples Data — Joint Controllership
In the Warmth feature, each paired partner is simultaneously a data subject and a data author. When Partner A uploads a photo to share with Partner B, Partner B receives that photo as their own data. Deletion requests from one partner remove that partner's contributions but may not delete the other partner's independent copies. Both partners are encouraged to exercise their own rights (see §7) as needed.
2i. Website Cookies & Local Storage
On flowerisblooming.com and compose.flowerisblooming.com, we use strictly necessary cookies and local storage for authentication, checkout, abuse prevention, gift delivery, security telemetry, and remembering your cookie choices. Optional analytics or marketing storage is off unless you choose it in the cookie banner or Cookie Settings control. You can change your choice at any time through Cookie Settings in the site footer or compose interface.
3. Information We Do Not Collect
- We do not collect background location or location unless you opt in to a location-based feature.
- We do not collect Calendar, Reminders, Health, Fitness, or step-count data.
- We do not use analytics or crash diagnostics for advertising or third-party tracking, and we do not intentionally log gift content in those tools.
- We do not load optional website analytics or marketing storage unless you consent.
- We do not serve advertisements.
- We do not use cookies or web tracking technologies in the mobile app.
- We do not sell, share, rent, or trade your personal data with third parties for their commercial purposes.
- We do not use your data to train artificial intelligence or machine learning models.
- We do not operate a flower/plant photo identifier, and we do not send Google user data, user photos, gift media, or plant/flower photos to OpenRouter, Google Gemini, Anthropic, or other third-party AI model providers.
4. Legal Basis for Processing (GDPR / UK GDPR)
| Processing Activity | Legal Basis |
| Authentication (Google/Apple Sign-In) | Contract — necessary to provide cloud sync |
| Cloud sync of focus data | Contract — core functionality you opted into by signing in |
| Push notifications | Consent — you explicitly grant permission via the system prompt |
| Gift delivery | Contract — necessary to deliver the gift you chose to send |
| Couples & Warmth features | Contract + Consent — necessary to provide the couples features you opted into by pairing |
| Subscription management | Contract — necessary to verify and deliver your purchased subscription |
| Explore / gardener location | Consent — you explicitly opt in |
| Strictly necessary website cookies/storage | Contract + Legitimate Interest — required for sign-in, checkout, security, gift delivery, and consent records |
| Optional website analytics/marketing storage | Consent — used only if you opt in through Cookie Settings |
| Mobile app analytics and crash diagnostics | Legitimate Interest — understanding reliability, preventing abuse, and improving the Service without using the data for advertising |
| Abuse prevention, security, fraud | Legitimate Interest — protecting the service and other users |
5. Automated Decision-Making
The personality feature performs automated matching of your onboarding responses to one flower in our library. This is a form of automated decision-making as defined in GDPR Article 22. However, the outcome is informational and entertainment-only; it has no legal or similarly significant effect on you, and Article 22's restrictions on solely-automated decisions generally do not apply. You can always ignore the automatically selected flower and pick a different one manually. You may also contact us to request human review of any personalized output you believe is inappropriate.
6. Data Storage, Retention & International Transfers
Your data is stored locally on your device. If you sign in, your data is additionally stored in:
- Google Firebase (Firestore, Authentication, Storage, Cloud Functions) — servers in the United States and/or other Google regions
- Firebase Analytics and Crashlytics — app interaction metrics and crash diagnostics processed by Google/Firebase
- Expo Push Notification Service — servers located in the United States
If you are located in the EEA, UK, or another jurisdiction with data-transfer restrictions, your data may be transferred to and processed in countries that may not provide an equivalent level of data protection. These transfers are safeguarded by Standard Contractual Clauses (SCCs), the EU-U.S. Data Privacy Framework where applicable, or equivalent mechanisms adopted by each processor. You can avoid international transfers entirely by using the app without signing in.
Retention Schedule
- Local data: retained on your device until you uninstall the app or clear app data.
- Cloud user data: retained as long as your account exists. Accounts inactive for more than 24 consecutive months may be deleted on notice.
- Couples data: photos, voice notes, scratchpad, doodles, memories, questions, streaks — retained while the couple is paired. Unpairing stops new data sharing; previously shared content persists until either partner deletes it or deletes their account.
- Gift data: retained only as needed to deliver and operate the gift link, then deleted or anonymized according to the current service retention schedule.
- Analytics and crash diagnostics: retained according to Firebase Analytics and Crashlytics settings, then used only in aggregate or diagnostic form to improve reliability.
- Push tokens: removed when you disable notifications or delete your account.
- Deletion: live data is deleted within 30 days of a deletion request. Backups are purged on a rolling 30-day window, so deletion fully propagates within approximately 60 days.
7. Your Rights
All Users
- Access: request a copy of the personal data we hold about you
- Deletion: request deletion of your personal data and account
- Correction: request correction of inaccurate data
EEA, UK & Swiss Residents (GDPR / UK GDPR)
- Data portability: receive your data in a structured, machine-readable format
- Restriction: request restriction of processing in certain circumstances
- Objection: object to processing based on legitimate interests or automated decision-making
- Withdraw consent: withdraw consent at any time (e.g., disable notifications, disable Explore)
- Lodge a complaint: with your local data protection supervisory authority
California Residents (CCPA / CPRA)
- Right to know: what personal information we collect and why
- Right to delete: request deletion of your personal information
- Right to non-discrimination: we will not discriminate against you for exercising your rights
- Right to correct: request correction of inaccurate personal information
- Right to limit: limit the use of sensitive personal information (we do not use sensitive personal information for secondary purposes)
- No sale / no share: we do not sell or share your personal information as defined by CCPA/CPRA
Brazil Residents (LGPD)
- You have rights to access, correction, anonymization, deletion, portability, and information about sharing, consistent with the LGPD.
Vietnam Residents (Decree 13/2023/ND-CP)
- You have rights to access, correction, deletion, restriction, objection, and withdrawal of consent regarding your personal data, consistent with Vietnamese data protection law.
Other Jurisdictions
Residents of Australia (Privacy Act 1988), Canada (PIPEDA), Singapore (PDPA), and other jurisdictions with applicable data protection laws have analogous rights under their local laws.
To exercise any right, contact us at [email protected]. We respond within 30 days (or within the timeframe required by your local law).
8. Children's Privacy
Flowers is not directed at children under 13 (or under 16 in the EEA). We do not knowingly collect personal information from children below these ages. If you believe a child has provided us with personal data, please contact us and we will promptly delete it.
9. Third-Party Services
- Firebase Authentication — Google / Apple Sign-In. Firebase Privacy Policy
- Firebase Firestore, Storage, Cloud Functions — cloud data, media, and server logic. Firebase Privacy Policy
- Firebase Analytics and Crashlytics — app interaction metrics and crash diagnostics. Firebase Privacy Policy
- Expo Push Notifications — push delivery. Expo Privacy Policy
- RevenueCat — mobile subscription entitlement management. RevenueCat Privacy Policy
- Gift web checkout provider — web subscription payment processing, recurring billing, taxes, fraud screening, and receipts. The provider's privacy terms are shown during checkout.
- Apple StoreKit — iOS in-app purchases processed by Apple. Apple Privacy Policy
- Google Play Billing — Android in-app purchases processed by Google Play. Google Privacy Policy
10. Security & Sensitive Data Protection
We treat account identifiers, authentication data, Google user data received through Google Sign-In, private couples content, gift notes and media, location data, push tokens, and support/deletion requests as sensitive data for our service.
We use the following data protection mechanisms for sensitive data:
- Encryption in transit: app, website, Firebase, and checkout traffic is sent over HTTPS/TLS. We do not intentionally transmit sensitive data over unencrypted channels.
- Encryption at rest: Firebase Authentication, Firestore, Storage, and Cloud Functions data are protected by Google Cloud/Firebase encryption at rest. On-device app data is kept inside the operating system's app sandbox and is not shared with other apps by Flowers.
- Access controls: Firebase Authentication identifies signed-in users. Firestore and Storage Security Rules restrict cloud data to the user account, couple, or gift link it belongs to, and backend administrative access is limited through Firebase/Google Cloud IAM.
- Couples and private media scoping: couples photos, videos, voice notes, doodles, question answers, and relationship metadata are scoped to the paired users only. Storage paths and database documents are owner-, couple-, or gift-scoped to prevent unrelated accounts from accessing them.
- Google user data minimization: Google Sign-In is limited to basic identity scopes. We do not request Gmail, Drive, Calendar, Contacts, or other broad Google API scopes. Google identity data is used only for sign-in, account display, cloud sync, account recovery, security, and legal compliance.
- No external AI photo processing: the retired flower/plant identifier was removed. Flowers does not send Google user data, user photos, gift media, or plant/flower photos to OpenRouter, Google Gemini, Anthropic, or other third-party AI model providers. If we introduce any future feature that uses a new external AI/media processor, we will update this policy before collecting that new category of data.
- Logging limits: we do not intentionally log gift note text, recipient or sender names, photos, videos, voice notes, precise location, OAuth tokens, Firebase ID tokens, payment methods, or private couples content in analytics, crash diagnostics, or routine server logs.
- Retention and deletion controls: gift data is retained only as needed to deliver and operate gift links, refund and applicable Android-cancellation webhooks disable paid gift links where applicable, push tokens are removed when notifications are disabled or the account is deleted, and deletion requests remove live cloud data within 30 days with backups purged on a rolling window.
- Abuse monitoring and validation: we use server-side validation, Firebase/Cloudflare security telemetry, rate limits, and Content Security Policy reporting to detect misuse without expanding the categories of personal data we collect.
- Operational safeguards: production data access is limited to support, security, debugging, and legal-compliance needs. Server credentials and private keys are kept out of client code, and security-sensitive secrets are not intentionally written to logs.
However, no method of electronic transmission or storage is 100% secure and we cannot guarantee absolute security.
11. Over-the-Air (OTA) Updates
To deliver bug fixes and content updates quickly, the app may receive JavaScript and asset updates outside of the App Store review process via Expo's OTA-update service. These updates do not introduce new permissions or new categories of data collection — any material change in data handling will be accompanied by an updated version of this policy.
12. Changes to This Policy
We may update this policy from time to time. Material changes will be posted on this page with a revised effective date. Significant changes may also be surfaced inside the app. Your continued use of the app after changes are posted constitutes acceptance of the updated policy.
13. Contact Us
Questions, rights requests, and data deletion requests: [email protected] — we aim to respond within 30 days.