CITI ProgramCITI Program
All ideas

Self-service learner account deletion (anonymization) with institutional approval and org offboarding

Summary Learners should be able to request deletion of their LMS account and training history themselves, without going through Support. Institutions should be able to delete their affiliates' data, for example at contract end. When a deletion goes through, the learner's data is anonymized: no database records are deleted, and the process can't be undone. Principles Institutions control their data. For affiliated learners, the institution decides (it's the controller and CITI is the processor). For independent learners, CITI is the controller, so the learner's request goes ahead without anyone else's approval. Removal works one affiliation at a time. Full anonymization only happens when a learner has no remaining affiliation and no independent purchases. Anonymize, don't delete. Completion, enrollment and transcript rows stay in place, attached to an anonymous ID, so reporting and record integrity still work. Keep a record without PII. A tombstone record lets us show that training was completed and later erased at the learner's request with admin approval, without keeping anything that identifies the learner. 1. Learner-initiated request Add a "Request account deletion" option to the learner's account settings. Verify identity by having the learner re-enter their password and confirm through a link emailed to them. Once MFA ships in the LMS, MFA replaces the emailed link. Before the learner submits, the page tells them that: deletion is permanent and cannot be undone it removes their CITI Program records only. Records their institution has already copied into its own systems (for example through Automated Downloads (ADS)) have to be deleted by contacting the institution directly they should download any certificates they want to keep first The learner can see the status of their request (pending, approved, denied, completed) and gets notified of the outcome. 2. Approval routing Independent learners: no approval needed. Anonymization runs after a short cooling-off period, during which the learner can cancel. Affiliated learners: the request is emailed to all institutional admins at each affiliated institution and shows up in the admin interface. At each institution, any one admin can approve or deny for that institution. v1 rule: every affiliated institution must approve. A denial from any institution denies the whole request. Automatic reminders go out during a response window (for example, 30 days). Mixed accounts (an affiliated learner who also bought courses independently): CITI is the controller for the independent records, so those don't need institutional approval. 3. Org-initiated deletion and offboarding An institution's top-level admin can request deletion for selected affiliates or for all of them, without the learners' approval. If the institution's Data Processing Agreement (DPA) — the contract that defines how CITI handles personal data on the institution's behalf — requires it, this can also be triggered at contract end. For each learner: Affiliated only with this org: full anonymization. Has other affiliations: remove this org's affiliation, scrub the org-specific data (employee ID, department, supervisor, custom registration answers), and stop ADS feeds to this org. Completions that other affiliations rely on stay with the learner. Guardrails: a typed confirmation, a cooling-off window, and an optional notice period for learners. During that period, learners can download their certificates, and those with no other affiliation can convert to an independent account. 4. Anonymization Replace the name, email, username and other PII fields with placeholders, for example "Anonymized Learner [anon ID]". Clear free-text fields and generated certificate files. Make sure ADS doesn't push anonymized values over institutions' existing copies of the records. Define how certificate verification links behave after anonymization. 5. Audit record (tombstone) Fields: anonymous ID, institution(s), courses and completion dates, request date, approving or initiating admin, action, and completion date. No learner name, email, IP address or free text. Use reason codes only. Goal: if subpoenaed, we can show that an anonymized learner at Institution X completed course Y and that the record was erased at their request with admin approval. 6. Salesforce Once the LMS finishes anonymizing a learner, it notifies Salesforce (through the API or a Platform Event), matching on an LMS Learner ID external ID field. Contact: scrub the name, email, phone and address, and set email opt-out. Cases: keep the case record and its category for reporting. Redact the subject and description, and delete or redact email messages, comments, chat transcripts and attachments. Clean up Field History, the Recycle Bin and Data Cloud, if they're in use. Alternative worth exploring: Salesforce Privacy Center, a paid add-on with built-in "right to be forgotten" policies. It could replace a custom Apex/Flow build. NetSuite stays out of scope. Invoice and payment records are kept to meet tax and accounting requirements. Open questions Should a non-response after the response window count as approval? That would need to be in customer agreements. Or should it count as denial, or escalate? For v2, should multi-affiliation requests be decided per affiliation instead of all-or-nothing, so the learner gets a partial outcome when one institution denies? Do our standard customer agreements and DPAs name the institution as controller and CITI as processor? Legal needs to confirm this, and whether CCPA applies to BRANY directly or only through service-provider contracts. How long should the cooling-off and learner-notice periods be? Should certificate verification links keep working after anonymization (showing a generic "record exists") or stop working? Should we keep a keyed identifier that can be matched for legal holds, or keep only the fully anonymous tombstone (recommended)? Counsel should decide. Build the Salesforce side ourselves or buy Privacy Center? Should this ship before or after MFA? (The emailed confirmation link is the interim option.)