Privacy policy

1. Overview and controller

This Privacy policy explains how personal data is processed on playtippr.de and in the Tippr apps for iPhone, iPad and Android. The controller is Yannik Muth, Leo-Leistikow-Allee 4, 22081 Hamburg, Germany, email hallo@playtippr.de.

We process data required for operation, security, communication and the functions described below. The main legal bases are performance of a contract, consent, legal obligations and legitimate interests under Article 6 GDPR.

2. Website hosting by Cloudflare

The website is delivered as a Cloudflare Worker through the network of Cloudflare, Inc., 101 Townsend St, San Francisco, CA 94107, USA. Cloudflare receives technical connection data for Website hosting, content delivery, TLS encryption and protection against abusive requests.

This may include the IP address, requested URL, time, browser and device details, HTTP headers, security data and error data. The legal basis is Article 6(1)(f) GDPR: our legitimate interest in a secure, fast and stable website. We have a data processing agreement with Cloudflare. Transfers to the United States rely, as applicable, on the EU-US Data Privacy Framework or EU Standard Contractual Clauses. Details: cloudflare.com/privacypolicy.

3. Contact and handling of requests

If you contact us by email, we process the sender address, content, time and metadata needed to respond. The legal basis is Article 6(1)(b) GDPR for contractual matters and otherwise Article 6(1)(f) GDPR. We delete correspondence when it is no longer needed and no legal duty or claim requires retention.

Our mailbox hallo@playtippr.de is operated by Fastmail Pty Ltd, PO Box 234, Collins Street West, VIC 8007, Australia. Fastmail receives, stores and sends our emails and processes the sender address, content, attachments and metadata of the messages. The legal basis is Article 6(1)(f) GDPR: our legitimate interest in a secure and reliable mailbox. According to Fastmail, it also processes data outside the EU, including in Australia and the United States; according to Fastmail, backups and logs are kept in the United States. Fastmail states that it safeguards transfers from the EU with Standard Contractual Clauses. Details: fastmail.com/about/privacy and fastmail.com/policies/dpa.

We track bug reports, requests and enquiries from emails, from in-app feedback (section 10) and from public app store reviews in Linear, a service of Linear Orbit, Inc., 2261 Market St STE 10632, San Francisco, CA 94114, USA. Where needed for handling, we transfer the text of the request, the display name or name, the date and internal identifiers of the post, email or review. The legal basis is Article 6(1)(f) GDPR: our legitimate interest in complete and traceable handling. Linear also processes data in the United States. Under Linear's terms of service, its data processing agreement applies, which includes EU Standard Contractual Clauses. Details: linear.app/privacy and linear.app/dpa.

AI-assisted handling

AI services from Anthropic (Claude) and Anysphere (Cursor Grok Bot) help us assess support cases and prepare replies. This may involve processing the message text needed for the case, display name, technical details and handling status. Grok Bot receives shortened case cards with email addresses, phone numbers and image content removed. Message text and display names may still contain personal information. A reply is sent only after our individual approval.

The legal basis is Article 6(1)(b) GDPR where handling the request is necessary to perform the contract, and otherwise Article 6(1)(f) GDPR. Our legitimate interests are reliable request handling and fixing app errors. These providers may also process data outside the EU or EEA, particularly in the United States. Information about their processing and international transfers: Anthropic Privacy Policy and Cursor Privacy Policy.

4. Account and app use

Depending on how you use Tippr, we process your email address, authentication data, internal account ID, display name, optional profile image and favourite team, predictions, points, statistics, awards, group memberships, group content, chat messages, comments, push token, platform, app version and technical error data.

The legal basis is Article 6(1)(b) GDPR. Core data is stored with Supabase as our processor in an EU data centre in Ireland. Our contracting party is Supabase Pte. Ltd. in Singapore; Supabase, Inc. in the United States also provides technical support and operational services. Supabase may transfer data to Singapore and the United States for these purposes; its data processing agreement includes EU Standard Contractual Clauses. Details: supabase.com/privacy and supabase.com/legal/dpa.

