Privacy
Limelight has no accounts, no sign-in and no database of people. Almost everything it knows about you lives in your own browser. This page lists exactly what leaves your device, when, why, who handles it and how long it's kept. There isn't much to list.
Nothing to sign up for, nothing to sign into, no password. There's no list of users because there aren't any; everyone is a visitor.
A show is saved to your browser, to a file on your computer, or as a setup code you copy. The code is the show. There's no copy on a server for it to point to, and nothing is uploaded when you save.
Lessons finished, steps done, check scores and the name you type on the progress page live only in the open page, and nothing keeps them after it closes. To keep them, you copy a progress code and paste it back in yourself, on this device or another. No server is involved.
No ads, no analytics service, no third-party scripts, no fingerprinting, no cookies, no tracking across sites. The tool does give each browser a random ID for its own visit counter, described below. Pages and their files come only from limelight.show. What you choose to send us goes to the services listed under Who handles data for us, and nowhere else. We don't sell personal information.
Four things can leave, and all of them are listed here in full. Only the first happens on its own. The other three happen only when you press Send or write to us.
The first time a browser opens the tool, it makes up a random ID and sends it once. That lets the site answer "how many different devices have used this?" Stored with it:
It doesn't store your IP address, your city, your name, anything you typed, or anything about your show. The ID is random. It isn't made from anything about you, and it isn't meant to identify you. This counter runs once per browser, ever, and is never sent again.
Each record is one small file in the host's private file storage (Vercel Blob), named after the random ID. Private storage can't be opened from the internet. Only the site's own functions can read it, and they show the records only to the owner, who needs a private key to see them. Anyone can ask the site for the total number of devices, which is just a number.
The Feedback button, and the Send report button on the box that appears when something breaks, send a report to the site's owner. Nothing is sent unless you press the button. A report can contain:
The Feedback button in the course is simpler. It sends what you wrote, your email if you typed one, and the address of the course page you were on.
How a report travels. The site passes it to a small Google Apps Script that emails it to the owner's Gmail inbox. If feedback email delivery is switched on, Resend, an email service, delivers a copy too. A picture isn't attached to the email. It's uploaded to the host's private file storage (Vercel Blob) under a random name, and the report carries a link to it. The link opens the picture only for the owner, with a private key. Each report is also written to the host's function log as it arrives, so nothing is lost if the email fails. The host keeps those logs only for a short time.
The contact page sends the reason you picked and your message, plus a name and an email address only if you typed them. It travels the same way as a feedback report, without any technical details. Nothing is sent unless you press Send.
Mail to hello@limelight.show or support@limelight.show is forwarded by Namecheap, the domain's registrar, to the owner's Gmail inbox. Replies are sent from Gmail or through Brevo, an email sending service. Your message, your address and anything you attach are kept as email.
These are stored by your browser, on your device, and are readable only by this site in that browser. None of them are sent anywhere, except the parts of a report you choose to send.
In the tool:
In the sound tool, only when you press Save: the workspace (its cue list and settings) and the audio files it uses, kept in the browser's own database (IndexedDB) so they're there next time. Audio that no saved workspace uses any more is deleted the next time you open the tool. Before you press Save, your audio is held only in the open page. The tool also remembers how you laid it out (which panels are showing, the inspector's height). Nothing in the sound tool is uploaded: not your cues and not your audio. A workspace you download is a file on your computer, and only yours. A Light cue, which presses GO in the lighting tool, passes a short message (GO, Back or a cue number) between two tabs of the same browser on your computer; it never leaves the computer. The lighting tool acts on it whenever a Lab tab of it is open in that same browser (a lesson in the course never does).
In the mixing tool, nothing you mix is kept: there is no autosave. The browser remembers only how you set the tool up (where the meters read, whether the EQ graph shows its spectrum and labels, and Hover help) and your theme. A mix is kept only when you save it as a file on your computer, and that file is only yours. Audio files you add play only in the open page: they're never stored or uploaded. The microphone is used only after you allow it; its sound is played on your computer, never recorded, stored or sent anywhere, and it stops when you close the page.
In the course: no progress is kept. For as long as the tab is open, the browser holds a random tab id that pairs the teacher-notes window with its lesson, and which page a check was opened from. Both are gone when the tab closes. Your theme choice is shared with the tool.
The site sets no cookies. Clear your browser's site data and all of the above is gone. The site can't recover it, because it never had it.
Teachers and IT departments tend to ask the same questions, so here are the answers in the words a policy needs.
The tool doesn't ask anyone, including children under 13, for a name, email address or birthdate to use it. The visit counter does send a random browser ID and the country when the tool is first opened, and we use those only to count visits and see roughly where the tool is used. A student's name typed on the course progress page never leaves that browser. See Children under 13 below.
Limelight doesn't currently receive or keep students' progress, quiz answers or grades. Those stay in the open course page or in a progress code the student holds. The operator of this site can't see any student's results.
There's no sign-up and nothing personal is asked for, so there's no account for a parent or school to approve. If a student does send a message, a school or parent can ask for it to be deleted; see Your choices and requests.
The site is served from limelight.show only. It loads no third-party scripts, fonts or images from anywhere else. Allowing that one domain is the whole configuration.
These follow the approach of Oregon's Student Information Protection Act (ORS 336.184), California's Student Online Personal Information Protection Act (SOPIPA), and similar student-privacy laws. They're promises about how we behave, not a legal opinion about which laws apply.
A school or district that needs a written student-data agreement, or these promises in a letter, can ask through the contact page or at hello@limelight.show, with an address to reply to.
If Limelight receives student information for a school, the agreement can set out what information is collected, why it's used, who can receive it, how long it's kept, how it's deleted, and what happens if the school stops using Limelight.
The site is hosted on Vercel, which serves the pages, runs the site's few small functions (feedback, pictures and the visit counter) and holds the files they store. Like any host, Vercel processes connection details (including IP addresses) to deliver the site and protect it, and handles them under its own privacy policy. Limelight doesn't store IP addresses. The visit counter keeps only the country the host works out from the connection.
These services do the delivering and storing. Each one handles data under its own privacy policy.
We don't sell personal information, and we don't share it with advertisers or data brokers.
When we delete something, we remove it from the inbox, the storage and the services we control. Copies in a service's own backups or logs expire on that service's schedule.
You don't have to send anything to use Limelight. Reports and messages are optional, the email box is optional, and in the Feedback box the show and the technical details are boxes you can untick.
Anyone can ask for a report, message, email or picture they sent to be deleted, and a parent or teacher can ask on a student's behalf. Write to support@limelight.show or use the contact page. Tell us roughly when it was sent and what was in it, such as the first few words, the email address you gave, or the page you were on, so we can find it. We'll delete it and tell you when it's done, within 30 days.
A device record has no name in it, so we usually can't tell which one is yours. Clearing your browser's site data removes the random ID from your device. The record left behind isn't linked to anything else we hold, and it's deleted on the schedule above.
The tool doesn't ask children for a name, email address or birthdate to use it, and nothing in the tool or the course needs one. The visit counter does send a random browser ID and the country when the tool is first opened. We use those only to count visits and understand where the tool is being used.
Students: if you're under 13, please don't put your name, email address or other personal information into a feedback or contact message unless a parent or teacher is helping you. A first name, or nothing, is fine, and the email box is only needed if you want a reply.
If we learn that we received personal information from a child under 13 in a way that needs a parent's consent, we'll take the steps the law requires, including deleting it. A parent or school can also tell us, and we'll delete it. Parents can ask us what a child sent, or ask for it to be deleted, at support@limelight.show.
Limelight is operated from the United States. Some of the services we use may process information in the United States or elsewhere.
Privacy laws in other countries may apply depending on where you are and what Limelight does with your information. Where a law such as the GDPR or the UK GDPR applies, we'll handle personal information as that law requires, including your rights to access, correction, deletion and objection. The controller is Limelight's operator, as described in section 12 of the terms.
If you have a privacy question or request, write to support@limelight.show.
Some information sent through feedback, the contact page or email is handled by the services listed under Who handles data for us. We limit access to those services and use accounts and security controls suited to the information they hold.
We don't promise that any internet service is completely secure.
We want Limelight to be usable by students and teachers with disabilities. We're working to make the site and the course accessible, and to follow WCAG 2.1 Level AA where the technology allows.
If something on the site is hard to use because of a disability, write to support@limelight.show and tell us what you were trying to do. We'll work with you on an accessible way to use the material.
Some pages link to other sites, such as Wikimedia Commons for the course photos, GNU for the license, and the Open Fixture Library. Those sites follow their own privacy policies, not this one.
If what the site keeps ever changes, this page changes first, with a new effective date at the top. A change that matters gets a short note at the top saying what changed and when. The intent won't change. No accounts, nothing personal asked for, and your work stays yours.