Privacy Policy

Last updated: October 15, 2026

PinkyBond, a product of Veronata, Inc. (“we,” “our,” or “us”), is committed to protecting your privacy and the privacy of your partner. This policy explains what data we collect, what we don't collect, and how what you share with your partner is protected with end-to-end encryption. We never sell your data, show you ads, or share it with data brokers. Please read Section 7: what you say to the Coach may be kept and reviewed.

1. We cannot read what you share with your partner

PinkyBond is built so that we cannot read, access, or decrypt the data that flows between PinkyBloom (her app) and PinkyBond (your app). We never hold the key. Everything the two apps send each other is encrypted on the phone using AES-256-GCM before transmission. Our server (the Blind Relay) holds the content of what you share — messages, check-ins, photos, voice notes, videos and files — only as encrypted blobs it cannot decrypt. The few things it can read, such as the call log, are listed in Section 2. The Coach, the AI in PinkyBond, works differently and is described in Section 7.

2. What Our Server Stores

Our Convex backend stores the following for each message or data snapshot:

  • Pairing ID: A SHA256 hash of sorted public keys. Not tied to any identity.
  • Ciphertext: Base64-encoded AES-256-GCM encrypted data we cannot read.
  • Message type: “chat” or “snapshot” (we know the type but not the content).
  • Sender role: “bloom” or “bond” (we know which app sent it).
  • Timestamp: When the message was sent.
  • Size: The length of the ciphertext.

Messages are deleted on delivery. A message stays on our server only until your partner's phone receives it, and is deleted as soon as it has. If that phone stays offline, the message is deleted after 30 days at most (some types, such as status snapshots and call-setup messages, much sooner). What remains after delivery is a small delivery record with no content — which message it was, and whether it was delivered or expired, and when — kept for 30 days so the sender's app can show that a message was not delivered.

Photos, voice notes, videos and files (up to 2 GB each) are encrypted on the phone with a fresh key for every file. That key travels only inside the encrypted message, so only your two phones have it. The encrypted file is stored with Cloudflare R2, our storage provider, and deleted as soon as your partner's phone has downloaded it — after 30 days at most. We keep the file's size and upload and download times for the same 30 days. If your partner's app has not been updated to a version that supports large files, files go the older way instead: up to 25 MB, encrypted with your pairing key, stored with Convex, and kept for 30 days even after they have been opened.

So that calls and notifications work, the server also keeps:

  • A call log: for each call between you, which of your two phones called, when it started, rang, was answered and ended, whether it was voice or video, whether it was answered, missed or declined, and how long it lasted. This is not end-to-end encrypted — the server reads it to tell a phone that was switched off about the calls it missed. It never contains any audio or video: calls are end-to-end encrypted between the two phones and are never recorded. The call log is kept for 90 days, deleted when you unpair, and never combined with analytics.
  • Notification tokens: the push-notification token Apple or Google issues to the app. We delete it the moment Apple or Google tells us it is dead, and otherwise after 270 days without being refreshed — the point at which the address has expired anyway. It used to be 30 days, which meant your partner could not reach you after a quiet month. Notifications sent by our server never carry the text of a message.
  • Presence: whether each app is currently online or typing, so your partner can see it.
  • A weekly byte count of the files your pairing sends, for a fair-use limit, deleted after five weeks.
  • Couple activity counts: for each pairing, daily counts with no content — how many messages, media, calls and call minutes, and AI chats and voice calls there were that day, and which of the two apps was active — kept under the pairing ID to understand how couples use the apps, together with a record of when the pairing was first seen and which kind of app build each side used. They are kept after you unpair, and contain no health data and no message content.

