What happens to your data
Your profiles, business cards and contacts are encrypted in your browser before they reach our servers. The key is yours, not ours: there is no master key, so we cannot read this content, even if we wanted or had to. Where this protection ends, for example because the code comes from us, we name below just as openly as what we need to run the service. With a company account, the company also holds a key. That is explained here too.
1. Your case, step by step
Choose your case
Step by step
- 1Sign upYour browser creates your keys, and your password never leaves it. We hold a check value of your phone number and your account e-mail, sealed on the server.
- 2Saving a profileYour browser seals your profile with your key. We store only ciphertext and cannot read it.
- 3Sharing your card and QR codeYour card is sealed. The key sits in the link behind the #, and that part never reaches our server.
- 4Request and exchangeRequests and notes are sealed for the recipient. We see that two accounts exchange contacts, not what they exchange.
- 5ContactsYour contacts, groups and rules are sealed with your key. Only you can read them.
- 6PayingLink, a Stripe service, sells Premium and packages in its own name. We never see card details. For the free month we store only a check value of the payment method, without any link to your account, for 24 months.
- 7Log and administrationWe log events without content. Our administration sees your e-mail only masked, and revealing it is logged.
- 8Lost accessWithout your password, a remembered device or a passkey you cannot get to your data, not even with our help. That is the price of us not having the key.
- 9DeletingDeleting removes profiles, requests, devices and rules. Check values of phone and e-mail stay for a blocking period, the log without content for 24 months. We delete frozen free accounts after 24 months, with a warning first.
Who can read what
| The person | Other side | Contacly server | Contacly admin | Service providers | |
|---|---|---|---|---|---|
| Profile | reads it | after approval | no | no | no |
| Business card | reads it | with the link | no | no | no |
| Contacts, groups, rules | reads it | no | no | no | no |
| Requests and notes | reads it | reads it | only that it exists | only that it exists | no |
| Account e-mail | reads it | no | sealed, opens it to send mail | only masked | mail service, Stripe |
| Phone number | reads it | after approval | only a check value | only a check value | SMS service when sending |
| Payments | their own | no | amounts, no card | amounts, no card | Link and Stripe |
| Who exchanged with whom | reads it | reads it | readable | as figures and an anonymous graph | no |
Anyone with direct access to the database sees what the “server” column shows, and no more: ciphertext stays ciphertext without the key.
Step by step
- 1Sign upYour browser creates the company account’s keys and the emergency kit; we hold the kit only in sealed form. We can read your master data (name, address, website, switchboard) and your domains. The collective address is sealed on the server. Contacly checks the domain and approves the company.
- 2Saving a profileYour staff’s profiles are sealed the same way, but you can read them through the escrow copy and change them according to the template. That happens in your browser; our server only sees ciphertext. The template itself is readable for us.
- 3Sharing your card and QR codeThe same as for private accounts. QR colour and note preset come from your template and are readable for us.
- 4Request and exchangeThe same, and you can read the content through the escrow copy. For billing we keep a readable record that an exchange ran through your pool: the request and the side, no content.
- 5ContactsYour staff’s contacts belong to you. You can read and export them; the export is created in your browser. The server only records the format and the number.
- 6PayingLink sells here too. Stripe receives the company name, the collective address and the company number, and your VAT number if you enter one. We see seats, interval, amounts and Stripe IDs, never a profile.
- 7Log and administrationYour log shows device, action, seats, master data old and new, and template names. People appear there only as a membership; your browser fills in the name from the sealed team list. Our administration sees master data and the company per account, never profiles, contacts or the team list.
- 8Leaving and handing overA person reports leaving. You delete the account and can hand their contacts to someone else; the other side gets a sealed notice. If you do not react in time, Contacly removes the person’s access. The contacts stay with you.
- 9Lost accessWith your password or the emergency kit you get back in. If both are gone, nobody can open the escrow copies, not even Contacly.
- 10DeletingWhen you close the company account we delete every staff account, the master data and the company account. Export the contacts first; afterwards they are gone. Invoices stay with Link.
Who can read what
| The person | Company | Other side | Contacly server | Contacly admin | Service providers | |
|---|---|---|---|---|---|---|
| Profile of a staff member | reads it | reads it | after approval | no | no | no |
| Business card | reads it | reads it | with the link | no | no | no |
| Contacts of a staff member | reads it | reads it | no | no | no | no |
| Requests and notes | reads it | reads it | reads it | only that it exists | only that it exists | no |
| Team list (names, function, department) | no | reads it | no | no | no | no |
| Master data, template, events of the company | partly, on the card | reads it | partly, on the card | readable | readable | no |
| Account e-mail | reads it | for the invitation | no | sealed, opens it to send mail | only masked | mail service, Stripe |
| Payments | no | their own | no | amounts, no card | amounts, no card | Link and Stripe |
| Who exchanged with whom | reads it | reads it | reads it | readable | as figures and an anonymous graph | no |
Anyone with direct access to the database sees what the “server” column shows, and no more: ciphertext stays ciphertext without the key.
Step by step
- 1Sign upThe invitation goes to your work address; we hold it only as a check value and in sealed form, and delete it when you accept. Your browser creates your keys and also seals an escrow copy for your company. You are told before you join.
- 2Saving a profileThe company reads along hereYour browser seals your profile like everyone else’s. Your company can read it through the escrow copy and change it according to its template. Contacly cannot read it.
- 3Sharing your card and QR codeThe same as for private accounts. Your company can set the QR colour and the note.
- 4Request and exchangeThe company reads along hereThe same, and your company can read the content. For billing our server sees that the exchange ran through the company pool.
- 5ContactsThe company reads along hereYour contacts belong to the company. It can read and export them, and when you leave they stay with the company. For anything private, use a private account.
- 6PayingYour company pays. None of your data goes to Stripe for this.
- 7Log and administrationWhat your company does with your account is in its log. You see those entries yourself under “Your company” in the settings. What your company reads there in its own browser, the server cannot see.
- 8Leaving and handing overYou can report that you are leaving. Your company deletes the account; if it does not do so in time, Contacly removes your access. The contacts stay with the company.
- 9Lost accessYour company restores your access.
- 10DeletingYour company deletes your account and can hand over your contacts. The blocking period then applies only within company accounts, so your private account is not affected.
Who can read what
| The person | Company | Other side | Contacly server | Contacly admin | Service providers | |
|---|---|---|---|---|---|---|
| Profile of a staff member | reads it | reads it | after approval | no | no | no |
| Business card | reads it | reads it | with the link | no | no | no |
| Contacts of a staff member | reads it | reads it | no | no | no | no |
| Requests and notes | reads it | reads it | reads it | only that it exists | only that it exists | no |
| Team list (names, function, department) | no | reads it | no | no | no | no |
| Master data, template, events of the company | partly, on the card | reads it | partly, on the card | readable | readable | no |
| Account e-mail | reads it | for the invitation | no | sealed, opens it to send mail | only masked | mail service, Stripe |
| Payments | no | their own | no | amounts, no card | amounts, no card | Link and Stripe |
| Who exchanged with whom | reads it | reads it | reads it | readable | as figures and an anonymous graph | no |
Anyone with direct access to the database sees what the “server” column shows, and no more: ciphertext stays ciphertext without the key.
Step by step
- 1Sharing your card and QR codeYou open the card with the key in the link; our server does not see it. If the card belongs to a company account, it says so: “Account of company X. Company X also sees your card.”
- 2Request and exchangeThe company reads along hereYour request is sealed for the person, and their company can read it too. The notice is shown before you send it. We only see that you exchange.
- 3ContactsThe company reads along hereIf you exchanged with a company account, your card is with the company too. You can end the exchange at any time.
- 4Leaving and handing overIf someone leaves the company, your contact can pass to another person. You then get a notice and can end the exchange.
Who can read what
| The person | Their company | Contacly server | |
|---|---|---|---|
| Your card after the exchange | reads it | reads it | no |
| Your request and your note | reads it | reads it | only that it exists |
| That you exchanged | reads it | reads it | readable |
Anyone with direct access to the database sees what the “server” column shows, and no more: ciphertext stays ciphertext without the key.
2. What we see, and what we don’t
| Data | Protection | Who can read it |
|---|---|---|
| Profile (all fields) | End to end, with your profile key | You and people you approved for an exchange |
| Business card (name and chosen fields) | End to end; the card key is in the link behind the # and never reaches the server | Whoever has your link or QR code |
| Contacts, groups, when a contact last changed, your notes on contacts, rules, names on the block list | End to end, with your account key | Only you |
| Requests and notes | End to end, sealed for the recipient | Sender and recipient |
| Live code (changes every minute) | The code and its key end to end: the key is sealed in your personal data, the code travels sealed in the request, only your devices check it | Only you and the person who scanned it. We see that an approval came through a live code (our record of the approval notes “live code”), not the code |
| Recommendations (only if you allow them) | Note, cards and who recommended end to end, sealed for each side; your card key goes to your contacts inside your sealed profile | The recommender and the two people. We see that two people have an open recommendation for each other, like a request, until both accept, one declines or 30 days pass; then it is deleted. Not who recommended, not the note, no card |
| Partner companies (only if your company connects with one) | Cards, share links and - where your company allows it - profile keys, sealed under a partnership key that only the two companies and their people hold | The people of the partner company; the whole profile only where your company allows it. We see which companies are connected, in which mode, which profiles are listed and when a profile was opened; no name, no card |
| Push preview (“Anna would like to …”) | Sealed for your device | Only your device |
| Password | Never leaves your browser (OPAQUE) | Nobody, not even us |
| Phone number | We store only a check value and a proof of verification | It passes through our server to the SMS service when a code is sent; the SMS service sees it. We do not store it in readable form – unless we block a number by hand for abuse; it then stays readable on our internal block list |
| Account e-mail | Sealed on the server (not end to end) | Our server opens it to send you mail. Our administration sees it only masked, and revealing it is logged |
| Payments | With Link and Stripe | Link, a Stripe service, sells Premium and packages. We see no card details, only amounts and references |
| Free Premium month | Check value of the payment method | No link to your account, deleted after 24 months |
| Metadata | Readable, needed to run the service | We see when accounts were created, plan, balance, between which accounts exchanges exist (not their content), times, language, quiet hours |
| Activity log (audit) | Readable, needed to run the service; no content | Who, when, what, device type and browser; for sign-ins and security events an approximate place (country and city). Entries of one sign-in are linked and show it too. No IP address in the log. You see it according to your plan. Our administration can read it for support and security; when it opens the log of one account, that is logged too |
| IP addresses | Briefly, against abuse | Our rate limits store them only as a hash; our hosting provider logs access. If you write to us through the contact form, your IP address is in the mail we receive. When you buy, we read only the country from it and do not store it |
Several accounts in one browser. Accounts signed in side by side wait in a sealed cookie of this browser. No table on our side links them; our server only sees them together in the moment a request carries that cookie. Someone reading our database could at most guess from points in time. Each remembered account keeps its keys here under its own device key, until you sign out and forget this device. Rules run in your browser for the account that is open; those of a waiting account run when you open it.
Limits of the log. We do not change entries, and a rule in the database refuses changes and early deletion. Whoever controls the whole database could switch that rule off, so the log is no proof against ourselves. The place is an estimate from the network: a VPN or a mobile network can show another city. And the log only knows what reaches our server: what your browser does with decrypted data stays out of it.
Registering with an address or number that is taken. We then send no code, and the page does not say whether an account exists: it looks the same as for anyone else. The account that holds the address or number gets an e-mail with a sign-in code instead.
No tracking. We use no analytics or advertising tools.
3. Honest limits
- The code comes from us. As with any encrypted web app, our server delivers the code that encrypts in your browser. A compromised server could deliver altered code. Our code is not public. You can check what your browser sends (see “Check it yourself”), and anyone who wants to examine the code can get time-limited access on request and under contract.
- Metadata. We see that two accounts exchanged contacts, not what they exchanged. Groups and names are sealed, but the exchange graph itself is needed to run the service.
- Account e-mail. It is encrypted at rest but not end to end, because otherwise we could not send you mail.
- Links of one account can be linked. Whoever has two of your share links can tell that they belong to the same account, but cannot read more.
- No recovery without device and password. If you lose your password, all remembered devices and passkeys, you have to exchange your contacts anew. That is the price of us not having the key.
- Test phase. As long as demo mode is active, verification codes can be shown for testing. On the production domain it is locked; before launch it can only be opened there for a limited time, 30 days at most.
4. Company accounts
With a company account, a company manages the accounts of its staff. Profiles and contacts stay end-to-end encrypted, but the company gets a key to them, Contacly does not. Anyone with an account through a company learns this before joining, permanently in the settings, and with every contact.
| What | Person | Company | Contacly server |
|---|---|---|---|
| The person’s account key, and with it profiles, contacts, rules | Yes (password, remembered devices) | Yes: escrow copy, sealed in the person’s browser for the company’s key when accepting the invitation | No, stores only the sealed copy |
| Key of the company account | No | Yes (password; emergency kit to print) | No, stores the kit only in sealed form |
| Team list with names, function, department | No | Yes | No |
| Staff profiles (applying the template) | Yes | Yes, through the escrow copy in the company’s browser | No, the routes deliver and store ciphertext only |
| Staff contacts, export | Yes | Yes; the export is created in the company’s browser | No |
| Event and note on a contact | Person and other side | Yes, through the escrow copy | No, they are in the sealed envelope |
| Hand-over notice when a person is deleted | The other side | No | No |
| A contact assigned to a person | Yes, with a sealed note; the other side gets the person’s card and can end it | Yes; the keys are wrapped again in the company’s browser | No, it stores sealed grants and notes only |
| Company address book (when the company switches it on) | Every person of the team, read only | Yes; a team key made in the company’s browser | No: sealed keys and which grant a line stands for; nothing once the other side ends the exchange |
| A company confirming a private profile | The person; the other side checks the signature | Sees the request, sealed for it | Hash of the work e-mail, a commitment to the function (not the function), which of your profiles shows the company and whether its name is on the card |
| Profile of the contact person (name, function, mobile, e-mail) | Yes; the person agrees when taking the role | Yes, through the escrow copy | No: only the profile key sealed in the person’s browser for Contacly’s admin key. Our administration opens it in the browser after unlocking that key with a passphrase; every access is recorded in the company’s log |
What our server additionally knows: master data (name, company number, address, website, switchboard, register, status, e-mail domains) and templates; events (name, date, place, assigned people as IDs); who belongs to which company (account IDs, seat, joining, leaving, last sign-in day, number of contacts); that an exchange ran through the company pool (request ID and side, no content); invitations, with the address only as a hash and sealed, and names given for them only in encrypted form; the key is only in the mail link, passes our server and mail provider once when sending and is not stored. All of it is deleted on acceptance or expiry. Our administration sees master data and the company per account, never a profile (except the contact person’s, see the table), a contact or the team list; the company’s log (who, when, what, device type and browser, at sign-in an approximate place, no content).
- The company reads along. It can read profiles and change them according to the template, export contacts, give them to a person of the team or share them with the whole team, restore access and delete the account.
- The other side can end any exchange, also with a company account. A managed person cannot, because the contacts belong to the company.
- No key restart of your own for managed accounts and company accounts; otherwise the escrow copy would be useless. Lost access goes through the company.
- Way out. A person can report leaving. If the company does not delete the account in time, Contacly removes the access (sign-in, devices, second factor, phone check value). The contacts stay with the company.
- Contacly can delete a company account. As a rule with a date: the company gets an e-mail with a link. If it confirms that it wants to keep the account, the account stays; if not, it is deleted after that date, with all staff accounts, profiles and contacts. If no subscription is running 14 days after registration, this happens automatically. In clear cases, such as a plainly false registration, also at once. Contacly cannot read the contents when doing so either.
- Company key and emergency kit lost: then nobody can open the escrow copies, not even Contacly.
5. For IT and data protection
The questions a company asks before buying, on one page.
| Question | Answer |
|---|---|
| Who holds which key? | The person holds their account key. The company holds an escrow copy of it, sealed in the person’s browser. Contacly holds neither. See “Company accounts”. |
| Who is responsible for what? | For the profiles, the team list and the contacts of managed accounts, the company is the controller. We process these data on its behalf (Art. 9 Swiss FADP, Art. 28 GDPR). For our own operating data we are responsible ourselves. |
| Where can we read the terms? | In the B2B terms and the data processing agreement linked below. Both are still drafts until legal review is complete; the version is shown on the pages. |
| Which service providers, which region? | See “Our service providers”. Database in the EU (Ireland), server functions in Frankfurt. |
| How long is what kept? | See the privacy policy, section on retention. The company decides about staff accounts; closing the company account deletes them. |
| How do our data get out? | Contacts as an export from the company’s browser. What the server holds on the company as a JSON download in the server view (company settings). |
| What happens when someone leaves or we cancel? | See the steps “Leaving and handing over” and “Deleting” above. |
| One shared password: how is it protected? | An e-mail code for every new device, a fresh code for sensitive actions, a device list and a log of who did what from which device. |
| Who reports incidents to whom? | Security reports to security@contacly.com. Incidents involving your staff’s data: see the data processing agreement. |
| Can we check this ourselves? | Yes: developer tools (“Check it yourself”), the server view, the demo company, and code inspection on request. |
6. Check it yourself
- Open Contacly in Chrome, Edge or Firefox and sign in.
- Open the developer tools (F12), Network tab.
- Change a field in your profile, for example “Company: Test company”, and save.
- Click the request to /api/account/profiles/… in the list, Payload tab.
- Expected: instead of “Test company” you only see a string like the one below. That is all our server receives.
- Optional: open your share link and see that the part behind the # never appears in a request.
Prefer it without developer tools? What the server sees of you in your account settings shows the same thing.
PUT /api/account/profiles/…
{
"blob_layer2": "v1.pk1.1ip8GknwKhM_oPmw.XfKU5bUE69X0nh5Vnx5ZIHTFvxeHKiqkGvuY7YIMQeXIYBevYnTTAnZS0c6BXxnwLud89fyeeJ6BB1mwa4_MuuJ3TB6hWFLqQoZU9EdRA3IwoO7YTrDfS_IJ…",
…
}As a company
- In the company account, press F12, Network tab.
- Open a person in the team and apply the template.
- Look at the requests to /api/company/members/…/profiles/…: only ciphertext goes back and forth. It becomes readable only in your browser.
- In the server view of the company you see the wrapped keys and the sealed team list: that is all the server has of them.
7. Our service providers
| Service | What for | What it sees | Where |
|---|---|---|---|
| Vercel | Hosting, delivery of the website, server functions | Access including IP, encrypted content passing through | Functions in Frankfurt (Germany); delivery worldwide |
| Supabase | Database | Stored data as in the table above: ciphertext, hashes, metadata | EU (Ireland) |
| Stripe and Link | Payments; Link sells as merchant of record | Payment details, the e-mail and name given, country, for companies also company name and number | EU and USA |
| Telnyx | SMS with verification codes; at sign-up and on a change of number, whether the number is a mobile | Phone number and code when sending; the number for the check | USA and the mobile networks of the recipient’s country |
| Migadu-Mail GmbH | E-mails | E-mail address and content of the (generally worded) mail | France and Germany (EU) |
| Push services of the browsers (Apple, Google, Mozilla, Microsoft) | Notifications | Only the encrypted message and the time | Depending on the device |
As of 2026-11-15. The same list is in the privacy policy.
8. Methods we use
- Key exchange: X-Wing (hybrid: ML-KEM-768 and X25519), which also protects against future quantum computers
- Encryption: AES-256-GCM
- Password: OPAQUE (RFC 9807), the password never leaves the browser; key derivation with Argon2id
- Signatures of confirmations: Ed25519; your browser checks for itself whether a number was confirmed
- Key derivation: HKDF-SHA-256
- Second factor: TOTP, passkeys (WebAuthn), recovery codes
- Remember device: a non-exportable device key in the browser (WebCrypto)
- App lock (optional): with a passkey that supports PRF, the key on this device opens only after fingerprint, face or device PIN; it closes again when you come back after the chosen time. Everything stays on the device, the server learns nothing about it
9. Code inspection on request
Our code is not public. Anyone who wants to examine it, for a security review or due diligence, gets a personal snapshot of the code on GitHub or GitLab, as they prefer: read-only, time-limited, under contract. The access ends by itself after the last day. The contract explicitly allows reporting vulnerabilities.
Independent security researchers and auditors: please get in touch. We decide on an inspection without a fee case by case.
Request inspection10. Report a vulnerability
Please write to security@contacly.com. We confirm receipt, keep you informed and thank you on the list below if you wish.
Safe harbor. If you search and report in good faith, do not access or change other users’ data, do not disrupt the service and do not publish the vulnerability before it is fixed, we will not take legal action against you.
- Not allowed: attacks on other users, social engineering, denial of service, automated mass scanning.
- On contacly.com, test only with your own accounts.
Thanks
Nobody yet. You could be the first.