Support center

Help, without the guesswork.

Setup notes, troubleshooting, and direct links for Creative Catcher. If your issue persists, contact the developer with your Android version, device model, and the event status shown in the app—never send your PIN or access token.

Contact support
Contact support

Tell us what happened.

Support email: mohamed.elsamman.dev@gmail.com

Email the developer
01

Getting started

Complete the setup flow, activate Device Protection, grant camera and location permissions, and connect Gmail if you want alerts.

02

Google account connection

Sign-in identifies your selected Google account. Gmail alerts are a separate, send-only authorization. Reconnect from Settings if the app shows authorization required.

03

Device Protection

Creative Catcher uses Android’s consumer Device Administrator with only the watch-login capability to observe supported failed unlock callbacks.

04

Camera permission

Camera access is used for a single front-camera evidence photo after a qualifying event or protection test. It is not a live preview or continuous camera feed.

05

Location permission

Location adds context to an event. The app may use a recent last-known location or request a current fix; it does not request Android background-location permission.

06

Background protection

Keep Creative Catcher enabled in battery and background settings. Samsung, Xiaomi, OPPO, Realme, and other OEMs may restrict background execution differently.

07

Gmail alerts

Alerts are sent through the linked Gmail account and can include the event time, location details, place label, and a captured photo. Delivery can wait for network and valid authorization.

08

Local evidence

Events are stored in app-private local storage. The current app does not upload evidence to Google Drive or a Creative Catcher server.

09

App Lock

The app-specific PIN is separate from the Android device credential. Strong biometrics can be enabled for the app lock; Creative Catcher never receives your biometric template.

10

Battery and OEM settings

Battery optimization exemption and OEM auto-start/background permissions can improve reliability, but Android and device manufacturers can still limit background work.

Frequently asked questions

Common answers

Why wasn’t a photo captured?

The camera permission may be denied, the front camera may be unavailable or busy, Android may block the background foreground-service start, the hardware may fail, or the capture may time out. The event remains local with a failure status.

Why is location unavailable?

Location permission or device location services may be off, no usable fix may be available, or Android/OEM background limits may prevent a fresh fix. The app may use a real recent cached location when available.

Why didn’t I receive an email?

Check that Gmail authorization is connected, the device has network access, the linked account is correct, and the event’s Gmail status is not auth-required or failed. Reconnect Gmail from Settings and run the protection test.

Does Creative Catcher know my Google password?

No. Google’s Credential Manager and Identity Services handle sign-in and authorization. Creative Catcher receives account identity and authorization results, not your password.

Does the app upload data to its own server?

No developer backend or Creative Catcher server is present in the current build. If Gmail is authorized, the app sends the alert through Google’s Gmail API to the linked account.

Where are my photos stored?

Captured photos are stored in the app’s private evidence directory on the device. The normal path encrypts them with AES-256-GCM using Android Keystore. A decrypted preview may be created temporarily in the app cache when you view it.

How do I disconnect Google access?

Open Settings in Creative Catcher and choose Disconnect. This clears local account, token, and scope state. For account-level revocation, use Google’s account permissions page.

What happens when the device is offline?

The event is stored locally first. Gmail delivery can remain pending and retry when connectivity and a usable authorization token are available.

Does it work on every Android phone?

No feature can be promised on every phone. Android version, permissions, camera hardware, location state, OEM background policies, and Google Play services affect behavior.

What happens after Force Stop?

Force Stop pauses protection and clears scheduled work until you manually reopen Creative Catcher. This is an Android system limitation.

Privacy and deletion

Review exactly what is processed in the Privacy Policy. To remove local evidence, use the in-app delete control or Android’s Clear storage/Uninstall controls. For the complete instructions, see Delete account and local data.

Service terms are available at Terms of Service.