Data usage

What Libling stores. Your email address (for signing in), the places you create (libraries, rooms, bookcases, shelves), the items catalogued there, and the photos you take. Photos live in a private storage bucket in the EU (Supabase); after a shelf photo is read, only a downscaled copy is kept. Nothing is public: only you, and people you explicitly share a library with by email, can see your catalogue.

What leaves the service, and why. Two things only. A photo you scan is sent to Google's Gemini API to read the spines — that is the product's core function. And when Liblinglooks an item up, the title and author (never your photos, never your email) are sent to the open catalogues: Open Library, Libris, Google Books, MusicBrainz, Discogs, TMDB, BoardGameGeek, and — for records — Spotify, to find the exact album link.

A library can remember where it is, but only if you press the button that asks your device — never on page load, and never from a photo (resizing strips the GPS tag before anything is uploaded). What is stored is rounded to about 110 metres, enough to tell one home from another and too coarse to point at a door. Anyone the library is shared with can see it, and “Forget this location” removes it for good.

What Libling does not do. No advertising, no analytics trackers, no selling or sharing of your data with anyone. There are no third-party cookies; the only cookies are the ones that keep you signed in.

Deleting. Deleting a photo, item, or library removes it and its files permanently. Deleting everything you have created removes all of your content; if you also want the account itself gone, use the contact route you signed up through.

Last updated: September 2026.