Privacy policy

What we collect

• Your account. Your name, your email address, a password we only ever keep scrambled, the date you signed up, and one row per login session with the browser it was made from.
• Your orders. The brief you write, the reference links you attach, the plan you picked, the amount, and the dates it moved through.
• Your messages. Everything written in an order thread, by you and by whoever is cutting the job.
• Payment reports. Which method you used, the reference number, the amount, and whether the owner has confirmed it against the account.
• Mail, if you hold a mailbox here. Headers, message bodies and attachments, in and out.
• Server logs. Our host records requests the way every host does: address, page, time.

We never see a card number. Card payments happen on Stripe’s own checkout and Stripe keeps everything about the card. A bank transfer reaches us as a reference you type in yourself, so nothing else about your bank account comes near this database.

Nothing is uploaded to us on the order side either. References arrive as links to where they already live, and finished work goes back out as a link.

Why we hold it

To run your account, make the video you asked for, talk to you about it, take the money and keep the owner’s books straight. That is the whole list.

We do not sell it and we do not rent it out. The only email that leaves here is the kind that has to: invite links, address confirmation, password resets, and an answer when you write to us. There is no newsletter and no marketing list to get off.

Where it is processed

Six companies touch it. Each does one job for us and nothing of its own with what it sees.

• Vercel hosts the site. Every page you load is served by them, and their request logs are the logs named above.
• Neon is the database: accounts, orders, briefs, messages, payment records.
• Resend sends our email and receives the mail addressed to mailboxes on this domain.
• Cloudflare R2 stores raw mail messages and their attachments.
• Stripe takes card payments and holds the card details we never get.
• Zum Rails handles Interac e-Transfer and EFT for payers with a Canadian bank.

Their servers are not all in the country you are sitting in. If you would rather your brief stayed off one of them, ask before you order and we will tell you honestly whether that can be done.

Past those six, nobody. There is no ad network here and no data broker. We would hand something over if a court ordered it, and we would tell you unless the order said we could not.

How long we keep it

• Your account and its orders stay while the account does.
• Paid orders stay after that. What was bought, for how much, when, and who confirmed it is the owner’s accounting record, and it is kept as long as the tax authorities where the business sits expect it to be kept. Your brief text and your messages are not part of that record and go when you ask.
• Deleted mail sits in trash for 30 days. After that it moves to the owner’s vault, which holds it another 60 days, and then it is gone for good.
• Login sessions last 30 days. Logging out ends one on the spot.
• Host logs age out on Vercel’s own schedule. We keep no copy of them.

Who can see the inside of an order

The inside of an order means the brief, the references, the messages and the deliverables. The client who wrote it sees it, and so do the team members assigned to cut it. Nobody else, and that includes the owner.

The owner sees the outside of every order at all times: which plan, how much, what state it is in, who is assigned, which dates. To let the owner read the inside you switch Let the admin see this order on for that one order. It is off until you do, and you can switch it back off.

The people cutting your job are anonymous to you. You see “Team member 1”, “Team member 2”, in the order they were assigned. Their names, addresses and faces never reach a client screen or a client email. It runs the other way too: they see the work and whether the order is paid, never your payment details and nothing at all about another client.

Payment records are the owner’s alone. You see the state of your own orders, and nobody else’s.

One cookie

It is called su_session and it holds a signed session id. Nothing else: no name, no email, nothing anyone could read off it. Scripts on the page cannot see it, it lasts 30 days, and logging out throws it away. Without it you cannot stay logged in.

There is no analytics cookie, no advertising pixel and no third-party script watching what you do on a page. That is also why no consent banner stopped you on the way in. There was nothing to consent to.

What you can ask us to do

Ask for a copy of everything we hold about you, ask us to fix what is wrong in it, or ask us to delete the lot. Write to hello@secondunit.video from the address on the account and a person will do it. Thirty days is the outside limit we hold ourselves to; it is usually the same week.

If a paid order has to stay in the books, we will tell you which record is staying and why, and delete everything around it.

Not for under-18s

Accounts here are for adults. Do not make one if you are under 18, and do not put a child’s details in a brief. If you think a child’s data has ended up here, write to hello@secondunit.video and it will be taken out.

When this page changes

The date at the top moves whenever the words do. If a change actually affects you, a new company handling your data or a new use for it, we email the address on your account before it takes effect rather than hoping you re-read this page.

How to reach a person

hello@secondunit.video. It is read by the person who runs Second Unit, not by a ticket queue.

The rules for the work itself are in the terms, and what happens when a cut is wrong is on refunds and revisions.