joviapp-kellnerhilfe

Pro Privacy Notice for the JoVi App

Legal version: 2026-06-06.pro.v1 Approved for app version: 2.1.8+261601438

Version date: 06.06.2026

1. Purpose of This Pro Privacy Notice

This Pro Privacy Notice supplements the general Privacy Policy and the Cloud Privacy Notice of the JoVi App for paid Pro features, team features, and subscriptions. It applies in particular to activation, entitlement verification, team operation, synchronization, and the related server-side processing.

2. Categories of Processed Data

When Pro features are used, the following data may in particular be processed:

• product and plan identifiers of the selected subscription
• purchase- or transaction-related identifiers
• submitted server-side verification data as well as receipt, token, or other proof data used for entitlement verification
• status information regarding activation, renewal, expiry, cancellation, or restoration
• assignment of an entitlement to a user account or device
• team and membership data such as team name, roles, status, and join or leave timestamps
• jointly edited menu, order, statistics, and activity data in the team context
• technical entitlement, role, and synchronization data for collaborative Pro features
• technical validation and logging data for entitlement management and abuse prevention, including in particular submission, processing, and validation timestamps, processing states, error categories, error details, and platform or source information

3. Purposes of Processing

Processing is carried out in particular in order to:

• unlock paid Pro services
• technically verify purchase receipts or entitlements
• keep subscription status up to date
• manage teams, roles, and permissions in the Pro context
• synchronize shared working states between Pro members
• handle support, abuse, or reversal cases
• retain records for entitlement management and secure product delivery

4. Recipients and Platform Context

For Pro features, data may in particular be processed with the following recipients or service categories where technically necessary for purchase handling, entitlement verification, team operation, synchronization, or abuse prevention:

• the relevant app store or platform provider, in particular Google Play or the Apple App Store, for purchase handling, subscription management, restoration, and store-side status information
• the Firebase backend services used by the app and provided by Google LLC, in particular Firebase Authentication, Cloud Firestore, and Cloud Functions, for account assignment, entitlement verification, team management, synchronization, and server-side validation
• technical verification and infrastructure contexts where purchase receipts, tokens, receipt data, or comparable proof records are processed and checked on the server side

In this context, product and plan identifiers, purchase-related identifiers, receipt or token data, account assignments, team and role data, synchronization data, technical validation logs, and activation, renewal, expiry, or restoration information may in particular be processed.

Depending on the app store, platform, backend service, and technical infrastructure, processing may also take place outside the European Union or the European Economic Area. The concrete data processing and any third-country transfers are governed by the privacy information and contractual terms of the respective providers involved.

5. Legal Bases

Processing is carried out in particular for the performance of the paid usage relationship, for subscription handling and entitlement verification, for compliance with legal obligations, and for ensuring secure operation. Where individual Pro-related processing steps go beyond what is strictly necessary for the paid usage relationship and depend on optional cloud-supported use, processing may additionally be based on your consent or your deliberate activation and use of those optional functions.

6. Storage Period

Pro-related data are stored only for as long as necessary for activation, proof, entitlement verification, team operation, synchronization, support, abuse prevention, legal obligations, or billing-related documentation.

According to the currently implemented technical setup, the following retention periods and deletion logics apply in particular:

• active teams are generally closed automatically on the server side 42 days after their creation
• closed teams are generally deleted recursively 30 days after the closure timestamp
• when a team is closed, open join requests are deleted and memberships are moved into an archived state
• when a team is deleted permanently, the related membership documents and the team including its substructures are deleted
• failed or technically suspicious receipt records are generally retained for up to 90 days after processing
• successfully processed receipt records are generally retained for up to 180 days after the relevant reference point; for active or future-ending subscriptions, that reference point is generally the subscription expiry date, otherwise the processing or validation time
• technical purchase-token or comparable mapping data are generally retained for up to 365 days after the last relevant activity or inactive marking
• inactive user accounts without an active Pro subscription may generally be deleted if no relevant activity has been detected for at least 12 months; an additional technical safety buffer of 7 days applies to expired subscriptions

The decisive factor always remains the technical necessity of the respective data type. Where legal obligations, ongoing disputes, abuse prevention, or security interests require longer retention, storage may exceed these periods in individual cases.

7. Consequences of Non-Acceptance

If you do not accept this Pro Privacy Notice, paid Pro features, team features, and other collaborative Pro services cannot be activated or locally confirmed on this device. Free base use of the app remains unaffected.

To the extent that individual Pro-related processing operations are based on your consent or on your deliberate use of optional functions, you may withdraw such consent at any time with effect for the future by signing out in the app and no longer using Pro or cloud features. This ends future consent-based use, but does not automatically terminate every other permissible processing activity connected to an existing or already completed Pro usage relationship.

This does not affect processing that remains necessary for contract performance, billing, evidentiary records, entitlement verification, security purposes, abuse prevention, statutory retention obligations, or the technical handling of existing team and entitlement states.

8. Relationship to Other Privacy Notices

This Pro Privacy Notice specifies the general Privacy Policy for paid Pro features. Where cloud features are also used, the Cloud Privacy Notice applies in addition.