Support – Billing, Account, Help

Need Help Fast?

Use Contact and explain the issue clearly. We aim to acknowledge ordinary support requests within 7 business days when action is needed.

Best support message: account email, exact URL, country, device/browser, time of failure, screenshots, and what you expected to happen. Do not send passwords or passphrases.

Billing

For billing, token, invoice, cancellation, duplicate-charge, or failed-access problems, use Contact and choose the billing route where available.

Include account email, checkout time, receipt or invoice reference, token package, affected URL, and what went wrong. Do not send full card numbers.

Account Access

Use Forgot Password on sign-in to reset access. Update profile details in Profile Settings after you are back in.

If account recovery fails, send the account email, username if known, last successful login date, and billing reference if relevant. We cannot recover a lost passphrase for you.

Tokens & Unlocks

For token balance, unlock, invoice, or paid-access problems, contact support within 30 days and include the affected story/page and checkout or invoice reference.

Useful details: token package, approximate purchase time, receipt, whether the balance changed, and whether the problem is reading, checkout, or account state.

Publishing Help

Support can route creator, submission, moderation, or policy questions to the right page: Contribute, Access, Protect, Rules, Appeals, or Legal.

Support does not create a publication promise, revenue-share deal, legal opinion, or takedown result by itself. Bigger rights and publishing decisions require the correct written route.

Safety & Bugs

Security issues belong on Bugs. Do not scan, probe, exploit, or test AngryPages without written authorization.

If you found a security problem by accident, stop immediately and report the minimum evidence needed to reproduce it. Do not access, download, retain, or expose user data.

Priority

Billing lockouts, account access, safety, legal, privacy, and active service failures get the fastest review. General suggestions and complex requests can take longer.

We aim for practical action, not endless ticket language: fix the problem, route it correctly, or tell you what evidence or policy path is missing.

What Not To Send

Never send full card numbers, passwords, passphrases, private keys, government IDs, or unrelated private material through ordinary support messages.

If sensitive evidence is genuinely required, ask for the correct secure route first. Redact other people, unrelated accounts, and unnecessary private details before sending screenshots.