Data Deletion and Backups
What each deletion action removes. This version has no user accounts.
Updated: 25 October 2026 · Based on the latest Tamtamo workspace
Delete one student
Use the student’s delete control on the class screen and confirm. The name/nickname, instrument, levels and history in that student record are removed. Previously generated class comments, arrangements and rehearsal plans are separate documents; delete them separately when needed.
Delete a class
In class settings choose “Bu sınıfı sil” and confirm. The class, its students, linked arrangements and rehearsal plans are removed. Independent teacher-added works and other classes are not deleted.
Delete all local working data
In “Verilerim”, choose “Tüm yerel verileri sil”. You may export a JSON backup first. After two confirmations, this workspace’s classes, students, teacher works, arrangements, plans and notation draft are removed and recording/playback stops. There is no automatic undo. Old device/cloud backups remain until you also delete those copies.
Backups, exports and originals
JSON backups, CSV tables, PDF/printed outputs, screenshots and other exported copies are unaffected by in-app deletion. Manage original audio/image/PDF/MusicXML files separately in your gallery/file manager. Consult the authorised person for records subject to institutional retention duties.
Server records and account requests
This distribution has no accounts or active shared-data server, so it does not offer a fictitious account-deletion form. If accounts/cloud are added, in-app account deletion and the required web request route must be implemented. Website logs and sent support correspondence are separate from local class records; address those requests to the disclosed controller channel.
