Your data & privacy

Privacy Policy

Last updated: 15 November 2026 · Version 1.4

How we process personal data through Contacly — what we collect, why, on what legal basis, with whom we share it, and the rights you have.

1. Controller (and, where applicable, representative and DPO)

The controller responsible for processing personal data through Contacly is:

Rahm Digital Solutions (sole proprietorship), Passage du Cardinal 8, 1700 Fribourg, Switzerland
Email: privacy@contacly.com · Commercial Register of the Canton of Fribourg, UID: CHE-429.673.854

We have not appointed a representative in the EU (Art. 27 GDPR) or in the United Kingdom (Art. 27 UK GDPR). Please send all requests directly to us at the address above.

A data protection officer is not required for our processing (Art. 37 GDPR) and has not been appointed.

2. What Contacly is (purpose of the service)

Contacly is a platform for controlled exchange of contact data through profiles, links, QR codes, identity/phone verification, and traceable approvals. This policy explains what personal data we process, why, on what legal basis, with whom we share it, and the rights you have.

3. Whose data we process, and what data

We process personal data about two groups:

  • Account users — the people who register and operate Contacly profiles.
  • Contacts — third parties whose contact details are entered, requested, exchanged, or stored through the service by a user.

The categories we process are:

  • Identity & contact data: name, email address, phone number, company, role, profile information.
  • Encrypted profile content: the content of your profile (name, phone number and e-mail address as shown in the profile, company, notes, business card, groups, your list of sent requests, your own notes on contacts and the date a contact last changed its data) is encrypted in your browser with keys we do not hold. We store only the encrypted form and cannot read it. Readable to us are: the e-mail address of your account (stored encrypted; our server opens it only to deliver mail, and our administrators see it masked), plan and payment status, exchange balances, timestamps, session and device data, protected (hashed) identifiers of your phone number and e-mail address, and the number and time of requests and exchanges. Exception: numbers and addresses on our block list for misuse (see below).
  • Account & content data: profile content, notes, decisions/approvals, vCard exports, language and settings.
  • Verification data: phone-verification and OTP records, verification status and timestamps.
  • Block list for misuse: if we block a phone number or e-mail address by hand for misuse (for example spam or fraud attempts), we keep it readable on an internal block list, together with a protected hash and a short reason. Only our administration sees this list; matching uses the hash.
  • Technical data: access tokens, device and browser information, IP address, and security/system logs.
  • Activity log (audit trail): what happened in your account and when: sign-ins and failed attempts, security settings, devices, requests and decisions, rules, profile changes, payments, e-mails we sent you, and what Contacly or your organisation did on your account. With each entry: who did it, and the device type and browser (for example “Chrome on Windows”). For sign-ins and security events also an approximate place (country and city), which our hosting provider derives from the IP address. Entries of the same sign-in are linked and show that place too. The log holds no IP address and no content of profiles, notes or contacts. It is written for every plan; what you can see of it depends on your plan.
  • Live code: when someone exchanges with you through your temporary live code, our record of that approval notes “live code” (so it shows that you probably met). The code itself and its key stay end to end: they travel sealed and only your devices check them; we never see them.
  • Billing data (Premium): plan, transaction status and the limited payment metadata returned by our payment provider. We do not store full card numbers.
  • Payment-method check (free Premium month): for each payment method that got a free Premium month or paid for Premium, a non-reversible check value that we derive with a secret key from our payment provider’s card feature, the same kind of value for the subscription, whether it was a live or a test payment, and the date of the last use. Never the card number, no other card details and no link to your account, name or e-mail address.
  • Phone-number check (Premium light): for each phone number whose account had Premium (Premium light or paid), a non-reversible check value that we derive with a secret key from the already protected hash of your number, whether it was a live or a test payment, and the date of the last use. Never the number itself. It is not linked to your account, name or e-mail address; we can only recognise the number with it when an account with that number wants to start Premium light again. This way Premium light exists only once per number, also with a new account.

We do not intentionally collect special-category data (e.g. health, religion, political opinions) under GDPR Art. 9, and you should not enter such data into free-text fields.

4. Where the data comes from

Most data is provided directly by you when you register, build a profile, verify your phone, or make and approve requests. Some data is generated automatically when you use the service (e.g. logs, tokens, timestamps).

Where a user enters or shares the contact details of another person, we receive that person’s data from the user, not from the person directly. In that case the user is responsible for having a lawful basis to share it, and we make the information in this policy available to the affected person on request and, where required, proactively, in line with GDPR Art. 14.

