Capgent logoCapgent logoCapgent
DocsPlaygroundBenchmarksGuestbook
Sign inTry demo
Capgent logoCapgent logoCapgent

Explore

PlaygroundBenchmarksGuestbookProtected demo

Resources

DocsProjectsSDK (npm)GitHubWebsite

Documentation

Getting startedAPI referenceIntegration guideChangelog

Legal

Privacy policyTerms of serviceDSR/DSAR
All systems normal

© 2026 Capgent

Data subject requests (DSR / DSAR)

Effective date: March 28, 2026

This page explains how to exercise privacy rights for personal data processed in connection with Capgent (web app, dashboard, and APIs described in the project repository). Capgent is operated by an independent developer; there is no dedicated enterprise support desk.

1. What is a DSR / DSAR?

A data subject request (DSR) is a request from an individual about their personal data. A data subject access request (DSAR) is a request to access (receive a copy of) that data. Depending on where you live (e.g. EEA, UK, California), you may also have rights to correction, deletion, restriction, objection, or portability.

2. What you can request

Examples of requests we can process when we can verify your identity:

  • Access: A summary of categories of personal data we hold about you in connection with Capgent, and a copy where appropriate.
  • Correction: Fixing inaccurate account or profile data you cannot fix in the UI.
  • Deletion: Deleting your account and associated dashboard data where technically feasible and not required to be retained by law.
  • Objection / restriction: Where applicable law allows, limiting certain processing.

Some API-side data (e.g. ephemeral challenge state, aggregated logs) may not be tied to you in a identifiable way; we will explain that in our response where relevant.

3. How to submit a request

Preferred channel: Open a GitHub issue in the Capgent repository using the Issues tab. Title it clearly (e.g. "Privacy / DSR request") and include:

  • Your name and the email address associated with your Capgent account
  • The type of request (access, deletion, correction, etc.)
  • Any relevant details (e.g. approximate signup date) to help us locate your data

Alternative: If you cannot use GitHub, contact via the professional channels linked from the site footer (e.g. LinkedIn) with the same information; responses may be slower.

4. Verification

To protect your privacy, we will take reasonable steps to verify that the request comes from you (or your authorized agent). This may include confirming control of your account email or additional checks for sensitive requests.

5. Timelines

We aim to respond within 30 days. Complex requests may require an extension where permitted by law; we will notify you if that applies.

6. Appeals and complaints

If you disagree with our response, reply in the same thread (GitHub issue or email chain) explaining why. You may also lodge a complaint with your local data protection authority (e.g. a supervisory authority in the EEA/UK).

7. Authorized agents

If an agent submits a request on your behalf, we may require proof of authorization and may still need to verify your identity directly.

8. Related policies

  • Privacy policy — what we collect and why
  • Terms of service — rules for using the service