Privacy Policy

This is a courtesy translation. The German version is legally binding. Datenschutzerklärung (Deutsch)

Chip Stack is a small app that a private poker round uses to organise its dates, the host order and its history. This page explains which data is involved, where it is stored and how you can get rid of it again.

Last updated: 20 October 2026

Controller

AppManufaktur
Inh. André Jaszka
Rebhuhnweg 12
59227 Ahlen-Vorhelm
Germany
Email: info@jaszka.com
Phone: +49 160 948 13 420

This policy applies to the “Chip Stack” apps for iOS and Android and to the website at chipstack.jahaus.de: start page, legal pages, support and invitation pages. The apps and the website run via my own server.

The key points

• There is no account: no email address, no phone number, no password.
• There is no tracking, no advertising and no analytics tools.
• The data is stored on my own server at my home in Germany.
• Push notifications are optional and only active if you turn them on.

How access works

When you create a round or join one with an invitation code, the server generates a random access key for exactly this membership. Your device stores it in the system’s protected keychain/keystore and sends it with every request. The server itself does not store the key, only a check value derived from it (SHA-256). There is a separate key for each round.

Which data is processed

On the server

• Your membership: the name you enter in the round (for example your first name), a random identifier of your seat, your chip colour, your position in the rotation, whether you are currently paused, whether you created the round, the time you joined and, where applicable, the time you left, as well as the check value of your access key.
• Data of the round: the name of the round, the dates (date, time and, if entered, a location), who is or was host when, the order, substitute hosts including undo operations, the invitation code and the check value of the recovery code.
• Notification history: events of the round (for example “date changed” or “has joined”) with the identifiers of the seats involved, plus, for each seat, up to which point you have read or cleared the history or hidden individual entries. The texts containing names are only generated from the current names when they are displayed.
• Push token (only if you turn on push notifications): a delivery address for notifications on your device, the platform (iOS or Android), the language of your device (German or English, so that the notification arrives in that language) and when it was created and last confirmed, per membership.
• Server log: For each request, a random request identifier, the method (for example GET), the path requested and the response status are logged. The path may contain the identifier of the round and of seats; invitation codes and push tokens are made unrecognisable beforehand. Your IP address, your browser or device and content are not logged. Errors are logged with a technical error message; when notifications are sent, together with the identifier of the round.
• IP address, only briefly: To protect against abuse (for example trying out codes one after another), the server counts requests per IP address. These counters are held in memory only. Each counter is valid for at most 24 hours; after that the server deletes it, including the IP address, within one minute. After a restart all counters are gone.

Only on your device

• your memberships (identifier of the round, access key, seat identifier, name of the round),
• the currently selected round, a copy of the round’s last state for fast loading, your chip colours and your push setting.

The app only uses the camera when you scan an invitation QR code; the image does not leave your device. The app only uses the motion sensors for a depth effect on the table; these values do not leave your device either.

Purposes and legal basis

• Providing the app (creating a round, joining, dates, order, history, notifications): Art. 6(1)(b) GDPR, because you use the app under the Terms of Use.
• Push notifications: only if you turn them on and your system allows it; legal basis as above, Art. 6(1)(b) GDPR. You can turn them off at any time in the system settings. The app then unsubscribes your push token from all your rounds on the server as soon as you next open it and it reaches the server; if that fails, it tries again the next time you open it. Until then the server still sends notifications to the delivery service, but your device does not show them. If you turn them back on later, the app registers the token again. You can also unsubscribe with “Delete local data” or by leaving the round.
• Security and operation (abuse counters, log, backups): Art. 6(1)(f) GDPR. My legitimate interest is a secure, stable service that survives outages and protects codes from being guessed.
• Storage on your device: The app only stores what is strictly necessary for the service you have requested (Section 25(2) no. 2 TDDDG, the German Telecommunications Digital Services Data Protection Act).

Who sees the data

• The other members of your round see your name, your chip colour, the rotation, the dates and the history. Anyone who opens an invitation sees, before joining, the name of the round, the number of members and the names of seats that have not yet been taken.
• Cloudflare (Cloudflare, Inc.): The server is reachable via a Cloudflare Tunnel; this applies to the apps and to the website. The encrypted connection ends at Cloudflare and is forwarded from there; in doing so, Cloudflare processes your IP address, the time, the paths requested, the browser or device identifier and, technically, also the content transmitted, as a processor. This serves delivery and protection against attacks. The legal basis for the website is Art. 6(1)(f) GDPR; my legitimate interest is a secure, available website. The website sets no cookies, uses no analytics or tracking tools and loads no content from other providers, not even external fonts.
• Expo Push Service (650 Industries, Inc.): only if you have turned on push notifications. Expo receives your push token and the text of the notification, which contains first names from your round and, where applicable, the date and location. Expo delivers the notification via the Apple Push Notification service (iPhone) or Google Firebase Cloud Messaging (Android); both act as sub-processors of Expo.
• Google Firebase Cloud Messaging (Google LLC) directly: On Android, the app obtains its device token from Google via the app’s Firebase project, likewise only if you have turned on push notifications.
• netcup (netcup GmbH, Karlsruhe, Germany) hosts my email mailbox, as a processor. It only holds emails you send me (see “Contact by email”).
• Apple (App Store) and Google (Google Play) distribute the app. Whatever arises when you buy and download it, including payment data, they process under their own responsibility in accordance with their own privacy policies. I do not receive card or account details. The stores send me sales and billing reports (for example order number, date, country and price, and for Google Play also city and postal code); in individual cases Google may send me your name and email address if this is necessary for processing. I use this information only for billing, tax and refunds (Art. 6(1)(b) and (c) GDPR), retain it in accordance with the statutory retention periods (Section 147 of the German Fiscal Code, AO) and do not combine it with the app’s data. Where necessary, my tax adviser and the tax office receive it.

