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 Data Processing Agreement

Version: 1.0, effective 1 November 2026

Contents

  1. 1. Definitions
  2. 2. Roles and scope
  3. 3. Instructions
  4. 4. Confidentiality and personnel
  5. 5. Security
  6. 6. Sub-processors
  7. 7. Data Subject requests
  8. 8. Security Incidents
  9. 9. Data protection impact assessments and consultation
  10. 10. Deletion and return
  11. 11. Audits and information
  12. 12. International transfers
  13. 13. India: DPDP Act and SPDI Rules
  14. 14. United States: CCPA and similar laws
  15. 15. Liability
  16. 16. Term, precedence and general
  17. Annex I: Description of the processing
  18. Annex II: Technical and organisational measures
  19. Annex III: Sub-processors

This Data Processing Agreement ("DPA") forms part of the OhAuthCat Terms of Service (terms-of-service.md), or any other written agreement for the Service, 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, which provides OhAuthCat ("OhAuthCat"), and the customer that has accepted those terms ("Customer") (together, the "Agreement"). It applies automatically when the Customer accepts the Agreement. No separate signature is needed; a Customer that wants a countersigned copy may request one at legal@ohauthcat.com.

1. Definitions #

1.1 Capitalised terms not defined here have the meaning given in the Agreement.

1.2 In this DPA:

  • "Applicable Data Protection Law" means all laws on the processing of personal data that apply to a party's processing of Customer Personal Data under the Agreement, including, as applicable: the Digital Personal Data Protection Act, 2023 of India and the Digital Personal Data Protection Rules, 2025 ("DPDP Act"); the Information Technology Act, 2000 and the Information Technology (Reasonable Security Practices and Procedures and Sensitive Personal Data or Information) Rules, 2011 ("SPDI Rules"); Regulation (EU) 2016/679 ("EU GDPR"); the EU GDPR as it forms part of UK law and the Data Protection Act 2018 ("UK GDPR"); the Swiss Federal Act on Data Protection of 25 September 2020 ("FADP"); and the California Consumer Privacy Act of 2018 as amended by the California Privacy Rights Act of 2020, and its regulations ("CCPA"), and similar US state privacy laws.
  • "Controller", "Processor", "Data Subject", "Personal Data", "Processing", "Supervisory Authority" and "Personal Data Breach" have the meanings given in the EU GDPR. Where the DPDP Act applies, "Controller" includes "Data Fiduciary", "Processor" includes "Data Processor", "Data Subject" includes "Data Principal" and "Personal Data" includes "digital personal data". Where the CCPA applies, "Controller" includes "business", "Processor" includes "service provider" and "Personal Data" includes "personal information".
  • "Customer Personal Data" means Personal Data that OhAuthCat processes on behalf of the Customer in providing the Service, as described in Annex I.
  • "Customer Organization" means a business customer of the Customer whose identity provider or SCIM client is connected to the Service.
  • "User" means an individual whose identity data is received through a Customer Organization's identity provider or SCIM client, including an employee or contractor of a Customer Organization.
  • "Environment" means a sandbox or production environment of a project in the Customer's account.
  • "Instructions" means the Customer's documented instructions under section 3.
  • "Security Incident" means a Personal Data Breach affecting Customer Personal Data in OhAuthCat's or a Sub-processor's systems.
  • "Sub-processor" means a third party that OhAuthCat engages to process Customer Personal Data.
  • "SCCs" means the standard contractual clauses approved by European Commission Implementing Decision (EU) 2021/914 of 4 June 2021.
  • "UK Addendum" means the International Data Transfer Addendum to the EU Commission Standard Contractual Clauses issued by the UK Information Commissioner under section 119A of the Data Protection Act 2018, version B1.0, in force 21 March 2022, as amended.

2. Roles and scope #

2.1 Roles. For Customer Personal Data, the Customer is the Controller and OhAuthCat is the Processor. Where the Customer acts as a Processor for a Customer Organization or another third party, the Customer warrants that the Instructions it gives, including the appointment of OhAuthCat as a Sub-processor, have been authorised by the relevant Controller, and OhAuthCat is a Sub-processor to the Customer.

2.2 OhAuthCat as Controller. OhAuthCat is a Controller for the data described in its Privacy Policy (privacy-policy.md), including the Customer's account, team member, billing and support data, and security logs it keeps to protect the Service. This DPA does not apply to that data.

2.3 Aggregate data. OhAuthCat may derive anonymous, aggregated statistics (for example, counts of sign-ins by country, network and identity-provider type, and service latency) that do not identify the Customer, any Customer Organization or any User, and may use them to operate, secure, plan capacity for and improve the Service. Such statistics are not Customer Personal Data. OhAuthCat does not store client IP addresses with these statistics.

2.4 Customer obligations. The Customer:

  • (a) is responsible for the lawfulness of the Processing it instructs, including having a lawful basis and giving any notice and obtaining any consent that Applicable Data Protection Law requires from Users and Customer Organizations;
  • (b) decides which attributes are mapped and which data are sent to the Service, and must not map, send or require Special Categories of Personal Data (Art. 9 EU GDPR), Personal Data relating to criminal convictions (Art. 10), sensitive personal data or information under the SPDI Rules (including passwords, financial, health, biometric or sexual-orientation data), government identification numbers, or the Personal Data of children, except as permitted in Annex I;
  • (c) is responsible for the security of its own systems, its API keys, its webhook endpoints and log-stream destinations, and the accounts of its team members;
  • (d) will not instruct OhAuthCat to process Customer Personal Data in breach of Applicable Data Protection Law.

