Información legal
Privacy Policy
Versión 1.1 · vigente desde 10 de noviembre de 2026 Versiones anteriores
Esta no es la versión vigente. Abrir la vigente
Aún no hay traducción, se muestra la versión en inglés.
Contenido
Privacy Policy
Version 1.3 — 7 November 2026
This Policy explains how POTALONU processes personal data when you use the POTALONU website (potalonu.com), the POTALONU Telegram bot and Telegram Mini App, and the organizer dashboard (together, the "Platform"). It applies to Buyers, Organizers, Recipients and visitors.
1. Who is responsible for your data
1.1. The controller of your personal data is the POTALONU entity that operates the Platform for you:
- POTALONU LTD, a private company limited by shares registered in England and Wales, company number 17565970, registered office 128 City Road, London, EC1V 2NX, United Kingdom — for all users and Events, except as stated below;
- POTALONU, LLC, Delaware, USA, file number 2576779, 1111B South Governors Avenue, Dover, DE 19904 — for orders, Tickets, payments and Organizer data relating to Events that take place in the United States, and for the accounts of users who live in the United States.
Payment data relating to payments in Russian roubles is processed by POTALONU LTD and POTALONU, LLC as joint controllers under an arrangement between them. POTALONU LTD informs you about this processing in this Policy and receives and answers your requests about it at help@potalonu.com; you may exercise your rights against either company.
1.2. Contact for all privacy matters: help@potalonu.com; Telegram: @potalonusupport. Our representative in the European Union under Article 27 GDPR will be named in the Legal Notice.
1.3. Organizers are separate controllers. When you buy a Ticket, the Organizer of the Event receives your data as the seller (section 5) and is responsible for its own use of it. The Organizer's details are shown on the Event page and in your order confirmation.
2. What data we collect
Account. Name, username, email address, password (stored as a hash), language. If you sign in with Telegram: your Telegram ID, first and last name, username, language, and whether your account is a Telegram Premium account or a bot; we verify the sign-in data Telegram sends us but do not store the verification data. If you sign in with Google: your email address and name.
Balance. When your account is created, we create a balance record for it: Coins earned and spent and, if you publish Events or receive Donations or Revenue Splits, proceeds, fees and payouts (Organizer Terms, clause 3.5).
Orders and Tickets. Event, Tickets and Add-ons ordered, amounts, currency, payment status and method, order time, the answers you give to the Organizer's checkout questions, Ticket status and check-in time, Coins earned and spent. We do not receive or store your card number: card details are entered on the payment provider's page.
Organizer and Recipient data. Business name or, if you publish Events in your own name, your name as shown on the Platform; registration and tax details, address, payout account details, documents provided for identity verification (collected and held by our payment partners, not by us, except where you send them to us directly), team members and scanner devices you add to your organization, sales, fees and payouts. If you publish an Event, your account name and, where set, your profile picture and page are shown publicly as the Organizer of that Event (section 5).
Communications. Messages you send to support by email or in the Telegram bot, and our replies.
Technical data. IP address, device and browser type, pages visited, referral source and UTM parameters, Mini App launch parameters, error reports. Cookies and similar technologies are described in the Cookie Policy.
Location. The city we show events for is determined from your IP address in the Mini App or from the venue of your last purchased Ticket. You can change the city at any time.
3. Why we process your data and on what legal basis
| Purpose | Data | Legal basis |
|---|---|---|
| Creating and operating your account, signing you in | account, technical | performance of the contract (Buyer Terms / Organizer Terms) |
| Selling and delivering Tickets, processing payments, refunds and payouts, running the Coins programme, keeping your balance | orders, balance, Organizer data | performance of the contract |
| Showing you as the Organizer of Events you publish: on the Event page and in listings, on Tickets and in Buyers' order confirmations and emails | account (name, profile picture, page) | performance of the contract (Organizer Terms); legal obligation to identify the seller to consumers |
| Sending transactional messages: Tickets, sign-in codes, email confirmation, refunds, changes and cancellations of Events | account, orders | performance of the contract |
| Announcing new Events of Organizers, artists and venues you follow | account, follows | your consent given by following; withdraw by unfollowing on the page |
| Showing Events for your city | technical, orders | legitimate interest in a relevant listing; you can change the city |
| Support and complaints | communications, orders | performance of the contract; legitimate interest in resolving issues |
| Security, fraud prevention, bot protection, error monitoring | technical | legitimate interest in a secure service; legal obligations |
| Verifying Organizers and Recipients before payouts, sanctions screening | Organizer data | legal obligations (anti-money-laundering, sanctions); contract with payment partners |
| Accounting, tax and reporting obligations, including platform reporting rules (DAC7 and UK equivalent where applicable) | orders, Organizer data | legal obligations |
| Analytics of how the Platform is used | technical | consent (cookies; see the Cookie Policy) |
| Advertising measurement for Organizers who use their own Meta Pixel on their Event pages | technical, purchase amount | consent (cookies; see the Cookie Policy) |
| Internal statistics on buyers (one-time, repeat and regular buyers; spend) | orders | legitimate interest in understanding the Platform; visible to Platform staff only, no automated decisions |
| Establishing, exercising or defending legal claims | all categories | legitimate interest |
Where the legal basis is legitimate interest, you may object (section 8).
4. Automated decisions and profiling
We do not make decisions about you by automated means that have legal or similarly significant effects. Payment fraud screening is performed by our payment partners under their own policies; a declined payment can be retried or discussed with support. Event listings are sorted by date and by category priority set by our staff; there is no personalised ranking. The city filter and the Event announcements you receive depend on the city determined as described in section 2.
5. Who receives your data
Organizers. For each order, the Organizer of the Event receives your name, email address, Telegram username or identifier where provided, order and Ticket details, check-in data and your answers to the Organizer's checkout questions. Organizers may export the email addresses of their Buyers. Under the Organizer Terms, Organizers may use this data only to deliver the Event and to communicate with you about it; any other use, including marketing, requires a separate lawful basis obtained by the Organizer. Organizers are independent controllers and are responsible for their own compliance.
Recipients. Where a Donation or a Revenue Split is involved, the Recipient sees the order amount and, for Donations, your name as shown at checkout.
Buyers and visitors, if you publish an Event. Everyone who views the Event page or an Event listing sees your name and, where set, your profile picture and page as the Organizer; Buyers also receive your name on their Tickets and in their order confirmations and emails.
Service providers (processors). Companies that process data on our behalf and on our instructions:
| Provider | Service | Location of processing |
|---|---|---|
| Render | application hosting and database | Germany |
| DigitalOcean (Spaces) | file storage | Netherlands |
| Amazon Web Services (S3) | file storage | Ireland |
| Sentry | error monitoring and logs | Germany |
| Seats.io | seating charts | EU |
| Cloudflare | content delivery, bot protection, registration captcha (Turnstile) | USA (global network) |
| Google (Workspace) | sending emails to users | USA |
| Google (Maps API) | venue addresses | USA |
| Google (Sign-in) | sign-in with Google account | USA |
| Google (Analytics) | usage analytics, with your consent | USA |
| IPinfo | determining the city from the IP address in the Mini App | USA |
| Gravatar (Automattic) | avatars; receives a hash of your email address | USA |
| Segment (Twilio), where enabled | user profile and purchase events for analytics | USA |
Payment partners (independent controllers for their own processing).
| Partner | Service | Data | Location |
|---|---|---|---|
| Stripe (Stripe Payments UK Ltd; Stripe, Inc. for Events in the United States) | card and local payments, Connected Accounts, payouts | name, email, amount, order details; for Organizers — identity and bank details | United Kingdom; USA |
| Rouble Payment Provider — a third-party payment provider engaged by POTALONU, LLC | payments in Russian roubles, for Events where the Organizer has enabled them | email, amount, order details | Hong Kong; payments are routed through Russian payment systems, so payment data may be processed in Russia |
| Telegram and Telegram Wallet | Telegram bot and Mini App; payments in USDT inside the Mini App | Telegram ID, bot messages, amount | outside the EU/UK |
| Bridge Building Inc. and its affiliates | payout accounts for Organizers who choose them | Organizer identity, address and documents, as provided by the Organizer to Bridge | USA; Luxembourg (EU) |
| Meta (Meta Pixel), only on Event pages where the Organizer uses its own pixel | advertising measurement for the Organizer | page views, purchase amount and currency | USA |
Others. Authorities, courts and regulators where the law requires; professional advisers; a buyer of our business in a merger or sale, under the same protections.
We do not sell personal data.
6. Transfers outside the EU and the UK
Our hosting, database, files, error monitoring and seating charts are in the European Union. Some providers and partners listed in section 5 process data in the United States or in other countries. Where data leaves the EU or the UK, we rely on the European Commission's standard contractual clauses and the UK addendum or international data transfer agreement, on adequacy decisions (including the EU-US Data Privacy Framework for certified US providers), or, for payments you choose to make in Russian roubles or USDT, on the necessity of the transfer for the performance of your contract. You can request details of the safeguards at help@potalonu.com.
7. How long we keep your data
| Data | Retention |
|---|---|
| Account | while the account exists; deleted on your request (section 8), subject to the rows below |
| Orders, Tickets, payments, refunds, payouts, invoices | 10 years after the transaction, for accounting and tax obligations |
| Organizer verification and tax reporting data | as required by anti-money-laundering, sanctions and tax reporting law (generally 5 to 10 years) |
| Support communications | 3 years after the last message |
| Technical logs | 12 months |
| Analytics data | as set in the Cookie Policy |
When you delete your account, data that we are not required to keep is deleted or anonymised; data we must keep is restricted to that purpose.
8. Your rights
You have the right to access your data, to receive a copy in a portable format, to correct it, to delete it, to restrict its processing, to object to processing based on legitimate interest, and to withdraw consent at any time (which does not affect processing before withdrawal). To exercise a right, write to help@potalonu.com or @potalonusupport from the email address or Telegram account linked to your account; we respond within one month. You can also stop announcements by unfollowing an Organizer, artist or venue on their page, and manage cookies as described in the Cookie Policy.
If you believe we have not handled your data correctly, you may complain to a supervisory authority: in the United Kingdom, the Information Commissioner's Office (ico.org.uk); in the European Union, the authority of the country where you live; residents of other countries may contact their local data protection authority.
9. Security
Traffic to the Platform is encrypted (HTTPS with HSTS) and routed through Cloudflare. Passwords are stored as bcrypt hashes; payment partner credentials are encrypted in our database; stored data is encrypted at rest by our hosting providers. Access to user data in the dashboard is role-based (platform staff; users managing the Events they publish; team members and scanners of organizations; artists and their managers), and accounts are locked after repeated failed sign-in attempts. No system is completely secure; tell us at help@potalonu.com if you suspect unauthorized access to your account.
10. Children
The Platform is for users aged 16 and over. We do not knowingly collect data from children under 16; if you believe a child has provided data to us, contact us and we will delete it.
11. Telegram Mini App
When you open the Mini App, Telegram passes us launch data: your Telegram ID, name, username, language, Premium and bot flags, the parameter that opens a specific page, whether the bot may message you, and a signature with a timestamp that we use only to verify the data. The Mini App's own privacy button links to this Policy. Payments in USDT inside the Mini App are made through Telegram Wallet under Telegram's terms.
12. United States residents
We do not sell or share personal data for cross-context behavioural advertising as defined in California law, and we do not process sensitive personal data for purposes requiring a right to limit. US residents may exercise the rights in section 8 and will not be discriminated against for doing so.
13. Changes
We may update this Policy. Material changes are announced on the Platform before they take effect. The date of the current version is at the top.