Tippr League

In the app you automatically take part in the Tippr League, a weekly table with up to 17 other predictors who do not have to be in your groups. They see your display name, your jersey (colours and pattern; unless you choose your own, the home kit of your favourite team; never your profile picture), your position, your league level, your weekly points, the number of your predictions and your predictor card with figures we calculate from your scored predictions. They do not see your groups, individual predictions or chat messages. For this we store your league, position, points and promotion or relegation for each week for as long as your account exists.

The legal basis is Article 6(1)(f) GDPR: our legitimate interest in offering a competition beyond your own groups. You can object at any time by turning off “Play in the league” in the app under Profile, Settings. After that, every league table, including those of past weeks, shows only “No longer playing” instead of your name and jersey. Other predictors can hide or report your entry for themselves; we review reports in line with the terms of use.

Tippr in your browser

The Tippr web app on playtippr.de keeps your sign-in session, your chosen language and drafts and display states, such as a group you started creating or hints you have already seen, in your browser's storage (local storage and a language cookie). These entries are strictly necessary for the functions you use (Section 25(2) No. 2 of the German TDDDG) and are not used for advertising. The sign-in session ends when you sign out; you can delete the other entries in your browser at any time. Storage for browser notifications and advertising consent is described in sections 5 and 7.

Predicting on the website without an account

If you make a prediction on playtippr.de without an account, we create an anonymous account with Supabase for it. It contains no email address and no name, only an internal account ID, your prediction and a separate round that holds only this prediction. The website keeps the sign-in for this account in your browser storage (local storage). If you do not take the prediction over into the app, we delete the account, round and prediction automatically after 30 days, and likewise such an account that holds no round.

Handover from the website to the app

So that a prediction, a draft round or an invitation survives the trip through the App Store or Google Play into the app, we create a handover when you tap “Continue in the app” or “Send to your phone”. It contains only what you entered on the website yourself (predictions with match and score, round name, display name or invitation code), plus language, device type, the page and campaign you came from, and whether you used the button or the QR code. It is linked to the anonymous account described above. It can be reached through a random code in the link; our database stores only a hash of this code. Like every address you open, the full link is also seen by our hosting provider (section 2). The link contains no names, email addresses or account data, but for a prediction it does contain the match, score and kick-off time. Anyone who knows the link can view the handover on playtippr.de until it is taken over into the app.

On iPhone, the website copies the link to the clipboard when you tap the button so that the app can pick it up on first launch; iOS may ask you whether Tippr may read the clipboard. On Android, the code is part of the Play Store link, and Google Play passes it to the app on installation. When you open the app, the handover is assigned to your account, the predictions are added to your round, and the account records as its origin that you came from the website, together with the campaign, if no origin has been recorded yet.

A handover is valid for seven days. Handovers that are not taken over are deleted when they expire, those taken over 30 days later. If you choose on your phone to continue in the browser without the app, the website remembers this choice in your browser storage until you undo it with “Use the app after all”. The legal basis is Article 6(1)(b) GDPR, because you want to keep using Tippr with your entries in the app; for the origin details it is Article 6(1)(f) GDPR, our legitimate interest in knowing which pages lead to the app.

5. Other services

Apple Sign In or Google OAuth processes data required for authentication. Apple Push Notification Service or Firebase Cloud Messaging processes device push tokens when notifications are enabled. API-FOOTBALL supplies fixtures and results; we do not send it account data, predictions or group data.

Browser notifications in the web app

In the Tippr web app on playtippr.de you can switch on browser notifications under Settings, “Notifications” and choose the occasions individually. Only after your click does the browser ask for permission and register a service worker for the web app. We then store the delivery address generated by the browser with its keys, a random identifier for this installation, language, time zone, the occasions you chose, the version of your consent and the times of registration, last renewal and withdrawal. Your browser keeps the link to your account in its local storage.

