What to report
Possible vulnerabilities affecting public websites, products, authentication, data handling, or customer-facing workflows.
Security
Responsible disclosure for Anslation security reports.
Responsible disclosure gives users, researchers, partners, and customers a clear way to report possible vulnerabilities without exposing private data or disrupting service.
What to avoid
Do not disrupt service, access data that is not yours, run destructive tests, or publicly disclose before review.
How to help
Share the affected page or URL, steps, impact, screenshots or logs if safe, and a contact method for follow-up.
Related paths
Choose the right trust or help path.
Responsible disclosure is for vulnerability reports. Other confidence or support needs should use the matching path.
SecurityReview the broader security posture, access expectations, and public trust commitments.
- Posture
- Access care
- Report context
- Policy hub
- Confidence guides
- Accountability
- Help routing
- Order support
- Product questions
- Machine-readable
- Contact route
- Canonical file
In practice
What this looks like for you.
What each part does, what it changes for you, and where to go next.
Dedicated page
Trust routing
Disclosure has its own dedicated path
Responsible disclosure does not rely only on general security information. It has a direct path, linked from launch readiness, trust, and policy guidance.
Outcome
You can find the right reporting path without guessing where vulnerability information belongs.
- Dedicated disclosure path in place.
- Launch readiness checks point to a real reporting path.
- Trust and support keep vulnerability reports separate from general help.
Disclosure pathTrust claritySafe reporting
Read moreCleaner routing
Support separation
Reporting expectations are explicit
Responsible vulnerability reports stay separate from account, billing, order, product, and project support requests.
Outcome
Support stays easier to route, and vulnerability reports get clearer starting detail.
- Vulnerability report detail is listed.
- Unsafe testing behavior is discouraged.
- Non-vulnerability issues route back to support.
Support routingReport qualityTrust operations
Read moreDetails
Clear answers without clutter.
What to expect, in short sections with the key points called out.
Report scope
A responsible report should focus on a real vulnerability or meaningful risk in an Anslation public surface.
- Include affected route or product surface, reproduction steps, expected impact, and whether the issue is still active.
- Keep private data, credentials, payment details, and third-party account information out of the report unless absolutely necessary.
- For account, order, billing, product access, or project questions, use Support instead of the disclosure path.
Safe testing expectations
Responsible disclosure depends on care. Testing should not harm users, customers, systems, or public availability.
- Do not run destructive tests, denial-of-service attempts, spam, social engineering, or physical attacks.
- Do not access, modify, delete, download, or share data that does not belong to you.
- Stop testing and report promptly if you encounter private information or service-impacting behavior.
Review expectations
Anslation aims to acknowledge useful reports, investigate them, and coordinate next steps based on impact.
- Reports should be reviewed for reproducibility, affected scope, impact, and remediation priority.
- Public credit, bounty eligibility, or formal program terms are not implied unless a written program says so.
- Give Anslation reasonable time to investigate and resolve before public disclosure.
Disclosure FAQ
Responsible reporting should be clear before contact.
These answers reduce confusion and keep reports useful, safe, and easier to review.
Where should a vulnerability report go?
Send a responsible report to security@anslation.com with the affected URL, reproduction steps, expected impact, and a safe way to contact you.
What should not be sent?
Do not send credentials, payment details, private customer data, destructive test results, or information collected from accounts or systems you do not own.
Is this the right path for account, order, billing, or project help?
No. Use Support for account, order, billing, product access, creator, store, service, or project questions that are not vulnerability reports.
Does this page create a bug bounty program?
No. This page explains responsible reporting expectations. Any bounty, reward, or public credit must be defined in a separate written program.
Disclosure flow
How to send a responsible disclosure report to Anslation.
Report possible vulnerabilities with safe scope, useful reproduction detail, and a clear contact path.
Step 1
Confirm report scope
Use responsible disclosure for possible vulnerabilities, not account, billing, order, creator, product access, or project support.
Step 2
Keep testing safe
Do not disrupt service, access data that is not yours, run destructive tests, or share private information.
Step 3
Include useful detail
Share the affected URL, reproduction steps, expected impact, screenshots or logs only when safe, and a follow-up contact method.
Step 4
Send the report
Email the responsible disclosure inbox and give Anslation reasonable time to investigate and resolve.