5. Purposes and legal bases

We process personal data for the following purposes, each under the stated legal basis (GDPR Art. 6):

PurposeLegal basis
Creating and operating your account and profile; providing requests, approvals, exchange and vCard exportPerformance of a contract — Art. 6(1)(b)
Phone/identity verification, misuse and fraud prevention (including block lists and the notice of a blocked company sign-in), platform and account securityLegitimate interests — Art. 6(1)(f): keeping the service secure and trustworthy and preventing abuse
Maintaining the activity log: traceability of exchanges, your own view of what happened in your account, detecting misuseLegitimate interests — Art. 6(1)(f): verifiable, traceable consent to contact exchange and the security of accounts — and, where applicable, legal obligation Art. 6(1)(c)
Billing, invoicing and tax/accounting records for PremiumLegal obligation — Art. 6(1)(c) (retention) and contract Art. 6(1)(b)
Granting the free Premium month only once per payment methodLegitimate interests — Art. 6(1)(f): preventing misuse of the free month
Support and communications about the serviceContract Art. 6(1)(b) and/or legitimate interests Art. 6(1)(f)
Non-essential cookies/storage, if any are ever usedConsent — Art. 6(1)(a)

Where we rely on legitimate interests, you have the right to object (see Section 9). Where we rely on consent, you may withdraw it at any time without affecting processing already carried out.

6. Who we share data with, and international transfers

Recipients. We share personal data only with service providers acting as our processors under GDPR Art. 28, bound by data-processing agreements, in these categories: hosting/cloud infrastructure, database, email delivery, SMS/OTP delivery, payment processing, monitoring/error-logging, and customer support tooling. We do not sell personal data, and we do not share it for advertising (see Section 12).

Codes by SMS and e-mail. When a verification code is sent, the SMS or e-mail provider receives the phone number or e-mail address concerned, and the number or address passes through our systems for that purpose; we do not store it afterwards (only a protected hash and a salted commitment). Encrypted profile content is never passed on in readable form. If an address or number is already used by an account when registering, no code is sent; instead, the account that holds it receives an e-mail with a sign-in code at its own address.

Providers and locations. We use these providers (Art. 19(4) Swiss FADP):

ProviderPurposeWhere data is processed
Vercel Inc., USAHosting of the website and server functionsServer functions in Frankfurt (Germany); delivery through a worldwide network
Supabase Inc., USADatabase (profile content only in encrypted form)EU (Ireland)
Stripe Payments Europe Ltd., Ireland, and Stripe, Inc., USAPayment processingEU and USA
Link – a service of the Stripe group ([[company per the Stripe agreement]])Selling Premium and exchange packages in its own name (independent controller): payment, taxes, receipts, supportEU and USA
Telnyx LLC, USASending SMS codes; checking whether a new number is a mobile (number lookup)USA and the mobile networks in the recipient’s country
Migadu-Mail GmbH, SwitzerlandSending e-mailsFrance and Germany (EU)
Apple, Google, Mozilla, Microsoft (USA)Delivering encrypted push notifications to your browserUSA

Purchases through Link (independent controller). When you buy Premium or an exchange package, Link – a Stripe service – sells it to you as seller in its own name. For this, Link/Stripe collects your name, e-mail address, billing address (to calculate taxes) and payment details directly from you at checkout and processes them as an independent controller (not as our processor) for payment, taxes, fraud prevention and customer support, under the privacy notices of Link and Stripe linked at checkout. Name and billing address are then also kept in the customer record of our Stripe account; we do not copy them into our own database. We receive only what your account needs: whether and when you paid, receipts, the type and last four digits of the payment method, and the check value for the free-month rule (see above). We never see card numbers. Donations are processed by Stripe as our processor, as described above.

Country when buying. We offer paid plans only in certain countries. Before a purchase starts, we therefore compare two countries with that list: the country of your location, which our hosting provider derives from your IP address, and the country of your mobile number, which your browser works out and sends us without the number. We store neither. If the country of the billing address lies outside the list after the purchase, we note that country, the kind of purchase and the session number in the admin log in order to review the purchase.

International transfers. Germany, the rest of the EU/EEA and Switzerland provide adequate data protection. For transfers to the USA we rely on the Swiss-US or EU-US Data Privacy Framework where the provider is certified under it, and otherwise on the EU Standard Contractual Clauses with the Swiss addendum; a copy is available on request.

7. How long we keep data (retention)

