Data Retention

This Data Retention Policy describes how MyTravelPeace approaches retention of information processed by the Service.

It reflects current architecture categories. Exact numeric retention periods for each category require legal and operational finalization and may show as Pending Legal Review below. Read with the Privacy Policy.

We aim to retain Personal Information only as long as needed to provide the Service, enforce agreements, resolve disputes, meet legal and accounting obligations, and maintain security—then delete or anonymize it when appropriate.

We do not promise indefinite retention, customer-downloadable database backups, or automated export packages unless separately launched as a product feature.

Account identifiers and profile-related fields are retained while the Account remains active and as needed after closure for security, fraud prevention, and legal compliance.

Trip and itinerary content, checklist items, and collaborator relationships are retained while associated with an active Account and trip records in the product.

Share-link access depends on sharing settings you configure. Removing collaborators updates access going forward.

Local subscription projections (plan, status, period fields, and Paddle billing identifiers) are retained to operate entitlements and reconcile billing events.

Paddle retains payment records according to its Merchant of Record and legal obligations. MyTravelPeace does not store full payment card numbers in application databases.

Operational events used for Admin monitoring—including security, activity, and system categories—are retained for reliability, abuse prevention, and operational review for a period appropriate to those purposes.

Security events may include hashed IP values and limited user-agent context where implemented.

Public Radar aggregate counters (for example daily or monthly request/success/failure/quota/blocked metrics) are retained as operational metrics. They are not designed as prompt transcripts.

AI usage metering records used to enforce plan allowances are retained as needed for billing entitlement and abuse prevention.

If operational backups exist at the infrastructure layer, residual copies may persist for a limited period after deletion from primary systems. Backup handling is an operator process, not a customer download feature.

Self-serve Account deletion workflows may be added later. Until then, deletion requests should be submitted through the designated support channel when published.

We do not invent deletion SLAs in this Policy. Response handling will follow counsel-approved processes.

We may update this Policy when retention practices change. Numeric schedules, once approved, will replace Pending Legal Review markers where applicable.

Questions about this document may be directed to MyTravelPeace through the support channel designated by the operator.

Pending Legal Review — this section requires counsel confirmation for jurisdiction-specific wording.

Related documents: Privacy Policy, Terms of Service, and other pages linked from the Service footer.