Skip to document
How it worksPolicyAPIDocsPricing
Sign in
Home/Trust & legal/Data Processing Agreement
DOCUMENT STATUS
Public reference copy

This page is adapted from Selkay’s published materials. Your workspace agreement and the documents presented during signup govern your use of the service. For a current copy, contact hello@selkay.com.

Data Processing Agreement (DPA)

Effective Date: October 2026
Last Updated: November 2026
Applicable Legal Frameworks: EU GDPR (Regulation (EU) 2016/679) Article 28 · UK GDPR & Data Protection Act 2018 · India Digital Personal Data Protection Act, 2023 (DPDP Act)


This Data Processing Agreement (“DPA”) supplements and forms a legally binding part of the Master Services Agreement or Terms of Service (the “Agreement”) entered into by and between Selkay Technologies Pvt. Ltd. (“Selkay”, the “Processor”) and the customer entity (“Customer”, the “Controller” or “Data Fiduciary”).

This DPA governs the processing of Personal Data submitted by Customer to Selkay in connection with Customer’s use of the Selkay Edge Content Moderation Platform, moderation API, and web dashboard (the “Services”).


1. Definitions & Applicable Frameworks

  1. “Applicable Data Protection Law” means all global data protection and privacy statutes applicable to the processing of Customer Personal Data under this Agreement, including:
    • EU GDPR: Regulation (EU) 2016/679 of the European Parliament and of the Council (General Data Protection Regulation).
    • UK GDPR: The Data Protection Act 2018 and the GDPR as incorporated into United Kingdom law by the European Union (Withdrawal) Act 2018.
    • India DPDP Act: The Digital Personal Data Protection Act, 2023, and accompanying rules issued by the Ministry of Electronics and Information Technology (MeitY).
  2. “Customer Personal Data” means any digital personal data or personal information processed by Selkay on behalf of Customer in the course of providing the Services.
  3. “Data Subject” or “Data Principal” means the identified or identifiable natural person to whom Customer Personal Data relates.
  4. “Data Fiduciary” and “Data Processor” have the respective meanings assigned under the India DPDP Act.
  5. “Controller”, “Processor”, “Personal Data”, and “Personal Data Breach” have the meanings defined under the EU GDPR and UK GDPR.
  6. “Subprocessor” means any third-party infrastructure vendor engaged by Selkay to assist in performing processing activities on behalf of Customer.

2. Roles, Scope & Nature of Processing

  1. Parties’ Regulatory Roles:
    • Under the EU GDPR and UK GDPR: Customer is the Data Controller; Selkay is the Data Processor.
    • Under the India DPDP Act 2023: Customer is the Data Fiduciary; Selkay is the Data Processor acting solely under a valid contract to process digital personal data.
  2. Purpose of Processing: Processing Customer text submissions solely to perform real-time automated safety policy evaluation, keyword and regex pattern matching, scoped redaction, heuristic scoring, edge semantic caching, and aggregated statistical rollups in accordance with Customer’s policy configurations.
  3. Categories of Data Subjects / Data Principals:
    • Customer’s authorized workspace administrators, developers, and team members.
    • End-users of Customer’s applications whose text submissions are routed through the moderation API.
  4. Categories of Personal Data:
    • Workspace Administrators: Full name, display name, verified email address, profile avatar, workspace permission role, and OAuth provider identifiers from one or more federated providers (Google OAuth 2.0, GitHub OAuth 2.0), linked by verified email address.
    • Application End-Users: Optional customer-generated pseudonymous user identifier (user_hash) and text or image content submitted for moderation. Submitted content may contain personal data.
  5. Special Category & Sensitive Data Prohibition: Customer covenants not to intentionally submit special categories of personal data (GDPR Article 9) or sensitive personal data under DPDP unless explicitly authorized under a mutually executed enterprise schedule.

3. Processor Obligations

