Identity, membership and tenant configuration
Retention model
Tied to the lifecycle of the account, source or product purpose.
Deletion trigger
Account/workspace deletion or validated privacy request
← Back to Blocchi
Security & privacy
Data retention & deletion
Blocchi keeps data only for as long as needed to operate the contracted features, protect the service and meet applicable legal, contractual or audit obligations. Deletion accounts for primary copies, derived data, providers and backups.
Synced CRM and business records
Retention model
Tied to the lifecycle of the account, source or product purpose.
Deletion trigger
Tenant deletion, approved source-data purge or privacy/legal deletion event
Canonical, mastered and derived analytics data
Retention model
Tied to the lifecycle of the account, source or product purpose.
Deletion trigger
Deletion of the governing tenant/source data or explicit approved derived-data purge
Uploaded files and imported datasets
Retention model
Tied to the lifecycle of the account, source or product purpose.
Deletion trigger
File/dataset deletion, tenant deletion or temporary-processing completion
Integration credentials and OAuth tokens
Retention model
Tied to the lifecycle of the account, source or product purpose.
Deletion trigger
Integration removal, credential rotation, tenant deletion or security incident
Application error, trace and operational telemetry
Retention model
Provider-managed, with configuration and limitations reviewed by Blocchi.
Deletion trigger
Provider retention expiry or validated deletion request where provider tooling supports scoped erasure
Product analytics and consent telemetry
Retention model
Provider-managed, with configuration and limitations reviewed by Blocchi.
Deletion trigger
Privacy request, consent-driven removal where applicable, or provider retention expiry
Transactional email recipient and delivery metadata
Retention model
Provider-managed, with configuration and limitations reviewed by Blocchi.
Deletion trigger
Provider retention expiry or validated privacy/tenant deletion request
Billing and subscription metadata
Retention model
Driven by applicable legal, financial or contractual obligations.
Deletion trigger
Account deletion after applicable legal/financial retention requirements expire
AI prompt context and generated output
Retention model
Provider-managed, with configuration and limitations reviewed by Blocchi.
Deletion trigger
Governing product-data deletion plus provider retention expiry
Backups and recovery copies
Retention model
Provider-managed, with configuration and limitations reviewed by Blocchi.
Deletion trigger
Provider backup expiry
Minimization
We collect and send providers only the data needed for the approved purpose.
Derived data
Deletion does not stop at the source table: canonical, analytical and derived copies are included in scope.
Backups
Live data is removed first. Immutable backups may age out under the verified provider window and are not restored to active use without re-applying the deletion obligation.
Deletion requests
Validated requests follow a governed procedure that identifies primary and derived data, integrations, providers and backup disposition. Data subject to a legal, financial, security or audit obligation may be preserved for the necessary period with the exception documented.
Register updated 2026-09-08.