Placeholder template. This page is a structured draft for review. It is not legal advice and must be completed and approved by qualified counsel before publication. Replace all bracketed items.
Our approach
Security is designed into our engineering process from the start, including for agentic systems that use tools and act on data.
- Encryption in transit (TLS/HSTS) and at rest for systems we operate.
- Least-privilege access, multi-factor authentication, and access reviews.
- Secure development practices, dependency scanning, and code review.
- Defined permissions, execution boundaries, and human approval for sensitive agent actions.
- Logging and monitoring to investigate failures and incidents.
- Vendor review for sub-processors. [ADD SUB-PROCESSOR LIST]
Compliance
[STATE ONLY WHAT IS TRUE — e.g. "SOC 2 Type II report available under NDA" or "aligned with NIST CSF / ISO 27001 controls". Do not claim certifications that are not held.]
Responsible disclosure
If you believe you have found a security vulnerability, please email support@adbyrd.com with the subject "Security Report" [OR a dedicated security@ address]. Include steps to reproduce. Please do not access data that isn't yours, degrade service, or publicly disclose before we have had a reasonable time to respond. Our security.txt is available at /.well-known/security.txt.
Data processing agreements
A Data Processing Agreement (DPA) is available for client engagements on request.