Subprocessors
Every external service Hunts uses to operate. What each one receives, what they don't, where they're based, and their privacy/DPA terms. Updated when we add or remove anyone.
Region: AWS · GDPR-compliant data centers (configurable per project).
Stores your contacts, deals, tasks, activity log, Gmail message index, and subscription state. Row-level security scoped to your user — Supabase staff can't read your data except via a court order or break-glass support escalation.
Tokens (Gmail, Razorpay) are encrypted at rest with AES-GCM using a project-scoped key Supabase doesn't have visibility into.
Region: Global edge network (200+ POPs).
Serves the marketing site (/, /hunts/, etc.) and the CRM SPA shell (/crm/) from their global edge. Sees your IP and request paths via standard HTTP — same as any visit to any website behind Cloudflare.
Does not see your application data (contacts, emails, etc.) — those flow directly to Supabase from your browser.
Region: India (HQ Bangalore). PCI-DSS Level 1.
Handles all paid-plan checkouts via Razorpay's hosted checkout page. Sees your name, email, billing address, and payment instrument details (card, UPI ID, bank account) during the transaction.
We never see card numbers, CVVs, UPI PINs, or bank credentials. What we store from a successful payment: Razorpay's opaque subscription ID + customer ID, plan ID, status, and an audit log of webhook events.
Only customers who upgrade to Pro or Team are sent to Razorpay. Free-tier users never touch it.
Region: Google's global infrastructure. Subject to your Google account region.
Authentication via Google OAuth. If you opt into Gmail Sync, Google sees the access token requests we make and the message metadata + bodies we fetch (last 90 days, contacts-only filter applied client-side). Calendar integration sees busy/free queries against the calendars you've enabled — never event content.
You can revoke our access anytime at myaccount.google.com/permissions. Revocation kills the sync within minutes.
Hunts adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Region: AWS us-east-1.
Sends transactional emails (booking confirmations, password resets if added). Listed because the BookMe surface uses it; the Hunts core CRM doesn't send transactional mail today.
No Google Analytics, no Facebook Pixel, no advertising or behavioural-tracking service. No session-replay tools (Hotjar, FullStory, LogRocket). No third-party feature flag SaaS. No CDN-side AB-testing platforms.
Hunts' value is in being calm. Half the calm comes from not selling your shadow to a dozen brokers.
If we add a new subprocessor that handles customer data, we update this page and email all paying customers at least 14 days in advance. The change log will track additions, removals, and material scope changes.
Beta operators and free-tier users get the same notice via the address on file at auth.users.email.
Questions: [email protected].