How Affinira handles personal data
The short version
The marketing pages you are reading collect almost nothing and need no account; the account area is different, and is described separately below. Cookies and analytics follow the rules described below; the site also uses the browser storage described below, and its hosting platform's own operational logging is the platform's, described under “Hosting and server logs”. Account features — signing up, and the people and memories you save — belong to the account area. Signing up and saving are two separate things a site can offer, and each depends on how it was set up: where saving is offered, a save goes to this site's database and the screen tells you whether it went through; where it is not, the site tells you so instead of taking your details. Affinira's own code can set three cookies for the marketing and review surfaces, and all three are switched off on Vercel, which is where this site is built to run; a site set up for accounts also sets a session cookie once you sign in, and two short-lived markers on the sign-up and password-reset journeys, all described in the cookie policy. The cookie policy lists what they are, what one of them would hold, and exactly what that switch checks. Analytics — cookieless Vercel Web Analytics, on marketing pages only — runs only if you affirmatively accept it in the consent banner; rejecting or ignoring the banner loads nothing, and you can withdraw at any time under Cookie settings. If you email us and the message arrives, we hold your address and what you wrote. Our hosting platform’s own logging is the platform’s, described under “Hosting and server logs”. Affinira also uses storage in your own browser — exchange records and onboarding drafts in session storage, consent choices and theme preferences in local storage — which is set out under “Storage in your browser” below. Where saving is offered in the account area, the people, relationships, notes and memories you enter there are real data about real people, held as described under “Account data” below. This page describes how the site behaves today.
Who is responsible for your data
The data controller is Eivura, S.L., Avenida de Roma 23, 43005 Tarragona, Spain (NIF B26588327, VAT number ESB26588327). The address for all privacy questions and requests is hello@affinira.com. Full company identification is on the legal notice page.
This policy also covers Affinira's Android app and its Wear OS watch app on Google Play. The phone app is a native app. It connects to the internet only to reach Affinira's servers (affinira.com), over HTTPS, and it handles the information described on this page plus the app data described below. It asks for your camera only when you use Scan, and for your microphone only when you record a Debrief note. The watch app asks for its microphone only when you record a Debrief note on the watch. You can turn off either permission in your phone's or your watch's settings. Your phone and your watch can share your card's link by NFC when you hold them near another phone, and your phone can read another person's card the same way.
With the watch app, you can record a Debrief note of up to 2 minutes. The watch app does not connect to the internet itself. It keeps the recording encrypted on the watch and sends it to the Affinira app on your paired phone through Google Play services. The phone holds the audio only in its memory and sends it to our servers, which pass it to Microsoft Azure Speech in France to turn it into text. Our servers do not store the audio, and they do not store the text at this step. The phone keeps the text, encrypted, until you approve or delete it. After 7 days an unapproved note is no longer shown, and the app deletes it the next time it runs. When you approve the note, the phone sends the text to our servers. We tidy it with Claude by Anthropic, run on Amazon Bedrock in the EU, as for other Debrief notes, and save both the original text and the tidied note in your account. Each recording sent counts toward your monthly voice-note limit, even if you delete the text. The watch deletes a recording once your phone has dealt with it, or when you delete it before it is sent. A recording belongs to the account that was signed in on your phone when you made it. If you sign out on your phone, the watch keeps any recording that is still waiting, and sends it only when the same account signs in again. Your phone also sends the watch your cards, their labels and logos, your plan and your first name, so the watch can show your card and its QR code. Signing out on your phone removes your cards from the watch. The watch app is not included in backups.
In the Android app, your Menu, Home and QR screens keep an encrypted copy on your phone, so they open without a connection. Only the copy of whoever is signed in is kept. If you scan a card, its photo waits on your phone, encrypted, until it has been read or cannot be read, and is then deleted from your phone. The details read from it stay on your phone until you add the contact or discard them. If you save a contact, or record or type a Debrief note, while the connection is poor, it waits on your phone, encrypted, until it reaches your account, and is then removed from your phone. If your account cannot take a scanned contact as it is, it goes back under Ready to review until you correct it or delete it. A note that has not been sent stays on your phone, and the app tries again a few times to send it. Signing out of the app deletes all of this from your phone, including any photo, recording, contact or note that has not been sent yet, and the text of watch notes you have not approved. Signing out also removes your card from the lock screen and from your watch. Recordings still waiting on your watch are not deleted, as described for the watch app above, and the Follow-ups widget stays connected, as described below.
When you sign in to the Android app, it creates a security key in Android's protected key storage on your phone. The private part of the key never leaves your phone. We store the public part with your app sign-in, so that only this phone can keep your session going. With it we store the app's version, when the session started and when it was last used. Every request from the app also carries the app's version number, which we use to tell you when an update is needed. The app sends your phone's time zone to your account, so that follow-up and reminder dates match your day. It replaces a time zone you set on the website. When you sign out, we end the app session as soon as your phone is online, and we delete its record after 30 days. The app then deletes the key from your phone.
The Android app makes its own notifications on your phone. It does not use a push service such as Google's. While you are signed in and Follow-ups due or Card activity is on, the app asks our servers about every 15 minutes, over the same secure connection it uses for everything else, how many follow-ups are due in the next 14 days and how many times your cards were saved or shared. The answer holds only dates and numbers, never a name, a company or a card. To answer, we keep two running totals for your account (saves and shares) and the time they last changed. To do this we keep a running count of Save contact taps and shares for each account, whether or not card Analytics is on. We don't record who saved or shared, and the totals are deleted with your account. Your phone keeps the last numbers and the upcoming follow-up dates so that it can show follow-ups at 9am your time; signing out deletes them. Your notification choices are saved on that phone only. When a note you recorded on your watch is ready to review, your phone shows that notification itself and sends us nothing extra.
Earlier test versions could store a browser push address; none remain.
If you add the Follow-ups widget to your phone's home screen, the app connects it with a key of its own, because the widget runs outside the app. Your phone keeps the key and the last list the widget fetched: the name and company of each person due for a follow-up, and why they are due. We store only a hashed copy of the key, with when it was made and when it was last used. A key stops working 90 days after it was last used, and we keep up to 10 for each account. Signing out of the app does not disconnect the widget. To stop it, open Settings, go to This phone and choose Disconnect widgets. Deleting your account also removes every key. The key and the list are not included in your phone's backups.
What we process today
Email you send us is one category described below; where this site offers account saving, the account-data section applies as well. The hosting platform’s own logging is the platform’s, described under “Hosting and server logs”. Analytics only ever begins if you accept it. Affinira also uses storage in your own browser, which is described below alongside what it does not process.
Email, when you write to us
If you email hello@affinira.com, what arrives, if it arrives, is your email address, anything you chose to write, and the ordinary headers email carries. What we do with it is an undertaking we have made, not a control this site enforces: to use it only to read and answer your message, never to add you to a mailing list because you wrote to us, and to share it with nobody. News emails go only to people who asked for them and confirmed their address.
Hosting and server logs
The site is built to run on Vercel's infrastructure. The operational logs that platform generates — request logs, build logs, and error diagnostics — are Vercel's, governed by its terms and described in its own documentation. Our own application logging rules forbid writing names, email addresses, message text, or tokens into logs. Where those servers run is set out in “Where your data is hosted” below.
Analytics, only if you accept it
We use Vercel Web Analytics to understand aggregate usage of our public marketing and resource pages. The service is enabled, but its script loads only after you accept analytics. Rejecting or ignoring the banner loads no analytics script and sends no analytics events. You can withdraw consent at any time in Cookie settings to stop further collection. Product screens, public profiles, checkout and account pages are excluded. We remove query strings and fragments from reported page URLs. Vercel may process page-view timestamps, referrer information, approximate location, browser, operating system and device information. It uses a hash derived from the incoming request to distinguish visitors without analytics cookies; Vercel says visitor sessions are automatically discarded after 24 hours. This is not a promise that aggregate reports are deleted after 24 hours. Our cookie policy explains the consent controls and browser storage.
Storage in your browser
Affinira uses storage in your browser. Exchange records and onboarding drafts use session storage. Consent choices and theme preferences use local storage. The cookie policy describes the consent choice and the theme preference in full.
Account data, where this site offers accounts
Where account saving is available, a save is sent to this site's own database, and the screen tells you whether it went through. The access rules for that database are written in this product and tested against a local database. As written and tested, those rules let only you read your relationships, your notes, and any channel or link you mark private; they treat the fields you mark public as public, and show them at your address only while your profile is published; and they let the members of your organisation read the rest of your profile record. Signing up and saving are two separate things a site can offer, and where either is unavailable this one says so before taking your details rather than after.
If you choose to sign in with Google, Google confirms who you are and shares your name and email address with us, through Supabase, which handles sign-in for us. We do not receive your Google password. Google's own privacy policy applies to Google.
When you scan a paper card, the photo is read by Claude by Anthropic, run on Amazon Bedrock in the EU, to fill in the contact's details. Affinira does not store the photo.
The same processing applies when Affinira reads printed contact details from an event badge. QR codes on badges are read on your device first.
When you record a Debrief voice note, the audio is turned into text by Microsoft Azure Speech in France, and the text is tidied into a note by Claude by Anthropic, run on Amazon Bedrock in the EU, after you review and approve the transcript. Your recordings and notes are not used to train AI. Our AI providers process your Debrief content without retaining it. Affinira does not store audio on its servers; recordings are removed from your device after successful transcription. If you are offline, the recording waits on your device until it can be sent or you delete it. In the Android app, signing out also deletes it. A note recorded on the watch follows the path described for the watch app above. Affinira keeps the note in your account, on a contact if you link one. It is deleted when you delete it, when the last contact it is on is deleted, when your account is deleted, or when our contact retention rules remove it.
If your team connects its own CRM (HubSpot or Zoho CRM) or an automation in Zapier or Make, Affinira sends contact details from your team's account to that service when your team asks it to. That service then holds them under your team's own agreement with it.
Team owners and admins see each member's account name and email address in the team's member list.
Some features send an email for you to someone else: emailing your card to a contact you scanned, inviting someone to your team, or inviting someone to be an ambassador, where that is offered. We send it to the address you give. Each of these emails has a link that lets the recipient stop further emails of that kind from Affinira.
If you connect Claude or ChatGPT to your account (Ultra and Team), Affinira sends that assistant only what you ticked when you connected it: details from your own cards, including their private labels and ventures (never the links that open them), your due follow-ups, and up to 10 of your own contacts that match a search. It never sees your team's contacts or your Debrief recordings. If you also ticked them, the assistant can change your cards' details, private labels, design (including text colour, text style, languages and translations) and QR style, create new live cards, and create your events and change their name, dates and place (it then also sees those details for up to 25 of your events). It can also add, replace or remove your card images (cover, photo, logo, icon logo and moving logo) and change how they fit, and add, change or remove your ventures and their logos. Before an image is replaced or removed, a venture or a venture's logo is removed, or an earlier version is put back, Affinira requires a second, confirming request and tells the assistant to check with you first. The assistant can never delete a card or an event. When you attach an image in ChatGPT, Affinira fetches it once from OpenAI's file service. Otherwise the assistant sends the image through a one-time upload link that stops working after 10 minutes. The image is then kept as your card's image. The assistant can show you a picture of your card's public page through a link that works for 15 minutes. The picture never shows your QR code, your private label or details that are not public, and we do not store it. We record when each picture was made, to apply a weekly limit. Before the assistant changes a card's details, design or image fit, or puts back an earlier version, we save the card as it was, so that you can undo the change. We keep the last 3 saved versions of each card for 24 hours. They never include images, so an image that was replaced or removed cannot be brought back. What the assistant receives is held by its provider (Anthropic or OpenAI) under your own account with them, and their terms apply. We keep a record of each connection and of each request it makes (which action and how many results, never what they contained), and delete these records when you delete your account. You can disconnect an assistant at any time under Connected apps, and a Team admin can switch assistants off for the team.
What we do not process
The people and conversations shown in the product tour are synthetic fixtures, not records of anyone, and what the tour keeps in your browser is described above. No tracking cookies exist, and no analytics runs without your consent — the only measurement is the consent-gated, cookieless analytics described above (the cookie policy covers this in detail). Payments are processed by Stripe. Affinira never sees or stores your full card details; we keep your Stripe customer reference, your plan and its billing status.
What changes where these features are available
Some features are not offered everywhere. Each item below applies only where its feature is available.
Where the contact inquiry form is enabled
Inquiries you submit through the site — your message and the contact details you include — will be stored so we can answer them and keep the thread. Where this site does not offer the form, the way to write to us is email.
Where accounts are enabled
Where accounts are available, the sign-in provider holds your sign-in identity. Where saving is also available, a save of your profile, connections, memories, or follow-ups is sent to this site’s database and the screen reports whether it went through; where it is not, saving is refused rather than accepted. Either exists only for people who have created an account on that site; the storage the prototype itself uses is described under "Storage in your browser".
Where accounts are available, the product's public/private rule applies to your records the way it applies to the fixtures in the tour: private notes, memories, and follow-ups are never treated as public — and an owner's profile is served at its public address only while it is published. The security page describes how that boundary is built.
Your rights, and how to use them
You can ask us what personal data we hold about you, ask for a copy of it, ask us to correct it, or ask us to delete it. Send any of these requests to hello@affinira.com — it is the single address for privacy requests. Before anything is disclosed or deleted, the person asking has to be confirmed as the person the data is about. We only act on a request from the email address on your account, or after you confirm it from that address. If that isn't enough to know it's you, we may ask for one more detail about your account. We never ask for ID documents for this. If you have neither created an account on a site where accounts are available nor emailed us, the honest answer is that we may hold nothing about you at all. If you have an account, the account data described above is what a request reaches. If you have emailed us and the message arrived, that correspondence is what a request reaches; deleting it when you ask is an undertaking we have made, handled with the same check.
Where data lives, and for how long
- When you share your details on someone’s card
- Kept untilUntil the card owner deletes it, Affinira removes it following a verified request, or the owner’s account is erased.
Where your data is hosted
This is where each part of Affinira runs:
- Website and servers: Vercel, running in Dublin, Ireland.
- Database, files and sign-in: Supabase, in Ireland.
- Email: Resend, sending from Ireland: account email from replies.affinira.com and news from news.affinira.com. The emails we send you, with your name and email address, pass through it.
- Debrief voice transcription: Microsoft Azure, France Central.
- AI for Scan and Debrief tidy-up: Anthropic's Claude, run on Amazon Bedrock in the EU through Vercel AI Gateway.
- Payments: Stripe, through Stripe Payments Europe, Limited in Ireland.
Some of these providers are companies based in the United States that, with their sub-processors, may access data from outside the European Economic Area, for example for support or security. For any such transfer we rely on the EU–US Data Privacy Framework where the provider is certified under it, and otherwise on the European Commission's Standard Contractual Clauses in that provider's data processing agreement. If your team connects a CRM, Zapier, Make, Claude or ChatGPT, that service's own locations apply.
Retention periods
We keep your data while your account exists, unless this page gives a shorter time. When you delete your account, your cards stop working at once. We then erase your cards, photos and logos, contacts, notes and login. We keep billing records, because the law requires it. We also keep entitlement and subscription-revocation records, account-access history, administrative holds, deletion records and audit records. These kept records are not anonymous. Stripe keeps its own customer and billing records. The delete your account page lists what is deleted and what is kept.
When this policy changes
This policy describes actual behavior. The cookie policy and the consent controls describe the same choices from their own side. The date at the top of this page is the day this policy was last reviewed. It is not legal advice.