Skip to content
  • Product
  • Pricing
  • Migrate
  • SAML debugger
  • Security
  • Docs
Sign inStart free
  • Product
  • Pricing
  • Migrate
  • SAML debugger
  • Security
  • Docs
  • Metadata validator
  • SCIM tester
  • IdP Radar
  • Trust centre
Start freeSign in

Legal

OhAuthCat Customer Agreement (Terms of Service)

Version: 1.0. Effective: 1 November 2026. Last updated: 19 November 2026

Contents

  1. 1. Definitions
  2. 2. Accounts and eligibility
  3. 3. The Service
  4. 4. Customer responsibilities
  5. 5. Acceptable use
  6. 6. Customer Data
  7. 7. Our personnel and access to Customer Data
  8. 8. Suspension, account takedown and the Kill Switch
  9. 9. Beta Features
  10. 10. Free Plan, Sandboxes, the Hosted Test IdP and Free Tools
  11. 11. Fees, billing, renewals and taxes
  12. 12. Upgrades, downgrades and Plan limits
  13. 13. WorkOS-compatible API support window
  14. 14. API changes and versioning
  15. 15. Intellectual property
  16. 16. Publicity
  17. 17. Third-party open source and connected services
  18. 18. Confidentiality
  19. 19. Warranties and disclaimers
  20. 20. Indemnities
  21. 21. Limitation of liability
  22. 22. Term and termination
  23. 23. Force majeure
  24. 24. Assignment and subcontracting
  25. 25. Governing law and disputes
  26. 26. Anti-bribery and ethics
  27. 27. Export controls and sanctions
  28. 28. Notices
  29. 29. Changes to this Agreement
  30. 30. General
  31. 31. Entire agreement and order of precedence
  32. 32. Contact

This Customer Agreement (the "Agreement") is between 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"), and the business entity that accepts it ("Customer", "you"). OhAuthCat is a product of Generic Technologies Private Limited.

You accept this Agreement when you click to accept it, create an Account, use the Service, or sign an Order Form that refers to it. If you accept on behalf of a company or other legal entity, you confirm that you have authority to bind that entity, and "Customer" means that entity. If you do not have that authority, or you do not agree, do not use the Service.

This Agreement applies as a click-through agreement to the Free, Pro and Business plans. It is also the base agreement for the Enterprise plan, where an Order Form adds to it or changes it as clause 31.3 describes.


1. Definitions #

In this Agreement, the following capitalised terms have these meanings. Other terms are defined where they first appear.

1.1 "Account" means the account you create on the Dashboard, together with every Project and Environment in it.

1.2 "Account Holder" means an individual who has a login to your Account, including owners, admins and members you invite.

1.3 "Add-on" means an optional paid feature listed on the Pricing Page or in an Order Form, such as log streaming, extended retention, a custom portal domain on the Free plan, extended compat/workos support and, for Enterprise only, data residency, Premium success, a dedicated cell and bring-your-own-key encryption ("BYOK"), each when generally available.

1.4 "Affiliate" means an entity that controls, is controlled by, or is under common control with a party, where "control" means owning more than 50% of the voting interests.

1.5 "API" means the OhAuthCat management REST API, the SSO broker endpoints, the SCIM endpoints, the WorkOS-compatible API under compat/workos, the webhook and log streaming interfaces and the MCP server, together with their documentation.

1.6 "Applicable Data Protection Law" has the meaning given in the DPA.

1.7 "Beta Feature" means any feature, API, tool or region that we label "beta", "preview", "early access", "experimental" or similar, or that we make available for evaluation before general availability.

1.8 "Confidential Information" has the meaning given in clause 18.1.

1.9 "Customer Data" means all data, including personal data, that you, your Account Holders, your Customer Organizations or Users submit to the Service or that the Service receives from an identity provider or SCIM client on your behalf. It includes identity provider configurations, User profiles and attributes, directory data, sign-in and SCIM events, audit logs about your Environments and branding assets you upload. It does not include Usage Data.

1.10 "Customer Organization" means a business or other organization that is your customer, or a part of your own organization, and that you set up in the Service so that its identity provider or directory can connect to your application.

1.11 "Dashboard" means the developer dashboard at console.ohauthcat.com and any successor.

1.12 "Documentation" means the user guides, API references, error catalogue and other technical documentation we publish at https://docs.ohauthcat.com, as updated from time to time.

1.13 "DPA" means our Data Processing Addendum in Data Processing Agreement as published at https://ohauthcat.com/legal/dpa, or a data processing agreement signed between the parties that replaces it.

1.14 "Environment" means a separately configured instance of the Service within a Project. Each Project has at least one sandbox Environment ("Sandbox") and one production Environment ("Production Environment"); some plans allow more.

1.15 "Fees" means the fees for the Service and Add-ons stated on the Pricing Page at the time of purchase, in your checkout, or in an Order Form.

1.16 "Free Tools" means the free browser tools on our marketing website, including the SAML debugger, the metadata validator and the SCIM conformance tester.

1.17 "Hosted Test IdP" means the test identity provider and SCIM simulator we host for use with Sandboxes.

1.18 "Kill Switch" means the per-Environment control described in clause 8.6.

1.19 "Merchant of Record" or "MoR" means a third-party reseller that sells the Service to you in its own name and collects payment and applicable sales taxes, as described in clause 11.6.

1.20 "Order Form" means an ordering document for the Enterprise plan, or for other negotiated terms, signed by both parties and referring to this Agreement.

1.21 "Plan" means the Free, Pro, Business or Enterprise subscription plan, with the limits and features described on the Pricing Page or in an Order Form.

1.22 "Portal" means the hosted setup portal that IT administrators of Customer Organizations use to configure connections, including portal pages served on a custom domain.

1.23 "Pricing Page" means our public pricing page at https://ohauthcat.com/pricing.

1.24 "Project" means a container in your Account that groups Environments for one of your applications.

1.25 "Service" means the hosted OhAuthCat service for enterprise single sign-on (SAML 2.0 and OpenID Connect) and SCIM 2.0 directory synchronisation, including the Dashboard, the Portal, the API, the Hosted Test IdP, import and export tools, and any Add-on you buy. It excludes Third-Party Services.

1.26 "SDKs and CLI" means our software development kits (including for Node.js, Python and Go) and the ohauthcat command-line tool, licensed under the licence in SDK and CLI Licence.

1.27 "SLA" means our Service Level Agreement in Service Level Agreement, as published at https://ohauthcat.com/legal/sla.

1.28 "Third-Party Services" means products and services not provided by us, including identity providers (such as Okta, Microsoft Entra ID, Google Workspace, JumpCloud and OneLogin), SCIM clients, your own applications and hosting, payment providers and MoRs, and any service to which you stream logs or send webhooks.

