Explicit choice and opt-out
During setup, Mongle asks you to choose “Share” or “Don’t send.” Before consent, after refusal, and after you turn sharing off in Mongle Settings, no analytics event is created, stored, or sent. Turning it off cancels in-flight requests. Every feature remains available either way.
What an event can contain
The fixed allowlist covers onboarding completion, app opens, permission results, draft and cover steps, theme choices, save and share results, deletion, cadence changes, and reminder changes. Events may include coarse source, cadence, theme, result, permission, and photo-count buckets plus app version, build, distribution, and iOS major version. TelemetryDeck also records when its server receives an event.
No returning-user identifier
Mongle sends an empty TelemetryDeck clientUser value. A random session ID exists only in memory for the current app process and changes after relaunch. The app creates no account ID, IDFA, IDFV, device name, or installation ID and keeps no analytics queue on disk.
TelemetryDeck processing and retention
Mongle sends allowed events directly to TelemetryDeck’s v2 ingest service. Under Aroido’s current free plan, events are available in the dashboard for a three-month live access window. TelemetryDeck states that older events may be unloaded to cold storage, so its retention and privacy terms also apply. Because events contain no returning-user identifier, Aroido cannot isolate one person’s past events.