Trust route
Last updated July 15, 2026Responsible disclosure for Anslation security reports.
Responsible disclosure gives visitors, researchers, partners, and customers a clear way to report possible vulnerabilities without exposing private data or disrupting service.
1
Report inbox
Use one clear report path so vulnerability information reaches the right review queue.
Safe
Testing rule
Reports should avoid destructive testing, privacy harm, service disruption, or data access beyond what is necessary.
Clear
Useful detail
The best reports include affected URL, reproduction steps, expected impact, and contact details.
Public route system
Responsible disclosure stays connected to the full Anslation public site.
Every company page should answer what the visitor is reading, where it fits, what is safe to show publicly, and what route should come next.
102
Public routes
7
Route groups
7
Primary paths
Public-safe standard
Only approved public pages are described here. Account-only dashboards, non-public logic, and operating modules stay out of the public website map.
UnderstandLearn what Anslation is and how the company is structured.ChooseMatch the visitor goal to the right product or service lane.VerifyRead trust, support, policy, and public quality expectations.StartTurn the route decision into a structured project request.
CompanyStory, people, culture, proof, careers, and operating context.36
Company homepageStart projectPricing
Primary groupOpen
SolutionsSoftware, services, finder, pricing, and business fit.4SolutionsSolution FinderSoftware
Primary groupOpen
ProductsAnslation One, Ansi, and connected product surfaces.41Anslation OneAnslation CloudAnsiOne
Primary groupOpen
GrowthMarketing, advertising, measurement, campaigns, and visibility.2MarketingAdvertisement
Core groupOpen
CommerceStore, creators, catalog, launches, and order support.6StoreCreatorsAnslation Store
Core groupOpen
What to report
Possible vulnerabilities affecting public websites, products, authentication, data handling, or customer-facing workflows.
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 route, steps, impact, screenshots or logs if safe, and a contact method for follow-up.
Company routes
Move across story, people, trust, and support without losing context.
Anslation should feel like one connected company system. These routes keep the public journey clear from overview to culture, hiring, trust, support, and direct contact.
Company
About
Anslation is a creative software company building connected products, service delivery systems, marketing engines, advertisement operations, ecommerce surfaces, creator programs, and operating software.
Company structureStudio teamsOperating model
Open page
People system
Team
Anslation is organized into four studios with clear ownership, clean handoffs, visible leadership, and room to grow as the company scales.
StudiosLeadershipOwnership
Open page
Company direction
Leadership
Anslation leadership keeps company direction, studio quality, trust readiness, and future team growth aligned without exposing private operating details.
DirectionStudio reviewsTrust readiness
Open page
People
Culture
Anslation culture is built around clarity, high ownership, craft, calm execution, and the belief that creative work and operational discipline should support each other.
OwnershipCraftLearning
Open page
Join
Careers
Anslation is a home for builders, designers, marketers, operators, creators, and business-minded product people who want their work to compound.
Future rolesCandidate clarityBuilder culture
Open page
Trust center
Trust
The Trust Center brings Anslation security, privacy, policies, responsible disclosure, ecommerce rules, creator terms, data handling, and service commitments into one clear place.
SecurityPrivacyLegal
Open page
Help
Support
Anslation Support gives visitors a clean starting point for product help, project delivery, store orders, creator programs, billing questions, and general company routing.
Product helpStore ordersCreator support
Open page
Start
Contact
Reach the right team directly — product, services, marketing, advertising, store, creators, partnerships, or general inquiries.
Business inquiryPartnershipsSupport routing
Open page
Related routes
Choose the right trust or help path.
Responsible disclosure is for vulnerability reports. Other confidence or support needs should use the matching public route.
Security
Review the broader security posture, access expectations, and public trust commitments.
Posture
Access care
Report context
Open security
Trust
Open the wider trust hub for privacy, policies, commerce confidence, and service commitments.
Policy hub
Confidence routes
Accountability
Open trust
Support
Use support for product access, order, account, billing, creator, or project help.
Help routing
Order support
Product questions
Open support
Security text
Machine-readable responsible disclosure contact information for researchers and automated tools.
Machine-readable
Contact route
Canonical file
Open security.txt
Proof library
Stories Anslation can publish as the work becomes public.
These cards create a credible case-study structure without inventing client logos or unverified numbers.
Dedicated page
Trust routing
Disclosure now has its own public route
The site no longer relies only on a general security page. Responsible disclosure has a direct route that can be linked from launch readiness, trust, and policy surfaces.
Outcome
Visitors can find the right reporting path without guessing where vulnerability information belongs.
Dedicated disclosure route added.
Launch readiness can link to a real page.
Trust and support routes can separate vulnerability reports from general help.
Disclosure routeTrust clarityPublic-safe reporting
Read detail pageCleaner routing
Support separation
Reporting expectations are explicit
The page separates responsible vulnerability reports 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 detail pageDetails
Clear answers without clutter.
Readable sections, short points, and obvious next steps make the company pages feel calm and trustworthy.
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 should acknowledge useful reports, investigate responsibly, 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.