Vdex privacy policy
The short version
- Vdex has no accounts, no servers of its own, no advertising, no analytics and no tracking.
- Everything you type stays on your phone or computer. The people who make Vdex never receive it.
- Information leaves your device only when you use a feature that needs it: linking your own cloud storage or calendar, looking up the weather or an address, scanning a page, or sharing something. Every case is listed below.
1. Who is responsible
Vdex is made and published by its developer, TheCrowBro, as an open-source project. The complete source code is public at github.com/TheCrowBro/Logi-Video-Production-app-, so anyone can check what the app does. Questions about this policy can be asked by opening an issue on that page.
2. What Vdex stores, and where
Vdex keeps the information you enter in the app's own storage on your device: the browser's storage for the web app, and the app's folder for the desktop app. That information can include:
- Bookings: the job, the client and their contacts, addresses, dates, the schedule, notes, and the hours you worked.
- Call sheets, quotes and invoices made from those bookings.
- Crew: names, roles, phone numbers, email addresses and day rates.
- Equipment: items, serial numbers, values, warranties and service history.
- Venues: addresses, access notes and map coordinates.
- Insurance policies and their dates.
- Your own profile: your name, contact details and the QR contact card made from them.
- Timecode notes, scripts you import, and your settings.
None of this is sent to us. You can see, export or erase all of it at any time under Settings → Backups & data.
3. Your PIN and fingerprint or face unlock
If you set a PIN, Vdex encrypts its storage with a key derived from that PIN using AES-256-GCM. The PIN itself is never stored, and nobody, including us, can recover it. Fingerprint or face unlock uses your device's own system (WebAuthn). Vdex never sees your fingerprint or your face; it only receives the device's confirmation that it was you.
4. When information leaves your device
Each of the following is optional. You switch it on, or trigger it, yourself.
Cloud storage you link
You can link Dropbox, Google Drive, Microsoft OneDrive, a WebDAV server of your choosing, or a folder on your computer. Vdex then saves its backup files into your own account, so your other devices can read them and a copy survives a lost phone. That content is held by the provider under its own privacy policy. We have no access to it. Sign-in tokens stay on your device and are encrypted while Vdex is locked. You can unlink the storage in Vdex at any time and withdraw Vdex's access in your provider's account settings.
Calendar sync and calendar feeds
If you switch on calendar sync, Vdex creates and updates events for your bookings in your own Google Calendar or Microsoft Outlook calendar: the title, dates, location and description. The "Add to calendar" buttons open your calendar app with the same details. If you create a calendar feed, Vdex saves a calendar file to your linked storage and asks that provider for a share link. Anyone who has that link can read the feed, so share it only with the people you want.
Weather
For a booking with a location, Vdex asks Open-Meteo (open-meteo.com) for the forecast. It sends the map coordinates of the shoot location and nothing else: no names, no account and no identifier.
Addresses and maps
When you look up a venue or press "Find on map", Vdex sends the address text to OpenStreetMap's Nominatim service to turn it into coordinates, and loads map images for the area shown from OpenStreetMap's tile servers. Directions buttons open Google Maps or Apple Maps on your device with the address.
Scanning a printed script
Text recognition runs on your device. The first time you use it, the app downloads the recognition library and its English language data from public content delivery networks (cdnjs by Cloudflare, jsDelivr and the Tesseract.js project). The photo of the page never leaves your device.
Signing in to Google or Microsoft
When you link Google Drive or Google Calendar, the sign-in library from Google loads and the sign-in happens with Google directly. The same applies to Microsoft when you link OneDrive or Outlook; its library loads from jsDelivr. Vdex receives only a token that lets it reach the files and calendars you allowed.
Sharing
When you email a call sheet, a quote or an invoice, Vdex opens your mail app with the text ready to send. Printing and the share sheet hand the document to the app you choose. Vdex sends nothing itself.
Invoice and quote links, and payment buttons
When you make a link for a client, the whole quote or invoice is packed inside the link itself. Opening it loads only Vdex's own page files; the contents of the document never reach us or any server, and nothing is stored online. Anyone who has the link can read it, so share it only with the client. The Pay buttons on an invoice open the payment service you chose, such as PayPal, Venmo, Cash App or a payment page of your own, with the amount and the invoice number filled in; what happens from there is between the client and that service, under its privacy policy. Vdex is never told whether a payment was made; you record payments yourself.
The website, updates and the app stores
Vdex's files are served by GitHub Pages. When you open the app, or it checks for a new version, your browser requests files from GitHub, which keeps ordinary web server logs such as your IP address, browser type and the time, under GitHub's privacy statement. The desktop app checks GitHub for new versions in the same way. If you installed Vdex from Google Play, Google gives us overall install and crash statistics. Those are not linked to anything inside Vdex.
The services Vdex may contact
| Service | When | What it receives |
|---|---|---|
| Dropbox, Google, Microsoft | Only if you link them | Your backup files, calendar events, and your sign-in |
| Open-Meteo | Bookings with a location | The shoot location's coordinates |
| OpenStreetMap | Address lookups and maps | The address text and the map area shown |
| cdnjs (Cloudflare), jsDelivr, Tesseract.js | First use of script scanning or Microsoft sign-in | A request for a code library, like any web page |
| GitHub | Opening the app and checking for updates | Ordinary web server logs |
5. Device permissions and why Vdex asks for them
- Camera: the white balance reader, the range finder, QR code scanning and script scanning. Images are processed on the device as you look at them.
- Microphone: the sound level meter and timecode sync listen live. Nothing is recorded or stored.
- Location: sunrise and sunset times, the weather, and the "use my location" button for a venue. A position is kept only where you save it, such as in a venue.
- Notifications: reminders for shoots and equipment service are scheduled on your device. There is no push server.
- Motion and orientation: the level and the range finder.
- Files: importing and exporting backups, saving PDFs, and scripts you share into Vdex.
- Fingerprint or face: unlocking, as described above.
Each permission is asked for the first time a feature needs it, and can be withdrawn at any time in your device's settings.
6. Children
Vdex is a tool for working film and video professionals. It is not directed at children under 13, or under the age of digital consent where you live, and we do not knowingly hold any information about them.
7. Your choices
- Export or back up everything, or erase everything, under Settings → Backups & data.
- Unlink a cloud storage or calendar in Vdex, and withdraw Vdex's access in that provider's account settings.
- Deny or withdraw any device permission in your device's settings.
- Uninstalling Vdex removes everything it stored on that device. Copies you placed in your own cloud storage stay there until you delete them.
8. Security
Vdex is delivered over HTTPS, runs only code from the addresses listed above, and stores nothing on any server of ours. With a PIN set, your information is encrypted on the device whenever Vdex is locked, hidden or closed. The source code is open for anyone to review.
9. Changes to this policy
When this policy changes, the date at the top changes with it, and the full history is visible in the project's public repository.
10. Contact
Open an issue at github.com/TheCrowBro/Logi-Video-Production-app-/issues.
← Back to Vdex