Security
CAIQ v4 self-assessment
Last updated 16 November 2026.
This is the aiteam.space self-assessment against the Cloud Security Alliance CAIQ v4.0.3 (Cloud Controls Matrix v4). It is a self-assessment: no third party has audited it, and it is not a certification.
It lists the 18 controls that are in place on aiteam.space today, with how each one is met. Every control listed is answered Yes. Controls that are not listed are not claimed.
AIS · Application and Interface Security
- AIS-04 Secure Application Design and Development
- Every page is served with an enforced Content Security Policy that carries a new nonce on each request. HTTPS is enforced with HSTS (two years, preload). Other sites cannot frame our pages; the one exception is the Telegram mini app page, which only Telegram's web client can frame. Browsers are told not to guess content types.
- AIS-05 Automated Application Security Testing
- Every change runs the site's automated checks before release: type checks plus more than a hundred scripted checks, including checks on the security headers, the session cookie and cross-site requests.
- AIS-06 Automated Secure Application Deployment
- Production is built and deployed by a scripted pipeline from the main branch. The live site is not edited by hand.
CCC · Change Control and Configuration Management
- CCC-04 Unauthorized Change Protection
- The main branch accepts changes only through a reviewed pull request. Direct pushes are refused by a repository rule.
CEK · Cryptography, Encryption and Key Management
- CEK-03 Data Encryption
- Data is encrypted in transit: every request is served over HTTPS. Site data is stored encrypted at rest in Untrace Vault, with a separate data key for each collection.
DSP · Data Security and Privacy Lifecycle Management
- DSP-07 Data Protection by Design and Default
- Sign-in link and session tokens are stored only as SHA-256 hashes. Email addresses never appear in storage keys in clear. Client IP addresses are hashed before use and never stored raw. Card details go straight to the payment processor and never reach us.
- DSP-11 Personal Data Access, Reversal, Rectification and Deletion
- From Settings, a signed-in person can download everything we hold about them as a JSON file, and can delete their account. Deletion stops and deletes their Sons, cancels billing, revokes connected apps, ends every session and erases the account after 7 days.
- DSP-14 Disclosure of Data Sub-processors
- Every sub-processor and what it processes is listed in section 5 of the Privacy Policy.
- DSP-16 Data Retention and Deletion
- Retention periods are published in section 6 of the Privacy Policy. Sign-in links expire after 15 minutes and sessions after 30 days. An hourly job finishes account erasures when their 7 days are up.
IAM · Identity and Access Management
- IAM-05 Least Privilege
- Team members get one of five roles: Owner, Admin, Developer, Reviewer or Viewer. Each action checks the capability it needs, not a rank. A Viewer changes nothing.
- IAM-07 User Access Changes and Revocation
- Team admins can change a member's role or remove the member. Signing out deletes the session on our side, not only in the browser.
- IAM-13 Uniquely Identifiable Users
- Every account is one verified email address. Sign-in is by a single-use link or code sent to that address, or by Google sign-in.
- IAM-15 Passwords Management
- aiteam.space accounts have no password. Sign-in links are single use, expire after 15 minutes and are rate limited per email address and per network. The setup chat refuses messages that look like a password or key.
- IAM-16 Authorization Mechanisms
- Session cookies are HttpOnly, Secure and SameSite. Any state-changing API call from another site, including other aiteam.space subdomains, is refused before the session is read.
IPY · Interoperability and Portability
- IPY-02 Application Interface Availability
- Personal data can be exported at any time in a machine-readable JSON file from Settings, without contacting us.
IVS · Infrastructure and Virtualization Security
- IVS-05 Production and Non-Production Environments
- Staging runs on its own copy of the data, behind access control, with its own credentials. It never holds production credentials.
- IVS-06 Segmentation and Segregation
- Each Son runs in its own private container.
STA · Supply Chain Management, Transparency and Accountability
- STA-07 Supply Chain Inventory
- Third-party code is pinned by a lockfile and installed from it exactly. Third-party licences are listed in the repository.
Questions
Write to hello@aiteam.space for the questionnaire in the CSA spreadsheet format or for any control not listed here. How we handle personal data is in the Privacy Policy.