Data processing agreement.

The customer is the controller of the personal data of attendees at its event. Chemistry is the processor: we only process that data on the customer's behalf and for the purpose below.

For the data of the customer's accounts (name, email address, billing details) we are the controller ourselves; the privacy statement applies to that.

We process the data to sign attendees up, match them with each other for one-to-one conversations at the event, message them about it over WhatsApp, collect their feedback and give the customer an anonymised report.

We do not use the data for any other purpose, not for our own marketing and not to train AI models.

Processing lasts as long as the engagement and ends with the deletion described below.

Data subjects are the attendees who sign up for the event. The data concerned:

• name and phone number (WhatsApp);
• the WhatsApp messages between the attendee and the bot, and their delivery status;
• the answers to the intake questions, such as job title, company, what someone is looking for and who they want to meet;
• public data from the LinkedIn profile, only if the attendee shares a profile link: job title, employer, experience and reach, and a level derived from them;
• matches, the place and time of the conversation, and the feedback on the match (whether the conversation happened, a rating and any remark).

We only process the data on the customer's written instructions. This agreement, the event settings and what the customer does in the dashboard count as those instructions.

If we believe an instruction infringes the GDPR, we say so straight away.

Whoever works with the data at our side is bound to confidentiality and only gets access when the engagement requires it.

We take appropriate technical and organisational measures. Currently these include:

• the database is in the EU (Frankfurt) and the application runs in the Frankfurt EU region;
• all connections are encrypted (TLS); storage at our hosting providers is encrypted;
• organisers sign in with a personal account with a password and a second factor (authenticator app), and per event only see what the customer gives them access to;
• the database cannot be read from outside through a public API;
• secrets and keys live only in the server environment, not in the code;
• monitoring of the platform records no phone numbers or message texts;
• we collect no more than needed, and delete automatically (see Retention).

The customer agrees to the sub-processors below. We impose the same obligations on them as in this agreement and remain responsible for them towards the customer.

If we want to add or replace a sub-processor, we announce it by email in advance. The customer may object on reasonable grounds within 14 days; if we cannot resolve it, the customer may end the engagement free of charge.

Some sub-processors are based in the United States or may process data there. Those transfers are covered by the European Commission's standard contractual clauses (SCCs) or, where the sub-processor participates, the EU-US Data Privacy Framework.

If we discover a personal data breach, we notify the customer without undue delay and at the latest within 48 hours, with what we know at that point: what happened, which data and how many attendees, the consequences and what we are doing about it.

The customer decides whether the breach is reported to the supervisory authority and to the data subjects. We help with that.

We help the customer with attendee requests for access, correction or deletion. In the dashboard the customer can view an attendee's data and remove an attendee; that deletes the person with their messages, matches and ratings, at every event with the same phone number.

An attendee can always send STOP. They then get no more messages and are no longer matched. Their data stays until the purge, so the partner of a match already made keeps their history; if they want it gone sooner, the customer removes them or they email us.

If a request reaches us, we forward it to the customer.

The platform keeps attendees, with their messages, answers, LinkedIn data, matches and ratings, until the customer deletes them. This keeps two people from being matched again at a later event. The customer deletes all data of an event with the button in the dashboard. An attendee who sends "delete my data" is deleted at once. After the agreement ends we delete the data at the customer's request.

What remains are aggregated figures (how many sign-ups, how many conversations, the average rating) and an anonymised report with quotes without names. No attendee can be identified from them.

Database backups are overwritten after the fixed period of our database provider. We keep hosting logs no longer than needed to resolve problems.

On request we give the customer the information needed to show that we comply with this agreement. Once a year, or after a data breach, the customer may have an audit carried out by an independent expert bound to confidentiality, with reasonable notice of at least 14 days and at the customer's expense.

Liability under this agreement is as set out in the terms and conditions.

This agreement lasts as long as we process data for the customer. At the end we delete the data as described above; if the customer wants it beforehand, it can export the attendees from the dashboard before the purge.

Obligations that by their nature continue, such as confidentiality, still apply after that.