Privacy policy for NFC.cool Business Card

What this policy covers

This policy covers:

• the Business Card by NFC.cool app for iPhone, iPad and Android, and its App Clip;
• the card pages at mycard.nfc.cool, and at a team's own domain when a team connects one;
• NFC.cool Business Card for Teams: the web console at business.nfc.cool, its API, and its connection for AI assistants.

This policy also covers cards made in the NFC.cool Tools app and the contacts left on them.

Everything else in the NFC.cool Tools app, and the nfc.cool website, have their own privacy policy.

Who is responsible

The controller for the processing described here is:

There are two exceptions, where we process details on someone else’s behalf:

• Details people leave on a card. The card's owner is the controller, or on a team card the team. See Details people leave on a card.
• A team's cards for its members, and its invitations. The team is the controller. See Teams.

We have not appointed a data protection officer. For any question about your data, write to the controller at the address above.

The data we process, and why

Your account

When you create an account we store:

• your email address and a username. The username is part of your card's web address, so it is public;
• your password, stored only as a salted hash, never as text;
• if you use Sign in with Apple: the user identifier Apple gives us and the email address Apple shares, which can be a private relay address;
• whether you confirmed your email address, when you joined and when you last signed in;
• which app you signed up in, and the customer identifier of your in-app subscription (see Subscriptions in the app);
• the 4-digit PIN you can set to protect private cards. We store it encrypted, and decrypt it only to check it and to show it to you;
• the date you started a team trial, if you did, because each person gets one trial.

The apps keep you signed in with a short access token (15 minutes) and a refresh token (180 days). The iPhone app keeps them in the iOS Keychain. The Android app keeps them encrypted on the phone and also in Google’s Block Store, which can include them in your Google account backup, so you stay signed in on a new phone. We keep a record of each refresh token until it expires, so that “sign out everywhere” and a password change can end every session. The web console uses a session cookie.

Purpose: to give you an account, sign you in, keep it secure and contact you about it. Legal basis: performance of our contract with you (Art. 6(1)(b) GDPR).

Your cards

A card holds what you put on it: your name, photo, job title, company, department, a short bio and note, phone numbers, email addresses, postal addresses, websites, social media profiles, your birthday, logos, a header image, colours, and the title, subtitle and image of its App Clip card. The app also uploads the card as a vCard, which we store.

Each card is a web page at mycard.nfc.cool, and on a team card also at the team’s own domain if the team connected one. Anyone who has the link, taps your NFC tag or scans your QR code can open it and save your details.

• Public card: listed in our sitemap. Search engines may index it.
• Private card: opens only with its PIN, and tells search engines not to index it. A link you share from the app can carry the PIN, so the person you give it to can open the card directly.

Purpose: to show your card to the people you share it with. Legal basis: Art. 6(1)(b) GDPR.

People who view a card

When someone opens a card page or the App Clip, we record:

• that the card was viewed, and when;
• that the card was saved to contacts, and when;
• that a link on the card was tapped, and when, and whether that was on the web page or in the App Clip.

These records hold no IP address, no device identifier, no cookie and nothing else about the visitor. The card’s owner, and on a team card the team, see them as counts.

To deliver a page, our server receives the visitor’s IP address and browser details, as every web server does. Our server logs keep them for a short time (see Technical data, errors and security). We also use the IP address to limit abuse, such as too many PIN attempts or contact form submissions: the counters are kept in our cache and expire after at most a day. Card images and page files are delivered by the content delivery network of our hosting provider, DigitalOcean.

Purpose: to show card owners how their card is used, and to protect the service and its users from abuse. Legal basis: our and the card owner’s legitimate interests in those purposes (Art. 6(1)(f) GDPR).

Details people leave on a card (leads)

A card owner can switch on lead capture. A visitor can then leave their details with the card owner: first name, last name, email address, phone number, job title, company and a note, and, if the card asks for one, a selfie. The card decides which of these it asks for. This happens on the card page or in the App Clip.

When a selfie is sent, our server resizes it, adds the card owner’s and the visitor’s names and a logo, and stores it privately with the contact. It can be opened only through a short-lived signed link, given to the people who can see the contact.

