§1Parties and roles
This data processing agreement (“DPA”) is part of the organizer agreement between the organizer and TruAlly:
- Company
- [TruAlly legal entity — not set]
- Address
- [Registered address — not set]
- MERSIS
- [MERSIS number — not set]
Company details not yet published. The registered title, address and MERSIS number of the contracting TruAlly company will appear here before this text takes effect.
- For the personal data the organizer collects for its events, the organizer is the data controller and TruAlly is the data processor within the meaning of Law No. 6698 on the Protection of Personal Data (“KVKK”).
- Where the organizer is subject to the EU General Data Protection Regulation (“GDPR”), the same roles apply as controller and processor, and this DPA is intended to serve as the contract Article 28 GDPR requires.
- This DPA does not cover data TruAlly controls itself — TruAlly accounts and the platform-wide profile and matchmaking — which the privacy notice and the KVKK information notice describe.
§2Subject matter, nature and duration
- Subject matter and purpose: providing the TruAlly event software to the organizer — registration, passes, exhibitor and stand management, matchmaking, meetings, messaging, badges, check-in, leads, payments for the organizer’s sales and reports.
- Nature of processing: collection through forms and imports, storage, organisation, display to the audiences the organizer configures, matching, transmission of messages and notifications, export and deletion.
- Duration: for as long as the organizer agreement is in force, and afterwards only until the data is returned or deleted under §11.
§3Data subjects and categories of data
Data subjects: the organizer’s attendees, exhibitors and their staff, sponsors, speakers, visitors, and the organizer’s own staff.
Categories of data: identity (name); contact (email, phone and other details provided); professional (company, position, industry, offers and needs); event participation (registrations, answers to the organizer’s registration questions, passes, meetings, check-ins, badge scans and leads); customer transaction (orders, stand bookings, invoices and payment status — card details are entered on the payment provider’s page and are not stored by TruAlly); communications (messages sent through the platform); and transaction security (session records, IP addresses in logs, audit records).
The service is not designed for special categories of personal data (Article 6 KVKK, Article 9 GDPR). The organizer will not configure registration questions that collect them unless it has a lawful basis to do so and has told TruAlly in writing.
§4Processing on documented instructions
TruAlly processes the organizer’s personal data only on the organizer’s documented instructions. This DPA, the organizer agreement and the organizer’s use and configuration of the service are those instructions; further instructions may be given in writing.
TruAlly does not process the data for its own purposes, does not sell it, and does not use one organizer’s event data for another organizer. If the law requires TruAlly to process the data otherwise, it will tell the organizer first unless the law forbids it. TruAlly will tell the organizer if, in its view, an instruction breaches data-protection law.
§5Confidentiality of personnel
TruAlly gives access to the organizer’s personal data only to staff and contractors who need it to provide, support or secure the service, who are bound by a written confidentiality obligation or a statutory one, and whose access is limited to what their role requires.
§6Security measures
TruAlly takes the technical and organisational measures Article 12 of the KVKK requires to prevent unlawful processing of and access to personal data and to keep it safe, and the measures appropriate to the risk under Article 32 GDPR. They currently include:
- encryption in transit (TLS) for traffic between users and the service;
- encryption of secrets the service holds, such as the organizer’s payment-provider credentials, and encrypted session cookies;
- role-based access control: organizer staff see only what their role allows; staff sign in with a password and a second factor; participants sign in with single-use links;
- isolation of each organizer’s data from every other organizer’s, enforced in the application for every request;
- audit logs of administrative actions, including access by TruAlly’s own staff;
- regular backups, integrity-checked, kept on a rolling cycle;
- data minimisation and retention rules, such as removing personal details from security records after a set period.
TruAlly may update these measures as technology and risks change, provided the overall level of protection does not decrease.
§7Sub-processors
The organizer authorises TruAlly to engage the sub-processors named on the sub-processor list. TruAlly imposes on each of them data protection obligations no less protective than this DPA and remains responsible to the organizer for their performance.
TruAlly will give at least 30 days’ notice before adding or replacing a sub-processor, by updating the list and emailing the workspace owner. Within that period the organizer may object on reasonable data-protection grounds. The parties will try in good faith to resolve the objection; if they cannot, the organizer may terminate the organizer agreement before the change applies.
A payment service provider the organizer connects to its own workspace is engaged by the organizer under its own contract, not by TruAlly.
§8Assistance to the organizer
Taking into account the nature of the processing, TruAlly helps the organizer meet its obligations as controller:
- Data-subject requests under Article 11 KVKK (Articles 15–22 GDPR): the organizer console lets the organizer find, export, correct and erase a person’s event data. If a request reaches TruAlly for data the organizer controls, TruAlly forwards it to the organizer without undue delay and does not answer it on the organizer’s behalf unless instructed.
- Security, breach handling and assessments: TruAlly provides the information reasonably needed for the organizer’s own risk assessments, data protection impact assessments and dealings with the Personal Data Protection Board or another supervisory authority.
§9Personal data breaches
If TruAlly becomes aware of a breach affecting the organizer’s personal data, it notifies the organizer without undue delay and within 48 hours of becoming aware, so that the organizer can notify the Personal Data Protection Board within the 72 hours the Board expects (and, where the GDPR applies, its supervisory authority under Article 33 GDPR).
The notification describes, as far as then known, what happened, the categories and approximate number of people and records concerned, the likely consequences, and the measures taken or proposed. Information not yet available is provided as it becomes available. TruAlly takes reasonable steps to contain the breach and limit its effects. Notifying the Board and the people concerned is the organizer’s decision as controller.
§10International transfers
Some sub-processors process data outside Türkiye; the sub-processor list shows where. TruAlly transfers the organizer’s personal data abroad only under Article 9 of the KVKK as amended in 2024:
- to a country, sector or organisation covered by an adequacy decision of the Board; or
- under an appropriate safeguard — in practice, the standard contract published by the Board, notified to the Personal Data Protection Authority within five business days of signature — or another safeguard Article 9 provides, such as binding corporate rules or a written undertaking authorised by the Board; or
- where a specific transfer falls within the exceptions Article 9 allows.
Where the organizer is subject to the GDPR and personal data is transferred to a country without an EU adequacy decision, the parties will put in place the EU standard contractual clauses or another safeguard under Chapter V GDPR.
§11Deletion or return at the end
- For 30 days after the organizer agreement ends, the organizer can export its event data with the export tools in the organizer console.
- After that, TruAlly deletes or anonymises the organizer’s personal data, unless the law requires it to be kept, in which case it is kept only for that purpose and period.
- Deleted data drops out of backups as they rotate on their normal cycle; until then backups are not used for any other purpose.
- On request, TruAlly confirms in writing that deletion has been carried out.
§12Audits
- Documentation first. TruAlly makes available the information reasonably needed to show compliance with this DPA: a description of its security measures, the sub-processor list and answers to reasonable written questionnaires.
- On-site audit. If the documentation is not enough, or a supervisory authority requires it, the organizer may audit, itself or through an independent auditor bound by confidentiality, with at least 30 days’ written notice, no more than once a year unless after a breach, during business hours and without access to other organizers’ data.
- Audits are at the organizer’s cost.
§13Liability and precedence
Liability under this DPA is governed by the limitation of liability in the organizer agreement, to the extent the law allows. Governing law and courts are those of the organizer agreement.
Where this DPA and the organizer agreement conflict on the processing of personal data, this DPA prevails.
§14Contact
Questions about this DPA, data-subject requests that reach you about TruAlly’s processing, and audit requests go to support@trually.test.