Privacy Policy
Last updated: 17 October 2026
Morph is an Android launcher with switchable home-screen profiles. This policy explains exactly what it reads on your device, what leaves your device, and what does not.
Morph needs no account, shows no ads, and sells no data. An account is needed only for Morph Pro, the optional subscription. Unless you turn on Morph Remote, a Pro feature that lets an AI assistant control your launcher, almost everything Morph touches stays on your phone.
What stays on your device
Everything in this section stays on your phone. The one exception is Morph Remote: if you sign in to it and agree to its disclosure, the items it names are copied to its server, as described in Morph Remote below.
- Your installed app list. Morph holds the
QUERY_ALL_PACKAGESpermission because a launcher has to know what you have installed in order to show an app drawer, place icons, search in Spotlight, and match icon packs. This list is read on the device and is never transmitted, uploaded, or shared unless you turn on Morph Remote. - Your profiles. Names, wallpapers, icon layouts, widgets, colours and font choices are stored in app-private storage.
- Wallpaper images you choose are copied into app-private storage so Morph can render them.
- Pocket contents. Notes, checklists, links and files you save to Pocket are stored in app-private storage. A Pocket file leaves the device only if you explicitly tap Share, which grants the app you pick a temporary, single-file permission. Morph Remote copies your notes, links and checklists, and only the names of your files, never the files themselves.
- Recent apps used to order Spotlight results, kept per profile.
- Cues. If you link a profile to Do Not Disturb, a schedule, a Bluetooth device, a Wi-Fi network or driving, the days and times you choose, the name and address of that device and the name of that network are stored in app-private storage, and whether Do Not Disturb is on, which paired device is connected, which network you are on, whether Android Auto is connected and whether your phone is in a vehicle are checked on the device to switch profiles. Only the most recent "in a vehicle" or "not in a vehicle" change is kept. None of these readings is ever transmitted; Morph Remote copies only the cues you have set up (for example the network or device name a profile is linked to), never whether they are on. Analytics records only that a cue of a given type was linked or switched a profile, never the device, network, schedule, activity or profile.
Other permissions, and why
| Permission | Why |
|---|---|
QUERY_ALL_PACKAGES | Show your apps in the drawer, on the home screen, and in search. |
READ_SHORTCUTS | Show an app's own shortcuts when you long-press its icon. |
BIND_APPWIDGET | Host the widgets you add to a profile. |
SYSTEM_ALERT_WINDOW | Optional, and off unless you enable it. Used only to keep your own home-screen icons tappable during a brief input freeze some manufacturers introduce after returning home. Morph never draws over other apps. |
ACCESS_NOTIFICATION_POLICY | Optional. Only if you ask a profile to turn on Do Not Disturb when you pick it; Morph turns it back off when you leave, if it was the one that turned it on. |
ACCESS_FINE_LOCATION | Only for Wi-Fi cues. Android shares the name of the Wi-Fi network you are connected to only with apps allowed precise location. Morph reads that name and nothing else: it never requests your position, never tracks where you are, and does not ask for background location. |
ACTIVITY_RECOGNITION | Only for Driving cues. Google Play services on your phone tells Morph when it starts or stops being in a vehicle. Morph uses nothing else from it and sends none of it anywhere. |
POST_NOTIFICATIONS | Optional, and asked for only from the Morph Remote screen. Used to tell you when an assistant connects to Morph, and when something an assistant asked for needs a tap on your phone to finish. |
BLUETOOTH_CONNECT | Only for Bluetooth cues: to list your paired devices and see which one is connected. Morph never scans for devices and does not use it for location. |
Morph Pro and your Morph account (optional)
Morph Pro is an optional subscription, bought through Google Play, that unlocks Pro features (today, Morph Remote and automatic backup). It belongs to your Morph account, so it follows you to a new phone.
- Your Morph account is a Google sign-in, made only when you choose to from the Morph Pro screen. Through Google Firebase Authentication it holds your email address, name, the link to your Google profile photo, a Google-issued account identifier and when you last signed in. Morph uses only the email (to recognise accounts Morph gives Pro to) and the identifier.
- Your subscription. Google Play handles the payment; Morph never sees your card or payment details. Morph receives from Google Play, and keeps, what it needs to know whether you are Pro: the purchase's token, which plan, its status (active, renewing, cancelled, in a payment grace period, ended or refunded) and its renewal or end date. Your account identifier is attached to the purchase so the purchase can be matched to your account.
- Managing it. Cancel or change your plan in Google Play; the Morph Pro screen links there. Refunds follow Google Play's policies.
- Signing out of the account on a phone keeps your account and your subscription, so signing in again restores Pro.
Morph Remote (optional, part of Morph Pro)
Morph Remote lets an AI assistant you choose, such as Claude, read and change your launcher when you ask it to: switch profile, add apps to your home screen, add to a Pocket checklist, and so on. It needs Morph Pro and your Morph account, and it is off until you open it from the profile screen and agree to a disclosure in the app listing what it sends. Nothing below is sent before that. If your Pro subscription ends, Morph Remote stops syncing at once, and what it kept on the server is deleted 30 days later unless you subscribe again.
What it sends, and keeps while you are connected:
- Your Morph account's email, kept with each assistant you connect (see your Morph account).
- Your installed app list: each app's name and its Android package and activity names, personal or work profile, and the installed icon packs and widgets.
- Your profiles: names, the apps on each home screen and where, wallpaper and theme settings (for a photo you picked, only the fact that it is a photo; the photo stays on your phone), widgets, and cues, including the days and times of a schedule and the name of a linked Wi-Fi network or Bluetooth device. The names and addresses of your paired Bluetooth devices are sent too, so an assistant can link one.
- Your Pocket: tab names, notes, links and checklists; for a file, only its name, type and size.
- A change history: each change an assistant asked for, which assistant, when, and whether it was made. Kept for at most 90 days.
- Technical details: a push-notification token (so the server can wake your phone when your assistant asks for a change), the app version, which permissions a cue would need, and whether notifications are allowed.
How it is used. Only to let your assistant answer you and make the changes you ask for. A copy is kept on the server so your assistant can read it while your phone is asleep; your phone stays the source of truth. It is not used for analytics or advertising, and it is not sold.
Your assistant. When you ask your assistant about your launcher, it receives the parts it needs to answer, and it can change what you ask it to. What your assistant does with that is governed by its provider's own privacy policy, for example Anthropic's for Claude. You connect an assistant yourself, from its own settings, and you can disconnect it at any time.
Photos from the web. If you ask your assistant to use a photo from a web address as a wallpaper, your phone downloads it directly from that address. The site sees the request as it would any download; the photo is not sent to Morph's server.
Where it is kept. On servers run for Morph by Cloudflare, sent over HTTPS and encrypted at rest. Google Firebase handles sign-in and the push notifications that wake your phone. Both act as our service providers. See Cloudflare's privacy policy.
Deleting it. Delete account, on the Morph Pro screen, cancels your Pro subscription if you have one (so you are not billed again; there is no refund for the time left), then deletes your Morph account, your subscription record, the server's copy of your phone's data and its change history, and cuts off every assistant you connected, at once. You can do the same without the app at morph-remote-mcp.harjot-oberai.workers.dev/delete-account, by signing in with the same Google account. Disconnect, on the Morph Remote screen, deletes Remote's server data but keeps your account and subscription, so you can connect again. Uninstalling Morph does not reach the server, so delete or disconnect first.
What is collected
Released builds of Morph include Google Firebase (Analytics and Crashlytics) and Mixpanel, and all are enabled.
Usage analytics. Morph records which features you use and when: opening the app, moving through setup, creating and switching profiles, and using the app drawer, search, widgets and Pocket. This is how we tell whether the app works for people — for example, whether setup is too long, or whether a feature is ever found.
Morph Remote's own analytics follow the same rule: that you connected, disconnected or agreed to its disclosure, and which kind of change an assistant made and whether it worked. Never what was changed.
These records describe that something happened, never what. They never include app or package names, profile names, wallpaper images, search terms, or any Pocket text, links or files. Where a record needs a detail to be useful it is a category, not content — for example that a Pocket item was a note rather than a file, never the note itself. Counts are recorded as ranges rather than exact numbers. The one exception is feedback you choose to send us, described next.
Feedback you send. Morph has a feedback form, reached from the icon beside the question mark on the profile screen. If you use it, the rating you pick and anything you type are sent to our analytics provider so we can read them. This is the only place Morph transmits something you wrote. It is entirely optional — the form is never shown unprompted, nothing is sent unless you press send, and the app works identically if you never touch it. Please do not include personal details in the message; we only need to know what is and is not working.
Our analytics providers also attach standard technical data to these records: a randomly generated identifier for your installation, and basic device and network characteristics — device model and manufacturer, screen size, operating-system and app version, mobile carrier and connection type, and an approximate region derived from your IP address. These are added by the analytics libraries themselves rather than chosen by us.
The identifiers are specific to this install: they are not your name or advertising ID, they are not shared between apps, and they are discarded when you uninstall Morph.
If you sign in to a Morph account, your analytics are also linked to the account's identifier: a random code issued by Firebase, not your email or name. That is how a subscriber who reinstalls Morph or moves to a new phone is counted as one person rather than two, and how we can see whether Pro is working for the people who pay for it. A few of these records are made by our server rather than the app, for things the app cannot see, such as a subscription renewing or ending, or whether a change an assistant asked for reached your phone; they follow the same rule and say only what kind of thing happened. Signing out stops the link: the app starts a new installation identifier. When you delete your Morph account we ask Mixpanel to delete the analytics linked to it.
Crash reports. If Morph crashes, Crashlytics sends a stack trace with the device model, OS version, and an installation identifier, so the fault can be fixed.
Google and Mixpanel process this data as our service providers. See Firebase privacy, Google's privacy policy and Mixpanel's privacy policy.
Backups
Morph does not use Android's automatic Google backup. Instead, Backup & restore (in the About Morph sheet) lets you export your setup to a file: your profiles and their cues, home-screen layouts, widgets, Pocket notes, links and checklists, your own wallpaper photos and settings. Pocket files are not included. The file goes only where you save it (for example your Google Drive or Downloads); it is never sent to us. Anyone with the file can read it, so keep it somewhere private. Restoring replaces your current setup, after keeping a copy on the phone so the restore can be undone.
Automatic backup (Morph Pro). With Morph Pro, the same backup is also made automatically and kept in your Morph account, so a reinstall or a new phone only needs your Google sign-in. It holds exactly what the file holds, including your own wallpaper photos and the names of the apps on your home screens, and is stored on servers run for Morph by Cloudflare, sent over HTTPS and encrypted at rest. Morph keeps your newest 5 backups and uses them only to restore your setup when you ask. You can turn automatic backup off on the Backup & restore screen. If your Pro subscription ends, new backups stop and the existing ones are deleted 30 days later; deleting your Morph account deletes them at once.
Children
Morph is not directed at children under 13 and does not knowingly collect data from them.
Your choices
- Uninstalling Morph removes all of its on-device data, including Pocket.
- If you have a Morph account, Delete account in the app, or the account deletion page, cancels any Pro subscription and deletes your account and everything Morph keeps on the server for it.
- To request deletion of analytics or crash data associated with your installation, email us at the address below and include the approximate date and device model.
Changes
If this policy changes materially, the updated version will be posted here with a new date, and significant changes will be noted in the app's release notes.
Contact
Questions about this policy: dev.matlabs@gmail.com