Data Retention and Lifecycle
Linquid uses lifecycle controls to protect data integrity while enforcing retention limits.Deletion model
Core patterns include:- soft delete for recoverability windows
- cascade cleanup for dependent records
- asynchronous cleanup jobs for large datasets
- a record can disappear from UI before all downstream aggregates fully converge
- derived analytics can continue to settle after deletion actions
Module lifecycle overview
| Module | Typical lifecycle pattern | Operator notes |
|---|---|---|
| Links and campaigns | active -> paused/archived -> deleted lifecycle | Historical metrics may remain visible for governed windows |
| Rules | active -> disabled/archived -> removed | Traffic behavior changes immediately after save; analytics settle after propagation |
| Conversion/customer records | ingested -> validated -> retained -> aged out by policy | Customer profiles can outlive individual event rows depending on retention policy |
| Affiliate commissions/payouts | pending -> approved -> paid/reconciled | Finance records typically follow stricter retention expectations |
| Integrations/webhooks | connected -> paused -> disconnected -> cleaned up | Delivery logs can persist beyond active integration state |
| Access/session artifacts | active -> expired -> revoked -> removed | Security logs may keep summary traces for audit workflows |
Retention controls
Retention depends on plan and data family. Examples of retention-sensitive datasets:- event and conversion streams
- analytics rollups
- logs and delivery histories
- invite/session artifacts
Retention-aware operations
When planning large changes, account for retention effects:- bulk deleting links can temporarily affect aggregated rollups before lifecycle jobs converge.
- plan downgrades can reduce historical query windows and export depth.
- paused integrations can still have retained historical logs in reporting views.
- partner payout records may remain for compliance even when partner status changes.
Lifecycle states users usually encounter
Typical record lifecycle states across modules:- active
- paused/disabled (for selected operational modules)
- archived
- soft-deleted
- permanently removed after retention/cleanup policy
Expected visibility behavior by state
| State | List pages | Analytics totals | Exports | |---|---|---| | Active | Visible | Counted | Included | | Paused/Disabled | Visible with state indicator | Usually counted historically; future activity depends on module | Included | | Archived | Hidden from default lists unless filtered | Historical totals remain | Included when in selected date range | | Soft-deleted | Usually hidden | Can still settle for a short period | May appear temporarily until cleanup completes | | Permanently removed | Not visible | Not included for removed period after convergence | Not included after retention window closes |What users should expect
After deletion actions:- records may disappear immediately from UI lists
- analytics and exports can have propagation delay
- derived totals can change as cleanup jobs complete
Lifecycle-safe change process
- Export baseline data before destructive actions.
- Apply action in smallest possible scope first.
- Verify analytics and exports after propagation delay.
- Document expected deltas for support and finance teams.
- Perform final confirmation once cleanup windows pass.
Lifecycle-sensitive actions to monitor
- workspace or campaign archival/unarchive changes
- link disable/expiry/click-limit transitions
- domain removal and related redirect behavior
- integration disconnect and webhook disable operations
- plan downgrade effects on feature access and retained data windows
Operator expectations during cleanup windows
- recent deletes can remain visible in some operational logs temporarily
- summary metrics can settle after asynchronous compaction jobs
- some exports may include records no longer shown in primary list pages until cleanup converges
Incident response scenarios
| Scenario | Immediate action | Follow-up action |
|---|---|---|
| Accidental deletion | Check recoverability window and restore options | Validate downstream metrics after restoration |
| Unexpected metric drop after archive | Confirm filters and state changes | Reconcile with export snapshot from before action |
| Missing historical rows after downgrade | Confirm current plan retention profile | Export needed ranges before future tier changes |
Governance checklist
- document internal retention policy by plan
- define recovery windows for accidental deletions
- validate lifecycle automation quarterly
- maintain deletion runbooks for customer support and compliance handling
/user-guides/manual/data/exports-and-operational-checks/user-guides/manual/workspace/security-and-compliance/user-guides/manual/monetization/plans-pricing-and-limits-reference