Notifications are delivered through your browser's push service, depending on the browser by Google (Firebase Cloud Messaging, for example for Chrome), Mozilla (Firefox) or Apple (Safari). The push service receives the delivery address, technical connection data and the content of the notification in encrypted form only. Private messages appear in the notification only with a generic text. These providers may also process data in the United States.

The legal basis is your consent under Article 6(1)(a) GDPR and Section 25(1) TDDDG. You can withdraw it at any time in Settings or through your browser's permissions; when you sign out, the web app removes this browser's registration. We delete withdrawn or invalid registrations after 30 days, as well as registrations that have not been renewed for 180 days.

App versions still in circulation may send product events and a random installation identifier to TelemetryDeck in parallel with our own analytics. According to the provider, processing takes place in Germany and IP addresses are not stored. This service is being discontinued. Details: telemetrydeck.com/privacy.

Email delivery with Brevo

We send emails from the app and website through Brevo, a service of Sendinblue SAS, 17 rue Salneuve, 75017 Paris, France. These include:

• Sign-in emails: confirming registration, sign-in links, password resets and changes of email address. The legal basis is Article 6(1)(b) GDPR.
• Prediction reminders by email if you have switched them on in the app or in the web app on playtippr.de; they are off by default. Prediction reminders chosen in the web app are only sent by email if you cannot receive a push notification on a device or in the browser. The legal basis is your consent under Article 6(1)(a) GDPR.
• Further emails that you can switch on individually in the web app on playtippr.de: result summaries, mentions in the group chat, reminders and messages from group administrators, and reminders about missing special predictions. All of them are off by default. The legal basis is your consent under Article 6(1)(a) GDPR.
• Private messages from group administrators to you, in full. These emails are on by default. The legal basis is Article 6(1)(b) GDPR because they are part of the group function.

Brevo processes your email address, the content of the email, for emails from a group also the sender's display name and the group name, and sending and delivery data. You can switch off these notifications in the app's notification settings under “Email notifications” or in the web app under Settings, “Notifications”, or unsubscribe using the link in each of these emails.

If you reply to an email from a group administrator, Brevo receives the reply. We initially store every email received through Brevo unchanged as a raw copy with sender, subject and content. We delete this raw copy after 90 days. If the reply comes from your account address, we deliver the reply text, without the recognisably quoted history, to the group administrator as a message in the app. A delivered reply remains as a message in the group inbox for as long as it exists there. The legal basis is Article 6(1)(b) GDPR.

According to its privacy policy, Brevo sends emails on behalf of its customers as a processor under its Data Processing Agreement. Details: brevo.com/legal/privacypolicy.

Branded prediction games

Prediction games that we operate for companies or brands at their own address on playtippr.de, such as playtippr.de/brandingpeople, have their own privacy policy linked there, which sets out who is responsible for processing. We also send their registration, confirmation and notification emails through Brevo, using a sender address under @playtippr.de in the brand's name.

Newsletter

We no longer offer a newsletter. We deleted the entries from the former form in November 2026. We no longer collect data for this purpose.

6. Usage measurement and technical operational data

Our own product analytics in the app and website is disabled on the server. Without an explicit Yes, we do not analyse your screens, actions, sessions, flows or displayed experiment variants for product analytics. You can use the app without this consent. The absence of an objection or an old objection setting is not a Yes. This statement applies only to our own product analytics and does not describe advertising in the app and on the website (section 7). The identifier-free reach count on playtippr.de, described in the subsection “Reach counting on playtippr.de without cookies”, is separate.

Messwerk receives only six narrowly limited technical app events: auth.failed, group_header.load_failed, match.list_empty, paywall.offerings_failed, perf.load and error.occurred. They serve to detect sign-in, loading and offer failures, empty match lists, technical loading times and errors. They contain only restricted technical attributes, such as platform, app version, error category or duration band. Reports contain no account, session, device or daily changing identifier. A random identifier for each event is used solely to recognise duplicate submissions and is not used to link usage activity.

