Security at XPLIO
Effective date: August 9, 2026 · Version 3.0
This page describes the security controls XPLIO has in place. If you are evaluating XPLIO and need detail that isn't covered here, email security@xplio.com and we'll answer your questions directly.
1. Keeping your organization's data separate
XPLIO is multi-tenant: many organizations share one application and one database. Making your data unreachable from another organization is the most important thing we do, so we enforce it in the database itself rather than relying on application code to remember.
- PostgreSQL row-level security, in FORCE mode, on 268 tables. Every table holding organization data carries a policy restricting rows to the organization making the request. FORCE means the policy applies even to the table's owner, so a query that forgets to filter returns nothing rather than returning another organization's records.
- The organization context is bound per request and cleared when the request ends, so it cannot carry over between requests that share a database connection.
- The few genuinely cross-organization operations — platform administration, matching an incoming payment webhook before we know whose it is — go through an explicit, individually justified exception rather than by switching the protection off.
2. Where your data lives
XPLIO runs on Google Cloud Platform in the United States. The application runs on Cloud Run with no public address of its own; all traffic arrives through a single Google Cloud load balancer. The database is Cloud SQL for PostgreSQL and is not reachable from the internet. Files are stored in Google Cloud Storage. TLS certificates, including those for customer custom domains, are issued and renewed by Google Certificate Manager, so we never handle private keys.
We use a small set of other providers for specific jobs: Stripe for payments and Amazon SES for transactional email.
3. Encryption
- In transit. Traffic between your browser and XPLIO is encrypted with TLS 1.2 or 1.3, using certificates issued by Google Trust Services.
- At rest. The database and file storage are encrypted with AES-256 using Google-managed keys. This is the platform default and is not something we can switch off.
- Application layer. Third-party credentials your organization enters — payment keys, mail credentials — are encrypted with Fernet (AES-128-CBC + HMAC-SHA256) before they reach the database, so they are not readable from a database copy alone.
4. Signing in
- Passwords are hashed with scrypt (n=214, r=8, p=1), a memory-hard function chosen to make large-scale offline cracking expensive. We never store or log plaintext passwords.
- Passkeys (WebAuthn / FIDO2) are supported, giving phishing-resistant sign-in with a security key or device biometric.
- Two-factor authentication is available on any account, via authenticator app or emailed code, with single-use recovery codes.
- Single sign-on via Google, Apple, or SAML.
- Sessions are server-issued tokens held in HttpOnly, Secure, SameSite=Lax cookies. Signing out, changing a password, or losing a role ends the session immediately.
- Rate limiting on sign-in and password reset, by address and by account, to blunt credential-stuffing and account-guessing.
- Bot protection. Public forms that create records or take payment — sign-up, sign-in, giving, public forms, support requests — are protected by Cloudflare Turnstile and verified on our servers.
5. Who can see what
- Permissions are scoped to an organization. A role in one organization grants nothing in another.
- Each endpoint declares the specific action it requires and is checked individually, rather than trusting a broad "is an admin" flag.
- XPLIO staff roles are held separately from your organization's roles, and staff access to a workspace for support is time-limited and recorded.
- Security-relevant actions are written to an audit trail belonging to the organization they affect.
6. Application security
- Database queries use parameterized statements through an ORM.
- Output is escaped by the rendering framework, and every response carries a Content Security Policy.
- Every response also sets X-Content-Type-Options, X-Frame-Options, Referrer-Policy, Permissions-Policy and Cross-Origin-Opener-Policy.
7. Payments
All card processing is handled by Stripe, which is certified PCI DSS Level 1. Card numbers are entered directly into Stripe's own payment form and are never sent to, processed by, or stored on XPLIO's servers.
8. Reporting a vulnerability
If you think you have found a security problem, email security@xplio.com with what you found, how to reproduce it, and the impact you expect. We will acknowledge your report, keep you updated while we investigate, and will not pursue legal action against anyone reporting in good faith who does not access or alter other customers' data. Please give us a fair chance to fix an issue before disclosing it publicly.
9. Your data and your rights
How we collect, use, retain and delete personal data — and how to export or remove your organization's data — is covered in our Privacy Policy. You can request a full export of your workspace at any time. For a data processing agreement, email privacy@xplio.com.
Last reviewed: August 9, 2026. We rewrite this page when our controls change, not on a schedule.