3. Instructions #

3.1 OhAuthCat will process Customer Personal Data only on the Customer's documented Instructions, unless required to do otherwise by law to which OhAuthCat is subject. In that case OhAuthCat will tell the Customer of the legal requirement before processing, unless that law prohibits it on important grounds of public interest.

3.2 The Customer instructs OhAuthCat to process Customer Personal Data:

  • (a) to provide, secure and support the Service in accordance with the Agreement and the documentation, including authenticating Users, issuing profiles, receiving and storing SCIM resources, delivering events and webhooks, streaming logs to destinations the Customer configures, generating debug bundles the Customer requests, and running imports and exports the Customer starts;
  • (b) as initiated by the Customer, its team members, Customer Organizations' IT administrators and Users in their use of the Service, including through the dashboard, the management API, the setup portal, the CLI, the SDKs and the MCP server;
  • (c) to comply with other reasonable written instructions of the Customer that are consistent with the Agreement.

3.3 The Agreement, this DPA and the Customer's configuration of the Service are the Customer's complete Instructions at the time of signature. Additional instructions outside their scope require prior written agreement, including on any fees.

3.4 OhAuthCat will tell the Customer promptly if, in its opinion, an Instruction infringes Applicable Data Protection Law. OhAuthCat is not obliged to perform a legal review of the Customer's Instructions.

3.5 Customer-directed destinations. Where the Customer configures OhAuthCat to send Customer Personal Data to a destination it chooses (its webhook endpoints, log-stream destinations, redirect URIs or the WorkOS-compatible API), that transfer is made on the Customer's Instruction, and the recipient is not a Sub-processor of OhAuthCat.

4. Confidentiality and personnel #

4.1 OhAuthCat will ensure that every person it authorises to process Customer Personal Data is bound by a written obligation of confidentiality or an appropriate statutory duty, which continues after their engagement ends.

4.2 OhAuthCat restricts access to Customer Personal Data to personnel who need it to provide, secure or support the Service. Staff have no standing access to production databases; break-glass access is time-boxed, audited and alerted. Support access to a Customer's configuration is read-only, needs a recorded reason and is written to the Customer's audit log.

4.3 All personnel complete security and privacy training when they join and every year after that, and OhAuthCat keeps records of the training.

5. Security #

5.1 OhAuthCat will implement and maintain the technical and organisational measures in Annex II, which are designed to protect Customer Personal Data against a Security Incident and to ensure a level of security appropriate to the risk, as required by Article 32 EU GDPR, the SPDI Rules and section 8(5) of the DPDP Act.

5.2 OhAuthCat may update the measures in Annex II from time to time, provided the updates do not materially reduce the overall level of protection of Customer Personal Data.

5.3 Annex II identifies measures that are planned and not yet in place. Planned measures are not commitments until OhAuthCat updates Annex II to mark them as in place.

5.4 The Customer is responsible for using the Service's security features appropriately, including multi-factor authentication for its team, scoped and expiring API keys, IP allow-lists where needed, verified domains, and keeping SCIM tokens and webhook secrets secret.

6. Sub-processors #

6.1 General authorisation. The Customer gives OhAuthCat general written authorisation to engage Sub-processors. The Sub-processors in place on the date of this DPA are listed in OhAuthCat's sub-processor list at https://ohauthcat.com/legal/sub-processors (Annex III), which the Customer approves.

6.2 Sub-processor terms. OhAuthCat will engage each Sub-processor under a written contract that imposes data protection obligations no less protective than those in this DPA, to the extent applicable to the nature of the services the Sub-processor provides. OhAuthCat remains liable to the Customer for each Sub-processor's performance of its obligations as if they were OhAuthCat's own.

6.3 Notice of changes. OhAuthCat will notify the Customer of any intended addition or replacement of a Sub-processor at least 30 days before the new Sub-processor processes Customer Personal Data, by updating the sub-processor list and sending notice to subscribers of that list and to the owners of the Customer's account by email.

6.4 Objection. The Customer may object to a new Sub-processor on reasonable grounds relating to data protection by writing to subprocessors@ohauthcat.com or privacy@ohauthcat.com within the notice period. The parties will then discuss the objection in good faith. OhAuthCat may, at its option, offer a configuration or alternative that avoids the new Sub-processor for the Customer's data. If no resolution is reached within 30 days of the objection, the Customer may terminate the affected part of the Service by written notice, and OhAuthCat will refund any prepaid fees for the terminated part covering the period after termination. This is the Customer's sole remedy for an objection.

6.5 Emergency replacement. Where OhAuthCat must replace a Sub-processor urgently to protect the security or continuity of the Service (for example, because a provider fails or is compromised), it may do so on shorter notice, and will notify the Customer as soon as reasonably possible. The objection right in section 6.4 then applies from the date of that notice.

