Privacy Policy
Local-First Architecture & Data Collection
Log-It! stores your logs, customized daily goals, reminders, preferences, and consent records locally on your device using Room SQLite and DataStore. Log-It! operates with zero central proprietary servers; MIYLabs does not host an external user database.
Third-Party Google Services & Cloud Integrations
To provide seamless functionality, Log-It! offers optional integrations with Google services. When you opt into these features: Google Sign-In & Firebase Authentication processes your account credentials and security tokens; Google Drive Backups uses strictly the restricted
drive.appdata scope to store backup archives in your personal, hidden appDataFolder; Android Health Connect reads and writes strictly HydrationRecord entries to synchronize water intake across fitness platforms. You can manage connected apps anytime in your Google Account Third-Party Connections.Health Connect Data Protection & Use Commitments
Our Health Connect data-use commitments reflect the Limited Use requirements:
- Health Connect data is accessed solely to record fluid intake and synchronize daily hydration history across compatible platforms under your direction.
- Health data is NEVER sold, rented, or transferred to data brokers, advertising platforms, or information resellers.
- Health data is NEVER used to train artificial intelligence (AI) or machine learning (ML) models.
- Health data is NEVER used for advertising, marketing, or interest-based profiling.
- You can inspect, manage, or revoke Health Connect access at any time through your Android device settings.
Data Security & Technical Protections
We implement rigorous technical safeguards to protect your personal information:
- Encryption in Transit: All data transmitted between the app and external Google services (Firebase Authentication, Google Drive API) is encrypted using industry-standard Transport Layer Security (TLS/HTTPS).
- Encryption at Rest: Local SQLite database records reside strictly within Android's private, sandboxed application directory (inaccessible to other applications). Cloud backups stored in Google Drive are protected by Google Cloud's native AES-256 server-side encryption.
Advertising, Consent & Strict Health-Data Isolation
Current release: up to eight inline banners
Log-It! includes Google Mobile Ads / AdMob and Google's User Messaging Platform (UMP). The production app may show one clearly labelled inline banner near the top and one at the end of each main tab: Home, History, Reminders, and Settings. These placements are separated from app controls by deliberate spacing; there are no interstitial, rewarded, or app-open ads. Ads never appear in notifications and are never triggered by logging water or another beverage. Google may process your IP address, app and device identifiers (including the Android advertising ID when available), diagnostics, consent choices, and ad interaction signals to provide, secure, measure, and—only where permitted by your choices and law—personalize advertising. UMP requests consent where required and exposes Ad privacy choices in Settings when a privacy-options form is required. Development builds use Google's official test inventory only and cannot generate publisher revenue. Hydration entries, goals, Health Connect data, Google Drive backups, account details, and exported files are never supplied to the advertising SDK or used for ad targeting. Learn how Google uses partner data in Google's partner-sites policy and manage the advertising ID using the Android advertising ID guide.
Log-It! includes Google Mobile Ads / AdMob and Google's User Messaging Platform (UMP). The production app may show one clearly labelled inline banner near the top and one at the end of each main tab: Home, History, Reminders, and Settings. These placements are separated from app controls by deliberate spacing; there are no interstitial, rewarded, or app-open ads. Ads never appear in notifications and are never triggered by logging water or another beverage. Google may process your IP address, app and device identifiers (including the Android advertising ID when available), diagnostics, consent choices, and ad interaction signals to provide, secure, measure, and—only where permitted by your choices and law—personalize advertising. UMP requests consent where required and exposes Ad privacy choices in Settings when a privacy-options form is required. Development builds use Google's official test inventory only and cannot generate publisher revenue. Hydration entries, goals, Health Connect data, Google Drive backups, account details, and exported files are never supplied to the advertising SDK or used for ad targeting. Learn how Google uses partner data in Google's partner-sites policy and manage the advertising ID using the Android advertising ID guide.
Children’s privacy
Log-It! is intended for users aged 13 and older (16 and older in the EEA and UK), not younger children. Optional Google sign-in and Firebase Authentication, Drive backups, Health Connect, and advertising SDKs may process data as described above. Local-first storage does not mean that all personal data stays on the device.
Children and anyone below the legal drinking age in their location must not drink alcohol. Meeting the app's minimum-use age does not permit alcohol use. Parents and guardians should supervise age-appropriate app use.
The age screen keeps only a broad age group on this device, separate from Drive backups; the exact entered age and date of birth are not saved in the age profile. For users under 18, the app requests child-directed, general-audience-rated ads and shows only the top banner on each main tab. Adults retain the existing top and bottom banners. Age-related ad-treatment signals are sent to Google; hydration and account records are not used for ad targeting.
Deletion scope and limitations
Clearing app storage or uninstalling removes local data only. Drive backups and Health Connect records remain until separately deleted. Disconnecting Google access alone does not delete backups or the Firebase app identity. There is currently no combined deletion action or verified outside-app Firebase deletion request path.
Self-Service Rights & Technical Support
Clearing app storage or uninstalling removes local data only. Drive backups and Health Connect records remain until separately deleted. Disconnecting Google access alone does not delete backups or the Firebase app identity. There is currently no combined deletion action or verified outside-app Firebase deletion request path. privacy@miylabs.uk
Log-It!
- Google Drive:
drive.appdata/appDataFolder - Health Connect: Hydration read + write only
- Technical Support: logit@miylabs.uk
- Privacy: privacy@miylabs.uk