1.29 "Usage Data" means data about the operation and use of the Service that we collect or derive, such as performance metrics, error rates, request counts and aggregated or de-identified statistics, that does not identify you, any User or any Customer Organization.

1.30 "User" means an individual end user of a Customer Organization, or of your own organization, whose identity is asserted to your application through the Service or whose record is synchronised through SCIM.


2. Accounts and eligibility #

2.1 Business use only. The Service is for businesses, developers acting for a business, and other organisations. It is not offered to consumers. By accepting this Agreement you confirm that you are acquiring the Service for the purposes of your trade, business, craft or profession and not as a consumer under any consumer protection law, including the Consumer Protection Act, 2019 (India).

2.2 Age and capacity. Every Account Holder must be at least 18 years old and legally able to enter into contracts.

2.3 Accurate information. You must give accurate, complete and current registration, contact and billing information, including your legal name, billing address and, where you have one, your GSTIN or other tax identifier, and keep it up to date.

2.4 Account security. You are responsible for all activity in your Account. You must:
(a) keep Account Holder credentials, passkeys, one-time password devices, API keys, webhook secrets, SCIM bearer tokens and signing keys secret;
(b) use the multi-factor and passkey options the Dashboard offers and, where you enable single sign-on for the Dashboard, keep that configuration secure;
(c) remove Account Holders who no longer need access; and
(d) tell us without undue delay at security@ohauthcat.com if you become aware of any unauthorised access to your Account or any compromise of a key, token or secret.

2.5 Account Holders. You are responsible for your Account Holders' compliance with this Agreement. You may let your contractors and Affiliates use the Service on your behalf, and you remain responsible for them.

2.6 One Free Account. You may not create several Accounts, or several Free Projects beyond the Plan limit, to avoid Plan limits or Fees.

2.7 Sanctioned persons. You may not open an Account if you, or any person that owns or controls you, is on a sanctions list described in clause 27.


3. The Service #

3.1 Provision. Subject to this Agreement and payment of the Fees, we will make the Service available to you during the term of your subscription, according to your Plan, the Documentation and, where it applies, the SLA.

3.2 Right to use. We grant you a non-exclusive, non-transferable, non-sublicensable (except as allowed in clause 3.3) right, during the term, to access and use the Service to add single sign-on and directory synchronisation to your own applications for your internal business purposes and for the benefit of your Customer Organizations and Users.

3.3 Customer Organizations and Users. You may let your Customer Organizations' IT administrators use the Portal, and your Users sign in through the Service, only in connection with your applications. They receive no direct rights from us under this Agreement, and you are responsible for making sure their use of the Service complies with this Agreement.

3.4 Environments. Sandboxes are for development and testing. Production Environments are for live use. We may apply different limits to Sandboxes and may purge them as described in clause 10.2. Only Production Environments count as "production" for Plan limits and the SLA.

3.5 Hosting location. At the date of this Agreement we host the Service and store Customer Data in the Amazon Web Services Asia Pacific (Mumbai) region (ap-south-1), across three availability zones, with content delivery, DNS and security services provided by Cloudflare's global network. Additional regions and data residency choices are planned but are not live. We will not describe a region as available until it is generally available. Details of where data is processed, and by which sub-processors, are in the DPA and in Sub-processors.

3.6 Changes to the Service. We continuously improve the Service and may add, change or remove features. We will not make a change that materially reduces the core functionality of the Service (single sign-on, SCIM directory synchronisation, the Portal and the management API) during your current paid subscription term, except where clause 3.7 or clause 15 applies, or where needed for security, to comply with law, or because a Third-Party Service stops supporting a function.

3.7 Security changes. We may change the Service at any time without notice where we reasonably believe the change is needed to protect the security or integrity of the Service, Customer Data or Users. For example, we may refuse a sign-in that we cannot fully validate, retire a weak cryptographic algorithm, or require a stronger configuration. The Service is designed so that any degraded mode refuses a sign-in rather than accepts one it cannot fully validate, and nothing in this Agreement requires us to change that.

3.8 Support. We provide support according to your Plan, as described on the Pricing Page:
(a) Free: Documentation and community support. Ticketed support is available only for account, billing and security reports.
(b) Pro: email support, with a target first response within two business days.
(c) Business: chat and ticket support, with a target first response within one business day, and within four hours for sign-in outages.
(d) Enterprise: as set out in the Order Form, including a 24/7 emergency line and a named contact.
Response times are targets, not guarantees, unless an Order Form says otherwise. "Business days" and "business hours" mean Monday to Friday, 09:00–18:00 IST, excluding Indian public holidays. Severity 1 incidents on the Business and Enterprise Plans are handled 24×7.

3.9 Status page. We publish a status page at https://status.ohauthcat.com showing the status of sign-in, SCIM, the management API, the Dashboard, the Portal and webhooks, with uptime history. We post incident updates there and publish post-incident reviews for severe incidents.

3.10 Third-Party Services. The Service works with Third-Party Services that we do not control. We are not responsible for their availability, security or behaviour, or for changes they make that affect how they work with the Service. Your use of a Third-Party Service is governed by your agreement with its provider.


4. Customer responsibilities #

4.1 Configurations. You and your Customer Organizations are responsible for the configuration of identity providers, SCIM clients and connections, including metadata, certificates, redirect URIs, attribute mappings, role and group mappings, just-in-time provisioning rules, policies and expressions. The Service validates configurations as described in the Documentation, but you are responsible for checking that a configuration does what you intend before you rely on it in production.

4.2 Customer Organizations. You are responsible for:
(a) deciding which Customer Organizations to create and which of their IT administrators to invite to the Portal;
(b) your contractual relationship with each Customer Organization, including any commitments you make to it about availability, security or data protection, which must be consistent with this Agreement and the DPA; and
(c) promptly disabling or deleting a Customer Organization, connection or directory that should no longer have access.

4.3 Domain verification. Some features, such as activating the Portal, verified-domain policies and just-in-time provisioning, rely on domain verification. You must only verify, or ask a Customer Organization to verify, domains that you or that Customer Organization lawfully control. You must not use the Service to assert identities for email domains that the relevant Customer Organization does not control.

4.4 Your application. You are responsible for your application's use of the identities, attributes, groups and events the Service returns, including how you create sessions, authorise access and handle deprovisioning events. You must validate tokens and webhook signatures as the Documentation describes.

4.5 Keys and secrets. You must keep API keys (other than keys the Documentation describes as publishable), webhook signing secrets, SCIM bearer tokens and private keys secret, store them securely, restrict them to the scopes you need, and rotate them promptly if you suspect compromise. You are responsible for all use of the Service made with your keys until you revoke them.

4.6 Lawful use and notices. You are responsible for the lawfulness of Customer Data and for having all notices, consents and other lawful bases needed for us to process Customer Data under this Agreement and the DPA, including notices to Users and Customer Organizations.

