1. Who is responsible for whose data?
Desdoor involves two different relationships, and responsibility differs between them.
- Your account and your team: the data controller under the Turkish Personal Data Protection Law (KVKK, Law No. 6698) and the GDPR is Raşit Şahin (owner of the Desdoor brand; desdoor.com). Address: Bereketzade Mah. Büyük Hendek Cad. No:11/1 Beyoğlu/İstanbul · E-mail: privacy@desdoor.com
- Guests of your events: you are the data controller for guest list, ticket and application data. Desdoor processes this data only on your behalf and on your instructions, as a data processor. Informing your guests is your responsibility; this policy is written to help you do that.
Contact: privacy@desdoor.com · Support: support@desdoor.com
2. Data we process
Account and team
| Data | Why |
|---|---|
| E-mail address | Sign-in, account recovery, notifications |
| Name, profile photo | So the team can see who did what |
| Role and permissions | Access control |
| Notification token | App notifications |
| Session and device signals | Fraud prevention |
Guest and ticket data
| Data | Why |
|---|---|
| Guest name, number of companions | Identity matching at the door |
| Arrived / not arrived and entry time | Occupancy tracking and the night report |
| VIP mark | Operations |
| Gender | Statistics and occupancy breakdown. This is not the guest's own declaration; it is selected by the door staff. The organizer can switch this field off entirely in settings. |
| Ticket holder's name, age | Ticket record (age is optional) |
| Guest / ticket e-mail and phone | Ticket delivery and contact. Kept in a separate record with narrower access; people working through a door link cannot see it. |
Event applications
Name, gender, year of birth (required for the age-limit check), Instagram username, e-mail, the consents you gave, and an irreversible digest of the IP address the application came from. The raw IP address is not stored.
Blocklist
Name, phone, e-mail and a short reason note for people the organizer does not want to admit to the venue, plus the user ID of whoever entered the record. This is the organizer's business decision and is used for automatic application rejection. The reason field is limited to 280 characters, and the interface clearly warns that special categories of data such as health or criminal records must not be written there.
Other
- Team messages — deleted when the event is archived
- Staff performance counters — who issued how many tickets, how much revenue
- Images — event poster, ticket design, organization logo, profile photo
- Activity log — who did which action
- E-mail of people who opted in to marketing — only with explicit consent
- Subscription and purchase information — plan and payment status
- Crash and performance data — to fix app errors, not linked to an identity
3. Service providers
Your data is processed only by the providers below, acting on our behalf. None of them may use the data for their own purposes, and data is never sold to anyone.
| Provider | Purpose | Where |
|---|---|---|
| Google Firebase | Authentication, database, file storage, server functions, notifications | European Union |
| Google reCAPTCHA Enterprise | Detecting fake clients on the web | Google infrastructure |
| Apple DeviceCheck / Google Play Integrity | Detecting fake clients in the mobile app | Apple / Google |
| Amazon SES | Sending ticket and notification e-mails | European Union |
| Sentry | Crash and error reporting | Sentry infrastructure |
| RevenueCat | Subscription management | United States |
Ticket QR codes are generated on our own server and embedded in the e-mail; no third-party QR service is used. The app and the invitation page do not load files from external sources.
4. Retention periods
| Data | Period |
|---|---|
| Account and team information | As long as the account is open. If there is no sign-in for three years, warning e-mails are sent in the 33rd and 35th month; at the end of the 36th month the account is deleted together with the data of any organization you are the sole owner of. |
| Live event data (guests, tickets, applications) | Deleted automatically 30 days after the event ends |
| Figures of an archived event (attendance, revenue, breakdowns) | As long as the organization exists |
| Name list of an archived event | Deleted automatically after 24 months; the figures remain |
| Blocklist | As long as the organization exists; the organization owner can clear it at any time |
| Activity log | 30 days |
| Digest of a deleted account's e-mail | 30 days (abuse brake) |
| Undeliverable e-mail addresses | 12 months |
| Our subscription and payment record | 5 years after the relationship ends (statutory retention) |
When an organization is deleted: everything belonging to it — events, guests, tickets, archives, reports, images and all uploaded files — is permanently deleted. No shadow copy is kept. If you have your own legal retention obligations, export your data before deleting.
5. Deleting your account
In the app, go to Settings → Account Management → Permanently Delete My Account. You will be asked to sign in again for security.
- Deleted: your e-mail address, name, profile photo, phone number, notification tokens and your sign-in account.
- Kept: the record of actions you performed (tickets you issued, guests you checked in, cash figures) is the organization's business record and is not deleted. Only your name appears in these records; nothing that allows contacting you remains.
If you are the organization owner, deleting your account deletes the entire organization — all events, guests, archives and team access included. This cannot be undone.
A new account cannot be opened with the same e-mail address for 30 days. This is an abuse brake, not a permanent block.
6. Your rights
Under KVKK Article 11 and the GDPR you have the right to learn whether your data is processed, to request information, to learn whether it is used in line with its purpose, to request correction or deletion, to object to processing, and to request a portable copy.
You can send your requests to privacy@desdoor.com. We respond within 30 days at the latest.
If you are a guest: your data is processed by the organizer of the event you attended. You can send your request directly to the organizer or write to us; we will forward it to the organizer concerned.
7. Security
Data is encrypted in transit. Access is role-based: door staff see the guest list but not contact details or revenue. Door links are locked to a single event and become invalid automatically when the event ends.
9. Children
Desdoor is a business tool and is not directed at people under 18. Event applications apply the age limit set by the organizer (18 by default).
Contact
For privacy questions: privacy@desdoor.com
© 2026 DESDOOR. All rights reserved.