Security

How Aztrix protects your data and your customers' data

TLS 1.2+

Encryption in transit

AES-256

Encryption at rest

RLS

Row-level data isolation

MFA

Multi-factor authentication

Infrastructure

Aztrix owns no hardware and operates no data centers. Most of the platform runs on managed cloud services whose providers hold SOC 2 Type II, ISO 27001, and other certifications. A small number of components run on virtual servers that we administer ourselves; those are listed below, and their patching, access control, and monitoring are our responsibility rather than a provider's.

Managed services

  • Database & Authentication: Supabase, hosted on AWS in the EU. SOC 2 Type II certified, with automated daily backups and encryption at rest
  • Edge Network & WAF: Cloudflare. SOC 2 Type II, ISO 27001, and PCI DSS certified. Provides DDoS protection, Web Application Firewall, global CDN, and frontend hosting
  • Payments: Stripe. PCI DSS Level 1 certified. Aztrix never stores, processes, or transmits raw card numbers

Components we operate ourselves

  • Reverse proxy: a virtual server on DigitalOcean (EU) that terminates TLS and routes traffic for partner-branded domains
  • Email: a self-hosted mail stack on DigitalOcean (EU), with outbound delivery relayed through Resend
  • Secrets vault: a self-hosted vault on Hetzner (Germany) holding operational credentials. It stores no customer data

Data Protection

Encryption

All data is encrypted both in transit and at rest:

  • In transit: TLS 1.2 or 1.3 on all connections; older protocols (TLS 1.0 and 1.1) are refused. HSTS headers prevent protocol downgrade attacks
  • At rest: AES-256 encryption on all database storage via Supabase/AWS infrastructure
  • Secrets management: API keys and credentials are held either as encrypted environment variables or in our self-hosted vault, never in source code

Data Isolation

Every database table enforces Row-Level Security (RLS) policies at the PostgreSQL level. These policies execute inside the database engine itself — before data ever reaches the application layer. This means:

  • Users can only access their own data and data shared with them
  • Organizations are fully isolated — no cross-organization data access is possible
  • Partner accounts have scoped access limited to their managed users
  • Admin access is audited and restricted to authorized personnel

Application Security

Authentication

  • Powered by Supabase Auth with support for email/password and social providers
  • Multi-factor authentication (MFA/TOTP) available for all accounts, and required for admin access: the server accepts admin actions only from an MFA-verified session
  • Session tokens are short-lived and automatically refreshed; a session ends after 24 hours, or after 12 hours of inactivity
  • Role-based access control (RBAC) enforced at both application and database level

Input Validation & Rate Limiting

  • All user inputs are validated and sanitized server-side
  • Rate limiting protects critical endpoints (registration, verification, checkout) against abuse
  • Centralized validation library guards against injection attacks and regex denial-of-service

Secure Development

  • Code changes normally go through a pull request with a written risk evaluation and automated code and security review. Aztrix has one maintainer, so there is no second human reviewer, and some changes are pushed directly
  • Automated CI runs tests and security checks on pull requests and on pushes to the main branch. These checks flag problems; they do not block a release on their own
  • Dependencies are regularly audited for known vulnerabilities
  • Security-sensitive code paths are reviewed with additional scrutiny

Availability & Reliability

  • Multi-region deployment via Cloudflare's global edge network
  • Automated daily database backups
  • Error monitoring via Sentry with real-time alerting
  • Uptime targets and incident response procedures documented in our SLA

Privacy & Compliance

  • GDPR: We respect data subject rights including access, rectification, erasure, and portability
  • LGPD: Compliant with Brazilian data protection requirements for our BR market operations
  • Cookie consent: Granular cookie preferences with opt-in consent per our Cookie Policy
  • Data processing: Full details in our Privacy Policy

Vendor Security

We carefully select infrastructure partners based on their security certifications and track record:

VendorPurposeCertifications
SupabaseDatabase, Auth, Edge FunctionsSOC 2 Type II, HIPAA
CloudflareCDN, WAF, DDoS, WorkersSOC 2 Type II, ISO 27001, PCI DSS
StripePayment ProcessingPCI DSS Level 1, SOC 2
SentryError MonitoringSOC 2 Type II
GitHubSource Code, CI/CDSOC 2 Type II, ISO 27001

Responsible Disclosure

If you discover a security vulnerability, please report it responsibly. Contact us at [email protected]. We ask that you:

  • Do not publicly disclose the vulnerability before we have had a chance to address it
  • Provide sufficient detail for us to reproduce and fix the issue
  • Allow reasonable time for us to respond and deploy a fix

We appreciate your help in keeping Aztrix and our users safe.