TAMTAMO / DATA AND USE

Personal Data Notice — Publication Draft

Prepared around the current workspace’s data flows under Türkiye’s Law No. 6698. Controller identity and request details must be completed.

Updated: 25 October 2026 · Based on the latest Tamtamo workspace

Publication details are incomplete. Do not use this as a final store-submission notice until operator identity, request channel and log retention are completed.

Controller and roles

The app developer/operator and the school or teacher using student data for their own educational purposes may have different roles. The developer has no automatic access to local working records in this distribution. Controller/processor roles depend on who actually determines purposes and means, not software ownership alone. Confirmed identity and contact fields must be completed below.

Data categories and purposes

Relevant features can process class/student identifiers, instrument/interests, assessment levels and history; audio/images during processing; works/notes, arrangements and rehearsals; exports and technical access/request records. Purposes are classroom activities, music-teaching plans, notation, user-requested exports/backups, technical security and support. Educational records are not used for advertising profiles or standardised aptitude/health diagnoses.

Collection method and legal basis

Data comes from teacher-entered forms, user-started activities/recordings, selected files, local storage and technical access to the site/contact channel. The basis for student-data processing must be established for the actual educational activity and authority under Articles 5 and, where applicable, 6. This notice does not assume consent for every operation. Notice, legal consent and device permission are separate processes. Establish the required basis and information before processing real student data.

Transfers and recipients

Automatic transfer of class records to a shared server or AI is disabled here. Users determine recipients of files they export/share. If retained in the mobile build, Google Fonts, cdnjs and jsDelivr may receive technical connection details and process them abroad. Before introducing cloud, server audio or AI services, determine recipients, purpose, country and the actual conditions under Articles 8 and 9.

Retention and removal

Local records can remain until removed by you or app/device data clearing; the 30-assessment limit is not an expiry date for a whole student record. Audio and annotated images are handled temporarily rather than as permanent working records; notes and results may be stored. Backups and exports are separate copies. The relevant controller must establish school retention duties and server/communication log periods.

Individual rights and requests

Article 11 rights include learning whether data is processed; requesting information on purposes, use and recipients; correction and, when conditions apply, deletion/destruction; notification to recipients; objection to adverse results from solely automated analysis; and compensation for damage from unlawful processing. Students/guardians should contact their school/teacher for school-held records and the listed request channel for developer-processed site/support data. Records inaccessible to the developer must be managed on their holding device. Request verification should not seek more data than necessary.

Publication details

Developer / data controller
Not provided yet
Request email
Not provided yet
Request / contact address
Not provided yet
Website access-log retention
Not provided yet

Related pages

App availability ↗