OhAuthCat Privacy Policy
Version 1.0. Effective 1 November 2026. Last updated: 19 November 2026
1. Who we are and what this policy covers #
1.1 OhAuthCat is a product of Generic Technologies Private Limited, a company incorporated in India (CIN U72200TN2019PTC130162), with its registered office at 201/1, Arcot Road, Virugambakkam, Chennai, Tamil Nadu 600092, India ("OhAuthCat", "we", "us", "our").
1.2 OhAuthCat provides enterprise single sign-on (SAML 2.0 and OpenID Connect) and SCIM 2.0 directory sync as a hosted service (the "Service") to software companies ("Customers"). The Service includes the developer dashboard at console.ohauthcat.com, the setup portal used by IT administrators, the management API, the sign-in broker, the SCIM endpoint, webhooks, the command-line tool, the SDKs and our websites, including ohauthcat.com and its free browser tools.
1.3 This Privacy Policy explains how we handle personal data for which we decide why and how it is processed. In the language of data protection law, we are the "controller" (EU and UK GDPR), the "data fiduciary" (India's Digital Personal Data Protection Act, 2023, the "DPDP Act"), the "body corporate" (India's Information Technology Act, 2000 and the SPDI Rules) or the "business" (California Consumer Privacy Act as amended by the CPRA, the "CCPA"). Section 3 lists those situations.
1.4 This policy does not govern the identity data of the people who sign in to our Customers' applications through the Service. For that data we act only on our Customers' instructions. Section 4 explains this.
1.5 In this policy, "personal data" means any information that relates to an identified or identifiable person, and includes "personal information" and "digital personal data" as those terms are used in the laws listed in section 11.
2. Summary #
| Question | Short answer |
|---|---|
| Question: Where is the Service hosted? | Short answer: Amazon Web Services, Mumbai region (ap-south-1), India. No other hosting region is live today. |
| Question: Do you sell or share personal data for advertising? | Short answer: No. We do not sell personal data, and we do not share it for cross-context behavioural advertising. |
| Question: Do you use advertising or tracking cookies? | Short answer: No. We use only strictly necessary cookies. Our analytics (Cloudflare Web Analytics on the marketing website, and PostHog, EU cloud, once it starts; see section 5) runs without cookies. |
| Question: Who sees my data? | Short answer: Our staff who need it, and the service providers listed in our sub-processor list. |
| Question: How long do you keep it? | Short answer: For a fixed period per category, set out in section 3 and section 9. |
| Question: How do I exercise my rights? | Short answer: Email privacy@ohauthcat.com or our Grievance Officer (section 15). |
| Question: I signed in to an app that uses OhAuthCat. Who do I contact? | Short answer: The company whose app you signed in to. It controls your data; see section 4. |
3. Personal data we control #
For each category below we describe the data, why we use it, our legal basis, how long we keep it and who receives it. "GDPR basis" refers to Article 6(1) of the EU GDPR and UK GDPR. "DPDP ground" refers to consent under section 6 of the DPDP Act or a legitimate use under section 7.
3.1 Website visitors (ohauthcat.com, documentation and free tools) #
3.1.1 Data. When you visit our websites, our servers and our content-delivery provider receive the technical data every web request carries: your IP address, browser user agent, the page requested, the referring page and the time. If our product analytics is enabled, we record pseudonymous page views and interactions (for example, which pages were viewed and which buttons were pressed) without setting cookies or storing an identifier on your device. On the marketing website, Cloudflare Web Analytics also counts page views and page-load performance from the request data above, again without cookies or a device identifier. Neither analytics tool runs on the free browser tools.
3.1.2 Free browser tools. The SAML debugger, metadata validator and SCIM conformance tester on our website run in your browser. The SAML debugger and metadata validator process what you paste on your device; the browser downloads the validator program from our website, and the tools send none of your content anywhere. The SCIM conformance tester sends test requests, including the bearer token you enter, directly from your browser to the SCIM endpoint you choose to test; those requests do not pass through our servers, and we do not receive the token, the requests or the responses.
3.1.3 Regional demand telemetry. To decide where to open future regions, we look up the approximate city, region, country and network (ASN) of a client address in a copy of the MaxMind GeoLite database that runs on our own servers. The client IP address is discarded immediately after the lookup and is never stored with the result. MaxMind receives no data from us. The resulting counts are aggregate and do not identify anyone.
3.1.4 Purposes. To deliver the website, keep it secure, protect it against abuse, understand which content is useful and plan capacity.
3.1.5 GDPR basis. Legitimate interests (Art. 6(1)(f)) in operating, securing and improving our website. Our analytics is cookieless and pseudonymous, and we have balanced it against your interests on that basis.
3.1.6 DPDP ground. Consent given through use of the website after notice in this policy, and, for security processing, the legitimate uses permitted by section 7 of the DPDP Act.
3.1.7 Retention. Raw IP addresses in security logs: 30 days. Product analytics events: 12 months. Aggregated regional telemetry holds no personal data.
3.1.8 Recipients. Cloudflare (content delivery, DNS, security, cookieless website analytics), Amazon Web Services (hosting), PostHog (EU cloud; analytics, not active yet).
3.2 Waitlist #
3.2.1 Data. Your email address and the time you joined. We verify that a person, not a bot, submitted the form using Cloudflare Turnstile, which processes technical data about your browser.
3.2.2 Purposes. To invite you to the Service when a place is available and to send related messages about access.
3.2.3 GDPR basis. Consent (Art. 6(1)(a)), given when you submit the form. You can withdraw it at any time.
3.2.4 DPDP ground. Consent (section 6).
3.2.5 Retention. Your entry is stored in our own database (not with a form provider). It is deleted at once if you ask us to remove it, and 30 days after we send you an invitation.
3.2.6 Recipients. Amazon Web Services (hosting and email delivery through SES), Postmark (backup email delivery), Cloudflare (Turnstile).
3.3 Dashboard account holders (developers and team members) #
3.3.1 Data.
- Identity and contact: name and email address; your role in the team (owner, admin, developer or viewer).
- Sign-in credentials: passkey public keys and their metadata; time-based one-time password (TOTP) secrets, stored encrypted; recovery codes, stored only as a keyed hash (HMAC) and never in readable form; email one-time codes; and, if you choose to sign in with them, your GitHub or Google account identifier and the profile details those services return (name, email).
- Session and security data: session identifiers (stored only as hashes), session creation and expiry, the country derived from your IP address, a hash of your browser user agent, sign-in times, and IP addresses in security logs.
- Activity: actions you take in the dashboard and the API, recorded in the audit log of the relevant environment (for example, "member X rotated an API key").
- Usage analytics: pseudonymous, cookieless product analytics about how the dashboard is used.
3.3.2 Purposes. To create and manage your account; to authenticate you and protect the account (including multi-factor authentication and backup passkey recovery); to provide the Service; to keep an audit trail your team can inspect; to send you service messages (for example, certificate-expiry warnings, security alerts and changes to terms); to detect and prevent fraud and abuse; and to improve the dashboard.
3.3.3 GDPR basis. Performance of a contract (Art. 6(1)(b)) for account and service operation, where you are the Customer or act for it; legitimate interests (Art. 6(1)(f)) in securing the Service, keeping audit records and improving the product; legal obligation (Art. 6(1)(c)) where we must keep or disclose records.
3.3.4 DPDP ground. Consent given when you sign up, and the legitimate uses in section 7 of the DPDP Act for the purpose you voluntarily provided the data for, compliance with law and responding to security threats.
3.3.5 Retention.
- Account and credential data: for as long as your membership exists, then deleted within 30 days after you close your account or are removed from it. When a customer account is closed by its owner, it can be reopened within 7 days, and its data, including backups, is then deleted within 60 days after that window; billing and tax records are kept for 8 years.
- Dashboard sessions: until they expire or are revoked.
- Raw IP addresses in security logs: 30 days.
- Audit log entries naming you: by the plan of the environment: 7 days (Free), 90 days (Pro), 1 year (Business), as agreed (Enterprise). Audit logs are append-only and leave only through this scheduled purge.
- Product analytics: 12 months.
3.3.6 Recipients. Amazon Web Services; Cloudflare; Amazon SES and Postmark (email); PostHog (analytics, not active yet). If you choose GitHub or Google sign-in, GitHub, Inc. or Google LLC receive the sign-in request and act as independent controllers under their own privacy policies. Other members of your team see your name, email, role and audit entries.
3.4 Billing contacts and payment #
3.4.1 Data. Legal name of the buyer, billing contact name and email, billing address, country and state code, GSTIN (for Indian businesses), plan and add-ons, subscription status, invoice records and payment references from our payment providers. We never receive or store card numbers or bank account details. Payments are taken only on our providers' hosted checkout pages.
3.4.2 Who bills you.
- Customers paying in Indian rupees pay Generic Technologies Private Limited through Razorpay (with Cashfree as a fallback). We issue GST tax invoices.
- Customers paying in any other currency buy through a Merchant of Record, Dodo Payments. The Merchant of Record is the seller of record, collects payment and handles sales tax and VAT. It processes your payment data as an independent controller under its own privacy policy, and it shares with us the subscription and contact details we need to provide the Service.
3.4.3 Purposes. To charge for the Service, issue invoices, meet tax and accounting duties, manage subscriptions and recover unpaid amounts.
3.4.4 GDPR basis. Contract (Art. 6(1)(b)); legal obligation (Art. 6(1)(c)) for tax and accounting records; legitimate interests (Art. 6(1)(f)) in fraud prevention and debt recovery.
3.4.5 DPDP ground. Legitimate uses under section 7 (the purpose for which the data was provided; compliance with law, including the Central Goods and Services Tax Act, 2017).
3.4.6 Retention. Invoices, tax and accounting records: 8 years, which covers the Central Goods and Services Tax Act, 2017 (72 months after the due date of the annual return) and the Companies Act, 2013 (8 years). Other billing profile data: while the subscription is active and then 8 years after it ends, the same period as tax and accounting records.
3.4.7 Recipients. Razorpay Software Private Limited and Cashfree Payments India Private Limited (INR payments); Dodo Payments Inc. (Merchant of Record); our professional advisers and tax authorities where required.
3.5 Support and correspondence #
3.5.1 Data. Your name, email address, the content of your messages and any attachments, and the account or environment the request concerns. When support staff need to look at your configuration, that access is read-only, requires a recorded reason and is written to your environment's audit log.
3.5.2 Purposes. To answer questions, resolve incidents, handle security reports, improve documentation and keep a record of what was agreed.
3.5.3 GDPR basis. Contract (Art. 6(1)(b)) for Customers; legitimate interests (Art. 6(1)(f)) for other correspondents.
3.5.4 DPDP ground. Legitimate use under section 7 (data voluntarily provided for a specified purpose).
3.5.5 Retention. 2 years after the ticket or conversation is closed.
3.5.6 Recipients. Zoho Corporation Private Limited (Zoho Mail, our staff email, hosted in India); Amazon Web Services and Postmark (transactional email).
3.6 IT administrators who use the setup portal #
3.6.1 Context. IT administrators at our Customers' business customers ("Customer Organizations") use the hosted setup portal to connect their identity provider. The configuration they enter and the people they invite are handled for the Customer (section 4). We handle the IT administrator's own account and contact details as described here, to the extent we decide how they are used, for example to secure the portal and to send them service and security notices.
3.6.2 Data. Name and email address (as provided by the Customer or the invitation), the setup link or invitation used, portal session data (stored as hashes; sessions last at most 1 hour and end after 30 minutes idle), actions in the portal recorded in the audit log, and IP addresses in security logs.
3.6.3 Purposes. To authenticate the administrator, secure the portal, send setup, certificate-expiry and security notices, and keep audit records.
3.6.4 GDPR basis. Legitimate interests (Art. 6(1)(f)) in operating a secure setup portal for our Customers.
3.6.5 DPDP ground. Legitimate use under section 7, and the consent the Customer obtains when it invites the administrator.
3.6.6 Retention. Portal sessions are deleted once expired. Setup links and invitations are deleted 30 days after they expire or are revoked, with their sessions. IT contact records last as long as the Customer keeps them. Audit entries follow the plan periods in section 3.3.5. Raw IP addresses: 30 days.
3.6.7 Recipients. Amazon Web Services; Cloudflare; Amazon SES and Postmark. No product analytics runs on the portal.
3.7 Security logs and abuse prevention #
3.7.1 Data. IP addresses, request metadata, user agents, rate-limit counters, bot-check results, error codes and the security events we detect.
3.7.2 Purposes. To protect the Service, our Customers and their users against attacks, fraud and abuse; to investigate incidents; to enforce our terms, including suspending accounts used for phishing or abuse.
3.7.3 GDPR basis. Legitimate interests (Art. 6(1)(f)) in network and information security (Recital 49 GDPR); legal obligation (Art. 6(1)(c)) where incident reporting is required.
3.7.4 DPDP ground. Legitimate uses under section 7, including responding to threats and compliance with law (including directions of CERT-In under section 70B of the IT Act).
3.7.5 Retention. Raw IP addresses in security logs: 30 days. Rate-limit and replay-protection state: seconds to minutes, held in memory with an automatic expiry. Security and access logs, and security incident records: 1 year, stored in India, which meets the 180-day minimum in CERT-In's directions of 28 April 2022.
3.7.6 Recipients. Amazon Web Services; Cloudflare; law-enforcement or regulators where the law requires.
3.8 Staff access #
3.8.1 Data. Our own staff sign in to internal tools through Cloudflare Zero Trust Access, with a one-time PIN sent to their Company email address and passkeys. Every staff action on a Customer account, such as a support look-up, a plan change, an account suspension or switching an environment off, is recorded with the staff member's identity and a mandatory reason. Where we record the staff member's identity in Customer-visible logs we use a hashed identifier.
3.8.2 This section concerns data about our staff, and the record of what they did with Customer data. It is listed here so Customers know such records exist. Our staff's personal data is covered by OhAuthCat's internal staff privacy notice, which personnel receive when they join.
3.9 Business contacts, events and sales #
3.9.1 If you correspond with us about a purchase, an Enterprise order or a partnership, we keep your name, role, company, contact details and the correspondence, to manage the relationship (legitimate interests; DPDP legitimate use for the purpose provided). Retention: 2 years after the last contact. We do not buy contact lists.
4. Data we process for our Customers #
4.1 Our role. When a person ("User") signs in to a Customer's application through OhAuthCat, or is provisioned through SCIM, the Customer decides why and how that User's data is processed. The Customer is the controller (or data fiduciary). OhAuthCat is the processor (or data processor), and where the Customer itself acts for a Customer Organization, a sub-processor. We handle that data only to provide the Service and only on the Customer's documented instructions, under our Data Processing Agreement (the "DPA").
4.2 The data. Identity attributes the Customer Organization's identity provider or SCIM client sends (name, email address, identity-provider subject and identifiers, group memberships, roles and up to 50 custom attributes per environment the Customer chooses to map), sign-in events (time, IP address, user agent, result and error codes) and directory sync events. Annex I of the DPA describes this in full, with retention periods.
4.3 Which policy applies. The privacy policy of the company whose application you use governs this data. Please send requests about it (access, correction, deletion and so on) to that company. If you send them to us, we will pass them to the Customer where we can identify it, and we will not answer the request ourselves unless the Customer instructs us to or the law requires.
4.4 What we do not do. We do not use Users' identity data for our own purposes, for advertising or to build profiles, and we do not sell it. We do not combine one Customer's User data with another's. The only aggregate we derive is anonymous counts (for example, sign-ins per country and identity-provider type) that cannot identify a User or a Customer.
5. Cookies and similar technologies #
5.1 We use only cookies that are strictly necessary to provide a service you asked for. We do not use advertising cookies, cross-site tracking or third-party marketing pixels.
| Cookie or technology | Where | Purpose | Lifetime |
|---|---|---|---|
| Cookie or technology: Dashboard session cookie (Secure, HttpOnly, SameSite=Lax) | Where: console.ohauthcat.com | Purpose: Keeps you signed in; protects against cross-site request forgery | Lifetime: Until sign-out or session expiry: at most 12 hours, or 2 hours without activity |
Cookie or technology: __Host-ohc_portal_session (Secure, HttpOnly, SameSite=Strict) | Where: Setup portal and custom portal domains | Purpose: Keeps the IT administrator's setup session | Lifetime: At most 1 hour; ends after 30 minutes idle |
| Cookie or technology: Sign-in state | Where: Broker during sign-in | Purpose: Single-use, sealed state that binds a sign-in to its request | Lifetime: Up to 10 minutes |
| Cookie or technology: Cloudflare Turnstile | Where: Sign-up, waitlist and sandbox creation forms | Purpose: Tells people and bots apart | Lifetime: Per Cloudflare's documentation |
| Cookie or technology: Cloudflare security cookies | Where: All sites behind Cloudflare | Purpose: Bot and attack mitigation | Lifetime: Per Cloudflare's documentation |
| Cookie or technology: Cloudflare Web Analytics | Where: Marketing website only; never the free tools, setup portal or dashboard | Purpose: Counts page views and page-load performance; sets no cookie and stores no identifier on your device | Lifetime: Not applicable |
| Cookie or technology: PostHog (cookieless mode) | Where: Website and dashboard only. Not active yet: listed in advance, and subscribers to sub-processor notices are told before it starts | Purpose: Pseudonymous product analytics; sets no cookie and stores no identifier on your device | Lifetime: Not applicable |
| Cookie or technology: Browser local storage | Where: Dashboard | Purpose: Your interface preferences (for example, theme) | Lifetime: Until you clear it |
5.2 Because we use only strictly necessary cookies, we do not show a consent banner. If we add any non-essential cookie, we will ask for consent first.
6. Who receives personal data #
6.1 Service providers (sub-processors). We use the providers in our sub-processor list to host and run the Service. They act on our instructions under written contracts that require confidentiality and security.
Failed sign-in explanations (Anthropic). The developer dashboard and the setup portal can show a plain-language explanation of a failed SSO sign-in, written by Anthropic's Claude model through the Anthropic API. It is used only when someone opens the explanation of a failed sign-in, 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 (it is off by default); otherwise our built-in Connection Doctor text is shown and nothing is sent to Anthropic. The request holds only redacted error context from our own catalogue: the error code, our description and known cause for it, the names of the checks that ran and the identity provider type. It never holds secrets, tokens, email addresses, SAML payloads or other personal data. Under Anthropic's Commercial Terms, this data is not used to train Anthropic's models and is kept by Anthropic only for as long as those terms allow. Anthropic is listed in our sub-processor list.
Error monitoring (Sentry). When a page of our websites, the developer dashboard, the setup portal, the hosted sign-in pages or OhAuthCat Passport hits an unexpected error, it sends an error report to Sentry (Functional Software, Inc.), stored in Sentry's EU data storage location in Frankfurt, Germany. A report holds the stack trace, the error message, browser and operating system details and pseudonymous identifiers. Before it leaves your browser we remove URL query strings and fragments (where sign-in codes and tokens travel), request bodies, cookies, headers, form values and any email address in the report; we do not store your IP address with it. We collect errors only: no performance tracing, no session tracking and no session recording. The free browser tools never send error reports. Sentry is listed in our sub-processor list. Our legal basis is legitimate interests (Art. 6(1)(f)) in keeping the Service working and secure.
6.2 Independent controllers. Payment providers and Merchants of Record (section 3.4), and GitHub and Google when you choose to sign in with them, process data under their own privacy policies.
6.3 Your team and your Customers. Members of a Customer's team see the configuration, audit logs and member list of that Customer's projects. IT administrators of a Customer Organization see what the setup portal shows them.
6.4 Legal requests. We disclose personal data to authorities only when the law requires it and after checking the request is valid. Where we may, we tell the affected Customer first.
6.5 Business transfers. If Generic Technologies Private Limited is involved in a merger, acquisition or sale of assets, personal data may transfer to the successor, which will be bound by this policy or give notice of changes.
6.6 No sale, no sharing. We do not sell personal data and do not share it for cross-context behavioural advertising, as those terms are used in the CCPA.
7. International transfers #
7.1 Where we host. The Service runs in Amazon Web Services' Mumbai region (ap-south-1), India, across three availability zones. Backups are held in ap-south-1 and copied to Amazon Web Services' Hyderabad region (ap-south-2), also in India. We will update this policy and our sub-processor list, with the notice described there, before any other hosting or backup region is used.
7.2 Transfers out of the EU, EEA, UK and Switzerland. India does not have an adequacy decision under the EU or UK GDPR. When we receive personal data from those places, we rely on the European Commission's Standard Contractual Clauses (Decision (EU) 2021/914), the UK International Data Transfer Addendum, and the corresponding Swiss arrangements, and on the supplementary measures described in section 8. Some providers process data in other countries under their own transfer mechanisms, listed in the sub-processor list: Sentry (error monitoring, stored in Germany, with account settings and support access in the United States), Postmark (backup email), and Dodo Payments (Merchant of Record) in several countries. Amazon SES sends our email from India. Our Indian payment gateways, Razorpay and Cashfree, process data in India.
7.3 Transfers out of India. The DPDP Act allows transfer outside India except to countries the Central Government restricts. We do not transfer personal data to any restricted country.
7.4 You can request a copy of the relevant safeguards by writing to privacy@ohauthcat.com.
8. How we protect personal data #
8.1 We apply the measures in Annex II of the DPA to all personal data, including:
- encryption in transit with TLS 1.2 or higher (TLS 1.3 on custom hostnames);
- envelope encryption of secrets with keys held in AWS Key Management Service; API keys, SCIM tokens and portal tokens stored only as keyed hashes and shown once;
- tenant isolation enforced in the data layer, with tests that try cross-tenant access on every endpoint;
- multi-factor authentication on every plan, with passkeys preferred;
- no standing staff access to production databases; staff tools reachable only through zero-trust access; every staff action audited with a reason;
- append-only audit logs that even account owners cannot edit;
- logs that never contain tokens, secrets, SAML payloads or full email addresses.
8.2 No system is perfectly secure. If a personal data breach affects you, we will notify you and the regulators as the law requires.
8.3 We do not hold a SOC 2 report or any other security certification today. Our trust page states what is built and what is planned.
9. How long we keep data #
9.1 We keep personal data only for as long as the purpose needs, then delete or anonymise it. Deletion runs on scheduled jobs. The periods are:
| Data | Period |
|---|---|
| Data: Sub-processor change-notice subscription (email address) | Period: Kept until you unsubscribe; deleted at once by the one-click link in every notice |
| Data: Waitlist entry | Period: Deleted at once on request; 30 days after an invitation is sent |
| Data: Raw IP addresses in security logs | Period: 30 days (all plans) |
| Data: Audit log entries | Period: Free 7 days; Pro 90 days; Business 1 year; Enterprise as agreed |
| Data: Portal sessions | Period: Until expiry (at most 1 hour) |
| Data: Portal links and invitations | Period: 30 days after they expire or are revoked |
| Data: Dashboard account and credentials | Period: Membership, then deleted within 30 days of closure |
| Data: Billing, tax and accounting records | Period: 8 years (Central Goods and Services Tax Act, 2017; Companies Act, 2013) |
| Data: Support correspondence | Period: 2 years after the ticket closes |
| Data: Security and access logs | Period: 1 year, stored in India (CERT-In directions of 28 April 2022) |
| Data: Data-export download links | Period: 24 hours |
| Data: Product analytics | Period: 12 months |
| Data: Backups | Period: 60 days (7-day point-in-time recovery plus weekly snapshots) |
9.2 Retention for Users' identity data is set out in Annex I of the DPA.
9.3 Data in backups is overwritten as backups expire. We do not restore deleted personal data from a backup except to recover from an incident, and then we re-apply deletions.
10. Automated decisions #
10.1 We do not make decisions with legal or similarly significant effects about you based solely on automated processing. Automated checks we run (for example, refusing a sign-in whose email domain the organization has not verified, or blocking a bot on a form) are security controls; you can contact us to have one reviewed by a person.
11. Your rights #
11.1 Everyone. Whatever your location, you can ask us to tell you what personal data we hold about you, correct it, delete it, or stop sending you marketing email. We answer within 30 days, or sooner where the law requires.
11.2 EU, EEA and UK (GDPR). You have the rights of access (Art. 15), rectification (Art. 16), erasure (Art. 17), restriction (Art. 18), data portability (Art. 20), objection, including to processing based on legitimate interests (Art. 21), and to withdraw consent at any time without affecting earlier processing. You may complain to your local supervisory authority; in the UK, the Information Commissioner's Office.
11.3 India (DPDP Act and IT Act). You have the right to:
- obtain a summary of the personal data we process about you and the processing activities, and the identities of the data fiduciaries and processors we have shared it with (section 11);
- have your data corrected, completed, updated and erased (section 12);
- have a readily available means of grievance redressal through our Grievance Officer (section 13);
- nominate another individual to exercise your rights in the event of your death or incapacity (section 14); write to privacy@ohauthcat.com with the nominee's name and contact details;
- withdraw consent at any time, as easily as you gave it.
You must first raise a grievance with us. If you are not satisfied with our response, you may complain to the Data Protection Board of India. You also have the duties in section 15 of the DPDP Act, including not to file false or frivolous complaints.
11.4 California and other US states. California residents have the right to know, access, correct and delete personal information; to opt out of sale or sharing (we do neither); to limit the use of sensitive personal information (we use it only for permitted purposes, such as account security); and not to be discriminated against for exercising these rights. You may use an authorised agent. Residents of Colorado, Connecticut, Virginia, Utah, Texas, Oregon and other states with similar laws have comparable rights, including to appeal a refusal by replying to our decision. In the last 12 months we collected the categories described in section 3: identifiers, commercial information (billing), internet and network activity, and professional information, for the business purposes stated there.
11.5 Switzerland, Brazil, Singapore and other countries. You have the rights your local law gives. Write to us and we will handle the request under the law that applies.
11.6 How to make a request. Email privacy@ohauthcat.com. We may need to verify your identity, normally by asking you to confirm from the email address on the account. We do not charge for requests unless they are manifestly unfounded or excessive. Dashboard members can also change their profile, credentials and team membership directly in the dashboard, and can download a copy of their own personal data at any time from the Account page of the dashboard (Download my data).
12. Children #
12.1 The Service is a business tool. It is not directed at anyone under 18, and we do not knowingly collect personal data from anyone under 18 as a controller. If you believe a child has given us personal data, write to privacy@ohauthcat.com and we will delete it. The DPDP Act requires verifiable parental consent for processing a child's data; because we do not intend to process such data, we do not offer that process.
12.2 Customers decide which Users may sign in to their applications. A Customer that lets children sign in must handle the related obligations as controller.
13. Marketing #
13.1 We send service messages to account holders as part of the Service. We send product news only to people who have opted in or, where the law allows, to existing Customers about similar services, and every such message has an unsubscribe link.
13.2 If you subscribe to sub-processor change notices, we keep your email address until you unsubscribe, and use it only to send those notices. Every notice has a one-click unsubscribe link, which deletes the address at once.
14. Changes to this policy #
14.1 We may change this policy. We will post the new version with a new "Last updated" date. For material changes we will give at least 30 days' notice by email to account owners and on our website before the change takes effect, unless a change is required sooner by law.
14.2 Previous versions are archived at https://ohauthcat.com/legal/archive/.
15. Contact and Grievance Officer #
15.1 Privacy questions and requests: privacy@ohauthcat.com
15.2 Grievance Officer (Information Technology Act, 2000 and the rules made under it; DPDP Act):
- Name: Koushik Raj
- Designation: Chief Executive Officer
- Email: grievance@ohauthcat.com
- Address: Generic Technologies Private Limited, 201/1, Arcot Road, Virugambakkam, Chennai, Tamil Nadu 600092, India
- We acknowledge grievances within 24 hours and resolve them within 15 days.
15.3 Security reports: security@ohauthcat.com. Legal notices: legal@ohauthcat.com.
15.4 We have no establishment or representative in the EU or the UK. EU and UK users can contact our Grievance Officer in India at grievance@ohauthcat.com (section 15.2), or write to privacy@ohauthcat.com. We have not appointed a Data Protection Officer. If that changes, we will name them here.