StrateQX logoStrateQX
Get Your Strategy Today

Security

Last updated: August 2026

Security, for us, starts with collecting less data in the first place — not with a badge wall. Here's exactly how we think about it.

1. Our approach

The single biggest security decision we've made is architectural: most of StrateQX's tools are designed to keep your business data on your device rather than collecting it in the first place. Data you never send us can't be part of a breach on our end.

2. Data in transit

The entire site is served over HTTPS/TLS. Any information that does travel between your browser and our infrastructure — a contact form submission, a report request — is encrypted in transit.

3. Data at rest

Strategy Builder answers and similar tool inputs are stored in your browser's local storage — on your device, not our servers. Where we do hold data server-side (contact form submissions, report requests), it's kept only as long as needed to respond to you, on infrastructure operated by reputable, security-conscious hosting providers.

4. Local-first AI

Where our AI features run locally, your business context and conversation never leave the machine generating the response. When a request is routed to a hosted AI provider instead (because a local model isn't available), only the specific content needed to answer that request is sent — not a bulk export of your data.

5. No password, no account, less to lose

StrateQX's tools today don't require you to create an account or a password to get value from them. No account system means no password database to protect and no login credentials of yours that could be exposed — one less attack surface, by design rather than by accident.

6. What we don't claim

We won't tell you we hold a specific security certification (SOC 2, ISO 27001, or similar) unless we actually do — we'd rather describe our real practices honestly than display a badge that isn't backed by an audit. If and when we pursue formal certification, this page will be updated to reflect it, not the other way around.

7. Responsible disclosure

If you believe you've found a security issue with StrateQX, we want to know before anyone else does. Contact us directly with details — we'll acknowledge your report and work to address genuine issues promptly. Please don't publicly disclose a vulnerability before giving us a reasonable chance to fix it.

Questions about this page?

Reach out and we'll get back to you directly — no ticket queue.

Contact us →