Selkay covenants and agrees that it shall:

  1. Documented Instructions Only: Process Customer Personal Data strictly upon documented instructions from Customer, including with respect to geographical data routing and regional database group selection.
  2. Confidentiality Commitment: Ensure that all personnel authorized to access or process Customer Personal Data have committed to contractual confidentiality or are subject to statutory confidentiality duties.
  3. Commercial Data Protection Commitments:
    • Selkay certifies that it shall not sell, rent, or trade Customer Personal Data.
    • Selkay certifies that it shall not retain, use, or disclose Customer Personal Data for any purpose other than for the operational purposes specified in the Agreement, or outside the direct relationship between Selkay and Customer.
    • Selkay certifies that it shall not combine Customer Personal Data with personal information received from third parties for profiling or advertising.
  4. Technical & Organizational Security Measures (Article 32 / DPDP): Implement and maintain the technical and organizational measures described in Section 4 below.
  5. Subprocessors (Article 28.2 / DPDP): Engage subprocessors listed in the Subprocessors Registry, subject to applicable data processing terms. The registry describes the stated change notification procedure.
  6. Data Subject & Data Principal Rights Assistance:
    • Erasure Requests: Provide an account erasure workflow through POST /v1/auth/erase-account or the Settings dashboard. The workflow returns a receipt with a verification_signature generated using HMAC-SHA256 over the receipt ID, job ID, workspace ID, identifier hash, and timestamp. Records may remain where retention is required by law or technical safeguards.
    • Right to Portability & Access (GDPR Art. 20 / DPDP § 11): Provide automated self-service machine-readable JSON exports (GET /v1/auth/export-data) of workspace profile, identity, and membership records.
    • Correction & Rectification: Support live self-service updating of workspace identity and configurations via the dashboard.
  7. Personal Data Breach Notification: Notify Customer without undue delay and in any event within 48 hours after confirming a Personal Data Breach impacting Customer Personal Data, providing details regarding the nature of the breach, affected records, and remediation actions taken.
  8. Deletion upon Termination (GDPR Art. 28.3(g) / DPDP § 8(7)): Upon termination of the Services or cessation of the business purpose, delete or return all Customer Personal Data in accordance with Section 5, unless retention is mandated by applicable statutory law.

4. Technical and Organizational Security Measures (TOMs)