3. What We Do NOT Collect

  • Names, email addresses, or phone numbers — except a first name you choose to give the Coach, which is sent with your Coach requests and used to answer (Section 7), and an email address you choose to give when you contact support (Section 11)
  • Her cycle, mood or health information in readable form — except, only if she allows it in PinkyBloom, the context described in Section 7 (her life stage, cycle phase, the mood and energy she shares, your forecast and when your rough days tend to cluster), which reaches the Coach in readable form with your requests and is used to answer; it is not part of what we keep for review
  • Journal entries or recordings of your calls
  • Audio of your Coach calls (never recorded or kept; see Section 7)
  • Location data or GPS coordinates for our own use — if you send her a place, or share your live location with her, those coordinates are end-to-end encrypted on your phone first. We relay them; we cannot read them. See Section 4. If you allow the app to use your location, the Coach receives your location, rounded to about 110 metres, to answer (Section 7).
  • Advertising IDs or hardware device identifiers (the app creates its own random identifiers instead: an install ID, used for anonymous analytics and the Coach's usage limits, and a wallet ID for voice time — see Sections 7 and 8)
  • Browsing history

4. Encryption Details

Key exchange: Curve25519 ECDH. Public keys are exchanged in person by scanning a QR code, or remotely with a one-time pairing code that expires after 24 hours. Only public keys ever pass through our server, and it cannot derive your shared secret from them.

Encryption: AES-256-GCM with HKDF-SHA256 key derivation (salt: “PinkyBond-v1”).

Key storage: Shared secrets are stored in the iOS Keychain, protected by the device passcode, or in the Android Keystore, hardware-backed where available. The pairing keys never leave the device. If you turn on chat backup, the separate key that encrypts the backup is kept in your iCloud Keychain (or derived from a passphrase you choose) or in Android's Block Store (Section 12).

Nonce: 12 bytes, randomly generated per message to prevent pattern analysis.

5. Safety Mode

PinkyBloom includes a Safety Mode feature that sends synthetic (fake) data to PinkyBond when activated. This data is encrypted and transmitted through the same relay as real data, making it indistinguishable. Safety Mode is controlled entirely by the PinkyBloom user. The PinkyBond user is not notified when Safety Mode is active.

6. Payment

PinkyBond is free. Optional purchases (Plus for her, and voice calls with the Coach through a voice subscription or Extra time) are bought through Apple In-App Purchase or Google Play Billing; what we keep about those purchases is described in Section 7. We have never collected or stored payment details: purchases, including those made before 10 September 2026, when PinkyBond had a paid tier, are processed entirely by Apple or Google, and any subscription is managed and cancelled in your Apple Account settings or in Google Play.

7. The Coach (AI)

The Coach's answers are generated by a hosted AI service, not on your phone. Nothing described in this section is sent until you turn the Coach on and confirm that you are 18 or older. When you use the Coach, the app sends our server:

  • What you type to the Coach, with the recent turns of that conversation
  • In a voice call with the Coach, your voice, streamed live (see “Voice calls” below)
  • What you have told the app about yourself for the Coach (such as your first name, how long you have been together, whether you live together and what you want to work on)
  • Her context, only if she has allowed it in PinkyBloom (“Let his Coach use what I share”, off by default): her life stage, cycle phase, the mood and energy she shares, your forecast for the coming days and when your rough days tend to cluster. This goes, in readable form, to our AI model provider with your requests. Without her permission, none of her data and none of the Coach's earlier replies about her are sent — only your own messages
  • Your shared tasks, if you use them; any of her tasks that mention her health are replaced with “(private item)” before they are sent
  • Your location, rounded to about 110 metres (about a city block), if you have allowed the app to use your location, and the events in a stretch of your calendar, only when you allow it for a request that needs it
  • A photo of a meal or a nutrition label you choose to add to the food log
  • Technical data: a random install identifier (used to apply usage limits), the app's language, your region, your phone's local date and time, the wallet identifier described below, and, if you are paired, a random pairing identifier used only to count how often couples use the Coach

The Coach never receives your chat with her, her messages or her health data beyond what is listed above.

Processing and retention. Requests pass through our server to the AI model provider we use, which processes each request on our behalf to produce the answer. We do not authorise our AI, voice and speech providers to use your data to train their models. They process it only to provide their service to us, and they may keep it for a limited time under their own terms to run, secure and prevent abuse of their service; we do not control that period and do not promise any particular retention by them. We keep the text of conversations for review, as described under “Conversations we keep for review” below. We do not keep your photos or screenshots, and we keep counts with no content, such as the number of requests per day. Your conversation history with the Coach is also stored on your phone.

Conversations we keep for review. When you chat with the Coach or talk with it by voice, we may keep the text of the conversation: your messages, its replies and, for calls, a transcript of the words. We never keep the audio. Before we store it we remove email addresses, phone numbers, card numbers, street addresses and web links that carry tokens. We do not remove names or other things you say, and what you type may include health information; if you tell the Coach something, it can be in what we keep, so please do not include details about other people. Conversations that touch a crisis or eating care are kept only as a flag, without their text.

We keep it under a random install identifier (not your name) for up to 90 days, then delete it automatically. A small team under confidentiality reads it through an access-controlled tool, and our hosting and AI providers process it on our behalf. We use it to check and improve the quality and safety of the Coach, to test the product and to measure how it is used. Excerpts that reviewers label for testing are kept without direct identifiers. We never sell it, never use it for advertising and never give it to data brokers.

Your choice. In Settings, “Help improve the Coach” stops this collection and deletes what we kept for your phone. “Delete what I’ve shared” deletes it without turning the switch off. You can also ask us to delete it. In the European Economic Area, the United Kingdom, Switzerland and any other place where the law requires your permission first, we ask first and the switch starts off, so conversations are kept only if you turn it on, and the basis is your consent. Elsewhere the switch starts on, and you can turn it off at any time.

Voice calls. A voice call with the Coach streams your audio in real time to our voice-call provider, which hosts the call. Your speech is transcribed by a speech-to-text provider, the reply is written by our AI model provider, and it is spoken by a text-to-speech provider. These service providers process the call on our behalf only to transcribe your speech, write the reply and speak it, and we do not authorise them to use it for training. We do not record calls and we do not keep the audio. We may keep a transcript of the words of the call for review, as described under “Conversations we keep for review”. The context described above (such as what you have told the app about yourself, and her context if she has allowed it) is passed to the call when it starts. The location, calendar events and tasks the app sends for a call are held with the call and deleted shortly after it ends, within about two hours.

Lookups. When you ask the Coach to search the web, find a place, check the weather or play music, our server sends the search, and your location, rounded to about 110 metres, where the lookup needs it, to the service that answers it: a web-search provider, a places-and-maps provider, a public weather service or a music service. A barcode you scan for the food log is looked up by our server in a public food database, not by your phone. These lookups do not include your identifiers. We use your location only for that request, while you are using the app, and do not store it beyond it (on a call it is held with the call and deleted within about two hours).

Voice time and purchases. The app creates a random wallet identifier, kept in the iOS Keychain or in the Android app's backed-up data, and attaches it to App Store or Google Play purchases of voice time. Under that identifier our server keeps your purchases (product, dates, renewal state and the store's transaction identifier), your remaining voice time, and a record of each voice call: when it started, how long it lasted, the time used and which lookups it used — never the audio or what was said. We do not link the wallet identifier to your name, email or store account. The only exception is an optional account, which can link your wallet identifiers so purchases can be restored (see “Accounts and Server Memory”). These records are kept to account for your voice time and for our financial records.

