Legal contact & complaints

1.Contact the operator

The site currently lists contact@kookey.me for project inquiries, but mailbox monitoring, response times, and postal contact details have not been verified. A monitored legal and privacy contact, the operator’s full legal name, and postal address have not been published yet. We’ll share them before the hosted service opens. Until then, do not assume an email has been received or that a response deadline applies. Do not include passwords, authentication tokens, or unnecessary sensitive documents in an initial message.

2.What to include

• The page or account URL involved and a clear description of the concern.
• The relevant policy or right, if known, and the country whose law or authority is involved.
• A safe reply address; avoid sending passwords, payment details, or unnecessary identity documents.
• For a privacy request, identify the right you want to exercise and enough context to locate the data without disclosing unrelated sensitive information.

3.Choose the right kind of request

Privacy requests, copyright notices, safety reports, security vulnerabilities, consumer complaints, and official legal requests need separate handling. The hosted service has no in-app reporting or account-rights workflow yet. Before these service features are available, we’ll share the right address or form for each request, what information to include, and how to send it securely.

4.Independent complaints

The competent authority depends on the operator, the user’s location, the service, and the issue. kookey’s legal jurisdiction and the hosted service’s regulatory classification have not been confirmed, so we can’t yet say which authority applies to each visitor. We’ll share the relevant authority and its official contact details after the legal review.

5.What happens after submission

A monitored inbox, acknowledgment process, response target, languages supported, and escalation route have not been confirmed. These details will be published before the hosted service opens. The final process will explain how a request is logged, when proportionate identity checks may be needed, how the operator responds, and what to do if a request is incomplete or delayed. Do not send passwords or identity documents unless a verified process explains why they are needed.

6.Urgent safety and security concerns

This website does not provide emergency response or an in-app safety report. Dedicated safety and security contacts are not available yet. We’ll publish them before user accounts open. If someone faces immediate danger, contact the appropriate local emergency service; do not wait for a project email response. A vulnerability report should be sent privately after a verified security contact is published.