Skip to main content

Documentation Index

Fetch the complete documentation index at: https://www.opentrain.ai/docs/llms.txt

Use this file to discover all available pages before exploring further.

If you are submitting a right-to-erasure or other personal-data request, for example under the EU GDPR, the UK GDPR, or the California Consumer Privacy Act, this page explains how to send the request, what we do with it, and how long each step takes. We are not your lawyer. This page describes our operational process. It does not interpret which laws apply to you, what your rights are under those laws, or whether OpenTrain is a controller, processor, or business as those terms are defined in any specific statute.

​
How to submit a request

Email support@opentrain.ai with the subject Erasure request from the email address tied to your OpenTrain account. Include:
  • The email address on the account.
  • The action you are requesting: deletion of the account, removal of specific content, or another erasure-related action.
  • Any specific URLs, pages, or records you want addressed.

​
Identity verification

Before we act, we verify the request actually comes from the account holder. This usually means replying from the email tied to the account, and in some cases additional confirmation. We complete this within one business day of acknowledging your request.

​
Our response cadence

  • Acknowledgement: same business day, in our reply to your email.
  • Status response with the specific actions we will take: within 5 business days of acknowledgement.
  • Fulfillment target: within 30 calendar days of the verified request. This is the upper bound we plan to. The full data scrub on a deletion-style erasure typically completes within 24 hours of verification.
If we cannot meet a step on time, we will tell you and explain why.

​
What erasure executes

For a verified request, erasure runs the same data-handling we apply to a deletion request, plus any specific records you call out, for example removal of your account-level identifiers from a particular conversation. Specifically, we:
  • Make your public profile page private immediately so anonymous visitors and search engines can no longer see it.
  • Set your account to closed and your profile to noindex.
  • Scrub your name, email address, profile slug, profile photo, bio, location, resumes, integration IDs, and connected payment IDs from your user record.
  • Delete your work history, education entries, skill/language records, AI-interview entries, and messaging-preference records.
For the operational click-flow on the in-app deletion control, see Delete your account.

​
What erasure does not remove

For operational and legal reasons, a small set of data persists after an erasure-style request:
  • Records we are required to retain by law, for example transaction and tax records tied to payments we have processed.
  • Anonymized aggregate analytics that no longer identify you as an individual.
  • Third-party caches, including Google search results. See Removing your profile from Google search results.
  • Conversations and content you sent to other users on the platform, where another user has a legitimate copy of those messages. As part of an erasure request, we will assess what is possible on a case-by-case basis.

​
If you want to file a complaint

If you believe we have not handled your request properly, you can contact your local data protection authority. Examples of authorities you can contact directly: We do not represent any of those bodies and we cannot file complaints on your behalf.