Last updated: 12 August 2026
Narrly is a free tool that helps video editors line up a Guide voice-over against a Master recording. This policy explains, in plain English, what happens to your data when you use it. The short version: we collect as little as possible, we don't keep your audio, and we don't ask who you are.
Narrly is run by two people, James Millner and Ross Martin, both based in the UK ("we"/"us"). We decide together what data Narrly handles and why, so in law we're what's called joint controllers. In practice that means we're both responsible for everything set out here, and it doesn't matter which of us you contact: whoever picks it up, you'll get the same answer and the same help. If you want to reach us about anything in this policy, email hello@jamesmillner.dev.
There's no sign-up and no login. We don't ask for your name or your email address; you just open the site and use it. Narrly is free during early access, and we don't take payments of any kind, so there are no card or billing details for us to handle.
To be straight with you: we don't build any profile of who you are, but running a website does mean briefly handling a bit of technical data, like your IP address in our server logs, to keep the service working and to stop people abusing it. We keep those logs for no more than 30 days, then they're deleted automatically. And the audio you upload will, of course, contain voices. We never use any of this to work out who you are or to market to you.
There are two reasons in law that let us handle your data.
When you upload audio and ask Narrly to line it up, we handle those files because it's the only way to give you the thing you asked for. The law calls that performance of a contract (UK GDPR Article 6(1)(b)).
For everything else we rely on our legitimate interests (Article 6(1)(f)): keeping brief technical logs so we can keep the service up and stop people abusing it, and keeping anonymous records of each run so we can spot problems and make Narrly better. We've weighed that against your privacy and we think it's a light touch, because we don't build profiles, we don't market to you, and we never try to work out who you are. If you'd like to object to any of it, just email us.
When you upload your audio, it's processed entirely on our own systems within the EU. It is never shared with third-party AI platforms or cloud services, and it's used only to produce your files.
Your files are temporary. They're deleted when you close the tab or start a new session, and if anything slips through, it's automatically purged within a few hours; at the very latest. We don't keep your audio, the working files we create while processing it, or the final outputs.
To keep Narrly running well and improve it, we keep a small record of each run: high-level technical and performance figures only, like timings and quality scores. There are no visible file names, none of your audio, and nothing of what was said.
While your session is live, the record is tied to a random, temporary reference so we can tell that a run led to a download. Once the session is over that reference is deleted, and what's left is a set of numbers with nothing linking it back to you. As far as we can tell there's no way to trace one of these records to a person. We keep them for up to 24 months so we can spot trends and make Narrly better, then they're deleted.
To be transparent: because nothing connects these records to you, we can't pick out the ones from your runs if you ask us to. There's nothing in them that tells us which were yours.
We use a privacy-first, cookie-less analytics service to see basic, aggregate numbers: how many people visited a page, and how many got as far as running an analysis or downloading a result. It's counts only, never tied to you as a person. There's no cross-site tracking, no personal profiles, and no advertising cookies.
We don't use tracking cookies. The only thing Narrly stores in your browser is your light/dark theme preference, so the site remembers how you like it. That's the lot.
We use a small number of trusted service providers to run Narrly: a cloud hosting provider (EU-based) and a privacy-first analytics provider. They act on our instructions and only get what they need to do their job.
Your audio, your results, and everything we do with them stay on our own servers inside the EU, over an encrypted (HTTPS) connection. As a UK operator, sending data to the EU is covered by the UK's adequacy rules, so it's treated as safe as keeping it in the UK.
The one exception is our analytics provider, which counts visits and is based outside the EU, in a country the UK recognises as having equally strong data protection laws. It only ever sees the basics any website sees, like your IP address and which page you loaded. It never receives your audio or your results.
We take reasonable technical and organisational steps to protect the little data we do handle: everything runs over an encrypted (HTTPS) connection, and access to our systems is locked down. No system on the internet is ever completely bulletproof, but because we hold so little and delete your audio so quickly, there's very little sitting around to be at risk in the first place.
Narrly is intended for users aged 16 or over, and we don't knowingly collect data from children. Since there's no sign-up and we don't ask who you are, we can't gather personal details from anyone to begin with. If you believe a child has somehow provided us with personal information, email us and we'll delete it.
Because we keep so little, there's usually very little to act on, but you still have the usual rights under UK data protection law: to ask what we hold, to have it corrected or deleted, to object to or restrict how we use it, and to data portability.
If you're ever unhappy with how we handle your data, you can complain to the Information Commissioner's Office (ICO) at ico.org.uk, though we'd genuinely appreciate the chance to put things right first.
This is a plain-English summary of how Narrly works, written in good faith. If anything here is unclear, just ask.