Scope and operator
logmio, by TOMOSHIBI LLC, makes report images from Apple Health records for you to review and share. It has no app-specific account registration or feature for syncing cards to a server.
Reading and using Health records
The ten supported metrics are weight, body fat percentage, BMI, steps, sleep, Move, Exercise, stand time, walking/running distance and flights climbed. Read requests follow the one to five metrics you select. Permitted records are used to display cards, compare values and create images. logmio does not write to Apple Health. Completing a read request alone does not establish that permission was granted or records exist.
Body measurements use the latest record on the report day and the previous measurement. Steps and activity use the previous calendar day's total and the day before that. Sleep uses the main sleep ending on the report morning and the preceding night. Days follow the current device time zone. Missing records or comparison values are not filled with another day's data.
The app does not pass health values, measurement timestamps, photos, names or card comments to advertising or external analytics. Health data is not used for advertising.
Data stored on your device
Daily card health values, measurement timestamps, comments, designs and completed share/Photos-save status are saved as structured on-device records. Saving edits can record a card before an image is exported. Photos imported for backgrounds or avatars are stored as reduced copies on the device. A temporary image is also created for sharing.
Daily designs and comments are separate from the base design for future cards. History reads values again from Health records for that date; it is not an image archive with values fixed at save time. Reading again does not itself rewrite saved history. Successful empty results remain missing; previously loaded values are labelled when shown during loading or a complete read failure.
The card storage area uses iOS file protection and an operating-system setting that excludes it from backup. That area is separate from Apple Health and Photos sync and backup settings.
Deletion and sharing you initiate
Deleting a card removes it from the app's History. Saving may retain an on-device preservation copy; deleting history does not necessarily erase preservation copies or imported images at the same time. Contact us if you need clarification about deleting related data.
Health originals, PNGs saved to Photos and copies at sharing destinations are managed separately in their respective apps or services. A shared image contains the health values, photos, comments and other content you chose to display. Review the image and destination before sharing, and check that service's data practices. logmio does not post automatically.
Purchases
Apple processes purchases and restoration. logmio checks verified entitlements to apply logmio Plus. The app has no feature for receiving payment-card details or your Apple Account password. Apple's purchase and refund support is also available for transaction issues.
Advertising, consent and network communication
The free version uses Google Mobile Ads and Google's User Messaging Platform (UMP). After confirming free entitlements, the app checks the consent state and starts the ad SDK only when ad requests are permitted. It stops new ad startup, requests and presentations while a purchase is active or entitlements remain unresolved. Checking the consent state itself involves network communication.
The app does not pass health values, card dates, images, names, comments or custom targeting to advertising. It adds non-personalized settings to ad requests and disables publisher first-party ID and ad-personalization settings. The app has no added code that requests iOS tracking permission.
The ad SDK may process technical information such as IP addresses, device/app information, identifiers, and ad views or interactions. These are separate from card health values. See Google Mobile Ads data disclosures . The actual processing scope with this app's configuration requires confirmation before publication.
When UMP requires it, Settings shows Ad Privacy Options. Ad-frequency records store output-request counts and the last actual ad-presentation time on the device, without health values or card dates. Support and Terms explain the policy: each share/save is a candidate, except within 60 seconds of an actual presentation and on the next output immediately following it.
Optional analytics and crash diagnostics
Optional analytics and diagnostics through Firebase Analytics and Sentry are currently disabled. Settings switches are off and unavailable, and transmission through these optional integrations is not started. Before enabling them, we will review separate analytics/diagnostics choices, explanations, consent and withdrawal controls.
The prepared analytics code passes only fixed event and screen names, without health values, images, names, free text or selected dates as parameters. Diagnostic code disables screenshots, view hierarchies and automatic interaction/network records, then limits outgoing events to diagnostic categories. Actual SDK traffic and technical information, retention, processing regions and withdrawal behavior require verification before enabling these integrations. Advertising and purchase communication are separate from them.
Feedback and contact
The current in-app feedback screen does not send externally or report a completed submission. It does not automatically attach health values, photos, names or card comments. Do not enter confidential or health information.
Use the TOMOSHIBI APPS contact form for support and data-handling questions. The in-app preparation screen has no reply-address field.
Changes
Material changes will be reflected here, with consent obtained again where required.
Before publication — private draft notes
This is an unpublished review draft for the next 1.0 candidate. The effective date, public URLs, availability regions, specific retention periods, and actual support/deletion-request operations are not yet confirmed. Deletion methods and retention for preservation copies and imported images, plus real-device file protection, backup exclusion and restoration behavior, require verification.
Google's disclosures must still be reconciled with the integrated SDK settings, privacy manifests, App Privacy declarations, regional UMP consent/privacy options, production ad delivery and actual traffic. Non-personalized settings or the absence of an ATT request do not establish zero collection, no tracking, or legal/advertising-policy compliance.
A separate prepared feedback client routes through Cloudflare to the operator's Discord, but is not connected to the product screen. Before enabling it, confirm the message and app version/build/language/entitlement fields, recipients, retention, deletion and reply operations. Optional analytics/diagnostics activation, consent/withdrawal and actual SDK traffic also remain unverified. Saving this draft does not start or verify those operations.