7. Data Subject requests #

7.1 Taking into account the nature of the Processing, OhAuthCat will assist the Customer by appropriate technical and organisational measures, insofar as possible, to fulfil the Customer's obligation to respond to requests from Data Subjects to exercise their rights under Applicable Data Protection Law.

7.2 Self-service. The Service lets the Customer meet most requests itself:

  • (a) Access and portability: the management API and dashboard return organizations, connections, directory users and groups, and events; POST /exports produces a downloadable export of an Environment in a documented format, and POST /audit_logs/exports produces a CSV export of the audit log;
  • (b) Correction: User attributes come from the Customer Organization's identity provider or SCIM client; correcting them at the source updates the Service on the next sign-in or SCIM request;
  • (c) Erasure: a SCIM DELETE from the identity provider removes the directory user; deleting a connection (DELETE /connections/{conn}), directory (DELETE /directories/{dir}) or organization (DELETE /organizations/{org}) deletes the related profiles at once; and a profile is deleted automatically after 13 months without a sign-in.
  • (d) Single profile: the management API has no endpoint that deletes one SSO profile on its own. OhAuthCat deletes a named profile on the Customer's written request within 30 days.

7.3 Requests sent to OhAuthCat. If OhAuthCat receives a request from a Data Subject that relates to Customer Personal Data and it can identify the Customer, it will forward the request to the Customer without undue delay and will not respond to it except to tell the Data Subject to contact the Customer, unless the Customer instructs otherwise or the law requires.

7.4 Where the Customer cannot fulfil a request through self-service, OhAuthCat will provide reasonable assistance on request. OhAuthCat may charge its reasonable costs for assistance that goes beyond what the Service provides, after telling the Customer the expected cost.

8. Security Incidents #

8.1 Notice. OhAuthCat will notify the Customer without undue delay, and in any case within 48 hours, after OhAuthCat confirms a Security Incident affecting the Customer's Customer Personal Data.

8.2 Content. The notice will describe, to the extent then known: the nature of the Security Incident, including the categories and approximate number of Data Subjects and records concerned; the likely consequences; the measures taken or proposed to address it and mitigate its effects; and a contact point. Where the information is not available at once, OhAuthCat will provide it in phases as it becomes available.

8.3 Delivery. Notice will be sent by email to the owners of the Customer's account, and may also be posted on the status page for incidents that affect many customers. The Dashboard does not yet offer a separate security-contact field; the Customer may ask OhAuthCat in writing to copy notices to an additional address.

8.4 Cooperation. OhAuthCat will take reasonable steps to contain, investigate and remediate the Security Incident, preserve evidence, rotate affected keys, and cooperate with the Customer so the Customer can meet its own obligations to notify Supervisory Authorities, the Data Protection Board of India and Data Subjects.

8.5 OhAuthCat's own obligations. OhAuthCat reports cyber security incidents to the Indian Computer Emergency Response Team (CERT-In) where required by its directions under section 70B of the Information Technology Act, 2000 (currently within 6 hours of noticing a reportable incident). Such a report does not require the Customer's consent and does not delay the notice in section 8.1. OhAuthCat will not otherwise notify Supervisory Authorities or Data Subjects of a Security Incident on the Customer's behalf unless the Customer instructs it or the law requires.

8.6 No admission. Notice of or a response to a Security Incident is not an acknowledgement of fault or liability.

8.7 Unsuccessful attempts that do not compromise the security of Customer Personal Data, such as pings, port scans, denial-of-service attempts and failed sign-ins, are not Security Incidents.

9. Data protection impact assessments and consultation #

9.1 Taking into account the nature of the Processing and the information available to OhAuthCat, OhAuthCat will provide reasonable assistance to the Customer with data protection impact assessments and prior consultations with Supervisory Authorities that the Customer must carry out under Applicable Data Protection Law, to the extent they relate to the Service. OhAuthCat will first meet this obligation by providing this DPA, its security documentation and its answers to a standard security questionnaire.

9.2 Where the Customer is notified as a Significant Data Fiduciary under the DPDP Act, OhAuthCat will provide reasonable information to support the Customer's periodic data protection impact assessment and audit.

10. Deletion and return #

10.1 During the term. The Service deletes Customer Personal Data on the schedules in Annex I, section 8, and when the Customer deletes the relevant objects.

10.2 Return. Before the end of the Agreement, the Customer may export Customer Personal Data using the export features in section 7.2(a). On written request made within 30 days after termination, OhAuthCat will make an export available if the Customer cannot use the self-service export.

10.3 Deletion. If the Customer closes its account itself, the Service stops at once, an account owner may reopen the account within 7 days, and OhAuthCat then deletes all Customer Personal Data, including backups, within 60 days after that 7-day window ends; the Customer should export Customer Personal Data before closing. Otherwise, after the Agreement ends, OhAuthCat will delete all Customer Personal Data, including backups (section 10.4), within 90 days after termination, after an export period of 30 days (section 10.2), using the Environment deletion process, which removes rows and stored objects and repeats until no data remains. Retained after deletion are only records that hold no Customer Personal Data: an Environment tombstone, anonymous project and account rows, and the deletion record. Audit log entries leave through their normal retention purge (Annex I, section 8).

