Digevent Privacy Policy

Published: September 15, 2026

This Privacy Policy (hereinafter "Policy") applies to all information that the Operator may obtain about the User when using the website digevent.org and the local Digevent service installed at event venues (hereinafter together "Service").

Use of the Service means User's agreement to this Policy. If you do not agree to these terms, refrain from using the Service.

This Policy was developed in accordance with Federal Law No. 152-FZ of July 27, 2006 "On Personal Data", Federal Law No. 149-FZ of July 27, 2006 "On Information, Information Technologies, and Information Protection", and for users from the European Union, the General Data Protection Regulation (GDPR).

1. Key Concepts

• Operator — [OPERATOR NAME, TO BE SPECIFIED], processing personal data within the Service.
• User / Guest — event attendee or any other person sending a file through the Service.
• Venue — event location (club, hall) where the local Digevent server is installed.
• Event — a specific event at a Venue, to which the Service automatically assigns files sent within its timeframe.

2. What data we collect

2.1. Data you provide yourself

• The uploaded file itself (photo, video, or audio) and its metadata — file name, size, type, checksum (MD5);
• If you use login via social network (Telegram/Google/Facebook/VK/TikTok — feature in development at the time of this Policy's publication) — the minimal set of data that the network transmits to the Service to display your name next to the submitted materials (usually name and profile identifier, sometimes profile photo);
• Name provided manually, if social network login is not used and the Venue offers to sign materials with your name voluntarily.

2.2. Data collected automatically

• IP address of the request (processed by Cloudflare infrastructure when delivering the request to the Service);
• Venue and approximate upload time (used to assign the file to the correct event);
• Technical request data (browser/device type, User-Agent).

2.3. What we DO NOT collect

The Service does not request a password for basic file submission, does not collect payment data (at the time of this Policy's publication, guest file submission is free), and does not track precise geolocation beyond the fact of submission at a specific Venue.

3. Purposes of processing

1. Receipt and storage of the submitted file in the archive of a specific Venue/Event;
2. Association of the file with the author (when using social network login or manually providing a name) for subsequent voluntary coordination with performers/organizers regarding which event materials can be published;
3. Accrual of bonus tokens if the corresponding program is active at the specific Venue;
4. Protection of the Service from abuse — duplicate submissions, malicious attachments, storage overflow;
5. Compliance with legal requirements.

4. Legal basis for processing

Processing is based on: the fact of use of the Service (implied consent) and, separately, explicit consent when using social network login; the legitimate interest of the Operator in ensuring the operation of the Service and protection against abuse; legal requirements applicable to the Operator.

5. Where and how data is stored

The Service has two independent storage systems with different data fates — this is important to understand:

• Temporary transit (only for files sent via digevent.org/send, not directly over the venue's Wi-Fi) — the file temporarily goes into cloud storage (Cloudflare R2) and is stored there ONLY until the local server of the corresponding Venue retrieves it — normally from several minutes to hours. Receipt of new files in this transit is automatically suspended if the accumulated volume exceeds the set limit, until the Venue processes the queue — so the transit storage does not grow uncontrollably.
• Local Venue archive — accepted files (including those sent directly over Wi-Fi in the hall) are stored on a server that is physically located at the Venue itself. The retention period of the archive is determined by the operator of the specific Venue — the Service does not establish a centralized retention period for all venues.

Data transmission to and within the Service is protected by encryption (HTTPS/TLS). Access to temporary transit storage is limited to authorized API access of the specific Venue.

6. Data sharing with third parties

• Cloudflare, Inc. — request delivery infrastructure and temporary transit storage (R2), see Cloudflare Privacy Policy;
• Your chosen social network (when using login through it) — processes your login data according to its own privacy policy; the Service receives from it only a minimal identification set;
• To the operator of the corresponding Venue — the entire accepted Event archive; this is the main purpose of the Service;
• Per legal request from government authorities.

The Service does not transmit submitted files to any third parties for editing, publication, or other commercial use without a separate coordination procedure with the author and/or performers following the event — this is a separate, voluntary process outside the scope of automatic processing described in this Policy.

7. Cookies

The digevent.org/send page itself does not set cookies for guests. If you use login via social network, the network itself may set its own cookies during the login process — this is regulated by its own policy, not this Policy.

8. Your rights

You have the right to: obtain information about what data about you is being processed; request clarification or deletion of it; revoke previously given consent (including use of social network login). To do so, contact the details in section 11. We review requests within 30 calendar days.

9. Cross-border data transfer

Due to the use of global Cloudflare infrastructure and the guest's choice of international social networks for login, some data may be processed outside the country where the file was sent (in particular, in the USA). Such transfer is carried out to the extent necessary for the operation of the corresponding service (Cloudflare, chosen social network).

10. Changes to the Policy

The Operator may make changes to this Policy. The current version is always available at https://digevent.org/privacy. Continued use of the Service after publication of a new version means agreement to the changes.

11. Contact information

For questions about personal data processing, contact:

• Operator: [OPERATOR NAME, TO BE SPECIFIED]
• Email: privacy@digevent.org

Last updated: September 15, 2026

← back to file upload