What leaves the device, and what never does.
Your latitude and longitude leave the device only when the app turns a point into a place name (reverse‑geocoding), in two situations:
Picking a country and city in the Settings autocomplete sends nothing: the list and every city's coordinates are built into the app, so that lookup is entirely on‑device.
In both reverse‑geocode cases the use is ephemeral: the third‑party geocoding service (OpenStreetMap's Nominatim) processes the request and does not retain your coordinates in a way that links back to you. Your location is not sent anywhere else — not to Sentry, not to PostHog, not to Lotabytes' own servers. There is no background location tracking.
This is the only category of personal information that ever leaves your device.
When the app crashes or hits an unhandled error, an anonymous crash report is sent to Sentry, the error‑tracking service we use to find and fix bugs. A typical report contains the technical stack trace, exception type, operating system / version / device model / app version, and the anonymous device identifier described in K4. It does not contain your location, your name, your email, contents you've typed into the app, or anything from your platform store account.
Where enabled in the build, Sunline sends anonymous usage events to PostHog (EU region) so we can understand which features are used and where things go wrong — for example "app opened", "purchase completed", "asset download failed", or an end‑of‑session summary of which features were toggled. Events carry a small set of properties such as a device‑class string (e.g. mid2k-2096x1024-1.8), the app version and build number, and event‑specific facts (like the tier of a failed download). They do not carry your coordinates, your country / city, your name, your email, or any store account identifier.
On first launch the app generates a random UUID (e.g. 3f29e0a2-…) and stores it locally. It is attached to crash reports and analytics events purely so we can group multiple events from the same install together when investigating bugs or measuring how a feature is used. It is not derived from any device hardware identifier, advertising ID, or account, and it cannot be used to identify a particular physical device or person — it is just a random number generated on your device.