We keep personal data only as long as necessary for the purpose it was collected for:

  • Account/profile data: for the life of the account.
  • Free accounts: after 60 days without a new phone verification, the account is deactivated and stops accepting requests. If it stays deactivated for 24 months, we delete it together with its profile data; we notify you by e-mail 30 and 7 days beforehand. Confirming your phone number reactivates the account and stops the deletion.
  • Premium and free alike: the plan changes the features, not how long data is kept. After a downgrade the profile data stays under the rules above.
  • Billing/tax records: retained for the statutory period (10 years under Swiss accounting law, Art. 958f CO).
  • Payment-method check (free Premium month): deleted automatically 24 months after the last use (free month or Premium payment), test entries after 7 days. It stays after an account is deleted, because it is not linked to any account.
  • Phone-number check (Premium light): deleted automatically 24 months after the last use (Premium light or Premium payment), test entries after 7 days. It stays after an account is deleted, because it is not linked to any account.
  • Activity log: kept as long as the account exists and for 24 months after account deletion, then deleted. We keep it because it shows what happened in the account and evidences that contact exchanges were properly authorised (our legitimate interest and, where applicable, a legal obligation). We do not change entries.
  • Block list for misuse: until we lift the entry. You can ask us at any time to review a block (see “Your rights”).
  • Block period after an account is deleted: the phone number and e-mail address of a deleted account stay on a block list as a protected hash for the block period (30 days by default), so that a deleted account cannot be created again straight away. After that they are deleted automatically.

8. How we protect data (security)

What is stored, who can read it and where the limits lie: our security page

We apply appropriate technical and organisational measures under GDPR Art. 32, including access controls, authentication, tokenisation, encryption in transit, end-to-end encryption of profile content, logging, and least-privilege access. No system is perfectly secure, but we maintain procedures to detect, investigate and respond to personal-data breaches, and we will notify the competent supervisory authority and affected individuals where the law requires (GDPR Arts. 33–34).

End-to-end encryption. The keys that open your profile are protected by your password, which we never receive (OPAQUE sign-in); a database leak, a backup or a look into the database therefore reveals no profile content, and neither can our administrators read it. For the same reason we cannot reset a forgotten password or open your profile for you: you can confirm on another signed-in device, with a fingerprint, face scan or passkey, or start over after a 72-hour waiting period (your contacts then have to be exchanged again). Please note that the code of the app is delivered by our servers: end-to-end encryption protects your data from storage and database access, not from a deliberately malicious update of the app itself.

9. Your rights

Depending on where you live, you have the following rights, which you can exercise free of charge by contacting privacy@contacly.com. We respond within one month (GDPR Art. 12(3)).

  • Access to your data, and a copy of it.
  • Rectification of inaccurate data and completion of incomplete data.
  • Erasure (“right to be forgotten”), subject to our retention duties in Section 7.
  • Restriction of processing.
  • Objection to processing based on legitimate interests.
  • Data portability (for data processed by consent or contract).
  • Withdrawal of consent at any time, without affecting processing already carried out.

You also have the right to lodge a complaint with a supervisory authority — in Switzerland, the Federal Data Protection and Information Commissioner (FDPIC); in the EU/EEA, the authority in your country of residence.

California residents (CCPA/CPRA): you have the rights to know, delete, and correct, and the right to opt out of “sale” or “sharing.” We do not sell or share personal information as those terms are defined under the CCPA, and we will not discriminate against you for exercising your rights.

10. Cookies and local storage

Contacly uses only strictly necessary cookies and local storage — for sessions, login state, language, security and PWA functionality. These are required to run the service and do not need consent. We do not use analytics, advertising, or tracking cookies. If we ever introduce non-essential cookies, we will request your consent first through a cookie banner.

Several accounts in one browser. If several accounts are signed in in one browser, a sealed cookie holds their sessions. It stays in this browser; we store no link between these accounts. Your organisation does not see which other accounts you use.

11. Changes to this policy

We may update this policy when the service, our providers, or legal requirements change. We will update the “Last updated” date above, and for material changes we will notify account users in advance by email or in-app notice. The current published version governs.

12. No ads, no tracking

Contacly uses no advertising trackers, advertising cookies, or behavioural profiling for advertising. We do not sell or share personal data, including for advertising. Technical logs are used only for operating, securing, troubleshooting and auditing the service.

13. Company accounts, managed accounts and company confirmations

