Перейти к основному содержанию
Все политики

Data and Security

Public Authority Data Requests Policy

Lawfulness review of public authority data requests, objection to overly broad requests, minimum data, records and notifying the user.

Version
1.0
Effective
19 November 2026
Owner
Board of Directors, International Social Benefit Association
Review
At least once a year and whenever legislation or platform rules change
Category
Data and Security
Last updated
19 November 2026

Обязательную силу имеют турецкая и английская версии; при расхождении преимущество имеет турецкий текст. Тексты политик показаны на английском языке.

Язык текста

1. Purpose

To explain how we act when a public authority asks hangel for data about its users: how we review the request, what we share, what we do not share and how we inform the user.

2. Scope and legal basis

All requests from courts, prosecutors' offices, law enforcement and regulators with supervisory powers for personal data that hangel processes. Requests from a public authority outside Türkiye (Turkey) go through the same review.

Outside the scope of this policy:

  • A user's own requests about their data (KVKK Article 11): handled under the Personal Data Protection Policy.
  • Requests to remove content: handled under the Content Moderation and Takedown Policy. If one letter asks both for content removal and for data, the data request goes through this policy.

Legal basis: the Personal Data Protection Law No. 6698 (KVKK; in particular its provisions on proportionality, transfer and data security) and Law No. 5651 (hangel's obligations as a hosting provider).

3. Principles

  1. We review the lawfulness of every request. We check the authority's competence, the legal basis and the scope of the request. No data is given without review.
  2. We object to unlawful or overly broad requests. If competence or a legal basis is missing, or the request is wider than necessary or unclear, we object in writing and ask for the scope to be narrowed; where needed, we take legal advice.
  3. We share only the minimum data needed. We stay within the people, data types and date range the request covers. Data of users outside the request is not shared. Special categories of data, such as health data, are given only if the request and its legal basis clearly cover them.
  4. We record every request and response. The request, the review decision, the response given and the scope of the data shared are recorded with their dates; requests that are refused or narrowed are recorded too.
  5. We inform the user. Unless the law or a lawful order from the authority prohibits notification, we tell the user whose data is requested.

4. Roles and responsibilities

  • Person who receives the request: records the official letter and passes it to the Board of Directors without releasing any data.
  • Board of Directors: carries out the lawfulness review; decides on the response, a request to narrow the scope or an objection; takes legal advice where needed. There is no compliance officer appointed for this work.
  • Technical lead: extracts only the data within the scope approved by the Board of Directors and delivers it by a secure route.

5. How it works at hangel today

  1. Receipt: Letters from public authorities arrive at info@hangel.org. A letter should show the authority, the person acting for it, the legal basis and the data requested.
  2. Review: We check that the letter really comes from the authority, the authority's competence, the legal basis (an article of law or a court decision) and the scope (people, data types, date range, deadline). If the request comes from a foreign authority, we also look at the legal route by which it can reach hangel and at the KVKK rules on transfers abroad.
  3. Decision: The Board of Directors takes one of three decisions: the request is in order and is answered; more information is requested; or the request is unlawful or overly broad and is objected to or narrowing is requested.
  4. Sharing: Data within the approved scope is given by a secure route and only to the requesting authority.
  5. Notifying the user: If notification is not prohibited, the user whose data is shared or requested is informed by e-mail or in-app notification.
  6. Record: The request and the response are kept in the relevant correspondence file together with the date, the authority, the legal basis, the data requested and given, the Board decision and the user notification. Retention follows the Data Retention and Destruction Policy.
  7. Current position: As of 19.11.2026, hangel has received no data request from a public authority in the last 12 months.

6. Not yet in place and our goals

  • There is no separate register or admin panel screen for public authority requests; the record is kept in the correspondence file. Our goal is to track them as a separate record in the Legal Desk.
  • We do not publish a transparency report showing the number, type of authority and outcome of requests. Our goal is to publish an annual summary once requests are received.
  • There is no written target time for responding to a request and there are no ready-made response or objection templates.
  • Contracts with service providers do not yet require, for every provider, that public requests received directly by the provider be reported to us (where the law allows); our goal is to require this.

7. How to reach us

Official letters from public authorities: info@hangel.org. People who believe their data was shared because of a public request, or who want information about their own data: kvkk@hangel.org.

8. Review

At least once a year; also when legislation or platform rules change and after the first public request is received.

9. Related documents

Personal Data Protection Policy · Privacy Policy · Content Moderation and Takedown Policy · Data Retention and Destruction Policy · Data Breach Response Policy · Compliance Management Policy

Все политики