How Aiara handles your data
Full transparency on data flows, sub-processors, security measures and data processing agreements — all directly available for download.
Data Processing Agreement (DPA)
Pursuant to Art. 28 GDPR and Art. 9 FADP (revised Swiss FADP)
We provide the DPA as a ready-to-sign document. Please download the version in your preferred language, complete it and send the signed copy to support@aiara.ch — we will counter-sign promptly.
Current version: 1.0 · Effective: 2026-01-01
Sub-Processors
These providers process data on our behalf — fully listed in the DPA.
| Provider | Place of processing | Purpose |
|---|---|---|
Sidora AG Hosting infrastructure | 🇨🇭 Switzerland | Hosting of the Aiara application, database, backups |
Brevo (Sendinblue SAS) Transactional e-mail | 🇫🇷 EU | Sending of system e-mails (activation, reports, warnings) |
Stripe Payments Europe Ltd. Payment processing | 🇮🇪 EU | Subscription billing — no website-visitor data |
We notify existing customers of any change to this list at least 30 days in advance via e-mail.
Technical and Organisational Measures
Security measures pursuant to Art. 32 GDPR and Art. 8 FADP.
Encryption in transit
All connections exclusively over TLS 1.2 or higher. HSTS enforces HTTPS.
Encryption at rest
Database backups are stored encrypted. Passwords are stored exclusively as bcrypt hash.
IP pseudonymisation
Raw IP addresses are never stored. Instead, a non-reversible SHA-256 hash with a server secret is used.
Tenant isolation
Strict data separation via organization_id at application and database level. Three-layer domain lock.
Backups & recovery
Daily backups, redundantly stored, 7-day retention with point-in-time restore. RTO under 24 h.
Access control
SSH access exclusively via key auth. Multi-factor for administrative access. Role-based authorisation.
Audit logs
Consent logs are immutable (append-only). Data changes are logged with timestamp and user reference.
Domain lock
Three layers: server middleware (Origin/Referer), per-domain CORS, client-side hostname check.
What is stored where?
Locally in the visitor's browser, or on our servers in Switzerland.
aiara_banner_configBanner configuration (layout, colors, texts). Performance cache, 1 hour TTL. No personal data.
aiara_consentVisitor's consent decision, 12 months. SameSite=Lax.
aiara_vidPseudonymous visitor ID (UUID v4), used solely for consent record. 12 months. Origin-bound — no cross-site tracking possible.
GET /api/v1/banner/{id}GET endpoint for banner configuration. No personal data in request or response.
POST /api/v1/consent/{id}POST endpoint with visitor ID, consent decision, action, URL. Server stores IP hash (SHA-256), never the raw IP.
Questions about data processing?
We typically respond to data protection or compliance enquiries within one business day.
support@sidora.ch