Privacy Policy
Last updated: October 8, 2026
This policy explains what happens to your data when you use INSV Player at insv-player.com.
The short version
- Your recordings never reach insv-player.com. They play in your browser: from your device, from the server a link points to, or from your Google Drive.
- There are no accounts, no cookies and no ads, and INSV Player sells no data.
- The site counts visits and plays without cookies and without knowing who you are.
Recordings you open
Files on your device. A file you drop or choose is read by your browser, on your device. It is never uploaded.
Links. A recording you open by its link is read by your browser straight
from the server that holds it, in parts, as it plays. That server sees your requests, as
it would for any download, and handles them under its own policy. The page's address then
holds the link (/?url=…) so that you can share it: anyone you give the
address to can open the same recording, if its server lets them.
Files from Google Drive
When you open a recording from Google Drive, Google asks you to sign in and to let INSV Player use the files you pick. You then pick them in Google's file picker.
- What the site can use: only the files you pick, not the rest of your Google Drive. It reads their contents, names and sizes. It does not read your name, your email address or anything else in your Google account.
- What it uses them for: to play the recording in your browser, to match the two files of a split recording by their names, and to search Google's picker for a split recording's second file by its name. It only reads the files: it never changes, creates or deletes anything in your Google Drive.
- Where they go: your browser reads the files straight from Google, in parts, as the recording plays. They never pass through insv-player.com, and the site keeps no copy of them.
- The access token: once you allow access, Google gives the page a token that expires within an hour. The page keeps it in memory, sends it only to Google with each request for a file, and forgets it when you close or reload the page.
- Who else gets it: no one. The site does not share or sell Google user data, does not use it for advertising, and does not use it to train AI or machine-learning models. The site's counts (below) note that a recording came from Google Drive and the camera model it names, never which file.
- Taking access back: remove INSV Player from your Google Account's third-party connections at any time.
Google's sign-in and file picker are Google's own pages: Google handles what you do there under the Google Privacy Policy. The page loads Google's code for them only when you point at, tap or tab to a Google Drive button.
INSV Player's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
What the site counts
The site counts its visits with Vercel Web Analytics, from Vercel, the company that hosts it. It sets no cookies and stores nothing on your device. Vercel tells visits apart by a code computed from each request and discards it after 24 hours, so it cannot follow you from one day to the next, or across other sites.
For each page view, it records the page, without anything after its ?; the
time; the site you came from; your country, region and city, worked out from your IP
address; your browser and operating system, with their versions; and whether you use a
phone, a tablet or a computer.
The site also counts:
- each recording that plays: whether it came from a file, a link or Google Drive, and the camera model the recording names;
- each recording that fails: the player's error code, and its message with links and file names taken out; the camera model and its firmware; your browser and its version; and, when a link could not be read, the service it points to, such as Dropbox, or "other site" for any other;
- each file or link the page turns down, and why, such as a link that is not https://.
None of this names a file, a link or a camera's serial number. The counts show which cameras and browsers play and what fails, so that it can be fixed. Under the GDPR, they rest on the legitimate interest in keeping the player working.
Hosting
Vercel Inc., in the United States, hosts the site. Like any web host, it receives each request your browser makes to insv-player.com, with your IP address, your browser and the full address of the page, including a link in it, and keeps them in its logs for a short time to run and protect the site. Vercel handles them under the Vercel Privacy Policy.
What stays on your device
When you look around a recording by moving your phone, the page reads the phone's motion sensors, and the readings stay on the phone. "Copy link" puts the page's address on your clipboard and nowhere else.
Other sites
The site links to others, such as GitHub and bubo2.com, which handle your visit under their own policies. Bubo² supports INSV Player but gets no data from it: following the link to bubo2.com tells Bubo² only that you came from here.
Where data is processed
Vercel and Google process the data above in the United States and in other countries where they run servers, under their own safeguards for moving data between countries.
Your rights
Depending on where you live, laws such as the GDPR give you the right to ask what personal data is held about you, to have it corrected or deleted, and to object to its use. The site itself keeps no personal data, and its counts cannot be traced back to you, so there is usually nothing to find or delete; write to the address below for help with any request. You can also complain to the data protection authority where you live.
Children
The site is not meant for children under 13.
Changes
When the way the site handles data changes, this page and its date are updated first.
Contact
INSV Player is run by Perica Milošević. Write to insv-player@bubo2.com with any question about this policy.