OhAuthCat Sub-processors
Version 1.0. Published 1 November 2026. Last updated: 19 November 2026
1. About this list #
1.1 OhAuthCat is a product of Generic Technologies Private Limited, Chennai, India ("OhAuthCat"). This page lists the third parties that process personal data on OhAuthCat's behalf ("Sub-processors") when we provide the Service to our customers, as described in our Data Processing Agreement (the "DPA"), section 6 and Annex III.
1.2 It also lists, separately, third parties that receive personal data as independent controllers under their own terms. They are not Sub-processors, but we list them so customers can see every place data goes.
1.3 Primary hosting. The Service is hosted in Amazon Web Services' Mumbai region (ap-south-1), India. No other hosting region is live. We will update this page, with notice under section 4, before any other region processes customer data.
1.4 Customer-directed recipients. Destinations the customer configures (its own application and redirect URIs, webhook endpoints, log-stream destinations) receive data on the customer's instruction and are not Sub-processors.
1.5 Not a Sub-processor: MaxMind. We use the MaxMind GeoLite database to derive approximate location from IP addresses. It runs as a local file on our own servers; MaxMind receives no data from us.
2. Sub-processors #
| # | Entity | Purpose | Location of processing | Data categories | Transfer mechanism | Data processing agreement |
|---|---|---|---|---|---|---|
| #: 2.1 | Entity: Amazon Web Services India Private Limited (the AWS contracting party for accounts in India), with Amazon Web Services, Inc. | Purpose: Hosting of all Service roles (Kubernetes, load balancers), the managed PostgreSQL database (Amazon RDS) and the self-managed Valkey cache, AWS Key Management Service (encryption keys), object storage for exports, debug bundles, invoices and customer logos (served at assets.ohauthcat.com through CloudFront) and static website hosting (S3 and CloudFront). Transactional email through Amazon SES is listed separately in 2.7 | Location of processing: India (ap-south-1 Mumbai; backup copies in ap-south-2 Hyderabad). CloudFront delivers static content and logos from its global edge network | Data categories: All Customer Personal Data (Annex I of the DPA) | Transfer mechanism: Data at rest in India. For EU/UK data: SCCs with AWS (AWS Data Processing Addendum), and SCCs between customer and OhAuthCat (DPA section 12) | Data processing agreement: AWS Data Processing Addendum |
| #: 2.2 | Entity: Cloudflare, Inc. | Purpose: DNS, reverse proxy, TLS termination, web application firewall and DDoS protection in front of the API, sign-in broker, SCIM endpoint and websites; custom portal hostnames (Cloudflare for SaaS); Turnstile bot checks on sign-up, waitlist and sandbox forms; Zero Trust Access for staff tools; cookieless website analytics (Cloudflare Web Analytics) on the marketing website only, never on the free browser tools, the setup portal or the dashboard | Location of processing: Global edge network (data processed in transit at the nearest location) | Data categories: Data in transit through the network, including sign-in requests and SCIM payloads; request metadata (IP address, user agent, headers); Turnstile browser signals; for Web Analytics, page views with request metadata of website visitors (no cookie or device identifier) | Transfer mechanism: SCCs (Cloudflare Data Processing Addendum); EU-US Data Privacy Framework certification | Data processing agreement: Cloudflare Customer DPA |
| #: 2.3 | Entity: ActiveCampaign, LLC (Postmark) | Purpose: Secondary transactional email, used if Amazon SES is unavailable | Location of processing: United States | Data categories: Recipient email address and message content (for example, setup invitations, certificate-expiry and security notices) | Transfer mechanism: SCCs (Postmark Data Processing Addendum). ActiveCampaign is certified under the EU-US Data Privacy Framework; we rely on the SCCs | Data processing agreement: Postmark Data Processing Addendum |
| #: 2.4 | Entity: PostHog Inc. (EU cloud) | Purpose: Not active yet: listed in advance, and subscribers are notified before it starts. Cookieless product analytics on the developer dashboard and the marketing website only; never on the setup portal or the free browser tools | Location of processing: European Union (Frankfurt, Germany) | Data categories: Pseudonymous usage events of dashboard members and website visitors. No Customer Personal Data (Users' identity data) is sent to PostHog | Transfer mechanism: EU hosting; PostHog Data Processing Agreement with SCCs for any onward transfer | Data processing agreement: PostHog DPA |
| #: 2.5 | Entity: Zoho Corporation Private Limited (Zoho Mail) | Purpose: Staff email and support correspondence | Location of processing: India | Data categories: Support correspondence, which may include Customer Personal Data a customer chooses to send (for example, an email address in a support ticket) | Transfer mechanism: Data at rest in India. For EU/UK data: SCCs between customer and OhAuthCat (DPA section 12) | Data processing agreement: Zoho Data Processing Addendum, not published as a page; issued to account administrators on request to legal@zohocorp.com (Zoho GDPR page) |
| #: 2.6 | Entity: Anthropic, PBC | Purpose: Plain-language explanations of failed SSO sign-ins in the developer dashboard and the setup portal (Claude Haiku model, through the Anthropic API). Used only when a failed sign-in's explanation is opened, only while we have the feature switched on for the Service, and only for customer accounts whose administrator has turned it on in the dashboard (off by default); otherwise the built-in Connection Doctor text is shown and nothing is sent | Location of processing: Data stored in the United States; requests may be routed to Anthropic's processing locations in the United States, Europe, Asia and Australia, as published in Anthropic's Privacy Center ("Where are your servers located?", checked 30 October 2026) and its sub-processor list at https://trust.anthropic.com/subprocessors | Data categories: Only catalogue data: the error code, the Connection Doctor's description and known cause for it, the names of the checks that ran and the identity provider type. The prompt is redacted error context built from that catalogue data. No personal data, secrets, tokens, email addresses or SAML payloads are sent to Anthropic. Under Anthropic's Commercial Terms, the data is not used to train its models and is kept by Anthropic only for as long as those terms allow | Transfer mechanism: Anthropic Data Processing Addendum with SCCs, incorporated into Anthropic's Commercial Terms | Data processing agreement: Anthropic Data Processing Addendum |
| #: 2.7 | Entity: Amazon Web Services India Private Limited, with Amazon Web Services, Inc. (Amazon Simple Email Service, "Amazon SES") | Purpose: Primary transactional email: sign-in codes, invitations, setup links, certificate-expiry and security notices, billing and sub-processor notices | Location of processing: India (SES sending region ap-south-1, Mumbai) | Data categories: Recipient email address and message content | Transfer mechanism: Data at rest in India. For EU/UK data: SCCs with AWS (AWS Data Processing Addendum), and SCCs between customer and OhAuthCat (DPA section 12) | Data processing agreement: AWS Data Processing Addendum |
| #: 2.8 | Entity: Functional Software, Inc. d/b/a Sentry | Purpose: Application error monitoring: reports of errors in our websites, the developer dashboard, the setup portal, the hosted sign-in pages and OhAuthCat Passport, so we can find and fix faults. Errors only: no performance tracing, no session tracking and no session replay. Never on the free browser tools | Location of processing: European Union (Sentry's EU data storage location, Frankfurt, Germany). Sentry keeps some account and project settings in the United States, and its affiliates and sub-processors may access data to provide the service, as published on Sentry's sub-processor page (checked 13 November 2026) | Data categories: Error events: stack traces, error messages, browser and operating system metadata and pseudonymous identifiers. Before an event leaves the browser we remove URL query strings and fragments, request bodies, cookies, headers, form values and any text holding an email address. No request bodies and no email addresses are sent to Sentry, and IP addresses are not stored | Transfer mechanism: Sentry Data Processing Addendum: the EU-US Data Privacy Framework, with SCCs (Decision (EU) 2021/914, with the UK Addendum and Swiss changes) where the Framework does not apply (Sentry DPA, Schedule 3, checked 13 November 2026) | Data processing agreement: Sentry Data Processing Addendum |
3. Independent controllers (not Sub-processors) #
These parties receive personal data to provide their own service under their own privacy terms. They are not engaged to process Customer Personal Data on our behalf.
| Entity | Role | When | Location | Data |
|---|---|---|---|---|
| Entity: Razorpay Software Private Limited | Role: Payment gateway for customers paying in Indian rupees (primary) | When: Customer pays in INR | Location: India | Data: Billing contact, payment details entered on Razorpay's hosted checkout, payment metadata |
| Entity: Cashfree Payments India Private Limited | Role: Payment gateway for INR (fallback) | When: Customer pays in INR and Cashfree is in use | Location: India | Data: As for Razorpay |
| Entity: Dodo Payments Inc. and its group companies (including Dodope Payments Limited and Sarvapanchhi Technologies Private Limited) | Role: Merchant of Record for all non-INR purchases: sells the subscription, collects payment and handles sales tax and VAT | When: Customer pays in any currency other than INR | Location: Multiple countries; see Dodo Payments' privacy policy | Data: Billing contact, address, tax identifiers, payment details on its hosted checkout |
| Entity: GitHub, Inc. | Role: Optional sign-in to the developer dashboard | When: Only if the dashboard member chooses "Sign in with GitHub" | Location: United States | Data: The member's GitHub account identifier, name and email |
| Entity: Google LLC | Role: Optional sign-in to the developer dashboard | When: Only if the dashboard member chooses "Sign in with Google" | Location: Global | Data: The member's Google account identifier, name and email |
Card and bank details are entered only on the providers' own hosted checkout pages and never reach OhAuthCat's pages or servers.
4. Notice of changes and how to subscribe #
4.1 We give at least 30 days' notice before a new Sub-processor starts processing Customer Personal Data, except in an emergency described in DPA section 6.5.
4.2 Notice is given by updating this page and by email to:
- the owners of every customer account; and
- everyone subscribed to sub-processor updates.
4.3 To subscribe, use the form at https://ohauthcat.com/legal/sub-processors#subscribe. We confirm your subscription by email, and every notice email has a one-click unsubscribe link. We keep your email address until you unsubscribe, and use it only for these notices. Questions about this list can be sent to subprocessors@ohauthcat.com.
4.4 To object to a new Sub-processor, write to subprocessors@ohauthcat.com or privacy@ohauthcat.com within the notice period, as set out in DPA section 6.4.
5. Planned changes (not yet in effect) #
These are recorded in our plans but do not process any data today. Each one will go through the notice in section 4 before it starts.
- A public status page at https://status.ohauthcat.com, hosted on GitHub Pages (GitHub, Inc.), outside Cloudflare's proxy and outside our AWS account; its availability checks run in GitHub Actions. It processes no Customer Personal Data: updates are published as a feed, not by email subscription.
- Additional hosting regions (United States, European Union, Singapore, Middle East) and a second cloud provider (Google Cloud) for later stages. None is live.
6. Change log #
| Date | Change |
|---|---|
| Date: 1 November 2026 | Change: First published list: Amazon Web Services, Cloudflare, Postmark, PostHog (EU cloud), Zoho Mail, Anthropic (failed sign-in explanations). Independent controllers: Razorpay, Cashfree, Lemon Squeezy, Dodo Payments, GitHub (optional sign-in), Google (optional sign-in). |
| Date: 1 November 2026 | Change: Cloudflare entry (2.2) clarified: Cloudflare also provides cookieless website analytics (Cloudflare Web Analytics) on the marketing website only, never on the free browser tools, the setup portal or the dashboard. No new Sub-processor and no Customer Personal Data involved. |
| Date: 11 November 2026 | Change: Each Sub-processor's data processing agreement is now named and linked in section 2. We accept each Sub-processor's standard terms. The Anthropic entry (2.6) now says the explanations also appear in the setup portal, when they are used, and that the data is not used for model training. No new Sub-processor and no change to the data processed. |
| Date: 11 November 2026 | Change: Amazon SES listed as its own entry (2.7) instead of inside the Amazon Web Services entry (2.1). No new Sub-processor and no change to the data it processes. |
| Date: 12 November 2026 | Change: The Anthropic entry (2.6) now says failed sign-in explanations are off by default and are used only for customer accounts whose administrator turns them on in the dashboard. No new Sub-processor and no change to the data processed. |
| Date: 13 November 2026 | Change: New Sub-processor: Functional Software, Inc. d/b/a Sentry (2.8), for application error monitoring in Sentry's EU data storage location (Frankfurt, Germany). Errors only, with URLs, request bodies, cookies, headers, form values and email addresses removed before sending; never on the free browser tools. |
| Date: 13 November 2026 | Change: 2.1: describe the database as Amazon RDS PostgreSQL; no change of sub-processor or location. |
| Date: 13 November 2026 | Change: 2.4: PostHog is marked as not active yet. No front end sends data to it today; subscribers are notified before it starts. 2.8: Sentry also receives no session tracking. No new Sub-processor and no change to the data processed. |
| Date: 14 November 2026 | Change: Payment providers (independent controllers, section 3): Dodo Payments is now the Merchant of Record for all purchases in currencies other than INR. Lemon Squeezy stays listed in advance but is not active yet; no data goes to it. No change to the Sub-processors. |
| Date: 19 November 2026 | Change: Payment providers (independent controllers, section 3): Lemon Squeezy (Link, LLC) removed. It was never activated and no data went to it; Dodo Payments remains the Merchant of Record for all purchases in currencies other than INR. No change to the Sub-processors. |