A platform designed for privacy and data security

Security measures

• Data location

  • In the cloud deployment, all application data, files and AI processing are kept in the Microsoft Azure Sweden (Sweden Central) region, within the European Union.
  • Database backups are copied to the paired region within the EU (Sweden South); email service data is stored in the European data location.
  • AI calls are processed within the EU data boundary using an Azure OpenAI “Data Zone” deployment.

• Encryption

  • All traffic runs over HTTPS with TLS 1.2 or higher; HTTP requests are redirected to HTTPS.
  • The database, file storage and cache are encrypted at rest with Azure-managed keys.
  • Organization secrets such as SMTP passwords and OAuth tokens are additionally encrypted at the application layer with AES-256-GCM; infrastructure secrets are kept in Azure Key Vault and accessed by services via managed identity.

• Tenant isolation

  • Each organization’s data is separated with PostgreSQL Row Level Security: the application runs with a restricted database role that can only see the rows of the organization in the current session.
  • In addition to RLS, queries are explicitly filtered by organization ID; administrative operations run under a separate role and a separate session.

• Authentication and access

  • Passwords are hashed with argon2id; minimum 10 characters, with uppercase and lowercase letters, a digit and a special character.
  • Sessions use httpOnly cookies; rate limits on login and password reset endpoints.
  • The Survai admin panel runs on a separate domain, with mandatory two-step verification (TOTP) and support for IP restrictions.
  • Within each organization, Owner, Admin, Editor, Analyst and Viewer roles and per-survey access permissions.

• Audit log

  • Customer account, limit, user, invitation and survey actions are logged with the date, person and action.
  • Logs are kept in the Survai admin panel; they can be filtered and exported as CSV.

• Backup and continuity

  • The production database runs with zone-redundant high availability; 35-day point-in-time restore and geo-redundant backups.
  • File storage is protected with geo-zone-redundant storage (GZRS), versioning and 30-day soft delete.
  • Applications run as at least two instances across multiple availability zones.

• Network and edge security

  • In production, the database, cache, file storage, key vault and AI service are accessed through private network endpoints and are not exposed to the internet.
  • Web application firewall (WAF) on Azure Front Door: Microsoft default rule set, bot management and rate limiting.
  • Uploaded files are scanned for malware with Microsoft Defender for Storage.

• Anonymity and data minimization

  • In anonymous surveys, no link between a response and the participant is stored.
  • Groups with fewer than 5 responses are not shown in analytics screens, comparisons, the PDF report or Ask AI.
  • In anonymous surveys, values such as department, location or job title that fall into a group with fewer than 5 responses are shown as “Hidden (<5)” in the response list, CSV / XLSX exports and the REST API; these surfaces are also available only to authorized roles and API keys.
  • On a participant erasure request, personal data is anonymized; responses remain anonymous for statistical purposes only.

• Data processing controls for AI

  • Only masked, aggregated results are sent to Ask AI; no sample response text, names or email addresses are sent.
  • In sentiment and theme analysis, open-ended comments are sent to the model after email addresses, phone numbers, ID and employee numbers, links and participant names are removed by automated rules.
  • Only Microsoft’s first-party Azure OpenAI Service is used; access is via managed identity rather than API keys.
  • Microsoft commits not to use customer data sent to Azure OpenAI to train models.
  • AI can be turned off per organization; drafting, suggestions and Ask AI are limited by a monthly quota.