Security

What happens to your data

As of 2026-11-15

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

2. What we see, and what we don’t

DataProtectionWho can read it
Profile (all fields)End to end, with your profile keyYou 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 serverWhoever has your link or QR code
Contacts, groups, when a contact last changed, your notes on contacts, rules, names on the block listEnd to end, with your account keyOnly you
Requests and notesEnd to end, sealed for the recipientSender 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 itOnly 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 profileThe 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 holdThe 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 deviceOnly your device
PasswordNever leaves your browser (OPAQUE)Nobody, not even us
Phone numberWe store only a check value and a proof of verificationIt 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-mailSealed 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
PaymentsWith Link and StripeLink, a Stripe service, sells Premium and packages. We see no card details, only amounts and references
Free Premium monthCheck value of the payment methodNo link to your account, deleted after 24 months
MetadataReadable, needed to run the serviceWe 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 contentWho, 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 addressesBriefly, against abuseOur 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.

WhatPersonCompanyContacly server
The person’s account key, and with it profiles, contacts, rulesYes (password, remembered devices)Yes: escrow copy, sealed in the person’s browser for the company’s key when accepting the invitationNo, stores only the sealed copy
Key of the company accountNoYes (password; emergency kit to print)No, stores the kit only in sealed form
Team list with names, function, departmentNoYesNo
Staff profiles (applying the template)YesYes, through the escrow copy in the company’s browserNo, the routes deliver and store ciphertext only
Staff contacts, exportYesYes; the export is created in the company’s browserNo
Event and note on a contactPerson and other sideYes, through the escrow copyNo, they are in the sealed envelope
Hand-over notice when a person is deletedThe other sideNoNo
A contact assigned to a personYes, with a sealed note; the other side gets the person’s card and can end itYes; the keys are wrapped again in the company’s browserNo, it stores sealed grants and notes only
Company address book (when the company switches it on)Every person of the team, read onlyYes; a team key made in the company’s browserNo: sealed keys and which grant a line stands for; nothing once the other side ends the exchange
A company confirming a private profileThe person; the other side checks the signatureSees the request, sealed for itHash 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 roleYes, through the escrow copyNo: 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.

QuestionAnswer
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.

What leaves your browser when you save (shortened)
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

ServiceWhat forWhat it seesWhere
VercelHosting, delivery of the website, server functionsAccess including IP, encrypted content passing throughFunctions in Frankfurt (Germany); delivery worldwide
SupabaseDatabaseStored data as in the table above: ciphertext, hashes, metadataEU (Ireland)
Stripe and LinkPayments; Link sells as merchant of recordPayment details, the e-mail and name given, country, for companies also company name and numberEU and USA
TelnyxSMS with verification codes; at sign-up and on a change of number, whether the number is a mobilePhone number and code when sending; the number for the checkUSA and the mobile networks of the recipient’s country
Migadu-Mail GmbHE-mailsE-mail address and content of the (generally worded) mailFrance and Germany (EU)
Push services of the browsers (Apple, Google, Mozilla, Microsoft)NotificationsOnly the encrypted message and the timeDepending 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 inspection

10. 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.

Every statement on this page has been checked against the code. If you find something that does not hold, please tell us.