Privacy Policy

Version 1.3 · Effective date: 21 September 2026

1. Data controller

The controller of personal data is Jakub Jędrzejczak, a sole trader operating under the business name Jakub Jędrzejczak Trenpreneur, entered in the Polish Central Register and Information on Economic Activity (CEIDG):

• Address: ul. Słoneczna 16, 05-822 Milanówek, Poland
• Tax ID (NIP): 5291862937
• Business ID (REGON): 542257682
• Contact e-mail for data matters: oyey.games@gmail.com

The controller is not required to appoint a Data Protection Officer (DPO) and has not appointed one. For all matters concerning personal data, please write to the e-mail address above.

Processing is governed by the GDPR — Regulation (EU) 2016/679 of the European Parliament and of the Council of 27 April 2016.

2. Scope — the short version

• The app requires no account and no sign-in.
• The app does not profile users and does no tracking whatsoever. It does not use location, the camera, the microphone, contacts, health data or advertising.
• There is one exception to “we collect no data”: codes and creator referrals. If you claim a reward with a code (from a creator, a discount code or a gift) or — on Android — install the app from a creator's referral link, we record that referral and your later purchases in the app, so that we can settle the share owed to whoever gave you that code or link (see section 5). On iOS they are tied together by an identifier assigned by Apple; on Android by an identifier our app itself attaches to the purchase (a hash of the creator's handle plus a random string generated once on that installation). Neither holds any of your details — but we do not call them anonymous, because they link the purchases of one account or one installation. Without a redeemed code and without an install from a creator's link we record nothing about your purchases.
• Once downloaded, the games run offline; content and settings (e.g. player names, spice level, choice of forfeits) are saved locally on your device and are never sent to us. On Android your crew, seen cards and settings may be included in your Google backup if you have it switched on in your phone — we have no access to it, and the code and referral data are never backed up.
• Payments and subscriptions are handled by Apple within the App Store and, in the Android version, by Google within Google Play. It is Apple or Google, not us, that processes transaction and payment data (see section 4).
• We process personal data only when you contact us yourself (e.g. a support e-mail or a bug report) — in that case we process the data you send us (see section 7).
• We separately process the data of creators who have joined the code programme and whom we pay a share — the only group whose full identification and payment details we hold (see section 6). If you are a player, that section does not concern you.

3. What data we process and why

Simply using the app (playing) means that we process no personal data at all on our servers. The table below covers the only situations in which data is processed — and shows who the controller is.

4. Payments and subscriptions (Apple and Google)

In the iOS version, all in-app purchases (a single game, a game bundle, the weekly subscription) are processed through Apple In-App Purchase. This means that:

• billing runs through your Apple ID account;
• we neither see nor store your card details or full billing data — they are processed by Apple as the payment service provider;
• how Apple processes data is described in the Apple Privacy Policy;
• you manage your subscription (including cancellation) and any refunds in your Apple ID / App Store settings — details in the Terms (§ 6).

From Apple we receive sales reports and also notifications about individual transactions in the app (which product, when, in which country, for how much). They contain no name, no e-mail address and nothing from your Apple account. We need those notifications solely to settle the code programme described in section 5.

In the Android version, all in-app purchases are processed through Google Play's billing system (Google Play Billing). This means that:

• billing runs through your Google account;
• we neither see nor store your card details or full billing data — they are processed by Google as the operator of the Play Store and the payment service provider;
• how Google processes data is described in the Google Privacy Policy;
• you manage your subscription (including cancellation) in the Play Store: profile icon → Payments & subscriptions → Subscriptions (or at play.google.com/store/account/subscriptions); refunds are handled by Google under the Google Play refund policies — details in the Terms (§ 6).

From Google we receive sales reports and notifications about transactions in the app. A notification arrives at our subscription in the Google Cloud Pub/Sub service and carries only a technical purchase token; on that basis we fetch the details (which product, when, in which country, for how much, whether it was refunded) from the Google Play Developer API. They contain no name, no e-mail address and nothing from your Google account. Google may, however — under the Google Play Terms of Service — make available to us in the Play Console the order details needed to handle a purchase or a refund (the order number, the country and also — since the Google Play Terms of Service provide for passing the provider a name and an e-mail address — details of the Google account used for the purchase); we look those up only when you yourself contact us about a purchase or a refund. We need those notifications and look-ups solely to settle the code and referral programme described in section 5.

5. Codes and the referral programme

You can claim a reward in the app with a code. We issue codes in three situations: as a creator code (someone who recommends Oyey to their audience), as a discount code and as a gift. For you they behave identically, and the App Store or the Play Store always performs the redemption, not us. On Android a creator may also give you a referral link to Google Play: installing from such a link counts as a referral for us, although it is not a code and unlocks no reward.

