Tips Privacy Policy
Last updated: November 1, 2026
1. Controller and scope
Yaroslav Baran, trading as RESTOBOT (RESTOBOT Yaroslav Baran), Śląska 6, m. 14, 02-472 Warsaw, Poland; NIP 1133092409; REGON 524951267. Contact: [email protected]. RESTOBOT is the controller for running the tipping platform and its own transaction, support and security records. This notice supplements the general Privacy Policy. Venues and recipients can be separate controllers for their own tip allocation, employment, tax and complaints purposes.
2. Data and purposes
We process the tip amount, currency, time, recipient or pool allocation, venue, payment and transfer references, payment status, refunds and disputes. These records are needed to carry out the service you request (Article 6(1)(b) GDPR), to comply with any applicable accounting obligation (Article 6(1)(c)), and for proportionate fraud prevention and claims handling (Article 6(1)(f)).
Full card numbers and security codes are entered into the payment provider's interface. RESTOBOT does not store them. The integration processes payment identifiers, status and provider responses; it is inaccurate to treat every payment-related identifier as anonymous or say that RESTOBOT receives only a success/failure flag.
You can submit a rating or comment. We process it to provide the requested feedback function (Article 6(1)(b)). Where you pay a tip without selecting stars, the current system records an inferred five-star rating; this is an inference from the transaction, not a statement you explicitly made. Contact support to question or correct it. Avoid unnecessary names or sensitive data in free-text comments.
Technical request and log data, such as IP address, browser information and payment-session identifiers, supports security and operation under Article 6(1)(f). Information you supply in a complaint is used to investigate and respond. We do not require a RESTOBOT payer account, but a payment provider may need identifying or contact data for the payment.
3. Recipients and payment providers
Stripe processes card payments and may act as a processor for instructed payment functions and as an independent controller for its own compliance, fraud-prevention and other purposes. Its roles depend on the service and purpose; see Stripe Privacy Policy and Stripe Data Processing Agreement.
The recipient and authorised venue staff can see relevant amounts, allocation, payment status and feedback needed to administer tips. Depending on the enabled route, records can concern a direct worker payment or a venue pool and its later distribution. Optional comments may be public where the feature is enabled. IT, hosting and communications providers receive the information needed for their functions; authorities receive information where lawfully required.
4. Retention
Retention is based on the transaction, support, security and legal purpose. Transaction evidence is needed while payment, refund or dispute obligations remain unresolved and for applicable claims periods. Accounting or tax records are retained only for the statutory period applicable to that record; this is not automatically five years from the transaction date. Feedback is retained for its relevant display or complaint purpose and reviewed on a deletion request. Security logs must be kept no longer than necessary for their security purpose. Providers can have separate statutory retention obligations.
Contact support for the period applicable to a specific record or to request deletion. Erasure is subject to lawful retention obligations and other GDPR conditions; removal of a public comment does not necessarily erase related dispute evidence immediately.
5. International processing and cookies
Providers may process data outside the EEA. Such transfers require an applicable adequacy decision or a GDPR Chapter V safeguard, such as Standard Contractual Clauses with necessary supplementary measures. A provider's independent processing and transfer arrangements are described in its notice. Contact support for recipient and destination information and a copy of applicable transfer safeguards.
The payment page uses technical cookies or equivalent storage required for the requested payment and security. Optional analytics or advertising storage requires prior permission where required by law. The general Privacy Policy and, when the page is on a venue website, that venue's cookie notice explain enabled optional tools and how to change your choices.
6. Rights and changes
Under the GDPR and subject to its conditions, you can request access, correction, erasure, restriction and portability; object to legitimate-interest processing; and withdraw any consent without affecting earlier lawful processing. You can complain to the Polish President of UODO (uodo.gov.pl) or another competent supervisory authority, including in your habitual residence or place of work.
Email [email protected]. A transaction reference, date and amount may help locate a record, and proportionate identity verification may be needed. We normally respond within one month. A permitted extension of up to two further months will be explained within the first month. Providing required payment data is necessary to process the payment; feedback is optional.
This is an information notice, not a request for blanket consent. Changes do not retroactively authorise new processing; any required notice or separate consent will be provided.