Security

Your data stays yours

Spreadsheets and databases hold some of your most sensitive information. Here is exactly how GPTExcel protects it, and what we're adding next.

  • AES-256 at restFiles, data and credentials
  • TLS in transitHTTPS only, everywhere
  • No AI trainingYour data never trains models
  • Isolated sandboxSecure VM for each session
  • Read-only databasesOnly the tables you choose
  • GDPR-readyConsent, access and deletion

Last updated November 21, 2026

Standards we follow

  • GDPR
    In place
    GDPRRights, consent and deletion
  • AES-256
    In place
    AES-256Encryption at rest
  • TLS
    In place
    TLSEncryption in transit
  • No training
    In place
    No AI trainingOn any customer data
  • Limited use
    In place
    Google API Limited UseFor Google Drive data
  • SOC 2Type I
    Planned
    SOC 2 Type IIndependent audit
  • SOC 2Type II
    Planned
    SOC 2 Type IIIndependent audit

In place today

How we protect your data

In place

Encryption

Your data is encrypted wherever it is stored and whenever it moves.

  • Files and account data are encrypted at rest with AES-256.
  • All traffic uses HTTPS, and browsers are told never to connect without it.
  • Database passwords and connected-account tokens get a second, separate layer of encryption, each bound to its owner.
  • Server secrets are kept in dedicated secret stores, never in source code.
In place

Data isolation and access

Your chats and files are private to you unless you choose to share them.

  • Every request is checked on our servers against the signed-in account.
  • Files are downloaded through short-lived signed links, never public URLs.
  • Shared chats are read-only snapshots, and you can revoke a link at any time.
  • Teams have owner, admin and member roles; only owners and admins manage team files and billing.
In place

Code sandbox

When GPTExcel analyzes a file, the code it writes runs in an isolated sandbox, never on our application servers.

  • Each session runs in its own secure VM, separate from every other user's.
  • Code runs with least privilege and can only reach the files of the chat it's working on.
  • The sandbox has no general internet access.
  • Sandbox images are scanned for known vulnerabilities before release.
In place

AI and your data

We use leading AI models through business agreements built for customer data.

  • Your files, chats and query results are never used to train AI models, ours or our providers'.
  • Only what a request needs is sent: the question, the relevant part of the chat, and the data the analysis reads.
  • Answers about new spreadsheet functions are checked against official documentation, with the source linked.
In place

Database connections

Connect PostgreSQL, Supabase or Neon without giving GPTExcel the power to change anything.

  • Statements are checked before they run and run read-only, so your data can't be changed.
  • Only the tables you choose can be queried.
  • Very expensive queries wait for your approval.
  • Connections are encrypted and verify the server's certificate by default.
  • We give you a script to create a read-only database user, and recommend it.
In place

Google Drive and OneDrive

Connectors are optional and ask only for what they need.

  • Google Drive uses Google's narrowest file permission: GPTExcel only sees files you pick or save through it.
  • OneDrive files are opened only when you pick them or save to OneDrive, and our OneDrive app is from a Microsoft verified publisher.
  • Disconnecting deletes the stored credential.
  • Our use of Google user data follows the Google API Services User Data Policy, including its Limited Use requirements.
In place

Accounts and sign-in

No passwords to leak: you sign in with Google, Microsoft or a one-time email link.

  • Sessions are kept in secure cookies that page scripts can't read.
  • Requests are rate limited to block abuse and runaway automation.
In place

Application security

Defenses built into the web app itself.

  • A strict Content Security Policy limits what the site can load and stops other sites from framing it.
  • Uploaded workbooks are read as data; macros are never run.
  • Analytics and marketing scripts only load after you consent.
GDPR
In place
GDPR-ready

Privacy and GDPR

We follow the GDPR's principles for everyone, wherever you are. The details are in our Privacy Policy.

  • You can see, export and delete your data. Deleting your account removes your chats, files, connections and team memberships.
  • Analytics and marketing cookies only load after consent, and you can change your choice at any time.
  • We don't sell personal data.
  • International transfers rely on safeguards such as standard contractual clauses where required.

Infrastructure partners

Built on audited infrastructure

The certifications below belong to each provider, not to GPTExcel. Follow a link to check them.

What's next

Security roadmap

Where we are today, and what we're working towards. We'll update this page as items land.

  • Encryption at rest and in transitIn place
  • Isolated secure VM for each code sessionIn place
  • No AI training on customer dataIn place
  • Read-only database access, limited to the tables you chooseIn place
  • Content Security Policy and HSTSIn place
  • GDPR consent management and data subject rightsIn place
  • Responsible disclosure and security.txtIn place
  • Microsoft verified publisher for OneDriveIn place
  • Data Processing Agreement for business customersPlanned
  • Multi-factor authenticationPlanned
  • SSO (SAML / OIDC) for teamsPlanned
  • SOC 2 Type IPlanned
  • SOC 2 Type IIPlanned

Report a security issue

If you think you've found a security issue, email us the details. Our contact is also in security.txt.

contact@gptexcel.uk

Questions about security for your team? Same address, or see the connectors page for how database access works.