Talo Launcher privacy policy

Last updated 8 November 2026, for version 1.0.43.

Talo Launcher is a home screen for Android. It has no account, no analytics, and no network permission: the app cannot reach the internet, and nothing it holds is sent anywhere. Everything below stays on the phone and is deleted when the app is uninstalled, except a picture you choose to save to your pictures, which is yours (see "Pictures of a page's background").

This same text is in the app, under Settings ▸ System ▸ Privacy ▸ Privacy policy and Settings ▸ System ▸ About.

Who is responsible

Talo Launcher is made by Darsery, in Croatia, which is responsible for this policy. For anything about privacy, write to support@darsery.hr.

What the app keeps, and where

Your layout and settings — pages, widgets, folders, colours, icon style and every preference, and how often and at what hours you open each app from the launcher (used to sort "most used", to fill the "Suggested" row, and, a few days after the welcome, to offer the apps you open most for the first row of home). Kept in the app's own storage. Included in Android's cloud backup and in a phone-to-phone transfer, if you have those turned on in Android's settings, and in any backup file you export yourself. "Reset usage counts" in Settings ▸ Apps and search ▸ App lists clears the counts and the hours together.

What you write and set up on the home screen — the note widget's text, the countdown's name and day, your focuses (their names, hours and which apps each hides), saved background presets, and which apps pause before opening. Kept with your layout and settings, and backed up the same way. While you undo a change, a copy of your settings is held in memory for a few seconds and then let go; it is never written anywhere.

The time machine's snapshots — copies of how your layout and settings stood, so Settings ▸ System ▸ Share and backup ▸ Time machine can show them, go back to them, or bring back one page, widget or part from them: one for each day they changed; one just before each change you can undo, and one when you leave Settings having changed something, each named for what changed ("Battery removed", "changes in Settings: Look"), kept 7 days; one before a restore, a reset or a trip back; and the ones you pin and name, kept until you unpin or delete them. Launch counts and other records of use are left out of all of them. Kept in a folder of the app's own, excluded from Android's cloud backup, from phone-to-phone transfer and from exported backups, and gone when the app is uninstalled. Photos and other apps' widgets a snapshot still names are kept as long as it is, so going back brings them too. A pinned layout you put on a schedule is switched to and from by the launcher itself, at the times you set, the next time home is shown; the schedule is kept on this phone only. "Share" opens Share and import (below) for a snapshot, which goes only where you send it. The days and the kept ones stay for as long as you choose in Settings ▸ System ▸ Share and backup ▸ Keep history for: a week, a month (the default) or three months. "Forget history" there deletes every snapshot but your pinned layouts at once.

What else you set up — the daily limits you give apps, the shapes you draw for apps (each a line of 32 points, nothing else), the notifications you pin to home (Android's key for each, which names the app and the notification's number, and is let go when the notification goes), and the bedside clock's hours. Kept with your layout and settings, and backed up the same way.

Icons you picked — pictures you chose for apps yourself. Kept in the app's own storage, and included in backup files you export, so a restore puts them back.

Page photos — pictures you choose as a page's background. Android's photo picker hands over only the picture you pick; the launcher never asks to read your photos. A copy, scaled to the screen, is kept in the app's own storage, included in backup files you export, and deleted when you remove it from the page or remove the page.

Photo frame — pictures you choose for the photo frame widget, through the same photo picker. Copies, scaled to the screen, are kept in the app's own storage and deleted when you remove them in the widget's settings. They are not included in backup files.

Your name on what you share — only if you type one, under Settings ▸ System ▸ Share and backup or in Share. Kept on the phone, not in your home or its backups, and written into what you then share — codes, files and saved wallpapers — so whoever receives it sees who made it. Leave it empty to share without a name. What you bring in can carry someone else's: the launcher shows it, and keeps the name of the theme your look came from, to credit it when you share your look on; you can take that credit off there too.

