Skip to main content

trust

Trust

Last updated 23 October 2026

01

Trust at Adroyt

Security and compliance are foundational to Adroyt. We build every layer of the platform with security-first principles — encryption at rest and in transit, hardened infrastructure, least-privilege access, and continuous compliance with the standards enterprise procurement teams ask about. This page is the single source of truth for our security posture, certifications, and the way we handle data.

02

Data Encryption

At Rest

All data stored on Adroyt servers is encrypted using AES-256. Database backups are encrypted using the same standard.

In Transit

All data transmitted between your browser and Adroyt is protected with TLS 1.2 or higher. We enforce HSTS and HTTPS across all endpoints.

03

Infrastructure Security

  • Hosted on infrastructure providers that hold SOC 2 Type II reports (DigitalOcean, Supabase)
  • Network segmentation and private subnets for databases
  • Web Application Firewall (WAF) protecting all endpoints
  • DDoS mitigation at the network edge
  • Automated vulnerability scanning of all container images and dependencies

04

Access Controls

We follow least-privilege principles throughout:

  • Role-based access control (RBAC) at the application and infrastructure level
  • SSH access via short-lived certificates only
  • All production access is logged and audited
  • Tenant data is strictly isolated — no cross-tenant data access

Multi-factor authentication

Adroyt supports TOTP-based multi-factor authentication with single-use recovery codes, and every user can enrol a second factor today. To be straight about where we are: MFA is not yet enforced at sign-in, and enforcement is a per-tenant setting under the customer administrator's control rather than something we mandate across all tenants. A remediation programme is in progress. We would rather tell you this than have you find it, and we are happy to share the specific findings and their fixes under NDA — email [email protected].

05

Certifications & Frameworks

SOC 2 Type II

Adroyt's controls are built to align with the SOC 2 Trust Service Criteria for Security, Availability, and Confidentiality. A SOC 2 Type II examination has not yet been started; formal third-party certification is on our roadmap. Enterprise customers can contact [email protected] for our current control documentation.

GDPR

Adroyt acts as a data processor for customer personal data under the EU General Data Protection Regulation. Our commitments include lawful basis for all processing activities, Standard Contractual Clauses (SCCs) for international transfers, support for right to erasure and data portability, and 72-hour breach notification. The standalone Data Processing Agreement lives at adroyt.io/dpa.

CCPA / CPRA

Adroyt complies with the California Consumer Privacy Act and its amendments. We do not sell personal information to third parties. California residents may exercise their rights by contacting [email protected].

ISO 27001

Our security program draws on ISO/IEC 27001:2022. Adroyt is not ISO 27001 certified; formal third-party certification is on our roadmap.

06

Data Residency

Adroyt customer data is stored in the European Union — a single PostgreSQL database in Frankfurt, Germany (AWS eu-central-1), with the application and cache hosted in Frankfurt as well.

Stored data is not the same as processed data. When you use AI features, the content of the request is processed by Anthropic in the United States. OpenAI, also in the United States, is the fallback if Anthropic is unavailable.

You can record a preferred region in Settings, and we disclose our sub-processors against it, but we do not currently enforce region-specific physical storage: every tenant's data is in Frankfurt regardless of the preference set. Per-region storage is on our roadmap and is not available today. Transfers to sub-processors outside the EEA are covered by EU Standard Contractual Clauses.

If you have a residency requirement we cannot meet today, we would rather tell you now — contact [email protected].

07

Accessibility

Adroyt is designed to be usable by everyone, including people with visual, auditory, motor, and cognitive disabilities. Adroyt targets WCAG 2.2 Level AA across the product. We are not claiming conformance: we have open, tracked Level AA defects, and they are listed under Known limitations below.

Standards we build against

  • WCAG 2.2 AA — Web Content Accessibility Guidelines (W3C). Our target; not yet met in full.

We have not published a VPAT or Accessibility Conformance Report, so we do not claim conformance to any government procurement accessibility standard. If you need a formal ACR for procurement, contact [email protected] and we will tell you where we are.

How we verify

We run an automated accessibility suite — axe-core 4.13, Lighthouse, keyboard-navigation and focus-indicator checks — against our own screens, and a separate axe sweep against the live public site. The sweep is currently informational: it reports violations, it does not yet block a release. Making it a release gate is in progress. Today's public-site results: /login and /register pass with zero violations; the marketing homepage has one open contrast defect, described below.

Screen reader support

Adroyt is tested against the two most common screen-reader / browser pairings:

  • NVDA with Mozilla Firefox
  • VoiceOver with Apple Safari

Our automated suite checks the machine-verifiable parts of screen-reader support on every run: landmark structure, heading hierarchy, skip links, and an accessible name on every button, link and form control. We maintain a written manual-testing protocol covering three critical flows. The first manual session has not yet been run; when it is, it will be logged.

Keyboard navigation

Interactive elements in Adroyt are reachable using only the keyboard, with the documented exception below. Tab order follows the visible reading order, focus indicators are visible, and modals return focus to the triggering element on close. The AI side panel is fully inert when closed so it does not leak focusable children into the tab order.

Contrast

Contrast is checked automatically in both the dark and light themes against the WCAG AA thresholds (4.5:1 body text, 3:1 UI components and large text). One open defect: 43 elements on the public marketing homepage currently fail the AA body-text threshold. It is tracked and being fixed. The authenticated product has not yet been swept in production.

Known limitations

  • Gantt charts and complex data visualisations have limited screen reader support — we provide equivalent tabular data views as a fallback.
  • Custom drag-and-drop interactions in the Kanban board do not currently expose a keyboard-only alternative. A keyboard DnD pattern is in the roadmap.
  • Some interactive elements are missing accessible labels; a fix is in flight.

Reporting an accessibility issue

If you encounter an accessibility barrier, please email [email protected]. We aim to respond within two business days and, for WCAG-level failures, ship a fix in the next release cycle.

08

Vulnerability Disclosure

We operate a responsible disclosure programme. If you discover a security vulnerability, please report it to [email protected]. We aim to acknowledge reports within 3 business days and will keep you informed while we investigate and fix the issue. We do not pursue legal action against good-faith researchers.

09

Contact

By topic: