Back to account
EN

Aula Club

Privacy policy

Text version: 15. 10. 2026. The benefits table shows the current programme settings.

Draft for completion by the operator. Before announcing an effective date, suppliers and any transfers outside the EEA, deletion and backup periods, and consistency between discounts and till settings must be confirmed. This notice is neither consent to processing nor a substitute for the duty to provide information.

1. Who is responsible for your data

Programme operator and personal data controller
Red 55 Production s.r.o.
Company registration number
01739506
Registered office and postal address for requests
Mikulova 1572/13, Chodov, 149 00 Praha 4
Aula Café premises
Kamýcká 129, 165 00 Praha-Suchdol
Contact email
info@aulacafe.cz

The operator identified above is the controller of data used for Aula Club and related communication. Send privacy requests to the listed email or by post to the registered office. This notice describes processing under Regulation (EU) 2016/679 (GDPR). Acknowledging it during registration is not blanket consent: each purpose has its own legal basis.

2. What data we use

You provide your first and last name, email, country, optional date of birth, language and communication preferences, messages and feedback, and records of accepting terms and marketing consent. Access records include a password hash, session data and, depending on your chosen security, two-factor authentication information or passkey public keys and identifiers. Your device does not send us the biometric data used to unlock a passkey.

Loyverse supplies the customer identifier and card code, assigned receipts including items, prices, times, discounts and returns, spend and loyalty balances. App operation generates points, tier, reward, invitation, message-delivery and read records, IP addresses, browser details and security logs. For enabled push notifications we store the subscription endpoint and technical keys. Related payment records may include a transaction identifier and masked or pseudonymous card identifier from the payment provider. Club does not request a full card number or CVC.

3. Purposes and legal bases

Account management, till identification, calculating and redeeming benefits, purchase history, membership requests and related operational communication are necessary to perform the membership contract (GDPR Article 6(1)(b)). The date of birth enables an optional birthday benefit; membership and other benefits work without it. An account cannot operate without basic registration and access details. Country is currently mandatory in the form and used to understand the membership's composition; it is not anonymous while linked to an account.

Security, fraud prevention, evidence of membership, protection of legal rights and proportionate internal operational analysis rely on the controller's legitimate interests (Article 6(1)(f)), subject to necessity and impact on your rights. Legally required accounting and tax records and cooperation with authorised bodies rely on legal obligations (point (c)). Voluntary marketing consent falls under point (a). Necessary pre-contract enquiries are also processed to take steps at your request.

4. Voluntary marketing and notifications

Consent to offers and news is not a membership condition. It covers Aula Café's own offers in Club and selected electronic channels, including enabled push notifications. Withdraw it at any time, free of charge, in your profile or by contacting the controller. Withdrawal does not affect earlier lawful processing or ordinary membership benefits. Browser notification permission is not itself marketing consent.

Essential security and contractual messages, such as password recovery or changes to terms, are separate from marketing. Opening-hours alerts and push categories can be configured in your profile. Browser permission can also be revoked on the device. Necessary records of consent and withdrawal may be retained to demonstrate compliance and respect your refusal of further marketing.

5. Invitations and shared receipts

Registering through an invitation links your account to the inviter. They see your first and last name, invitation status and aggregate spend recorded towards activation. This view does not show individual purchase items; spend ordinarily stops updating after activation. The link enables the referral and verifies the reward. Register without an invitation if you do not want a link; contact the controller if one already exists.

If you generate a digital receipt link, anyone who obtains it can view the shared content without signing in. Sharing is optional and may disclose purchase time, items, value and benefits. New links currently expire after 30 days; existing links keep their individual expiry. Do not share links publicly unless you intend the content to be public.

6. Who may access data

Hosting is provided by Hukot.net, operated by SecurityNet.cz s.r.o., company number 27501418. Authorised staff and, as necessary, application maintenance and security, email and push suppliers may access data. Loyverse processes customer and till records to link membership to purchases. Push notifications use infrastructure provided by the browser or device provider. A payment provider, such as SumUp for applicable payments, processes payment data according to its role and legal duties.

Accountants and professional advisers subject to confidentiality, and public authorities with legal powers, may receive data. Suppliers acting as processors require an appropriate GDPR Article 28 agreement. Independent controllers provide their own privacy information. When AI sales analysis is enabled, the app sends aggregate business metrics, not a list of member accounts; customer personal data must not be entered in free-text instructions. We do not sell data. The specific outgoing email supplier must be confirmed before this version is issued.

7. Transfers outside the European Economic Area