Themes and trials — the community themes come inside the app, with its updates; nothing is fetched. A theme you try for a day is kept on the phone with how your look was before it, so it can go back; nothing about it leaves the phone. Themes you keep as your own are kept with your settings, and travel in your backups like the rest of the look. "From a photo", in the themes' dice, uses Android's photo picker, which hands over only the picture you pick: its colours are counted on the phone to choose the theme's, and nothing of the picture is kept.

Pictures of a page's background — made only when you tap "Save as a picture" or "Set as wallpaper" in a page's background: the background is drawn on the phone at the screen's size and saved as a PNG in Pictures ▸ Launcher, where your gallery shows it. Like any picture you save, it stays there if the app is uninstalled, and you delete it there. Inside the picture, as text the file format allows, go the background's recipe (its colours, gradient and texture, never its photo) and, if you have given one, your name, so the launcher can bring the background back from the picture. "Set as wallpaper" makes it the wallpaper of the home screen, the lock screen or both, through Android, without saving a copy; or, with "With another app", saves it as above and hands it to the app you pick from Android's list.

What page backgrounds follow — a page can take its colour from the wallpaper, the time of day, the cover of what is playing, the battery level or how far through the day it is, and can move a little as you tilt the phone. All of it is read on the phone while home is showing and none of it is kept: the time of day comes from the clock and time zone, not your location, and the tilt from the motion sensor, which needs no permission and is only listened to while a page that moves is on screen.

Facts about this phone — when the launcher started marking newly installed apps, and when each app arrived, used for the new-app dot. Kept in a file of its own that is excluded from Android's cloud backup, from phone-to-phone transfer and from exported backups: they describe this phone, and carried to another would make every app on it look new.

Clipboard history — the text and pictures you copy or cut, if "Collect copies" is on (it is on by default and can be turned off in Settings ▸ Widgets ▸ Clipboard). Kept in a separate file that is excluded from Android's cloud backup and from phone-to-phone transfer, so what you copy does not travel to Google's servers or to a new phone. It is left out of automatic backup files too, unless you turn on "Include clipboard history" in Settings ▸ System ▸ Share and backup, and out of anything you share unless you tick "Copied items" yourself.

A copy that is a shared code — the text a camera app copies after reading one of the launcher's QR codes — or a recipe (a "Talo setup" or "Talo theme" an AI chat wrote) is recognised as it is picked up, and the launcher asks which of its parts to bring in; nothing else about a copy is looked at for this.

Android only shows the clipboard to the app on screen, so copies are picked up when you return home — the latest one, if you copied several while away. Anything the copying app marks as sensitive, such as a password manager's copy, is skipped. Which app a copy came from is not something Android tells a home screen, and is not recorded.

Problem reports, when you send one — Settings ▸ System ▸ About ▸ Send a problem report writes a short text and hands it to your email app, addressed to the developer; nothing is sent unless you send it there. It says: the launcher's version; the phone's maker, model, Android version and build; whether the launcher is the home app and has notification and usage access; how many pages, widgets of each kind, apps and focuses there are, and the theme; what the setup check finds in counts; how many of the launcher's frames were late since it started, counted in memory only; and the last crash, if there was one. It never names your apps, and contains nothing you typed, copied or wrote.