The previous server-side counts of invitation, group and handover links are also disabled. Functional accounts, links and handovers in section 4 remain separate. Product analytics events sent by the browser are not accepted; there is no daily changing analytics identifier. We count store redirects and button presses on the public pages only as described in the following subsection.

The legal basis for these narrowly limited operational data is Article 6(1)(f) GDPR: our legitimate interest in error detection, stability and capacity planning. This does not permit general click or screen tracking.

Reach counting on playtippr.de without cookies

On the public pages of playtippr.de we count how often a page is viewed and how often a button leading to the App Store, Google Play, the app or to creating a prediction group is pressed there. For each day we store only a total per combination of: page path without parameters, language version, device class (phone, tablet or computer), type of origin of the visit (for example Google, another search engine, direct or within playtippr.de) and, for button presses, the target and position of the button. A move from a public page into the web app at /tippspiel is counted for the page it started from. Screens of the web app itself and invitation, group and handover links are not counted. If our download link is opened without one of our pages before it (for example via a QR code or from another website), we count it without a page path, only as “direct” or “external”.

For this we store no IP address, no time of day, no full browser or referrer details, no cookies and no identifier. Nothing is stored on or read from your device for this purpose. The values come from the data your browser sends with every page request anyway; when such a button is pressed, the page additionally sends a short message with the target and position of the button. Individual visits or visitors cannot be traced from the daily totals. Recognisable programs and search engine crawlers are not counted. If your browser sends the “Global Privacy Control” or “Do Not Track” signal, we do not count your visits.

The purpose is to see which pages lead to the app or to a prediction group and to improve the website accordingly. The legal basis is Article 6(1)(f) GDPR: our legitimate interest in an effective website measured sparingly. The daily totals are held by our processor Supabase (EU data centre in Ireland) and deleted after 395 days.

Server-side facts and objection

Account, group, prediction, purchase, push, invitation and calendar data necessary to provide the app are separate (sections 4, 5 and 8). Additional analysis of minimised server facts derived from these data uses Article 6(1)(f) GDPR to assess usage, reliability and operations. This does not permit copying chat text, specific prediction content, names, email addresses or full links into analytics. Derived account or group identifiers and personal daily values remain personal data.

You may object at any time to additional server-fact analysis and operational data processing based on legitimate interests, without giving a reason, by emailing hallo@playtippr.de, preferably from your account address if you have one. We process the request within one month. Processing necessary for the app function you requested remains separate. For reports without identifiers, we do not collect additional identity solely to associate them retrospectively. Analysis uses groups of at least five and additional safeguards; this minimum size alone does not make data anonymous. Raw data is not sent to external AI services for unrestricted analysis. Measurement is not used for personalised advertising or automated decisions with legal or similarly significant effects.

Data and recipients

Our own measurement contains no chat messages, keystrokes, screen recordings, contacts, precise locations or advertising identifiers. IP addresses are technically visible during network transmission; Messwerk does not store them as measurement data or derive a country or substitute identifier from them. A coarse language/region value may come from the language setting. Hosting and other services in sections 2 to 5 and Google in section 7 are separate.

We use hosting with Hetzner in Germany for our own Messwerk processing; existing Tippr core data and historical analytics holdings remain with Supabase. This does not mean that every provider in this policy processes exclusively in Germany or without third-country involvement. The respective provider and transfer disclosures still apply.

Retention and historical holdings

Fixed maximum periods apply to Messwerk from the relevant event or activity day: 90 days for technical operational data, 395 days for standard measurement data and 730 days for personal daily values. A retention period does not authorise additional collection not described here. Irreversibly anonymous aggregates may remain longer; pseudonymous daily values do not qualify.

These Messwerk periods do not mean that retention of the historical Supabase holdings has already changed. The existing routine provides 14 days for technical raw events and 120 days for other raw events; separate daily-value tables are not automatically covered. Deletion and objection must also reach associated identifiers and derived daily values and be respected during restoration. General account-deletion rules are in section 11.