4.7 Compliance with law. You will use the Service in compliance with all laws that apply to you, including data protection, export control, sanctions and anti-bribery laws.

4.8 Your systems. You are responsible for your own applications, hosting, networks and internet connections and for any equipment or software you use to access the Service.

4.9 Contacts. You must keep at least one owner contact email in your Account that you monitor, because we send security notices, suspension notices, Kill Switch events, certificate expiry warnings, webhook endpoint failures and changes to this Agreement to that address.


5. Acceptable use #

5.1 Prohibited uses. You must not, and must not allow any Account Holder, Customer Organization, User or third party to, use the Service to:
(a) send, host, facilitate or support phishing, including pages, flows or connections that impersonate an identity provider, brand or sign-in page to deceive Users;
(b) harvest, collect or capture credentials, session tokens, one-time codes or other authentication secrets from anyone who has not knowingly authorised it, or attempt to intercept another party's sign-ins;
(c) distribute malware, ransomware, spyware or any other harmful code, or use any Portal, custom domain, webhook or asset URL to host or point to it;
(d) send spam or unsolicited messages, including through Portal invitations;
(e) impersonate any person or organisation, or misrepresent your affiliation with any person or organisation, including by using another party's brand on the Portal or a custom domain without its permission;
(f) infringe, misappropriate or violate any intellectual property, privacy or other right of any person;
(g) process data unlawfully, or process special categories of personal data or children's data through the Service except to the extent strictly needed for identity attributes and permitted by law;
(h) engage in or facilitate fraud, money laundering, terrorism financing or any other unlawful activity; or
(i) violate any law, including sanctions and export control laws.

5.2 Prohibited technical activities. You must not, and must not allow anyone else to:
(a) gain or attempt to gain unauthorised access to the Service, another customer's Account, Environment or data, or any related system or network;
(b) probe, scan or test the vulnerability of the Service, or run load, stress or performance tests against it, without our prior written consent; security research is welcome under our published vulnerability disclosure policy at https://ohauthcat.com/security/disclosure (contact details in https://ohauthcat.com/.well-known/security.txt), which takes precedence for good-faith research;
(c) scrape, crawl or harvest data from the Service, the Portal, the Documentation or our websites by automated means other than through the API as documented;
(d) interfere with or disrupt the integrity or performance of the Service, including by exceeding rate limits, sending malformed traffic intended to cause failures, or circumventing rate limits, bot checks, plan limits or usage controls;
(e) reverse engineer, decompile, disassemble or otherwise attempt to derive the source code, algorithms or non-public interfaces of the Service, except to the extent applicable law expressly permits this despite this restriction;
(f) copy, modify or create derivative works of the Service (other than of the SDKs and CLI as their licence allows), or use the Service or its Documentation to build a competing product or service;
(g) resell, sublicense, rent, lease, time-share or offer the Service as a standalone single sign-on or directory service bureau to third parties, or otherwise make it available to anyone other than as part of your own applications as allowed by clause 3; or
(h) remove, obscure or alter any proprietary notice, or, on the Free plan, the "Secured by OhAuthCat" badge.

5.3 Fair use of shared resources. Each Plan includes the limits stated on the Pricing Page and in the Documentation, such as connection counts, Environments, team seats and rate limits. We may throttle traffic that exceeds rate limits or threatens the stability of the Service for other customers, and we will tell you if we do this other than briefly.

5.4 Reporting abuse. Anyone may report abuse of the Service at abuse@ohauthcat.com. We review reports and may act under clause 8.


6. Customer Data #

6.1 Ownership. As between the parties, you (or your Customer Organizations and Users, as applicable) own all rights in Customer Data. We acquire no ownership of Customer Data under this Agreement.

6.2 Licence to us. You grant us a worldwide, non-exclusive, royalty-free licence, for the term of this Agreement and any post-termination period in clause 22, to host, copy, transmit, display and otherwise process Customer Data only as needed to provide, secure and support the Service, to prevent or address service, security or technical problems, to comply with law, and as otherwise described in the DPA.

6.3 Data processing. The DPA forms part of this Agreement. To the extent we process personal data contained in Customer Data, we act as your processor (or, where you are yourself a processor for a Customer Organization, as your sub-processor) and will do so in accordance with the DPA. Our processing of personal data as a controller, for example of Account Holders' account details, billing contacts and support correspondence, is described in our Privacy Policy in Privacy Policy.

6.4 Usage Data. We may collect and use Usage Data to operate, secure, maintain and improve the Service, to plan capacity, and to produce aggregated statistics. Usage Data does not identify you, any Customer Organization or any User, and we will not disclose it in a form that does.

6.5 Retention during the term. We keep categories of Customer Data for the periods stated in the Documentation for your Plan. At the date of this Agreement these are:

DataFreeProBusinessEnterprise
Data: Events APIFree: 7 daysPro: 30 daysBusiness: 90 daysEnterprise: As agreed
Data: Audit logFree: 7 daysPro: 90 daysBusiness: 1 yearEnterprise: As agreed
Data: API request log and sign-in timelinesFree: 3 daysPro: 30 daysBusiness: 90 daysEnterprise: As agreed
Data: SCIM request logFree: 3 daysPro: 30 daysBusiness: 90 daysEnterprise: As agreed
Data: Debug bundlesFree: 7 daysPro: 7 daysBusiness: 30 daysEnterprise: As agreed
Data: Raw IP addresses (security logs only)Free: 30 daysPro: 30 daysBusiness: 30 daysEnterprise: 30 days

A User profile is deleted after 13 months without a sign-in, and at once when its connection or Customer Organization is deleted. Retention beyond these periods is available through the extended retention Add-on. We may shorten a retention period only with 30 days' notice and never below the period stated for your Plan when you bought it, during that paid term.

6.6 Export. During the term you may export Customer Data through the API, the Dashboard and the CLI, including a full export of connections, directories, Customer Organizations and settings in our documented import bundle format, and audit log exports in CSV format. We do not charge for exports. Signing private keys and secrets are not exportable where the Documentation says so, for security reasons.

6.7 Debug captures. Some troubleshooting features record redacted protocol payloads, such as SAML responses with sensitive values removed, only inside an explicit, time-limited capture window that you or a Customer Organization administrator opens. You are responsible for opening capture windows only when needed.

6.8 Backups. We keep backups of the Service for disaster recovery. Data deleted from the live Service may remain in encrypted backups until those backups expire under our backup cycle, which is 60 days (covering 7-day point-in-time recovery and weekly snapshots), after which it is overwritten. Data in backups is not used for any other purpose.

6.9 Security. We will maintain the technical and organisational security measures described in the DPA and its security annex. We do not currently hold a SOC 2 report or any other third-party certification, and we will not represent that we do until it is issued. We will tell you about personal data breaches as the DPA requires.


7. Our personnel and access to Customer Data #

