← goblip.co

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

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:

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.

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

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:

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.