Cashletics
Home Cashletics PiggyRun Guide Legal Contact HU
Documents Terms and Conditions Privacy Policy Cookie & Tracking Policy Health Data Statement Banking Notification Consent Age Restriction and Exclusion of Minors In-app Consent Texts and Flow Promotions and Prize Draws Imprint
korhatár

Age Restriction and Exclusion of Minors

Rules for the minimum age of 16, age declaration and exclusion of minors.

Version: v1.10.2 Effective date: 2026-10-12

B BLOCK · FOR USERS

Age Restriction Statement

Minimum Age Requirement and Exclusion of Minors

KK-001-EN

Data Controller Mózer Ferenc (sole trader)
Registered address 6044 Kecskemét, Hetény-Belsőnyír 268/2., Hungary
Tax number 41905517-1-23
Privacy contact privacy@cashleticsapp.com
Effective date 12 October 2026
Prepared by Dr. Crespo Zsuzsanna | zsuzsanna@crespo.hu
Version v1.10.2
Legal basis Consent age threshold: GDPR Art. 8 + Hungarian implementation · Full exclusion of under-16s: Data Controller decision · Google Play Families policy
Governing language Hungarian (KK-001). In case of any discrepancy between the Hungarian and English versions, the Hungarian version shall prevail.

cashleticsapp.com/legal.php · Public document GDPR-compliant ✔

GOVERNING LANGUAGE NOTICE

This document is the English translation of the Hungarian Age Restriction Statement (KK-001).

In case of any discrepancy between the Hungarian and English versions, the Hungarian version shall prevail.

Hungarian version: cashleticsapp.com/legal.php?lang=hu

1. Summary — Minimum Age and Exclusion

⛔ Cashletics is available exclusively to users aged 16 or older.

Persons under the age of 16 may not register or use the application.

Parental consent is not accepted as a substitute — see Section 5.

This document sets out the legal basis for the Cashletics minimum age requirement, the technical implementation of the age verification process, and the exclusion mechanism for underage users. The document has been prepared in compliance with the following regulatory frameworks:

  • Regulation (EU) 2016/679 of the European Parliament and of the Council (GDPR) — Article 8

  • Hungarian Act CXII of 2011 on the Right to Informational Self-Determination and Freedom of Information (as the national implementation of GDPR Article 8 — 16-year threshold)

  • Google Play Families policy (current 2025 version)

2. Legal Basis

2.1 GDPR Article 8 — Child's consent

Under GDPR Article 8(1), in relation to the offer of information society services directly to a child, the processing of personal data of a child is lawful where the child is at least 16 years of age. Where the child is below the age of 16, such processing is lawful only if and to the extent that consent is given or authorised by the holder of parental responsibility over the child.

2.2 Why 16 — why not lower?

GDPR Article 8(1) allows Member States to lower the age threshold to 13 years. Hungary has not exercised this option: under the Hungarian national implementation, the minimum age is 16 years. Since Cashletics targets the Hungarian and broader EU market as its primary audience, the 16-year threshold applies. For users outside the EU, the same threshold is applied as a consistent global standard. The 16-year age limit is therefore a statutory requirement governing consent-based processing. Beyond this, the Data Controller has decided of its own accord to exclude persons under 16 from the service entirely: it does not implement parental consent handling, and therefore a user under 16 cannot register even with parental consent. The reasons for this decision are set out in Section 5.

2.3 Google Play Families policy

Under the Google Play Families policy, any application that processes health data (Health Connect) or financial data is automatically excluded from the Families programme. The age restriction declaration must state that the application is not designed for children. Cashletics falls into both categories:

  • Health data: step count (Health Connect / HealthKit) — GDPR Article 9 special category data

  • Financial data: banking notification reading, income/expense tracking

ℹ Play Store configuration

In the Play Console, under the app's target audience:

• Select "Adults only" category

• Do NOT tick "Designed for families"

• This is listed as a technical action item in D2-UGY

3. Age Declaration at Registration and on the Consent Screen