10.4 Backups. Customer Personal Data in backups is deleted as the backups expire, within 60 days. Until then, OhAuthCat keeps backups secure under this DPA, does not process the data in them except to restore the Service after an incident, and re-applies deletions after any restore.

10.5 Legal retention. OhAuthCat may retain Customer Personal Data where the law requires, only for as long as required, and will keep it confidential and secure and process it for no other purpose.

10.6 On request, OhAuthCat will confirm deletion in writing.

11. Audits and information #

11.1 Information. OhAuthCat will make available to the Customer the information reasonably necessary to demonstrate compliance with this DPA and Article 28 EU GDPR.

11.2 Documents first. OhAuthCat will meet audit requests first by providing, under confidentiality: this DPA and Annex II; its security documentation and policies (information security, incident response, business continuity and disaster recovery, access control, data retention and deletion, vendor management, and a threat model summary); answers to a reasonable industry-standard security questionnaire, once a year; and, once OhAuthCat's periodic security testing has started (planned, Annex II, section 12), a summary of the findings under a non-disclosure agreement.

11.3 Certifications. OhAuthCat does not hold a SOC 2 report, ISO/IEC 27001 certificate or other third-party certification on the date of this DPA. If OhAuthCat obtains one, it will make the report or certificate available on request under confidentiality, and the Customer agrees that it satisfies the corresponding audit requests for the period covered.

11.4 On-site audits. Where the information in sections 11.2 and 11.3 is not sufficient to show compliance, or where a Supervisory Authority requires it, the Customer (or an independent auditor it appoints that is not a competitor of OhAuthCat and is bound by confidentiality) may audit OhAuthCat's compliance with this DPA, provided that:

  • (a) the Customer gives at least 30 days' written notice with a proposed scope, unless a shorter period is needed after a Security Incident or by a Supervisory Authority;
  • (b) the audit takes place during normal business hours in India, at most once in any 12-month period (except after a Security Incident or on a Supervisory Authority's demand), and lasts no more than 2 business days. The limits on notice, frequency and duration in (a) and (b) do not apply to an audit following a Personal Data Breach;
  • (c) the audit does not give access to other customers' data, to systems in a way that would compromise their security, or to the premises of Sub-processors (for which OhAuthCat will instead provide the Sub-processor's own audit reports where available);
  • (d) the Customer bears its own costs and pays OhAuthCat's reasonable costs for the time its personnel spend on the audit at OhAuthCat's then-current professional services rates, quoted in writing before the audit starts, except where the audit reveals a material breach of this DPA by OhAuthCat;
  • (e) the Customer gives OhAuthCat a copy of the audit report, which is OhAuthCat's confidential information.

11.5 Nothing in this section limits the rights of a Supervisory Authority, or the Customer's rights under clause 8.9 of the SCCs, which are met as set out in this section.

12. International transfers #

12.1 Hosting location. OhAuthCat hosts the Service in Amazon Web Services' Mumbai region (ap-south-1), India. OhAuthCat will not move the primary hosting of Customer Personal Data to another country without the notice in section 6.3. Sub-processors may process Customer Personal Data in the locations listed in Annex III.

12.2 EU transfers. To the extent the Customer's transfer of Customer Personal Data to OhAuthCat is a transfer of personal data from the EEA to a country without an adequacy decision, the SCCs are incorporated into this DPA by reference and apply as follows:

  • (a) Module Two (controller to processor) applies where the Customer is a Controller, and Module Three (processor to processor) applies where the Customer is a Processor;
  • (b) the Customer is the "data exporter" and OhAuthCat is the "data importer";
  • (c) Clause 7 (docking clause) applies;
  • (d) Clause 9(a): Option 2 (general written authorisation) applies, with the time period set out in section 6.3 of this DPA (30 days);
  • (e) Clause 11(a): the optional language on an independent dispute resolution body does not apply;
  • (f) Clause 13: the competent supervisory authority is that of the EU member state where the data exporter is established or, if it is not established in the EU, where its Article 27 representative is established, or otherwise the Data Protection Commission of Ireland;
  • (g) Clause 17 (Option 1): the SCCs are governed by the law of Ireland;
  • (h) Clause 18(b): disputes are resolved before the courts of Ireland;
  • (i) Annex I of the SCCs is completed by Annex I of this DPA; Annex II of the SCCs by Annex II of this DPA; and Annex III of the SCCs by Annex III of this DPA;
  • (j) the notification of a Personal Data Breach under clause 8.6(c) of the SCCs follows section 8 of this DPA; the audits in clause 8.9 follow section 11; and the deletion certification in clause 8.5 and clause 16(d) is given only on request.

12.3 UK transfers. For transfers from the United Kingdom, the SCCs as completed in section 12.2 apply as amended by the UK Addendum, which is incorporated by reference. Table 1 of the UK Addendum is completed with the parties' details in Annex I; Table 2 with the modules and options in section 12.2; Table 3 with Annexes I to III of this DPA; and in Table 4 neither party may end the UK Addendum under its section 19.