8. Analytics

To see which features help and to find problems, PinkyBond collects anonymous usage analytics. It is on by default, and you can turn it off at any time in the app's Settings; the app works the same either way. The iOS and Android versions collect the same analytics:

  • Interaction events: app opens, sessions and their length, screens viewed, and which features you used — never what you wrote, logged, or sent.
  • Feature health: the steps of pairing; whether notifications are allowed and arrive; whether an AI answer appeared and roughly how fast; and for calls, their type (audio or video), how they connected, how long they lasted, and how they ended.
  • Error codes: a short category code when something fails (for example, a message that could not be sent). When the app crashes or freezes, the report holds the kind of failure, roughly how long a freeze lasted, the iOS or Android version, and the memory offsets (iPhone) or code names and line numbers (Android) of the app's own code that was running — technical labels, not text. It never holds an error message, anything you wrote or logged, a name, or any health data, and it is tied only to your anonymous install ID. We use no third-party crash-reporting service: on iPhone the reports come from Apple's own diagnostics, which iOS shares with us only if you allow it in your iPhone's settings.
  • Context: a random install ID the app creates (not tied to your Apple or Google account, and never stored together with your pairing ID), app and system version, device model, the app's language, the region set on your device (never GPS, and never worked out from your IP address), and whether you are paired and roughly how long ago, in ranges such as “4–7 days”.

