Table of Contents

Class ErasureContributorContext

Namespace
Excalibur.Compliance
Assembly
Excalibur.Compliance.Abstractions.dll

Context information passed to IErasureContributor during erasure execution.

public sealed record ErasureContributorContext : IEquatable<ErasureContributorContext>
Inheritance
ErasureContributorContext
Implements
Inherited Members

Properties

DataSubjectIdHash

Gets the SHA-256 hash of the data subject identifier.

public required string DataSubjectIdHash { get; init; }

Property Value

string

DeclaredLocations

Gets the declared table-and-field pairs registered against a store kind this contributor covers.

public IReadOnlyList<DataLocationKey> DeclaredLocations { get; init; }

Property Value

IReadOnlyList<DataLocationKey>

Remarks

The erasure service filters these to the contributor's CoveredStoreKinds before the call, so a contributor names what it erased without having to guess which consumer-chosen table belongs to it. A pair registered with no store kind never appears here and therefore stays outstanding — silence fails closed.

IdType

Gets the type of identifier used to identify the data subject.

public required DataSubjectIdType IdType { get; init; }

Property Value

DataSubjectIdType

RequestId

Gets the erasure request tracking ID.

public required Guid RequestId { get; init; }

Property Value

Guid

Scope

Gets the scope of the erasure operation.

public required ErasureScope Scope { get; init; }

Property Value

ErasureScope

TenantId

Gets the tenant identity whose data is being erased — the OWNER, and what key handles derive from.

public string? TenantId { get; init; }

Property Value

string

Remarks

Not a partition, and never to be compared against one. See TenantPartition.

TenantPartition

Gets the tenant partition whose legal obligations apply to this erasure.

public required KeyedTenantPartition TenantPartition { get; init; }

Property Value

KeyedTenantPartition

Remarks

The fact a retention declaration is joined against. It is carried beside TenantId rather than derived from it because the two are different: the owner is the exact term the data was encrypted under, the partition is what a declaration names, and a single-tenant deployment's owner is not its partition. A contributor deciding whether an obligation applies MUST read this one.