Performance measurement in the Android app

To find and fix stutter and long loading times, the Android app measures technical performance values from version 1.5.7 onwards: start-up and loading times, tab switches, duration and result of data requests, frame times and the share of janky or frozen frames per screen. During longer stalls it also records a limited number of technical code positions (class, method, line), without error messages or screen content. In addition, it records coarse device details: app and Android version, manufacturer, memory, processor and refresh-rate class, graphics level, network type, and temperature and battery-saver state. The device model is only sent if it is widespread among our users; otherwise it is recorded as “other”.

Performance reports contain no account, installation, device or advertising identifier, no predictions, group or chat content, no order of visited screens and no time of day, only the date. We do not link them to accounts or to the rest of our product analytics. The IP address is technically visible during transmission. It is not stored in the performance database but appears in the access logs of our processor Supabase (EU data centre in Ireland), which are deleted after 7 days. We delete performance reports after 90 days at the latest.

In narrowly limited individual cases, the app can additionally send a cleaned system trace, only on Android 15 or later and only over Wi-Fi. This function is switched off by default. Before sending, the app removes exact time references, process details, paths and freely chosen labels. Such files are kept in non-public storage and deleted after 30 days at the latest.

The legal basis here is also Article 6(1)(f) GDPR: our legitimate interest in a smooth and stable app. An objection to product analytics also applies to performance measurement: the app then deletes reports not yet sent and stops measuring.

7. Advertising with Google AdMob and Google AdSense

The free apps may display ads supplied by Google AdMob, and the web app and the prediction pages on playtippr.de (predictions, leagues, matchdays, matches and the tip helper) may display ads supplied by Google AdSense. Both services are provided by Google Ireland Limited, Gordon House, Barrow Street, Dublin 4, Ireland. The rest of playtippr.de shows no ads and loads no advertising scripts. An active Tippr Pro subscription removes ads from the apps and the web app. The prediction pages show no ads while you are signed in to a Tippr account in that browser.

Google AdMob in the apps

According to Google, the Google Mobile Ads SDK may collect or share IP address and coarse location, product interactions and ad events, diagnostics, device identifiers and account identifiers for advertising, analytics and fraud prevention. On Android this can include the advertising ID and app set ID where available. Tippr does not request App Tracking Transparency on iOS, so AdMob does not receive an IDFA there. This does not describe Android.

Google may process data for its own purposes. Sources: Google Mobile Ads SDK data disclosure and Google Privacy Policy.

We use Google's User Messaging Platform for consent. The legal basis for processing that requires consent is Article 6(1)(a) GDPR. You can change the decision in the app under Profile, Settings, Privacy and “Manage advertising consent”. Withdrawal applies for the future. Google states that applicable adequacy decisions and Standard Contractual Clauses protect transfers to the United States.

Google AdSense in the web app and on the prediction pages

Before any ad loads in the web app or on a prediction page, Google's consent platform (Privacy & messaging, based on the IAB Europe Transparency and Consent Framework) asks for your consent. You can refuse as easily as you can agree, and the web app and the predictions remain fully usable without consent. Without your consent we show no ads there, not even non-personalised ones.

With your consent, Google and the partners named in the dialog may store and read cookies and similar technologies on your device. This may involve processing your IP address, browser and device details, the page you visit, ad interactions and cookie identifiers to deliver, personalise and measure ads and to prevent fraud. The consent platform stores your decision in a cookie on playtippr.de; this is necessary so that your choice is respected (Section 25(2) No. 2 TDDDG).

The legal basis is your consent under Article 6(1)(a) GDPR and Section 25(1) TDDDG. You can change or withdraw it at any time with effect for the future: in the web app under Settings, “Manage advertising consent”, and on the prediction pages via “Change consent” above each ad or “Change ad consent” in the footer. Ads that have already loaded are then removed. Google also processes data for its own purposes as an independent controller and may transfer it to the United States; according to Google, it relies on adequacy decisions and Standard Contractual Clauses. Details: How Google uses information from sites that use its services and Google Privacy Policy.

