Airdun Security: Data Access, Encryption, and Permissions

Airdun requests only the Stripe permissions it needs. It does not touch or store raw card data, and every workspace is isolated. This page documents how data is accessed, protected, and controlled.

​

Stripe access and recovery scope

Airdun connects to Stripe through a scoped OAuth integration with two distinct access levels:

• Reads: payment history, subscription data, customer records, and failure reasons, to detect failures and build recovery cases.
• Two kinds of write:
  • Saving the new card as default: when a payment fails on a use case you have put live, Airdun sets the subscription to keep the card the customer pays with as its default, so future renewals use it.
  • Paying an invoice (adaptive retries): when adaptive retries are on for a use case (they are by default for Renewals and Free trials; New customers has none), Airdun can pay a failed invoice through Stripe, with the payment method already on file. It is the same charge Stripe’s own retries would make, on the same invoice and for the same amount; Stripe’s retries keep running under your retry policy. Adaptive retries are turned on or off per use case.
  These are the only changes Airdun makes in your Stripe account. It does not create charges outside an existing invoice, issue refunds, or modify plans or prices.

​

Card data Airdun never stores

Airdun is not a card vault, and it is not designed to be one. The following data never leaves Stripe’s systems:

• Full card numbers (PANs)
• CVCs / CVVs
• Full bank account numbers

All payment method data lives exclusively within Stripe. Airdun works with tokenised references and metadata only (card brand, last four digits, expiry, and funding type).

​

Workspace isolation

Every Airdun account operates in a logically isolated workspace. Your payment data, customer records, and recovery activity are partitioned at the data layer: no other merchant can query, view, or interact with your workspace. Airdun employees access production data only under strict internal controls and for support purposes only.

​

Role-based permissions

You control who on your team can do what inside Airdun. Invite team members from Settings → Members as Admin or Member. Roles can be changed or members removed at any time; an Owner cannot be removed until their role is changed.

​

Encryption

• In transit: all data between your browser, Airdun’s services, and third-party providers is encrypted using TLS 1.2 or higher.
• At rest: all stored data is encrypted at the infrastructure level.
• Credentials: sensitive credentials (such as integration tokens) receive an additional layer of application-level encryption on top of the infrastructure-level encryption.

​

Authentication

Airdun does not store your password. Authentication is fully delegated to a dedicated identity provider, which handles credential storage and hashing independently of Airdun’s own systems. If you sign in with Google, your Google account’s 2-step verification applies to Airdun.

​

Infrastructure

Airdun is hosted entirely on Google Cloud Platform in the EU (Paris region, europe-west9). No data is processed or stored outside the European Union except where explicitly described in the Privacy Policy for specific third-party processors that operate under Standard Contractual Clauses.

---