Security
Effective date: June 8, 2026
Overview
DeuceGC uses layered controls to protect accounts, billing workflows, and product data. No system is perfectly secure, but we work to keep access scoped, monitored, and appropriate to the product we operate.
Core controls
- Supabase provides hosted authentication and database infrastructure.
- Stripe hosts checkout, renewals, invoices, and billing portal access. DeuceGC does not store full payment card numbers.
- State-changing application routes enforce same-origin protections.
- Public geocoding and weather routes use rate limits, bounded caching, and coordinate validation.
- Stripe webhook processing verifies signatures and records idempotent event handling to reduce duplicate processing.
- Account deletion and billing cancellation flows require authenticated requests.
Analytics and diagnostic controls
- PostHog analytics and Sentry diagnostics follow the privacy preference model exposed in the app.
- Analytics payloads are intended to exclude free-form notes, email addresses, full names, precise GPS coordinates, and raw OAuth errors.
- Sentry context is intended to remain limited to operational debugging data rather than unnecessary personal content.
Access and vendors
- DeuceGC limits provider usage to vendors needed for hosting, billing, analytics, diagnostics, maps, and email delivery.
- Current subprocessors are listed on the public Subprocessors page.
Account actions
- Users can sign out from the Account Hub.
- Subscription management happens through the Stripe customer portal after checkout.
- Users can request account deletion or data-related help by contacting hello@deucegc.com.
Reporting concerns
If you believe you found a security issue or suspicious account behavior, contact hello@deucegc.com. Please do not include sensitive secrets or exploit details in an unsafe public channel.
Updates
We may update this page as our controls, vendors, or operational practices change.