Interface ErasureRequest._FinalStage
- All Known Implementing Classes:
ErasureRequest.Builder
- Enclosing class:
ErasureRequest
-
Method Summary
Modifier and TypeMethodDescriptionadditionalProperties(Map<String, Object> additionalProperties) additionalProperty(String key, Object value) auditDisposition(ErasureRequestAuditDisposition auditDisposition) auditDisposition(Optional<ErasureRequestAuditDisposition> auditDisposition) How to handle the subject's audit and version-history trail.build()contextScope(List<String> contextScope) contextScope(Optional<List<String>> contextScope) The contexts in which to erase the subject.externalId(String externalId) externalId(Optional<String> externalId) Your own externalId for the subject, as an alternative tosubjectId.The platform id of the subject to erase (the userId, clientId, or orgId returned when the subject was created).
-
Method Details
-
build
ErasureRequest build() -
additionalProperty
-
additionalProperties
-
subjectId
The platform id of the subject to erase (the userId, clientId, or orgId returned when the subject was created). Provide exactly one of
subjectIdorexternalId. -
subjectId
-
externalId
Your own externalId for the subject, as an alternative to
subjectId. Provide exactly one ofsubjectIdorexternalId. -
externalId
-
contextScope
The contexts in which to erase the subject. As the data controller, you declare the blast radius: each listed context is erased independently and reported separately on the certificate. Omit or leave empty to erase every context the subject has data in; those contexts are then enumerated and erased one at a time, never as a single account-wide sweep. Any context you do not list is left untouched, and managing that residual data is your responsibility.
-
contextScope
-
auditDisposition
ErasureRequest._FinalStage auditDisposition(Optional<ErasureRequestAuditDisposition> auditDisposition) How to handle the subject's audit and version-history trail. This governs only the audit data — the subject's records and documents are always erased regardless.
retain-redacted(the default) keeps the compliance audit trail with sensitive data redacted;purgeadditionally hard-removes the audit history itself (subject to your legal obligations). -
auditDisposition
-