Privacy Policy
Last updated: November 5, 2026
1. Data controller
The data controller is VisitCard, operated by Fiducium Sàrl, c/o Gaël Ghislain Monney, Rue des Beaux-Arts 14, 2000 Neuchâtel, Switzerland (Company ID: CHE-488.904.546). Contact: hello@visitcard.app. This company is subject to the Swiss Federal Act on Data Protection (nFADP) and, for users located in the European Union, endeavours to comply with GDPR principles. Under these frameworks, the formal designation of a data protection officer is not mandatory for our organisation size. All data protection enquiries: hello@visitcard.app.
2. Data collected & legal bases
- Account data (email, name, hashed password) — legal basis: performance of contract (art. 6.1.b GDPR); date of the last sign-in and of the last activity in the dashboard (two dates only, with no history and no IP address), for support and service follow-up — legal basis: legitimate interest (art. 6.1.f GDPR)
- Business card profile (photo, title, phone, social media) — legal basis: performance of contract + consent
- Payment data (subscription, plan, invoice history) — legal basis: contract + legal obligation (art. 6.1.b and 6.1.c)
- Aggregated analytics (views, visitor country, device type) — legal basis: legitimate interest (art. 6.1.f), pseudonymised data
- Technical logs (IP for rate-limiting, timestamps) — legal basis: legitimate interest (security)
- Business card scanner — The photo of a business card is sent to Anthropic PBC (United States), our image-analysis sub-processor, solely to read the contact details, in two cases: when an account holder uses the “Scan a card” feature (from their dashboard, their card or their personal scan link), and when a visitor of a card chooses “Fill in with a photo of my card” to pre-fill the contact form. This button is optional: visitors can always enter their details by hand. The photo is not stored by VisitCard and Anthropic does not use it to train its models. Only the reviewed contact details are saved: by the account holder in their address book; for a visitor, only if they then send the form. Transfers to the United States are governed by standard contractual clauses.
- Visibility of your card — your card is available to anyone who has its link or QR code. By default, it is not offered to search engines (
noindextag) and is not listed in our sitemap; it only is if you tick “Make my card visible on Google” in the editor, and you can untick this box at any time — legal basis: consent (Art. 6.1.a GDPR) - Leads and newsletter — When you request a demo, a QR code by email or a newsletter subscription, we record your email address, language and where the request came from (for a demo, also the company and team size). In reply to a demo request, we may send you a personal link to a demo page, valid for 14 days; to limit its forwarding, we count how often it is opened (date of the first and last opening, number of openings and a device fingerprint derived from the browser and part of the IP address, never the address itself); this data is deleted together with the demo request. If you tick the box provided or subscribe to the newsletter, we email you a confirmation link: your consent is only recorded when you click it (double opt-in). We then keep proof of that consent (date, accepted wording, a hash of your IP address, never the address itself) and send you our news and tips by email — legal basis: consent (art. 6.1.a GDPR, art. 3(1)(o) Swiss UCA). These emails are sent through Resend, Inc. (sub-processor) and contain no open-tracking pixel and no click-tracking links. You can withdraw your consent at any time with the unsubscribe link in every email; your data is kept until you unsubscribe or ask for its deletion at hello@visitcard.app. Without confirmed consent, your address is only used to handle your request; it is removed from the leads list 30 days after your last request.
- Ambassador programme — If you are an ambassador: your code, your split, your commissions and payouts, the (non-reversible) fingerprint of the IP addresses used on your space and your payout details (name, address, status, UID or VAT number where applicable, IBAN), encrypted (AES-256) and used only to pay you. The invoices (PDF) attached to your transfer requests are kept in a private storage area, accessible only to you and to the administration, for payment and accounting. If you came through an ambassador link: that link’s code (
vc_refcookie, 60 days), the fingerprint of your IP address and that of your payment card (provided by Stripe), used only to prevent self-referral. The ambassador only sees your first name and the initial of your last name. Legal basis: performance of the contract and legitimate interest (abuse prevention). - NFC card orders — If you order a physical NFC card: the order, the delivery address and phone number entered at payment (Stripe), and the data printed on the card (name, job title, company, logo, link to your card). They are used only to produce and send the card: the printed data and the delivery address are passed, for production, to a print shop based in France (European Union). Legal basis: performance of the contract.
3. Storage and security
Your data is hosted on Cloudflare infrastructure (ISO 27001 certified datacenters). The database (Cloudflare D1) and uploaded images (Cloudflare R2) are stored in the European Union (Cloudflare’s EU jurisdiction); the application is served by Cloudflare’s global network, each request being handled by the nearest datacenter. The database uses D1 SQLite with encryption at rest. Passwords are hashed using PBKDF2-SHA256 with 100,000 iterations and a unique salt per user. All communications are encrypted with TLS 1.3. CSRF tokens protect all forms. IP-based rate limiting is applied on all sensitive routes, using temporary counters kept in the Cloudflare D1 database.
4. Sub-processors (art. 28 GDPR)
| Sub-processor | Role | Location | Policy |
|---|---|---|---|
| Cloudflare, Inc. | Application hosting and delivery (global network, CDN), D1 database and R2 image storage (EU jurisdiction) | EU (database and images); US company (DPF) | cloudflare.com/privacypolicy |
| Stripe, Inc. | Payment processing, billing, VAT | USA (DPF) | stripe.com/privacy |
| Resend, Inc. | Delivery of transactional emails, the newsletter (double opt-in) and onboarding emails triggered by account events (EU sending region: Ireland) | Ireland (EU); US company (SCC) | resend.com/legal/privacy-policy |
| Infomaniak Network SA (Geneva, Switzerland) | Email hosting (hello@visitcard.app address, replies to emails) | Switzerland | www.infomaniak.com/en/legal/confidentiality-policy |
| Print shop (France, EU) | Production and shipping of personalised NFC cards (printed data, delivery address) | France (EU) | — |
| Google LLC (GTM/GA4/Google Ads) | Analytics and advertising conversion measurement (with consent only) | USA (DPF) | policies.google.com/privacy |
| Google LLC (Google Fonts) | Font files, fetched by our servers and served from visitcard.app (Google receives neither the IP address nor any visitor data) | USA (DPF) | policies.google.com/privacy |
| Google LLC (Sign in with Google, Google Wallet, Gmail API) | Sign-in with Google; adding the card to Google Wallet; Gmail API (gmail.settings.basic scope), used only at your request to install your email signature in Gmail | USA (DPF) | policies.google.com/privacy |
| Microsoft Corporation | Sign-in with Microsoft; Outlook add-in (office.js library loaded from Microsoft’s servers) | USA (DPF) | privacy.microsoft.com |
| Anthropic PBC | Image analysis for the business card scanner (contact detail extraction): photos taken by account holders, and by visitors of a card who choose to pre-fill the contact form | USA (SCC) | anthropic.com/legal/privacy |
VisitCard’s use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
5. Cookies
VisitCard uses, in particular, the following strictly necessary cookies: visitcard_session (authentication, HttpOnly, SameSite=Lax), csrf_token (CSRF protection, SameSite=Lax, Max-Age 24h) and vc_signup (automatic sign-in after email verification, 3 hours). Other short-lived functional cookies (two-factor authentication, sign-in with Google or Microsoft, dashboard) are listed in the Cookie Policy. Visitors located in Switzerland (country of the IP address): Google Tag Manager and the Google tag load on every page as soon as you arrive, with Google Consent Mode v2 in advanced mode, set to “denied” by default (analytics_storage, ad_storage, ad_user_data and ad_personalization set to denied). Until you accept, no Google cookie is set or read; the tag nevertheless sends Google cookieless signals (“pings”): consent status, page viewed, timestamp, browser type and IP address (used for transmission and approximate location). Google uses them to estimate, in aggregated and modelled form, visits and conversions that are not measured. Once you consent, Google Analytics 4 and Google Ads set their cookies and measure, each according to the accepted category (Analytics / Marketing). Visitors located outside Switzerland: Google Tag Manager and the Google tag are loaded only after you consent (Analytics or Marketing); before that, nothing is sent to Google, not even cookieless signals. Your choice is stored in the vc_consent cookie (365 days). The vc_src cookie (30 days, internal measurement) remembers where your first visit came from (referring site, campaign, referral link or ad click, without any advertising identifier) for VisitCard’s internal statistics; it is linked to your account if you sign up and is never shared with third parties. Visitors in Switzerland (country of the IP address): it is set on the first visit and deleted if you decline analytics cookies; other visitors: it is only set if you accept analytics cookies. If you arrive through a Google Ads ad, the identifier of that click is kept in the vc_gclid cookie (90 days) with your consent to marketing cookies (in Switzerland, unless you have refused them in the banner), then with your account if you sign up, to measure our ads’ conversions (sign-up, trial, purchase): VisitCard then sends it to Google Ads with those conversions. Google Ads enhanced conversions: only if you accept marketing cookies, when you sign up, start a trial or make a purchase, your account’s email address is sent to Google in hashed form (a SHA-256 fingerprint computed in your browser, never in plain text nor in a web address), to credit that conversion to our ads. Public cards (visitcard.app/c/…) set no cookies and load no third-party audience-measurement or advertising tools; their fonts are served from visitcard.app: Google Fonts does not receive the visitor’s IP address. Details: Cookie Policy.
6. Your rights (GDPR)
Under GDPR articles 15–22, you have the right to access (art. 15), rectification (art. 16), erasure (art. 17), restriction (art. 18), portability (art. 20), and objection (art. 21). To exercise these rights: hello@visitcard.app. We respond within 30 days. You also have the right to lodge a complaint with your national supervisory authority.
7. Retention periods
| Data category | Retention period |
|---|---|
| Active user account | Duration of subscription + 30 days after account deletion |
| Contacts received via card form | 3 years from last contact (legitimate interest), erasable on request at hello@visitcard.app |
| Billing data & invoices | 10 years (statutory accounting obligation) |
| Rate-limiting logs (IP) | 2 × the limiting window (from 15 minutes to 7 days depending on the feature), then deleted — Cloudflare D1 database |
| Aggregated analytics (card views) | Duration of account, deleted with account |
| Contacts on hold (plan limit reached) | 90 days maximum, then deleted unless the card holder upgrades |
| Google Analytics data (GA4) | Collected only after consent; retained 14 months at Google |
| Transactional emails (Resend) | 30 days in Resend logs, then deleted |
| Database backups | 30 days, managed by Cloudflare D1 |
| Leads (demo, QR tool, newsletter) | Until you unsubscribe or ask for deletion; without confirmed consent: 30 days after the last request |
| Ambassador programme (commissions, payout details) | Until the account is deleted; completed payouts and their details: 10 years (accounting obligation, art. 958f CO) |
| NFC card orders (delivery address, printed data) | 10 years (accounting obligation, art. 958f CO) |
8. International transfers
Cloudflare, Stripe, Resend, Google, Microsoft, Anthropic are US companies. The database and uploaded images are stored in the European Union (Cloudflare’s EU jurisdiction), and transactional emails are sent from Resend’s EU region (Ireland). The application is nevertheless served by Cloudflare’s global network, and these providers remain subject to US law. Transfers to recipients certified under the EU-U.S. Data Privacy Framework and its Swiss extension (Swiss-U.S. Data Privacy Framework, recognised by the Federal Council since 15 September 2024), in particular Cloudflare, Stripe, Google, Microsoft and HubSpot, rely on these adequacy decisions (art. 45 GDPR; art. 16(1) FADP and Annex 1 to the Data Protection Ordinance, DPO). Otherwise, they are governed by the European Commission’s Standard Contractual Clauses (decision 2021/914), with the adaptations for Swiss law recognised by the Federal Data Protection and Information Commissioner (FDPIC; art. 16(2)(d) FADP). In the table in § 4, “DPF” refers to the Data Privacy Framework and “SCC” to the Standard Contractual Clauses.
9. Public contact form
When a visitor sends a message via the contact form on a VisitCard business card, the data entered (name, email, optional phone, optional company, message) is forwarded by email to the card’s owner and stored in VisitCard’s database (Cloudflare D1) to enable contact management. The legal basis is legitimate interest (GDPR art. 6.1.f). Data is retained for 3 years from the last interaction and can be erased on request at hello@visitcard.app. An optional marketing opt-in is offered; declining does not prevent message delivery. Rate limit: 3 messages/hour per IP. When a card holder has reached their plan’s contact limit, details submitted through the form are kept by VisitCard “on hold”, without being accessible to the card holder, for at most 90 days; they become accessible to the holder if they upgrade within that period and are deleted otherwise. You can request their deletion at hello@visitcard.app.
If the card holder has turned on the automatic thank-you email (paid plans), the visitor receives, once only and at the address they entered, a short email from the holder (“Thank you for our conversation”, with a link to their card and contact details): it is the follow-up to the visitor’s own request to be contacted, with no promotional content and no advertising tracking. Replies go directly to the holder. So that it is never sent twice, VisitCard keeps a non-reversible fingerprint of the address (hash), never the address itself, for as long as the card exists.
If the card holder has connected their CRM (HubSpot, Pipedrive or bexio), the data sent through the form is transmitted there on their instruction; they are then responsible for that processing. Visitors’ IP addresses are not stored when a card is viewed; for messages sent through the contact form, the IP address is stored in pseudonymised form (last block set to zero) and erased after 30 days.
10. Minors
VisitCard is reserved for persons aged at least 18 (Terms of Use, § 3bis). We do not knowingly collect data about persons under 18; if we learn that an account has been opened by such a person, it may be deleted.
11. Contact & complaints
For any data protection query: hello@visitcard.app. If you are not satisfied with our response, you can contact the Swiss Federal Data Protection and Information Commissioner (FDPIC): edoeb.admin.ch. If you reside in the European Union, you also retain the right to lodge a complaint with your national supervisory authority.