THE DETAILS, IN PLAIN SIGHT

Privacy policy

What we collect, why we need it, and the choices that belong to you.

No Gramello account is required. Your diary and personal tracking data stay on your device; we do not store a copy on our servers.

Effective date: November 4, 2026

Gramello is a food, water, and workout tracker provided by Edward Herbert II. This policy describes Gramello's account-free Android, iOS, and desktop web apps and its website. Contact gramello@edwardofclt.com with privacy questions or requests.

No Gramello account; local diary storage

You do not need a Gramello account. Your diary, water entries, goals, saved meals, custom foods, workout routines, custom exercises, and workout history are stored on your device. We do not keep a server-side copy of new personal tracking data in the native or main web app, or provide account-based syncing between devices. The main web app stores its diary in this browser's IndexedDB storage. Export a backup before clearing site data.

This does not mean that using Gramello involves no information processing. The native apps send limited usage analytics, described below. Online food lookups, website visits, purchases, and support requests also involve the information described in this policy. Your health and nutrition records are not included in usage analytics.

Information used by Gramello

  • Personal tracking information: Food and water entries, amounts, nutrition values, goals, saved meals, custom foods, workout routines, custom exercises, and completed sessions provide your diary, totals, and trends. Native and main-web apps keep this data locally and do not upload it as personal tracking records to Gramello's servers.
  • Search and barcode information: Online food-search terms, category/restaurant filters, and product barcodes are sent to Gramello's public catalog service hosted by Cloudflare. Local results appear first; the app requests online results after a short pause. These requests do not include diary entries, goals, custom foods, or an account identity. The catalog Worker does not log query contents or persist searches. Requests use the public catalog API at gramello-catalog.abeh78.workers.dev. Finding offline menus sends the restaurant name you enter; saving a menu sends its public menu identifier. Requests do not include a Gramello analytics installation ID or authentication credentials. Cloudflare may process connection information for service/security purposes.
  • Technical information: When you connect to the website, food-lookup services, or other external services, those services receive connection and request information, such as an IP address, request time, and browser or device information. Providers may keep operational and security logs.
  • Support information: Information you choose to email us, including your contact details and the details you supply to investigate an issue. Share only the personal or diary information needed to explain your request.
  • Usage analytics: A randomly generated installation identifier, fixed action and screen names, event identifiers and timestamps, and app, operating-system, and analytics-library versions. These events contain no diary contents or health information. See Usage analytics below.

Optional workout export to Apple Health and Health Connect

In the installed iOS or Android app, you can enable workout export in Workouts settings. After you grant workout write permission, Gramello writes newly completed workouts to Apple Health or Health Connect on your device. Exported information includes the activity category and start/end times; Health Connect also stores the workout title, and Apple Health receives the title as Gramello metadata. Detailed sets, lifted weights, repetitions, RPE, calories and heart rate are not exported. Existing history and Hevy imports are not automatically exported.

For these phone-created workout exports, Gramello requests workout write access only and does not read health records created by other apps. Edits and deletions of exported Gramello sessions are synchronized while export is enabled. Failed changes remain queued locally and retry when you reopen the app, save another workout, or choose Retry. Pausing export stops further attempts but leaves existing health records and queued changes; an attempt already in progress may finish. Revoking permission in the system health settings prevents further writes. Replacing or restoring a diary backup disables export and cancels pending changes; it does not remove existing health records. A native operation already dispatched before cancellation may finish.

Consent, export identities and pending changes are stored locally and excluded from Gramello's portable diary backups. Workout contents are not sent to Gramello servers or usage analytics. Apple Health and Health Connect control storage, backup and sharing of exported records under their own settings and policies. Other apps you authorize through those services may access the exported records.

Apple Watch workouts and optional heart rate

The Apple Watch companion stores downloaded routine snapshots, active sets, completed workouts and pending transfers locally. It exchanges selected routines and completed set workouts with the paired iPhone using Apple's device connectivity. Receiving a file does not mean it is in History: opening Gramello on iPhone lets the local diary finish importing it. No Gramello account or hosted diary is involved.