Cloudflare, Expo and Google are based in the USA. The transfer there is based, per recipient, on the following (Data Privacy Framework means: the European Commission’s adequacy decision on the EU-US Data Privacy Framework):

• Cloudflare, Inc. (USA) – EU-US Data Privacy Framework (certified, checked on 27 September 2026), additionally the Cloudflare Data Processing Addendum with EU Standard Contractual Clauses.
• 650 Industries, Inc. (Expo, USA) – EU-US Data Privacy Framework (certified, checked on 27 September 2026), additionally the data processing terms with EU Standard Contractual Clauses (Module 2) in Expo’s Terms of Service (§ 3.2). Apple and Google deliver the notifications as sub-processors of Expo.
• Google LLC (USA, Firebase Cloud Messaging on Android) – EU-US Data Privacy Framework (certified, checked on 27 September 2026), additionally the Firebase Data Processing and Security Terms.

You can obtain a copy of these safeguards on request at info@jaszka.com.

I do not sell any data and do not pass it on to anyone else, except as described above.

Contact by email

If you send me an email, I process your email address, your name if you give it, the content of your message and the time. I use this only to reply to you and to handle your request, including requests about your data protection rights.

• Legal basis: If it concerns the use of the app, Art. 6(1)(b) GDPR. Otherwise Art. 6(1)(f) GDPR; my legitimate interest is being able to answer requests. For requests about your rights, Art. 6(1)(c) GDPR in conjunction with Art. 12 GDPR.
• Storage period: I delete your email once your request has been dealt with, unless statutory retention periods require me to keep it. I keep requests about your rights as proof for up to three years after they are closed (Art. 5(2) GDPR, limitation period under Section 195 of the German Civil Code, BGB).
• Recipient: My mailbox is hosted by netcup (netcup GmbH) in Germany. Your email does not leave the EU for this.

How long data is stored

• Round, dates and history of the round: until the creator deletes the round.
• Notification history: only the latest 100 entries per round; older ones are deleted automatically.
• Your seat after leaving: It remains in the round with your name so that the history stays correct and you can take it over again if you rejoin, until the round is deleted. If you delete your name when leaving, it is immediately replaced by “Former member”.
• Push token: until you leave the round, are removed, use “Delete local data”, turn off notifications in the system settings and the app then reaches the server, the round is deleted or the delivery service reports that the token is no longer valid.
• Backups: The server copies the database to itself every hour and deletes each copy after 48 hours. Deleted data may therefore still be contained there for up to 48 hours. There are no other backups.
• Server log: 14 days; older entries are deleted automatically by the server’s operating system.
• Abuse counters with IP address: in memory only, for at most 24 hours (plus up to one minute until clean-up).
• Connection data at Cloudflare: Cloudflare uses it only for forwarding and protection against attacks and keeps it only as long as this requires. Cloudflare does not state a fixed period.
• Emails to me: see “Contact by email”.

Deleting data

Because there is no account, you delete your data per round. These are the ways to do it:

In the app: leave the round and delete your name

1. Open the settings at the top left and then “Group and members”.
2. Under “Leave poker round”, tick “Delete my name in this round”.
3. Tap “Leave poker round” and confirm with a second tap.

The following then applies immediately: your name is replaced in the round by “Former member”, including in the history. Your access key becomes invalid, your push tokens for this round are deleted, and the membership disappears from your device. You leave the rotation. What remains: the dates and the host history of the round, now without your name. Without the tick, your name remains so that you can take over your seat again later.

If you created the round, first hand over the creator role to another member or delete the whole round.

Deleting the whole round

The person who created the round can remove it in the app under Settings, “Data and deletion”, “Delete poker round permanently”. To do so, the name of the round must be typed in. The round, all seats, dates, the history, the notifications and all push tokens are then deleted immediately, for all members.

Cleaning up this device only

Under Settings, “Data and deletion”, “Delete local data”, the app first unregisters your push token from all your rounds on the server and then deletes, on the device, the selected round, the cached copy, the chip colours and the push setting. Your memberships remain in place.

In all other cases

If you no longer have access (for example after losing your device) or you were removed from a round, write to me at info@jaszka.com and state the round and your name in it. I will then delete or anonymise your name manually. In backups, deleted data disappears when the backups expire (see How long data is stored).

Your rights

You have the right of access (Art. 15 GDPR), rectification (Art. 16), erasure (Art. 17), restriction of processing (Art. 18) and data portability (Art. 20). You may object to processing based on Art. 6(1)(f) GDPR on grounds relating to your particular situation (Art. 21). You can change your name in the app yourself at any time. For everything else, an email to info@jaszka.com is sufficient. I reply within one month (Art. 12(3) GDPR).

You also have the right to lodge a complaint with a data protection supervisory authority, for example the authority where you live (Art. 77 GDPR).

Security

All connections are encrypted via HTTPS. The server stores access keys and recovery codes only as check values. The server only accepts connections via the tunnel and has no open database access.

Do you have to provide data?

The app does not work without a name in the round; you do not need a real full name for this, a first name or nickname is enough. The location of a date and push notifications are optional.

Changes

If the app changes in a way that involves other data, I will update this policy. The version with the most recent “last updated” date above applies.