Privacy policy

Your account

Signing in is handled by Netlify Identity, not by Latentshoot’s own database. It holds your email address, the name you gave it, and — if you sign in with a password rather than with Google — your password, which Latentshoot itself never sees or stores. Signing in leaves a small marker in your browser so you stay signed in between visits.

What is stored in Latentshoot’s database

Once you are signed in, Latentshoot stores the things a shoot needs: your team, the projects under it, and for each project the shot list, the shoot days and running order, the moodboard, the locations, the gear list, and the people on the crew list for that shoot. Two categories of that are personal data about people other than you, and worth naming plainly:

• Your library — the clients and contacts you keep at team level, so you do not retype them on every shoot. This is personal data about third parties (a client’s contact details, a model’s agency, a crew member’s phone number), and you are the one who decides to put it in Latentshoot and who has a basis for holding it — Latentshoot stores it on your behalf, it does not collect it independently.
• A project’s people and locations — a casting of a library contact onto one shoot (their call time, their number for that job), plus each location’s address, access notes, parking, permit and the person to ring there. Call sheets exist to carry exactly this, which is why it is treated as more sensitive than the rest of a project — see share links, below.

A project’s client name is never stored as its own text field — it is looked up from the client record each time, so renaming a client does not leave a stale copy sitting on old projects.

Uploaded images

Moodboard references, shot sketches and your team’s logo are kept as files in Netlify’s file storage (Netlify Blobs) rather than in the database itself. Each file is served back from a web address containing a long random code, and that code is the only thing protecting it: the service that makes the thumbnails you see in the app cannot be told to check whether you are signed in. Anyone who has the exact address of an uploaded image can view it. Do not put anything confidential in a moodboard reference or a shot sketch.

Share links

A share link is how a client or a crew member sees a project without an account. It works the same way as an uploaded image: the long random code in the link is the key. There is no password or login behind it unless you are on a plan that lets you add one. Anyone who has the link can see whatever it was created to show — a moodboard, a shot list, a schedule, or (on a call-sheet link) crew and location contact details. Treat a call-sheet link the way you would treat the printed sheet: fine for the people on the job, not for a public post. Switching a link off stops it working immediately; Latentshoot keeps a record that it existed and when it was last opened, for your own reference, even after it is switched off.

Payments

Upgrading a plan and managing billing happens through Stripe Checkout and the Stripe customer portal. Card details are entered on Stripe’s own pages and never reach Latentshoot’s servers. What Latentshoot stores about billing is limited to the references Stripe gives it for you and your subscription, the plan you are on, whether it is active, and when it next renews.

What stays on your device

On-set mode saves your taps — a shot marked captured, a reorder, a recorded duration — on the device itself before sending them, so a tap survives with no signal. Until they have gone through, they exist only on that one device: clearing your browser’s data for this site, or using a private window, can lose a change that had not sent yet. These public pages, including this one, carry no analytics or advertising trackers of any kind.

Who else sees any of this

Latentshoot is built entirely on Netlify: the site itself, the database behind it, file storage, sign-in and the image handling all run there. Payments are handled by Stripe. Maps, and looking up an address to place it on one, come from OpenStreetMap and its Nominatim address search. The map link printed on a call sheet opens Google Maps; following it is a visit to Google, the same as clicking any link. None of these exist to further process your data for their own purposes beyond providing the service Latentshoot is built on; none of them other than Stripe ever receives payment details.

Getting your data out, or deleting it

Latentshoot does not yet have a self-service export or account-deletion button. Until it does, write to hello@latentshoot.com and ask for either — a copy of a project’s data, or the deletion of your account and everything under it. One thing to know going in: a client or contact you have used on a shoot is archived rather than deleted when you remove it from your library, because it is part of the record of work already done; archiving hides it from your day-to-day lists without erasing that history. A full account deletion removes it regardless. [Exact retention periods for archived and deleted data, and the process and timeline for handling a deletion request, are to be finalised.]

Who is responsible for this data

Latentshoot is provided by [legal entity name and registered address to be added], subject to the laws of [governing jurisdiction to be added]. Requests about this policy, including a formal data-protection enquiry, can be sent to [a designated data-protection contact, or a statement that none is yet required, to be added] via the contact address above in the meantime.

Changes to this policy

If what Latentshoot stores or how it is used changes in a way that matters, this page will be updated and the date at the top will change. It is worth a re-read occasionally rather than only once.

Contact

Questions about anything above: hello@latentshoot.com.