Trust and policies
How Anslation handles your data, orders, and reports.
One place for Anslation policies, data handling, store and creator rules, vulnerability reporting, and service commitments.
Every document on this page is a draft until its final legal review.
No service-level agreement or data processing addendum is published on this site yet. Questions about a policy go to support@anslation.com.
Practices
What we do today.
Each row names a practice and the page that shows it. What is not published yet says so.
7 of 9 areas published with evidence
| Area | What we do | Evidence |
|---|---|---|
| Vulnerability reports | A published reporting path with scope and safe-testing rules, and a security.txt file that names security@anslation.com. | Security |
| Dedicated inboxes | Separate addresses for new work, support, privacy, security, and careers, so a message reaches the team that handles it. | Contact |
| Cookies | Analytics stay off until you allow them, and you can change the choice on the Cookie Policy page. | Cookie Policy |
| Starting a project | No login details, access keys, or customer records are needed to start a brief. | Start a project |
| Release checks | Analytics, redirects, the support path, and order checks are in place before a release goes live. | Launch checklist |
| Orders | Refund, shipping, and cancellation policies, and order tracking for store purchases. | Refund Policy |
| Creator programs | Creator terms for programs, collaborations, and content work. | Creator Terms |
| Service-level agreement (SLA) | – Not yet published | Ask a question |
| Data processing addendum (DPA) | – Not yet published | Ask a question |
Policies
The documents themselves.
All eight policies. Open the one you need; each carries a draft notice until its final review.
Key trust questions, answered quickly.
You often want a quick answer before opening every policy document. These cover the most common ones.
What is the trust page for?
It is one public place for Anslation policies, data handling, vulnerability reporting, support, creator, and commerce information.
Where should someone report a vulnerability?
Use responsible disclosure, and include the affected URL, the impact, and the steps to reproduce it.
Which pages should customers review first?
Trust, Support, Privacy Policy, Terms of Service, and any store or creator policies relevant to the specific purchase or engagement.
Send a support or policy question.
Office hours: Monday to Saturday, 10:00–18:00 IST+91 74158 85838