Privacy Policy
What we collect, why we collect it, and what we deliberately do not collect.
Who is responsible
22TAP is operated by Orlando Gonzalez, an individual sole proprietor based in California, United States. There is no company or LLC behind it.
You can reach us at hello@22tap.com, including about anything in this policy. That address is read by a person, and we answer from it.
Your account
Your name, your email address and your password — because an account cannot exist without them.
Your password is never stored as you typed it. Only a cryptographic hash is kept, and we cannot read it or recover it. If you lose it, we can only help you set a new one.
Your profile
Whatever you choose to put in it: name, business name, job title, a short bio, phone number, SMS number, WhatsApp number, email address, postal address, and your links.
Every one of these fields is optional. You decide which to fill in, and you decide whether the profile is published or kept private.
Your cards
The permanent code printed on each 22TAP you own, which product it is, and which profile it opens. If your order had a reference, we keep that too so we can find it again.
IP addresses: where they are stored, and why
Your IP address can be stored in two different places, for two different purposes, with two different lifetimes. We would rather lay this out plainly than make a blanket claim we would have to walk back.
1. Your sign-in sessions. When you sign in, the session record includes your IP address and your browser’s user-agent string. The authentication system we use stores them as part of the session so that a session can be recognised and revoked. They stay for as long as that session record does.
2. Abuse prevention. To stop someone hammering the sign-in form, or using it to send verification emails to other people, we count recent requests per IP address. Those counters hold IP addresses.
A counter stops being useful about a minute after the request that created it, and an automatic sweep deletes expired counters whenever there is traffic on the authentication pages. We do not promise a deadline by which every IP address is gone: if nobody uses those pages for a while, the last counters sit there until somebody does. What we can say is that expired counters are deleted automatically, that the sweep never touches a counter that is still active, and that none of this is used for analytics.
Requests to resend a verification email are counted separately, using a one-way fingerprint derived from the IP address — never the address itself, and never the email address it was sent to.
Both of these concern you as an account holder. Neither applies to someone who taps your card.
What we deliberately do not collect
This section is about the people who tap or scan your card. They are not our customers, they never agreed to anything, and they get the strongest treatment.
When somebody opens your profile we record three things: that a view happened, a coarse country, and whether the device was a phone, a tablet or a desktop.
That is all. We do not store their IP address — not even hashed — nor their browser user-agent, nor any cookie, identifier or fingerprint that could follow them, nor anything that could link one visit to another.
A public profile page sets no cookies at all. There is no advertising network, no tracking pixel and no third-party analytics anywhere on 22TAP. Our fonts are served from our own servers, so opening a profile does not call out to anyone else.
We cannot tell you who viewed your profile, because we do not know.
Our internal change log
Every administrative change — publishing a profile, linking a card, deleting an account — is written to an append-only log. The database physically prevents that log from being edited or deleted, which is what makes it worth anything as a record.
It is not free of personal data, and we will not claim otherwise. It holds three different kinds of thing.
Field names and minimised values. When you change your job title, the log records that the job title changed, who changed it and when. It does not record the old or new title.
Identifiers. Entries carry internal identifiers: the profile they concern, the permanent code of a card, and a label of the form user:<your account id>. On their own these are not your name or your email, but while your account exists they point at you. Once your account and profile are deleted, they point at records that no longer exist.
Older entries. Entries written before we introduced the minimisation above may contain actual values, such as text you had in your profile. They cannot be removed, for the same reason the log is trustworthy: the database refuses to modify or delete them. We are telling you this instead of claiming the log can be wiped clean, because it cannot.
Cookies
One cookie, and only after you sign in. It keeps your session open so you are not asked to log in on every page. It is not used for analytics or advertising. Signing out removes it.
22TAP staff use a separate cookie for the internal admin area. It is never set on a customer account or a public profile.
What your published profile shows
A published profile is public. Anyone holding your card, and anyone who knows its web address, can see what you put in it. Search engines can find it.
Your account email address is never shown there unless you add it to the profile yourself.
You can unpublish at any time from your account. The change applies to our systems as soon as you save it, so the next person who opens your card sees the new version rather than the old one. A page somebody already has open in their browser will not change until they reload it, and we cannot reach anything that was copied, screenshotted or saved on their device.
We email you for two reasons only: to verify your address when you register, including re-sending that verification if you ask, and to let you reset your password.
We do not send marketing email, and there is no mailing list to be on.
Who else processes your data
We keep this list short on purpose. Vercel hosts the website and serves it. Neon runs the database where your account, profile and cards are stored. Hostinger carries our outgoing email.
Each of them stores data on infrastructure they operate, under their own terms. Nobody else receives your personal data. We do not sell your personal information, and we do not share it for cross-context behavioural advertising.
How long we keep it
We publish no fixed retention periods, because the honest answer is a description rather than a schedule.
Your account and profile are kept for as long as you have an account. They are deleted when you ask us to delete them.
Sign-in sessions, with the IP address and user-agent described above, expire after 30 days. A session is deleted when you sign out, and an expired one is deleted the next time it is used. There is no scheduled purge, so an expired session you never return to may sit in the database until the account itself is deleted.
Abuse-prevention counters are deleted by the automatic sweep described above, with no guaranteed deadline.
Profile view counts are deleted together with the profile.
The change log is permanent and cannot be deleted, with the three kinds of content described above.
Your rights
You can ask us to tell you what personal data we hold about you and give you a copy, to correct anything that is wrong — most of it you can correct yourself from your account — or to delete your account and your personal data. Write to hello@22tap.com.
California law gives residents rights over their personal information, and the rights that apply to you may depend on where you live. Rather than recite a list, we will say what we do: we honour any request we are able to honour, and if we cannot, we tell you why.
Deletion is done by hand, and we verify who is asking
There is no self-service delete button in your account. Deletion is carried out manually, after verifying the request, because it cannot be undone and because a deletion requested by the wrong person would be as damaging as a breach.
We act on a deletion request only when one of the following is true:
the request arrives from the email address registered on the account; or you demonstrate access to the account itself; or we identify you in person.
If none of those is possible, we will not delete the account. We will never ask you to put a temporary code into your public profile to prove who you are.
What deletion removes, and what it does not
Removed from our live database: your account, profile, links and profile view counts; your sign-in sessions and stored credentials, which signs you out everywhere; and the email address, order reference and claim details attached to your cards.
Your physical cards survive. Each card keeps its permanent printed code — it is stamped on an object you own and it is never reused — but it is unlinked from your profile and switched off. A card that was reported lost stays reported lost.
A record of the deletion is added to the change log, noting when it happened, under which request reference, and how we verified your identity. It contains no name, email address or phone number, but it does contain your former account identifier and the codes of the cards that were unlinked.
Older change-log entries cannot be removed, as described above.
Automated database backups kept by our hosting provider may still contain a copy for a period after deletion. We cannot edit the contents of a backup; copies age out on the provider’s own schedule.
Children
22TAP is meant for adults using a professional or business profile. It is not directed to children, and we do not knowingly collect personal information from anyone under 13. If you believe a child has created an account, write to us and we will remove it.
Changes
If we change this policy we will publish the new version here and update the date below. Last updated: October 28, 2026.