Contact
What are you writing about?
Reach the right person directly. All three channels are read.
- Channels
- 3
- Languages
- TR · EN
- Vulnerability reports
- security@
- Demo
- 30 min
Channels
Where to write.
Sales and scoping
Your user count, your request volume, and which tier fits. Pricing is discussed here.
sales@trustlayersec.comSecurity review
The architecture document, control list, data processing agreement; and vulnerability reports.
security@trustlayersec.comTechnical support
Questions about an existing deployment, and incident reports.
support@trustlayersec.comSupport
Support by tier.
Response-time targets are set in the contract; quoting a number without knowing your scope would be meaningless.
| plan | support |
|---|---|
| Starter / Team | Email support |
| Business | Priority support with an SLA |
| Enterprise | Dedicated account manager |
Why is there no uptime figure on this site?
Because the architecture deliberately protects auditability ahead of availability: if the audit record cannot be written, the request is not processed. That is a design decision to stop rather than quietly operate off the record, and it honestly prevents us from committing to a high availability percentage on a single-instance deployment. The availability target is defined in the contract once your deployment topology is settled.