Privacy Policy

Last updated: 27 September 2026

This page describes what SudoBizCard actually collects, which is less than most services of this kind. Where we've chosen not to collect something, it says so and says why.

The short version

• We do not store the IP address of anyone who looks at a card.
• We do not run advertising or third-party tracking scripts, and we do not sell or share personal data with data brokers.
• What a card's owner sees about their visitors is deliberately coarse: counts, country, and phone/tablet/laptop.
• The details you put on a card are public because that is what a business card is — except the fields you mark private, which are withheld.

1. Your account

To have an account we keep your name, your email address, and a one-way hash of your password — never the password itself. If you sign in with Google, we keep the identifier Google gives us and the email on that account, so the next sign-in finds you; we do not receive your Google password.

We record when your email was verified and when sessions were invalidated, because that is what makes “sign out everywhere” work.

2. What you put on a card

Everything you add to a card — name, title, company, photo, links, bio, contact details, theme — is stored so it can be shown. A published card is public: anyone with the address can open it, and search engines may index it. Keep a card in draft and only you can reach it.

Private fields. Marking a field private removes it from the published page and from the downloadable contact file. It is withheld, not merely hidden by styling, and it applies to every theme.

3. Visitors to a card

When someone opens a card we record one row: the date, whether they arrived by tapping a physical card or by a link, a two-letter country code, and one of mobile, tablet or desktop. On this website we also record the browser family, the operating system family, the preferred language from the browser, and the domain they came from if they followed a link.

We do not store their IP address. The country comes from a header our network provider has already set, so the address never has to be looked up, let alone kept. Uniqueness — “roughly how many people” rather than “how many page loads” — is decided by a session cookie, so it doesn't need one either. Nothing recorded about a visit identifies the visitor, and nothing links two visits to different cards to the same person.

Automated visitors — crawlers, and the link previews chat apps generate — are not counted, which is why the numbers are a floor rather than an exact figure.

4. When a visitor contacts you

If a visitor fills in a lead form, an enquiry form, or books a time, they are handing their details to the card's owner on purpose: name, and whatever of email, phone, company, role and message the form asked for. Alongside it we keep the country and device class, and the domain they arrived from. We do not keep their IP address or their full browser string.

That information belongs to the card's owner. SudoBizCard does not use it to market to those people.

5. Payments

If you buy a paid plan, the payment is handled by Stripe. Card numbers go from your browser to Stripe and never reach our servers — we could not store them if we wanted to. We keep the subscription status, the plan, and Stripe's identifiers for the customer and subscription, which is what a receipt and a renewal need.

6. Other services, and exactly when they are involved

• Our hosting provider runs the servers and the network in front of them. Web server logs, which do contain IP addresses, are kept by that infrastructure for a short period for security and abuse handling; they are not part of the analytics above and are not used to build profiles.
• Cloudflare Turnstile, if bot protection is switched on, receives the visitor's IP address in order to tell a person from a script. This is the one place a visitor's address is deliberately sent anywhere.
• Email delivery. Notifications and password resets pass through the mail provider configured for this installation, which necessarily sees the recipient address and the message.
• An AI assistant is optional and off unless an administrator configures one. When it is on and you use it, the text you ask it to work on is sent to that provider's endpoint. Don't paste anything into it you wouldn't send to a third party.

Anything not listed here is not receiving your data.

7. Cookies

A session cookie, which is what keeps you signed in and what lets visit counting tell one person from two. A remember-me cookie if you ask to stay signed in. A CSRF token cookie, which is a security measure. That is the whole list: no advertising cookies, no analytics cookies belonging to anyone else.

8. IP addresses in the moment

Rate limits — on sign-in attempts, on form submissions, on password resets — are counted against an IP address so one source cannot flood the site. Those counters live in memory, expire within minutes, and are not written to the database or joined to any record about you.

9. The PulseCard app

PulseCard keeps a copy of your own cards on your device so they open without a network. Its card analytics follow the same rule as above: a daily, per-card, non-reversible token instead of an address, plus country and device class, and views are deleted automatically after 90 days.

The app's location features are opt-in and deliberately short-lived. When you make yourself visible at an event, your position is held in a cache with a 60-second expiry — it is never written to the database, so there is no history of where you have been. Positions shown to other people are offset by up to about 100 metres before they leave the server, so “nearby” can work without anyone being pinpointed. Setting your visibility to ghost stops it entirely.

10. How long we keep things

• Your account and cards: until you delete them.
• Visits to a card: 90 days in PulseCard. On this website they are kept while the card exists, and deleting a card deletes them.
• Leads, enquiries and bookings: until you or the card's owner deletes them, or the card is deleted.
• Billing records: as long as tax and accounting rules require, which is longer than the account itself.

11. Your choices

You can edit or delete any card at any time, and mark any field private. Deleting a card deletes its visits, leads and enquiries with it. You can export your own contact data from your account.

To get a copy of what we hold about you, to correct it, or to have your account and its data deleted, email sudo@sudobizcard.com from the address on the account. We'll act within 30 days and tell you when it's done. Deletion is deletion, not deactivation — anything we must keep for tax reasons is named in the reply.

12. Children

SudoBizCard is for working adults and is not directed at children under 16. We don't knowingly collect their data; if you believe we have, tell us and it will be removed.

13. Security

Traffic is encrypted in transit. Passwords are hashed. Secrets and tokens are encrypted at rest. Database backups are taken nightly and verified. No system is perfect: if something goes wrong in a way that affects you, we will say so rather than hope you don't notice.

14. Changes

If this policy changes in a way that matters — a new recipient of your data, a new category collected — we will say so on this page and date it, rather than quietly editing it.