Analytics never include cycle, mood, or health information, check-ins, messages, or anything that identifies you or your partner. Events go to our own backend (hosted on Convex), which does not store IP addresses with them, and they are never sold, shared, or used for advertising or cross-app tracking. Individual events are deleted after 180 days; daily summaries per anonymous install are kept to measure long-term trends. Turning analytics off stops all further collection.

9. Data Deletion

An account is optional; if you created one, see “Accounts and Server Memory” below for how to delete it. Besides that, what there is to delete is the pairing, and you can do that at any time from Settings → Remove Partner. This permanently destroys the pairing, removes all locally stored data, and deletes what our server holds for your pairing ID: undelivered messages and files, delivery records, the call log and notification tokens. Removing the pairing does not delete the voice-call and purchase records kept under your wallet identifier (Section 7), which we keep to account for your voice time and for our financial records. It also does not delete the couple activity counts described in Section 2.

Conversation records kept for review (Section 7) are deleted by the Settings switch “Help improve the Coach”, by “Delete what I’ve shared”, or on request, and automatically after 90 days.

10. Law Enforcement Requests

If we receive a valid legal request, we can only provide what is described in Sections 2 and 7: encrypted messages and files that have not been delivered yet, which we cannot decrypt because we do not possess the keys; content-free delivery records from the last 30 days; the call log from the last 90 days, which shows when the two phones in a pairing called each other, for how long and with what outcome, but never what was said; and the voice-call and purchase records kept under a wallet identifier (Section 7); the couple activity counts (Section 2); and any support request you sent us (Section 11). We may also hold the text of Coach conversations kept for review (Section 7), which we could be required to provide; we never keep audio. We will notify affected users of legal requests unless prohibited by law.

11. Support requests and feedback

If you contact us from the app's support form, we receive what you write, any screenshots you attach, the email address you give (optional), your anonymous install identifier, and the app version, system version and device model. In the iPhone app, if you answer “Not really” when the app asks whether you are enjoying it and tell us what we could do better, we receive what you write with the same identifier and technical details. Both are stored by our backend (hosted on Convex) and sent to our team by email through an email delivery service, so that we can answer and improve the app. They are used for nothing else, and are kept for about 90 days, then deleted.

12. Chat backup

Backing up your chat is optional and off until you turn it on. On iPhone, the backup is written to your own iCloud Drive, in the app's own container, and encrypted on your phone first with a key kept in your iCloud Keychain (or, if iCloud Keychain is off, derived from a passphrase you choose), so that a new iPhone signed in to your iCloud account can restore it. We never receive the backup or the key. On Android, the backup is written to your own Google Drive — not to us. It goes into the app's private app-data folder: PinkyBond asks Google for one narrow permission, drive.appdata, which cannot see any other file in your Drive — not your documents, not your photos. The backup is encrypted on your phone before it is uploaded, with a key held in Android's Block Store; we never receive the backup and we never receive the key. Deleting the backup from inside the app removes it from your Drive, and you can revoke access at any time in your Google Account settings.

13. Children's Privacy

PinkyBond is not intended for use by anyone under the age of 17. We do not knowingly collect data from children. The Coach is available only to people who confirm they are 18 or older; we rely on that confirmation and do not verify age. If we learn that a person under the required age has used the app, we will end their access and delete the data we hold about them. We do not sell the personal information of anyone, including anyone under 18.

How We Share Data

We never sell your data, never show ads, and never give it to data brokers. We share it only in these ways:

  • Service providers acting for us. Companies that process data on our behalf and under our instructions, only to provide their service to us: hosting, database and file-storage providers, the AI model, speech and voice providers and the lookup services described in Section 7, an email delivery service for support messages, and Apple and Google for app distribution and purchases.
  • Your partner, only what you choose to share (see partner sharing).
  • Legal and safety. If we believe in good faith that the law, a legal process or a valid government request requires it, or that it is needed to protect someone’s safety, our rights or the service. We will tell you first where we are allowed to.
  • A business transfer. If we are part of a merger, sale or reorganisation, your data may move to the successor, which must honour this policy or tell you first.

Security

We protect data with encryption in transit, access controls and, for partner content, end-to-end encryption that we cannot decrypt. The conversation review tool is access-controlled and used by a small team under confidentiality. No system is perfectly secure and we cannot promise that data will never be accessed without permission. If a breach affects you, we will tell you as the law requires.

