What these periods mean
These are the application retention rules prepared for deployment. Due records are deleted on the next successful daily cleanup; outages and a backlog can delay physical removal. Share access stops at its expiry even before cleanup. Production job execution and supplier log/backup periods are still unverified school adoption gates. Contact tumble.tools@gmail.com for the status or a deletion request.
| Data | Application retention |
|---|---|
| Account, profile, preferences, saved lessons/resources, folders and private catalogue entries | Until you remove the item or erase the account. Saved teaching material is separate from generation history. |
| Teaching sessions, observations, adaptations and flashcard generation history | 30 days from creation; earlier on Account history clear, related source deletion or account erasure. Saved follow-up lesson content remains until removed. |
| AI request/routing/tool records and operational usage | 90 days from the generation chain/event; earlier account erasure. Quota counters keep the current UTC day and previous 7 days. Short continuation validity is separate from record retention. |
| AI waitlist request and declaration | While the account exists, so access decisions stay accountable; removed on account erasure. |
| Private feedback and public-resource share events | 90 days, or earlier applicable account/resource deletion. GitHub copies are a separate operator process. |
| Shared Workshop snapshots | Until owner/source/account deletion or chosen expiry. New links default to 30 days; options are 1, 7, 30 days or no expiry. A withdrawn/expired token cannot be reused. |
| Private generated images, observation pictures and other private files | While referenced by saved, shared or published material. Unreferenced files at least 24 hours old are selected for removal on the next successful cleanup. Save a wanted generated image into a lesson within that grace period. |
| Published teaching resources | Publication lifecycle and catalogue removal. Account erasure removes author attribution; published content may remain. Ask for removal of personal prose or an improperly published resource. |
| Minimal deletion fences and operational status | Prevent old offline retries or withdrawn links from reappearing. Account-related fences are removed with account erasure where safe; permanent token digests retain no raw token, snapshot or account attribution. |
| Browser drafts and local teaching history | Browser storage explains expiry, sign-out and clear-device controls. Obsolete Gap Analysis browser records are removed on startup; downloaded reports and device backups are outside this cleanup. |
Account rights and files
Account provides export with file bytes, profile correction, history clearing and confirmed account erasure after recent sign-in. Erasure removes private files through the storage service before account records and authentication. A failed operation remains retryable; do not treat an error as completed deletion. School records and published personal prose may need manual assistance. Withdrawing a share prevents future access but cannot delete another person's download or printed copy.
Supplier copies and administrative records
Hosting, authentication, email and storage logs/backups follow actual supplier settings. Their production retention periods and recovery procedures are not yet verified; we cannot promise immediate erasure from backups. The observed Supabase Free plan has no included project backups. External/manual copies and recovery have not been established, and database backups alone would not cover uploaded file bytes. Before school adoption the agreed annex must specify those periods. Deleted data must not be made live again after restoration. AI supplier retention is described in AI transparency, not inferred from application settings.
Support, complaints, adoption and notice-subscription correspondence is handled by Karl through the published mailbox. Proposed handling is to review ordinary support and withdrawn/unsuccessful adoption requests after 12 months; keep only information still needed for an unresolved matter. Keep active school agreements and minimum completion/notice records for their operational and documented legal purpose, with an agreed, justified post-termination period before acceptance. These manual periods and mailbox access/backup controls require owner/DPO confirmation; automated database cleanup does not clean email. No indefinite blanket retention or completed mailbox purge is claimed.
GitHub feedback copies are reviewed on a privacy request and at least every 90 days while retained. Closing an issue is not erasure: personal text/attachments must be removed separately. Downloads, device backups and school-held copies remain the holder's responsibility.