Privacy Policy
Last updated 15 November 2026
Basalt is built so that your files, your library and your viewing stay in your home. Refora Technologies runs no Basalt server, has no Basalt accounts, and receives no data from the apps: no telemetry, no analytics, no crash reports. This page sets out exactly what the apps keep, where, and the few things that ever leave your network.
1. What this covers
This policy covers the Basalt apps published by Refora Technologies: Basalt Host, on Windows, on
a Linux desktop, with no screen as a Linux service, and as a Docker image; Basalt for Windows;
Basalt for Linux; and Basalt for Android, whether it is installed from this website or from Google Play. It also
covers this website, basalt.reforatech.com, in section 8.
The apps are free software under the GPLv3, and their source code is public, so anything this page says can be checked.
2. The short version
- Your files are read and sent only between your own devices, on your own network, or to a device nearby that you send them to and its owner accepts, always encrypted with TLS 1.3. None of it goes through the internet.
- Everything the apps remember is kept on your own devices, mostly on the host’s computer.
- The only requests the apps make beyond your network are checking for and downloading updates, from GitHub or, for the Google Play version, Google Play, and, only if you switch them on, looking up posters for your films and series, and covers and photos for your music.
- This website counts visits with Google Analytics, which you can opt out of. See section 8.
3. What stays on your devices
On the host’s computer
Basalt Host keeps its data in one folder, and none of it is sent anywhere:
| Host | Where |
|---|---|
| Basalt Host on Windows, and Basalt for Windows | %APPDATA%\Basalt\, in your Windows user profile |
| Basalt Host on a Linux desktop | ~/.config/basalt/, in your home folder |
| Basalt Host with no screen | /var/lib/basalt-host/, readable only by the host’s own user |
| Basalt Host in Docker | /config, the folder you mount there |
| What | Why |
|---|---|
| Settings | The drive you chose to share, the host’s name, and the switches in its settings. |
| The host’s identity | A private key and certificate, made on that computer, that devices use to recognise this host. On Windows, the key is sealed by Windows for that computer, so a copy of the file opens nowhere else. |
| Paired devices | Each device’s name, its device identifier (see section 4), the public half of its sign-in key, whether it is read only or manages the host, and when it was last seen. |
| Setup code | On a host with no screen, the one-time code that lets the first device set it up, until a device has used it. |
| Profiles | Each profile’s name and colour, and its PIN in hashed form, never the PIN itself. For a profile let in from another drive, its name, colour and the drive it comes from, and never its PIN. |
| Files kept for devices that are away | A file sent through the host for a device that is away, until that device takes it or it is removed, with who sent it, to whom, and the file’s name and size. Kept outside the shared drive and encrypted, unless a device that manages the host turns that off, in which case they go into a Basalt shares folder on the drive. |
| Watch history and stars | How far through each video you are, and your starred files, per profile or per device. |
| Converting | Whether converting is on, how many films the host converts at once, and what it measured its computer can do. |
| Updates | Whether automatic updates are on, and the newest version it has found. |
| The media index | What is on the drive, sorted into films, series, photos, music and videos, with each video’s picture size. |
| Thumbnails and posters | Pictures made from your photos and videos on that computer, and posters, if you switched posters on. |
| A log | What the host did, such as devices connecting and anything that went wrong. It can include file and folder names from the drive. On Windows and a Linux desktop, it is replaced each time the host starts. With no screen, it goes to the system journal, and in Docker to the container’s log, kept as that system keeps them. |
On other Windows computers
Basalt for Windows keeps which host it is paired with, that host’s key fingerprint and last address, a remembered
profile sign-in if you asked for one, and your settings, in %APPDATA%\Basalt\. It signs in to the
host with a key of its own, made on that computer: kept in its TPM security chip where it has one, where it can
never be read out, and otherwise protected by Windows’ own per-user protection, so a copy of the file is of no use
on another account or computer.
Basalt for Windows and Basalt for Linux also keep a list of what was shared to and from the computer, for the Inbox,
and a nearby log: the steps of each share with a device nearby, with the names and network
addresses of the devices involved. It stays on that computer, and is only ever sent if you choose to send it to us.
Files shared to the computer are saved to the folder you choose, the Basalt folder in your Downloads
unless you change it.
On Android
Basalt for Android keeps the same things in its own private storage, which other apps cannot read, and its sign-in
key in the phone’s hardware key store, which no app can read it out of. That storage is left out of phone backups,
so a pairing never travels to another phone. Files you download, and files shared to the phone, are saved to the
Download/Basalt folder, where you and your other apps can see them.
4. What travels over your network
Announcements. So that devices can list it, the host announces itself on your local network every three seconds. The announcement carries the host’s key fingerprint, the computer’s name, the drive’s name, a port number, whether pairing asks for a PIN, and whether the host is waiting to be set up. Any device on the same network can see it, as with a network printer. It carries no files and nothing about who uses Basalt.
Connections. Everything else between a device and the host, including file lists, the files themselves, video streams, profile sign-ins and Manage host, is encrypted. Each device remembers the host’s key when it pairs and checks it each time it connects.
Recognising your devices. So that a phone or computer is recognised as the same device after Basalt is reinstalled, each app sends the host a device identifier. It is made from an identifier your phone or computer already provides to apps, scrambled one way before it leaves the device, so the original cannot be worked out from it. It is sent only to your own host, never anywhere else, and it is used only to keep one entry per device. It does not let a device connect: only pairing with the host does that.
Sharing between your devices. When you share a file with another device in your home, the offer goes through the host, which adds who sent it: the file names and sizes, and the sending and receiving devices. The file itself goes straight from one device to the other, encrypted, or, for a device that is away, waits on the host as described above. So that your devices can show which of them are on, each one tells the host while it is connected, and the host shows the devices of a profile to that profile’s other devices.
Devices nearby. With Receive from devices nearby on, a device answers devices looking for it on the same Wi-Fi, and, on Android and Windows, says it is there over Bluetooth Low Energy, with its name (such as the phone’s model or the computer’s name), its kind, a short code, and whether it asks for a code. Anyone nearby with Basalt, or a Bluetooth scanner, can see that, as with any Bluetooth device. It carries no files and nothing about your drive. When someone shares with it, the offer, the file names and sizes, and the files go over an encrypted connection between the two devices; with no Wi-Fi in common, over a small Wi-Fi the receiving device opens only for that share. Nothing is sent before the person receiving says yes, and none of it goes through the internet or to us. Turning the switch off stops all of it.
What the host sees. The host knows which paired devices are connected, what each is transferring, and which profile is signed in on each. It shows that in its own window, to whoever uses the host’s computer, and in Manage host, to the devices you have let manage it. It keeps watch history as described above, and does not send any of it anywhere.
5. What leaves your network
The apps make requests beyond your network for three purposes only: updates, and, if you switch them on, posters, and album covers and artist photos.
Updates
Basalt Host asks api.github.com whether a newer release exists a minute after it
starts and then twice a day. With Update automatically on, which is the default, it downloads a
new release from GitHub when nothing is playing, checks that it is signed by Refora Technologies and matches its
signed SHA-256 checksums, and installs it. On Linux, a small system helper does the downloading, checking and installing, and asks GitHub
the same question. In Docker, the host checks but never installs anything itself.
Basalt for Windows, Basalt for Linux and the Android app from this website ask api.github.com when
they open and twice a day while open, and download and check a new release only when you choose to install it.
These requests carry nothing about you, your devices or your drive beyond what any web request carries, which is your IP address. They are handled by GitHub under GitHub’s privacy statement.
The Google Play version is updated by Google Play instead. It asks Google Play whether an update
is waiting, and Google Play downloads and installs it when you choose to. To show what an update brings, it reads
that version’s release notes from api.github.com. Once, after you have watched a few films over at
least a week, it asks Google Play to offer you its rating card; Google decides whether it appears, and Basalt never
learns whether or how you rated it. These requests are handled by Google under
Google’s privacy policy.
Posters, only if you switch them on
Download posters is off until you turn it on, in Basalt Host or in Manage host. When it is on, the host sends the title and year of each film and series it recognised to Free Movie DB, a free film database service, and, if you add your own key and that service has no answer, to The Movie Database (TMDb). It saves the pictures it gets back. Those services receive the titles and your IP address, under their own privacy policies, and never your files. Switching posters off stops the lookups.
Album covers and artist photos, only if you switch them on
Download album covers and artist photos is off until you turn it on, in Basalt Host or in Manage
host. When it is on, the host sends the names of albums, songs and artists that have no picture of their own to
MusicBrainz (musicbrainz.org), and fetches covers from the Cover Art Archive
(coverartarchive.org) and artists’ photos from Wikidata and Wikimedia Commons
(wikidata.org, commons.wikimedia.org). If you add your own fanart.tv key, it also asks
fanart.tv (webservice.fanart.tv) for artists’ photos, by the artist’s MusicBrainz identifier and your
key. It saves the pictures it gets back. Those services receive the names and your IP address, under their own
privacy policies, and never your files. Switching it off stops the lookups.
Recognising films in the first place happens on the host’s computer, against a catalogue shipped inside the host. It needs no connection and sends nothing. Converting a film for a device that cannot play it also happens there, with FFmpeg on that computer, and sends nothing.
Things you start yourself
Play in your player hands a film to another player you choose, such as VLC, over a link that only exists on that phone or computer. What that player does is covered by its own policy.
The Docker image is downloaded from the GitHub Container Registry (ghcr.io) when you,
or a tool you set up, pull it, under GitHub’s privacy statement.
Send feedback opens a new email in your own mail app, addressed to us, with the app’s version and the kind of device filled in (on a phone, its model and Android version). Nothing is sent unless you send it, and we treat it as any email (see section 8).
6. Profiles and PINs
Profiles are optional. A profile is a name, a colour and a PIN of 4 to 8 digits, kept on the host. The PIN is stored only in hashed form, and repeated wrong PINs lock the profile for a while. Neither the host’s window nor Manage host ever shows PINs. Resetting a PIN or removing a profile signs that profile out of every device at once, and removing it also deletes its history and stars on that drive.
A profile can be used on another host you pair with, once someone who manages that host lets it in. The other host receives the profile’s name and colour and a statement from its own drive that the device acts for it, never its PIN, and keeps its own history and stars for it.
7. Android permissions
Basalt for Android asks for the following, each for one reason.
| Permission | What it is used for |
|---|---|
| Internet, and network state | To reach the host on your home network, and to check for updates. |
| Local network, Wi-Fi state and multicast | To hear hosts announcing themselves on the Wi-Fi, so you can pick one from a list, and to find devices nearby on the same Wi-Fi when you share. |
| Change network state | To keep the connection on the Wi-Fi when that network has no internet access, instead of Android moving it to mobile data. |
| Change Wi-Fi state | To open a small Wi-Fi of its own when a device nearby with no Wi-Fi in common sends you files, or to join that device’s, only for that share. |
| Nearby Wi-Fi devices | To look for and connect to that Wi-Fi of a device nearby. Declared to Android as never used to find where you are. |
| Bluetooth (find, advertise and connect to nearby devices) | To find devices nearby when you share, and, with Receive from devices nearby on, to let them find this one. Finding is declared to Android as never used to find where you are. On Android 11 and earlier, this is the older Bluetooth permission. |
| Location (precise and approximate) | Android needs it before an app can look for the Wi-Fi networks around, which reaching a device nearby with no Wi-Fi in common takes. Basalt never reads your location, and it is asked for only when you use devices nearby. |
| Foreground service and wake lock | To let a transfer or a song carry on while the screen is off, and, with Always ready to receive on, to stay ready to receive files with the app in the background. A notification says so while it happens. |
| Run at startup | With Always ready to receive on, to show a notification after the phone restarts that makes Basalt ready again with one tap. It does not start receiving by itself. |
| Notifications | For those notifications, for transfer progress, and for files offered to you, with Accept and Decline. |
| Install packages | Only in the version from this website: to hand an update you chose to install to Android’s own installer. Android asks you before allowing it. The Google Play version does not ask for it, because Google Play installs its updates. |
| Storage (older versions of Android) | To save downloads to the Download folder on versions of Android that need it. |
The app reads photos, videos and files on the phone only when you choose them to upload, through Android’s own picker, or when you share them to Basalt from another app.
8. This website
For this website, Refora Technologies is responsible for the data described here. It is kept to what the site needs to work, and to counting visits.
- Hosting. The site is served by Netlify, which receives your IP address and the pages you ask for in order to deliver them, and keeps them in its server logs for a short time, under Netlify’s privacy policy.
- Analytics. This website uses Google Analytics to count visits and see which pages are read. It sets cookies in your browser and receives details such as your browser, device type, approximate location and the pages you visit, which Google processes under its privacy policy. It is not used for advertising, and we see only totals, never who you are. To opt out, choose Cookies at the foot of any page, then Don’t count me; your choice is remembered in your browser. Browser add-ons that block analytics work too.
- No advertising. This site shows no ads and loads no advertising or social media trackers.
-
The version number. To show the latest version and file sizes, your browser asks
api.github.comonce per visit. GitHub sees your IP address, as with any request. The answer is kept in your browser’s session storage until you close the tab, and is not a cookie. - Docs search. Searching the docs loads a list of the docs’ contents from this website, and searches it in your browser. What you type is not sent anywhere.
- Downloads. The download buttons go through this website, which sends your browser on to the file on GitHub’s servers. The file is downloaded from GitHub, under GitHub’s privacy statement.
- Email. If you write to us, we use your message and address only to reply, and keep them no longer than needed for that.
9. Your choices and rights
Because the apps keep your data on your own devices, it is entirely under your control. You can delete any of it: remove a profile or a device from the host, delete the host’s folder (section 3), clear the Android app’s storage, or uninstall the apps. Refora Technologies holds no data about you from the apps, so there is none for us to access, correct, export or delete.
For this website, you can opt out of analytics at any time, as above, and delete its cookies in your browser. If you have written to us by email and want that correspondence deleted, ask and we will. Depending on where you live, you may also have the right to complain to your data protection authority.
10. Children
Basalt collects nothing from anyone, so there is nothing to handle differently for children. Parents may want to give children their own profile, or a read-only device.
11. Changes to this policy
If this policy changes, the new version appears on this page with a new date at the top. A change that affects what the apps send anywhere is also noted in that version’s release notes.
12. Contact
Questions about this policy, or about anything Basalt does, are welcome.
- Email reforatech@gmail.com
- Open an issue on GitHub
- reforatech.com
See also the Terms of Use, which cover the licence, your content, and the open-source components Basalt is built on.