Where Data Is Processed

We and our providers process data in the United States and in other countries where they operate. Those countries may have data protection laws different from yours. If you are in the European Economic Area, the United Kingdom or Switzerland and your data is transferred outside it, we rely on the safeguard the law requires for that transfer, such as the European Commission’s standard contractual clauses (with the UK addendum where it applies), an adequacy decision, or the EU-US Data Privacy Framework where a provider is certified. You can ask us through our contact form for information about the safeguard that applies.

Your Rights and Choices

You can control your data from inside the app:

  • “Help improve the Coach” in Settings stops us keeping your conversations and deletes what we kept for your phone; “Delete what I’ve shared” deletes it without turning the switch off.
  • Anonymous Analytics in Settings turns analytics and crash diagnostics off.
  • Remove Partner and Delete All Data delete what our servers hold for a pairing.
  • Export lets you take your health data with you, and deleting the app removes what is stored on the phone.
  • If you have an account, you can export your account data and delete the account (see “Accounts and Server Memory”).
  • You can ask us to access, correct or delete what we hold, or to stop using it, through our contact form.

Depending on where you live, you may also have the right to know what we hold, to receive a copy, to correct or delete it, to restrict or object to its use, to withdraw consent, to appeal our decision, and to not be treated worse for using your rights. We will answer within the time the law sets. Send requests through our contact form. Because most people use the app without an account, we may need details only you can give (such as your account sign-in, purchase details or your install identifier) to find and verify your records; we will not ask for more than we need. We will answer within the time the law sets (generally 45 days in the US states that give these rights, and one month under the GDPR and UK GDPR, each extendable where the law allows). If we decline a request, you can appeal by replying to our answer through the contact form with the word “Appeal”, and we will answer your appeal in writing. You may use an authorised agent, for whom we may ask for proof.

Notices for Specific Places

These notices add to the rest of this policy for people in the places named. Where they differ, the more protective one applies to you.

  • European Economic Area, United Kingdom, Switzerland. The controller is Veronata, Inc., 2261 Market Street STE 22406, San Francisco, CA 94114, USA; contact us through our contact form. We use your data on these bases: to provide the app and the features you ask for (performing our contract); to keep the service secure, prevent abuse and understand how the app is used (our legitimate interests, which you can object to); to keep financial records (a legal obligation); and, for health information (your cycle, pregnancy and health context, and anything you tell the Coach), your explicit consent, which you give when you turn the Coach on and can withdraw at any time. In these places conversations are kept for review only if you turn on “Help improve the Coach”; the switch starts off. You have the right to access, correct, delete and receive a copy of your data, to restrict or object to its use, to withdraw consent, and to complain to your data protection authority. Recipients and transfers are described in this policy, and retention periods are in the section on how long we keep data.
  • California (CCPA/CPRA, CMIA). In the last 12 months we collected these categories: identifiers (random install, wallet and, if you create an account, account identifiers); commercial information (purchases); internet and app activity (analytics events); user content (what you tell the Coach, under the conversation rules in Section 7); and sensitive personal information (health, cycle and pregnancy information you log or share, and account log-in identifiers). We collect it from you and your device, use it to provide, secure and improve the app as described in this policy, and disclose it only to service providers that process it for us and to your partner at your choice. We do not sell or share personal information, including sensitive personal information, for cross-context behavioural advertising, and we use sensitive personal information only for purposes the law allows without a right to limit. You have the right to know, access, delete and correct, to opt out of sale or sharing (we do neither), and not to be discriminated against for using your rights. You may use an authorised agent; we may ask for proof.
  • Washington (My Health My Data Act), Nevada and similar laws. This is also our consumer health data notice. We collect consumer health data that you log or give us (cycle, pregnancy, symptoms, and health details you tell the Coach) to provide the features you ask for. We share it only with service providers that process it for us and with your partner when you choose to share it. We never sell it. You can withdraw consent, ask us to confirm and give you access to what we hold, and ask us to delete it, using the app’s settings or our contact form; if we decline, you can appeal, and you may contact your state attorney general.
  • Other US states, Canada (including Quebec), Australia, Brazil and elsewhere. Where your local law gives you rights over your personal information (such as access, correction, deletion, portability, objection or withdrawing consent), you can use them through our contact form and we will respond as the law requires. We do not sell your personal information. Your data is processed in the United States and other countries as described above.

