Trust & security
held to our own control set.
TryTrustable runs on TryTrustable. The same continuous evidence collection we sell is what produces our own posture, and our trust portal is the same product our customers publish to their buyers.
Read-only by default, isolated by tenant
Integrations use scoped read-only credentials. There is no agent running in your production environment, and no path by which one tenant's evidence can be read by another.
- Read-only, least-privilege integration credentials
- Row-level tenant isolation in the data layer
- Encryption in transit and at rest, keys rotated
- No customer data used to train models
- Hosted in India (Google Cloud, Mumbai) today; expanding to Singapore, the US and the EU
Least data, shortest life
The consent ledger stores a salted hash prefix of an IP, never the address. Evidence is redacted for PII before it leaves your environment when you ask it to be.
- Salted hash prefixes instead of raw IPs
- PII redaction on evidence, on by default
- Configurable retention per evidence class
- Export and deletion on request, without a support ticket
Found something? Tell us first.
Email security@trytrustable.com with steps to reproduce. We acknowledge within one business day, keep you updated weekly, and will not pursue legal action against good-faith research that respects customer data.
- Acknowledgement within 1 business day
- Fix or mitigation target: 30 days for critical
- Public credit if you want it
Send us your security questionnaire.
We will fill it in from our live posture on the call rather than mailing it back in a fortnight.
Read-only by default, isolated by tenant
We audit other companies' controls, which makes our own posture the first thing a serious buyer asks about. The short version: we take the least access that lets the product work, and we hold ourselves to the control set we ship.
| Area | What we do |
|---|---|
| Integration access | Read-only credentials and scopes on every integration. We do not take write access to customer cloud accounts, and the SDK performs no remediation on your behalf |
| Tenant isolation | Every query is scoped by organisation at the data layer, not by application convention. Cross-tenant access is a schema-level impossibility rather than a code review responsibility |
| Encryption | TLS in transit; encryption at rest on all stores, including backups. Secrets held in a managed secret store, never in environment files or images |
| PII redaction | Redaction runs inside the customer's process before anything is transmitted. We collect the shape of a data flow, not the values moving through it |
| Data residency | All customer data is hosted in India, on Google Cloud in Mumbai (asia-south1), today. We are expanding to Singapore, the US and the EU, and will list each region here when it is live |
| Access control | Role-based access internally, reviewed on a schedule, with access to production data logged and attributable to a person |
Least data, shortest life
The cheapest way to protect data is not to hold it. Evidence is collected as attestations and hashes wherever a hash will do, rather than as copies of the underlying artefact, and retention runs on a schedule with deletion enforced rather than documented.
This is also why the free tools on this site are built the way they are. Four of the five run entirely in the visitor's browser and transmit nothing, because a policy generator that collected company data in order to produce a document would be holding exactly the kind of data we tell customers to minimise.
Responsible disclosure
If you have found a vulnerability, we want to hear about it before anyone else does. Write to security@trytrustable.com with enough detail to reproduce it. We acknowledge within two business days, keep you updated while we fix it, and credit you publicly if you would like to be credited.
We ask for the usual courtesies: give us reasonable time to remediate before disclosing, do not access or modify data belonging to anyone else, and do not run tests that degrade service for other customers. We will not pursue legal action against researchers who follow those terms in good faith.
Certification, stated plainly
A platform that asks customers to trust it should be exact about where it stands rather than implying more than is true. Certification is in progress, not complete. We will say so on this page, with dates, when each is achieved, and until then you should treat the controls described above as claims we are willing to evidence on request rather than as independently attested facts.
Send us your security questionnaire and we will answer it from live control state rather than from memory. If a control is not in place, the answer will say so.
The things people ask us
Do you take write access to our cloud accounts?
No. Every integration uses read-only credentials and scopes, and the SDK performs no remediation on your behalf. Nothing we run changes state in your environment.
How is customer data isolated between tenants?
Every query is scoped by organisation at the data layer rather than by application convention, so cross-tenant access is prevented by the schema rather than by remembering to add a filter in code.
Where is our data stored?
In India, on Google Cloud in Mumbai (asia-south1), for every customer today. We are expanding to Singapore, the US and the EU.
Do you store the personal data the SDK observes?
No. Redaction runs inside your process before anything is transmitted, so what we receive is the shape of a data flow rather than the values passing through it. Evidence is stored as attestations and hashes wherever a hash is sufficient.
Are you SOC 2 or ISO 27001 certified?
Certification is in progress and not yet complete. We will state each certification on this page with its date when it is achieved. Until then the controls described here are claims we will evidence on request, not independently attested facts.
How do I report a security vulnerability?
Email security@trytrustable.com with enough detail to reproduce the issue. We acknowledge within two business days and keep you updated until it is fixed. We will not pursue legal action against researchers who give us reasonable time to remediate and who avoid accessing other customers' data.