Privacy Policy
Version dated 15 October 2026 · personal data, cookies and your rights
1. Who is responsible for your data
The controller of personal data in QRelay is Sebastian Kula, Wólka Zdunkówka 60, 21-310 Wohyń, Poland. For data enquiries, copies or account deletion, email sebastian.kula.24.12@gmail.com or write to the postal address above.
When a menu or code owner gives us other people’s data solely to publish or operate their service, they may be the controller and QRelay a processor. The data processing agreement covers that scope. We process account, billing and security data as controller for our own purposes.
2. Information we use
Account: email, account identifier and creation date, password hash, email verification status, verification and password-reset tokens and plan status. Terms records include the date, language, version and hash of the supplied document, registration or order reference and confirmation delivery status. We do not store your plain-text password.
Content: code names, link endings and destinations, menu content, sections, dishes, descriptions, prices and display settings. This may include personal data if you enter it. Published menu content is accessible to anyone with the link.
Statistics: scan count, last-scan time and events containing a code identifier and scan time. Menus have a view count. These tables do not contain guest profiles, IP addresses, locations or advertising identifiers. An event and its time can nevertheless relate to a person in a particular context, for example if an owner assigns a code to one individual.
Security and contact: session identifiers, hashed keys derived from IP addresses or emails in login, registration and reset rate-limit counters, technical server logs and correspondence. Hashing does not make data anonymous. Data comes from you, automatically when handling requests, and from Stripe in connection with payments.
3. Purposes and legal bases
Contract performance — GDPR Article 6(1)(b): registration, account maintenance, login, publishing codes and menus, statistics, Pro purchases, subscriptions and service enquiries. If you contact us as an employee or business representative, processing your contact details relies on the legitimate interest in communicating with that business under Article 6(1)(f).
Legal obligation — GDPR Article 6(1)(c): mandatory accounting and tax records, handling data rights and legally required reports. Legitimate interests — Article 6(1)(f): preventing abuse, diagnostics and security, answering other correspondence and establishing, exercising or defending legal claims.
Consent — GDPR Article 6(1)(a): optional Google Ads and conversion measurement. Access to device information is also governed by Polish electronic communications law. Refusing does not prevent registration, purchases or reading a menu.
4. Stripe and payment data
We send Stripe your email or customer identifier, QRelay account identifier and selected plan. Stripe returns a customer identifier and events used to establish Pro status. You provide card details, billing address and required tax details in the external payment system. QRelay’s database does not store full card numbers or CVC.
Payments use Managed Payments: Stripe/Link is merchant of record as identified at checkout. Stripe may act as an independent controller for sales, taxes, fraud prevention and financial obligations. See the Stripe Privacy Policy and payment documents for details and the relevant entity.
5. Hosting and other recipients
Hosting, the database, technical mail and backups are provided by SEOHOST sp. z o.o., ul. Obornicka 330, 60-689 Poznań, Poland. Its infrastructure chain may involve DATASPACE P.S.A., EXEA S.A. and OVH sp. z o.o. in Poland, and SEOHOST support may involve Quality Unit, s. r. o. in Slovakia. Access depends on the service or support case. Processing is subject to the requirements of GDPR Article 28.
After advertising-cookie consent, measurement data may be received by Google Ireland Limited and Google entities providing the service. The QR-generation library is served locally; the site does not fetch Google Fonts. Following a QR destination takes you to the owner’s chosen website, which has its own privacy rules.
Authorised service-maintenance staff, legal or accounting advisers when needed, and public authorities where required by law may have access. We do not sell the account database. On request, we provide details of current recipients and relevant safeguards.
6. Cookies and browser storage
Session: an essential PHP session cookie maintains login and protects forms. It is a session cookie, normally until the browser closes; session restoration also depends on browser settings. Server-side sessions are cleaned up according to hosting configuration. Signing out invalidates the current session.
Cookie choice: qr_consent in a cookie and local storage records consent or refusal and the choice date. The choice is valid for 180 days; a technical local-storage entry may remain until site data is cleared, but consent is requested again after expiry. This record remembers your decision and is not advertising.
Google Ads: the advertising tag is not loaded before consent. After consent, Google may receive IP addresses, browser identifiers, page URLs, visit sources and conversion events such as registration. We do not include email addresses or menu content in the event. Cookies named _gcl_* and other Google cookies may be stored depending on service settings; see Google’s cookie documentation.
Change consent or refusal through “Cookie settings” in the footer. Withdrawal stops further tag loading after the page reloads and does not affect the lawfulness of earlier processing. You can remove remaining Google cookies in your browser. Blocking essential cookies may prevent login; rejecting advertising does not restrict the service.
7. Transfers outside the EEA
Google and Stripe/Link services may involve processing outside the European Economic Area, including the USA. Each transfer requires a valid GDPR Chapter V basis: an applicable European Commission adequacy decision (for the USA, only for a certified recipient covered by it), or standard contractual clauses with a transfer assessment and necessary supplementary safeguards.
Using a US provider alone does not establish a lawful transfer basis. You may request information about safeguards, a copy or where to access them. See the Google Privacy Policy and Stripe Privacy Policy for their own practices.
8. Retention and backups
Account, code and menu data is kept while the account operates, until an item is deleted or an account-deletion request is fulfilled. Ending Pro alone does not delete content. Scan history is kept for the lifetime of the code; 7 and 30 days are chart windows, not event-deletion deadlines.
A password-reset token is valid for one hour and is removed after use; expiry alone does not instantly delete the record. An email-verification token is removed after confirmation. Login, registration and reset counters use short windows; records older than 24 hours are deleted the next time the rate-limiting mechanism runs.
Correspondence and case records are kept while a matter is handled, then only as necessary for legal obligations or claims until the relevant limitation period ends. Tax records, where applicable to us, are retained for the statutory period, generally 5 years from the end of the year in which the tax payment deadline fell. Stripe may have its own legal retention obligations.
Technical logs and backups follow SEOHOST infrastructure retention cycles. A backup may temporarily contain data deleted from the live database; it is not reused, and completed deletion requests are honoured when restoring. The hosting agreement provides for deletion of the last backup no later than 6 months after the SEOHOST contract ends. That period concerns the end of hosting, not automatic 6-month retention of every deleted account. Contact us for the current backup and log cycle.
9. Your rights and data requests
Within GDPR limits, you may request access and a copy, correction, deletion or restriction, and portability of data supplied under consent or contract and processed automatically. You may object to legitimate-interest processing on grounds relating to your particular situation, and to direct marketing at any time. Consent can be withdrawn without affecting earlier lawful processing.
Write to the contact in section 1. We respond without undue delay, normally within one month; complex cases may require a two-month extension, notified within the first month. If identity is reasonably in doubt, we request only the information needed to verify it. Account and content deletion is handled on verified email request; Pro’s CSV export covers scan history only and is not a full response to a data-access request.
You may complain to the President of Poland’s Personal Data Protection Office — see uodo.gov.pl — or another competent EEA supervisory authority. Contacting us first is not a condition for complaining.
10. Security and automation
We use HTTPS, password hashing, CSRF protection, ownership checks for edited resources and authentication rate limits. Backups are handled by hosting infrastructure. This does not guarantee that incidents cannot occur. We do not make solely automated profiling decisions producing legal or similarly significant effects under GDPR Article 22.
11. Required data, messages and changes
Providing email and password is voluntary but necessary for an account; billing details required at checkout are necessary to purchase. Verification, password, contract and account-service messages are used to provide the service. Accepting the terms or reading this policy does not replace separate marketing consent. We update this policy when processing changes and date each version. Material changes are notified appropriately; a new policy does not replace consent required for a new purpose.