12.4 Swiss transfers. For transfers subject to the FADP, the SCCs in section 12.2 apply with these changes: references to the EU GDPR are read as references to the FADP; the competent supervisory authority is the Swiss Federal Data Protection and Information Commissioner; references to "Member State" include Switzerland, so data subjects in Switzerland may bring claims there; and the SCCs also protect the data of legal entities until the revised FADP's exclusion of them takes effect, where applicable.

12.5 Conflict. If the SCCs or the UK Addendum conflict with this DPA, the SCCs or the UK Addendum prevail for the transfers they cover.

12.6 Supplementary measures. OhAuthCat applies the measures in Annex II, including encryption in transit and at rest, envelope encryption of secrets with keys held in a key management service, and access controls. OhAuthCat will: review any order from a public authority for access to Customer Personal Data for its legality; challenge orders it considers unlawful where reasonable; disclose only the minimum required; and, unless prohibited, notify the Customer of the order. OhAuthCat has not received such an order to date.

12.7 Onward transfers. OhAuthCat will make onward transfers of Customer Personal Data to Sub-processors outside India only under a mechanism that Applicable Data Protection Law recognises, as listed in Annex III.

12.8 Alternative mechanisms. If a transfer mechanism is invalidated or replaced, the parties will cooperate to adopt a valid alternative, and OhAuthCat may adopt an alternative that the law recognises by notice to the Customer.

13. India: DPDP Act and SPDI Rules #

13.1 Where the DPDP Act applies, the Customer is the Data Fiduciary and OhAuthCat is the Data Processor engaged under a valid contract, as required by section 8(2) of the DPDP Act. OhAuthCat will:

  • (a) process Customer Personal Data only to provide the Service, on the Customer's Instructions (section 3);
  • (b) take reasonable security safeguards to prevent a personal data breach, as set out in Annex II (section 8(5) of the DPDP Act and the DPDP Rules 2025);
  • (c) inform the Customer of a personal data breach as set out in section 8, so that the Customer can inform the Data Protection Board of India and each affected Data Principal;
  • (d) erase Customer Personal Data as instructed and as set out in section 10, and when the Customer tells OhAuthCat that a Data Principal has withdrawn consent or the specified purpose is no longer being served;
  • (e) assist the Customer with requests from Data Principals under sections 11 to 14 of the DPDP Act, including nomination, as set out in section 7;
  • (f) keep the logs the DPDP Rules 2025 require of a Data Processor, for the period they require.

13.2 The Customer remains responsible for giving notice to Data Principals, obtaining their consent or relying on a legitimate use, and for its own obligations as Data Fiduciary, including those of a Significant Data Fiduciary where applicable.

13.3 Where the SPDI Rules apply, OhAuthCat maintains reasonable security practices and procedures as described in Annex II. The Customer must not send sensitive personal data or information through the Service (section 2.4(b)).

14. United States: CCPA and similar laws #

14.1 Where the CCPA applies, OhAuthCat is a "service provider" and the Customer is a "business". OhAuthCat will process Customer Personal Data only for the limited and specified business purposes of providing the Service set out in the Agreement and Annex I.

14.2 OhAuthCat will not:

  • (a) sell or share Customer Personal Data, as "sell" and "share" are defined in the CCPA;
  • (b) retain, use or disclose Customer Personal Data for any purpose other than the business purposes specified in the Agreement, including for any commercial purpose other than providing the Service, or outside the direct business relationship between OhAuthCat and the Customer;
  • (c) combine Customer Personal Data with personal information it receives from or on behalf of another person or collects from its own interactions with consumers, except as the CCPA permits a service provider to do.

14.3 OhAuthCat will comply with its applicable obligations under the CCPA and provide the same level of privacy protection the CCPA requires of businesses. It will notify the Customer if it determines it can no longer meet its obligations. The Customer may take reasonable and appropriate steps, on notice, to stop and remediate unauthorised use of Customer Personal Data, and to ensure OhAuthCat uses Customer Personal Data consistently with the Customer's obligations, including through the audits in section 11.

14.4 OhAuthCat certifies that it understands and will comply with the restrictions in this section. These terms also serve as the "processor" contract required by other US state privacy laws, such as those of Virginia, Colorado, Connecticut, Utah, Texas and Oregon, to the extent they apply.

15. Liability #

15.1 Each party's liability arising out of or relating to this DPA, including the SCCs and the UK Addendum to the extent the law permits, is subject to the exclusions and limitations of liability in the Agreement.

15.2 Despite section 15.1, OhAuthCat's total aggregate liability for breaches of this DPA or of Applicable Data Protection Law in relation to Customer Personal Data is limited to two times (2×) the fees paid or payable by the Customer under the Agreement in the 6 months before the event giving rise to the claim (the "Data Protection Super-Cap"). The Data Protection Super-Cap replaces, and is not added to, the general cap in the Agreement for those claims. It does not limit liability that cannot be limited by law, or liability for gross negligence or wilful misconduct, which the Agreement treats separately.

15.3 Nothing in this DPA limits either party's liability to Data Subjects under clause 12 of the SCCs, to the extent the SCCs prohibit it.

