Law Enforcement Guidelines

Last updated: March 31, 2026

These Law Enforcement Guidelines are a reference for law enforcement, prosecutorial, regulatory, and other public authorities seeking disclosure, preservation, or emergency handling of Ringu user data.

These guidelines are informational only. They do not create any obligation for Ringu to disclose data in the absence of valid legal process or a legally recognized emergency basis. Ringu reviews requests case by case and may reject, narrow, or seek clarification on requests that are invalid, overbroad, disproportionate, or inconsistent with applicable law or user rights.

1. Submission Requirements

Requests must come through official government or law-enforcement channels and must identify the requesting authority, the responsible officer, and a reliable official contact method.

Requests should include:

• the name of the requesting authority and jurisdiction;
• the name, title, and official contact details of the requesting officer;
• the legal basis for the request;
• the specific account, content, or identifier at issue;
• the categories of data sought and the relevant date range;
• enough case context for Ringu to assess necessity, scope, and validity.

Ringu may decline to process informal, unsigned, or insufficiently specific requests.

2. Types of Data That May Be Requested

Depending on the account and feature involved, Ringu may hold categories of data such as:

• account registration information;
• login, session, and device records;
• public and non-public content data;
• messaging or interaction metadata;
• payment or transaction records for applicable features;
• preservation logs or enforcement records.

Not all data types are available for every account or every feature, and some data may no longer be retained when a request is received.

3. Legal Process and Scope

Authorities must use legal process that is valid for the jurisdiction, data category, and purpose involved. Ringu may require different levels of process for basic subscriber information, content data, transaction records, or other sensitive material.

Requests must be narrowly tailored. Overly broad requests, including requests for "all user data" without sufficient limits, may be rejected or returned for clarification.

4. User Notification

Where permitted or required by law, Ringu may notify users about legal requests for their data. Ringu may delay or withhold notice where notice is prohibited by law, would jeopardize an investigation, or could create a risk of harm.

If a requesting authority believes notice must be delayed or prohibited, the request should clearly state that basis.

5. Preservation Requests

Ringu may honor lawful preservation requests for a limited period where the request clearly identifies the account, content, or records to be preserved and the relevant time period.

Preservation does not guarantee disclosure. A separate valid legal request may still be required before preserved information is released.

6. Emergency Requests

Ringu may disclose limited data without standard legal process where we have a good-faith belief that doing so is necessary to prevent death, serious physical injury, child exploitation, or another legally recognized emergency.

Emergency requests should explain:

• the nature of the emergency;
• why the harm is imminent;
• the account or content involved;
• the specific data needed to address the emergency.

Ringu may request follow-up documentation where appropriate.

7. Cross-Border and Jurisdictional Issues

If the requesting authority and the relevant Ringu service operator are in different jurisdictions, additional legal-assistance procedures may be required, including treaty-based or court-to-court mechanisms.

Ringu may direct authorities to use a different process where local law, comity, data-protection requirements, or jurisdictional limits make that necessary.

8. Cost Recovery and Response Times

Ringu may seek reimbursement where permitted by law for unusual or burdensome production costs. Response times vary based on urgency, scope, legal sufficiency, and operational volume.

Emergency matters should be clearly identified as such. Submitting a request as an emergency does not guarantee emergency treatment.

9. Non-Law-Enforcement Requests

Parties seeking to report content, alleged intellectual property infringement, or other non-law-enforcement matters should use Ringu's ordinary reporting or legal channels instead of these guidelines.

General legal notices can be sent to legal@ringu.group.

10. Changes to These Guidelines

Ringu may update these Law Enforcement Guidelines to reflect changes in law, human-rights standards, operational practices, or product features.

11. Contact Us

Questions from public authorities about these guidelines can be sent to legal@ringu.group.