Heart-rate monitoring is optional and starts Off. When you enable it for a workout, Gramello requests heart-rate read and workout write permissions on Apple Watch, shows current and session average/peak heart rate when available, and automatically saves the genuine monitored workout to Apple Health when you finish. Set logging works without monitoring or available readings. Missing readings do not reveal whether you granted read permission. Apple may collect other workout samples in its Health pipeline; Gramello does not show calorie estimates or raw HR charts.

Raw heart-rate samples stay in HealthKit. Session summaries and native save/recovery receipts stay on the watch/HealthKit; they are not sent in the iPhone set-workout payload, portable Gramello backups, or usage analytics. The watch companion has no analytics integration. Health data is not uploaded to Gramello servers or used for advertising. Apple controls Health storage, backup and sharing under your settings.

The watch owns Health saving for watch-origin sessions. Importing or editing their set workouts on iPhone does not create a second synthetic Health workout, including when monitoring was Off or a watch save failed. Removing a retained watch copy, deleting Gramello History, or replacing a diary does not delete the Apple Health workout. Manage Health records separately in Apple's Health/Fitness controls. Portable diary backups include imported set workouts, not unsynced watch data or native sensor/recovery state. Keep pending workouts until History acknowledges them; removing the watch app or its data can lose local unsynced records.

Camera and device permissions

Camera access is used to read food barcodes. Barcode recognition happens on the device; the recognized barcode is sent for product lookup. Gramello does not upload or store camera photographs or video for this feature. You can decline or revoke camera permission and enter a barcode manually. Gramello does not request microphone access for barcode scanning.

Gramello does not collect your device's precise location, contacts, or photo library. Optional Apple Health and Health Connect workout export is described above.

How information is used

Personal tracking data is used to save entries and meals, calculate nutrition totals, and show trends. Native and main-web apps perform these operations locally. Online requests retrieve food information. Support messages help us answer questions and investigate problems; technical information helps providers operate and protect their services.

We do not sell your nutrition diary data or use it for targeted advertising.

Usage analytics

The native iOS and Android apps use Twilio Segment for product analytics. This helps us understand which features are used and improve Gramello. For example, an event can record that someone opened Trends, searched for food, or logged water. It does not contain what they searched for, ate, or drank, or any amounts.

The app creates a random installation identifier to group these events. It is not derived from your name, email address, advertising identifier, or hardware identifier. Gramello has no account to associate it with. We do not match this identifier to your real-world identity or combine it with other companies' data for advertising.

Analytics events include only that identifier, fixed event or screen names, event identifiers and timestamps, app name/version/build, operating-system name/version, and analytics-library name/version. They exclude food and water entries, nutrition values, goals, saved meals, custom foods, diary dates, search text, barcodes, names, email addresses, account profiles, device identifiers, device names, and location. The event's IP-address field is replaced with 0.0.0.0; Segment still receives the network connection needed to process a request.

Segment is currently the only recipient of these app analytics events; no downstream analytics destinations are connected. These events are used only for product analytics. We do not use them for targeted advertising, cross-app advertising tracking, or identity matching, and we do not send them to advertising destinations or data brokers. The marketing website does not include this analytics integration. There are no advertising integrations in the current app or website.

If these practices change, we will update this policy and provide the notices and user choices required for the new collection or sharing.

