Security and hosting
Effective: October 28, 2026 · Last updated: October 28, 2026
The short version
Gault holds numbers per location, never your customers. It runs in the United States on hosting providers that are independently audited (SOC 2 Type 2), each client's data is kept apart from every other client's, and only the people you invite can see it. Anything you send can be deleted in full when you ask.
What we take, and what we never take
Gault Visibility and Gault Presence read public information about your locations. Gault Custom needs only per-location totals.
| We take | We never take |
|---|---|
| Your location roster: business names, addresses, and any contact details you include | Your customers’ names, emails or phone numbers |
| For Gault Custom: marketing spend per location and channel; counts such as QR scans, ad clicks or visits; sales per location, or only the ratio (sales per $1 spent) if profit is sensitive | Card or payment details |
| Names and emails of the people you invite | Logins to your ad, sales or point-of-sale tools |
| For Gault Presence: your logo, colors, fonts and brand guidelines | Anything you don’t send |
Where it is hosted
The three providers that store or move Gault's data are in the United States and hold SOC 2 Type 2 reports, which an independent auditor checks every year. Each report is available from the provider on request.
| Provider | What it does for Gault | Where |
|---|---|---|
| Vercel | Runs the app and its servers; private file storage for Gault Custom | USA |
| Supabase | Database and sign-in | USA |
| Upstash | Fast storage for readings and results | USA |
Compliance pages: Vercel, Supabase, Upstash. The full list of every service Gault uses, with what each one sees, is at /subprocessors. Figures sent for Gault Custom are stored only with the three providers above and are never sent to any AI, place or search vendor.
How it is kept apart and protected
- Each client is walled off. The server decides which client a request belongs to; the database itself refuses one client's reads of another's data, even with the app's public key.
- Only invited people get in. Every page and data request needs a signed-in account tied to your company. Roles limit what each person can see; a single location sees only its own.
- Encrypted in transit. Every connection uses HTTPS. Passwords are stored hashed by the sign-in provider.
- Backed up. The account database is backed up daily (7 days rolling). Operational data is backed up nightly, encrypted, to private storage on a 14-day rolling window.
- Deleted on request. Anything you send is removed from live systems within 30 days of your request, leaves the backups as they roll over, and we confirm it in writing when you ask. The retention schedule is in the Privacy Policy.
- Never used to train AI. Your data is not used to train any model, and our AI providers' terms say the same of what we send them.
Hosting options
Every Gault customer runs on the standard setup above. For a client whose figures are sensitive, there are two further options, in order of how much changes:
| Option | What it means |
|---|---|
| Send ratios, not profit | You share return per $1 by location and channel, never raw profit or sales. Profit never leaves your systems; Gault still shows what works. |
| A database of your own | A separate database just for you, still run by Gault. A stricter wall, for a small added monthly cost. |
Reviews and questions
We welcome a security review by your own team or your agency before any data is shared, and we answer security questionnaires. A Data Processing Addendum is available on request. If you believe you have found a vulnerability, email hello@gaultandco.com with the subject "Security report".