8. Tippr Pro, store purchases, Stripe and RevenueCat

Purchases in the app are handled by the Apple App Store or Google Play. We do not receive card or bank details or a billing address for them.

For purchases on playtippr.de, we are the seller and responsible for handling the purchase (section 1). Checkout, subscription management, receipt emails and the customer portal are provided by RevenueCat Billing from RevenueCat (see below); payments are processed by Stripe.

The payment provider is Stripe; for customers in the European Economic Area, the responsible entity is Stripe Payments Europe, Limited, 1 Grand Canal Street Lower, Grand Canal Dock, Dublin, D02 H210, Ireland. You enter your payment details (such as card number, expiry date and security code, or the details of the chosen payment method) in a Stripe payment field at checkout; they go directly to Stripe, not to us and not to RevenueCat. Stripe also receives the amount, currency, your email address, country and postcode where requested, IP address and device and browser data. Stripe executes the payment on our behalf. To detect and prevent fraud and to meet its own legal obligations, such as anti-money laundering rules, Stripe processes this data as an independent controller. Stripe may transfer data to the United States and relies on the EU-U.S. Data Privacy Framework and EU Standard Contractual Clauses for this. In the Stripe account we see email address, country, product, amount, payment method type with the last four digits and transaction data for support, refunds and accounting; we do not receive full card or bank details. Details: Stripe privacy policy and Stripe Privacy Center (which Stripe entity is responsible for what).

For app purchases, Apple and Google remain responsible for payment, receipts, refunds and their statutory retention obligations. For purchases on playtippr.de, we keep receipts and accounting data (email address, product, amount, date, payment method and transaction ID) for as long as German tax and commercial law requires: accounting vouchers for eight years, books and records for ten years (section 147 AO, section 257 HGB).

We use RevenueCat, Inc., 1032 E Brandon Blvd #3003, Brandon, FL 33511, USA, as a processor to verify and manage subscription status and, for purchases on playtippr.de, also for checkout, receipt emails and the customer portal (RevenueCat Billing). RevenueCat receives the pseudonymous Tippr account ID, product and subscription status, purchase and expiry times, store country and limited technical offer attributes. We do not send it your name, predictions or groups, and the apps do not pass your account email address to RevenueCat. For purchases on playtippr.de, we pass the confirmed email address of your Tippr account to the RevenueCat Billing checkout so you do not have to enter it again; if there is no such address, the checkout asks for it. Where requested, it also collects country and postcode; payment details go directly to Stripe (see above). RevenueCat uses the email address for the purchase confirmation, receipts, notices about renewals, payment problems and cancellation, and for access to the customer portal, where you can cancel, change your payment method and download receipts. RevenueCat receives transaction and subscription data from Stripe (such as transaction ID, amount, currency, country, payment status and payment method type); RevenueCat does not store full card details. When you open “Manage subscription” in the web app, your browser loads a short-lived link to the customer portal through RevenueCat; we do not store this link.

The legal basis for purchase handling, payment, receipts and subscription status is Article 6(1)(b) GDPR (performance of a contract), for statutory retention Article 6(1)(c) GDPR in conjunction with section 147 AO and section 257 HGB, and for fraud prevention by Stripe Article 6(1)(f) GDPR (our legitimate interest in secure payments). RevenueCat also processes data in the United States; its data processing agreement includes EU Standard Contractual Clauses. Details: revenuecat.com/privacy and revenuecat.com/dpa.

