Privacy Policy

Schools. School name, web address, branding, time zone, a billing or administrative contact email, and purchase-order and invoice details.

Staff. The name and email address a director or delegate signs in with, the role the school assigns, and invitations sent to staff.

Students and other members. LyreLink does not ask members for their names, email addresses, or other contact details, and does not keep class rosters. A member joins with a school code and uses a session identifier on their device. Session identifiers, connection information, and push addresses are not necessarily anonymous. While a device is connected, staff can see how many devices are connected and which instrument part each one selected.

Music and rehearsal activity. PDF parts and song details that staff upload, the song queue, and messages staff send to members.

On the member's device. Part preferences, annotations, and downloaded parts stay in the browser on that device. If a member turns on song alerts, the browser's push address is stored so LyreLink can send them.

Service records. Records needed to run and protect LyreLink, such as audit records of staff and operator changes where auditing is enabled, and short-lived counters that stop repeated sign-in guessing. These records do not contain access codes, passwords, or music.

We use information to provide LyreLink to the school: signing staff in, showing members the right music, keeping devices in sync, supporting and securing the service, and billing the school.

We use student information only to provide LyreLink to the school. We do not sell student or user information, use it for targeted advertising, or build profiles of students for any purpose other than supporting the school's use of LyreLink.

Depending on the deployment and features in use, LyreLink relies on these providers for hosting, storage, sign-in, billing, communications, and operations:

• Vercel (application hosting)
• a managed PostgreSQL host (school, staff, and billing records)
• Upstash (live rehearsal state and alert subscriptions)
• Microsoft Azure (private music file storage)
• Ably (realtime updates)
• Clerk (staff sign-in and invitations)
• Stripe (billing)
• Cloudflare (DNS, operational alerts, and scheduled tasks)
• Resend (operational alert email)
• Healthchecks.io (independent scheduled-task monitoring)
• mailbox and routing providers (operational notifications and support correspondence)
• your browser's push service, if you turn on song alerts

Providers may also process certain information for their own purposes, such as account administration, security, fraud prevention, and legal compliance, under their applicable terms and privacy policies. Provider agreements and the services used determine their roles and obligations.

Information may be stored or processed in the United States and other countries. This includes backups, logs, support access, and delivery through providers and their subprocessors, including the browser-selected push service. We do not guarantee U.S.-only processing or that all processing stays in a particular country. A U.S. hosting or storage region alone does not establish where every provider processes information.

If your school requires a particular processing location, contact us before use. Any location-specific commitment must be verified and expressly included in a signed agreement with the school. This policy does not change an existing signed agreement or remove protections required by applicable law.

We tell subscribing schools before adding a provider that will handle their information. We disclose information otherwise only when the law requires it.

FERPA. Where a school relies on the school-official exception, the actual agreement and processing must establish the required institutional function, school direct control, legitimate educational interest, annual-notice criteria, and use and redisclosure conditions. This notice alone does not establish that arrangement.

COPPA. The intended school-directed audience is students aged 13 and older. Code-only membership does not establish age or resolve COPPA applicability, including actual knowledge of under-13 use. Required authorization, notices, security, and retention duties must be established for the actual use; school permission is not a blanket exemption.

Washington (RCW 28A.604). Applicable school-service duties must be assessed for the school and actual information handled. This draft notice does not by itself establish security-program, access, correction, or deletion compliance.

We keep a school's information while it subscribes. Staff can delete songs at any time. Directors can revoke a join code to reject online access by sessions issued with that code, or use the school-wide member-session revocation control to reject all existing member sessions. Creating another join code does not revoke existing codes or sessions.

A school can ask for an export of its information, or for deletion. When a school closes, its information stays restorable for a recovery period (currently 30 days). Expiry of that period does not automatically delete information: deletion requires an authorized purge after the recovery window, subject to retention holds and applicable legal requirements. The school's recorded retention setting is advisory, not an automatic deletion schedule. Billing records, audit records, backups, and recoverable storage versions are accounted for separately. We will tell the school what was deleted, what remains, and the applicable retention periods.

The routine recovery period is not an exception to earlier required deletion. Complete record and music return, earlier-deletion mechanisms, and lawful retained-copy handling still require verification before paid-school launch.

A disconnected device with prepared music may retain access until its existing server-issued offline lease expires: up to seven days for members and at most 24 hours for staff, shortened by session and applicable service deadlines. Payment grace does not extend a subscription term. It cannot renew that lease while offline; revocation is enforced when it reconnects.

A member can remove LyreLink information from their device by clearing the site's data in their browser.

Parents and eligible students should ordinarily contact their school, which controls its records in LyreLink. We help schools respond to access, correction, and deletion requests. Privacy requests can also be sent to security@lyrelink.com. Where applicable law requires a direct operator response, school routing is not a condition of that right.

LyreLink uses encrypted connections, keeps each school's information separate, stores sign-in codes and invitation links only in protected form, limits staff and operator access to what their role needs, and supports durable auditing of changes. Paid-school deployment requires auditing to be enabled and verified. No system is perfectly secure. We assess actual or reasonably believed unauthorized access, acquisition, use, disclosure, alteration, or loss of school information. When applicable law or a signed agreement requires notice, we notify the school without unreasonable delay, preserving earlier required deadlines. Required notice does not await final forensics.

We will give subscribing schools notice before a material change to how we collect, use, or share student information. The “Last updated” date reflects the most recent change.

Privacy and security questions, and vulnerability reports: security@lyrelink.com.