Data processing agreement (DPA) for company accounts
1. Parties and roles
1.1 Controller: the organisation with a company account (the “company”).
1.2 Processor: Rahm Digital Solutions, Passage du Cardinal 8, 1700 Fribourg, Switzerland (the “Processor”), the provider of Contacly.
1.3 The Processor is itself the controller of its own operational data (account e-mail, billing, abuse prevention, security logs); its privacy policy for Contacly applies to them.
2. Subject matter, nature and purpose
For the company, the Processor stores and transmits the data that the company and its employees enter and exchange in Contacly, in order to provide digital business cards and to exchange and manage contacts. The duration corresponds to the term of the contract for the company account.
On the company's instruction, the Processor makes the cards and, where the company sets it, the profiles of its people accessible to the people of connected partner companies (B2B terms 6.4 to 6.10). Every person can opt out of this.
3. Data and data subjects
| Data subjects | Data | Form on the Processor’s server |
|---|---|---|
| Employees with a managed account | Profile details (name, function, department, contact details), team list | End-to-end encrypted – not readable by the Processor |
| Account ID, seat, joining, exit, day of the last sign-in, number of contacts | readable (operation, billing) | |
| Invitation address | as a hash and sealed on the server, deleted when accepted or expired | |
| Employees’ contacts (the other side) | Business card, note, event | End-to-end encrypted |
| that an exchange exists between two accounts; counting for the company pool | readable (metadata) | |
| The company’s contact points | Collective e-mail address, switchboard | the company’s master data, readable |
| Event participants (from the company’s view) | A contact’s link to an event | End-to-end encrypted |
Sensitive personal data is not intended to be processed.
4. Instructions
The Processor processes the data only on documented instructions from the company. The instructions are this agreement and the settings the company makes in the company account (e.g. template, invitations, deletion, export). If the Processor considers an instruction unlawful, it informs the company.
5. Confidentiality
Persons at the Processor with access to systems are bound to confidentiality. Because of the end-to-end encryption, they cannot read content (profiles, contacts, team list).
6. Technical and organisational measures
- End-to-end encryption of profiles, business cards, contacts, rules, team list and requests in the browser; the keys leave the devices only sealed.
- Escrow copy: The account key of a managed person is sealed in the person’s browser for the company’s key. The Processor only stores the sealed copy.
- Emergency kit of the company account only sealed; without the kit and the company password, nobody can open the escrow copies.
- Sign-in with OPAQUE (the password never leaves the browser), confirmation codes by SMS or e-mail, optional second factor; company sign-in with a code sent to the collective address.
- Data minimisation: phone numbers and e-mail addresses for matching only as hashes; account e-mail sealed on the server, only masked in the admin area, every display logged.
- Logs without the content of profiles and contacts. The company log records seats, template names and the company’s master data, old and new, and persons only as memberships. Admin actions are logged. The company’s sign-ins carry the device type, browser and an approximate location (country and city), no IP address. Retention: as long as the company account exists, then 24 months.
- Access protection of the database (row level security, separate service keys), rate limits against abuse.
- Transport encryption (TLS) for all connections.
Details: /security.
7. Sub-processors
7.1 The company approves the following sub-processors. The Processor announces new sub-processors to the collective address at least 30 days in advance; the company may object for good cause and terminate the contract as of the date the change takes effect.
| Service | Purpose | What it receives | Region |
|---|---|---|---|
| Vercel | Hosting, server functions | Requests incl. IP address; content only encrypted | Functions Frankfurt (EU), delivery worldwide |
| Supabase | Database | stored data as in clause 3 | EU (Ireland) |
| Stripe and Link | Payments; Link sells as the seller | the company’s invoice and payment data | EU and USA |
| Telnyx | SMS with confirmation codes | phone number and code when sending | USA and the mobile networks in the recipient’s country |
| Migadu-Mail GmbH (registered in Switzerland) | E-mails | e-mail address and content of the (generally worded) mail | France and Germany (EU) |
| Browser push services (Apple, Google, Mozilla, Microsoft) | Notifications | only the encrypted message and the time | depending on the device |
7.2 The Processor contractually obliges the sub-processors to an equivalent level of protection. For transfers to countries without an adequate level of data protection, the Processor relies on standard contractual clauses or another permissible basis.
8. Assistance to the company
8.1 Data subjects’ rights: The company answers requests from its employees and contacts itself; it can read, change and export profiles and delete accounts. The Processor assists within what is possible without access to encrypted content.
8.2 Data security breaches: The Processor notifies the company of a data security breach affecting its data without undue delay after becoming aware of it, with the known details of its nature, extent and the measures taken.
8.3 Impact assessment: The Processor provides the information the company needs for a data protection impact assessment (in particular clause 6).
9. Deletion and return
9.1 The company exports the contacts in the browser before closing (CSV, vCard, xCard). On closing, the Processor deletes all managed accounts, invitations and the company account, including the encrypted content.
9.2 The phone number and e-mail of deleted managed accounts remain on a block list as hashes for the blocking period (set in the admin area, 30 days by default), which applies only within the same company; they are then deleted.
9.3 If the Processor deletes the company account under clause 9.4 of the B2B terms, the same applies to the data as when the company closes it.
9.4 Backups of the database are overwritten according to the database provider’s schedule.
10. Evidence and audits
On request, the Processor provides the company with the information needed to demonstrate compliance with the obligations (this agreement, clause 6, list of sub-processors). On-site audits are possible by arrangement and at the company’s expense.
11. Final provisions
Clause 13 of the B2B terms applies (Swiss law, place of jurisdiction Fribourg) and – in case of conflict on data protection matters – this agreement prevails over the B2B terms.