Cloud till, communication and other external services may use infrastructure outside the EEA. We cannot claim all data stays in the EU without checking actual contracts and subprocessors. Transfers may only take place in accordance with GDPR Chapter V, for example under an applicable European Commission adequacy decision or standard contractual clauses with any necessary supplementary measures.

Before issuing the final version, the operator will specify actual destination countries and safeguards used by its suppliers. Ask the controller for information about a particular transfer and how to obtain a copy of relevant safeguards, with commercially sensitive details redacted where necessary. This information does not itself replace contractual or technical safeguards.

8. How long data is retained

Data needed for the account and membership-benefit history is retained for the duration of membership. That purpose ends with membership; deletion or anonymisation must also address linked customer records with processors unless a separate legal basis justifies retention. Deleting the app account does not itself guarantee immediate removal of the Loyverse customer record or legally required documents.

Document retention depends on the legal category and when the statutory period begins. VAT documents are generally kept for 10 years and selected accounting records for 5 years; other categories have different rules. Evidence necessary to protect legal claims is kept for the relevant limitation period and any ongoing proceedings, not automatically all member data. Technical logs and backups should be limited to what security and recovery require. The operator must verify and specify actual retention and backup cycles, including consent evidence, before issuing the final version; this is not a claim that automatic deletion is already implemented.

For standard web hosting, Hukot.net states that backups are retained for up to 30 days depending on the plan, using backup infrastructure in the Czech Republic with possible redundancy in France and Germany. VPS backup scope depends on the service ordered and its settings. This does not describe the operator’s own copies or other suppliers’ backups; the actual contracted plan must be verified.

Hukot.net — backup scope

9. Cookies, device storage and external content

Technical cookies and browser storage support login, form security, language preferences and selected app features. The installed PWA stores app files and offline text; this does not guarantee that all pages or personal data are available offline. You can clear device storage in its settings, which may remove logins and preferences.

Depending on configuration, the website may load Google Analytics, Google Tag Manager and an embedded map. External content may transmit IP and device information to the provider and store other identifiers. Analytics or marketing storage and device access requiring consent must not start before consent, and refusal must be as easy as acceptance. Registration or acknowledging this notice does not provide that consent. The operator must implement suitable consent management before enabling these services; this text does not implement it.

10. Automated calculations and security

The system automatically totals spend and AP, assigns tiers, calculates discounts and checks bonus eligibility. Programme terms explain the rules and publish current thresholds. This processes purchasing behaviour for loyalty benefits, not creditworthiness. If you believe data or a calculation is wrong, you can request human review and correction.

Club does not implement solely automated decisions producing legal or similarly significant effects within GDPR Article 22. Access is restricted by roles, passwords are hashed, and passkeys or two-factor authentication can protect access. No online system can be described as absolutely secure. For personal data breaches, the controller follows statutory duties, including notifying authorities and affected individuals where GDPR conditions are met.

11. Your rights

Subject to GDPR conditions, you may request access and a copy, correction or completion, erasure, restriction and portability of data you supplied that is automatically processed on consent or contract grounds. Erasure is not absolute, particularly where data must be kept for a legal obligation or establishing, exercising or defending legal claims.

You may object to processing based on legitimate interests on grounds relating to your situation. You may object to direct marketing and related profiling at any time; we then stop using data for that purpose. You may withdraw consent at any time. An incorrect birth date can be corrected through the controller even when the profile field is locked. Exercising rights is not grounds for a penalty, although restricting necessary data may prevent continued membership.

12. Exercising rights and making a complaint

Contact the controller using the details above or write to its registered office. Explain your request and how we can contact you safely. Do not send passwords, recovery codes or full payment card details. Reasonable doubts about identity may require proportionate verification; we do not automatically demand an ID copy from every requester.

We respond without undue delay, normally within one month. Complexity or the number of requests may justify an extension of up to two further months; we inform you of the extension and reasons within the first month. Requests are normally free, subject to GDPR exceptions for manifestly unfounded or excessive requests. You may complain to the Czech Office for Personal Data Protection, Pplk. Sochora 27, 170 00 Prague 7, or a competent supervisory authority in another Member State, and seek judicial protection.

Office for Personal Data Protection — contact and submissions

13. Changes to this information

Current information is available without signing in, at registration and in your member profile. Material changes to purposes, recipients or other processing circumstances will be communicated appropriately before implementation. Changing this text alone cannot authorise a new purpose requiring a new legal basis or consent.

The date above identifies this text version, not the time of your consent. Operator identity comes from operator settings and the contact email from website settings. Information about actual suppliers, transfers and retention must reflect real operation, not merely the software's default capabilities.