How we count
Card owners see a few numbers about their card. Here’s exactly what each one means, what we leave out, and what we never track — for owners and for anyone who opens a card.
- We count real people opening a card and tapping its buttons.
- Link previews in chat apps and known bots are not counted.
- “Unique visitors” is an estimate. We say so, and we never store IP addresses.
- No cookies for analytics, no ad pixels, no tracking you across other sites.
01What we count
| Metric | Counted when | Doesn’t mean |
|---|---|---|
| Page views | A person’s browser loads the card. Repeat opens by the same visitor within 30 minutes count once. | The number of people. |
| Unique visitors ≈ | Distinct anonymous daily IDs that opened the card (see 03). | An exact headcount, especially across several days. |
| “Save contact” taps | The contact file (.vcf) is downloaded from the card. | That the contact was actually saved on a phone. We can’t see that, and don’t try to. |
| Contacts shared | The “Share my contact” form is accepted by our server. A double tap or retry counts once. | Marketing consent. That’s a separate, optional checkbox. |
| Call / Email / Link taps | Someone taps that button on the card. | That the call connected or the email was sent. |
| Source: QR · NFC · link | Read from the short link the card was opened with (?src=qr, nfc, link). | How many times a QR code was scanned without opening. |
02What we leave out
When you paste a link into a chat, the app fetches the page to draw a preview. That isn’t a person, so it isn’t a view. We exclude previews and crawlers from:
- iMessage
- Slack
- Telegram
- Facebook / Messenger
- X (Twitter)
- Discord
- Microsoft Teams
- Google, Bing & other search crawlers
- uptime monitors
We also skip prefetches that never render. The list is reviewed monthly; some unknown bots may still slip through, so treat small numbers with care.
03How “unique visitors” is estimated
We don’t use cookies or device fingerprints. Instead, for each visit we compute a one-way hash that changes every day:
The salt is random, rotates every 24 hours and is then deleted, so yesterday’s IDs can’t be matched with today’s. The IP address itself is never written to disk. That’s why we can count unique visitors within a day fairly well, but across a week we can only add the days up: someone who came back on Tuesday and Thursday counts twice. Hence the “≈”.
04“Save contact” taps, honestly
05What we never do
- No analytics cookies, local storage IDs or device fingerprinting on card pages.
- No third-party trackers, ad pixels or social “like” scripts. Card pages load only our own code and fonts.
- No tracking across other websites or apps, and no selling or sharing of visit data.
- No emails from us to people who share their contact. Only the card owner can reach out.
- No tracking pixels or tracked links in the emails we send owners.
06How long we keep it
Individual visit events are kept for 90 days, then rolled up into daily totals per card. Daily totals stay until the card or account is deleted. Card owners can export or delete their data from the app at any time; California residents can also exercise CCPA/CPRA rights via privacy@tesseraa.app.