Skip to content

Retention Policy Alignment

Date: 2026-06-25 Status: Accepted for the first paid pilot. Roadmap item: EP8-T3.

Decision

MamNajem will not add a new automated expired-record cleanup scheduler before the first paid pilot.

The pilot retention posture is:

Area Pilot decision
Retention table Use the privacy-policy periods as the source of truth: lease/property duration + 3 years, payments 10 years, messages 7 years after lease end, audit logs 5 years, notifications 1 year, usage/analytics 2 years.
Automated cleanup before release No new automated purge is required before the paid pilot. Product/legal text must not claim automatic cleanup until the scheduler exists.
Account deletion Keep the current API behavior: deletion is blocked with 409 Conflict while the user owns or participates in active or pending leases.
Legal/tax evidence Retain records beyond base periods when needed for lease, legal, tax, dispute, audit, payment, settlement, or support evidence.
Bank transfer snapshots Tenant-visible bank transfer snapshots stored on payment records follow payment/legal evidence retention, not owner bank account profile deletion timing.

Why

The mismatch was policy, not missing critical release code. DATA_RETENTION.md used old periods and said scheduler enforcement would arrive later; the privacy policy used different periods and implied configured cleanup procedures. Current backend behavior is request-time deletion with active/pending lease protection, not automated expiry cleanup.

Adding a background purge before the pilot would create higher risk than value unless counsel requires it. The safer launch posture is to state actual behavior, keep legal/tax evidence exceptions explicit, and avoid promising automation that does not exist.

Automated Cleanup Choice

No categories require automated cleanup before the first paid pilot.

Future scheduler candidates remain:

  • Lease messages after 7 years from lease end.
  • Notifications after 1 year.
  • Calendar events after 1 year after event date.
  • Usage/analytics data after 2 years.
  • Eligible lease/property records after lease duration + 3 years, only after legal/tax/dispute exceptions are cleared.

Account Deletion Behavior

Backend account deletion currently:

  • Blocks deletion while the user owns or participates in active or pending leases.
  • Hard-deletes the user record when deletion is allowed.
  • Cancels pending invitations, unlinks tenant associations, deletes subscription and Stripe Connect records, removes user-uploaded assets, and deletes reporter problem reports.
  • For owners, deletes owner graph records only after active/pending lease checks pass.
  • For tenants, logs the deletion and anonymizes/removes audit references where the data model supports it.

This behavior is now documented in DATA_RETENTION.md and reflected in privacy-policy-v1.md.

Evidence

Backend:

  • DATA_RETENTION.md now matches the privacy-policy retention periods.
  • privacy-policy-v1.md no longer says expired data is deleted through configured retention procedures.
  • RetentionPolicyConsistencyTest guards the period table, no-automation wording, active/pending lease deletion block, and legal evidence exceptions.

Product docs:

  • This page records the Product Owner decision for EP8-T3.
  • The pre-release charter marks the privacy/retention release gate as passed for policy/implementation alignment.

This decision does not replace Polish counsel review. The separate legal review gate must still confirm that the periods and exception wording are acceptable before a broad paid public launch.