Selkay enforces the following architectural safeguards across all cloud environments:

  1. Data Minimization & Ephemeral In-Memory Evaluation:
    • Text submitted to POST /v1/moderate is evaluated in memory. To reuse results for repeated inputs, the service may cache derived content hashes and moderation decisions. Image cache keys use SHA-256 hashes of decoded image bytes; raw image bytes are not stored as cache values.
    • Raw content receiving a “Pass” verdict is not retained as an event log. Separately, Selkay may cache derived content hashes and moderation decisions for repeated inputs. Image cache keys use SHA-256 hashes of decoded image bytes; raw image bytes are not stored as cache values. Plan-based event retention and optional debug text storage are described in this DPA.
    • Ephemeral debug raw text logging is strictly disabled by default in production; on eligible paid tiers, it may only be activated via explicit administrator toggle exclusively for non-Pass (flagged) incidents.
  2. Encryption Architecture:
    • At Rest: Tenant database connection URLs and access tokens in the centralized control plane are encrypted with AES-256-GCM using dedicated rotating cryptographic key epochs.
    • In Transit: All API endpoints and web dashboards enforce TLS 1.3 / TLS 1.2 with perfect forward secrecy and preloaded HTTP Strict Transport Security (HSTS, max-age=31536000).
  3. Data Sovereignty & Isolated Regional Databases:
    • Each customer workspace is provisioned with a logically and cryptographically isolated LibSQL tenant database deployed in the customer’s selected geographical group: Dublin, EU (dub), Virginia, USA (iad), Mumbai, India (bom), or Tokyo, Japan (nrt).
    • Moderation rules, custom dictionaries, and daily telemetry rollups reside strictly within the chosen regional cluster.
  4. Automated Lifecycle Pruning:
    • Scheduled pruning removes daily rollup metrics and tenant security audit records after 7 days on Free, 30 days on Spark, 90 days on Growth, and 365 days on Scale. R2 moderation log batches are not retained on Free or Spark; Growth retains them for 90 days and Scale for 365 days.
  5. Access Control & Least Privilege:
    • Strict 3-tier Role-Based Access Control (owner, admin, member).
    • Platform operator APIs (/operator/*, /internal/*) are physically and logically segregated from customer tenant traffic and require distinct cryptographic operator tokens.
    • Session tokens are signed using HMAC-SHA256, stored with randomized TTLs in Workers KV, and delivered with HttpOnly; Secure; SameSite=Lax cookies.
  6. OAuth Identity Federation: When a user authenticates via multiple OAuth providers sharing the same verified email address, Selkay associates these tokens with a single internal identity record. No third-party OAuth provider password or secret is received or stored; only the verified email and display name token claims are retained. For corporate workspaces, domain binding ensures only users with matching corporate email domains can access the workspace.

5. Deletion, Purging & Erasure Verification

  1. Account Erasure Workflow: An authorized user may submit an account erasure request through the API or Settings dashboard. The workflow deletes or invalidates associated account records and sessions and returns a receipt with an HMAC-SHA256 verification_signature covering the receipt ID, job ID, workspace ID, identifier hash, and timestamp. It does not represent that every copy is immediately overwritten; some data may remain where retention is required by law or technical safeguards.
  2. Scheduled Pruning: Expired moderation incident logs in Cloudflare R2 are deleted automatically by the scheduled pruning engine upon reaching the active plan retention threshold.
  3. De-Provisioning on Contract Termination: Within thirty (30) days of subscription termination and account deactivation, all associated tenant database storage is permanently decommissioned.
  4. Inactive Free Tier De-Provisioning: Workspaces on the Free tier that record zero (0) API requests and zero (0) console sign-ins across thirty (30) consecutive calendar days are permanently de-provisioned and deleted by automated maintenance routines, purging associated tenant databases, API keys, and custom rules. Paid workspaces are excluded from automated inactivity de-provisioning.

6. International Data Transfers & Standard Contractual Clauses

  1. Cross-Border Transfers: Where applicable, the parties must use a valid transfer mechanism for transfers of Customer Personal Data to a jurisdiction that requires one. The European Commission’s 2021 Standard Contractual Clauses and the UK International Data Transfer Addendum may be relevant, depending on the transfer and the parties’ circumstances. Those instruments are not attached to this page; confirm the executed agreement and applicable transfer terms with Selkay.
  2. India Cross-Border Transfers: Transfers of Customer Personal Data originating from India are subject to applicable Indian law and any restrictions in force. Customers should confirm the transfer arrangements that apply to their workspace and processing.

7. Privacy and Grievance Contact

The Selkay materials list the following contact channels for privacy questions and grievances:

  1. Contact channels: The source DPA identifies the Security & Compliance Division as the contact office and lists hello@selkay.com and admin@selkay.com. It does not name an individual contact or provide a street address.
  2. Response timing: The source DPA states that inquiries and grievances sent to hello@selkay.com are acknowledged within 48 hours and addressed within thirty (30) days.

8. Governing Law

This DPA shall be governed by and construed in accordance with the governing law specified in the primary Master Services Agreement, except where Applicable Data Protection Law (such as EU GDPR or India DPDP Act) mandatorily requires local jurisdiction and governing law.

Terms & acceptable usePrivacyData processing agreementSubprocessors

Questions about privacy, terms, or suppliers? Email hello@selkay.com.

selkay.

Content moderation API for product teams. Evaluate text and images against customizable workspace rules with regional edge residency.

Zero training on customer content.

PRODUCTHow it worksPolicy engineAPI referenceDocumentationPricing
TRUST & LEGALTrust overviewTerms of servicePrivacy policyData processing (DPA)Subprocessors
CONNECTGitHubLinkedInXReddit
© 2026 Selkay Technologies Pvt. Ltd. All rights reserved.