7.1 Our staff access production systems only through audited, time-limited access controls, and only as needed to provide and support the Service, investigate abuse or security incidents, or comply with law. Staff access to a specific Account's data requires a recorded reason and is logged.

7.2 We will not access the content of Customer Data for any other purpose, except with your instructions (for example when you ask support to look at a connection) or as required by law.


8. Suspension, account takedown and the Kill Switch #

8.1 Grounds for suspension. We may suspend your Account, a Project or an Environment, in whole or in part, if we reasonably believe that:
(a) you, an Account Holder, a Customer Organization or a User is using the Service in breach of clause 5, or in a way that creates a risk of harm to the Service, other customers, Users or third parties;
(b) your Account or keys have been compromised, or a configuration in your Account is being used to deceive Users;
(c) suspension is needed to comply with law, a court order or a binding request from a competent authority;
(d) Fees are overdue as described in clause 11.8; or
(e) you have breached clause 27 (export controls and sanctions).

8.2 Account takedown. Where clause 8.1(a), (b), (c) or (e) applies, our staff may suspend your whole Account. While your Account is suspended:
(a) all of its Environments refuse single sign-on and SCIM requests;
(b) Portal links stop working; and
(c) custom Portal, broker and SCIM domains are taken offline.
Every suspension and every lifting of a suspension is recorded with a reason in our audit trail.

8.3 Notice. We will notify the owner contacts on your Account by email when we suspend it, with the reason, unless we reasonably believe that notice would compromise an investigation, a legal obligation or the safety of Users. Where the risk allows it, we will give you notice and a reasonable chance to cure before suspension, and we will limit suspension to the affected Project, Environment, connection or Customer Organization where that is enough to address the risk.

8.4 Lifting suspension. We will lift a suspension promptly once the reason for it has been resolved to our reasonable satisfaction. Lifting an account suspension does not change the state of any Kill Switch you have set.

8.5 Effect. Suspension does not end this Agreement and does not stop Fees from accruing, except where the suspension was caused by our error. Downtime caused by a suspension under this clause does not count as downtime under the SLA. During a suspension you may still contact support and, unless the suspension is for a reason in clause 8.1(c) or (e), request an export of Customer Data.

8.6 Your Kill Switch. Each Environment has a Kill Switch that owners and admins of your Account can turn off and on in the Dashboard, giving a reason. While an Environment's Kill Switch is off, all single sign-on requests (including WorkOS-compatible routes and test sign-ins) and SCIM requests to that Environment are refused with a dedicated error code, while the management API, the Dashboard, webhooks and Customer Data stay available so that you can fix the cause. Our staff may also turn off an Environment's Kill Switch under clause 8.1, and every use of the Kill Switch is audited. You are responsible for the consequences of using the Kill Switch for your Customer Organizations and Users. Downtime while the Kill Switch is off is excluded from the SLA.


9. Beta Features #

9.1 We may offer Beta Features at our discretion. Beta Features are provided "as is", may be incomplete or contain errors, may change or be withdrawn at any time without notice, and are not covered by the SLA or by any support commitment.

9.2 You should not rely on a Beta Feature for production sign-ins unless the Documentation says it is suitable. Our total liability for Beta Features is limited as stated in clause 21.5.

9.3 Beta Features may be subject to additional terms we show you when you enable them. Those terms apply only to that Beta Feature.


10. Free Plan, Sandboxes, the Hosted Test IdP and Free Tools #

10.1 Free Plan. The Free Plan is provided without charge, with the limits on the Pricing Page (including three production single sign-on connections and three production directory connections). It has no SLA and only the support described in clause 3.8(a). We may change or end the Free Plan, or its limits, with at least 30 days' notice. If we end it, we will let you upgrade or export your Customer Data before it ends. We do not close or delete Free Accounts for inactivity.

10.2 Sandboxes and their purge. Sandboxes are for development and testing only and must not be used to authenticate real Users to production applications. A Sandbox created without an Account (an "unclaimed" Sandbox) is deleted, with all its data, seven days after it is created unless it is claimed into an Account before then. You can reset a Sandbox at any time. We may also limit or purge Sandbox data as described in the Documentation. Purged data cannot be recovered.

10.3 Hosted Test IdP. The Hosted Test IdP and SCIM simulator may be used only with Sandboxes, with test identities, to test integrations. They must not be used to assert the identity of real people or to access real systems. Their identities, keys and behaviour may change at any time.

10.4 Free Tools. The Free Tools run in your web browser. The data you paste or load into them is processed in your browser and is not sent to our servers except as the tool states. The Free Tools are provided "as is", without support, warranty or SLA, and you use their results at your own risk. You must not use them to analyse data you are not authorised to handle.

10.5 Liability. Clause 21.5 applies to the Free Plan, Sandboxes, the Hosted Test IdP and the Free Tools.


11. Fees, billing, renewals and taxes #

11.1 Fees. You will pay the Fees for your Plan and Add-ons. Prices on the Pricing Page are in US dollars unless stated otherwise, and separate prices in Indian rupees apply to customers billed in India. At the date of this Agreement, Pro is US$99 per month and Business US$499 per month per paid Project, with lower annual prices where offered, and Enterprise starts at US$3,000 per month, billed annually, under an Order Form. Prices exclude taxes.

11.2 Subscriptions and renewal. Paid Plans and Add-ons are subscriptions. Monthly subscriptions renew automatically for successive one-month periods, and annual subscriptions (including Enterprise unless the Order Form says otherwise) for successive one-year periods, each at the then-current price unless clause 11.3 or an Order Form says otherwise, until cancelled.

11.3 Price changes. We may change the Fees for a Plan or Add-on with at least 30 days' notice for monthly subscriptions and at least 60 days' notice before renewal for annual subscriptions. A price change takes effect from your next renewal after the notice period. If you do not agree to the change, you may cancel before it takes effect.

11.4 Cancellation. You may cancel a paid subscription at any time in the Dashboard or by contacting billing@ohauthcat.com. Each billing period is paid for in full in advance. Cancelling stops the subscription from renewing; you keep access to the paid Plan until the end of the period you have paid for, and your Account then moves to the Free Plan as described in clause 12.3. We do not give refunds, prorated amounts or credits for the rest of a period, for unused features or for downgrades, whether you cancel or close your Account, except where applicable law requires a refund or this Agreement or the SLA expressly provides for a credit or refund.

11.5 Customers billed in Indian rupees. If you are billed in Indian rupees, we are the seller. We charge you through Razorpay or, as a fallback, Cashfree, using their hosted checkout. We issue GST tax invoices under services accounting code (SAC) 998315 and charge GST at the applicable rate (18% at the date of this Agreement) in addition to the Fees. If you give us a valid GSTIN, we will show it on the invoice so that you can claim input tax credit where eligible. You are responsible for the accuracy of your GSTIN and billing address.

