What we collect, why, what we are able to read, and what you can ask us to do about it. Written to be read rather than to be defensible.
Last updated 20 August 2026
ReachCard is a physical NFC card that opens a profile you control. Your profile, your saved contacts and your images are stored encrypted. The person who taps your card never needs an account, and we record nothing about them.
There is one thing we want to be direct about, because most services in this space are not. We hold a key that can decrypt your profile and your saved contacts. It exists for a single reason: so that signing in lets you reach your own card on a device that does not have the card in hand. We do not read your content, we do not sell it, and we do not use it to train anything — but we could, and we would rather tell you that than write a sentence that sounds stronger than it is.
A copy of our database on its own is useless. The key is derived from a secret held in our server environment, not stored in the database, so a stolen dump is ciphertext and timestamps.
‹Legal entity name› (“ReachCard”, “we”, “us”) is the data controller for the personal data described here. Our registered address is ‹Registered address›. ‹Company number, if registered›.
For anything in this policy, including any request about your data, contact privacy@reachcard.me.
We do not use advertising or analytics trackers, we do not build profiles of visitors, and we do not buy or sell personal data.
| Your email address | Stored only as an unreadable one-way fingerprint (an HMAC), not as an address. It is used to recognise you at sign-in and to match you to a company team. For members of a company, we also keep a deliberately partial version (for example “j••••@gmail.com”) so the people administering that team can tell one member from another. |
|---|---|
| Your sign-in identity | If you sign in with Google, we store the opaque account identifier that Google gives us, and a password hash if you chose email and password instead. We never store your password itself, and we never receive your Google password. |
| Your profile | Your name, role, company, bio, links, chosen layout and appearance, and your photo and cover image. All of it is encrypted before it leaves your browser and stored as ciphertext. |
| Your saved connections | The people you have connected with, including anything a visitor chose to send you and a snapshot of a fellow member's name and link. Encrypted the same way. |
| Card records | The identifier of each card, whether it is unclaimed, claimed or revoked, which batch it came from, and which company issued it. A company may add its own label to a card it issued, to track who is holding it. |
| Card views | When a card is opened, we record the card identifier, whether it was a view or a link click, and the time. Nothing about the visitor: no IP address, no device details, no fingerprint, and not even which link was clicked. |
| Account activity | Your level, experience points, badges earned, and the fact that a connection exists between two accounts. Connections are stored as a link between two opaque identifiers, because features like counting mutual connections cannot be computed over encrypted data. |
| Sessions | A session identifier in a cookie, and its expiry, so you stay signed in. |
We can decrypt your profile, your saved connections and your images, using a key derived per account from a secret in our server environment. This capability exists so that signing in reaches your own card without your card present. Access is limited to what is necessary to operate and support the service.
We cannot recover your recovery key. It is not stored anywhere on our systems and cannot be reissued by support. If you lose it and lose access to your cards, the data protected by it cannot be recovered by anyone, including us.
We do not know who taps your card. There is no visitor identity in our records to disclose, whether to you, to a company, or to anyone who asks.
A company that issues cards can see that its cards are active and how often they are opened. It cannot see what the cardholder put on their profile.
We set only what the service needs to function, and nothing for advertising or analytics.
Our servers are in ‹region›. If you are in the UK or the EEA and your data is processed outside it, that transfer relies on the appropriate safeguards, such as the UK International Data Transfer Agreement or the EU Standard Contractual Clauses.
If you are in the UK or the EEA you have the rights below, and we extend them to everyone regardless of where you are. To use any of them, email privacy@reachcard.me. We will respond within one month, and will tell you if we need longer.
ReachCard is not intended for children under 16, and we do not knowingly collect their data. If you believe a child has an account, contact us and we will remove it.
If we change this policy we will update the date at the top, and we will tell account holders directly about anything that materially affects them — particularly any change to what we are able to read.