Privacy Policy | Body Hub | You Know Its Me Studios

About this policy

This policy covers the Body Hub Android app, package com.youknowitsmestudios.bodyhub, and this legal and support website.

Body Hub is operated by KAWAII AND CARDS LLC and published under the studio name You Know Its Me Studios. “We” means KAWAII AND CARDS LLC.

For support and privacy inquiries, visit the support form. Contact email: youknowitsmestudios@gmail.com.

Body Hub stores your profile and records on your device. A local profile is not an online account. The app does not provide developer-operated cloud synchronization or a complete backup-and-restore service. Some optional features and platform services involve other providers, as explained below.

Information and purposes

The information used depends on what you enter and which features and permissions you choose.

Profile and preferences: birth date, sex, height, weight, goals, activity level, food preferences, allergies, dietary restrictions, available ingredients, training experience, equipment, movement limitations, and training time. These support personalization, calorie estimates, and meal and workout suggestions. Pregnancy and breastfeeding questions appear when Female is selected; these answers affect whether calorie estimates are available. Optional smoking and alcohol-habit answers can inform a summary you request.
Health and fitness records: food, nutrients, water, alcohol, workouts, individual exercise sets, sleep and recovery, weight, body measurements, goals, symptoms, vitals, and notes. The app uses these for logging, calculations, charts, progress summaries, and AI assistance with relevant saved records.
Medication information: entered medication schedules, doses logged, supply and refill information, and reminder choices. The app uses these to organize your records and schedule reminders, not to prescribe or determine a dose.
Images and scan data: selected or captured images for meal, recipe, nutrition-label, scale-reading, or profile features; saved body surfaces, reference outlines, and camera-setup details. Their different storage rules are explained below.
AI input and output: your questions, selected images, relevant saved records and profile information, answers, summaries, and editable drafts. These are processed to answer the request you make.
Operational information: settings, earned achievements and dates, reminder identifiers and due times, local AI timing estimates, Health Connect source identifiers and synchronization tokens, and phone-step tracking state. These support the relevant app features.
Purchase information: Google Play product and purchase information, purchase tokens and signatures used to check and acknowledge purchases, and a local Premium status and last-check time. These are used for access and restoration.

Processing and storage

Your saved records, edit history, profile, retained photos, scan geometry and outlines are held in the app’s local store. Health Connect imports are local copies of data shared through Android; “sync” in these settings means updating those copies, not uploading them to a Body Hub server.

The app has no developer-operated endpoint for uploading your health records, images, or AI conversations. It has no integrated advertising, third-party analytics, or automatic crash-report upload service. Health records are not sold, used for advertising, or sent for general-purpose model training by Body Hub.

Local processing still involves sensitive personal information. It does not mean that the app never accesses data or that every feature works without a network. Food lookup, Google Play delivery and purchasing, a selected cloud file provider, website visits, and support email can involve network services.

On-device AI

Text and image assistance runs locally on your device. Body Hub does not send prompts, selected records, images, or results to a hosted AI service, and it has no remote inference fallback. The model processes the records and profile context supplied for the feature you request.

AI conversations and unsaved results are held in memory rather than saved as a chat archive. Leaving the assistant or backgrounding the app triggers cancellation and cleanup; local timing information is retained to estimate progress. A result becomes part of your saved records only when you review and save its draft. A summary you export becomes a separate file.

Model files are supplied through Google Play install-time packs. Installation and updates require the relevant Play services and may require a connection and substantial device storage. Having a local model does not establish that separate voice or platform services have the same privacy practices.

Personal insights and background analysis

Premium personal insights use relevant saved records, goals and preferences to identify recorded patterns. Calculations and record selection happen on the device. Optional local AI helps explain the selected evidence. Associations are not causes, missing logs are not zero, and proposed target or workout changes require your review before saving.

Insights, evidence references, dismissal and snooze choices are stored encrypted locally. Editing or deleting supporting records invalidates cached findings. This does not create a persistent conversation archive. Deleting all app data removes these caches and choices.

Background Intelligence can be turned off in Settings. Charging-only and Wi-Fi-only are independent preferences, both on by default; when both are on, both are required. Wi-Fi is a scheduling preference and does not authorize health-data uploads. Android determines when eligible background work runs. Your direct Ask requests and core tracking operate independently.

Insight notifications are off by default. You may choose a daily or weekly digest, with at most one useful insight notification per day and no health details on the lock screen. Quiet hours, dismissed or snoozed findings, and already-viewed insights are respected. Medication reminders and active workout timers remain separate.

Health Connect and phone steps

