Millowall · Android
Privacy policy
Effective 6 October 2026
Millowall has no account and no login. Your photos and collages never leave your phone. The only thing we ever receive is a bug report, and only if you write one and tap Send. Two Google services built into the app talk to Google directly: Google Play, which checks for and sells the premium unlock, and Google's ML Kit, which powers Magic cutout. Both are explained below.
What is collected
Millowall sends us the following, and only when you choose to send it. Services from other companies built into the app send some data of their own; those are set out separately under Services from other companies.
| Data | Required? | Details |
|---|---|---|
| Description | Required | The free text you type describing what went wrong. |
| App version | Automatic | Which build of Millowall you were running, so a report can be matched to a release. |
| Device and OS | Only if diagnostics is on | Phone manufacturer and model, Android version and API level. Needed to reproduce device-specific bugs. Sent only if you switch on diagnostics under Settings, Privacy. It is off until you do. |
| Settings snapshot | Optional, diagnostics on | A short summary of your quality, theme, rotation and battery-saver choices. There is a switch to leave this out before sending. |
| Crash log | Optional, diagnostics on | The stack trace from the most recent crash. Millowall only records crashes while diagnostics is on. The log is shown to you in full, and there is a button to remove it before sending. |
How it is handled
- Reports are anonymous. Millowall never asks for your name, email address, or any account details.
- Your photos, images, and collage layouts are never uploaded. They stay on the device.
- We never receive anything automatically. There is no background reporting and no auto-send when the app crashes.
- Before you send, the screen lists what the report will contain.
- Reports are sent over an encrypted connection to a private Google Sheet owned by the developer. No third-party analytics service is involved.
- Crash logs are stored locally and excluded from Android cloud backup and device transfer, so a stack trace cannot leak through a Google backup.
- If Android backup is on, your Millowall layouts and settings may be included in your device backup, which is held in your own Google account under Google's terms. Stickers, albums, photos copied into albums and photos brought in from a backup file are left out of the cloud backup, which keeps it under Google's size limit. A direct phone-to-phone transfer may include them. Crash logs and your purchase-unlock record are always left out of backup and device transfer.
- Settings, Backup and restore lets you save your library as a single file. The file is made on your phone and saved wherever you choose. Millowall never uploads it. If you tap Send, your phone's share menu hands it to the app you pick, such as WhatsApp or email. You choose what goes in. It can contain your layouts, your stickers, the photos in albums you keep copies of and, if you choose, the photos used in your layouts. Anyone who has the file can open those photos, so keep it somewhere you trust.
- Reports are stored on Google's infrastructure, which may be outside South Africa. Google provides appropriate safeguards for such transfers.
What it is used for
Diagnosing and fixing problems in the app. Nothing else.
Services from other companies
These are built into Millowall and send data straight to the company that runs them, not to us. We never receive it.
ML Kit, for Magic cutout (Google)
- When
- When you use Magic cutout in the Sticker Creator. If you have the premium unlock, Millowall also asks Google Play services to download the cutout model in the background, only on Wi-Fi, so your first cutout is instant.
- What it sends
- Usage and performance metrics: your phone's manufacturer, model and Android version, Millowall's package name and version, an identifier for this installation and one Google uses for diagnostics, how long a cutout took, the size and format of the image, and any error codes. Your photo itself is never sent. The cutout happens entirely on your phone.
- Why
- Google says it uses these metrics to measure performance, debug, maintain and improve ML Kit, and to detect misuse or abuse. We cannot see this data and have no use for it.
- Where it goes
- Straight from your phone to Google's servers over an encrypted connection. They may be outside South Africa. Google says it does not pass this data on to third parties. Google handles it under the Google privacy policy (opens in a new tab).
- How to avoid it
- Cut stickers out by hand instead of using Magic cutout. That involves no Google service. The background model download for premium users still happens on Wi-Fi.
Google Play Billing, for the premium unlock (Google)
- When
- Each time Millowall starts, it asks Google Play whether your Google account owns the premium unlock and what it costs in your country. If you buy it, Google Play runs the purchase.
- What it sends
- The purchase check and, if you buy, the purchase itself. Your card details, billing address and payment method go to Google only. We never see them. The app receives whether a valid purchase exists, and Google's reference for it.
- Why
- To take the payment, and to unlock the extra features on any phone signed in to the Google account that bought them.
- Where it goes
- Google Play's servers, over an encrypted connection. Google handles it under the Google privacy policy (opens in a new tab).
Sharing
Your data is not sold or rented. There is no advertising network in this app. Apart from the services above, nothing is shared with third parties.
Retention
Reports are kept for no longer than 24 months from receipt, and are deleted sooner once the problem is resolved and there is no further need for them. You can ask for yours to be deleted at any time.
Children
Millowall is not directed at children under 13, and does not knowingly collect information from them.
Who is responsible
Millowall is published by Charactir (Pty) Ltd, a company registered in South Africa (registration number 2016/385896/07), of 5 Washington Drive, Johannesburg, Northcliff Ext 15, 2195, South Africa. Charactir (Pty) Ltd is the responsible party under the Protection of Personal Information Act, 2013 (POPIA), and the data controller under the UK and EU GDPR where those apply. The Information Officer is Cornelius Hendrik Prinsloo, reachable at the address under Contact.
Delete your data
To have the data you sent us deleted:
- Email help@charactir.com with the subject "Delete my Millowall data".
- Tell us roughly when you sent your report and what it said. There is no account, so this is how we find it.
- We delete it and confirm by email within 30 days.
Everything in the report is deleted, as listed under What is collected. We keep nothing afterwards. If you never ask: Reports are kept for no longer than 24 months from receipt, and are deleted sooner once the problem is resolved and there is no further need for them.
Anything else Millowall keeps is stored only on your phone. Uninstalling the app, or clearing its storage in Android's settings, deletes all of it. If Android backup is on, a copy may also sit in your Google account's backup, which you can delete there.
Data sent to another company's service is held by that company, not us. See Services from other companies for each one's own policy.
Your rights
You can ask us to confirm what personal information we hold about you, give you a copy of it, correct it, delete it, or stop processing it. Email the address below and we will respond within 30 days. There is no account, so tell us enough about your report for us to find it: roughly when you sent it and what it said. For data held by another company's service, see its own privacy policy, linked above.
If you are unhappy with how your information has been handled, you may complain to the Information Regulator (South Africa) at inforegulator.org.za (opens in a new tab), or, in the EU or UK, to your local data protection authority.
Changes
If this policy changes, the effective date above changes with it, and the updated version is published on this page.