Your information
Privacy policy
Prepared 8 November 2026
This policy explains the public HornStudio information site and the private music teacher workbench, including its Google Calendar connection.
1. Contact
For questions about HornStudio, access to your information, corrections or deletion requests, contact info@loveozday.com.au. Please do not email passwords, authorization codes or classroom recordings.
2. This public website
This site provides application information. It has no login, forms, advertising, analytics scripts or tracking cookies. The hosting server may process ordinary request information, such as an IP address, requested URL and response status, to serve pages and investigate technical problems. This site does not display private teaching records.
3. Google Calendar access
The account holder grants read-only calendar permissions. HornStudio reads the list of calendars to let the teacher select one. For the selected calendar, it processes event identifiers, titles, start and end times, time zones and cancellation status to match lessons to students and maintain the workbench timetable.
The current synchronization workflow reads a rolling four-week window from the current day. It may also check an event already linked to a lesson when that event moves outside the window. Unknown private events are not imported as lessons. HornStudio does not import event descriptions, attendee lists or locations in this workflow.
Google’s permission screen may describe access to events on all calendars. HornStudio’s configured synchronization reads the calendar selected by the teacher; it does not write changes back to Google.
4. Use and storage
The teacher uses calendar information for lesson scheduling, matching and synchronization. HornStudio stores lesson times, source identifiers, synchronization status and teacher-confirmed aliases in its workstation database. It keeps encrypted authorization credentials separately on that workstation, not in this public website. It does not intentionally put credentials or full private event descriptions in application logs.
Lesson records remain available for teaching history after a calendar connection ends. Synchronization is separate from the teacher’s classroom analysis workflow, which can process selected teaching material through configured local or external AI providers. The teacher chooses and reviews that material; this public site does not run those analyses.
5. Sharing and human access
HornStudio does not sell Google user data, use it for advertising, or use it to develop, improve or train generalized AI or machine-learning models. The calendar connection communicates with Google to obtain authorized calendar data. Authorized operators may access stored data for teaching, support or security, and may disclose information when a legal obligation requires it. The public information-site host does not receive the workbench’s calendar credentials or lesson database.
HornStudio’s use and transfer of information received from Google APIs will adhere to the Google API Services User Data Policy, including its Limited Use requirements.
6. Disconnect, retain or delete
You can revoke HornStudio’s access through your Google Account connections. Revoking access prevents future authorized calendar reads but does not delete lessons already imported into HornStudio. Contact us to request deletion of stored authorization credentials or imported calendar information. We will confirm the scope with you so that a request does not unintentionally remove teaching records you need to retain.
Teaching records and calendar mappings remain until the teacher removes them or an operator completes an agreed deletion request. Backup copies may retain earlier data until the operator replaces or removes those backups. We do not promise immediate deletion from all backups.
7. Safeguards and changes
The operator restricts access to the workstation and protects stored authorization credentials using the operating system’s current-user encryption. These controls reduce risk but do not guarantee absolute security. We will update this page if the data flow or deployment changes materially, including any future online student service.