Privacy policy

Depending on the features you use, we collect:

• Account and identity information: your email address, display name, authentication provider and a Namely user identifier. You can also use the app anonymously before linking an account.
• Names and preferences: names you generate, search for, view, like, dislike or shortlist; name details; search filters and preferences; and related inputs such as a sibling name or inspiration that you choose to provide.
• Partner information: invite codes, connection status and the name preferences used to find matches with a connected partner.
• Optional due date: if you provide a due date, we use it to personalise pregnancy-stage content. A due date may be sensitive or health-related information. Providing it is optional, and it can be cleared in the app. Namely is not a medical device and does not diagnose, treat, cure or prevent any medical condition. Its timing content is general information, not a substitute for advice from a qualified health professional.
• Purchases and subscriptions: subscription, entitlement, renewal, expiry and app-store transaction status. Apple or Google processes your payment details; Namely does not receive your full card or bank details.
• Device, usage and diagnostics: app version, device model and operating system, language or timezone, app lifecycle and feature interactions, notification token and preferences, IP-derived approximate location, security and app attestation signals, and crash or error information.
• Support and sharing: information you put in a support message, along with any screenshot or attachment you choose to send. Content you share through the operating-system share sheet is sent to the recipient or service you select.

Our website may also receive standard hosting logs such as IP address, browser, requested page, timestamp and security events. We do not use advertising SDKs, collect the advertising identifier, or ask for access to your contacts, precise location, camera, microphone or photo library.

In Namely 6.1 and later, PostHog usage analytics and Firebase Crashlytics diagnostics are separate optional choices. Both are off until you choose to enable them, neither affects app features, and each can be turned off again in Settings. PostHog may receive your Namely identifier only while analytics is enabled. Crash reports created by Namely 6.1 and later are not assigned your raw Namely user identifier. On the first 6.1 launch, Namely clears any older Crashlytics user identifier and deletes unsent legacy reports before a later consented upload can occur. Turning a choice off stops new data from being sent to that service. Earlier app versions do not include these separate controls and may send the usage and diagnostic information described above automatically; update to the latest version to use the controls.

We use personal information to:

• create, secure and support your account;
• generate, save and synchronise baby names and preferences;
• connect partners and identify shared name matches;
• provide subscriptions, notifications and support;
• understand feature use, improve Namely and diagnose crashes or reliability problems;
• prevent abuse, fraud and unauthorised access; and
• meet legal obligations and enforce our terms.

Depending on where you live, we rely on your consent, performance of our contract with you, our legitimate interests in operating and improving Namely, and compliance with legal obligations. You can withdraw consent for optional processing at any time, but this does not affect processing that was already lawful.

When you choose an AI-powered generation or name-information feature, the name inputs and preferences needed for that request are sent through our protected Firebase backend to Google Cloud Vertex AI (Gemini). An older compatible generation service may use Microsoft Azure OpenAI while it remains available. The information sent can include selected names, name preferences, origin or letter filters, a sibling name or inspiration, and names already shown so they are not repeated. We do not intentionally include your email address or payment details in an AI prompt.

Namely 6.1 and later asks for your permission before sending this information to a third-party AI provider. You can decline or later withdraw that permission in the app. Declining means AI-powered generation and enrichment cannot run, but you can still use non-AI parts of the app. Earlier versions may not show this choice, so update to the latest version before using AI features if you want this control. Google Cloud and Microsoft state that customer prompts and outputs are not used to train their foundation models without permission; limited processing or retention may still occur for service delivery, caching, safety and abuse prevention under their terms.

We use the following service providers:

• Google Firebase and Google Cloud for authentication, database storage, server functions, notifications, app integrity, crash reporting and Vertex AI;
• Apple and Google for sign-in, app distribution, payments, subscriptions, device integrity and notifications;
• RevenueCat for subscription and entitlement management;
• PostHog Cloud US for product analytics; and
• Microsoft Azure OpenAI for the older compatible AI generation path while that service remains available.