11.6 Customers billed in other currencies: Merchant of Record. If you are billed in any currency other than Indian rupees, you buy the Service through a Merchant of Record, which at the date of this Agreement is Dodo Payments (Dodo Payments Inc. and its group companies). If we change the Merchant of Record, we will tell you before your next charge goes through the new one. In either case:
(a) the MoR is the seller of record of the subscription and charges you the Fees and any applicable sales tax, VAT or GST, and issues the invoice or receipt;
(b) your purchase from the MoR is also governed by the MoR's own buyer terms, which you accept at checkout; payment, refund, chargeback and tax matters are handled under those terms;
(c) this Agreement continues to govern your access to and use of the Service and our obligations to you, and the MoR has no obligation to provide the Service; and
(d) if the MoR's terms conflict with this Agreement on how you use the Service, this Agreement prevails; on payment, invoicing and tax collection, the MoR's terms prevail.

11.7 Payment details. Payments are taken only through the payment provider's or MoR's hosted checkout. We do not receive or store full card numbers. You authorise the payment provider or MoR to charge your chosen payment method for recurring Fees. For recurring payments in Indian rupees, the e-mandate registration, the additional factor of authentication and the pre-debit notice at least 24 hours before each charge, required by the Reserve Bank of India's rules on recurring transactions, are handled by our payment gateway (Razorpay or Cashfree). Enterprise customers are invoiced as set out in the Order Form.

11.8 Late payment. If a payment fails or an invoice is unpaid when due, we will notify you and the payment provider or MoR may retry the charge. You have a grace period of 14 days after the due date, during which we will send reminder emails. If Fees remain unpaid at the end of the grace period, we may, after giving at least 7 days' further written notice, move your Account to the Free Plan, suspend paid features, or suspend the Account under clause 8.1(d). We will not suspend sign-ins for non-payment while you are disputing the charge reasonably and in good faith and cooperating to resolve it. For invoiced customers, overdue amounts may bear interest at 1% per month, or the maximum rate allowed by law if that is lower.

11.9 Taxes. Fees exclude all taxes, duties and levies, which you will pay except for taxes on our net income. If you are required by law to withhold tax from a payment to us (for example tax deducted at source in India), you will gross up the payment so that we receive the full amount invoiced, unless the parties agree otherwise, and you will give us the withholding certificate (for example Form 16A) within the statutory period.

11.10 Billing disputes. You must raise any billing dispute in writing within 60 days of the charge or invoice date. The parties will work in good faith to resolve it.


12. Upgrades, downgrades and Plan limits #

12.1 Plan limits. Your Plan sets limits such as the number of production single sign-on and directory connections, Projects, Environments, team seats, custom domains, retention periods and features. Sandbox connections do not count toward production connection limits.

12.2 Upgrades. You may upgrade at any time. An upgrade takes effect at once. You will be charged a prorated amount for the rest of the current billing period, or as the payment provider or MoR calculates it.

12.3 Downgrades. A downgrade, including on cancellation or under clause 11.8, takes effect at the end of the current billing period (or at once for non-payment). After a downgrade:
(a) sign-ins never stop because of a downgrade: existing connections, directories, rules and policies continue to work and to be enforced as configured, even if they exceed the new Plan's limits;
(b) you cannot create new resources, or edit existing ones in a way that uses features or quantities above the new Plan, until you are within the limits; the Service returns a plan_limit_reached error;
(c) you can always delete resources;
(d) data beyond the new Plan's retention periods will be deleted at the next retention run; and
(e) features that the new Plan does not include, such as custom broker and SCIM domains or log streaming destinations, may be turned off, with at least 14 days' notice where the feature serves live traffic, so that you can update your Customer Organizations.

12.4 Exceeding limits. If you exceed a limit other than through a downgrade, we may ask you to upgrade or remove the excess. We will not stop sign-ins for existing connections without first giving you at least 30 days' notice.


13. WorkOS-compatible API support window #

13.1 What it is. The compat/workos API is a migration aid that lets applications built against the WorkOS single sign-on and directory sync interfaces use the Service with minimal changes. It can be enabled per Environment.

13.2 Support window. For each Environment, the compat/workos API has:
(a) standard support for 6 months from the date you enable it in that Environment, included in your Plan;
(b) optional extended support as a paid Add-on for months 7 to 12 (US$100 per month at the date of this Agreement) and months 13 to 18 (US$250 per month at the date of this Agreement); and
(c) end of support after month 18, when the compatible routes stop working and return a compat_support_expired (HTTP 410) error.

13.3 Notices. From month 4, responses from the compatible routes carry Deprecation and Sunset headers, and we email owners and admins at each phase. You are responsible for migrating to the native API before the end of your support window. Downtime of the compatible routes after the end of the support window is not covered by the SLA.

13.4 Compatibility. We aim to match the documented behaviour of the WorkOS interfaces we support, but we do not guarantee exact compatibility with every behaviour of a third-party service, and we are not affiliated with or endorsed by WorkOS. "WorkOS" is used only to describe compatibility.


14. API changes and versioning #

14.1 Versioned endpoints. Server-to-server API endpoints carry a major version in the path (for example /v1/). Minor versions are additive and selected with the OhAuthCat-Version header; new behaviour is opt-in, and each Environment has a pinned default version that changes only when you upgrade it.

14.2 Stability within a major version. Within a major version we will not make breaking changes to documented API behaviour except under clause 3.7 (security), to comply with law, or where a Third-Party Service forces the change. Adding new endpoints, fields, event types, error codes or optional parameters is not a breaking change, and your integration must tolerate them.

14.3 Unversioned endpoints. Browser- and identity-provider-facing endpoints (authorisation, assertion consumer service, OIDC callback, service provider metadata, Portal pages and the SCIM base URL) are not versioned, because identity provider administrators configure them once and keep them for years. We will keep those URLs stable and will follow your Environment's version pin for their behaviour.

14.4 Deprecation. We will announce the deprecation of a major API version, endpoint or documented behaviour at least 12 months before we remove it (or 6 months for a Beta Feature that becomes generally available in a changed form), except under clause 3.7. Deprecated endpoints send Deprecation and Sunset headers. We will keep at least one major version supported at all times, and we will keep supporting the previous major version for 12 months after its successor is released.

14.5 Webhooks. Webhook payloads carry an API version. Each webhook endpoint defaults to your Environment's version pin.


15. Intellectual property #

15.1 Our IP. We and our licensors own all rights, title and interest in the Service, the SDKs and CLI, the Documentation, the Free Tools, Usage Data and all related software, designs, trade marks and know-how, including all improvements and derivative works, whoever makes them. Except for the rights expressly granted in this Agreement and the SDK and CLI licence, no rights are granted to you, by implication or otherwise.

