Privacy Policy

What this policy covers

This policy explains how born.live handles information when you claim, buy, gift, list, sell, or manage a number and its public profile.

Information we collect

• Your born.live number, ownership credential, activity history, engraving, listing, gift, and transaction records.
• Profile details you choose to publish, including a display name, biography, and social links. Profiles are public by default and can be made private.
• An email address when you verify ownership, recover a number, receive a gift, or receive sale notifications.
• When you use Google sign-in: your Google account identifier, verified email address, and name. We use these only to sign you in, link your number, and help you recover it.
• When you use Apple sign-in: your Apple account identifier and the email or name Apple shares with us.
• For mobile Premium purchases, Apple or Google processes the payment. RevenueCat receives the BORN account identifier, product and purchase history needed to validate the transaction, prevent fraud, restore the purchase, maintain the Premium entitlement, and provide purchase analytics. We do not receive complete card or bank-account numbers from Apple, Google, or RevenueCat.
• For website purchases, marketplace sales, and seller payouts, we receive payment, payout-status, and transaction references from Stripe. We do not store complete card or bank-account numbers.
• When a born.live NFC device is tapped: the device identifier, time, broad device category, and a daily rotating pseudonymous identifier used to estimate unique tappers. We do not store the tapper's raw IP address or full browser user-agent in the NFC analytics record.
• If you tap another person's born.live device while signed in, we save a permanent connection between your born.live accounts so both of you can find each other again. The connection follows each person when their number changes.
• If you enable app notifications, we store an app delivery token linked to your account and send the notification title, message, and destination needed to alert you about service activity such as a new connection. You can turn notifications off in the app or in your phone settings.
• When you open a born.live referral link, we store the referring account, landing page, visit times, and an opaque first-party referral token. If you subsequently join the waiting list or claim a number, we attribute that action to the referring account. Referrers receive aggregate counts, not your email address or private account details.
• For BORN Credits, we store your balance, credit and debit ledger entries, the reward or spend type, the related account where applicable, and timestamps. When you unlock a wider network, we store which direct connection you unlocked so reopening it is free. This lets us show an accurate balance and prevent duplicate or abusive claims.
• To understand whether network exploration is useful, we record once per circle when you view its limited preview, open its unlock confirmation, and complete an unlock. These events are tied to your account and the circle, not to advertising identifiers, and do not expose a private profile.
• When you report or block a profile, we store the accounts involved, your selected reason and optional details, review status, and timestamps so we can enforce our community rules and prevent repeated abuse.
• Basic technical and security information such as request times, browser cookies, IP-derived security signals, and error logs.

How we use information

We use information to operate the register, marketplace, and BORN Credits system; prove number provenance; authenticate owners; issue eligible signup and referral rewards; prevent farming, fraud, and duplicate sales; process payments and payouts; deliver service emails; respond to support requests; and improve reliability.

We do not sell personal information. We do not use Google user data for advertising.

Who processes information

We use service providers where needed to operate born.live: Google and Apple for optional authentication; Apple and Google for mobile in-app payment processing; RevenueCat for mobile purchase validation, entitlement management, restoration, fraud prevention, and purchase analytics; Stripe for website payments and seller onboarding; Resend for transactional email; Expo for app notification delivery; and infrastructure providers for hosting and database storage. Each provider processes information under its own terms and privacy commitments.

Service reliability monitoring

We use PostHog, hosted in the United States, for internal troubleshooting of browser errors and failed API requests. Diagnostic reports contain technical details such as endpoint templates, response status, failure category, timing, release version, and sanitized JavaScript asset locations. They do not include request or response bodies, passwords, authentication credentials, email addresses, account numbers, or URL query parameters. We configure PostHog to discard client IP addresses from stored events and disable session recordings, automatic click capture, and page-view tracking for this integration.

Server reports use a new random identifier for each failure, not an account identifier. Browser diagnostic identifiers are held in memory rather than persistent analytics cookies, and browser reporting respects Do Not Track. These reports are used to identify and fix service failures, not for advertising or building customer profiles. We retain diagnostic data only as needed for troubleshooting and reliability, subject to our provider's retention settings. You can contact us about this processing using the address below.

Public records and privacy choices

A number’s provenance and non-identifying ownership activity may remain visible so the register can preserve its history. While your profile is public, your display name and profile image may appear as a limited preview to people exploring a connected circle. If you tap a BORN.LIVE Table Stand while signed in, that place may also see your public profile with the tap's time and stand location. Your biography, number, profile destination, and links are withheld from network previews until the viewer unlocks the circle. You can switch the profile to private from Mine. Private profiles remain anonymous in network previews, unlocks, and Places activity. Existing connections remain recorded, but people you connected with cannot open your profile or see those details while it is private. Blocking another account prevents both accounts from seeing each other's profile and removes that person from connection views.

Cookies and retention

We use secure cookies to recognise the browser that owns a number, protect requests, complete sign-in, and preserve referral attribution for up to 30 days. We retain account, transaction, and credit-ledger records for as long as needed to provide the permanent register, keep balances accurate, meet legal and financial obligations, resolve disputes, and prevent abuse. Credit records may be retained or de-identified after account deletion where needed to stop the same reward being claimed again. Account-to-account NFC connections and tap analytics are retained as part of the permanent service history. Notification delivery tokens remain until you turn notifications off, sign out, delete your account, or the device reports that the token is no longer registered. Referral attribution records are retained for community reporting and abuse prevention and may later be aggregated or deleted when no longer needed. The anonymous analytics identifiers rotate daily and cannot be used to reopen a person's profile. Short-lived sign-in states expire automatically.

Profile insights

Profile owners can privately see counts of profile views and profile-link clicks, dates, and whether activity happened on the website or app. Own-profile views are excluded and repeat views in the same 30-minute window are grouped. We use profile-scoped, short-lived pseudonyms for grouping, without storing raw IP addresses or browser user-agents in the insights records. Anonymous counts are not a list of identifiable people.

Sharing your profile visits is off by default. If you enable “Share my profile visits” in Settings while your profile is public, a profile owner can see your public name, photo, profile link and visit times in their viewer list. Private profiles and blocked accounts are not identified. Turning sharing off removes your identity from previous insight events; turning it back on does not reveal earlier anonymous visits. “Hide insights” only hides your dashboard button and does not change this separate visitor-sharing choice.

Individual insight events are retained for up to 90 days and removed when insights are next recorded or read. Daily totals by link and platform are retained for all-time reports without visitor identities or event identifiers. All-time history starts when collection began, not before. Deleting your account removes your profile’s events and totals and anonymises your visits to other profiles. These first-party insights are separate from our reliability-monitoring integration.

Your choices

You may ask to access, correct, export, or delete personal information, or object to certain uses. You can permanently delete your account inside the BORN.LIVE app; full instructions are on our account deletion page. Some provenance, payment, and anti-fraud records may need to be retained or de-identified where the law or integrity of the register requires it.

Contact

For privacy questions or requests, email hello@born.live.