Legal
Law Enforcement
Information for law enforcement agencies requesting data or cooperation from The Sugar Look.
Legal
Information for law enforcement agencies requesting data or cooperation from The Sugar Look.
Can't find what you need? Our support team can help with account and safety questions.
Need further assistance?This page explains how law enforcement and other authorized government agencies can submit requests for information or cooperation from The Sugar Look.
We take member privacy seriously and review each request for authenticity, legal validity, jurisdiction, and proportionality before responding.
This information should be read together with our Privacy Policy, Safety policy, and Terms of Service. Those pages describe how data is collected, retained, protected, and used on the platform.
Official requests must be submitted on agency letterhead or through another verifiable government channel associated with the requesting authority.
Requests should be sent through Contact Us by choosing the topic that best matches a law-enforcement or legal inquiry, or through the official contact method published for your region if one is provided separately.
We do not accept informal, anonymous, or unverifiable requests for member data. Requests that cannot be authenticated may be rejected or delayed pending verification.
Include enough detail for us to locate the relevant account, content, or incident without requesting unrelated records.
Each request should identify the requesting agency, the authorized official making the request, and official contact details for follow-up.
State the legal basis for the request, the applicable statute, order, warrant, or equivalent process, and the jurisdiction under which it was issued.
Define the scope clearly, including the accounts, usernames, profile URLs, content links, date ranges, and incident references involved.
Where available, provide account identifiers, email addresses or aliases used on the platform, timestamps, IP references, and any internal report or ticket numbers already known to your agency.
Broad or exploratory requests that do not identify specific records or a lawful basis may be narrowed or declined.
Each request is logged, reviewed for authenticity, and assessed for legal sufficiency and proportionality before any disclosure is made.
We disclose only information reasonably required by a valid request and within the scope of the legal process presented.
Data outside the requested account, time range, or incident scope is not provided unless separately authorized by valid legal process.
We may ask for clarification, additional legal process, or a narrower scope where a request appears overbroad or insufficiently supported.
Response times vary depending on complexity, scope, verification requirements, and current volume. Emergency requests involving imminent harm are prioritized where credible and lawful.
Depending on the request and applicable law, we may be able to provide account-related records such as registration email, alias, profile settings, subscription status indicators, posts, messages, reports, moderation actions, and security or access logs linked to the scoped request.
We may preserve or disclose information needed to investigate credible safety concerns, exploitation, fraud, or unlawful conduct tied to a valid legal process.
Disclosures are made in a form suitable for the request and may exclude data that was never collected, has been deleted under our retention rules, or is held only by an external provider.
We do not store payment card numbers, bank details, wallet credentials, gift card codes, or similar payment credentials. Those records cannot be produced from our systems because we do not receive or retain them.
Verification source materials submitted during account verification are permanently deleted after the verification process is completed and are not available as ordinary readable account data.
We do not provide data about accounts, users, or activity outside the lawful scope of a valid request.
We do not bypass platform safeguards, alter records, or provide access to live accounts except where required by valid legal process and technically feasible.
If there is an imminent risk of death or serious physical harm, clearly mark the request as an emergency and explain why immediate action is needed.
Include the account identifiers, content links, usernames, timestamps, and factual basis supporting the emergency nature of the request.
Credible emergency requests are prioritized for rapid review consistent with applicable law.
This process does not replace local emergency services. Agencies responding to active physical danger should use appropriate emergency channels in parallel where required.
Where permitted by law, agencies may request that specified records be preserved pending service of formal legal process.
Preservation requests should identify the account or incident with the same specificity required for a data request and state the anticipated follow-up legal process.
Preservation does not constitute disclosure. Data is retained only for the period and scope supported by the request and applicable law.
We review whether a request originates from an authority with lawful jurisdiction over the records sought and whether applicable cross-border legal process has been satisfied.
Requests from outside our primary operating jurisdiction may require additional documentation, treaty process, or local legal formalities before disclosure can be considered.
We may reject or seek clarification on requests that appear invalid, expired, improperly scoped, or inconsistent with applicable privacy and procedural requirements.
Authorized agencies may submit requests through Contact Us using the topic that best matches a law-enforcement or legal inquiry.
Include agency identity, legal basis, scope, and identifiers in the initial message so the request can be routed and reviewed without unnecessary delay.