LEGAL
Privacy Policy
Last updated: FILL IN: date
1. Scope of this policy — website vs. app
This website (zoneapp.hu) is a static, informational marketing page. On its own, it does not collect, store, or process any personal data about its visitors. There is no sign-up form, no contact form, no analytics, and no advertising tracking on the website itself.
The ZONE mobile application, which this website describes and promotes, does collect and process personal data — this is the actual subject of most of this Privacy Policy, because that's where real user data lives.
A note on the website's hosting infrastructure
The website is hosted on Vercel Inc., a company based in the United States. Even though the site collects no personal data of its own, serving the page still involves standard web-server-level processing (e.g. brief handling of IP addresses for routing and security purposes). Because Vercel is a US-based company, this technically counts as a transfer of data outside the European Economic Area (EEA) at the infrastructure level. Vercel's safeguards for this are described here: FILL IN: link to Vercel's Data Processing Addendum / Privacy Policy.
2. Who is the data controller
Under GDPR, the "data controller" is the person or entity that decides why and how personal data is processed.
- Full legal name: FILL IN: your full name
- Business registration: sole proprietorship / individual entrepreneur ("egyéni vállalkozó"), registration number FILL IN
- Tax identification number: FILL IN
- Registered / correspondence address: FILL IN
- Contact e-mail for privacy matters: FILL IN, e.g. privacy@zoneapp.hu
- Data Protection Officer: not currently required at this scale of operation.
If a company is incorporated in the future, this section must be updated, and existing users must be notified of the change in data controller.
3. What personal data the app collects, and why
| Category | Examples | Why it's collected |
|---|---|---|
| Account / registration data | full name, e-mail address, password (securely hashed), date of birth | creating and securing the user's account, verifying eligibility (age) |
| Profile photo | an uploaded image | displayed on the user's profile so others can recognize them |
| CV / résumé-style data | education history, work experience, skills, previous employers, professional summary, phone number | powers the core matching / recommendation feature of the app |
| Location data | approximate or precise device location | shows nearby matches / opportunities (Radar feature) |
| Technical / usage data | device type, operating system, app version, basic usage statistics | diagnosing issues, improving app stability and performance |
| FILL IN if there is any other data |
A résumé/CV typically does not contain GDPR "special category" data (health, religion, sexual orientation, etc.), but this should be double-checked once the app's data fields are finalized.
4. Legal basis for processing
- Performance of a contract — data strictly necessary to provide the service: account credentials, core CV/matching data.
- Consent — optional data or processing the user can decline: marketing emails, optional profile fields, push notifications, precise location.
- Legitimate interest — protecting the platform and its users: fraud prevention, basic security logging, aggregate usage statistics.
5. Who your data is shared with
- Hosting / backend infrastructure provider: Google Firebase (Google LLC / Google Ireland Limited). Specifically:
- Firebase Authentication — handles sign-up/login and stores authentication credentials (email, securely hashed password).
- Firestore / Realtime Database — stores profile information, CV/résumé data, and other user-generated content.
- Cloud Storage for Firebase — stores uploaded files, primarily profile photos.
- Firebase Cloud Messaging (FCM) — delivers push notifications; requires a device-specific messaging token.
- Firebase Analytics — collects aggregated app-usage statistics to help understand and improve the app.
- Push notification provider: Firebase Cloud Messaging (no separate third party).
- Analytics provider: Firebase Analytics (no separate third party).
- Other app users: FILL IN exact visibility rules — what part of a profile is visible to other users by default (e.g. name, photo, headline) versus what stays private (e.g. full address, phone number).
- Payment service provider — not yet applicable:
The app does not currently process any payments. Once a paid feature is introduced, the payment provider's name and its role under GDPR will be added here before the feature goes live, and users will be notified in advance.
- Legal disclosure: data may also be disclosed if required by law, court order, or to protect the rights, property, or safety of the company, its users, or the public.
Google provides a standard Cloud Data Processing Addendum for Firebase, which should be reviewed and accepted via the Firebase/Google Cloud console.
6. International data transfers
Since Google Firebase is the backend provider, and Google LLC is US-based, Firebase infrastructure may process and store data outside the EEA. Google is certified under the EU-US Data Privacy Framework (DPF) and additionally offers Standard Contractual Clauses (SCCs) as part of its Cloud Data Processing Addendum.
User data processed via Firebase may be transferred to and processed in the United States. This transfer is safeguarded under Google's certification to the EU-US Data Privacy Framework and/or Standard Contractual Clauses, as set out in Google's Cloud Data Processing Addendum: FILL IN: link.
7. How long data is kept
- Account data: retained while the account is active, then deleted within FILL IN, e.g. 30 days of account deletion, except where a longer period is legally required.
- Financial / billing records (once payments exist): retained for FILL IN — typically 8 years under Hungarian accounting law.
- Technical / crash diagnostics: retained for FILL IN, e.g. 90 days, then purged.
- FILL IN any other category with its own retention period
8. User rights
Under GDPR, every user has the right to:
- Access — request a copy of the personal data held about them.
- Rectification — request correction of inaccurate or incomplete data.
- Erasure — request deletion of their data, subject to legal exceptions.
- Restriction of processing — request a temporary stop to processing in certain circumstances.
- Data portability — receive their data in a structured, machine-readable format.
- Object — to processing based on legitimate interest or for direct marketing.
- Withdraw consent at any time, where processing is based on consent.
- Lodge a complaint with a supervisory authority — in Hungary, the Nemzeti Adatvédelmi és Információszabadság Hatóság (NAIH), naih.hu.
FILL IN: exactly how a user exercises these rights in practice, e.g. "Email privacy@zoneapp.hu, or use the 'Delete my data' option in Settings. We will respond within 30 days as required by law."
9. Age restriction
To use the app, a user must be at least FILL IN, e.g. 18 years old.
10. Data security
Account passwords are handled by Firebase Authentication, which stores them using a secure, industry-standard one-way hashing algorithm; raw passwords are never seen or stored directly. All data in transit between the app and Firebase is encrypted via HTTPS/TLS, enforced by default. Access to the Firestore database and Cloud Storage is restricted using Firebase Security Rules, limiting each user to their own data and to the data other users are meant to see. FILL IN: adjust to match your actual Firebase Security Rules configuration once finalized.
11. Changes to this policy
This policy may be updated from time to time; the "last updated" date above reflects the latest revision. For material changes (e.g. a new data controller, a new category of data collected, or the introduction of payments), users will be notified directly rather than relying solely on a silent update to this page.