These providers process information only for the service purposes described above and under their own privacy and data-processing terms. We may also disclose information if required by law, to protect people or Namely, or as part of a corporate transaction with appropriate safeguards. A connected partner can see the name preferences required to identify shared matches. Email providers, share targets and recipients you choose process content under their own terms.

We do not sell personal information, show third-party advertising, or use Namely data to track you across other companies’ apps and websites for advertising.

Namely is operated from Australia. Our providers may process or store information in Australia, the United States, the European Union and other countries where they operate. Firebase Authentication is primarily operated from the United States, other Firebase and Google Cloud services may operate globally, and our PostHog analytics project is hosted in the United States. Privacy protections in another country may differ from those in your home country. We use contractual, technical and organisational safeguards appropriate to the service and applicable law.

We retain account data while your account is active, or until you delete particular information in the app. Some history is also limited by storage size. Operational records are kept only as long as reasonably needed for the purpose described, security, dispute resolution or legal obligations.

You can request account deletion in Settings in the Namely app, or follow the steps on our account-deletion page. Once Namely accepts the request, the app blocks further account use while deletion or an uncertain network response is resolved. Account access and core active data are removed promptly. RevenueCat customer absence and PostHog person and event deletion are checked during the deletion workflow. PostHog recording deletion is accepted and queued by PostHog, but PostHog does not provide a recording-completion endpoint that Namely can independently verify. Raw processor identifiers are normally removed within 30 days. A genuinely unresolved request may retain the minimum user identifier needed for manual completion until the incident is resolved. Data independently belonging to a connected partner remains in that person’s account.

Limited deletion-security evidence does not remain in ordinary product use. Completed Firestore job records are removed no later than 30 days after the request. A redacted receipt status and a pseudonymous deletion proof, neither containing the raw user identifier, are retained for up to 180 days so an offline device or disaster-recovery restore cannot reactivate deleted data. Encrypted Firestore disaster-recovery backups are retained for up to 98 days and cannot have one account selectively removed from an existing backup; deletion proofs are reapplied before restored data is made active. Firebase Authentication and Firebase installation records may take up to 180 days to disappear from live and backup systems, and App Check replay protection can retain a token for up to 30 days.

For accounts whose earlier crash reports carried a Namely user identifier, Namely submits targeted Crashlytics deletion requests for both mobile apps and retries them in three bounded passes. Firebase returns an expected completion time, typically within 24 hours, but does not provide Namely with an independent completion check. Crash data otherwise follows Firebase’s service-retention period, generally about 90 days. App-store purchase records, support email, legal records and content sent to a share recipient may be retained independently under the relevant provider’s or recipient’s obligations.

Deleting Namely does not cancel an Apple App Store or Google Play subscription. You must manage or cancel it in the relevant store.

We use access controls, encrypted network connections, provider security controls, app attestation and restricted administrative access to protect information. No internet transmission or storage system is completely secure, so we cannot guarantee absolute security.

Namely is intended for prospective parents and other users aged 13 or older. A minor must use the service only with permission and supervision from a parent or guardian where required by local law. We do not knowingly collect personal information from a child under 13. If you believe that has occurred, please contact us so we can investigate and delete it.

Depending on your location, you may ask to access, correct, download, restrict or delete personal information, object to some processing, withdraw consent, or complain to a privacy regulator. You can clear many preferences and saved names directly in the app. You may also disable notifications through Namely or your device.

To make a privacy request or complaint, email hello@namelyapp.com. We may need to verify your identity. We will acknowledge and investigate a complaint, explain the outcome, and aim to respond within 30 days. In Australia, you may also contact the Office of the Australian Information Commissioner.

We may update this policy when our services, providers or legal obligations change. We will update the date above and provide additional notice in the app when a change materially affects how we use personal information or requires new consent.

Hog and Mole Pty Ltd, Australia
Privacy contact: hello@namelyapp.com