Last reviewed July 2026
Win! is a payment-adjacent platform. We take that responsibility seriously. This page explains, in plain language, exactly how we protect your data and your customers' payment details.
Card numbers, CVCs, expiry dates, and bank account numbers are entered directly into Stripe Elements — a secure, iframe-based checkout widget that runs entirely within Stripe's infrastructure. Those values are never transmitted to Win!'s servers and are never written to our database.
What we store is only what Stripe gives back after tokenisation: a payment method ID, the card brand, the last four digits, and whether the charge succeeded. No raw numbers. No CVCs. Ever.
Stripe is PCI DSS Level 1 certified
Stripe is certified as a PCI Level 1 Service Provider — the highest level of certification in the Payment Card Industry Data Security Standard. All card and ACH data is collected, stored, and processed inside Stripe's certified environment. View Stripe's security documentation →
Win! stores only the minimum necessary to operate the service:
We do not store, request, or have access to your Xero or QuickBooks Online password, your Stripe password, payroll data, payroll journal entries, bank feed credentials, or any data outside the OAuth scopes you explicitly grant.
In transit
All traffic between your browser, Win!'s servers, and third-party APIs (Stripe, Xero, QuickBooks Online) is encrypted using TLS 1.2 or higher. Connections over plain HTTP are not accepted.
At rest — OAuth tokens
The OAuth access and refresh tokens Win! holds on your behalf (for Xero, QuickBooks Online, and Stripe Connect) are encrypted at rest using AES-256-GCM at the application layer, with the encryption key stored separately from the database as an environment secret. A database backup alone is not sufficient to recover your tokens.
At rest — payment data
As described above, no raw card or bank account data is stored by Win!. Payment references (Stripe IDs, last-4) are stored in a managed PostgreSQL database hosted by Supabase, which encrypts data at rest by default.
Win! connects to your accounting platforms using OAuth 2.0. We request only the minimum scopes necessary to import invoices and reconcile payments:
You can revoke Win!'s access at any time from the Connections page inside Win!, or directly from your accounting platform:
When you disconnect a platform or delete your Win! account, we immediately delete the associated OAuth tokens from our database and revoke them with the provider so they cannot be used again.
If we confirm a security breach that compromises personal data, we will notify affected merchants within 72 hours and, where required by applicable law, notify the relevant supervisory authority.
Notifications will be sent to the email address on your Win! account and will include: what happened, what data was involved, what we have done to contain it, and what you should do next.
If you believe you have found a security vulnerability in Win!, please report it to us before disclosing it publicly. We aim to acknowledge all reports within 2 business days and resolve confirmed vulnerabilities promptly.
Security contact: contact our support team
Please include a description of the issue, steps to reproduce it, and the potential impact. We do not currently offer a formal bug bounty programme, but we do recognise researchers who report valid findings responsibly.