Share and import — Settings ▸ System ▸ Share and backup ▸ Share asks which parts of your setup to share (the home screen, the look, saved looks, clock, search, app lists, gestures, clipboard settings, your apps' names, icons and hidden or locked lists, and, only in a file, launch counts and copied items) and the name to give them. A QR code holds only the settings of the parts you tick; "Send picture" writes that code, with a small drawing of what it holds, to a file in the app's cache and hands it to the app you choose. "Send file" and "Save to a file" write the ticked parts, with the pictures they use, to a file that goes only where you send or save it. Nothing is sent anywhere by the launcher itself.

Import reads a code from the camera, a picture, a copy or a file. "Scan a code" shows the camera's picture on screen and reads each frame for a code on the phone; frames are never stored or sent, and the camera is on only while that screen is open. A setup too big for one code is shown by the other phone as a series of codes, which the scanner gathers the same way. "Pick a picture" uses Android's photo picker, which hands over only the picture you pick; it is read for a code on the phone and not kept. Before anything changes, the launcher shows what came in and changes only the parts you tick; undo is offered after.

Opening a home screen file — the launcher offers to open its files (JSON) handed to it by another app, such as a home screen shared from another phone. The file is read, its pages are drawn, and nothing is changed unless you tick parts and choose Bring in. Text shared to it, such as an AI chat's answer, is read the same way for a code or a theme recipe, and not kept.

Designing your home with AI — Import ▸ Design your home with AI copies a prompt to the clipboard: the recipe format and examples. Two things can go into it, each only if you tick it first: the names of your apps (not those in the private space), and your setup as it is — your theme, your gestures, and your pages with the names of the apps on them, folder names and the text of your notes and countdowns. Which apps you have hidden, locked or limited never goes in. The prompt always says how tall a page is on your phone and how tall each widget is drawn there, in dp, so the AI can fill a page without overfilling it. Nothing else about you or your phone goes in. Where you paste it is your choice, and that AI's own terms apply there; the launcher itself sends nothing anywhere. A recipe that comes back is read on the phone, apps in it are matched to yours by name, and nothing changes until you choose Bring in. "Copy a fix for the AI" copies only the recipe's own lines Talo could not read and the app names it gave that are not on the phone. Share ▸ Share as text sends what you ticked as a recipe, with the names of the apps on your pages, to the app you choose. A recipe can hide, lock, limit or rename apps and change the gestures, each listed by name before you bring it in; it can never unlock or show again an app you locked or hid.

Commands typed in the search — "note …", "count to …", "focus …" and "go back …" change the launcher's own settings, as their settings screens would. "msg Ana …" looks up the name in your contacts, only if you have allowed contacts for search, and hands the number and your words to your messages app; nothing is sent until you send it there.

Sensors — the bedside clock reads whether the phone is lying flat or standing still, from the motion sensors, which need no permission. They are listened to only while the bedside clock could be showing (on the charger, in its hours), and nothing is kept. The bedside clock also asks Android for your next alarm's time, to show it.

Crash reports — if the app crashes, the stack trace is written to a file inside the app so it can be read afterwards from Settings ▸ System ▸ About. It is never sent anywhere. You can copy it yourself and send it on if you want to report a problem.

Permissions, and what each is for

There is no internet permission. There is no advertising ID, no analytics, and no third-party service of any kind.

How it is kept safe

Everything above is kept in the app's own storage, which Android keeps from every other app, and none of it can leave the phone through the launcher: it has no network permission. Android's cloud backup, where it is on, is Google's and encrypted by Android; the parts named above are kept out of it. Files you export or share go only where you send them.

Your rights, and the GDPR

Everything above is processed on your phone, under your control, and the developer receives none of it, so the developer holds no personal data about you to show you, correct or delete. Clearing the app's storage, or uninstalling it, removes it all.

The one exception is an email you choose to send: a problem report or a question. It is read by the developer only to answer you and to fix what it reports, which is the developer's legitimate interest and what you asked for (GDPR Article 6(1)(b) and (f)). It is kept in the developer's email for no longer than that takes, and at most two years, and is never shared, sold or used for anything else. You can ask at any time to see it or to have it deleted, at the address above. You can also complain to a data protection authority: in Croatia, AZOP (azop.hr), or the one where you live.

Google Play. Installing the app from Google Play, buying Talo Pro, and Android's own crash and usage reports if you have allowed your phone to send them, are between you and Google, under Google's privacy policy. For a purchase, Play Console shows the developer the order (its number, country and price) as Google Play's terms allow, never your payment details; it is used only for refunds and the accounts. From those, the developer sees only Play Console's figures, such as how many phones have the app and anonymous crash reports, never who you are.

Changes to this policy

A changed policy comes with an update to the app, here and at the same address online, with the date at the top changed. Nothing new is ever collected without the policy saying so first.

Questions

Write to support@darsery.hr, or use Settings ▸ System ▸ About ▸ Send a problem report, which opens your email app with a message to the developer, for questions about privacy as much as problems. Nothing is sent unless you send it.

Children

The app collects nothing, so there is nothing collected from anyone of any age.