What should happen before tenant data is deleted?

A buyer should understand export first. SIRJ tenant data export packages can include access records, invitations, notifications, integration records, raw payloads, normalized events, attribution matches, dashboard snapshots, Ask Data cache, report snapshots, and report export records before deletion is requested.

Data exit review is safer when export, retention, and deletion are separate actions instead of one vague offboarding promise.

Which data does raw-event retention affect?

Raw-event retention focuses on attribution matches, normalized events, and raw integration payloads. The default retention window is 24 months, and the retention plan computes a cutoff before deleting expired rows from those evidence tables.

Retention review can stay specific: raw source evidence ages out separately from broad account deletion, report exports, billing state, or legal policy language.

Who can run deletion or retention actions?

Tenant data export requires data export permission. Tenant data retention and deletion require data administration permission, active account and client scope, rate-limit checks, and deletion confirmation that matches the active client.

Normal dashboard access should not imply the ability to export or delete tenant data. Retention and deletion belong behind stronger permissions and scoped runtime checks.

How are completed and failed data jobs reviewed?

Compliance jobs preserve pending, completed, or failed states. Completed jobs keep table counts and output references when available, failed jobs keep an error message, and export, retention, and deletion outcomes can create audit log evidence for review.

A failed data job should not disappear. Reviewers need to see whether export, retention, or deletion completed, failed, or produced output.

Records included in tenant data export review

Client memberships, Client invitations, Client context records, Notifications, Integration connections, Encrypted integration credentials, Integration sync state, Integration sync runs, Raw integration payloads, Normalized events, Attribution matches, Dashboard snapshots, AI trace records, Ask Data cache, Report snapshots, Report exports.

Records included in deletion review

Notifications, Report exports, Report snapshots, Ask Data cache, AI trace records, Dashboard snapshots, Attribution matches, Normalized events, Raw integration payloads, Integration sync runs, Integration sync state, Encrypted integration credentials, Integration connections, Client context records, Client invitations, Client memberships.

Export before destructive action

Start by deciding whether a tenant data export package is needed before retention or deletion changes the evidence available for review.

Export rows name the access, integration, reporting, source, and notification records that can be packaged for scoped review.

Confirm active account and client scope

Compliance jobs are created inside the active account and client scope, and deletion requires client confirmation before records are removed.

Roles, client workspaces, and audit pages explain the access boundary around export, retention, and deletion controls.

Apply the right control path

Export packages, retention runs, and deletion jobs follow different permissions, rate limits, record tables, and review outcomes.

The page separates export rows, retention rows, deletion groups, and control checks so reviewers can inspect each path separately.

Preserve status and counts

Completed and failed compliance results keep job status, table counts, output references when present, error messages when failed, and completion timestamps.

Audit and compliance evidence lets reviewers distinguish a completed export, failed package, completed retention run, or failed deletion job.

Route custom requirements to Enterprise

Custom retention terms, private connector requirements, custom destinations, or broader governance review should be scoped before production reporting depends on them.

Enterprise, procurement, exports, and custom connector pages keep custom governance separate from default public behavior.

What is the default raw-event retention window?

The default raw-event retention boundary in the product code is 24 months for attribution matches, normalized events, and raw integration payloads. Custom retention requirements should be scoped through Enterprise review.

Can SIRJ export tenant data before deletion?

Yes. The tenant data export path can package scoped client workspace records before a retention or deletion decision is made.

Can every user delete tenant data?

No. Retention and deletion require data administration permission, scoped account and client context, rate-limit checks, and deletion confirmation for the active client.

Does deletion remove report and integration records?

Deletion jobs follow a defined table order that includes notification history, report exports, report snapshots, Ask Data cache, dashboard snapshots, attribution and source records, integration state, credentials, connections, invitations, and memberships.