Privacy Policy
Kilogram is developed by Rinat Abidullin. This policy explains how information is handled when you use the Kilogram app, visit its website, or contact the developer. For privacy questions, write to rinatabidullin@gmail.com.
Information stored in the app
Kilogram stores the food diary and related settings on your device. This includes meals and their dates and times, foods and portions, saved nutrition values, custom products and recipes, recent products, nutrition goals, and appearance and widget preferences. When you use the goal calculator, the app can also store the information you enter for that calculation, such as age, sex, height, weight, and a selected activity level.
These details are used to provide the diary, calculations, nutrition summaries, goals, and other features you choose to use. The selected activity level is an input to a calculation; it is not continuous monitoring of your physical activity.
The current app does not require a Kilogram account or upload your diary to a developer-operated server. It does not provide its own cloud synchronization of the diary. Device backups, Apple Health, and files you choose to export are separate mechanisms described below.
Apple Health
Connecting Kilogram to Apple Health is optional and does not require Pro. The app asks for permission to write four nutrition measurements: dietary energy, protein, total fat, and carbohydrates. The exported records include their associated dates and times.
Kilogram does not request general access to health records created by other apps. To keep its exports consistent, it can inspect, update, and remove its own nutrition records, including records originating from the earlier FoodDiary app where they belong to the same app source.
When you enable or re-enable automatic transfer, the app processes existing diary history, including entries migrated from FoodDiary. Future-dated diary entries are also transferred with their saved dates; the app does not treat them as a separate meal-planning category. Changes or deletions in the diary can therefore replace or remove the app's previously exported nutrition records for affected days. Data from other app sources is not targeted by this replacement.
Only measurements you allow are written. You can stop automatic transfer in Kilogram and change permissions in Apple Health or the relevant system settings. Stopping transfer is not a command to delete earlier exports. Deleting Kilogram also does not automatically delete its records from Apple Health. Manage those records separately in Apple Health. Transfer depends on permissions and when the app can run; continuous background transfer is not guaranteed.
Health information is used for the nutrition features you request. It is not sold or used for advertising, marketing, or advertising profiles. Apple independently controls the storage, synchronization, and backup features of Apple Health under your Apple settings and Apple's privacy terms.
Widgets
Kilogram uses local shared storage to make selected diary summaries and preferences available to its widgets. Adding a widget can make nutrition information visible on a Home Screen or Lock Screen. Home Screen and Lock Screen calorie widgets are available without Pro; macronutrient and weekly widgets require Pro. Lock Screen nutrition values are hidden by default. The “Show nutrition on Lock Screen” setting can make them visible while the device is locked after its first unlock. Remove a Home Screen widget if you do not wish to display its information.
Purchases
Purchases and subscriptions use Apple's in-app purchase system. Apple handles payment details and billing. Kilogram receives the transaction and entitlement information needed to determine whether Pro access is available and to restore eligible purchases. This is not access to your full payment-card details or your Apple Account password.
Diagnostics
Kilogram keeps local technical information to diagnose issues with features such as migration and Apple Health transfer. Depending on the event, this can include timestamps, record identifiers, processing states, and error details. Such records should not be assumed to be anonymous merely because they are diagnostic.
The current app does not include a third-party advertising, tracking, or analytics SDK and does not automatically send these local diagnostic files to the developer.
The developer uses aggregate usage reports available through Apple's App Analytics to understand how Kilogram is used and improve its features. The developer also uses crash and performance reports made available by Apple to diagnose failures and improve reliability and performance. Availability of these reports depends on Apple's services and applicable sharing settings. These practices do not automatically send your diary or Kilogram's local diagnostic files to the developer. The developer does not use these reports for advertising or tracking.
If you choose to send a diagnostic file or screenshot to support, the information it contains becomes part of that support request.
Exports and migration
Exports are generated on your device. Files can contain diary entries, nutrition values, custom products, recipes, goals, and other information included in the selected export. Saving or sharing a file sends it to the destination or app you choose through the system interface. Review the content before sharing it, especially when it contains health-related information.
An exported file is a separate copy. Removing data from Kilogram does not remove copies previously saved in Files, a cloud drive, an email, or another app. CSV/JSON data export is available without Pro; PDF diaries and reports require Pro. The current app does not import its portable exports or provide full backup restoration.
When updating from FoodDiary, Kilogram can migrate existing local data and keep local migration-related records or copies. The migration does not by itself send the diary to the developer.
Support messages
When you email support, the developer receives your email address, the message, and any attachments you choose to send. This information is used to respond, investigate the reported issue, and maintain relevant support records. The support mailbox uses Gmail, so Google processes the message as an email service provider under the applicable service terms and Google Privacy Policy.
Please do not send passwords, full payment-card details, medical documents, or a complete diary unless the specific information is genuinely needed and you choose to provide it. Contacting support does not subscribe you to a mailing list.
Website and external services
The Kilogram website is hosted on GitHub Pages. GitHub records visitors' IP addresses for security purposes, including when a visitor is not signed in. See the GitHub Privacy Statement.
The website does not add advertising trackers, analytics scripts, or its own tracking cookies. Clicking an external link takes you to a service with its own data-handling practices. These services include Apple, the food-data providers, and Google Drive, which hosts the public download of the Kilogram Open Food Facts database. That public food database is not a copy of your personal diary.
Searching the food catalogues bundled with the current app takes place on the device; it does not submit your diary or search queries to Open Food Facts or USDA. Opening their external websites is a separate action. See Data Sources for information about the catalogues.
Retention and your choices
You control the diary and custom information through the app's available editing and deletion features. Removing an item from the active diary does not necessarily erase every local technical record or backup copy associated with it. Local migration copies, retained diary records, change history, and diagnostic records can have a separate lifecycle. There is no single in-app control that erases every local copy. Temporary export files are cleaned up after use where possible; abandoned export files are eligible for cleanup after 24 hours when export maintenance next runs. Widget snapshots, local Health transfer diagnostic files, and temporary export files are marked as excluded from device backups; this is not a blanket exclusion for the diary or migration copies.
Removing the app through the system's app-deletion controls removes its app storage as managed by iOS. Offloading an app is different and can retain its data. Apple Health records, Apple purchase history, system backups, previously exported files, and support correspondence are separate and are not all deleted by that action. Availability and retention of system backups depend on the relevant device and backup settings, not on a Kilogram cloud-sync feature.
Support correspondence is retained only as reasonably necessary to handle the request, keep relevant support records, or meet applicable legal obligations. You may contact rinatabidullin@gmail.com to ask about information held in support correspondence or to request access, correction, or deletion. Requests are handled subject to applicable law. The developer cannot remotely open or erase a diary that exists only on your device, and cannot erase records controlled independently by Apple, GitHub, or a destination you selected for an export.
A parent or guardian who believes a child has sent personal information to the support address may use the same contact to raise the concern.
Security and changes
Kilogram relies on the security features of the device and operating system, along with protections implemented for local app files. No storage or transfer method can be guaranteed completely secure. Protect access to your device and review files before sharing them.
This policy may be updated when the app, website, or data practices change. The preparation date identifies this document version. Questions can be sent to rinatabidullin@gmail.com.