Privacy policy

Birthday information stays on your device

Bloom stores names, birthday month and day, an optional birth year, favorites, reminder preferences, and source identifiers locally on your device. A birth year is not required. Signed-in accounts have separate local birthday records. Signing in does not upload birthdays to Supabase or provide cloud backup or cross-device synchronization.

Contacts and calendars are read only after you grant permission and initiate an import. You review which birthdays to save. Accounts such as Apple or Google may supply contacts or calendars through your phone; Bloom does not obtain their passwords. This version does not directly retrieve Facebook friends’ birthdays. Importing, editing, or removing a birthday in Bloom does not change the original contact or calendar event.

Local data is stored in app storage, not in a separately encrypted birthday vault. Your device protections and any device or browser backups also matter. Avoid importing information you are not entitled to use.

Account and email services

Supabase processes your email address, account identifier, authentication credentials and session tokens, and operational/security information such as IP addresses and authentication events to run and protect sign-in. Native session tokens use the operating system’s secure storage; the browser version uses browser storage.

Resend delivers verification emails on our behalf. It processes the destination email address, email content including the temporary verification code, and delivery metadata such as delivery status and timestamps. Birthday records are not included in these emails. These are account messages, not marketing subscriptions.

We use this information to provide the service, respond to requests, prevent misuse, and meet legal obligations. Where a legal basis is required, we rely on performance of our agreement for account services, legitimate interests for proportionate security and support, legal obligations where applicable, and consent where required for optional access.

Permissions, widgets, and notification previews

Contact and calendar access is optional. You can enter birthdays manually and revoke access in phone settings. Revoking access stops future access but does not erase birthdays already imported; remove those in Bloom. Notification permission is optional and can also be changed in phone settings.

Birthday details are passed to your device’s widget and local notification services so reminders can appear outside Bloom. In Widgets, Keep names private hides names in the lock-screen rectangular list and inline widget. It also hides the name in the circular countdown preview. The current native iPhone circular widget displays only the countdown and day label, so it contains no name even when the switch is off. The Android birthday widget hides names when this switch is on. iPhone home-screen widgets and the home-screen design previews continue to show names; remove those widgets if you do not want names visible there.

The widget privacy switch does not remove names from notification content. On iPhone, use Settings → Notifications → Bloom Birthday Reminder → Show Previews → Never, or When Unlocked. On Android, use Settings → Notifications → Lock screen notifications and hide sensitive content, or disable lock-screen notifications; labels vary by device. These settings control what the operating system displays, not the content Bloom schedules. People who can access an unlocked phone may still see birthday information. Widget designs and availability depend on platform and release.

Retention and deletion

Local birthdays and preferences remain until you remove them or clear the relevant app storage. Signing out keeps that account’s local birthdays on this device. Uninstalling may remove local data, but device or browser backups may retain copies under your backup provider’s settings. There is no automatic inactive-account deletion period.

Your account remains while you use it unless you delete it. Settings → Delete account requires recent verification and explicit confirmation. When deletion succeeds, Bloom deletes the authentication account and clears that account’s local data on this device. If an error occurs, follow the displayed instructions or contact us; do not assume deletion completed. Original contacts, calendar events, other accounts’ local data, offline copies on other devices, and system backups are not remotely erased by this action.

Resend’s standard email and delivery-log retention is 30 days, with backups retained for 7 days under its published service policy. Supabase may retain separate operational/security logs and provider-managed backup copies under its service policies; the period for viewing logs in a dashboard is not a guarantee that all copies have been erased. Account deletion does not instantly purge every provider security record or backup.

For requests handled by email, we aim to complete verified access, correction, or deletion requests within 30 days, subject to applicable legal deadlines and exceptions. We retain support correspondence only as needed to resolve the request, document its handling, and meet legal or security obligations, then delete or de-identify it. If retention is necessary for a legal obligation or dispute, we limit its use to that purpose. Contact us for information about a particular record.

Sharing, website visits, and security

We do not sell birthday or account information, use it for targeted advertising, or include advertising or behavioral analytics SDKs in this version. We share information with service providers only as needed to run the relevant service, with authorities when legally required, or as necessary to protect rights and security. A business transfer may involve account information subject to appropriate notice and safeguards.

Our public policy and support pages are hosted by Vercel. Like other hosting services, it processes connection information such as IP addresses, requested URLs, and technical logs to deliver and secure the website. These public pages do not require sign-in or intentionally set advertising cookies. If you email us, Google processes that correspondence through our Gmail contact address. If you use an address forwarded through our domain, NameSilo also processes the message and forwarding metadata to deliver it to our contact inbox.

We use reasonable technical and organizational safeguards, including controlled account access and encrypted network connections. No service or device can guarantee absolute security. Keep your device locked and never share a verification code with support or another person.

New York, United States, and international processing

Vicostock LLC administers Bloom under the applicable laws of New York State and the United States, including applicable data-security and breach-notification requirements. This does not limit mandatory privacy or consumer rights available where you live.

Bloom’s Supabase project is hosted in the United States, in Northern Virginia. Our email, hosting, and support providers may process information in the United States and other countries where they and their subprocessors operate. New York governing law does not mean all information is physically stored in New York. Where required for international transfers, we rely on applicable lawful safeguards, such as provider contractual protections and standard contractual clauses. Contact us for information about relevant safeguards.

Request access, correction, or deletion

Email vicostock@gmail.com with the subject ‘Bloom privacy request’. Tell us whether you want access to account information, a correction, deletion, or information about another applicable right. Include the email address associated with the account and enough detail to locate the issue. Do not send passwords, verification codes, identity documents, or your full contact list unless a necessary and secure verification process has first been agreed.

We verify requests proportionately, normally through control of the account email address. We will explain if further information is necessary, a request cannot be fulfilled, or a lawful extension applies. For birthdays stored only on your device, we cannot retrieve them remotely; you can review, edit, or remove them within Bloom, and we can guide you through that process.

Depending on your location and applicable law, you may also have rights to portability, restriction, objection, withdrawal of consent, an authorized agent, appeal, or a complaint to a privacy regulator. We will not discriminate against you for exercising a protected right. You may reply to our decision to request a review. New York is our legal baseline, not a waiver of rights in other jurisdictions.

Children and policy changes

Bloom is not directed to children under 13. We do not knowingly collect account information from children under 13. Contact us if you believe such an account exists. Storing a family member’s birthday locally is different from that person holding an account; you remain responsible for having permission to use the information.

We will update this policy as practices change, show the new effective date, and provide additional notice or obtain consent when required for material changes. Future cloud synchronization, new integrations, or paid services will be described before they change how your information is handled.