What Rill reads, and what never leaves your phone.

Rill is a home screen. It shows the apps on your phone, your notifications, your next calendar events, the weather and what is playing. This page says exactly what it reads to do that, what leaves the phone, and what does not. It is written to be checked against the code.

Rill is published by Bilco Works, Calgary, Canada.

There are two builds of Rill. The store build is the one on Google Play. The personal build is a private, sideloaded build for the developer's own phone and is not distributed. Where they differ it is said below; everything else applies to both.

Rill has no accounts, no analytics, no advertising, no crash reporting service and no servers of its own that the store build talks to.

What Rill reads, and why

What	Why	Stays on the phone?
The list of installed apps, their names and icons	It is a launcher: this is the list.	Yes.
Which apps you open from Rill, and when	The "recently opened" section, and the order of your favourites.	Yes, in Rill's own storage.
Notifications (with notification access, which you grant once)	To show each notification under the app that sent it, and to dismiss or open it from there. Also how Rill knows what is playing, for the media row.	Yes. Notifications are read from the system and drawn on screen; Rill keeps no copy.
Calendar (with the calendar permission)	The next two events of the coming day, under the clock. Titles, start times and whether an event is all-day (all-day events are skipped).	Yes.
Approximate location (with the location permission)	The weather. Rill uses the phone's *last known* coarse location and never asks for a fresh fix.	No — see below.
A photo you pick for a theme, or a font you import	To draw it behind the list, or to letter the list with it.	Yes. A copy is kept in Rill's private storage; deleting the theme or the font deletes the copy.
A data line you add under the date (Rill Collection)	A countdown or a fixed line stays on the phone. A Home Assistant line asks the Home Assistant server *you* typed in for one entity's state, on every return to the home screen, using the access token *you* typed in.	Countdown and text lines: yes. A Home Assistant line: no — see below.
A widget you add to the home list	Rill asks the system to draw that app's own widget in the space you gave it, by an id the system issued. Rill does not read what the widget shows, and cannot - the drawing is done by the system on the providing app's behalf.	Yes. Rill stores only the id and the height.
Your settings	To remember them.	Yes, unless you export them yourself.
A crash log, if Rill ever crashes	So a crash can be looked at from Settings.	Yes.

Every permission is optional. Rill explains what it will read before it asks, and a refused permission simply means that part of the header stays empty.

What leaves the phone

Weather. When you have allowed location, Rill sends a latitude and longitude to Open-Meteo (api.open-meteo.com) to fetch the forecast, over HTTPS. Rill sends nothing else anywhere on its own; the one other thing that can leave the phone is a data line you set up yourself, described next. Open-Meteo's own policy is at https://open-meteo.com/en/terms. Rill sends no account or device identifier with the request and keeps no record of where you were.

Purchases (store build). Unlocking the Rill Collection goes through Google Play Billing. Rill asks Google Play whether the Collection is owned and shows the price Play reports; the purchase itself, and any personal data involved in it, is handled by Google Play under Google's terms. Rill receives no name, email or payment details.

A Home Assistant line (Rill Collection). If you add one, Rill sends a request for the entity you named, carrying the long-lived access token you typed, to the Home Assistant address you typed - over HTTPS only, and to no other server. It is your server, your token and your address; Rill stores the token in its private storage, never logs it, and sends it nowhere else. Removing the line removes the token. A settings backup you export yourself ("Save to a file") contains your lines, token included - treat that file as you would the token. Countdown and text lines never leave the phone.

Nothing else. No app list, no notification, no calendar entry, no photo and no font ever leaves the phone.

The personal build only

The personal build is not on any store. In addition to the above it:

• checks a private update server for new versions and downloads them from it;
• fetches a summary of the developer's own investment account from that same server,

identified by a key typed into Settings.

Neither of these exists in the store build; the code for them is not compiled into it.

Storage and deletion

Everything Rill keeps is in its private app storage on the phone. Uninstalling Rill deletes all of it. There is nothing to delete anywhere else, because nothing is kept anywhere else.

Children

Rill is a general-purpose launcher and is not directed at children.

Changes and contact

This policy changes only when what the app reads or sends changes, and the change will be described here. Questions: [email protected].