How RistoBoost account deletion works.

1. Scope

This page concerns deletion of RistoBoost accounts and must remain consistent with the real technical flow implemented in the product and the related legal documentation.

2. Account deletion

RistoBoost provides or will provide a way to request or start account deletion. The actual path must be available in the app or through the official flow indicated by the provider.

3. Effects of deletion

Deleting the account results in loss of access to the profile and related features, subject to the time strictly necessary to complete the technical procedure and any required security, support, or compliance checks.

4. Data associated with the account

• After a deletion request, data associated with the account must be handled according to the real product logic, in compliance with the Privacy Policy and the internal retention schedule.
• Some data may be retained for a limited period if necessary for legal, fiscal, security, fraud-prevention, dispute-management, or rights-protection reasons.

5. Deletion and future subscriptions

• Deleting the RistoBoost account does not automatically imply cancellation of any future subscriptions managed through external app stores or payment providers.
• If a paid subscription is active in the future, the user will also need to verify and manage the subscription status through the relevant store or payment flow.

6. Verification and checks

The provider may require reasonable checks before completing deletion, especially in the presence of anomalies, suspicious activity, payment disputes, or doubts about account ownership.

7. Timing

Deletion requests should be handled within a reasonable period, taking into account technical complexity, necessary checks, and legal obligations.

8. Contacts

• Support email: support@cdrapps.com
• Privacy / legal email: privacy@cdrapps.com

9. Coordination with other documents

This page must be read together with the Privacy Policy, Terms of Service, and any future Subscription Terms.

10. Before final publication

• verify that the real in-app deletion path is active;
• verify that the public flow is consistent with the backend and any store requirements;
• coordinate this page with retention and privacy;
• verify that the relationship between account deletion and any future subscription is described correctly.