Who is responsible for these details. The card’s owner decides whether to collect contacts, which details to ask for and what to do with them. On a team card, the team decides. So the card’s owner or team is the controller of these details, and is responsible for using them lawfully and for telling the people they collect them from what they do with them. NFC.cool processes them on the owner’s or team’s behalf (Art. 28 GDPR): we store them, deliver them as described below, and use them for no purpose of our own. For teams this is set out in our data processing agreement, and for everyone else in the Business Card terms.

After a contact arrives, the card owner, and on a team card the team, can add notes, tags and a status, assign the contact to a team member, export contacts as a CSV file, and on a team send follow-up emails.

When a contact arrives:

• the card owner's phones get a push notification with the visitor's name. On a team card, the team's owners and admins (or the people the team chose) are notified too, with the name of the member who received the contact;
• if the card owner runs Conference Mode, the visitor's name and company appear on its Live Activity;
• on a team card, the details are sent to the team's webhooks, HubSpot or Salesforce, if the team connected them, and a follow-up email is scheduled if the team set one up.

Retention: a contact stays until the card owner or the team deletes it, or the card owner deletes their account. See How long we keep data for team contacts.

If you left your details on a card. The card’s owner or team decides about your details, so ask them first. They can show you what they hold, correct it and delete it. If you cannot reach them, or they do not answer, email info (at) nfc (dot) cool with the card’s link. We pass your request on to them and help them answer it. If a team is deleted, its owner chooses whether a contact assigned to one of its members moves to that member’s own account, where that member becomes responsible for it, or is deleted with the team.

Follow-up emails from teams

A team member can email a contact who left an email address, using the team’s templates. A team can also send one automatically after a delay, to every new contact during an event of up to 7 days.

• The email is sent by our email provider, Mailjet, from an NFC.cool address. It shows the member's name as the sender and sends replies to the member.
• Every email has an unsubscribe link. After someone unsubscribes, the team can no longer email that address. If an email bounces or is reported as spam, the team can no longer email that address either.
• We do not track whether a follow-up email was opened.
• We keep a copy of each email sent (recipient, subject, text and delivery status) with the contact.

Only teams on a trial or a paid plan can send follow-up emails, and the number per member and per team is limited.

Teams: NFC.cool Business Card for Teams

When someone sets up a team at business.nfc.cool we store the team’s name, its brand (logos, colours, company name, website), and, if the team sets up an App Clip card, its place name, address and phone number. We store the team’s members and their roles, invitations (the email address and name a team admin enters, and the card prepared for the person), requests to move a card into or out of the team, and the team’s cards.

The email we send with an invitation says which team invited you and links to this policy.

Who is responsible for members’ cards and invitations. The team decides what goes on the cards it makes for its members and whom it invites, so the team is the controller of these details. We process them on the team’s behalf under our data processing agreement. Your own account (your email address, password, sign-in and settings) is ours to look after, as described in Your account.

An admin can create and edit cards for members and set their job title and department. A member can see and edit their own card within the limits the team sets.

When a member leaves the team or deletes their account, the team keeps the card and the contacts it collected. If the member deleted their account, we first remove their name, photos, contact details, birthday and PIN from the card. Their job title and department stay on it until the team changes them.

Team billing: teams pay through Stripe. Stripe collects the payment details, billing address and any tax ID on its own checkout page. We do not see card numbers. We send Stripe the team’s name, the buyer’s email address and our internal team identifier, and we store Stripe’s customer and subscription identifiers, the plan, its status and trial dates.

Connections a team can switch on. These send data only when the team’s admins set them up:

