Cookie Policy (Summary and Links)

1. Purpose and place of this document

To describe briefly how cookies and similar technologies (browser storage, pixels) are used at hangel. The binding and detailed text is the existing Cookie Policy (contracts: cerez-politikasi); this document holds its place in the policy library and summarises today's technical practice.

2. Scope

The hangel.org website and apps that use the web view.

3. Principles

1. Non-essential measurement does not run without consent.
2. Analytics and marketing are consented to separately; changing one does not affect the other.
3. Consent can be changed at any time.
4. No profiling-based marketing measurement is aimed at children; marketing messages are switched off for 16–17-year-olds.

4. Roles and responsibilities

• Product and technical team: links any new measurement tool to a consent category before adding it.
• Data controller (the Association): updates the Cookie Policy.

5. How it works at hangel today

• Consent banner and preference centre: A consent banner is shown on the first visit; choices can be changed in the preference centre and in the registration form.
• Categories:
  • Necessary: what the service needs to work, such as session, security and language preference (no consent needed).
  • Analytics: Microsoft Clarity, Google Analytics (Firebase) and performance measurement; on NGO profile pages, the organisation's own Google Analytics (GA4) code if it has added one. Runs only if analytics consent has been given; form fields are masked in Clarity.
  • Marketing: Google Ads conversion measurement; on NGO profile pages, the organisation's own Meta Pixel and Google Tag Manager code if it has added them. Runs only if explicitly accepted.
• Where it is stored: The consent choice is kept in the browser's local storage; when it changes, measurement tools on the page are updated immediately.
• Error monitoring: Sentry error reports do not include names, e-mail addresses or user IDs.

6. Not yet in place and our goals

• Cookie consent is stored only in the browser; no server-side consent record (when, which category, which text version) is kept. The existing Cookie Policy is based on keeping such a record; our goal is a server-side record for signed-in users.
• The existing Cookie Policy lists "functional" cookies (language, theme) as a category requiring consent; in practice, language and theme preferences are stored without consent, like the necessary category. The category definitions need to be aligned after legal review.
• No up-to-date cookie list showing the name, duration and provider of every cookie and storage key is published.

7. How to raise a concern

kvkk@hangel.org

8. Review

At least once a year and whenever a new measurement tool is added.

9. Related documents

Existing "Cookie Policy" · Privacy Policy · Personal Data Protection Policy