The app also reports technical events about in-app ads to RevenueCat: whether an ad loaded or failed to load, whether it was displayed or clicked, the estimated revenue and currency reported by Google AdMob, the ad unit ID, the placement in the app and the name of the serving ad network, each together with the pseudonymous Tippr account ID. RevenueCat does not receive advertising IDs, ad content, predictions or location data for this. The purpose is to analyse subscription and ad revenue together. In the European Economic Area, the United Kingdom and Switzerland this only happens if, in the advertising consent dialog (section 7), you agreed to storing and accessing information on your device and to measuring ad performance; the legal basis is then your consent under Article 6(1)(a) GDPR and Section 25(1) TDDDG. If you withdraw this consent in the app under Profile, Settings, Privacy and “Manage advertising consent”, the app stops reporting such events. With Tippr Pro no ads are loaded, so no such events are reported.

Deleting the Tippr account does not cancel a subscription with Apple or Google; a web subscription bought on playtippr.de ends immediately because RevenueCat ends it together with the customer. During account deletion, the RevenueCat customer is automatically deleted before the Tippr account is deleted; if this step fails, the Tippr account is not deleted. RevenueCat-related access requests can be sent from your account address to hallo@playtippr.de.

9. Imports from other prediction games

A group administrator may import display names and point totals from an existing group. Contact details and historical individual predictions are not imported. The legal basis is Article 6(1)(f) GDPR: the group's interest in continuing its table. Unclaimed places are pseudonymised after no more than 180 days. Earlier deletion can be requested from the group manager or hallo@playtippr.de.

10. In-app feedback

The app has a public feedback board for bug reports, requests and questions. It is visible to all app users, including those without a permanent account. Posting, voting and commenting require a permanent account. The data is stored with Supabase in Ireland (section 4).

We process the title, text and category of your posts, your comments, optional attached images, your display name at the time of writing, your account ID, your votes, reports you submit and the posts you follow, as well as app version, platform, language and device model.

Other users see the title, text, category, status and vote count of a post and public comments. Your display name appears in the detail view of your post and with your comments. Who voted is not shown. Attached images are visible only to you and us. We can reply to posts, hide them, merge them and add internal notes.

If you write, vote for or comment on a post, you follow it automatically and receive push notifications about replies, status changes, a merge and when the change ships in an app version. The notification names the post title but no comment text. You can switch it off in the app's notification settings under “Feedback replies”.

The legal basis is Article 6(1)(b) GDPR for the feedback function and handling your request, and Article 6(1)(f) GDPR for the technical details: our legitimate interest in reproducing and fixing errors.

You can delete your own posts; comments and votes on them are deleted with them. When you delete your account, we delete your uploaded images, votes, reports, notifications and settings in the feedback board, as well as the list of posts you follow. Your posts and comments are anonymised, that is, kept without name, account link and device data and labelled “Gelöschtes Konto” (deleted account).

11. Retention and account deletion

Active Tippr account data is normally kept while the account exists. After deletion in the app or a verified email request, we process deletion or irreversible anonymisation of active data assigned to the account within 30 days. Posts and comments in in-app feedback are anonymised as described in section 10. If you voluntarily give a reason when deleting your account in the app, we store it without a link to your account. See Delete account and data.

Deletion cannot cover data that Apple, Google or Stripe retains under its own responsibility for purchases, billing, refunds, fraud prevention or legal obligations. We keep receipts and accounting data for purchases on playtippr.de after account deletion until the statutory retention periods end (section 8). The RevenueCat customer is automatically deleted before the Tippr account is deleted, as described in section 8. Receipts, suppression records or security data may be retained only while a legal retention duty or defence against specific abuse requires it and are blocked for other purposes.

Deleted data may remain in encrypted backups for up to 30 days. It is not restored to the active service unless required for recovery after a security incident and expires with the backup cycle.

12. Your rights

Subject to the GDPR, you have rights of access, rectification, erasure, restriction, portability and objection. Consent can be withdrawn for the future. You may also complain to a data protection authority. Email requests to hallo@playtippr.de; we may require confirmation through the account email address.

13. Security

We apply technical and organisational safeguards. Data is transmitted using TLS, passwords are not stored in plain text and access is restricted.

14. Changes

We update this policy if services, functions or legal requirements change. The current version is available on this page.

Last updated: 9 November 2026