Accounts and Server Memory

An account is optional. PinkyBond works without one, and everything that is free stays free without one. Where the app offers an account, you can create one with Apple, with Google or with your email address. This section describes what we hold if you do, and how it differs from the rest of this policy.

  • Who you are to us. For Apple or Google sign-in, the identifier that provider gives us for you (not your password, which we never see). For email sign-in, we send a one-time code to your address through an email delivery service; we then keep only a one-way cryptographic fingerprint of the address, so we can recognise it next time, and a partly hidden version (for example j***@g***.com) to show you which address you used. We do not keep the address itself. One-time codes expire after 10 minutes.
  • Sign-in sessions. Secure tokens (stored only in hashed form) for each phone you are signed in on, tied to that phone’s random install identifier. They expire after 60 days without use and in any case after a year, and you can sign out of all of them.
  • Your purchases link. A link between your account and the random wallet identifier(s) described in this policy, so that voice time and subscriptions can be restored on a new phone. The purchases themselves remain with Apple or Google and in the records described above.
  • Your partner link. If you are paired, a record that links your account and your partner’s account to your pairing, together with a key derived from your pairing that lets us check that you are really the two people who paired. It does not let us read your messages, which stay end-to-end encrypted. Unpairing ends the link.
  • What the Coach remembers, on our servers. While you are signed in, the notes the Coach keeps about you (dates, routines, what helps, details about your partner, and similar) are kept on our servers so they follow you to a new phone, with a copy on your phone. They are encrypted at rest on our servers. They are not end-to-end encrypted, because the Coach must read them to use them: our systems decrypt them when you chat or call and pass them to our AI model provider with your request, as described above. You can see, edit and delete each note, turn on incognito so that the Coach neither reads nor saves notes, and use forget everything, which empties every notebook. The Coach does not keep sensitive notes without your yes.
  • Notes about the two of you. A shared notebook about the two of you holds only facts that both of you have approved. Either of you can withdraw one at any time, and editing a fact asks for approval again. A fact reaches either partner’s Coach only while both of you have approved it and you are linked. Your own notes are never visible to your partner or to your partner’s Coach. If you unpair, the shared notebook is archived and no longer read.
  • An encrypted copy of your pairing keys (optional). If you choose to back up your pairing keys with your account, we store only ciphertext that was locked on your phone with a key we do not have. We cannot read it.

Why we use it. To sign you in, restore purchases, keep your notes across phones, make the partner features work, and protect the service from abuse. We do not use account data for advertising, never sell it and never give it to data brokers. For people in the EEA, the UK and Switzerland the basis is performing our contract with you; for abuse prevention, our legitimate interest in keeping the service secure; and, for notes that reveal health information, your consent, which you can withdraw by deleting the notes or the account.

How long we keep it. Until you delete your account or your notes, except sign-in sessions (see above) and one-time codes (10 minutes). Conversations we keep for review (Section 7) are still held under the install identifier, not your account; deleting your account deletes them for the phones you were signed in on, and the rest expire after 90 days.

Export and delete. You can ask for a copy of your account data (your sign-in methods, linked wallets, partner links and notes) and you can delete your account. Deleting it removes your sign-in identities, sessions on all phones, the link to your wallet identifiers, every notebook of notes about you, any backed-up pairing keys and your partner-link records. The couple is unlinked and the shared notebook is deleted; your partner’s own notes are not touched. Purchase, voice-time and call records stay with the wallet identifier, as described above, and only the link to your account is cut. Deleting your account also deletes the conversations kept for review from the phones you were signed in on; for any other phone, use “Delete what I’ve shared” or ask us. You can also ask us to delete your account through our contact form.

14. Changes to This Policy

We will notify users of material changes through the app. Continued use after notification constitutes acceptance.

15. Contact

For privacy questions or data deletion requests, please reach out through our contact form.

Veronata, Inc.
2261 Market Street STE 22406
San Francisco, CA 94114

Download on the App StoreGet it on Google Play