Company accounts. Organisations can open a company account and manage accounts for their staff through it (Professional and Professional Plus plans). For the profiles, the team list and the contacts of these managed accounts, the organisation is the controller; we process these data on its behalf (as a processor under Art. 9 FADP and Art. 28 GDPR). Please address questions about these data to the organisation first.

What the organisation sees. When you accept an invitation, your browser creates an encrypted copy of your account key for the organisation. With it the organisation can read your profiles and change them according to its template, see and export your contacts, restore your access and delete your account. We still cannot read these contents. We point this out in the invitation, before you join and permanently in your settings.

What the log shows. The organisation’s log shows what the organisation did, also on your account (for example opening a profile, the seat, the template, restoring access). You see these entries in your audit. The organisation does not see your sign-ins, your devices or your places.

Blocked company sign-in. After several sign-in attempts with the company number and collective address, we temporarily block signing in on new devices and notify the organisation by e-mail to the collective address: time, browser and device type, and approximate place (city and country, derived from the IP address; not the IP address itself). These details concern the person who tried to sign in; usually that is someone from the organisation, but it may also be a stranger. The purpose is the security of the company account (legitimate interest, Art. 6(1)(f) GDPR). We do not store the place in our database.

Contact person. Every company account names one person of its team as its contact person (at registration; it can be handed to another person later in the settings, who confirms in their own account). That person’s browser encrypts the key of their main profile for a key of Contacly whose secret part we keep only protected by a passphrase. This lets us – and only us, in the browser after unlocking that key – open the person’s name, function, mobile number and e-mail to reach the organisation about the company account (review, billing, security). Every access is recorded in the organisation’s log. For this processing we are the controller; the legal basis is the contract with the organisation and our legitimate interest in being able to reach it (Art. 6(1)(b) and (f) GDPR). The access ends when the role is handed over or the person’s account is deleted.

When you exchange contacts with a managed account. Before the exchange you see that the account is managed by an organisation; the organisation also receives your card and the profile data you share. You can end the exchange at any time.

What we additionally process (readable):

  • master data of the organisation (name, company number, address, website, switchboard, register entry, e-mail domains) and its template for company details;
  • which accounts belong to which organisation, the seat, joining and leaving, the day of the last sign-in and the number of contacts;
  • the organisation's events (name, date, place, assigned people); whether a contact was made at an event is stored only encrypted with the contact;
  • the counting of exchanges for the organisation's quota and billing;
  • invitations: the e-mail address as a hash and sealed on the server, names given by the organisation only in encrypted form (the key is only in the mail link and is not stored), deleted once accepted or expired.

Company confirmations. A company on Contacly can confirm that you work there, once for your account; several companies are possible. For this you confirm a work e-mail address; we store only a hash of it and a commitment to your job title, not the job title itself. In each profile you choose which confirmed company it shows. We store that choice and whether the company name is on your card, so that we can sign the confirmation for the people who see this profile or receive a request from it. The company sees your request, but not your profiles or contacts, and can withdraw the confirmation; you can remove it at any time. The confirmation is renewed every year.

Legal bases and retention. For the company account itself: the contract with the organisation (Art. 6(1)(b) GDPR); for staff accounts: the organisation's instructions; for confirmations: your request. When the organisation closes its company account or deletes a managed account, we delete the accounts with their encrypted contents; phone number and e-mail stay on a block list as a hash for the blocking period (30 days by default), which applies only within that organisation. If you report your departure and the organisation does not delete your account within its deadline, we remove your access; the contacts stay with the organisation.

14. Code inspection on request

Anyone who examines Contacly's source code on request and under contract (code inspection, see /security) is kept in a register: name, organisation and address of the inspecting party, the person signing for it, the e-mail address, the people with access and their user names on GitHub or GitLab, purpose, contract number, period and fee, and the dates of signature, payment and confirmed deletion.

Purpose and legal basis: concluding and performing the code inspection contract (Art. 31(2)(a) FADP; Art. 6(1)(b) GDPR). To give access we pass the user names to the chosen platform, GitHub (GitHub, Inc., USA) or GitLab (GitLab Inc., USA), where the snapshot is kept for the duration of the inspection. The transfer to the USA takes place because it is necessary for the contract you asked for (Art. 17(1)(b) FADP; Art. 49(1)(b) GDPR). After the last day we remove the access and delete the snapshot.

Retention: ten years after the end of the inspection, like business records (Art. 958f CO); then we delete the entry automatically.

Highlighted fields are placeholders to be completed before publication.