Public support identity
Choose the route
- Account, login, or access.
- Camera, microphone, loading, connection, or device problem.
- Billing, payment, recharge, coins, or paid-feature issue.
- Safety concern or another user's behavior.
- Privacy or data-rights question.
- Content correction or source question.
- Partnership, media, or legal only if a real responsible owner exists.
Send useful, safe context
For technical issues: page URL, date/time with timezone, device, operating system, browser/version, exact visible state, and a redacted screenshot. For billing: account identifier and order/transaction reference only when safe—never a full card number, CVV, password, or one-time code. For editorial corrections: page URL, exact statement, and supporting source.
Safety route
Leave first. Use the verified in-product Report path and Block when appropriate. Immediate danger belongs with local emergency services. Do not email intimate images or suspected illegal material.
Do not send
Credentials, authentication codes, government IDs, full financial details, intimate images, illegal material, or another person's unnecessary data. Identity verification for a privacy request must follow a defined secure process, not an improvised email demand.
Response expectations
Publish a response-time range only after a monitored operation can consistently meet it. Until then, make no SLA promise. Self-service help remains available through camera, microphone, loading, connection, and corrections.
Route billing without collecting card data
The mother-owned purchase surface and payment provider determine identifiers available to the user. Ask for the minimum safe reference needed to locate the issue, plus approximate time and visible result. Never request a password, CVV, full card number, one-time code, or screenshot that exposes them. Refund or entitlement outcomes cannot be promised here.
Route privacy requests through a defined process
State accepted request types only after operator responsibility and identity-verification steps are approved. Do not ask someone to email a government ID because the site lacks a secure process. Legal deadlines and jurisdictional disclosures require human legal review.
Forms must be real or absent
If launch uses email, show one verified mail link and safe-context guidance. Add a form only when storage, consent, spam, attachment, abuse, confirmation, and deletion behavior are implemented and tested.
Additional path: About · Editorial Policy · Safety Center