Retention is influenced by product configuration, legal requirements for specific industries, litigation holds, and the lifecycle of integrated subprocessors. VaseSign provides controls your organisation can align to policy — VaseSign does not substitute for your records-management programme.
Customer-configurable retention
Workspace administrators define how long completed envelopes and artefacts remain online subject to plan limits. Exports for archival storage remain customer-managed once downloaded — custody after export follows your internal controls.
Legal and regulatory holds
When instructed by lawful authority or internal governance, organisations may suspend deletion for affected records. Mechanics vary by deployment — enterprise agreements describe how hold notices are applied and released with audit trails where supported.
Operational backups
Backup copies exist for resilience and may persist briefly beyond interactive deletion until overwritten according to rotation schedules. Restoration from backup is exceptional and logged; customers requiring stricter erasure windows negotiate bespoke schedules where feasible.
Deletion pathways
End-user deletion triggers propagate according to application logic; residual artefacts in caches or derived indexes clear within documented eventual-consistency windows. Third-party subprocessors honour deletion instructions through contractual clauses reviewed during onboarding — reference the Subprocessors register.
Coordinate residency discussions alongside retention using Data residency.