With your permission, Body Hub can read: weight, height, body-fat percentage, lean body mass, body-water mass, bone mass, basal metabolic rate, steps, sleep sessions and stages, exercise sessions, resting heart rate, blood pressure, blood glucose, nutrition, and hydration. It uses these for your logs, calculations, trends, and relevant local AI requests. Imported data can include timestamps, source-app identifiers, record identifiers, recording method, and device manufacturer/model where supplied.

Choose categories in Settings → Connected Apps → Choose data types, then use Connect Selected Data. The initial import covers approximately the previous 29 days. Automatic refresh can import changes while the app is open. Allow background refresh requests a separate permission where supported and schedules periodic background imports. Android controls when background work runs.

Steps from Health Connect use its source-priority aggregate. On supported Android versions, Body Hub relies on Health Connect’s phone-step recording. On other compatible phones, you can enable Count Steps on This Phone, which uses the phone’s step-counter sensor and an ongoing notification. Activity-recognition permission is required on applicable Android versions. Tracking interruptions and restarts can leave gaps; no location permission is used for this feature.

Body Hub can write steps. If you allow Share Phone Steps With Health Connect, the fallback phone tracker writes its own measured step intervals, times, and phone manufacturer/model to Health Connect. Pending intervals counted before permission was granted can be shared afterward. It does not write imported records or your other Body Hub logs back to Health Connect. Other apps with appropriate Health Connect permissions may read the steps you share.

You can revoke read, write, and background permissions in Health Connect at any time. Revoking access stops the corresponding access but does not erase existing local imports or previously shared steps. Source changes and deletions can be reflected during successful synchronization, but deleting a local copy does not delete the source. See Body Hub’s Health Connect deletion controls.

Camera, photos, and body scans

Camera access is used for the capture you start. Selected images are opened through Android’s document picker. If you select a cloud-backed file, that provider may download it to your device under its own practices.

Temporary images: scan camera frames, intermediate masks, and label or scale images used for analysis are processed in memory. Body Hub does not save raw scan photographs, videos, thumbnails, or frame dumps. Capture handlers release app-owned buffers on completion, interruption, cancellation, or failure; image-analysis handlers also clear buffers when you leave or background the feature. The app cannot guarantee physical erasure of every buffer controlled by Android or device hardware.

Retained photos: a meal or recipe image is kept locally only when you choose to keep or attach it and save the record. An optional profile picture is cropped and retained when you choose Use Picture. These are encrypted copies in the local store. Removing an app copy does not delete the original in a gallery or file provider.

Derived scan information: choosing Save Body Shape retains body-surface geometry, a featureless front reference outline, and setup information such as entered height, camera configuration, and orientation. These are body-related personal data, not anonymous data. Later saved scans can carry a copy of the reference outline. Deleting one scan does not erase outline copies in other scans.

Microphone and voice providers

Speak Instead requests microphone access and uses Android’s on-device speech-recognition service on Android 12 or later when that service is available. Body Hub explicitly selects the on-device recognizer, requests offline recognition, and does not fall back to an online recognizer. If unavailable, you can type. Recognition is stopped and released when you leave the feature or background it; Body Hub does not save an audio recording.

Spoken guidance and Read Aloud use the installed Android text-to-speech engine. Body Hub offers voices reported by that engine as installed and not requiring a network. The engine receives the text it is asked to speak, which can include an AI answer about your records.

The recognition and speech providers depend on your device and Android settings; Body Hub does not select a single named provider for every phone. Provider software, language downloads, updates, and its own diagnostics are governed by that provider. Body Hub’s on-device AI does not guarantee that all activity of those separate services stays on-device. Keyboard dictation is also controlled by your keyboard provider.

External services

Open Food Facts: when you explicitly search for a food or barcode, Body Hub sends the entered search text or barcode over HTTPS to world.openfoodfacts.org. The request includes a Body Hub/Android user-agent; the service also receives network information such as your IP address. Body Hub does not attach your health history, profile, or image to that request and does not fetch product photos. Selected product information can be saved in your local food record. See Open Food Facts privacy information.
Google Play: Play distributes the app and its AI model packs and handles purchase and entitlement requests. Pack/app identifiers, delivery status, and necessary app, device, and network information are handled for distribution; these requests do not include your AI prompts or health records. For purchases, Play handles your Google account, payment and transaction information. Body Hub uses returned product and purchase details to check access and sends purchase tokens to Play to acknowledge eligible purchases. It does not receive your full payment-card details or send your health records with billing requests. See Google’s Privacy Policy.
Android and chosen providers: Health Connect, recognition, text-to-speech, document providers, and apps you choose for sharing process the information described in their respective sections. Body Hub has no direct proprietary Samsung Health or Google Fit connection; those apps must share supported data through Health Connect.

