Privacy Policy

1. Scope and users

Tamtamo helps teachers manage classes and students, run pitch, rhythm and listening activities, prepare scores, arrange parts for groups and plan rehearsals. It is a teacher-managed workspace. This distribution has no user accounts, payments, advertising or automatic cross-device synchronisation.

2. Stored working data

Working data includes the class name and creation time; a student name or nickname entered by the teacher, class association and instrument/interests; pitch, rhythm and listening levels, explanations, test date and suggested role. A student’s history may include up to the latest 30 assessments. Added works may include title, type, source/composer, notes and creation time. Arrangements, rehearsal plans, goals and a notation draft may also be stored. A full legal name is not required; a classroom nickname can be used.

3. Microphone and raw audio

The microphone is used when you start recording and grant the device permission. Local student assessment analyses audio on the device and writes results, rather than raw audio, to the permanent student record. Its playback URL is released when assessment finishes. In melody transcription, audio can remain temporarily available for “Listen to recording” during the working session. The audio file is not added to the local work record or JSON backup; extracted notes can be saved. This does not promise forensic erasure of memory. An original file recorded with another phone app may remain separately on your device.

4. Images, camera, PDF and MusicXML

Only files you select and images you supply through the device picker/camera interface are processed. The workspace code does not record video or monitor the camera in the background. Score-image/PDF recognition and MusicXML parsing run locally. An annotated score image may be shown temporarily; the persistent draft keeps note data instead of the annotated image. Deleting an app record does not delete originals in your gallery or files.

5. Storage, retention and security

The reviewed local workflow keeps class, student and notation records in device-local storage without active central-server sync. They may remain until deleted by the user or app/device data removal; there is no automatic expiry. JSON and CSV exports have no additional file encryption. Protect device access and backups. Device-backup and uninstall behaviour will be checked in the final Android/iOS package.

6. AI and optional server features

AI, server transcription, instrument separation and shared-data sync are not connected in this distribution. The source workspace contains connection options. If enabled, processing may include class name, student counts, instrument/interests and levels, works/notes, goals and your free text. Automatic prompts omit the student-name field, but class names and free text can still identify people. Removing names alone does not anonymise data. Server transcription/separation can upload raw audio. These services must not be enabled for personal-data use before recipients, countries, retention and required permissions are disclosed.

7. External resources and access logs

The promotional site has no advertising or behavioural analytics. Hosting, network/CDN and support providers may process IP and technical access records; retention will be disclosed for the deployment. The development workspace has Google Fonts, jsDelivr and optional cdnjs dependencies. The final mobile build must be checked for bundled resources and external requests; no blanket “no third-party data” statement is made before that check. External score archives have their own policies.

8. User exports and deletion

A JSON backup may contain all working collections; CSV contains the selected class’s student and assessment table. Printing/PDF moves the displayed records into the output medium. Sharing those files is your decision and requires appropriate authority and secure handling. You can delete a student or class, or remove all local working data from “Verilerim”. Previously created backups, CSV/PDF, screenshots and original audio/images must be deleted separately. See Data Deletion for details.

9. Student data and decisions

The teacher/institution entering student data must establish its authority and required notices. Microphone permission alone is not legal consent on a student’s behalf. Use nicknames and avoid unnecessary identifiers or contact details. Pitch/rhythm/listening results are classroom indicators, not a standardised aptitude test, medical diagnosis or definitive decision about a student’s future. The teacher reviews role suggestions.

10. Contact and changes

Developer/controller and request-channel details appear in Publication Details below. Until missing fields are completed, this notice is not final for store submission. Server, AI, account, advertising, analytics or payment changes require an update to reflect the actual release. The local-use description is not an automatic promise for all future versions.

Related pages