• Webhooks: for each new or changed contact we send its name, email, phone, job title, company, note, tags and status, the card's label, the email address of the member who holds the card, and the name and email address of the person it is assigned to, to an address the team chooses, for example a Zapier or Make hook. We keep a log of each delivery, with what was sent, for 30 days, or 90 days if it failed.
• HubSpot and Salesforce: each contact's name, email, phone, company and job title, its status where the team's account has a matching one, and a note with who captured it, its tags, its message and the team's notes with their authors' names, are created or updated in the team's own account. To assign the contact to the right person there, we look up the member's email address. We store the access tokens these services give us in encrypted form, and a delivery log for 30 days, or 90 days if it failed.
• Access tokens and AI assistants: an admin can create an access token for the team's API, or to connect an AI assistant (such as ChatGPT or Claude) through our MCP server. Within the token holder's role, the assistant can read the team's contacts, members, cards and their statistics, and can act for the holder, for example assign a contact, send a follow-up, invite a member or edit a card or the brand. Whatever the assistant reads is passed to the AI service the team chose, under that service's terms. We store only a hash of each token, and record each use (the token's name, what it did, when, and for some actions a short description) so admins can see it.
• Own domain: a team can serve its cards on its own domain. We check the domain's DNS records and request a TLS certificate for it from a public certificate authority.

Legal basis: performance of our contract with you and with the team (Art. 6(1)(b) GDPR). Where we handle the details of a person who acts for a team, such as its billing contact, our legitimate interest in running our contract with the team (Art. 6(1)(f) GDPR).

The contacts a team’s cards collect belong to the team: the team is their controller, and we process them on its behalf. Our data processing agreement under Art. 28 GDPR is part of our terms and applies to every team. It lists the services we use for this.

Subscriptions in the app

You buy a plan through the App Store or Google Play. Apple or Google handles the payment, and we never see your payment details. The app uses RevenueCat to manage purchases, and our server asks RevenueCat which plan is active. We store the plan, the store it came from, the customer identifier and when the plan ends.

• RevenueCat knows you by a random identifier that our server gives your account. It is not your email address. Before you sign in, RevenueCat uses an anonymous identifier.
• On iPhone, if you allow usage data (see Analytics and crash reports in the apps), RevenueCat also collects Apple's attribution token, which tells us whether the download came from an Apple Search Ads campaign. We use it only to measure our own ads. Legal basis: your consent (Art. 6(1)(a) GDPR).
• If you answer the questions about your work when you first open the app (your industry, your networking goals, how often you network and what makes it hard), the answers are stored with your customer record at RevenueCat. We use them to understand who uses the app and to tailor the plans and offers we show you. The questions are optional. Legal basis: our legitimate interest in understanding our users and tailoring our offers (Art. 6(1)(f) GDPR). The answers are few and not sensitive. You can object at any time by emailing info (at) nfc (dot) cool, and we then remove them.

Legal basis for the purchase: Art. 6(1)(b) GDPR.

Analytics and crash reports in the apps

The iPhone and Android apps use the tools below. The App Clip, the card pages and the console use none of them.

Usage data, only if you allow it. The app asks you once whether you want to share usage data, with two buttons: Allow and Don’t Allow. Until you answer, and if you choose Don’t Allow, Firebase Analytics and PostHog stay off. You can change your choice at any time in More, under Share Usage Data. Turning it off stops them from then on, and on Android also clears the analytics data kept on your phone.

• Firebase Analytics (Google), iPhone and Android: records which screens you open and some actions in the app, such as opening the paywall, signing up, signing in, signing out and deleting your account, with an identifier for the app on your phone and device details. On Android it also records the steps of the first-run questions and your answers to them. Its advertising features are off.
• PostHog, iPhone, on servers in the EU: records app opens, screens viewed and recordings of how you use the app. Recordings hide the text, text fields and images on the screen, and your card, so they do not show the details on your cards or contacts.

Purpose: to understand how the app is used and improve it. Legal basis: your consent (Art. 6(1)(a) GDPR), which is also the consent Portuguese law requires before an app stores or reads information on your phone for this purpose (Art. 5 of Lei 41/2004). You can withdraw it at any time, without affecting what happened before.

Crash reports, for everyone.

• Firebase Crashlytics (Google), iPhone and Android: when the app crashes, it sends a crash report with the device model, system version, app version, where in the app the crash happened, and an identifier for the app on your phone. Crash reports do not include your account or the details on your cards.

Crash reports are sent whatever you choose above, because we need them to keep the app working. They are strictly necessary for the app you asked for, so the law does not require consent for them. Legal basis: our legitimate interest in an app that works (Art. 6(1)(f) GDPR).

App settings.

• Firebase Remote Config (Google), iPhone: when the app starts, it fetches settings we can change without an update, using an identifier for the app on your phone. We use it only for settings the app needs to work, not for experiments or to target you.

Legal basis: our legitimate interest in adjusting the app without an update (Art. 6(1)(f) GDPR). Fetching these settings is needed to provide the app as you use it, so it does not depend on your choice about usage data.

The iPhone app never asks for permission to track you, so it cannot read your device’s advertising identifier. The Android app does not ask for the permission to use your advertising ID.

Push notifications

If you allow notifications, the app gives us a device token from Firebase Cloud Messaging, a Google service. We use it to tell you about new contacts and about Conference Mode. The notification, which includes a contact’s name, passes through Firebase and, on iPhone, Apple’s push service. A token is deleted when Firebase reports that it no longer works, and with your account.

Legal basis: Art. 6(1)(b) GDPR. You can turn notifications off in your phone’s settings.

Conference Mode

Conference Mode keeps your card’s QR code on your lock screen as a Live Activity. To keep it up to date we store its push tokens, which cards it shows, your time zone offset, and any event you name with its start and end time and tag. New contacts appear on it as they arrive. When you sign out, its push tokens are removed.

Legal basis: Art. 6(1)(b) GDPR.

Apple services

• Sign in with Apple: see Your account. If you stop using Sign in with Apple for the app in your Apple ID settings, Apple tells us and we delete your account, together with any team you own alone, as described in Delete your account.
• App Clip: lets someone open a card on an iPhone without installing the app. It records views, saves and link taps as described above, and can take a contact's details and selfie. It contains no analytics or crash reporting tool.
• App Clip cards at Apple: if you give a card its own App Clip card (on a paid plan), or a team sets one up, we send Apple, through the App Store Connect API, the card's web address, a title (usually your name), a subtitle that can include your first name or company, a header image (made from your photo unless you upload another), a category and, for a team, its place name, address and phone number. Apple uses this to show the App Clip card when someone opens the card's link. We remove it at Apple when the card no longer has one.
• Apple Wallet: when you add a card to Apple Wallet, our server builds the pass from the card (name, photo, job title, department, company, first email address and a QR code with the card's link), signs it with our certificate and sends it to your phone. We do not keep a copy, and the pass does not report back to us.

On your phone

The app asks for a permission only when you use the feature that needs it:

• Camera: to take your photo and selfies, including the selfie in a contact form.
• Photos: to pick a photo or logo, and to save a contact's photo to your library.
• Contacts: to let you pick one of your contacts to fill in your card. The app shows your address book on your phone so you can choose, and only the contact you pick is sent to us. On Android, the app can also save a contact you collected to your address book, with its photo, and update the contact your card was made from.
• Location: only when you tap Use my current location to put your business on your card's map. We store the place you choose on the card, not your location history.
• Microphone and speech recognition (iPhone): to dictate notes about people you met. The speech is turned into text on your iPhone.
• Calendars and reminders (iPhone): to add follow-ups about people you met to your calendar or reminders.
• NFC: to write your card's link to an NFC tag.
• Notifications: see Push notifications.

On iPhone, the notes, follow-ups and photos you keep about people you met in the Networking tab are not sent to us. They are stored on your iPhone and, if iCloud is on for the app, in your own iCloud account, where Apple keeps them for you.

How you heard about us

If you choose to tell us how you heard about NFC.cool, we store your answer with your account and use it only to understand how people find us. It is included in your data export and deleted with your account.

The question is optional and asked once, at the end of setting up a team at business.nfc.cool. You pick one answer from a list and can add a few words of your own, up to 200 characters. Your answer is never sent to webhooks, CRM systems or AI assistants.

Legal basis: our legitimate interest in knowing how people find NFC.cool (Art. 6(1)(f) GDPR). We weighed it against your interests: the question is optional, it asks for very little, the answer is never shared with anyone, and you can object to it or have it deleted at any time by emailing info (at) nfc (dot) cool.

Emails we send you

We send emails about your account and your team: confirming your email address, password resets, sign-in and setup links, team invitations, ownership handovers, email address changes, a trial about to end, a subscription that ended, a data export that is ready, and warnings before we delete an inactive account or a team whose subscription ended. They are sent through Mailjet.

Newsletter: when you sign up in the app, you can tick a box to get the NFC.cool newsletter. Only then is your email address added to our newsletter list at Mailjet, through a small service we run on Cloudflare. On iPhone it is also added to your customer record at RevenueCat. You can unsubscribe at any time.

Legal basis: Art. 6(1)(b) GDPR for account and team emails. Your consent (Art. 6(1)(a) GDPR) for the newsletter.

When you contact us

If you write to us from the app, the email it prepares includes your subscription customer identifier, the app version, your system version and how often you opened the app, so we can help you. We use what you send us only to answer you.

Technical data, errors and security

• Server logs: our server logs each request (the address requested, with PINs and sign-in tokens removed, the time, the result, the IP address and browser, and if you are signed in, your account number) and every error. The logs stay on our server, are not shared, and are deleted after 14 days.
• Error reports from the server: we use Sentry to find and fix errors. Every error is reported, and half of all requests are measured for speed. Sentry does not receive IP addresses, cookies, the contents of forms, contact details, email addresses, PINs or tokens. A report holds the technical details of the error, such as the address requested and the part of our code that failed.
• Rate limits: see People who view a card.

Purpose: to run the service securely and fix problems. Legal basis: our legitimate interest in a secure, working service (Art. 6(1)(f) GDPR).

Who receives data

We share data only with the people and services below, and only for the reasons given in this policy.

• Anyone you share a card with sees what is on it. On a team, owners, admins and managers see the team's cards, contacts and statistics; members see their own.
• DigitalOcean: hosts our server, database and files, and delivers files through its content delivery network.
• Mailjet: sends our emails, teams' follow-up emails and the newsletter.
• Cloudflare: runs the small service that adds newsletter sign-ups from the app to Mailjet, and protects DigitalOcean's content delivery network against bots (see Cookies).
• Google (Firebase): push notifications, app analytics, crash reports and remote settings.
• PostHog: usage analytics and session recordings in the iPhone app, if you allow them.
• Apple: Sign in with Apple, App Store purchases, push delivery on iPhone, and App Clip cards.
• Google Play: purchases on Android.
• RevenueCat: manages in-app subscriptions.
• Qonversion: checks subscriptions bought in the NFC.cool Tools app, for accounts made there.
• Stripe: team billing.
• Sentry: error reports from our server.
• A public certificate authority: certificates for a team's own domain (the domain name only).
• Services a team connects: its webhook addresses, HubSpot, Salesforce, and the AI assistants it connects. They receive data because the team chose to send it there.

We do not sell personal data.

Where your data is stored, and data outside the EU

Our server, database and files are hosted by DigitalOcean in its data centres in the New York area, USA. Mailjet stores emails in the EU, in Germany and Belgium. PostHog stores the iPhone app’s analytics in the EU.

Where data leaves the European Economic Area, each transfer rests on one of these safeguards:

• The EU-U.S. Data Privacy Framework. The European Commission decided that US companies certified under it protect personal data adequately (Art. 45 GDPR).
• Standard contractual clauses. The European Commission's model clauses are part of our contract with the service (Art. 46(2)(c) GDPR).

For each service:

• DigitalOcean, LLC (USA): server, database, files and data exports. Data Privacy Framework, with standard contractual clauses in its data processing agreement in case the framework stops applying.
• Functional Software, Inc. (Sentry, USA): error reports. Data Privacy Framework, with standard contractual clauses as a fallback.
• Google LLC (Firebase, USA): Data Privacy Framework, with standard contractual clauses in Google's terms.
• Cloudflare, Inc. (USA): Data Privacy Framework.
• Stripe: our contract is with Stripe Payments Europe, Limited in Ireland. Its transfers to Stripe, Inc. in the USA rest on the Data Privacy Framework.
• Apple Inc. (USA): standard contractual clauses.
• RevenueCat, Inc. (USA): standard contractual clauses.
• Qonversion: standard contractual clauses.

Webhook addresses, HubSpot, Salesforce and AI assistants receive data only when a team connects them. The team chooses them and is responsible for that transfer.

To get a copy of the standard contractual clauses that apply, email info (at) nfc (dot) cool. The European Commission explains these safeguards on its information page.

How long we keep data

• Your account and personal cards: until you delete your account, or until we delete it because it has been inactive (see below).
• Views, saves and link taps: as long as the card exists.
• Contacts on your personal cards: until you delete them or your account.
• A team's cards and contacts: until the team deletes them, or the team is deleted. When a team is deleted, cards held by a member go back to that member, cards held by nobody are deleted, unassigned contacts are deleted, and the owner chooses whether contacts assigned to a member move to that member's own account or are deleted.
• A team whose subscription ended, or whose 7-day preview ended without a trial: 12 months. We email its owners 30 days and 3 days before, then delete the team as above.
• Invitations, and a team's record of what its access tokens did: until the team is deleted.
• Follow-up emails: a copy is kept with the contact, as long as the contact. An address that unsubscribed, bounced or reported spam stays on the team's block list for as long as the team exists, so the team keeps respecting it.
• A data export: 7 days after it is ready, then the file is deleted.
• Webhook, HubSpot and Salesforce delivery logs: 30 days, or 90 days for a delivery that failed.
• Conference Mode: until you delete your account.
• Your customer record at RevenueCat: until you delete your account, or until you ask us to remove it.
• Sign-in tokens: until they expire (refresh tokens after 180 days), then removed daily. Setup links expire after 7 days and password reset links after 60 minutes. Console sessions expire after two weeks and are then removed.
• Rate limit counters: at most a day.
• Server logs: 14 days.
• Error reports at Sentry: 90 days.
• App analytics and crash reports: Firebase Analytics 2 months, Crashlytics 90 days, PostHog recordings 30 days and other PostHog usage data 1 year.
• Backups: deleted data stays in our database backups for up to 7 days, until they are overwritten.
• Billing records of a team's subscription (invoices, payments and the details on them): 10 years, as Portuguese tax and accounting law requires, then deleted. This also applies after the team or the account is deleted. Legal basis: our legal obligation (Art. 6(1)(c) GDPR).

Inactive accounts. If nobody has signed in to an account for a year, none of the cards it holds, its own or a team’s, has been viewed in that year, and it has no active subscription, we email a warning that it will be deleted in 30 days. A final warning follows 3 days before. If the account is still inactive then, we delete it in the same way as when you delete it yourself. We never delete an account this way while its owner owns a team, or while it has a lifetime plan.

What you must give us, and automated decisions

To create an account you need an email address and a password, or Sign in with Apple. Without them we cannot give you an account. Everything you put on a card is up to you. To pay for a team, Stripe needs a payment card and a billing address. No law requires you to give us personal data.

We make no decisions about you based solely on automated processing that have legal or similarly significant effects on you (Art. 22 GDPR). Inactive accounts are deleted under the fixed rule in How long we keep data, after two warnings, and signing in stops it.

Your rights

Under the GDPR you have the right to:

• get a copy of your data and information about how we use it (Art. 15);
• have wrong data corrected (Art. 16);
• have your data deleted (Art. 17);
• have processing restricted (Art. 18);
• receive your data in a machine-readable format and take it elsewhere (Art. 20);
• withdraw consent at any time, without affecting what we did before (Art. 7(3)).

Your right to object. Where we rely on legitimate interests (card statistics and protection against abuse, server logs and error reports, crash reports and app settings, the questions about your work, and the sign-up question), you can object at any time, on grounds relating to your situation (Art. 21 GDPR). We then stop, unless we have compelling legitimate grounds that override your interests, or need the data to establish, exercise or defend legal claims. Email info (at) nfc (dot) cool.

Most of this you can do yourself, as described below. For anything else, email info (at) nfc (dot) cool. We answer within one month.

You also have the right to complain to a supervisory authority, in the EU country where you live or work or where you think your rights were infringed. In Portugal, where we are based, that is the Comissão Nacional de Proteção de Dados (cnpd.pt).

If you left your details on someone’s card, that card’s owner or team is responsible for them, and you exercise these rights with them. If you cannot reach them, or they do not answer, email us with the card’s link: we pass your request on and help them answer it.

Download your data

Sign in to the web console at business.nfc.cool with your app account and open Export my data under your account. The app’s settings also give you a way to export your data. We build a ZIP file in the background and email you when it is ready. You can download it for 7 days, then we delete it. If other accounts use the same confirmed email address, they are included too. If you cannot sign in there, email us and we will send you your data.

The file contains your account, your plan, your answer to the sign-up question, your teams and what you did in them, each card with its images and its vCard, and daily counts of views, saves and link taps. For your personal cards it also contains your contacts with their photos, notes, follow-ups and tags. It does not contain a team’s contacts, which belong to the team: owners, admins and managers can export those as a CSV file from the team’s Leads page. It also leaves out passwords, PINs and tokens, and payment records, which the App Store, Google Play and Stripe keep.

Delete your account

You can delete your account:

• in the app: on iPhone in the Business Card tab, under Settings, Danger Zone; on Android under Settings, Danger Zone;
• in the web console at business.nfc.cool, under your account;
• by emailing info (at) nfc (dot) cool.

When you delete your account, we delete your account, your personal cards with their images and statistics, the contacts on your personal cards with their photos, your subscription record, your data exports, your sign-in sessions and tokens, your Conference Mode data, and your answer to the sign-up question.

If you are on a team, the team keeps the cards you held for it and the contacts they collected, with your personal details removed from the cards as described under Teams. Notes and follow-up emails you wrote on a team’s contacts stay with the team, without your name. A contact that was already sent to a team’s webhooks or CRM stays there, under the team’s responsibility.

If you are the only owner of a team, you first hand the team to someone else, or delete it along with your account. If you were the team’s billing contact at Stripe, we replace your email address there with another owner’s. Stripe keeps the billing records of a team, as described in How long we keep data.

Deleting your account does not cancel a subscription bought through the App Store or Google Play. Cancel it in your store account settings.

When you delete your account, we also ask RevenueCat to delete your customer record, if it is under the identifier our server gave your account or, for an older Android account, under your confirmed email address. A record we cannot tie to your account, such as an anonymous one, stays at RevenueCat. To have it deleted, email us. Data that Firebase and PostHog hold about your app use is not linked to your account on our side and is deleted on their schedules, described in How long we keep data.

Children

You must be at least 16 to use NFC.cool Business Card. It is made for professional networking and is not directed at children. If you think someone younger than 16 has given us personal data, email info (at) nfc (dot) cool and we will delete it.

Cookies

The card pages and the console use no advertising or analytics cookies, and load no third-party scripts. Fonts are served by us, through our hosting provider’s content delivery network.

These are the only cookies set on them:

• csrftoken: protects forms, such as the contact form on a card or the console's forms, against forgery. It is set when you open a card or the console, and lasts about a year.
• sessionid in the console: keeps you signed in. It remembers which team you last opened and where you are in team setup, and briefly holds what the console shows you only once, such as a new access token. It lasts two weeks from your last visit, and ends when you sign out. A team's pages renew it, because the console writes to it there. Before you sign in, it is set only if a Sign in with Apple attempt fails, to show you the error.
• sessionid on a card page: set only if you enter a wrong PIN, or open a preview of your own card from the app. After a wrong PIN it counts your wrong PINs, and lasts five minutes from the last one. After three wrong PINs you wait those five minutes, and the cookie ends with the wait. A preview opens your card without its PIN for 30 minutes, and its cookie ends with it. If both happen, the cookie ends when the later one does.
• org_apple_nonce: when you sign in to the console with Apple, ties the sign-in to your browser. It lasts 10 minutes.
• __cf_bm: set by Cloudflare for DigitalOcean's content delivery network, which delivers the files and images of the console and the card pages. It tells people from bots, and lasts 30 minutes.

Counting a tap on a card’s link sends no cookie. Signing in with Apple happens on Apple’s own page, which sets Apple’s cookies under Apple’s policy. Paying for a team happens on Stripe’s own page, which sets Stripe’s cookies under Stripe’s policy.

The console also keeps two things in your browser’s storage. Your light or dark theme is stored only when you pick one, and stays until you clear it. During team setup, the last setup step shown is kept until you close the tab, so the progress bar moves the right way. Neither is sent to us.

Legal basis: these cookies are needed for the console and the card pages to work, which is why we do not ask for your consent.

Security

All connections to our servers are encrypted with HTTPS, and browsers are told to use HTTPS only. Passwords are stored as salted hashes. PINs are stored encrypted. Access tokens for the team API are stored only as hashes, and tokens from HubSpot and Salesforce are stored encrypted. Selfies left with a contact and data exports are kept privately: they can be opened only through short-lived signed links, by the people allowed to see them. Admin access to our server requires two-factor authentication.

Photos, logos and header images on a card are public, like the card itself, and are delivered through DigitalOcean’s content delivery network.

No system is completely secure, but we work to protect your data and fix problems quickly.

Changes to this policy

When we change this policy, we update the “Last modified” date at the top of this page. We do not start to use your data for a new purpose, or share it with a new kind of recipient, before this page describes it.

Contact

Questions about this policy or your data: