Security & Privacy

Industrial product data is sensitive. Here is exactly how we handle it, and how we have designed AAS Studio so that most of your data never reaches our servers at all.

How we protect your data

Browser-local by default
The AAS editor runs entirely in your browser. Your product data, schemas, and files are never transmitted to our servers. Only the AI extraction feature sends data: text-only for standard extraction; the full source PDF for scanned documents and the battery-passport regulation path, which use vision/OCR by default. The output is never sent anywhere.
SHA-256 cryptographic anchoring
Every AI-extracted AAS file is anchored to a SHA-256 hash of the source PDF. The hash is embedded in the AAS metadata, creating a tamper-evident audit trail for regulatory liability.
Tamper-evident audit ledger
Sign, verify, and access-grant actions are recorded in an append-only, hash-chained ledger, partitioned so one tenant's chain can never reach another's. Verify your own chain hasn't been altered or truncated: GET /api/v1/audit-ledger?verify=1 (Bearer key required, scoped to your own tenant).
Human-in-the-loop certification
AI extraction requires an engineer to review and approve field values before import. Engineer initials and a timestamp are embedded in the AAS description, creating a documented review record.
Cloud models on isolated Neon Postgres
When you save models to the cloud, they are stored in a dedicated Neon Postgres database. Isolation is enforced in the application layer: every query is scoped to your account or your organization, so you can only reach your own models. Postgres row-level security is not enabled (ADR 005), and we would rather say that than imply a database-level control we do not have.
Automatic versioning
Every model save creates a snapshot and you can restore any previous version. Snapshots are not pruned on a schedule, so they persist until you delete the model or the account.
Authentication via Clerk
We use Clerk for all authentication. We do not store passwords. Sign-in supports Google, Microsoft, and email OTP. OIDC single sign-on against your own identity provider is available on a self-hosted deployment. SAML is NOT implemented; the page said otherwise until 2026-08-05.

Sub-processors

AAS Studio uses the following sub-processors. All data transfers comply with GDPR Chapter V (Standard Contractual Clauses).

Neon
Postgres database (cloud models, usage)
EU (Frankfurt)
Clerk
Authentication & user management
EU residency available
Anthropic / OpenAI / Google / xAI
AI extraction. Text-based extraction sends PDF text only; vision/OCR extraction (default for scanned documents and battery-passport regulation) sends the full source PDF to Anthropic and Google
USA (SCCs in place)
Vercel
Application hosting & CDN
Global (EU region on Enterprise)
Resend
Transactional email
USA (EU residency available, SCCs in place)
Sentry
Error monitoring. No-op unless configured; PII collection is disabled and only already-redacted error-level log entries + stack traces are sent, never request bodies or headers verbatim
USA (SCCs in place)

Frequently asked questions

Does AAS Studio send my product data to any third party?
No. The editor runs locally in your browser. Product data never leaves your device unless you explicitly use AI extraction or save to cloud. For text-based AI extraction, only the extracted PDF text is sent to the LLM provider (Anthropic, OpenAI, Google, or xAI depending on your key). For scanned documents and for the battery-passport regulation path, vision/OCR extraction runs by default and sends the full source PDF to Anthropic and Google. The output AAS file is generated in your browser.
What data is stored on your servers?
If you use the cloud library: your AAS file content, the model name, and metadata. If you use AI extraction: a usage count record (no file content). Your Clerk profile (email, name) is stored for authentication. We do not log request bodies.
What is your uptime SLA?
We do not offer one, and would rather say so than write a number we cannot stand behind. AAS Studio is operated by one person: there is no on-call rotation and no 24/7 monitoring, so a promise of 99.9% availability with a four-hour incident response would be a contractual commitment backed by nothing. This page carried exactly that promise until 2026-08-05. What is true instead: the editor runs in your browser and keeps working while our servers do not, the validator and the CLI gate run offline, and a signed record can be verified without us at all. An availability commitment can be negotiated as part of a self-hosted engagement, where the infrastructure is yours.
Do you have a data processing agreement (DPA)?
Yes. Enterprise customers receive a DPA on request. For GDPR compliance, AAS Studio processes data under EU Standard Contractual Clauses with all sub-processors including Neon (Postgres), Clerk (auth), and Anthropic (AI).
Can I self-host AAS Studio?
The editor component is open-source under MIT license. Enterprise customers can receive a private deployment package including the full Next.js application. Contact us for details.
Enterprise security requirements?

A data processing agreement, EU-region deployment, OIDC single sign-on and audit log export are available as part of a self-hosted engagement. We have NOT commissioned a third-party penetration test, so there is no report to send you; this page offered one until 2026-08-05.

Contact security team

Command palette

Navigate + run actions