3.1 When and how it takes place

The e-mail registration screen requests the year of birth (in YYYY format) and — alongside acceptance of the Terms and acknowledgement of the Privacy Policy — the declaration of being at least 16 years old, as a separate mandatory checkbox (HJ-001-EN Section 4.1). For registration with a Google account and before Google sign-in, a separate dialog requests the year of birth and the 16+ declaration. At legal re-acceptance of an existing account, the consent screen requests only the declaration, as the third mandatory checkbox, and not the year of birth (HJ-001-EN Sections 4.2 and 4.5). The user must actively confirm that they are at least 16 years old. The age threshold (16 years) is supplied by the server-side legal configuration.

3.2 Interface text

[ SCREEN: Consents and declarations — extract ]

────────────────────────────────────────────────

Mandatory declarations

[ ☐ ] „I accept the Terms”

[ ☐ ] „I acknowledge the Privacy Policy”

[ ☐ ] „I confirm that I am at least 16 years old”

────────────────────────────────────────────────

[ Continue ] — enabled only after the three mandatory boxes are checked

On the Hungarian interface the declaration reads: „Nyilatkozom, hogy elmúltam 16 éves”. On the registration screen the same three mandatory boxes appear next to the year-of-birth field; there are no optional toggles there.

3.3 Rules of operation

  • The checkbox is unchecked by default (not pre-ticked).

  • Without the declaration — and at registration also with an invalid year of birth or one corresponding to an age under 16 — it is not possible to continue and the app cannot be used.

  • The age check is based on the data subject's self-declaration. The year of birth is used only for a local pre-check: four digits, and the year of birth may be at most the current year minus 16; the 16+ declaration is required separately as well.

  • The app does not store the year of birth entered at registration, and it is not included in the consent log (data minimisation, GDPR Article 5(1)(c)). The profile contains a separate, optional age field; it is not part of the age check (profile data are covered by AT-001).

  • The declaration and the accepted KK-001 version are recorded in the consent log (ageConfirmed, agePolicyVersion — see HJ-001 Section 10).

4. Exclusion Mechanism — Persons Under 16

4.1 What an under-16 user sees

A person under 16 cannot truthfully make the declaration. Without the declaration, registration cannot be completed and it is not possible to continue from the consent screen, so the app cannot be used and no financial or step-count data can be recorded.

4.2 Contact and errors

  • In case of questions or an error, the data subject can ask for help at support@cashleticsapp.com; no separate appeals procedure is required.

5. Rationale for Excluding Parental Consent

GDPR Article 8(1) in principle allows children under 16 to participate in data processing with parental consent. In the case of Cashletics, this option is deliberately excluded for the following reasons:

Reason Explanation
Health data (GDPR Art. 9) Step count qualifies as a special category of data. Under Art. 9(2)(a), explicit consent must come from the data subject — legally uncertain in the case of a child.
Financial profiling risk Income/expense tracking + banking notification reading together create a detailed financial profile. This poses heightened risk for minors.
Technical verifiability Reliably verifying that parental consent is genuinely given by a parent (rather than the child themselves) is not technically feasible in a mobile application.
Play Families policy The Google Play Families programme cannot be applied to apps processing health or financial data — this applies regardless of parental consent.
Risk proportionality Based on the DPIA-001 risk assessment, the risk level (special category data + financial profile) is disproportionately high to be managed via parental consent alone.

ℹ Legal position

The exclusion of parental consent is not a mandatory statutory requirement, but a deliberate

data protection decision supported by the DPIA-001 risk assessment.

This position is subject to review by Dr. Crespo Zsuzsanna (KK-001, Section 5).

6. Cross-References to Other Documents

Document Reference subject
ASZF-001-EN (Section 3) Age restriction in the Terms of Use — persons under 16 cannot enter into a valid contract
AT-001-EN (Section 2) Privacy Policy — definition of data subjects: natural persons aged 16 or older only
HE-001-EN (Section 1) Health Data Statement — reference to KK-001-EN for age restriction justification
BH-001-EN (Section 1) Banking Notification Consent — reference to KK-001-EN for eligible data subject definition
HJ-001-EN (Section 4) Consent flow — age declaration at registration and on the consent screen (Sections 4.1–4.2)
DPIA-001 Data Protection Impact Assessment — risk basis for parental consent exclusion
GPS-001 Play Console Data Safety — "Designed for families": NO

7. Governing Language and Version Control

GOVERNING LANGUAGE

This document is an English translation provided for the convenience of non-Hungarian speaking users.

The authoritative version of this statement is the Hungarian language document KK-001.

In case of any discrepancy between the Hungarian and English versions, the Hungarian version shall prevail.

Hungarian version: cashleticsapp.com/legal.php?lang=hu

Version Date Changes Approved by
v1.5 1 August 2026 Initial version Dr. Crespo Zsuzsanna
v1.7 1 August 2026 Sybell registered address corrected (DPA-001); DPA-002 clause 3.6 breach notification narrowed + non-excludable liability categories; DPA-003 liability cap (12 months’ fees, min. HUF 500,000); publication date updated Dr. Crespo Zsuzsanna
v1.8 1 August 2026 Legal review approved (DPIA-001, LIA-001, PR-001; DPA-002 clause 3.6 + liability framework; DPA-003 liability cap). Signatures pending. Dr. Crespo Zsuzsanna
v1.9 1 August 2026 PiggyRun mini-game, Piggy Coin, entry ticket types (standard/silver/gold) and random reward packages (loot boxes) regulated; loot box gambling-law classification approved; gamification data elements extended (AT-001, ROPA-001); DPA-001 AdMob/Firebase acceptance dates; DPIA-001 I4 closed. Dr. Crespo Zsuzsanna
v1.9.1 1 August 2026 Sybell (DPA-002): instead of signing the draft agreement, Section 11.1 of Sybell’s GTC (20 July 2026, Art. 28(3) and (9) GDPR) governs the processing; references updated; GTC archived. Dr. Crespo Zsuzsanna
v1.10 1 August 2026 DPA-003 (Balázs Bánki): implementation of the developer comments — narrowing of the developer role and data categories, incident notification under Art. 33(2) GDPR, notification of unlawful instructions under Art. 28(3) GDPR, clarification of third-country transfers, deletion of the minimum liability floor. Addition of administrator feature switches and audit log (ROPA-001 row 17, 12-month retention); clarification of the admin interface access matrix (SZ-001 2.1). [külön nem került jóváhagyásra — a v1.10.1 váltotta fel]
v1.10.1 6 August 2026 · suppl. 4 September 2026 and 5 September 2026 EN terminology alignment (Article, Data Controller); implementation of the legal review decisions; data categories of the four undocumented collections in Section 4 of AT-001. Supplement of 4 September 2026: placeholder instead of a pre-filled signature date in unsigned copies (14 documents); GDPR Article 12(3) “without undue delay” wording implemented (AT-001 HU/EN, EJ-001); in DPIA-001 the retention of health data after withdrawal changed from 7 to 30 days, aligned with HE-001; corrected EU-US Data Privacy Framework reference in the English version of BH-001; in DPA-002 the processing relationship recorded as based on Section 11.1 of the Sybell GTC and the Controller's written instruction instead of a signature; column misalignment corrected in the Article 28 record of DPA-001. In addition: in ROPA-001 and ATJ-001 the number of recorded processing activities corrected to the actual 25 (previously 17 and 16 respectively); in the consent examples of HJ-001 the reference to the never-published AT-001 v1.8.3 corrected to the published v1.8. Implementation of the legal review decisions (4 September 2026): the assistance obligation under GDPR Article 28(3)(f) added as clause 3.7 of DPA-002 and clause 3.10 of DPA-003; in the Play Data Safety table of GPS-001, transfers to Firebase Analytics are no longer declared as sharing — consistent with the document's own conceptual distinction — and health and fitness data are no longer declared as required; Firebase Analytics (L1) and the aggregated analysis built on it (L3) removed from the scope of LIA-001, as their legal basis is consent, with the exclusion table extended accordingly; the incorrect reference to the Hungarian Infotv. removed from the age-limit reasoning of KK-001, together with the identical wording in GPS-001 and XHV-001; the response deadline in EJ-001 aligned with the public undertaking in AT-001 (60 days in total at most); an explanatory note added to the 30-day undertaking under Article 12(3); the Hungarian version of BH-001 supplemented with the description of third-country transfers; AT-001 now states the storage location of Cloud Firestore as the eur3 European multi-region, consistent with ROPA-001; the developer added to the list of processors in AT-001, and the instruction clause of DPA-003 extended with the transfer wording; in six places the term “anonymised” refined to “pseudonymised”. Based on the Controller's statement of 4 September 2026: two-factor authentication for the admin interface is recorded with its actual completion date (1 September 2026) instead of an expired deadline; the emergency shutdown access issued in the developer's name has not yet been activated, therefore the access matrix of SZ-001 and the transitional provision in clause 3.9.8 of DPA-003 record the current and the final state separately, listing the data actually accessible through that role; the revocation of the earlier project-level (Editor) permission is recorded. The data subject branch of INC-001 received the exemption grounds under GDPR Article 34(3), the retention period of ROPA item 06 was aligned with AT-001, an expired external reference was replaced, and header-row repetition was enabled for two multi-page tables in SZ-001. The duplicate logo on the first page — already present in the header — has been removed from the document body (29 documents); the header logo is unchanged and no document text was altered. Supplement of 5 September 2026: the primary and secondary age controls distinguished; the package-level legal approval recorded in the version table. Supplement of 6 September 2026: based on the Controller's reply of 5 September 2026, the effective date of the package was changed from 1 August 2026 to 1 October 2026 (79 places; the applicability wording of DPA-003, the approval dates in D2-UGY and the dates in the version tables were deliberately left unchanged). Supplement of 24 September 2026: the effective date of the package changed from 1 October 2026 to 12 OCTOBER 2026. Reason: under Section 14 of ASZF-001 and Section 9 of AT-001, users must be notified of changes at least 15 days before the effective date; publication and notification took place on 27 September 2026 (instead of the previously planned 25 September). The signature date of KK-001 and PR-001 is the day of publication. Dr. Crespo Zsuzsanna
v1.10.2 3 October 2026 · suppl. 8 October 2026 Sections 3 and 4 aligned with the app's actual operation (the controller's technical deviation list of 2 October 2026; the reviewer's decision of 3 October 2026): the age declaration is the third mandatory checkbox on the consent screen („I confirm that I am at least 16 years old”), based on self-declaration, with no year of birth stored; the description of the abort screen replaced by the disabled Continue; logging according to Section 10 of HJ-001 v1.10.2 (ageConfirmed, agePolicyVersion). The former discrepancy between the Hungarian 'step 1' and the English 'Step 2' has been removed. The effective date remains 12 October 2026. Supplement of 8 October 2026, before publication (based on the controller's technical answers of 3 October 2026): e-mail registration with a year-of-birth field and a separate 16+ checkbox, Google registration and sign-in with a separate age dialog, re-acceptance of an existing account with the 16+ checkbox only; the year of birth is a local pre-check and is not stored; the cross-reference points to HJ-001 Section 4. Dr. Crespo Zsuzsanna

Acknowledgement of Receipt

Data Controller

....................................................

Mózer Ferenc

Date: 27 September 2026

Prepared by

....................................................

Dr. Crespo Zsuzsanna

Date: [upon signature]

Next scheduled review: 1 August 2027

Download original DOCX Back to list
Cashletics

Pénzügyi motiváció játékosan – pénzügy, lépésszám és jutalmak egy appban.

Product

Cashletics PiggyRun Guide

Legal and support

ÁSZF / Terms Privacy support@cashleticsapp.com Delete account
© 2026 Cashletics. All rights reserved.