Privacy Policy
This policy explains what personal information … (“we”, “us”) handles when you use Rundown, why, and what choices you have. Rundown is a web application that organisations use to schedule photography and video assignments.
1. Whose data this is
Most of the information in Rundown is entered by a customer organisation about its own work. For that information the customer decides what is collected and why, and we handle it on the customer's behalf to provide the service. If your details appear in Rundown because an organisation scheduled an assignment involving you, that organisation is the right place to ask about them first.
2. What we handle
| Information | Where it comes from | What it is used for |
|---|---|---|
| Name, email address, role, and for requesters office, title and phone | You, or the administrator who adds or invites you | Creating your account, signing you in, showing who is assigned to what |
| Password | You | Signing you in. Stored only as a salted hash; we cannot read it |
| Assignments, requests, locations, notes, working hours and availability | Your team | The schedule itself |
| Contact name and phone number for an assignment, attendee names | Your team or a requester | So the assigned crew can reach the right person |
| A record of who changed an assignment and when | Created as people use Rundown | Giving your team a history of each job |
| IP address | Your browser's connection | Limiting repeated failed sign-ins and abuse. Kept for about a day |
| Email delivery records (address, subject, delivered or bounced) | Created when Rundown sends a notification | Showing your team whether a notification arrived |
| Subscription status and Stripe customer reference | Stripe | Knowing whether a team's subscription is active |
| Technical logs of requests and errors | Created as the service runs | Keeping the service working and fixing faults |
We do not collect payment card details; Stripe does that directly. We do not use advertising or analytics trackers, and we do not sell personal information or share it for advertising.
3. Storage in your browser
Rundown does not set cookies. When you sign in it keeps a session token, your name and role, your team's name and your display preferences in your browser's local storage, so that you stay signed in and the pages look the way you chose. Signing out removes the session.
4. Who else handles it
We use a small number of companies to run Rundown. Each handles information only to provide its part of the service:
- Cloudflare hosts the application and its database, and keeps the request and error logs.
- Resend delivers the emails Rundown sends, and so receives the recipient's address and the message.
- Stripe handles subscriptions and payment, for teams that subscribe.
- Google Fonts supplies the typefaces. Your browser fetches them from Google, which therefore sees your IP address and the fact that a Rundown page was loaded.
- GitHub stores encrypted backup copies of the database.
If you turn on a phone calendar link, your assignments (times, places, contacts and notes) are sent to whichever calendar service you add it to, such as Apple or Google, under that service's own terms. Turning the link off in Settings stops it at once.
These companies may process information in the United States and other countries. We may also disclose information if the law requires it, or to protect the service and the people who use it, and it may pass to a successor if the business is sold or merged.
5. How long we keep it
- Account and schedule information is kept for as long as the team's account is open. Deleting a job in Rundown marks it deleted but keeps the record, so that a team's history stays complete.
- When a team closes its account and asks us to, we delete its information from the live service within 30 days. Copies in encrypted backups expire within 90 days after that.
- Sign-in attempt records are kept for about a day, error records for about 30 days, and password-reset links for an hour.
- A demo team opened from our website is deleted, with everything in it, about 24 hours after it is created.
6. Security
Connections to Rundown are encrypted in transit. Passwords are stored only as salted hashes. Each team's information is separated from every other team's, access within a team is limited by role, repeated failed sign-ins are locked out, and backups are encrypted. No system is perfectly secure, and we cannot guarantee that information will never be accessed without permission. If a breach affects your information, we will tell the affected team's administrators without undue delay.
7. Your choices and rights
You can change your password in Settings, and an administrator on your team can correct your details or deactivate your account. Email notifications from Rundown can be switched off for your account by an administrator.
Depending on where you live, you may have the right to ask for a copy of your personal information, to have it corrected or deleted, or to object to how it is used. To make a request, write to …. If your information was entered by a customer organisation, we will usually pass your request to that organisation, because the decision is theirs.
8. Children
Rundown is a workplace tool. It is not intended for children, and we do not knowingly collect their information.
9. Changes to this policy
If we change this policy in a way that matters, we will tell team administrators by email or in the application before the change takes effect, and update the date at the top.
10. Contact
Questions about this policy or your information: ….