The NFC card you can trust, and check.

SAFE: the five layers

SAFE is TapInfo’s security framework. It covers everything between a card in someone’s hand and the data behind it, in five layers. Each layer lists its controls, the value we hold ourselves to, and the source of that value.

Threats we design for

The most common NFC card stores a direct web link on an unlocked chip. Here is what happens with that design, and with TapInfo, when things go wrong.

Ten questions to ask any NFC card provider

Use these to compare providers, including us. Each one links to our answer on this page.

Check a card

Every TapInfo card opens on tapinfo.io and shows its ID. Enter it here to see whether the card is genuine and active. If a card opens anywhere else, it isn’t a TapInfo card.

Credential lifecycle

Every card and tag is in exactly one state. States are shown with a symbol and a word, never colour alone. Every change is logged.

Organisation controls

When a company issues cards, it controls those cards. It doesn’t get access to its people’s private lives.

Security practice

How we build and run TapInfo, beyond the product controls above.

• Every code change is reviewed by a second person before release. Proposed
• Dependencies are scanned automatically and patched on a schedule; critical issues are patched within 7 days. Proposed
• Production access is limited to named people, uses hardware keys, and every access is logged. Proposed
• Secrets are kept in a managed vault and rotated; none live in code. Proposed
• Backups are encrypted, tested by restoring them, and kept for 35 days. Proposed
• This website sends strict security headers (HSTS, Content Security Policy, no third-party trackers) and publishes a security.txt file. Commitment
• Independent penetration test before general availability, with a summary published here. To confirm

We don’t claim certifications we don’t hold. When TapInfo is certified (for example Cyber Essentials or ISO 27001), the certificate will be linked here.

Privacy and your data

What we hold, why, for how long, and who can see it. The full legal text is in our privacy policy.

Your rights, in practice

• Export: download everything as JSON, CSV and vCard from your account, any time. Proposed
• Delete: close your account and live data is erased within 30 days, backups within 35. Proposed
• Ask: email privacy@tapinfo.io for a copy of your data. We reply within one month. UK law
• Complain: you can contact the Information Commissioner’s Office at ico.org.uk.

Data controller: Company legal name, ICO registration ICO registration number. Data is hosted in the UK or EU.

Subprocessors

Companies that process data for us. We give 30 days’ notice before adding one. Commitment

Status and availability

The resolver is the one part of TapInfo that has to be up for a tap to work. We target 99.9% monthly availability and publish incidents with a timeline and cause. Proposed

Live status: status.tapinfo.io To confirm

If the resolver were ever unreachable, a tap shows the browser’s connection error. It never falls back to another site.

Report a vulnerability

If you find a security problem in TapInfo, its cards, or this website, tell us. We won’t take legal action against good-faith research that follows this policy.

• Where: security@tapinfo.io Copy
• We reply within 2 working days, confirm or rule out the issue within 5, and agree a fix date with you. Commitment
• In scope: tapinfo.io and its subdomains, the TapInfo apps, the resolver, and TapInfo cards and tags.
• Please don’t: access other people’s data, run denial-of-service tests, or use social engineering.
• Credit: with your permission, we thank you by name here once the fix is out.

Machine-readable contact details are published at tapinfo.io/.well-known/security.txt.

What’s live

Every capability has one of five states: Available, Controlled rollout, In development, Direction, Not supported. Nothing is marked Available until it’s in customers’ hands.