Data processing agreement

A data processing agreement with Yleisölaskuri: the template and how to sign it.

For:Producer

Counter+This feature is included in the Counter+ and Venue Counter packages. See pricing

In this section: Guest list and people register (9)

When you store your event's guest, media or crew data in Yleisölaskuri, you are the controller and Yleisölaskuri is the processor. Article 28 of the GDPR requires a written data processing agreement between them. Below is a ready-made agreement with Yleisölaskuri's details already filled in.

How to make the agreement

  1. 1Copy the agreement and fill in the bracketed parts: your organisation's details and contact person.
  2. 2Sign the agreement and send it as a PDF to asiakaspalvelu@oskarijarvelin.fi.
  3. 3You'll receive the agreement signed by Yleisölaskuri by email.
Data processing agreement
DATA PROCESSING AGREEMENT

Parties
Controller: [Customer name], business ID [business ID], [address], contact person [name, email] ("Customer")
Processor: Tmi Oskari Järvelin (Yleisölaskuri), Y-tunnus 3284249-9, Kaislatie 11 L 54, 90150 Oulu, asiakaspalvelu@oskarijarvelin.fi ("Yleisölaskuri")

1. Purpose and scope
This agreement covers the personal data that Yleisölaskuri processes on the Customer's behalf when the Customer uses the Yleisölaskuri service to manage its events' personal data register (guest list, invitations, media accreditation and crew). It supplements the use of the service and applies for as long as Yleisölaskuri processes personal data on the Customer's behalf.

2. Description of the processing
Nature and purpose: storing, displaying and deleting data in the service to manage the event's guest list, access rights, entry, media accreditation and staff working days.
Data subjects: the event's guests, invited guests, media representatives, and subcontractor and Customer staff.
Personal data: name, title or role, organisation, media outlet or partner represented, email address, phone number, attendance or working days, access level, arrival time and entrance, accreditation status, and notes and additional details added by the Customer.
Special categories of data: the service is not intended for processing them. If the Customer collects special category data with custom fields (e.g. health-related dietary information), the Customer is responsible for the legal basis for processing it.
Duration: for as long as the service is used and until the deletion described in section 10 is complete.

3. Customer's obligations
The Customer is responsible for having a lawful basis for the processing, for providing data subjects with a privacy notice, and for storing only necessary data in the service. The Customer gives its processing instructions through the service settings and this agreement.

4. Yleisölaskuri's obligations
Yleisölaskuri
- processes personal data only on the Customer's documented instructions, including with regard to transfers, unless required to do so by law
- informs the Customer if, in its opinion, an instruction infringes data protection law
- ensures that persons processing the data have committed to confidentiality
- implements the technical and organisational security measures in the annex
- assists the Customer in responding to data subject requests; the Customer can search, correct and delete data itself in the service
- assists the Customer in meeting its obligations regarding security, breach notification, impact assessments and prior consultation
- makes available to the Customer the information needed to demonstrate compliance with this agreement.

5. Staff access to data
Yleisölaskuri's administrator may open the Customer's event dashboard for customer support only at the Customer's request or where strictly necessary to keep the service working.

6. Sub-processors
The Customer gives general authorisation to use sub-processors. At the time of signing, the sub-processors are:
- Supabase Inc. – database and files. Transfers outside the EU/EEA are based on the European Commission's standard contractual clauses (Implementing Decision (EU) 2021/914).
- Vercel Inc. – servers (server functions in Stockholm). Transfers are based on the EU–US Data Privacy Framework.
- Proton AG (Switzerland) – email, such as the invited guest's confirmation. Transfers are based on the European Commission's adequacy decision for Switzerland.
Yleisölaskuri notifies the Customer of changes to sub-processors at least 30 days in advance. The Customer may object to a change on reasonable grounds and, if necessary, stop using the service. Yleisölaskuri binds sub-processors to equivalent data protection obligations and is responsible for their performance.

7. Transfers outside the EU/EEA
Data may be transferred outside the EU/EEA only on the grounds described in section 6 or another ground under Chapter V of the GDPR.

8. Personal data breaches
Yleisölaskuri notifies the Customer of a personal data breach without undue delay and no later than 48 hours after becoming aware of it. The notification includes the known information on the nature of the breach, the data subjects and amount of data concerned, the likely consequences and the measures taken.

9. Audits
On request, Yleisölaskuri provides the information the Customer needs to verify compliance with this agreement. The Customer may, at its own cost, audit the processing or have it audited by an independent auditor at most once a year, with 30 days' notice.

10. Deletion of data
The service deletes an event's personal data automatically one month after the last day of the event, when the event's days have been set. The Customer can also delete the data itself at any time. When the use of the service ends, Yleisölaskuri deletes the Customer's remaining personal data within 30 days of the Customer's request, unless required by law to retain it. Data is removed from backups as part of the normal backup rotation.

11. Liability and governing law
The parties' liability is determined under Article 82 of the GDPR. This agreement is governed by Finnish law. Disputes are settled in the Oulu District Court.

Annex: technical and organisational security measures
- Data in transit is encrypted (HTTPS/TLS).
- Personal data is stored in a database the browser cannot access directly: all queries go through the server, and row-level security prevents the public key from accessing personal data.
- Access to an event's data requires the event's credentials (PIN code, customer account, or the partner's, media's and subcontractor's own links). Partners and subcontractors only see their own people.
- PIN codes are stored as salted scrypt hashes and sign-in links as SHA-256 hashes. Sessions are signed and expire.
- Staff sessions can be revoked at once and door links changed if a device goes missing.
- Pages containing personal data are not stored in device caches.
- Personal data is deleted automatically when the retention period ends.
- The sub-processors' services also encrypt data at rest.

Signatures
Customer: [place and date] [name and position] [signature]
Yleisölaskuri: [place and date] Oskari Järvelin [signature]

What the agreement covers

  • What data and whose data is processed, and how Yleisölaskuri may process it: only on your instructions.
  • Sub-processors (Supabase and Vercel), the transfer mechanisms and 30 days' notice of changes.
  • Breach notification, audits and deletion of data when the agreement ends.
  • An annex describing the app's technical and organisational security measures.

Data subjects are told about the processing in your privacy notice: A privacy notice for your event.

Didn't find an answer?

Tell us what you were looking for and we'll help.

Contact us