15.2 SDKs and CLI. Your use of the SDKs and CLI is governed by SDK and CLI Licence. Third-party components included with them are governed by their own licences listed in the THIRD_PARTY_LICENSES file shipped with them.

15.3 Your marks and branding. You grant us a non-exclusive licence during the term to use the names, logos and branding you upload to display them in the Portal, emails and custom domains as you configure. You confirm you have the right to use that branding.

15.4 Feedback. If you give us suggestions, ideas, bug reports or other feedback about the Service ("Feedback"), you grant us a perpetual, irrevocable, worldwide, royalty-free licence to use and exploit it without restriction or obligation. Feedback does not include Customer Data or your Confidential Information, and we will not identify you as its source without your consent.


16. Publicity #

16.1 We may identify you as a customer by name and logo on our website and in marketing materials. You may opt out at any time by writing to legal@ohauthcat.com, and we will remove your name and logo within 30 days from materials we control.

16.2 We will not issue a press release, case study or quote about you without your prior written consent.


17. Third-party open source and connected services #

17.1 The Service may include open source components, which are provided under their own licences. Nothing in this Agreement limits your rights under those licences.

17.2 If you configure log streaming, webhooks or an integration with a Third-Party Service, you instruct us to send the relevant Customer Data to that Third-Party Service. That service is not our sub-processor, and we are not responsible for what it does with the data.


18. Confidentiality #

18.1 Definition. "Confidential Information" means all non-public information disclosed by one party ("Discloser") to the other ("Recipient") that is marked confidential or that a reasonable person would understand to be confidential, including Customer Data, non-public pricing and Order Form terms, security reports and questionnaires, product plans and the non-public parts of the Service.

18.2 Exclusions. Confidential Information does not include information that the Recipient can show (a) is or becomes public through no fault of the Recipient, (b) was lawfully known to the Recipient before receipt without a duty of confidence, (c) is lawfully received from a third party without a duty of confidence, or (d) is independently developed without use of the Discloser's Confidential Information. Exclusions (a) to (d) do not apply to personal data in Customer Data, which is protected by the DPA in all cases.

18.3 Obligations. The Recipient will use the Discloser's Confidential Information only to exercise its rights and perform its obligations under this Agreement, will protect it with at least the care it uses for its own similar information and no less than reasonable care, and will disclose it only to its and its Affiliates' employees, contractors, advisers and sub-processors who need to know it and are bound by confidentiality obligations at least as protective as these.

18.4 Compelled disclosure. The Recipient may disclose Confidential Information if required by law or by a court or competent authority, if it gives the Discloser prompt notice (where legally allowed) and reasonable help to seek a protective order, and discloses only what is required. Requests from authorities for Customer Data are handled under the DPA.

18.5 Duration. These obligations last during the term and for five years after it ends, and for trade secrets and Customer Data for as long as they remain protected by law or held by the Recipient.

18.6 Return or deletion. On termination, each party will return or delete the other's Confidential Information on request, except for copies kept under a legal obligation or in routine backups, which remain protected by this clause until deleted. Customer Data is handled under clause 22.


19. Warranties and disclaimers #

19.1 Mutual warranties. Each party warrants that it has the power and authority to enter into this Agreement and that its acceptance has been duly authorised.

19.2 Our warranties. For paid Plans, we warrant that during the subscription term (a) the Service will perform materially as described in the Documentation, and (b) we will not materially reduce the security measures described in the DPA. If we breach this warranty, you must tell us in writing within 30 days of discovering the breach, and as your exclusive remedy we will use reasonable efforts to correct the non-conformity; if we cannot do so within 30 days, either party may terminate the affected subscription, and we will refund any prepaid Fees for the remaining term. This warranty does not apply to Beta Features, the Free Plan, Sandboxes, the Hosted Test IdP, the Free Tools, or problems caused by your configurations, Third-Party Services or misuse.

19.3 Your warranties. You warrant that (a) you have all rights, consents and lawful bases needed for us to process Customer Data under this Agreement and the DPA, and (b) your use of the Service and Customer Data complies with this Agreement and applicable law.

19.4 Disclaimer. Except as expressly stated in this Agreement, the Service, the SDKs and CLI, the Documentation and everything else we provide are provided "as is" and "as available". To the maximum extent permitted by law, we disclaim all other warranties and conditions, express, implied or statutory, including any implied warranties of merchantability, satisfactory quality, fitness for a particular purpose, title and non-infringement. We do not warrant that the Service will be uninterrupted or error-free, that it will detect or prevent every unauthorised access, or that it will work with every identity provider configuration. Availability commitments are only those in the SLA.

19.5 Identity decisions. The Service verifies identity assertions and directory data received from identity providers configured by you or your Customer Organizations. We are not responsible for the accuracy of information supplied by those identity providers, or for access decisions your application makes based on it.


20. Indemnities #

20.1 Our IP indemnity. We will defend you against any third-party claim alleging that your use of the Service, as provided by us and used in accordance with this Agreement, infringes that third party's patent, copyright or trade mark, or misappropriates its trade secret ("IP Claim"), and will pay any damages and costs finally awarded against you, or agreed by us in a settlement, for the IP Claim.

20.2 Exclusions. Clause 20.1 does not apply to claims arising from (a) Customer Data, your branding or your applications; (b) combination of the Service with products, services or data not provided by us, where the claim would not exist without the combination; (c) modifications not made by us; (d) use in breach of this Agreement; (e) Beta Features, the Free Plan, Sandboxes, the Hosted Test IdP or the Free Tools; or (f) open source components.

20.3 Remedies. If the Service is, or we reasonably believe is likely to be, the subject of an IP Claim, we may at our option and cost (a) obtain the right for you to continue using it, (b) modify it so that it is non-infringing without materially reducing its functionality, or (c) if neither is commercially reasonable, terminate the affected subscription and refund any prepaid Fees for the remaining term. This clause 20 states our entire liability, and your exclusive remedy, for IP Claims.

20.4 Your indemnity. You will defend us and our Affiliates, officers and employees against any third-party claim (including a claim by a Customer Organization, a User or a regulator) arising from (a) Customer Data, including a claim that it infringes a third party's rights or that its processing under this Agreement violates law; (b) your applications, or your or your Account Holders' use of the Service in breach of clause 4, clause 5 or applicable law; or (c) your relationship with your Customer Organizations, and will pay any damages, fines and costs finally awarded, or agreed by you in a settlement, for that claim.

20.5 Procedure. The indemnified party must (a) notify the indemnifying party promptly of the claim (a delay excuses the indemnifying party only to the extent it is prejudiced), (b) give the indemnifying party sole control of the defence and settlement, except that no settlement that imposes an obligation or admission on the indemnified party may be made without its consent (not to be unreasonably withheld), and (c) provide reasonable cooperation at the indemnifying party's cost. The indemnified party may take part with its own counsel at its own cost.


21. Limitation of liability #

