Deletion and Retention

Data Deletion and Retention

This document explains how Stacks, operated by Jose Araneta, handles user deletion requests and why some information may remain for limited periods after deletion is requested. Deletion should be described honestly: content may disappear from active product surfaces before it is fully removed from all backups or recovery systems.

Plain-language summary
  • Stacks includes backend deletion logic, and deletion requests begin an asynchronous cleanup workflow.
  • Some information may remain temporarily in backups, logs, or legal/security hold systems.
  • This policy does not promise instantaneous deletion where that would be inaccurate.
Effective date: March 1, 2026 Last updated: March 1, 2026
All policies

1. Purpose And Scope

This document explains how users can request deletion of their Stacks account, how Stacks expects to process content and account deletion, what information may remain temporarily after deletion begins, and why some information may be retained for legal, security, abuse-prevention, or technical reasons.

2. Core Principles

Stacks aims to retain information only for as long as reasonably necessary, honor valid deletion requests in a commercially reasonable and operationally consistent way, minimize retained information where practical, avoid promising instantaneous deletion where that would be inaccurate, and preserve information when reasonably necessary for legal compliance, security, fraud prevention, abuse investigations, or technical integrity.

3. How To Request Account Deletion

  1. Send a deletion request to support@mystacksapp.com from the email associated with the account, where possible.
  2. Include information sufficient to identify the account, such as username and account email.
  3. Complete reasonable identity verification if requested.

Stacks also supports in-app account deletion from the Profile screen. Support remains available for deletion follow-up questions, identity verification where needed, and cases where a user cannot access the app.

4. What Stacks Expects To Delete Or De-Identify

When a valid deletion request is accepted, Stacks begins an asynchronous deletion workflow that may result in deletion or de-identification of account profile information, user-created stacks and cards, uploaded photos, videos, audio, text, and related content metadata, certain collaboration or sharing records associated with the deleted account, push notification tokens and related device associations no longer needed, and other user-specific operational records that are no longer required.

5. What May Remain Temporarily After Deletion Begins

Even after deletion starts, some information may remain for a limited period in backup or disaster-recovery systems, logs or operational records, security or anti-abuse records, records needed to document and complete the deletion request itself, and systems where immediate removal is not technically feasible.

6. Retention Categories

Retention practices may vary across active account records, profile information, stack and card content, narration/audio content, collaboration and sharing metadata, notification tokens, logs and diagnostics, backup copies, and legal-compliance or dispute-related records.

7. Technical And Operational Limits

Deletion across distributed systems takes time, technical limitations may delay complete deletion in some environments, backups and disaster-recovery systems are not necessarily updated in real time, and full deletion timing may vary by system and data type. Stacks therefore does not publish a guaranteed completion deadline in this version of the policy.

9. Deletion Of Shared Or Collaborative Content

Because Stacks includes sharing and collaboration features, deletion outcomes may vary where content appears in collaborative contexts, where other users have independent rights or copies, or where shared records involve more than one participant.

10. If Deletion Fails Or Appears Incomplete

If a user believes deletion was not properly completed, they should follow up through support@mystacksapp.com with identifying information sufficient to locate the original request.

11. Contact