Privacy policy
Last updated 18 November 2026
Oversample is a bat call analysis app. It is a web app at app.oversample.com, a desktop app and an Android app.
This policy covers the web app, the desktop app, the Android app, the website oversample.com and the Oversample server (api.oversample.com).
Summary
- If you open or record audio: Oversample analyses the audio on your device. Oversample does not upload it. No account is needed.
- If you search for species or recordings: the search goes to the Oversample server. The server log contains a code made from your IP address. It does not contain the IP address.
- If you use the “Near” filter in Find recordings: “Me” and “Current recording” send a position, rounded to about 11 km, to the Oversample server. “Anywhere” sends no position.
- If you record with “GPS location” on (Android): the app writes the location into the recording file. Anyone you give the file to can read the location.
- If you choose “Sign in with Google”: Oversample saves your annotation files and project files to your own Google Drive. Oversample can see only the files it created there. Sign-in sets cookies.
- In every case: Oversample has no advertising, no tracking scripts and no analytics service from another company. The Oversample server keeps a log of requests, which is also used to count how the app is used.
What stays on your device
Oversample decodes and analyses the audio files you open on your device. Oversample does not upload them to any server. The same is true of microphone recordings, spectrograms, analysis results and species classifier results. The species classifier models run on your device.
Annotations and projects are saved on your device. If you sign in with Google, they are also saved in your Google Drive. See Google Drive sign-in.
The web app
The web app stores the following in your browser, for app.oversample.com only.
- Settings are stored in the browser's localStorage.
- Annotation files, project files, downloaded models and cached Xeno-canto species lists are stored in the browser's private file storage for the site (the Origin Private File System).
- Temporary working copies of audio that the app itself made, such as a denoised copy, are stored in the same private file storage. The app deletes these copies when the file is closed.
- If you enter your own Xeno-canto API key, the key is stored in the browser's localStorage.
The desktop app and the Android app
- The desktop app and the Android app store settings, annotations, recordings, downloaded models and a cache of Xeno-canto downloads in the app's own data folders on the device.
- The desktop app can also save an annotation file (.batm) in the same folder as the audio file that the annotations belong to.
- If you enter your own Xeno-canto API key in the desktop app, the key is stored in a file in the app's configuration folder.
- The Android app saves finished recordings to the phone's shared storage, in a folder named Recordings/Oversample. The Android app also saves exported files to the phone's shared storage.
Removing what is stored
- Clearing the site data for app.oversample.com in your browser removes what the web app stored.
- Uninstalling the Android app, or clearing its data in Android's settings, removes what the Android app stored in its own data folders. Recordings and exports in the phone's shared storage stay until you delete them.
- The desktop app's data stays in the app's data folder and configuration folder until you delete those folders. Their names contain
com.oversample.app. Annotation files saved beside audio files stay until you delete them.
Microphone, USB audio and location
Microphone and USB audio
The app asks for microphone permission only when you start listening or recording. On Android, the app also asks for permission to use a USB audio device at that time. The audio is processed on the device and saved only on the device.
The Android app shows a notification while it records. The Android app can keep recording in the background while that notification is shown.
“GPS location” (Android)
The “GPS location” recording setting is off by default. When it is on, the app reads the phone's location once at the start of each recording. The app writes the latitude and longitude into the metadata of that recording file. Oversample does not send the location anywhere. Anyone you give the file to can read the location.
“Privacy zones” (Android)
In “Privacy zones” you can add the Wi-Fi network that the phone is connected to. While the phone is on one of those networks, the app does not add the location to recordings. The saved network names stay on the phone. Android requires the location permission before an app can read the Wi-Fi network name.
“Include phone model” (Android)
The “Include phone model” setting is on by default. It writes the phone's manufacturer and model into the metadata of each recording file. You can turn it off in Privacy settings.
Location for regions and countries
Some features ask for your location to pick a region or country. Examples are the bat species list for your region and the region for a species classifier. The app works out the country on the device from a built-in map. The app keeps the position in memory until the app is closed. The app does not send the position anywhere, except when you use the “Near” filter in Find recordings.
The “Near” filter in Find recordings
- “Anywhere” is the default. It sends no position.
- “Me” uses your device's location.
- “Current recording” uses the GPS position stored in the open recording file.
For “Me” and “Current recording”, the app rounds the latitude and longitude to one decimal place, which is about 11 km. The app sends the rounded position to the Oversample server as part of the search.
Map links
When a recording has a location, the app shows links to OpenStreetMap and Google Maps. If you click one of these links, that site receives the coordinates. The app sends nothing to these sites unless you click a link.
Google Drive sign-in
Google sign-in is optional. It is available in the web app (app.oversample.com). You start it by choosing “Sign in with Google” in the app's settings.
What sign-in is for
Sign-in saves your annotation files (.batm) and project files (.batproj) to your own Google Drive, so that you can use them on another device.
The permission Oversample asks for
Oversample asks for one permission: https://www.googleapis.com/auth/drive.file. This permission lets Oversample see and change only the files that Oversample itself created in your Drive, or that you open with Oversample. Oversample cannot see, list or read your other Drive files.
What Oversample accesses
- Oversample accesses an “Oversample” folder that the app creates in your Drive, and the annotation files and project files inside that folder.
- Oversample reads the email address and display name of the signed-in Google account from Google Drive. The app shows them so that you can see which account is connected.
How Oversample uses this data
Oversample uses this data only to save, load and update those files, and to show the connected account. Oversample does not use this data for advertising. Oversample does not use this data to train AI or machine learning models. Oversample does not sell this data.
Where this data is stored
- File contents go directly between your browser and Google Drive. File contents do not pass through the Oversample server.
- The email address and display name are shown in the app. They are not sent to the Oversample server.
- The app keeps a record in your browser's storage of the files it last saw in your Drive: Google's ID for each file, the file's version, and a short code made from its contents. The record is labelled with the account's email address. The app uses the record to tell which copy of a file is newer. The record stays in your browser and is replaced when a different account signs in.
How the sign-in works
The Oversample server (api.oversample.com) handles the sign-in with Google. The Oversample server has no user database.
- When you sign in, Google gives the Oversample server a refresh token. A refresh token is a long-lived credential that can be exchanged for short-lived access tokens.
- The server puts the refresh token inside an encrypted cookie and sends the cookie to your browser. The cookie is set by api.oversample.com and lasts 180 days, after which you sign in again. The refresh token is stored only in that cookie. The server keeps no copy.
- While you are signing in, the server sets a second encrypted cookie that lasts at most 10 minutes. It holds the values that let the server check that Google's answer belongs to the sign-in you started.
- When the app needs a new access token, your browser sends the cookie to the Oversample server. The server decrypts the cookie, asks Google for a short-lived access token, and returns the access token to the app.
- The Oversample server does not keep the refresh token or the access token after the request.
- Access tokens are held only in the app's memory.
Sharing
Oversample does not share or transfer Google user data to anyone. The developer does not read your Drive files.
Removing access
- “Sign out” in the app revokes the token with Google and deletes the cookie.
- You can also remove Oversample's access at myaccount.google.com/permissions.
- Files that are already saved stay in the “Oversample” folder in your Drive until you delete them. You can delete that folder in Google Drive at any time.
- If you delete a project in the app while signed in, the app moves that project's file to the trash in your Drive.
The steps are also on their own page: Delete your Oversample account and data.
Google API Services User Data Policy
Oversample's use and transfer of information received from Google APIs, including Google Workspace scopes, will adhere to the Google API Services User Data Policy, including the Limited Use requirements.
Requests to other services
Every request to another service gives that service your IP address and the usual browser details, such as the browser type. Oversample does not control what those services log.
- GitHub Pages. GitHub Pages hosts oversample.com, app.oversample.com and archive.oversample.com (demo recordings). GitHub receives your IP address when you load them. The web app loads the list of demo recordings when it starts.
- jsDelivr. If archive.oversample.com fails, the app loads demo recordings from jsDelivr (cdn.jsdelivr.net) instead.
- Xeno-canto, with your own API key. Searches and audio downloads go from your device directly to xeno-canto.org, and include your key.
- Xeno-canto, without a key. You can choose to use the Oversample server instead. The Oversample server then makes the request to Xeno-canto with its own key, and Xeno-canto does not see your IP address.
- Searches that use the Oversample server. Species name search, country lists and Find recordings use the Oversample server, with or without your own key. Species lists are loaded from the Oversample server when it has them. These requests contain what you search for, the filters you choose, and your browser's language list. The language list is used to show species names in your language.
- Other collections in Find recordings. Find recordings also lists recordings from other collections. When you open one of these recordings, the audio is downloaded from Xeno-canto, from archive.org directly, or through the Oversample server from the host that holds the file (for example iNaturalist or Observation.org).
- Wikimedia Commons. If you search for or load a recording from Wikimedia Commons or Wikipedia, the app sends the request directly to Wikimedia's servers (commons.wikimedia.org, wikipedia.org, upload.wikimedia.org).
- Hugging Face. When you download a species classifier (BirdNET, BattyBirdNET or Perch) in Call detection, or the denoiser model for Denoised copy, the files are downloaded from Hugging Face (huggingface.co). Small label files and region files for a classifier are downloaded when you run the classifier. Your audio is not sent. The models run on your device.
- Links to other sites. The app has links to Xeno-canto pages, licence pages and reference sources for the bat book. These links send nothing until you click them.
The Oversample server and its logs
What the server logs
The Oversample server writes one log line for each request. The log line contains:
- the time of the request;
- the path requested, without the search text or other parameters. The path of an audio request contains the number of the recording, and the path of a species list request contains the group, such as bats;
- the response status and size;
- how long the request took;
- a 12-character code that the server makes by hashing your IP address together with a secret value.
The IP address itself is not written to the log. The same IP address gives the same code, so requests from one address can be linked to each other in the log.
When the server has to fetch a Xeno-canto search from Xeno-canto, because the search was not already cached, the server also logs the search text in a separate line.
The logs are kept with no set end date.
What the server keeps apart from logs
- The server keeps IP addresses in memory for a short time, to limit how many requests one address can make. These IP addresses are not written to disk.
- The server caches Xeno-canto search results for 24 hours. The server caches audio files until the cache is full. These caches hold data from Xeno-canto and the other collections, and are not linked to who asked for it.
What the server passes on
The server does not pass your IP address on to Xeno-canto or to other hosts that it fetches from.
How the logs are used
The logs are used to keep the server running, to stop abuse, and to count how the app is used, such as how many searches are made and which recordings are asked for most. The logs are not shared.
Where the server runs
The server runs on a virtual machine at Oracle Cloud.
Cookies, analytics and ads
- oversample.com and the app set no cookies, except the Google sign-in cookies described in Google Drive sign-in. Those cookies exist only if you sign in with Google.
- Oversample has no tracking scripts, no advertising, no crash reporting service and no analytics service from another company. Usage is counted only from the server logs described above.
- The app's scripts are served from the app's own site, not from third-party hosts.
Your choices
- You can use Oversample without signing in, without a Xeno-canto key, and without giving microphone or location permission. The features that need them will not work.
- You can turn “GPS location” and “Include phone model” on or off in the Android app's settings.
- You can leave the “Near” filter on “Anywhere” to send no position.
- You can sign out of Google in the app, or remove Oversample's access at myaccount.google.com/permissions. You can delete the “Oversample” folder in Google Drive.
- You can remove a saved Xeno-canto key in the app.
- You can delete what the app stored on your device. See What stays on your device.
- You can ask what the server log holds about you, or ask for it to be deleted. See Contact. The log holds only the code made from your IP address, so the developer needs the IP address you had at the time to find your log lines.
Changes to this policy
Changes are published on this page with a new “Last updated” date. The history of this page is public at github.com/pengowray/oversample.com.
If the way Oversample uses Google user data changes, the app will ask you to agree again before it uses the data in the new way.
Contact
Oversample is made by Pengo Wray.
For privacy questions and requests, email privacy@oversample.com.
You can also open an issue at github.com/pengowray/oversample/issues. Issues are public, so do not put private details in an issue.