← Back to flshy

Privacy Policy

Who we are

flshy is operated by overads private limited (a subsidiary of overads Inc.), referred to here as “overads”, “we” or “us”. If you want to reach a person about anything on this page, write to privacy@tryflshy.com.

Your footage never reaches us

This is the part that matters most, so it goes first. When you import a video into flshy, the file is read by your browser and stored locally on your machine. Editing, preview and export all happen on your own hardware. Your media is not transmitted to our servers, and we hold no copy of it.

There is one deliberate exception, and it only happens when you ask for it. If you use a cloud transcription feature, the audio needed for that job is sent to a speech-to-text provider so it can be turned into text, and is then discarded. The interface tells you when this applies, and offline transcription is available if you would rather nothing left the device at all.

What we actually collect

Account details

To sign in you give us an email address. If you use Google sign-in we also receive your name and profile picture from Google. We store a display name so the app has something to call you. That is the whole account record.

Sign-in codes and sessions

When you request an email code we store a hashed, short-lived, single-use version of that code. Once you are signed in we keep an opaque session identifier in a cookie so you stay signed in. Those cookies are strictly necessary for the service to function. Google Analytics sets cookies of its own, which are not necessary, and which are described under Analytics below.

Connected accounts

If you connect a third-party service, we store the access tokens needed to act on your behalf. Those tokens are encrypted with managed keys and are never exposed to the browser. Disconnecting a service deletes them.

Operational logs

Our servers keep short-lived technical logs (request times, error traces, IP address) to keep the service up and to defend against abuse.

Analytics

We use Google Analytics to count visits and see which pages people reach. It runs on this site and in the editor. It records page views, the page you arrived from, an approximate location derived from your IP address, and basic device and browser information, and it sets cookies so a browser that comes back is counted once rather than twice. It measures pages, not work: it never receives your footage, your projects, or anything on your timeline.

What we do not do

Who we share data with

We rely on a small number of processors to run the service: a cloud provider for hosting and storage, an email provider for delivering sign-in codes and service notices, Google Analytics for the visit counts described above, and Google if you choose to sign in with it. They act on our instructions and may not use your data for their own purposes.

We may disclose data if the law genuinely requires it, and will tell you where we are permitted to do so.

How long we keep it

Sign-in codes expire in minutes. Sessions expire when they lapse or when you sign out. Account records live until you delete your account, after which they are removed from live systems promptly and from backups on their normal expiry cycle.

Your rights

Depending on where you live, you may have the right to see the data we hold about you, correct it, delete it, take it elsewhere, or object to our processing of it. Email privacy@tryflshy.com and we will action it. You never need an account to ask.

Children

flshy is not directed at children under 13, and we do not knowingly collect their personal information.

International transfers

We operate from India and use infrastructure in multiple regions, so your data may be processed outside the country where you live. We use appropriate safeguards for those transfers.

Changes

If we change this policy we will update the date above, and for material changes we will tell you in the product or by email.