Privacy policy
Last updated: 20 October 2026 · applies to the Blip Android app and https://goblip.co
Blip has no ads, no analytics and no trackers. Your library lives on your device. The only things that ever leave it are the lookups that fetch box art, game details and achievement progress, whatever you go to your own RomM server for, and — only if you sign in to it — the game saves you sync with Blip Cloud. All of it is described below, in full.
What Blip stores on your device
- Your library: the file and folder names of the games you point Blip at, the metadata and artwork it fetches for them, your favourites, your play history and your per-game choices.
- Your settings: theme, layout, controls and the rest.
- Optional credentials you enter: your RetroAchievements username and Web API key, your ScreenScraper username and password, your SteamGridDB API key, the device token your RomM server issued when you approved the pairing, and the device token Blip Cloud issues when you sign in. They are stored on the device and used only to talk to those services on your behalf.
None of this is sent to us. The one thing of yours our own servers ever hold is what you sync with Blip Cloud, described in its own section below, and nothing reaches them until you sign in. This website is a static page that sets no cookies and runs no analytics.
What leaves your device, and where it goes
When Blip fetches artwork, game details or achievements, it queries these services directly from your device. A query carries the game’s title and platform — never your files, and never anything about you beyond what any internet request carries (your IP address, which each service receives and handles under its own policy). A service that needs credentials is never contacted until you have connected it:
- libretro thumbnails — box art, no account involved (policy).
- TheGamesDB — game details and box art (site).
- IGDB, a Twitch service — game details and artwork (policy).
- ScreenScraper — game details and regional box scans, queried with the username and password of the free account you connected (terms).
- SteamGridDB — posters, heroes and logos, queried with the API key you provided (policy).
- PlayMatch, by RetroRealm — SteamGridDB artwork without an API key, so it needs no credentials of yours (site).
- RetroAchievements — your achievement progress, queried with the username and key you provided (policy). Blip only reads it; it never writes anything back to your account.
- Your own RomM server, if you paired one — a machine of yours, at an address you typed, reached with a device token you approved in its web interface. Your RomM password never touches Blip.
Nothing else leaves the device. Blip never uploads your game files, your app list or your settings anywhere, and your library stays on the device: only the titles of the games whose saves you sync reach Blip Cloud.
Blip Cloud
Blip Cloud syncs your game saves between your handhelds. It is optional and in testing: nothing is sent to it until you sign in from Settings › Cloud, and the app works in full without it. These are our own servers, so this section is about data we hold.
- Signing in. With Google, your device sends our server a Google ID token once; we verify it and keep Google’s id for your account and the email address Google says is yours. With an email address, we send a six-digit code to it and keep the address. Either way the server then issues this device a token of its own, which is what the app uses from then on; your Google password never touches Blip, and Blip stores no password at all.
- What we store. Your email address; a name and a model for each device you sign in on (what the devices list shows), and the app version it runs; the saves you sync, with up to ten versions of each; what a save says about itself — its own title and a small picture, the icon the console wrote into it or, failing that, a thumbnail of the game’s cover; and, for each save, the game’s title, its platform and an identifier of the dump the save belongs to (a checksum of the ROM file, or the serial or title id read from it). Never the ROM itself, never your library, never your settings.
- What it is used for. Syncing those saves between your devices and showing them to you, in the app and at cloud.goblip.co. Nothing else: it is not sold, not shared and not used to profile you.
- Where it lives. On Cloudflare’s infrastructure (Workers, R2 and D1), under Cloudflare’s privacy policy; the sign-in code is emailed through Cloudflare’s email service. Everything travels over TLS. No other company processes it.
- How long. As long as your account exists. Each save keeps its last ten versions and older ones are deleted as new ones arrive; a save you delete, and an account you delete, are erased with every version.
- Your devices. The device token is stored on the device, excluded from Android’s cloud backup and from device-to-device transfer, so a new handheld signs in as itself. Signing out, or revoking a device from another one, invalidates that device’s token and nothing else.
Purchases
The Pro unlock is a one-time purchase handled entirely by Google Play. Blip never sees your payment details; it only learns from Play whether the unlock is owned, and caches that answer on the device so Pro works offline. Payments are governed by Google’s privacy policy.
Backups
If you use Android’s own backup, your library (favourites, play history, fetched metadata) is included so a new device can restore it. Your RetroAchievements, ScreenScraper and SteamGridDB credentials and your RomM device token are excluded from cloud backups on purpose; they only move in a direct device-to-device transfer, and otherwise you re-enter them. The Blip Cloud device token is excluded from both: the new device signs in on its own.
Permissions Blip asks for
- Folder access: you pick each game folder yourself through Android’s file picker; Blip can read only what you granted, and only reads file names.
- Installed app list: Blip is a launcher — it lists your apps to show them and to find your emulators. The list is displayed on your screen and never transmitted.
- Internet: the lookups described above and Blip Cloud, nothing else.
- Uninstall requests: the app drawer can ask Android to uninstall an app; Android shows its own confirmation.
- Notifications: so a library scan, an artwork sweep or a ROM download can show its progress while you are doing something else. The work runs whether or not you allow them — refusing only hides the progress bar.
- Foreground service: so a ROM download runs to the end in one pass instead of being stopped at Android’s limit for background work.
Two more are optional special accesses, granted by hand in Android’s own settings and never at runtime. Both exist for the game companion on a dual-screen handheld, and it works without either:
- Usage access: lets the companion notice that you left the game without coming back to Blip first, so it can put the game’s card away. Blip only asks which app is in the foreground, only while a game it launched is open, and that answer is never stored and never sent anywhere.
- Modify system settings: lets the companion’s brightness slider change the brightness of the screen above. Refused, the slider stays disabled and says why.
Deleting your data
Everything Blip stores on the device goes with the app: uninstalling it deletes it. Disconnecting RetroAchievements or RomM, or revoking the SteamGridDB key in Settings, deletes those credentials immediately. Data held by the third-party services you connected — your RetroAchievements account, for instance — is theirs to delete under their own policies.
Your Blip Cloud account is deleted from the app (Settings › Cloud › Delete account) or from cloud.goblip.co, without contacting anyone. Every device is signed out at once and every save, version, picture and device record is erased in the background; the saves on your devices are not touched. Signing out deletes nothing in the cloud.
Children
Blip is a general-audience utility and does not knowingly collect personal information from children. A Blip Cloud account holds an email address and nothing more about the person; one made by a child is deleted on request through the contact below.
Changes and contact
If Blip ever gains a feature that handles data differently, this page changes first and the “last updated” date moves. Questions go to the developer contact on Blip’s Google Play listing.