Vial Keyboard Layers
For Vial keyboards, in your browser
Privacy policy
In short
- No tracking. No analytics, no account, no servers.
- Your
.vilfile never leaves your device. - What it keeps stays in your browser.
- I only get something if you choose to contact me.
Who is responsible
Vial Keyboard Layers is made by Dileepa Ranawake, a sole trader in Hull, UK. I'm the data controller for anything you choose to send me.
What it does with your data
One purpose: show every layer of your Vial keyboard layout on one screen, from a .vil file you load. It only reads the file. It can't change anything on your keyboard.
- The
.vilyou load or drop on the page: read in your browser, to draw the map. It is never uploaded. - A
notes.jsonyou import: read in your browser, for your key names. - The default key names: when the page is opened from a website, it reads the
notes.jsonfile beside it on the same site. Nothing about you is sent with it. This is the only network request the page makes of its own. - Export notes.json saves a file to your device, where you choose. Nothing is sent.
What it keeps on your device
In your browser's local storage, for this site only:
- your display choices: Mac or PC labels, US or UK keyboard layout, light or dark theme
- the last
.vilyou loaded and its file name, so the page opens on your layout next time - names you give keys, layers and macros, kept per layout by the keyboard's ID from the
.vil, and what each named macro did when you named it
How long: until you remove it. The round-arrow button beside Load .vil removes the saved layout. Clearing this site's data in your browser removes everything.
The Mac app keeps its own copy in its own storage, and remembers its window's size and place.
What it never does
- No analytics, tracking or ads. It sets no cookies.
- No servers: there is nothing to upload to.
- No remote code: one file, with no third-party scripts or fonts.
- Nothing reaches me unless you contact me.
Who handles it for me
- GitHub hosts the live page (GitHub Pages). Like any web host, it handles your IP address to deliver the page and may keep it in its logs, under GitHub's privacy statement. I don't see those logs. A downloaded copy, or the Mac app, runs offline.
- My website (Cloudflare) hosts this policy page. The host handles your IP address to deliver it, and the site counts visits with Cloudflare Web Analytics, which sets no cookies and does not identify you. I see only totals. The Vial Keyboard Layers page itself counts nothing.
- Ko-fi handles the payment if you choose Buy me a coffee, with its payment provider, under Ko-fi's privacy policy. Ko-fi tells me about it. Why I keep it: UK tax law asks me to keep records of what I'm paid, for 5 years after the 31 January deadline for that year's tax return.
- Google stores the emails you send me in my Gmail inbox, and is a controller in its own right under Google's privacy policy. It is a US company and may store them in the US; it is certified to the UK–US data bridge.
- Other sites: Edit in Vial (vial.rocks), the GitHub and LinkedIn icons, and my GitHub profile open those sites in your browser. They have their own privacy policies.
Your rights
Under UK data protection law you can ask me for a copy of anything I hold about you, and ask me to correct it, delete it, limit how I use it, or stop using it. I'll reply within one month.
You can object to my using your email at any time: tell me and I'll stop.
What's in your browser is yours: clearing this site's data removes it.
If you're unhappy with how I've handled your data, you can complain to the Information Commissioner's Office (ICO).
Contact
Email [email protected].
I get your email, including your email address and name as your email app sends them, and anything you attach. Why: to reply and to improve the page. That is my legitimate interest: you wrote to me, and I need your email to reply. Where it's kept: my Gmail inbox. Only I read it. It is never sold, shared or added to a mailing list. How long: I delete emails about the page within 12 months, or sooner if you ask.
Changes
If what the page does with data ever changes, this page changes first, and the version and date above go up.