15.4 For Customers on the Free plan, who pay no fees, the Data Protection Super-Cap is US$20 (or its equivalent in Indian rupees), consistent with clause 21.5 of the Agreement.

16. Term, precedence and general #

16.1 Term. This DPA lasts as long as OhAuthCat processes Customer Personal Data, and survives the end of the Agreement until all Customer Personal Data is deleted under section 10.

16.2 Order of precedence. If there is a conflict, these documents prevail in this order: (a) the SCCs and the UK Addendum, for the transfers they cover; (b) this DPA; (c) an Enterprise order form, only where it expressly amends this DPA; (d) the Terms of Service; (e) the documentation.

16.3 Changes. OhAuthCat may update this DPA to reflect changes in Applicable Data Protection Law, the Service or its Sub-processors, giving at least 30 days' notice of material changes. Changes will not reduce the protection given to Customer Personal Data, except where required by law. Where the Customer has signed an Enterprise order form that fixes the DPA version, changes need the Customer's written agreement, except changes required by law.

16.4 Governing law. This DPA is governed by the law that governs the Agreement, except that the SCCs are governed by the law chosen in section 12.2(g) and the UK Addendum by the laws of England and Wales.

16.5 Severability. If any provision of this DPA is invalid, the rest remains in force, and the invalid provision is replaced with a valid one that comes closest to its purpose.

16.6 Notices. Notices to OhAuthCat under this DPA go to privacy@ohauthcat.com, with a copy to legal@ohauthcat.com. Security reports go to security@ohauthcat.com.


Annex I: Description of the processing #

A. List of parties #

Data exporter

  • Name: the Customer, as named in the account or order form.
  • Address and contact person: as given in the Customer's account or order form.
  • Activities relevant to the transfer: use of the OhAuthCat Service to provide single sign-on and directory sync to its Customer Organizations.
  • Role: Controller (Module Two) or Processor (Module Three).
  • Signature and date: by accepting the Agreement, on the date of acceptance.

Data importer

  • Name: Generic Technologies Private Limited (OhAuthCat).
  • Address: 201/1, Arcot Road, Virugambakkam, Chennai, Tamil Nadu 600092, India.
  • Contact person: Koushik Raj, Chief Executive Officer, privacy@ohauthcat.com.
  • Activities relevant to the transfer: provision of the Service.
  • Role: Processor (Module Two) or Sub-processor (Module Three).
  • Signature and date: on the date the Customer accepts the Agreement.

B. Description of the transfer #

1. Categories of Data Subjects

  • (a) Users: employees, contractors and other members of Customer Organizations who sign in through, or are provisioned to, the Customer's application.
  • (b) IT administrators and contacts of Customer Organizations who set up connections and directories in the setup portal or are named as IT contacts.
  • (c) Members of the Customer's team, only to the extent their names or identifiers appear in Customer Personal Data such as audit records (their account data is otherwise OhAuthCat's Controller data).

2. Categories of Personal Data

  • (a) User identity attributes received from the Customer Organization's identity provider over SAML 2.0 or OpenID Connect: identity-provider subject identifier (NameID or sub), email address, first and last name, and the profile identifier OhAuthCat derives from the connection and subject.
  • (b) Directory data received over SCIM 2.0: user name, email, active status, identity-provider identifiers, group names and memberships, and the other SCIM attributes the identity provider sends, including enterprise extension attributes such as department or job title.
  • (c) Roles and group-to-role mappings the Customer configures.
  • (d) Custom attributes: up to 50 attributes per Environment that the Customer chooses to map from identity-provider claims. The Customer decides what these contain, subject to section 2.4(b).
  • (e) Organization metadata the Customer sets (up to 50 keys, 4 KB per organization), which may contain Personal Data if the Customer puts it there.
  • (f) Sign-in events: time, outcome, error code, connection and organization, the profile signed in, approximate location derived from the IP address (country, region, city), network, and the sign-in timeline; client IP address and user agent in security logs.
  • (g) SCIM request records: method, path, status, error code and latency, with the request body redacted (no tokens, email addresses masked, string values removed).
  • (h) Events and webhook payloads describing changes to users, groups, connections and directories, which carry the attributes in (a) to (d).
  • (i) Debug bundles, only when the Customer or the Customer Organization's IT administrator creates one: sign-in checks, timeline and identity-provider metadata summary; and the redacted SAML response and decoded assertion only for verified test sign-ins or sign-ins inside an explicit, audited capture window (at most 1 hour or the next 20 captured sign-ins). Redaction keeps signatures and digests, replaces certificates with fingerprints, masks NameID and email addresses and attribute values, and never includes tokens or secrets.
  • (j) IT administrator data: name, email address, role (owner or viewer), notification preferences, setup-link and invitation records, portal session records and audit entries.
  • (k) Import data, when the Customer imports from another provider: the identity records and legacy identifiers needed to map existing users. Credentials supplied for an import are used once and not stored, unless the Customer opts into continuous shadow sync, in which case they are stored encrypted with an expiry.
  • (l) Test sign-in data: in test rows only, a masked email address (for example j***@acme.com).

