Data safety
How LBoursa answers the Google Play Data safety form, with the reasoning behind each answer.
Last updated: 10 November 2026
Data processed only on the device (portfolio, transactions, favorites, alerts, settings) is not “collected” under Google Play's definition. Answers for Google SDKs follow Google's disclosures for the Mobile Ads SDK and Firebase.
Data collection and security
| Question | Answer |
|---|---|
| Does the app collect or share any of the required user data types? | Yes |
| Is all user data encrypted in transit? | Yes — HTTPS only |
| Can users request that their data be deleted? | Yes — Delete your data |
| Does the app require an account? | No |
Data types
| Category → type | Collected | Shared | Optional? | Purposes |
|---|---|---|---|---|
| Location → Approximate location | Yes | Yes | Required | Advertising, Analytics, Fraud prevention (derived from IP by Google SDKs) |
| App activity → App interactions | Yes | Yes | Optional (Settings) | Analytics, Advertising |
| App info and performance → Crash logs | Yes | No | Optional (Settings) | Analytics |
| App info and performance → Diagnostics | Yes | No | Optional (Settings) | Analytics |
| App info and performance → Other performance data | Yes | Yes | Required | Advertising, Analytics |
| Device or other IDs | Yes | Yes | Required | Advertising, Analytics, Fraud prevention, App functionality (push token) |
Not collected: personal info, financial info, health, messages, photos, audio, files, calendar, contacts, browsing history, precise location.
Permissions
| Permission | Why |
|---|---|
INTERNET | Download market data, ads and push messages |
ACCESS_NETWORK_STATE | Offline banner, avoid useless refreshes |
POST_NOTIFICATIONS | Price alerts and news (Android 13+, optional) |
AD_ID | Added by the Mobile Ads SDK — advertising and analytics |