Security
How we protect your account, your work, and your payment data.
Last updated · May 25, 2026
To ensure the highest level of protection for your firm's data, Architools undergoes rigorous, independent security testing by StrayBit International. Our most recent third-party penetration test, completed in May 2026, evaluated our platform against leading global cybersecurity standards. To stay ahead of emerging threats, we commit to comprehensive third-party audits at least once a year, as well as following any major updates to our infrastructure.
This page describes the security controls that protect your data, project files, and designs across all Architools products. If you believe you've found a security issue, please email security@architools.netsee the responsible disclosure section below.
1. Authentication & Identity
Sign-in is powered by Google Cloud's enterprise-grade infrastructure. We never store passwords in plaintext. Google handles hashing, rate-limiting, and breach detection using the same systems that protect native Google accounts. Sessions expire automatically after a period of inactivity to prevent unauthorized access to your workspace.
2. Transport & Infrastructure Security
All data transmitted to and from Architools is encrypted in transit using industry-standard HTTPS and TLS 1.3. We utilize strict browser security policies (including HSTS and Content Security Policies) to actively protect your sessions against downgrade attacks, clickjacking, and cross-site scripting (XSS).
3. Data Access, Isolation & Privacy
Your account data is securely stored in Google Cloud's EU multi-region databases, ensuring high availability and strict adherence to European data privacy standards. Rigorous database security rules enforce strict per-user access: you have exclusive access to your own profile, subscriptions, and project data. Cross-origin requests to our backend are strictly verified and locked down to authorized endpoints.
4. Payments & Billing
Architools does not store, process, or transmit your credit card details. All financial transactions are securely handled by our Merchant of Record, a fully PCI DSS-compliant provider. Checkout occurs on their dedicated infrastructure, and our systems rely on cryptographically verified webhooks to grant subscription access, ensuring your payment data remains entirely isolated from our databases.
5. Monitoring & Vulnerability Management
We continuously scan our systems and third-party dependencies for known vulnerabilities and apply patches rapidly. Server-side secrets and credentials are fully isolated in secure vaults. We also utilize privacy-first error monitoring (hosted in the EU) to capture system errors without exposing your personal or project data, allowing us to fix issues proactively.
6. Responsible Disclosure
If you discover a vulnerability, please report it privately to security@architools.net before disclosing it publicly. We commit to:
- Acknowledge your report within 3 business days.
- Provide a fix or mitigation timeline within 14 days, or explain why a fix is not feasible.
- Publicly credit you for the finding (with your permission) once the issue is resolved.
- Not pursue legal action against security researchers acting in good faith and following this policy.
For general support questions, please use support@architools.net instead.
7. Updates to This Page
As our security posture evolves we'll update the controls listed here. Major changes will be noted at the top of the page along with the revision date. This page sits alongside our Privacy Policy and Terms of Service.