Festival Runner privacy
Last updated October 22, 2026
The short version
Festival Runner has no server and no database of its own. What you enter stays on your device and, if you sign in, in your own Google Drive or Dropbox. The app's developer can't see it. The only things that reach us are messages you choose to send: feedback and Pro beta requests.
On your device
Your projects, festivals and laurel images are kept in your browser's storage on that device. The app also remembers a few settings there: your light or dark theme, whether you've seen the welcome screen and, while you're signed in, your sign-in with Google (a token that expires after about an hour) or Dropbox (a token the app renews itself). The desktop app keeps its sign-in encrypted with your computer's keychain. If you use the app without signing in, nothing leaves your device.
If you sign in with Google
- The app asks for one permission, drive.file. It lets the app create files in your Google Drive and read only the files it created. It can't see anything else in your Drive.
- It creates a folder called "Festival Runner" holding your app data, your laurel images and any spreadsheets you export.
- It reads your Google email address only to show which account is signed in.
- Your browser talks to Google directly. Nothing passes through any other server.
- Google's sign-in uses Google's own cookies, under Google's privacy policy. Festival Runner sets no cookies of its own.
If you sign in with Dropbox
- The app gets its own folder in your Dropbox, Apps/Festival Runner, holding your app data and laurel images. It can't see anything else in your Dropbox.
- It reads your Dropbox email address only to show which account is signed in.
- Your browser or the desktop app talks to Dropbox directly, under Dropbox's privacy policy. Nothing passes through any other server.
Feedback, beta requests and update emails
- Send feedback (in Settings) sends your message, the email address if you add one, and, if you leave that box ticked, the app version and your computer's system type. It goes through a form hosted by Netlify and reaches us by email. Nothing else from the app is included.
- Requesting a Pro beta code sends the name, email and details you type into that form. We use them to send your code and, only if you tick the box, to email you when there's a new version. Every update email has a way to stop them.
- We keep these messages only as long as we need them to reply or to run the beta. Ask us any time to delete yours.
Updates (desktop app)
The desktop app checks GitHub, where its new versions are published, a few times a day. That request carries nothing about you or your projects, though GitHub sees your IP address like any web request (see GitHub's privacy statement).
Importing a spreadsheet
When you import from a Google Sheet, your browser reads that sheet from Google using the link you paste. The sheet must be shared as "Anyone with the link can view", so only import sheets you're comfortable sharing that way.
Removing your data
Settings → Erase all data removes everything from the device. To remove your synced copy, delete the "Festival Runner" folder from your Google Drive, or Apps/Festival Runner from your Dropbox. You can take away the app's access any time at myaccount.google.com/permissions or in Dropbox under Settings → Connected apps.
No tracking
No analytics, ads or trackers, and nothing is sold or shared. The app never has your projects, and messages you send are used only to answer you. The site is hosted on Netlify, which serves the app's files and, like any web host, keeps standard server logs such as IP addresses (see Netlify's privacy policy).
Children
Festival Runner is meant for filmmakers aged 13 and over, or the minimum age to have a Google account where you live.
Changes
If this policy changes, the new version will be posted on this page with a new date.
Contact
Questions: festivalrunner.support@gmail.com