21.1 Exclusion of indirect losses. Except for the Excluded Claims in clause 21.3, neither party is liable to the other, whether in contract, tort (including negligence), breach of statutory duty or otherwise, for any (a) loss of profits, revenue, business, goodwill or anticipated savings, (b) loss or corruption of data (except to the extent of the cost of restoring data from backups the defaulting party was obliged to keep), or (c) indirect, incidental, special, consequential, exemplary or punitive damages, even if advised of their possibility.

21.2 General cap. Except for the Excluded Claims and clause 21.4, each party's total aggregate liability arising out of or relating to this Agreement is limited to the total Fees paid and payable by you under this Agreement for the 6 months before the event that first gave rise to the liability.

21.3 Excluded Claims. The limits in clauses 21.1 and 21.2 do not apply to (a) a party's indemnity obligations under clause 20; (b) breach of clause 18 (Confidentiality), other than breaches involving Customer Data, which fall under clause 21.4; (c) your obligation to pay Fees; (d) a party's gross negligence, fraud or wilful misconduct; (e) your breach of clause 5 (Acceptable use); or (f) any liability that cannot be limited or excluded by law (together, the "Excluded Claims").

21.4 Data protection super-cap. Each party's total aggregate liability for breach of the DPA or of clause 6.9, including any personal data breach, is limited to two times (2×) the total Fees paid and payable by you for the 6 months before the event that first gave rise to the liability. For those claims this super-cap replaces, and is not added to, the cap in clause 21.2.

21.5 Free and test services. For the Free Plan, Sandboxes, the Hosted Test IdP, the Free Tools and Beta Features, and to the maximum extent permitted by law, our total aggregate liability is limited to US$20 (or its equivalent in Indian rupees). The Free Plan, Sandboxes, the Hosted Test IdP, the Free Tools and Beta Features are provided "as is", and to the maximum extent permitted by law we have no liability for them; this cap applies only where liability cannot be excluded.

21.6 SLA credits. Service credits under the SLA count toward the cap in clause 21.2.

21.7 Basis of the bargain. The parties agree that these limits reflect an informed allocation of risk and form an essential part of the bargain, and that the Fees reflect them.


22. Term and termination #

22.1 Term. This Agreement starts when you first accept it and continues until every subscription has ended and your Account is closed.

22.2 Termination for convenience. You may close your Account at any time in the Dashboard; clause 22.7A then applies. Closing stops the Service at once, including any paid Plan. Fees already paid or due for the current billing period, or for Enterprise the term in the Order Form, are not refunded or prorated (clause 11.4), unless the Order Form says otherwise or the law requires a refund. We may terminate this Agreement for convenience for the Free Plan with 30 days' notice, and for paid Plans at the end of a billing period with at least 90 days' notice.

22.3 Termination for cause. Either party may terminate this Agreement or an affected subscription by written notice if the other party (a) materially breaches this Agreement and does not cure the breach within 30 days of written notice describing it, or (b) becomes subject to insolvency, liquidation, administration or similar proceedings, or makes an assignment for the benefit of creditors, to the extent permitted by law. We may terminate at once by notice for a serious or repeated breach of clause 5 or a breach of clause 27.

22.4 Refund on termination by you for cause. If you terminate for our uncured material breach, we will refund any prepaid Fees for the remaining term after the termination date.

22.5 Effect of termination. When this Agreement or a subscription ends:
(a) your rights to use the affected Service end, and we will stop processing sign-ins and SCIM requests for the affected Environments;
(b) you must pay all Fees accrued up to the end date, and, unless you terminated for our breach, any remaining committed Fees under an Order Form;
(c) you must stop using the SDKs and CLI to access the affected Service.

22.6 Data export window. For 30 days after termination or expiry (the "Export Window"), we will keep your Customer Data and, on request, give you read-only access to the Dashboard and export API so that you can export it in the formats described in clause 6.6. This does not apply when you close your Account yourself (clause 22.7A), to Sandboxes purged under clause 10.2 or to data whose retention period has already ended.

22.7 Deletion. After the Export Window we will delete Customer Data from the live Service, and as backups expire under clause 6.8 it leaves the backups, so that all Customer Data, including backups, is deleted within 90 days after termination or expiry, unless law requires us to keep it. Audit log entries leave through their normal retention purge. On written request we will confirm deletion in writing.

22.7A Closing your own Account. If you close your Account yourself, the Service stops at once for all your Environments, and there is no Export Window, so export your Customer Data before you close. An Account owner may reopen the Account within 7 days of closure. After that, we delete Customer Data from the live Service, and all of it, including backups, is deleted within 60 days after the 7-day window ends, except data the law requires us to keep.

22.7B Billing records. Whichever way the Agreement ends, we keep invoices, billing, tax and accounting records for 8 years as the law requires.

22.8 Survival. Clauses 1, 6.1, 6.8, 11 (for amounts due), 15, 18, 19.4, 20, 21, 22.5 to 22.8, and 25 to 32 survive termination, together with any other clause that by its nature should survive.


23. Force majeure #

23.1 Neither party is liable for delay or failure to perform caused by events beyond its reasonable control, including natural disasters, epidemics, war, terrorism, riots, government action, labour disputes not involving the affected party's staff, failures of public utilities or telecommunications networks, failures of upstream internet or cloud providers not caused by the affected party, and large-scale denial-of-service attacks that reasonable protections could not prevent ("Force Majeure").

23.2 The affected party must notify the other promptly, use reasonable efforts to mitigate, and resume performance as soon as practicable. Force Majeure does not excuse your obligation to pay Fees already due.

23.3 If a Force Majeure event prevents performance of a material part of this Agreement for more than 30 consecutive days, either party may terminate the affected subscription by notice, and we will refund any prepaid Fees for the remaining term.


24. Assignment and subcontracting #

24.1 Neither party may assign or transfer this Agreement without the other party's prior written consent, which will not be unreasonably withheld, except that either party may assign it without consent to an Affiliate or to a successor in a merger, acquisition, corporate reorganisation or sale of all or substantially all of its relevant business or assets, if the assignee agrees in writing to be bound by this Agreement and is not a competitor of the other party or a sanctioned person. Any other attempted assignment is void.

24.2 We may use subcontractors and sub-processors to provide the Service, as described in the DPA, and remain responsible for them.


25. Governing law and disputes #

25.1 Governing law. This Agreement and any dispute or claim arising out of or in connection with it, including non-contractual disputes, are governed by the laws of India, without regard to conflict of law rules. The United Nations Convention on Contracts for the International Sale of Goods does not apply.

25.2 Informal resolution. Before starting proceedings, the parties will try to resolve any dispute by negotiation between senior representatives for 30 days after one party notifies the other of the dispute.

25.3 Customers in India. If you are incorporated or resident in India, the courts at Chennai, Tamil Nadu have exclusive jurisdiction over any dispute.

