DecksHome › Privacy Policy
Privacy Policy
1. Controller
Gleb Tkatchouk, Israel ("we", "us"), is the controller of the personal data described in this policy.
Contact for any privacy matter, including requests concerning your data: privacy@deckgames.app.
2. Scope
This policy applies to the mobile application Decks - Solitaire & Card Games (app.deckgames.decks) ("the App") and to this website. It does not apply to the App Store or any other service operated by a third party.
3. Data stored only on your device
The App has no user accounts. The following is stored locally and is not transmitted to us:
- games in progress, saved deals and hands;
- the record of moves made in a round;
- the history of rounds, outcomes and statistics;
- the session log kept for troubleshooting.
Deleting the App deletes this data.
4. Data collected with your consent, and app configuration
At the end of onboarding the App asks two separate questions: whether usage events may be sent, and whether crash reports may be sent. No usage events or crash reports are sent before that answer is given. If consent is refused, data queued on the device is deleted. Both answers may be changed at any time in Settings, section "Data".
4.1 Usage events
Each event carries the App version, the build environment (dev or prod) and the interface language. The complete list of events, with the purpose of each:
| Event | Purpose |
|---|---|
app_launched | frequency of use and entry point |
screen_shown | which screens are used and in what order |
onboarding_completed | completion rate of the introduction |
consent_answered | proportion of users granting each consent |
game_opened | which games are opened |
round_started | which games are played, and at which level |
round_ended | outcome of rounds: won, lost, abandoned |
round_resumed | return rate to unfinished rounds |
round_milestone_reached | progress reached within a round |
rules_shown | use of the in-app rules |
animation_completed | whether animations are watched in full |
animation_skipped | which animations are skipped, and when |
daily_opened | use of the daily task |
setting_changed | which settings are changed |
report_sent | use of the report function |
experiment_exposed | which variant of a trial the device received |
error_recorded | occurrence of an error, the screen, and a reproduction string |
paywall_shown | which condition led to the subscription screen |
subscription_purchased | which subscription was purchased |
purchase_failed | reason a purchase did not complete |
subscription_restored | restoration of a subscription on a device |
limit_reached | which free-tier limit was reached |
review_requested | that the App asked the system to show a rating prompt, and after which win |
Individual taps, card movements and the contents of games are not included in any event.
4.2 Device properties
The following properties are attached to the device record:
app_version— version and build number of the App.environment— whether the build is a test build or a released build.language— interface language.analytics_consent_granted— whether consent to usage events was given.crash_reports_granted— whether consent to crash reports was given.ai_level— selected opponent strength.shuffle_style— selected shuffle animation.intro_animation_enabled— whether the opening animation is enabled.total_rounds_played— number of rounds played on the device.total_rounds_won— number of rounds won.total_rounds_lost— number of rounds lost.total_rounds_abandoned— number of rounds abandoned.favorite_game— most played game on the device.first_game— first game played on the device.premium_active— whether a subscription is active.premium_product— which subscription is active.premium_pretend— whether the subscription test switch used in development builds is on (it does not exist in App Store builds).store_env— the store environment reported by Apple for the purchase check:production,sandbox,xcodeorunknown.
4.3 Identifiers
We create no identifier of our own and operate no user accounts. The analytics providers generate their own device identifiers (Amplitude device ID, Firebase app instance ID). These identify a device, not a person, and are reset when consent is withdrawn.
4.4 Crash reports
Where consent to crash reports is given, a crash transmits the device model, operating system version, App version and the stack trace of the failure.
4.5 Purchase records
Where a subscription is purchased or restored, the App records that the event occurred and which product was involved. Payment is processed by Apple. We do not receive payment card details, billing names or billing addresses.
4.6 App configuration
When the App starts, and then at most about once an hour, it asks Google Firebase Remote Config for its settings — for example the daily limits and which games are shown. This request does not depend on your answers to the consent questions and cannot be switched off in Settings; it is part of how the App works. The request is made by Google's Firebase software and, like any request over the internet, reaches Google together with the Firebase installation identifier of the App, the App version, the interface language and the country, and your IP address. If the request fails, the App uses built-in default settings and keeps working offline.
5. Data you transmit to us directly
Taking a screenshot within the App opens a report sheet. If you elect to send it, your own mail application opens with the screenshot attached and, unless you disable the option, the session log. No transmission occurs until you send the message. Such messages reach us as ordinary email at support@deckgames.app.
6. Purposes of processing
Data described in section 4 is processed to measure use of the App, to identify defects and failures, to evaluate product changes, and to account for subscription conversion. It is not used for advertising, profiling, or automated decision-making producing legal effects. Configuration requested under section 4.6 is used only to operate the App.
7. Legal basis and withdrawal of consent
Processing described in sections 4.1 to 4.5 is based on your consent (Article 6(1)(a) GDPR). Consent may be withdrawn at any time in Settings, section "Data". Withdrawal stops further collection and resets the identifiers referred to in section 4.3. Withdrawal does not affect the lawfulness of processing carried out before it.
8. Recipients
| Recipient | Function | Location |
|---|---|---|
| Amplitude, Inc. | product analytics | United States |
| Google LLC (Firebase Analytics, Crashlytics, Remote Config) | analytics and crash reporting (with your consent); app configuration (always) | United States and other Google regions |
| Apple Inc. | sale of subscriptions, on its own terms | its region |
The analytics providers act as processors under data processing agreements. Data is not sold and is not disclosed for advertising purposes.
9. International transfers
We are established in Israel, which the European Commission has recognised as providing an adequate level of protection for personal data (Decision of 31 January 2011, reaffirmed on 15 January 2024). Transfers from the European Economic Area to us therefore require no additional safeguards. Onward transfers by the processors named in section 8 to the United States are governed by the European Commission's standard contractual clauses.
10. Retention
Event and crash data is retained for 14 months and is then deleted by the processors on a rolling basis. Correspondence is retained for no longer than three years.
11. Your rights
Where the GDPR or the UK GDPR applies, you have the rights of access, rectification, erasure, restriction of processing, data portability and objection, and the right to lodge a complaint with your supervisory authority.
Because the App has no accounts, records ordinarily cannot be linked to an identified person. Requests concerning analytics data therefore require the device identifier; section 12 sets out the procedure.
12. Deletion of data
Stopping collection. In Settings, section "Data", disable "Usage events", "Crash reports", or both. Collection stops immediately and the identifiers referred to in section 4.3 are reset. Data already collected expires under section 10.
Deletion of data already collected. Send a request to privacy@deckgames.app. We will state what is required to locate the record for your device, delete it, and confirm deletion. Requests are acknowledged within 24 hours and completed within thirty days.
Deletion of local data. Delete the App. On iOS, its data may also be removed through Settings, General, iPhone Storage.
Correspondence. Email sent to us is deleted on request unless retention is required, for example while a payment dispute is pending.
13. Children
The App is not directed to children. Use requires a minimum age of 13, or 16 in jurisdictions where consent to processing requires that age, unless a parent or guardian consents. We do not knowingly collect data from children below the applicable age. Where we are informed that such data has been collected, it is deleted.
14. Security
Data on the device is stored within the application sandbox. Transmission to the processors named in section 8 is encrypted in transit. Access to analytics accounts is limited to the controller.
15. California residents
We do not sell or share personal information within the meaning of the CCPA and have not done so in the preceding twelve months. The rights set out in section 11 may be exercised through the contact address in section 1.
16. Israel
We are established in Israel and subject to the Protection of Privacy Law, 5741-1981. Transfer of data outside Israel to the processors named in section 8 is carried out on the basis of your consent.
17. Website
The website sets no cookies, loads no scripts, and uses no third-party analytics. The web server records each request in a log: IP address, date and time, the address requested, the response code, the referring page, and the browser identification string. The log is kept for fourteen days and then deleted; aggregate statistics derived from it (page views, referring sites, countries) contain no IP addresses.
Logs are processed on the basis of our legitimate interest (Article 6(1)(f) GDPR) in operating the site securely and in measuring how it is used. They are not combined with data from the App and are not disclosed to anyone except as required by law.
18. Changes
This policy may be amended. The date of the current version appears at the foot of this page. Where an amendment affects the categories or purposes of data collected, consent is requested again within the App.
19. Contact
Gleb Tkatchouk, Israel · privacy@deckgames.app