What happens after you redeem a code (iOS, App Store). The app sends us nothing and stores no marker on your device for this purpose. The App Store performs the redemption and we learn about it from Apple's signed notification. That notification carries the identifier Apple assigns to the pair “your Apple account plus our app” (appTransactionId), which stays the same across reinstalls and new phones. That identifier — and nothing else — is how we link your later purchases in Oyey to the code you redeemed.

What happens on Android (Google Play). Here the programme does not rest on codes alone, because for a game or bundle purchase Google does not tell us which code was used (Google passes on the name of a code only for a subscription redeemed with a custom code). The app learns the creator's handle in one of two ways: from a referral link to the Play Store, or from a code entered in the app that the Play Store has confirmed. On the first launch after installation the app asks the Play Store — once, through Google's Install Referrer mechanism — which link it was installed from, and remembers only the creator's handle from our link; everything else is discarded. If the app knows a creator's handle, it attaches an identifier (the obfuscatedAccountId field) to every purchase made from the app on Google Play, made up of eight characters of a hash of that handle and 24 random characters generated once and stored on that installation. Google records it against your order, and we read it back together with the transaction data from the Google Play Developer API. That identifier — and nothing else — is how we link your purchases to the creator who referred you. It stays on the phone until you clear the app's data or uninstall the app; unlike on iOS, it does not move to a new phone and does not come back after a reinstall (after merely clearing the data, the app may for 90 days after installation read the link referral again and generate a new random string — details: Data deletion). Without a code and without a creator's link the app attaches nothing to a purchase.

What that identifier does not contain (iOS). No name, no address, no e-mail, no phone number, no device identifier and nothing from your Apple account. It cannot be used to work out who you are, including by us. It is not anonymous data, though, and we will not call it that: it ties together purchases made on one Apple account, and Apple can link it to a person. It is pseudonymised data, which we treat as personal data under the GDPR, with all the rights that gives you (see section 11).

What the Android identifier does not contain. Likewise nothing about you: eight characters point to the creator and the rest is random — there is no name, no e-mail, no phone number, no identifier of your device and nothing from your Google account. It does, however, tie together purchases made from one installation of the app, and Google, holding the order data, can link them to your Google account. So we do not call it anonymous either: we treat it as pseudonymised data, i.e. personal data under the GDPR, with the same rights for you.

• Data (iOS): the identifier assigned by Apple (appTransactionId), the transaction identifier, the product identifier, purchase date, amount and currency, storefront country, refund status, and the name of the offer the code belonged to.
• Data (Android): the identifier attached by the app (as above), the order identifier and the technical purchase token assigned by Google, the product identifier, purchase date, amount and currency, storefront country, and refund or revocation status. For games and bundles Google does not pass us the name of a code or an offer, and for a subscription it does so only for a custom code — so we know the creator's handle from the link or from the code entered in the app.
• Purpose: to determine and pay the share owed to the person who referred you (by code or by link), and to settle that programme.
• Legal basis: Article 6(1)(f) GDPR (legitimate interest: settling a partner programme) and Article 6(1)(c) GDPR for accounting and tax obligations.
• Retention: 12 months from redemption or from the install from a creator's link (the settlement window), and for records needed for accounting, the period required by law, namely 5 years from the end of the tax year. On Android the app keeps attaching the identifier to purchases for as long as it knows a creator's handle, but we settle and keep in the register only purchases within that window.
• Recipients: the data comes from Apple and stays in our accounting systems. Apple's notifications arrive at an endpoint hosted on Cloudflare which does not store them and only acknowledges receipt. On Android the data comes from Google: we receive Google Play's transaction notifications through the Google Cloud Pub/Sub service (they carry only a technical purchase token) and fetch the purchase details together with our identifier from the Google Play Developer API. A creator never learns from us who you are: we hand over no identifiers, no e-mail addresses and no “who bought what” list. What they get are numbers: how many people redeemed their code or arrived from their link, how many purchases came of it and the amount owed to them — plus, if Apple or Google refunded someone after we had already paid, a correction line with the product name and the refund date and nothing about the person.
• No code and no link, no record: if you redeem no code and do not install the app from a creator's link, your purchases never enter our referral register and leave no trace with us at all.

