At Airstudio, each customer’s data is fully isolated using PostgreSQL database schemas, meaning every account has its own dedicated logical database within our PostgreSQL instance. This ensures no data is ever commingled between accounts — each customer operates in a secure, segregated environment.

When an account is closed, we delete the entire PostgreSQL schema associated with that account, permanently removing all data related to the customer — including files, metadata, user records, and any other stored information.

This architecture not only guarantees strong data isolation and security while the account is active, but also provides a clean and complete data deletion path when a customer chooses to leave the platform.

Active Account Isolation & Security

Each customer’s data is stored in its own dedicated PostgreSQL schema, providing strict logical separation of customer data:

• Access controls enforce query-level isolation so data is only accessible within the correct schema.
• No cross-account access is possible due to tenant-aware application logic and enforced scoping.
• We follow multi-tenant best practices:
  • Schema-level boundaries for logical isolation
  • Enforced tenancy checks on all operations
  • Limited, role-based access for internal tools

Network & Connection Security

Our database infrastructure is deployed within private subnets inside an AWS VPC:

• Not publicly accessible — only internal services with explicit permissions can connect.
• Protected by VPC security groups, IAM roles, and TLS encryption in transit.
• We use PEM certificates for database authentication, ensuring secure, encrypted connections between services.

Data Encryption at Rest and in Transit

All data stored in our database and file storage systems is encrypted at rest using AES-256 encryption, managed through AWS Key Management Service.

Data is also encrypted in transit using TLS, protecting all communication between application components.