Security at YARDtwin

YARDtwin runs on Microsoft Azure with Norway East compute and Sweden Central for data, registry, and secrets. All customer data stays within the EU/EEA, compliant with GDPR Articles 44–49.

• App Service (Linux Container) — Norway East
• Azure PostgreSQL Flexible Server — Sweden Central
• Azure Blob Storage — Norway East, private containers
• Azure Key Vault — Sweden Central, RBAC-controlled
• Azure Front Door + WAF — Prevention mode
• Log Analytics + Microsoft Sentinel — 90-day retention

All customer data is stored and processed within the EU/EEA — hosted in Microsoft Azure’s Ireland and West/North Europe regions. Creation of resources outside the approved EU regions is blocked at the platform level by an Azure Policy “Deny” rule, so customer data cannot be provisioned outside the EU/EEA. Where a limited-scope sub-processor operates outside the EU (for example AI OCR or email delivery), transfers are governed by EU Standard Contractual Clauses and only the minimum data necessary is sent.

YARDtwin uses a small, vetted set of sub-processors to deliver the service. Each is bound by a Data Processing Agreement. We maintain this register and notify customers of material changes in line with GDPR Article 28.

YARDtwin uses AI to read driver licences and shipping documents (OCR), to power the in-app assistant, and to generate voice guidance. AI processing is assistive: its output is presented to a person — for example a gate operator confirms every check-in — and YARDtwin does not make automated decisions producing legal or similarly significant effects on individuals (GDPR Article 22).

• Customer data is not used to train third-party AI models — our AI sub-processors process data only to return a result for your request.
• Data minimisation: AI document OCR can be switched off per site, so sites that prefer manual entry never send documents to an AI provider.
• Human oversight: extracted fields are reviewable and editable before they are committed to the record.

Strict CSP with per-request nonces on scripts (no unsafe-inline). Full set of security headers returned on every response: HSTS, X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy, Cross-Origin-Opener-Policy, Cross-Origin-Resource-Policy.

Independent penetration testing on 17–18 April 2026 (10 OWASP categories, 36 payloads): 0 vulnerabilities.Functional security testing on 11 April 2026 covering 1,890+ API calls across 270 appointments: 0 failures.Annual third-party pentest scheduled and SOC 2 Type II audit in progress.

• EU GMP Annex 11 — Data integrity (ALCOA+), append-only audit trail, electronic records, access control, validated
• 21 CFR Part 11 — Electronic records, audit trail, attribution, seal chain of custody
• GDPR — Data portability (JSON + CSV), DSAR workflow, consent tracking, EU/EEA-only residency
• SOC 2 Type II — Audit in progress

• Data Processing Agreement (DPA) template — for enterprise review & signature
• GDPR policy
• Privacy policy
• security.txt

We welcome reports from security researchers. Email admin@yardtwin.comwith a description of the finding and steps to reproduce. We acknowledge receipt within 2 business days and aim to patch critical issues within 7 days. Please do not publicly disclose vulnerabilities before we have had a chance to remediate.