Exercising your rights. We run no accounts, so our register holds neither your name nor your e-mail address and we cannot find records from them directly (on Android, the e-mail address of the Google account used for the purchase lets us look the order up in the Play Console, see section 4). Write to oyey.games@gmail.com and give us enough to find the purchase in the register: the purchase date, the amount and currency, what was bought and the country of your App Store or Play Store. On iOS all of it is on the receipt Apple e-mails you, and on Android in the order confirmation Google Play e-mails to the Google account used for the purchase — you can simply forward it. It also helps to say which code you redeemed or whose link you arrived from, and roughly when. Apple's transaction identifier speeds things up but is not required: the App Store does not show it in your purchase history. On Android the Google Play order number (it starts with “GPA.”) speeds things up — it is in the order confirmation and in your order history on Google Play. We will delete every matching record except those we are legally required to keep for accounting. See Data deletion.

There is no tracking. We never combine this data with data from other apps, websites or data brokers, we build no advertising profiles, and we do not ask for ATT permission because none is needed, and on Android we do not touch the advertising ID. Programme terms are provided to each creator individually when they join.

6. Creators in the code programme

This section concerns creators: people who have joined the code programme and whom we pay a share. It does not concern players — they are covered by section 5. Unlike players, a creator is known to us by name, because money cannot be transferred and an accounting document cannot be issued without that.

• Data: name or company name, address, tax number (NIP) or personal number (PESEL), bank account number, e-mail address, the creator's handle and the code or referral link assigned to it, plus invoices or bills and the payout history.
• Purposes and legal bases: entering into and performing the cooperation agreement, including calculating and paying the share — Art. 6(1)(b) GDPR; issuing and keeping accounting documents and settling taxes — Art. 6(1)(c) GDPR (legal obligation, including the Polish Accounting Act and Tax Ordinance); pursuing or defending against claims — Art. 6(1)(f) GDPR.
• Providing the data is voluntary but necessary for payment: without it we can neither transfer the money nor book the payout.
• Retention: for the duration of the cooperation, and data contained in accounting documents for 5 years from the end of the tax year in which the document was issued. After that we delete it together with the records.
• Recipients: the bank holding our account (to make the transfer), the accounting firm that keeps our books, tax authorities and other competent authorities to the extent required by law. We pass creators' data neither to Apple, nor to Google, nor to anyone else for marketing purposes.
• Rights: access, rectification, erasure, restriction of processing, portability and objection to processing based on legitimate interest — subject to the fact that data contained in accounting documents cannot be erased before the statutory period expires. You may also lodge a complaint with PUODO (see section 11).
• No profiling. We take no automated decisions about creators and do not profile them.

For matters concerning a creator's data write to oyey.games@gmail.com — here, unlike with players' data, the e-mail address used in the cooperation is enough.

7. Support contact and bug reports

When you e-mail us (support, a question, a complaint, a bug report), we process your e-mail address and the content of your message — solely in order to reply and handle the matter. Providing this data is voluntary, but necessary for us to be able to get back to you.

We handle correspondence using e-mail provided by Google (Gmail). We keep your e-mail for as long as it is needed to handle the matter and for the limitation period for any potential claims.

8. Third-party services and SDKs

To the best of our knowledge as at the date of publication, the app does not use any third-party analytics, advertising or tracking tools (e.g. Google Analytics, Firebase, PostHog, ad networks, pixels). In particular:

• we do not use tracking for advertising purposes (App Tracking Transparency / IDFA on iOS, the advertising ID on Android);
• we do not use advertising SDKs;
• we do not use AI/ML solutions that process your data;
• we do not embed cookies or similar technologies for marketing purposes.

The Android version contains Google Play libraries: for payments (Play Billing), for reading the link the app was installed from (Install Referrer) and for the rating prompt (In-App Review). That is Google's code — it may send Google technical data about its own operation in line with the Google Privacy Policy. Apart from those libraries the app has no code that connects to the internet, and it asks for no permission that requires your consent (location, contacts, camera and so on). The rating prompt is a Play Store dialog: Google displays and handles it as the operator of the Play Store, and we receive no data from it.

The third parties involved in the operation of the service are Apple (app distribution and payments), Google — as the operator of Google Play (distribution of the Android version, payments, the referral link, the in-app rating prompt), as the provider of Google Cloud (the Pub/Sub service through which we receive Google Play's transaction notifications) and as our e-mail provider Gmail (handling contact), Cloudflare, which hosts the endpoint that receives Apple's transaction notifications (see section 5), and GitHub (GitHub Pages) and Fastly, which host and deliver this website. Cloudflare does not store those notifications. The website has no forms, sets no cookies and runs no analytics — GitHub and Fastly process only the technical data inherent in serving a page (IP address, browser type, the address of the file requested) and their own server logs.

9. Sharing of data

We do not sell personal data and we do not share it with third parties for marketing purposes. Data may be processed only by:

• Apple — for app distribution and payment handling;
• Google (Google Play, Google Cloud) — for distribution of the Android version, payment handling and transaction notifications (Pub/Sub);
• Google (Gmail) — as our e-mail provider, if you contact us;
• Cloudflare — as the infrastructure provider for the endpoint that receives Apple's transaction notifications (it does not store them);
• GitHub (GitHub Pages) and Fastly — as the hosting and content delivery providers for this website, limited to the technical data inherent in serving it;
• the bank holding our account and our accounting firm — solely for payouts and settlements with creators (see section 6);
• competent authorities — only where required by law.

Using the services of Apple, Google (including Google Play and Google Cloud), Cloudflare, GitHub and Fastly may involve transfers of data outside the European Economic Area (including to the USA). All of these providers state that they apply the transfer mechanisms provided for in the GDPR. Apple relies on the standard contractual clauses (SCC) approved by the European Commission for transfers out of the EEA and is not on the list of participants in the EU–U.S. Data Privacy Framework. Google, Cloudflare, GitHub and Fastly are participants in that framework and additionally rely on SCCs. Details in the privacy policies of Apple, Google, Cloudflare, GitHub and Fastly. The current status of any participant can be checked on the programme's list.

10. Retention periods

• In-game data (player names, settings) — stored locally on your device until you delete it or uninstall the app; on Android also in your Google backup, if you have it switched on (you manage it in your phone's settings).
• E-mail correspondence — for as long as the matter is being handled and for the limitation period for claims.
• Transaction data relating to purchases — held by Apple or Google, in line with their policies and accounting regulations.
• Code programme data (see section 5) — 12 months from redemption or from the install from a creator's link, and for accounting purposes 5 years from the end of the tax year.
• Creators' data in the code programme (see section 6) — for the duration of the cooperation, and data in accounting documents 5 years from the end of the tax year.

11. Your rights (GDPR)

To the extent that we process your data (when you contact us, when you have redeemed a code or installed the app from a creator's link — see section 5 — or when you are a creator in the code programme, see section 6), you have the right to: access your data, rectify it, erase it, restrict processing, data portability, object to processing and — where processing is based on consent — withdraw that consent.

You also have the right to lodge a complaint with the supervisory authority: the President of the Personal Data Protection Office (PUODO), ul. Stawki 2, 00-193 Warsaw, Poland.

To exercise your rights, write to oyey.games@gmail.com. If the matter concerns code programme data, include the purchase date, the amount and currency, the name of the product and the country of your App Store or Play Store (easiest: forward the receipt from Apple or the order confirmation from Google Play; on Android the order number speeds things up). Without that it is hard for us to find the records, because we run no accounts and our register holds neither your name nor your e-mail address. Step-by-step instructions: Data deletion.

12. Withdrawing consent

The app does not operate on the basis of consent: code programme data is processed on the basis of legitimate interest and accounting obligations rather than consent (see section 5), and you may object to that processing. If features requiring consent appear in the future (e.g. a marketing newsletter), you will be able to withdraw your consent at any time — without affecting the lawfulness of processing carried out before the withdrawal — by writing to oyey.games@gmail.com or using the relevant option in the message or in the app.

13. Deleting data and accounts

The app does not allow you to create an account, so there is no account to delete. To remove data stored locally, simply clear the app’s data or uninstall it (on Android: phone settings → Apps → Oyey → Clear data; your Google backup may restore your crew, seen cards and settings, never the code or referral data). To have the e-mail correspondence you sent us deleted, write to oyey.games@gmail.com. If you claimed a reward with a code or installed the app from a creator's link, you can use the same address to request deletion of the code programme settlement data, giving the date and amount of the purchase and the country of the store, and on Android ideally the Google Play order number (see section 5). Details: Data deletion.

14. Age of users

The app is intended solely for adults (18+) and that is how we target it in both stores. In the App Store it carries the 18+ age rating under Apple's system. On Google Play age ratings are assigned by independent rating authorities (PEGI in most of Europe, USK in Germany) based on the IARC questionnaire we complete; the rating may differ between countries and is shown on the app's page in the Play Store. Whatever the store rating, the app is intended solely for adults. Inside the app you can additionally switch off the most explicit cards with the “18+ cards” toggle in settings. The app is not directed at minors and we do not knowingly collect their data.

15. Changes to this policy

We may update this policy (e.g. when the app’s features or our providers change). The current version is published at https://oyey.eu/privacy-en.html together with its effective date. We will flag any material changes in the app or on the website.