1) Who should use this page
This process is for authorized law-enforcement officers and government agencies acting in an official capacity. Members should report misconduct through the in-app reporting tools and safety@yahalaly.com. Yahalaly is not an emergency dispatch service.
Private parties, civil litigants, insurers, employers, family members, and private investigators should not use the emergency or law-enforcement channels. They may contact support@yahalaly.com, but Yahalaly will not disclose member data merely because it is requested.
2) Routine law-enforcement requests
Send routine requests from an official government or agency email address to support@yahalaly.com with the subject “[LAW ENFORCEMENT REQUEST]”. Include:
- The requesting officer's full name, title or rank, badge or professional identification number, agency, official postal address, work email, and direct telephone number.
- A case or reference number and a supervisor, duty desk, or publicly verifiable agency contact through which the requester's identity and authority can be confirmed.
- The request type, issuing authority, jurisdiction, applicable legal basis, and a complete, dated, signed copy of the warrant, order, subpoena, production request, or other process relied upon.
- Precise Yahalaly account identifiers, such as the registered email address or Yahalaly user ID. A name alone may not identify an account.
- The specific records requested, a narrow date range with time zone, how the records relate to the investigation, and any legally required response date.
- Instructions for a secure response method. Do not send classified material or unnecessary sensitive personal data through ordinary email; ask to arrange an appropriate transfer method first.
3) Verification, jurisdiction, and formal service
Yahalaly may independently verify a request through publicly listed agency contact details, contact the issuing authority, require additional credentials or documentation, and seek clarification or a narrower scope. Requests that do not establish the requester's identity, authority, legal basis, jurisdiction, or sufficiently specific account and records may be delayed, rejected, or returned for correction.
Submitting a request by email does not waive any applicable requirement for formal service, create consent to another jurisdiction, or accept defective process. Where formal service is legally required, use the service-provider details on the Contact & Legal Requests page and the legally required method of service.
Because Yahalaly's service provider is based in Germany, a request issued elsewhere may require an appropriate German, European Union, or international cooperation process. The mechanism depends on the requesting authority, location, and records sought.
4) Preservation requests
Send an official preservation request to support@yahalaly.com with the subject “[PRESERVATION REQUEST]”. State the legal authority for preservation and include the requester-verification details above, the exact account identifier, specific data categories, relevant date range and time zone, requested preservation period, case number, and known risk of loss.
- Yahalaly will assess whether a request is valid, legally permitted, sufficiently specific, and technically capable of being fulfilled.
- A request is not accepted until Yahalaly confirms acceptance in writing. Deleted, expired, overwritten, or never-collected records cannot be preserved.
- Preservation does not authorize disclosure. Valid disclosure process must follow before preserved records can be produced.
- Any extension request must arrive before the confirmed preservation period expires and must identify the continued legal authority and scope.
5) Emergency requests involving imminent harm
If someone faces immediate danger, contact the emergency services in the place where the person is located. Yahalaly is not monitored as a 24-hour emergency channel and cannot replace police, medical, or rescue services.
An authorized official may send an emergency disclosure request to safety@yahalaly.com with the subject “[EMERGENCY LAW ENFORCEMENT REQUEST]”. The request must come from an official agency address and include:
- All officer, agency, case, and verification information required for a routine request.
- A specific description of the emergency and why there is a good-faith basis to believe there is an imminent risk of death or serious physical harm.
- The person or people at risk, their known location, the narrow data requested, the relevant time period, and an explanation of how the requested data could help prevent the harm.
- The legal authority for emergency disclosure, a direct telephone number staffed for verification, and a certification that the information supplied is accurate to the requester's knowledge.
6) Emergency assessment and request review
Yahalaly may make a limited emergency disclosure only where applicable law permits it and the circumstances support a good-faith emergency assessment. Marking a request as an emergency does not create automatic access, bypass verification, or guarantee that relevant data exists or can be provided in time.
- Yahalaly assesses authenticity, issuing authority, jurisdiction, legal basis, necessity, proportionality, account identification, scope, and technical availability.
- Yahalaly may seek clarification, narrow an overbroad request, object to or challenge defective process where appropriate, or decline voluntary disclosure.
- When disclosure is required or lawfully justified, Yahalaly limits production to responsive data reasonably necessary for the valid request and available in its systems at the time of review.
- Yahalaly does not provide direct account access, unrestricted system access, or real-time surveillance merely on request. Any exceptional capability would require applicable legal authority and technical feasibility.
7) Records that may be available
Depending on the account, feature use, retention period, and request date, Yahalaly systems may contain registration and account data; self-declared profile, preference, values, and location information; photo and visibility records; likes, matches, blocks, messages, and guardian interactions; reports and moderation records; and limited session, IP-address, user-agent, email-delivery, security, and audit information.
This list describes possible categories, not a guarantee that any record exists, is complete, or will be disclosed. Yahalaly does not represent that it independently verifies government identity, age beyond a self-declared birth date, marital status, criminal history, employment, education, religious practice, or sanctions status. It cannot create records, recover data it no longer holds, or confirm claims it did not verify.
Account erasure removes substantial account and interaction data as described in the Privacy Policy. Limited safety evidence, audit records, suppression records, or deletion tombstones may remain for their stated purposes.
8) Member notice and confidentiality
Where legally permitted and appropriate, Yahalaly may notify an affected account holder of a request before or after disclosure. Notice may be delayed or withheld when prohibited by valid legal process or when notice could create a material risk to a person, evidence, an investigation, or service security.
A request for non-notification should identify the legal basis, specific reason, and applicable period. Yahalaly will assess confidentiality requirements under applicable law rather than treating an unsupported confidentiality request as binding.
9) Data protection and response handling
Law-enforcement requests may contain personal data. Requesters should provide only information necessary to identify the request, account, authority, and records. Yahalaly handles and records requests with access limited by role and purpose and may retain the request and response where reasonably necessary for legal compliance, security, accountability, or legal claims.
A production may be transmitted through a mutually agreed secure method. The requesting authority is responsible for protecting disclosed records after receipt and using them only under its lawful authority.
10) Contact summary
Receipt is not acceptance, legal service, confirmation that an account exists, or a promise of a particular response time. Yahalaly may update these guidelines as its procedures, service, or legal obligations change.
- Routine law-enforcement process: support@yahalaly.com — subject “[LAW ENFORCEMENT REQUEST]”.
- Preservation request: support@yahalaly.com — subject “[PRESERVATION REQUEST]”.
- Imminent death or serious-physical-harm request from an authorized agency: safety@yahalaly.com — subject “[EMERGENCY LAW ENFORCEMENT REQUEST]”.
- Member safety report: in-app reporting first, then safety@yahalaly.com.
- Privacy-rights request from a member: privacy@yahalaly.com.