Bundled camera, barcode-decoding, scan, and AI libraries process their respective inputs locally. Body Hub does not integrate a hosted image-analysis service. Third-party software notices are available in Settings → About & Licenses → Licenses.

Retention and deletion

Local records remain until you delete them or clear app data; the app does not automatically expire your saved history. Editing a record can retain earlier encrypted revisions. Deleting that record removes its revisions and its attached meal/recipe photo. Profile photos can be removed separately. Achievements already earned and phone-step tracking state can remain after an individual record is deleted.

Saved scan surfaces and their outlines remain until the containing scan records are deleted. To remove all copies of a shared reference outline, delete every scan containing it or clear all app data. Temporary captures and unsaved AI content are not intentionally written to an app image or conversation archive; their app-owned memory is released as described above. An original image you selected remains with its original provider.

Delete All Body Hub Data erases the local records, revisions, stored documents including profile/photos/outlines/achievements and entitlement cache, clears preferences and encryption keys, cancels scheduled work, and asks Android to clear the app’s remaining data. Installed app/model packages remain until uninstalling. An active Play subscription, Play transaction records, Health Connect records, exports, and support correspondence are separate.

The local entitlement cache contains Premium status and its last verification time. Access requires rechecking after up to seven days; the cached record itself remains until replaced or app data is cleared. Google controls retention of its purchase and account records. Body Hub does not maintain a remote entitlement account.

Support messages and attachments are deleted within 90 days after the issue is resolved. Information needed for an ongoing dispute or legal obligation may be retained for that purpose and is deleted when no longer needed. You can email the support/privacy contact to request deletion of correspondence; any information that must remain for those purposes is subject to the same limits.

Follow Body Hub data & deletion for the exact app controls and the limits of each action.

Security and Android backup

Saved record and document payloads, including retained photos and scan data, use AES-256-GCM encryption with a key held by Android Keystore. This is payload encryption, not a claim that every database byte or app setting is encrypted. Record IDs, revision numbers, hashed import keys, some preferences, local timing data, and scheduled-work metadata are stored separately. Records are decrypted in memory when used.

An optional Require Device Screen Lock setting uses Android device credentials to control opening the app. Network food lookups use HTTPS and the app disallows cleartext network traffic. No storage or software system is completely secure. Keep your device and operating system updated, protect its screen lock, and protect exported files.

The app disables Android automatic backup and explicitly excludes its data from Android cloud backup and device transfer. It does not offer a complete encrypted backup/restore workflow. Normal uninstalling or Android’s clear-storage control removes local app data, but neither reaches exports, earlier or independently created backups, copies made by other tools, or data held by other services. Manage any such copies separately; deletion is not a guarantee of forensic erasure from all device hardware or external systems.

This website

GitHub Pages hosts this website. GitHub processes website request information, including IP addresses, for operating and securing its hosting service. See the GitHub General Privacy Statement.

These static pages have no Body Hub account login, health-data upload form, advertising, analytics scripts, external fonts, or tracking integrations. Viewing them does not upload the health records stored inside your Body Hub app. Opening an external link sends a request to that website under its own privacy practices.

Audience and children

Body Hub is intended for teenagers and adults ages 13 and older. Users under 13 may not use Body Hub. This audience rule does not mean that adult calorie calculations, AI suggestions, or every health feature are suitable for minors. Teenagers should discuss health, nutrition, and training decisions with a qualified healthcare professional.

Google Play assigns Body Hub regional content ratings. Those ratings are separate from Body Hub’s intended audience and minimum age of 13; they do not set a universal minimum age for the app or establish that every health feature is suitable for minors.

Body Hub’s birth-date field is used for calculations; it is not an online age-verification process. The app does not enforce an app-wide age gate. The calorie estimator withholds estimates outside its supported age range of 18–100 and also applies other eligibility checks. That calculation limit is not an app-wide access restriction or a suitability assessment of other features.

If a child under 13 has used the app, stop that use and remove the local data with the Body Hub deletion controls. If information about a child was sent to support, contact us to request its deletion without resending sensitive details. We cannot identify or remotely erase information held only on a phone.

Updates and privacy inquiries

This policy will be updated when app features or data practices change. The effective date identifies the version in force. Changes that require additional notice or consent will be handled before the new processing begins. Review this page when updating the app.

For questions about this policy, information you sent to support, or applicable privacy rights, see our Body Hub support page for contact details. The operator cannot remotely view or erase records stored only on your phone.