Built so the office, the crew, and the customer can trust the ledger.
This page is maintained by Grounds Manager, Inc. to answer the security and data-handling questions we hear most often from operators and their property managers. We describe controls we actually have today — not certifications we don't.
Three controls we'll never cut corners on.
Encryption everywhere
All traffic between your browser, our app, and our database is encrypted in transit with TLS. Customer data at rest is encrypted on managed Postgres with disk-level AES-256.
Least-privilege access
Internal staff access is role-based and limited to what the role actually needs. Production database access is restricted to a small set of engineers and audited.
Daily backups, point-in-time restore
Our managed Postgres runs continuous backups with point-in-time recovery. If something goes wrong, we can restore to a specific minute, not just to last night.
What's actually in place today.
Email + password with hashed credentials. Optional Google sign-in.
HTTP-only, secure session cookies. Sessions invalidate on password change.
Database policies enforce tenant isolation — no customer can read another customer's data.
API keys and credentials are stored as managed environment variables, never in source code.
Automated checks on every deploy for known vulnerabilities in third-party packages.
Authentication events and administrative actions are logged and retained for review.
You own it. We just hold it.
Everything your crews and office upload — clients, properties, jobs, photos, estimates — belongs to you. We use it to run the Services and nothing else. We don't sell it, we don't share it for advertising, and we'll hand it back on request.
- Export anytime
Customer data is exportable as CSV from inside the app, no support ticket required.
- Deletion on request
Email us and we'll permanently delete your account and customer data within 30 days, subject to legal retention obligations.
- No training on your data
We don't train AI models on customer content. Period.
- Tenant isolation
Database-level policies prevent one customer's queries from ever returning another customer's rows.
Subprocessors.
We use a handful of vetted vendors to run the platform. Each one is bound by a data processing agreement and is used only for the purpose listed below.
| Provider | Purpose |
|---|---|
| Supabase | Application hosting, Postgres database, authentication, file storage |
| Stripe | Subscription billing and payment processing |
| Resend | Transactional email delivery (receipts, password resets, notifications) |
| Mapbox | Maps, geocoding, and route visualization |
| QuickBooks (Intuit) | Accounting sync — only when a customer connects their QuickBooks account |
| ServiceChannel | Vendor portal sync — only when a customer connects ServiceChannel |
| Google Analytics | Aggregated website usage analytics on marketing pages |
| Meta Platforms | Ad measurement and retargeting via the Meta Pixel — marketing pages only, never inside the app |
We notify customers of material subprocessor changes via in-app notice or email at least 30 days before they take effect.
Hosting
The application runs on Supabase managed infrastructure backed by AWS in the United States. Compute and database resources are isolated per tenant at the row level, and traffic terminates behind a managed reverse proxy.
Incident response
If we become aware of a security incident affecting customer data, we will notify affected customers without undue delay and provide what we know, what we're doing, and what (if anything) the customer needs to do.
Found something? Tell us.
If you believe you've discovered a vulnerability in Grounds Manager, please report it privately. We'll acknowledge within two business days, keep you in the loop while we investigate, and credit you publicly once a fix is shipped (if you want the credit).
support@groundsmanager.appFor privacy questions or data-subject requests, see our Privacy Policy. For the terms governing use of the Services, see our Terms of Service.