25.4 Customers outside India. If you are incorporated or resident outside India, any dispute that is not resolved under clause 25.2 will be finally resolved by arbitration under the Arbitration and Conciliation Act, 1996, before a sole arbitrator appointed by agreement of the parties or, failing agreement within 30 days, in accordance with that Act. The seat and venue of arbitration is Chennai, India, and the language is English. The arbitration is ad hoc, without an arbitral institution, and hearings may be held virtually. The award is final and binding, and judgment may be entered in any court of competent jurisdiction.

25.5 Interim relief. Nothing in this clause prevents a party from seeking urgent injunctive or interim relief from any competent court to protect its intellectual property or Confidential Information.


26. Anti-bribery and ethics #

26.1 Each party will comply with all applicable anti-bribery and anti-corruption laws, including the Prevention of Corruption Act, 1988 (India), the US Foreign Corrupt Practices Act and the UK Bribery Act 2010. Neither party will offer, give, request or accept any bribe, kickback or improper payment or advantage in connection with this Agreement.

26.2 Each party will notify the other promptly if it learns of a breach of this clause relating to this Agreement.


27. Export controls and sanctions #

27.1 The Service, the SDKs and CLI may be subject to export control and sanctions laws of India, the United States, the European Union, the United Kingdom and other countries. You represent that neither you nor any person that owns or controls you, nor any Account Holder, is (a) located in, organised under the laws of, or ordinarily resident in a country or territory subject to comprehensive sanctions, or (b) identified on, or owned or controlled by a person identified on, any applicable sanctions or restricted party list.

27.2 You will not use, export, re-export or allow access to the Service in breach of those laws, including for any prohibited end use.

27.3 We may suspend or terminate the Service at once, without liability, to the extent needed to comply with these laws.


28. Notices #

28.1 To you. We may give notices to the owner contact emails on your Account, through the Dashboard, or, for general changes, by posting on our website. Notices of breach, suspension or termination will be sent by email to the owner contacts.

28.2 To us. You must send legal notices to legal@ohauthcat.com, with a copy by courier or registered post to Generic Technologies Private Limited, 201/1, Arcot Road, Virugambakkam, Chennai, Tamil Nadu 600092, India, marked "Attention: Legal". Billing notices go to billing@ohauthcat.com, security reports to security@ohauthcat.com, privacy requests to privacy@ohauthcat.com and support requests to support@ohauthcat.com. Abuse reports go to abuse@ohauthcat.com, grievances to grievance@ohauthcat.com and sub-processor questions to subprocessors@ohauthcat.com.

28.3 Timing. An email notice is received when sent, unless the sender receives a delivery failure. A courier notice is received on delivery.

28.4 Grievance Officer. In accordance with the Information Technology Act, 2000 and the rules under it, and the Digital Personal Data Protection Act, 2023, our Grievance Officer is Koushik Raj, Chief Executive Officer, reachable at grievance@ohauthcat.com and at the address in clause 28.2. We will acknowledge grievances within 24 hours and resolve them within 15 days, or the shorter period the law requires.


29. Changes to this Agreement #

29.1 We may update this Agreement, the SLA, the DPA and the SDK and CLI licence from time to time. We will give at least 30 days' notice by email to the owner contacts and on our website before a material change takes effect. Changes required by law, or that only add new services or features, may take effect sooner.

29.2 If you do not agree to a material change, you may cancel before it takes effect. If you cancel for this reason during a prepaid annual term, we will refund the prepaid Fees for the remaining term. Continued use of the Service after the change takes effect means you accept it.

29.3 Changes do not apply to an Enterprise Order Form during its current term unless the Order Form allows it or you agree in writing, except changes required by law or the security changes in clause 3.7.

29.4 We keep previous versions of this Agreement at https://ohauthcat.com/legal/archive/.


30. General #

30.1 Independent contractors. The parties are independent contractors. Nothing in this Agreement creates a partnership, joint venture, agency or employment relationship.

30.2 No third-party beneficiaries. There are no third-party beneficiaries of this Agreement, except the persons indemnified under clause 20.

30.3 Waiver. A failure or delay in exercising a right is not a waiver of it.

30.4 Severability. If any provision is held invalid or unenforceable, it will be modified to the minimum extent necessary to make it enforceable, and the rest of this Agreement continues in effect.

30.5 Language. This Agreement is written in English. Any translation is for convenience only, and the English version prevails.

30.6 Electronic acceptance. The parties agree that this Agreement may be accepted electronically and that an electronic record of acceptance is valid evidence of it under the Information Technology Act, 2000.

30.7 Purchase orders. Terms in a purchase order, vendor registration form or similar document you issue have no effect, even if we accept or sign it, unless an Order Form expressly incorporates them.


31. Entire agreement and order of precedence #

31.1 Entire agreement. This Agreement, together with any Order Form, the DPA, the SLA, the SDK and CLI licence and the documents they refer to, is the entire agreement between the parties about its subject matter and replaces all prior agreements, proposals and representations about it. Each party confirms that it has not relied on any statement not set out in this Agreement. Nothing in this clause limits liability for fraud.

31.2 Order of precedence. If there is a conflict between these documents, the following order applies, highest first:
(a) an Order Form (only for the subscriptions it covers);
(b) the DPA;
(c) the SLA;
(d) this Agreement (Terms of Service);
(e) the Documentation and the Pricing Page.

31.3 Order Form changes. An Order Form overrides this Agreement only where it expressly refers to the clause it changes, or the conflict is unavoidable.


32. Contact #

Generic Technologies Private Limited (OhAuthCat)
201/1, Arcot Road, Virugambakkam, Chennai, Tamil Nadu 600092, India
Legal: legal@ohauthcat.com · Support: support@ohauthcat.com · Billing: billing@ohauthcat.com · Security: security@ohauthcat.com · Privacy: privacy@ohauthcat.com

Other legal documents

  • Privacy Policy
  • Service Level Agreement
  • Data Processing Agreement
  • Sub-processors
  • Refund and Cancellation Policy
  • Accessibility Statement
  • SDK and CLI Licence

Enterprise SSO (SAML 2.0, OIDC) and SCIM for B2B SaaS, at a flat price.

Theme

© 2026 OhAuthCat

Product

  • All products
  • End-user auth
  • Roles and M2M
  • OAuth provider and MCP
  • Terraform provider
  • Pricing
  • Migrate
  • Docs
  • Changelog

Free tools

  • SAML debugger
  • Metadata validator
  • SCIM tester
  • IdP Radar

Trust

  • Security
  • Trust centre
  • Status
  • Report a vulnerability

Legal

  • Terms
  • Privacy
  • DPA
  • Sub-processors
  • SLA
  • Refunds and cancellation
  • Accessibility
  • All legal documents

Company

  • Contact support
  • Sign in
  • Start free