3. Sensitive data

  • The Service is not designed to process special categories of Personal Data, data relating to criminal convictions, sensitive personal data or information under the SPDI Rules, or the data of children. The Customer must not map or send such data (section 2.4(b)).
  • Restrictions and safeguards applied to all data: encryption in transit and at rest, access controls and audit logging (Annex II), and the redaction rules in item 2(g) and 2(i).

4. Frequency of the transfer

  • Continuous, for the term of the Agreement: on every sign-in, SCIM request, API call and event.

5. Nature of the processing

  • Collection, receipt, validation, storage, organisation, structuring, retrieval, consultation, use, transmission (to the Customer's application, webhook endpoints and log-stream destinations), restriction, erasure and destruction, as needed to provide the Service.

6. Purposes of the processing

  • To authenticate Users of Customer Organizations into the Customer's application through single sign-on, and to issue profiles to the Customer;
  • to receive and store directory data from Customer Organizations through SCIM and make it available to the Customer through the API, events and webhooks;
  • to let Customer Organizations' IT administrators configure connections and directories;
  • to provide the Customer with logs, audit trails, debug tools, imports and exports;
  • to secure the Service, prevent abuse and support the Customer.

7. Duration of the processing

  • For the term of the Agreement and the deletion period in section 10, subject to the retention periods in item 8.

8. Retention

DataFreeProBusinessEnterprise
Data: User profilesFree: Deleted after 13 months without a sign-in, and at once when the connection or organization is deletedPro: SameBusiness: SameEnterprise: Same
Data: Directory users and groupsFree: Until deleted by the SCIM client, or the directory, organization or Environment is deletedPro: SameBusiness: SameEnterprise: Same
Data: Events (Events API)Free: 7 daysPro: 30 daysBusiness: 90 daysEnterprise: Custom (as agreed)
Data: Webhook deliveriesFree: Purged with events, on the same schedulePro: SameBusiness: SameEnterprise: Same
Data: Audit logFree: 7 daysPro: 90 daysBusiness: 1 yearEnterprise: Custom
Data: API request log and sign-in timelinesFree: 3 daysPro: 30 daysBusiness: 90 daysEnterprise: Custom
Data: SCIM request logFree: 3 daysPro: 30 daysBusiness: 90 daysEnterprise: Custom (90 days until set)
Data: Debug bundlesFree: 7 daysPro: 7 daysBusiness: 30 daysEnterprise: Configurable, up to 90 days
Data: Raw IP addresses (security logs only)Free: 30 daysPro: 30 daysBusiness: 30 daysEnterprise: 30 days
Data: Portal sessionsFree: Until expiry (at most 1 hour)Pro: SameBusiness: SameEnterprise: Same
Data: Portal links and invitationsFree: 30 days after expiry or revocationPro: SameBusiness: SameEnterprise: Same
Data: Hourly dashboard rollups (per Environment, no client addresses)Free: 62 daysPro: SameBusiness: SameEnterprise: Same
Data: Unclaimed sandbox EnvironmentsFree: All data deleted after 7 days, with a 24-hour settle windowPro: SameBusiness: SameEnterprise: Same
Data: Exports and audit-log exportsFree: Download links expire after 24 hoursPro: SameBusiness: SameEnterprise: Same
Data: BackupsFree: 60 daysPro: SameBusiness: SameEnterprise: Same

Retention ladders may be extended by a paid add-on, which the order form records.

9. Sub-processor transfers

  • As listed in Annex III, for the purposes and with the data stated there.

C. Competent supervisory authority #

As set out in section 12.2(f).


Annex II: Technical and organisational measures #

Measures marked (planned) are not yet in place and are not commitments until this Annex is updated. All others are built and in operation on the date of this DPA.

1. Hosting and infrastructure

  • The Service runs in Amazon Web Services' Mumbai region (ap-south-1), across three availability zones, on infrastructure OhAuthCat manages.
  • The database is the managed PostgreSQL database Amazon RDS, in a Multi-AZ deployment (a synchronous standby in a second availability zone) in OhAuthCat's own AWS account, and the self-managed Valkey cache holds short-lived state; no database vendor other than AWS (Sub-processor 2.1) holds Customer Personal Data.
  • Cloudflare sits in front of the API with origin-pull mutual TLS, so the origin accepts only traffic from Cloudflare on the primary path.
  • All production infrastructure is managed as code, and changes are reviewed.

2. Encryption

  • In transit: TLS 1.2 or higher for all public endpoints; TLS 1.3 on custom hostnames; mutual TLS between cells.
  • At rest: secrets (OIDC client secrets, webhook signing secrets, private keys, TOTP secrets) are envelope-encrypted with data keys wrapped by AWS Key Management Service; keys are held only in memory.
  • Verifiable secrets (API keys, SCIM tokens, portal tokens) are stored only as keyed hashes (HMAC-SHA256 with a server-side secret) with a display prefix, and are shown once at creation.
  • Service-provider signing keys are RSA-2048 with SHA-256, rotate with published overlap and key identifiers.
  • Disk and backup encryption at rest: EBS volumes and S3 objects are encrypted with AWS KMS keys. Debug bundles are stored encrypted in object storage.

3. Access control (customers)

  • Multi-factor authentication for dashboard members on every plan; passkeys (WebAuthn) preferred, TOTP as fallback, no SMS; owners must enrol MFA and keep at least one backup passkey.
  • Dashboard cookies are Secure, HttpOnly and SameSite=Lax, with CSRF tokens and a strict content security policy.
  • API keys are scoped by resource and action, can be restricted by IP allow-list and expiry, and every API route declares the scope it needs; a CI test proves no route is reachable without one.
  • Setup-portal sessions are sealed tokens in a __Host- cookie (Secure, HttpOnly, SameSite=Strict), limited to 1 hour, ending after 30 minutes idle; setup links are single-use where configured.

4. Access control (staff)

  • The staff console is reachable only through Cloudflare Zero Trust Access, never the public internet, with Cloudflare Access one-time PIN sent to Company email addresses and passkeys, and role-based scopes.
  • No standing production database access; break-glass access is time-boxed, audited and alerted.
  • Support access to a Customer's data is read-only, needs a recorded reason and is written to the Customer's audit log.
  • Staff actions such as account suspension and switching off an Environment require a reason and are audited.

5. Tenant isolation

  • Every tenant-owned record carries its Environment identifier, and the data-access layer requires it as a typed parameter; tests try cross-tenant access on every endpoint.
  • Profile identifiers are a keyed hash of the connection and identity-provider subject, so identities cannot collide across organizations.
  • A User is signed in only if the email domain belongs to a domain the organization has verified by DNS; otherwise nothing is written.

6. Application security for sign-in and provisioning

  • Authorization codes are single-use, expire after 60 seconds and require the secret API key; PKCE is checked in addition, never instead.
  • Exact redirect-URI matching; no wildcards in production.
  • Strict SAML handling: size limit (256 KB), DOCTYPE and entities refused, signature validation that uses only the signed element, full condition checks and replay protection.
  • OIDC ID tokens validated for issuer, audience, expiry, nonce and an algorithm allow-list.
  • SCIM: per-directory rate and concurrency limits and request size caps.
  • All fetches of customer-supplied URLs go through one hardened fetcher: https only, public addresses only, re-checked redirects, timeouts and size caps.
  • Outbound webhooks are signed with a timestamp and replay window.
  • When a dependency is unavailable, sign-ins may fail, but no check is skipped.

7. Logging, audit and data minimisation

  • Audit logs record every configuration change, including staff actions; they are append-only and the database refuses updates and deletes, except the scheduled retention purge.
  • Logs never contain tokens, secrets, SAML payloads or full email addresses; SCIM request records are stored redacted.
  • Raw SAML is not retained except in debug bundles inside the limits in Annex I, item 2(i).
  • Client IP addresses are kept only in security logs, for 30 days; regional statistics never store an address.
  • Retention purges run as scheduled, lease-guarded jobs (Annex I, item 8).

8. Availability and resilience

  • Three availability zones; the sign-in path continues from an in-memory configuration snapshot if the database loses quorum, with audit records buffered and written exactly once on recovery; at the buffer's limit, sign-ins fail closed rather than drop records.
  • A per-connection and per-Environment kill switch.
  • Backups: scheduled distributed backups and continuous change shipping to versioned, write-protected object storage, held in ap-south-1 across availability zones, with a copy in a second AWS region in India, ap-south-2 (Hyderabad), and kept for 60 days. Both copies are encrypted with AWS KMS keys held in their own region and write-protected with versioning and Object Lock. Point-in-time recovery for 7 days, plus weekly snapshots (planned target).
  • Restore drills monthly once backups are in place (planned).
  • Standby sign-in path that does not depend on Cloudflare (planned).

9. Change management and secure development

  • Code changes are reviewed and tested in CI, including invariant tests for each security rule, fuzzing of the XML and SCIM filter parsers, and dependency vulnerability checks.
  • Rolling releases with automatic rollback on failure and per-role canaries on sign-in roles.
  • Secrets are never committed to repositories; deployment secrets are encrypted.

10. Incident response

  • Severity-based incident process with on-call rotation, status-page communication and post-mortems (public for SEV1 incidents) (status page planned).
  • Evidence preservation, key rotation runbooks and Customer notification as set out in section 8 of this DPA.
  • Reporting to CERT-In within the period its directions require (currently 6 hours for reportable incidents).

11. Vendor management

  • Sub-processors are selected for their security posture and bound by written terms (section 6). The list is public (Annex III).

12. Testing and assurance

  • OhAuthCat performs periodic security testing of the Service and shares a summary of the findings under a non-disclosure agreement on request (planned; the first test has not yet run).
  • Internal security review before public beta (planned).
  • Bug bounty (planned).
  • SOC 2 audit: not held; to start when a customer contract requires it (planned).

13. Personnel

  • Confidentiality obligations for all personnel (section 4).
  • Security and privacy training (see section 4.3).

Annex III: Sub-processors #

The Sub-processors authorised under section 6 are those listed in OhAuthCat's sub-processor list (sub-processors.md), published at https://ohauthcat.com/legal/sub-processors, as updated under section 6.3. The list states each Sub-processor's entity, purpose, location, data categories and transfer mechanism.

Other legal documents

  • Terms of Service
  • Privacy Policy
  • Service Level 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