External services

  • Twilio Segment receives the limited app usage events described above. No downstream analytics destinations are currently connected. See Segment's privacy tools and policies.
  • Cloudflare hosts the desktop web app at app.gramello.com and the read-only catalog API. It receives connection information when serving the app, and search/filter/barcode requests, public menu identifiers, and connection information. The service stores public nutrition data, not personal diaries. The app does not contact USDA, Open Food Facts, or restaurants directly for catalog searches or barcode lookups; source links open those providers only when you choose to visit them. See Cloudflare’s privacy policy.
  • USDA FoodData Central and Open Food Facts supply published nutrition and product information. Product images may load directly from their external image hosts, which receive the network information needed to serve those images.
  • Restaurant nutrition sources supply published menu data included in the app's food catalog. Source URLs and retrieval dates accompany catalog records; the public catalog directory lists available menus.
  • Apple and Google handle purchases and distribution through the App Store and Google Play. A store account is separate from Gramello. Gramello does not receive your full payment-card details; each store handles payment information under its own policies.
  • OneLink handles the app-download links on our website and routes visitors according to their device. Visiting OneLink involves a request to that external service.
  • GitHub hosts the website, public catalog directory, and public issue tracker. Browsing the directory makes a request to GitHub Pages; catalog API lookups go to Cloudflare. GitHub receives information when you visit or use its services. Anything you post in a public issue is public; use email for private support.

These providers process information under their own privacy policies and the terms applicable to their services. Information may be processed in the United States or other locations where the relevant providers operate. We may disclose information we hold, such as support correspondence, when required by applicable law or necessary to protect the service and its users.

Website and cookies

The Gramello marketing, support, and legal website is hosted on GitHub Pages. It does not ask you to sign in, submit a form, or enter diary information. Fonts and website images are served with the site. The website does not send the native app's Segment events or run advertising integrations. GitHub receives connection information when it serves a page, including your IP address; see the GitHub Privacy Statement.

The desktop web app at app.gramello.com is hosted on Cloudflare Workers. It uses IndexedDB to store its local diary and a service worker for offline app assets. The desktop web app does not send Segment analytics events. It does not use a diary or account-authentication cookie, and personal diary operations do not call a server API. External services you choose to visit, including OneLink and app stores, follow their own cookie and privacy policies.

Storage and retention

Native and main-web personal tracking records are stored on your device or in your browser. You control the device and any backups available through your operating system or other backup tools. Backup and removal behavior depends on your platform and settings; removing the app may not remove a separate device backup. New native and main-web diary changes have no automatic server backup. Use Settings to export a portable backup.

Public food results are cached separately with a 20 MiB content/index-text budget; SQLite overhead uses additional space. Restaurant menus are downloaded only when you choose to save them offline, with per-menu and total limits. Settings shows catalog usage and lets you clear search cache or remove saved menus. Neither operation deletes diary records, recipes, private foods, or recovery copies. App updates may reclaim obsolete downloaded public catalogs and derived indexes without changing personal records.

Support correspondence is retained as needed to address your request and meet applicable obligations. External providers may retain their own technical, purchase, or support records under their policies. There is no Gramello account record.

The random analytics identifier persists in app storage across launches. Clearing app storage creates a new identifier; restoring a device backup may restore the previous one. Events may be queued on the device until they can be sent. Clearing local data does not delete events already sent to an analytics service. Segment retains received events under its Data Retention and Deletion Policy and the retention settings for our workspace's plan. There is no separate downstream analytics store connected. Contact us with questions about analytics retention or deletion.

Your choices and requests

You can manage diary entries, water entries, goals, and saved meals in the app, and change camera permission in your device settings. Use your device and backup settings to manage app storage and any separately retained backups.

The current native app sends the limited usage events described above automatically and does not have an in-app analytics switch. Camera permission controls barcode scanning; it does not control analytics. We will update this section when additional analytics controls are available.

For help or a privacy request concerning information you have sent us, email gramello@edwardofclt.com. We may ask for the information needed to identify and handle your request. Do not send passwords, sign-in codes, or payment-card details. We cannot supply a server export of local diary changes.

Analytics records use the random installation identifier, not your name or email. An email address alone does not identify those records. Contact us for help with an analytics request; we will explain what information is needed and what records we can identify. You do not need to send your diary to make a privacy request.

Children

Gramello is not designed for children under 13. If you believe a child under 13 has provided personal information to us, contact us so we can investigate and remove information we hold as appropriate.

Changes to this policy

We may update this policy when the app or its data practices change. The effective date above identifies the latest published version.

For product help, see Gramello support.