Booklight privacy policy
The short version
Booklight has no account and no ads, and Meridian11 receives nothing from it. It contains one library of Google’s, which reports how it is used to Google (see “Answers on this device”). Three more things can leave your device through Booklight, each only if you set it up yourself: search suggestions, which are off until you turn them on, and flight and Spotify lookups, which need a key of your own. Booklight can read the list of your calendars and add an event you save, each only if you allow it in its window; nothing of your calendar leaves the device through Booklight.
Permissions and what they are for
| Permission | What Booklight uses it for |
|---|---|
| Internet | Search suggestions from the search engine you chose, only while suggestions are on; flight and Spotify lookups, only with your own keys; and the usage reports of Google’s library |
| Uninstalling apps | The Uninstall action on an app’s row; Android asks you before it removes anything |
| Alarms and timers | Setting the timers, alarms and reminders you type in the Clock app |
| Modify system settings (optional) | Changing the screen brightness; it does nothing until you switch this on for Booklight in Android’s settings |
| Calendar (read) (optional) | The list of your calendars (their names and colours), to put an event on one by its name; never an event. Android asks you, and only when you press Allow… in the Booklight window |
| Calendar (add events) (optional) | Adding the one event you save from the panel, only with “Save events without opening Calendar” switched on in the Booklight window |
| On-device AI service | From Google’s library: connecting to the system’s own on-device model, which answers your prompts |
| Network state | From Google’s library: seeing whether the network is up before it sends its usage report |
Search suggestions
Search suggestions are off until you turn them on, from the card under the search field or in the Booklight window › Web search. You can turn them off there at any time. With suggestions off, nothing you type leaves your device.
While they are on, what you type is sent over HTTPS to the search engine you chose, to get suggested searches: Google by default, or DuckDuckGo, Bing, Brave Search or Ecosia if you change it.
- Sent: the text in the search field when you pause typing, if it is 2 to 80 characters and reads as words.
- Never sent: sums, web and email addresses, an app’s own address, text without letters, and anything typed after a keyword or with an app in the field (a note, a mail, a search of one site or of one app, a song to play).
- An app’s name followed by other words, typed in one go (“netflix severance”), is a web search like any other and is sent, until you have picked that app’s own row for such a text. From then on the app comes first for words after its name and they are not sent; picking the web’s row twice running makes it a web search again.
- The request carries no cookies, no account, no advertising or device identifier and no location, and it names the app as “Booklight” instead of your device model.
- Like any internet request, it reaches the search engine from your device’s internet address; that search engine’s own privacy policy applies to how it handles the request.
The suggestions that come back are shown as rows and kept only in memory; they are never saved. Booklight has no server of its own, so Meridian11 never receives what you type.
Flights
Nothing is sent unless you put in a key of your own. A flight number you type (“LH455”) is read on the device: Booklight carries a table of airlines, names the airline, and Enter opens the flight’s page in your browser.
If you put a key of your own for AirLabs (airlabs.co, a flight data service) into the Booklight window › Labs › Flights, the row also shows the flight’s times, gate and status. For that, the flight number and your key are sent over HTTPS to airlabs.co, and nothing else is.
- When: once, a moment after you stop typing, for text that reads as a flight number and as little else; after the keyword “flight”; and only when you move to its row for text that is usually something else (“ps5”) or for a flight number found in text you copied or another app handed over.
- A flight you pinned is asked about again while its small window is open, until it has landed: every half hour from three hours before it leaves, every three hours before that, sooner after a lookup that got no answer, and not at all while it is only a plan from the timetable more than ten hours off.
- The request carries no cookies and no identifiers. Like any internet request it shows AirLabs your internet address, and AirLabs can tie the lookups to the account the key belongs to; its own privacy policy applies.
- The answer is kept in memory for two minutes (that a number is not known, for an hour) and written nowhere.
The key is a file in Booklight’s private app storage; it is not part of your backup and goes to AirLabs only. Take it out in the same place and nothing is sent again. Booklight ships no key, and Meridian11 sees neither yours nor your lookups.
Spotify
Nothing is sent unless you put in a key of your own. Without a key, Spotify’s row has Search: Enter hands your text to the Spotify app on your device, which shows its search results, and Booklight itself sends nothing.
If you put a key of your own for Spotify’s Web API (a client ID and its secret, from developer.spotify.com) into the Booklight window › Labs, Spotify’s row also has Play, and Booklight looks the name up so that Spotify can play it.
- Sent, over HTTPS to api.spotify.com: the text you type while Spotify stands in the field and Play is armed (without the app’s name) and the country your device is set to, with a token Booklight gets by sending your key to accounts.spotify.com. Nothing else is sent.
- When: each time you pause typing there for about half a second, the text as it stands then (so a slow hand sends the start of a name before the whole of it), while Play is armed and Spotify is in the field because you chose it. Where Spotify is there only because it comes first of several music apps, for a single letter, or while another row stands above Spotify’s, nothing is sent until you press Enter on Play. Where Spotify’s row stands under another music app’s, it is asked when you move to that row.
- Never sent: anything while Search is armed, while you are typing without a pause, or text another app handed over.
- An album takes a second request (for its first song), and so does an artist (for a song of their own).
- The token is the key’s, not yours as a listener: nothing of your Spotify account (your playlists, what you listen to) is read.
- The request carries no cookies and no identifiers. Like any internet request it shows Spotify your internet address, and Spotify can tie the lookups to the account the key belongs to; its own privacy policy applies.
- What Spotify found is kept in memory for five minutes, and the token until it runs out (an hour); neither is written anywhere. If you make a recipe step of a song that was found, the song’s link is kept with the recipe.
The key is a file in Booklight’s private app storage; it is not part of your backup and goes to Spotify only. Take it out in the same place and nothing is sent again. Booklight ships no key, and Meridian11 sees neither yours nor your lookups.
Calendar events
An event you type (“event dinner tomorrow 7pm”, or a sentence such as “Add dinner with Sam tomorrow at 7pm to the Team calendar”) is read on the device, by Booklight’s own rules. Where those rules cannot tell the title from the place, the model on the device (see “Answers on this device”) is asked which words are which, a moment after you stop typing. It works out no date, and what it says is shown only if every word of it is one you typed.
Enter hands the event to a calendar app: its title, its time and its place.
- Where the event names no calendar, that is Android’s own request to add an event, to whichever calendar app there is.
- Where there is a calendar to name, it is a calendar link (https://calendar.google.com/calendar/render?…) with that calendar’s address in it (for most calendars an email address), given to Google’s Calendar app and to no other.
- The calendar app opens its editor, filled in, and you save the event there, or you don’t. Booklight itself opens no connection for it.
The list of your calendars is read only if you allow it, in the Booklight window: Privacy › Calendars, “New events go to” under Results, or the switch “Save events without opening Calendar”, which asks for both, to read the list and to add events. Android has one question for this and asks it about “your calendar” as a whole; what Booklight asks the system for is the list of calendars and nothing else. Where you have already allowed the list, Android does not ask again when you switch saving on: its one question was for the calendar as a whole. The switch stays off until you press it.
- Read: the list of the calendars of your Google accounts. For each its name, its colour, the id the system has for it, its owner’s address, the account it belongs to, whether it is that account’s own, and whether events can be added to it.
- Never read: an event. Nothing in Booklight reads one.
- The list is kept in memory only and is not written to Booklight’s files. Nothing of it leaves the device through Booklight.
Booklight saves an event itself only if you switch that on (“Save events without opening Calendar”, the Booklight window › Results). Then Enter, or a click, on Save writes the one event the row shows, with its calendar’s own default reminder: into the calendar you named; with none named, into the one chosen under “New events go to”; with none chosen, into your account’s own calendar. The row shows which before you press Enter.
- Only where nothing of when it is is a guess: the day and the time were both read from what you typed, or the day with “all day”, or a range of days.
- Never a line that asks for a repeat, one that says “next Tuesday”, one with a date that had just passed, one that names a calendar which is none of yours, or one typed without the keyword that begins with schedule, put, book or plan. Any such event opens in a calendar app, filled in, as above.
- An event that was saved is an ordinary event of your calendar: the account the calendar belongs to syncs it, as it does every event, under its own terms. Booklight sends it nowhere, never changes or removes an event, and keeps no copy of one.
Kept in Booklight’s settings: whether the switch is on; that Android’s question has been answered on this device; and, once you choose a calendar under “New events go to”, that calendar’s owner’s address (for most calendars an email address). The settings are in your own Android backup, and so that address is too. The switch and the answer are believed only on the device they were set on: settings that arrive with a backup never have saving on.
A time you convert (“3pm sfo in berlin”) can be added to your calendar with Add…: that opens your calendar app at that time, as above.
A line that reads as an event is not sent for search suggestions.
Answers on this device
A prompt (“fix …”, “sum”, “tasks”, or one of your own) is answered by the system’s own model, Gemini Nano, which Android keeps and runs on the device. Booklight reaches it through Google’s ML Kit library. Your text and the answer stay on the device: they are not sent to Meridian11, and the system’s service does not keep them.
That library, like all of ML Kit, reports how it is used to Google:
- Reported: the device model and Android version, Booklight’s name and version, an identifier made for this installation, which feature ran, how long it took, how large the input and the answer were, and error codes.
- Not reported: the text you typed, and the answer.
- It sends this in the background when the network allows. Google’s privacy policy applies to what Google receives.
Booklight cannot switch that off in this version; if you never use a prompt, the model is never asked. (The row that plays in a music app has one such question behind its arrow, “Which song is this?”: the model is given the name you typed there when you press Enter on it, and only then.) Where the device has no such model, a prompt opens the Gemini app with your text in its prompt instead, and you send it there or you don’t.
What stays on your device
Booklight remembers which result you picked for the text you typed, so your usual choice comes first: the result (for an app, its name in Android), the text, a count and a time. It also keeps your settings, your own links, snippets and recipes, and the emoji you picked lately. These are files in Booklight’s private app storage.
With what it learns it also keeps, for an app whose own search row you picked after typing its name and some words, that this app comes before the web for such a text.
The Booklight window › What Booklight keeps › Forget everything clears what it has learned.
If you turn on Show your usual, the empty panel shows the two things you run most from Booklight and the one you ran last. This uses the same record; the only new things kept are the switch, which two things had the first two rows last time, and the list of things you asked not to be suggested.
Notes you jot down go into files (Notes.md, Todo.md, a file per day if you ask for one) in a folder you choose once. Booklight reads and writes in that folder only, and reads it only when you search your notes or your tasks, or while your open tasks are pinned (“pin todo”). Files you make with “new file” go to your Documents folder, and QR codes you save go to Downloads.
Units, sums and time zones are worked out on the device.
The pinned window shows what you pinned until you close it; a pinned line is kept nowhere else.
If you have Android backup turned on, Android may include the files in Booklight’s app storage in your device backup, in your own Google account. That backup is managed by Android and your account; Meridian11 can’t see it. Uninstalling Booklight deletes its data from the device.
Other apps and their commands
Booklight reads what your installed apps declare they offer (their shortcuts) from their own packages. It starts one only when you press Enter on its row, and those apps never see what you type.
Choosing a web search, a suggestion or a typed address opens it in your browser, and choosing an app or a settings page opens that app. A mail, a calendar event, a note for Keep, a timer or alarm, or a question for Gemini is handed to the app that opens: your mail app, your calendar, the Clock, Gemini. Booklight sends none of it anywhere itself, and a mail or a Gemini question is only filled in: you send it there, or you don’t. From there, the browser, website or app works under its own terms.
The clipboard and text from other apps
When you open Booklight within two minutes of copying something, it asks Android what kind of thing was copied and how old it is (text, and whether the system found a link, a date, a phone number or a mail address in it) and shows one line under the empty field. What was copied is not read for that, and Android shows no “pasted” message. The line can be turned off in the Booklight window › What you copied.
What was copied is read when you press Tab or Down on that line or click it (Tab on the empty field also opens a fresh copy when the line is switched off), or when you ask for it (“clip”, “tr”, “tasks” or a prompt with nothing typed, or a link of yours that uses {clipboard}). It is given to the model on the device when you press Enter on one of the model’s rows, or a moment after you stop typing under a prompt’s keyword or “tr” with no text of your own. Something a password manager marked as private is never read and gets no line.
Text that another app hands to Booklight, from its selection menu or its share sheet, is shown in the panel and forgotten when the panel closes.
Booklight has no accessibility service, no notification access and no access to your contacts or location. Nothing of Booklight’s own runs in the background; the library’s usage report is a short job the system runs. A pinned flight’s window is on your screen, not in the background: it asks only while it is there.
Google Play
If you install Booklight from Google Play, Google Play gives Meridian11 statistics such as install counts, and reports of crashes and freezes from people who chose to share them with app developers. These come from Google Play, not from Booklight; they don’t identify you, and Google’s privacy policy covers them.
Children
Booklight is meant for people 18 and over, as Google’s terms for the on-device model ask, and isn’t directed at children. Meridian11 receives nothing from anyone who uses it.
Changes and contact
Changes to this policy are published on this page, with a new date at the top. Booklight's code is public at github.com/Meridian11Labs/booklight. Questions: email meridian11labs@gmail.com.