Skip to content
Weighly
FeaturesPricingPrivacySupportGet the app

Privacy Policy

Last updated: 11 September 2026

Weighly is built and operated by BitCraftery ("we," "our," or "us") — a trading name of a sole trader based in the United Kingdom, not a registered company. This Privacy Policy explains what information the Weighly app and our website at weighly.bitcraftery.com handle, why, and the choices and rights you have. It describes how Weighly actually works today.

Our Approach

  • Weighly needs a Weighly Premium subscription to add new entries. Anything already logged stays viewable without one. There are no adverts on any plan.
  • Your weight entries, goals, progress photos, food diary, and the workouts you record stay on your device. We do not upload them to our servers. The one exception is the personal plan: if you answer the setup questions, those answers are sent to us and to Anthropic to write your plan, as described below, and you can skip them.
  • We do not track you across other apps or websites, and we never sell your data. If you accept analytics cookies on our website, they measure how our own site is used and nothing beyond it.

Information We Handle

  • Signing in: signing in is required to add new logs (weights, food, workouts, photos and goals), to search for foods, and to receive news notifications, with Apple on iOS and with Apple or Google on Android. Anything already on your device stays there and stays viewable without signing in. The provider gives us a stable, anonymous identifier for your account and, only if you choose to share them, your name and an email address (which may be an Apple private-relay address). We store these on our servers so your account works across your devices and reinstalls.
  • On your device only: your weight entries, goals, progress photos, food and meal diary, the workouts you record, chosen units, language, theme, and reminder settings stay on your device and are not sent to us, apart from the setup answers described under Personal plan below.
  • Personal plan: if you answer the setup questions, the answers you give (age, sex, height, weight, goal, activity and eating habits) are sent to our server and to Anthropic's API to write your plan. They travel with your anonymous install identifier, never your name or email, so the plan can be stored with your account and rebuilt on a new device, and it is deleted with your account. Anthropic receives only the answers, not the identifier. Every question is optional and you can skip them all; the app then builds a plan on your device instead.
  • Workout and food-log reminders: if you turn on a workout reminder or a daily food-log reminder, they are local notifications scheduled on your device at the days and times you choose. They are created and delivered on your device, and nothing about them is sent to us.
  • Subscriptions: if you subscribe to Weighly Premium, Apple processes the purchase and tells us the subscription's status. We store that status — the product, its expiry date, and Apple's anonymous transaction identifiers — linked to your account so premium features unlock on your devices. We never receive your payment details.
  • Device and notifications: if you enable notifications, we store an app installation identifier and your device's push token — from Apple Push Notification service on iOS, or Firebase Cloud Messaging on Android — linked to your account, so we can deliver the reminders and notifications you ask for.
  • Food search and barcodes: when you search for a food by name or scan a barcode, the text you typed or the barcode number is sent to our servers to find the food, along with your app installation identifier (used to check you are signed in). We keep searched terms and scanned barcodes — stored without who searched them — so the shared food database grows and future searches are faster. New search terms are processed on our behalf by Anthropic's Claude API to generate nutrition information; only the search text itself is sent to Anthropic, never your identity. Barcodes we don't recognise are looked up in the Open Food Facts public database, again with the barcode number only.
  • Food contributions: if a scanned product isn't found, you can type in its nutrition and submit it. The product name, barcode, and nutrition values you submit are stored on our servers and join the shared food database, without your name or identity attached.
  • Camera: barcode scanning uses your camera. What the camera sees never leaves your device and is not recorded — only the detected barcode number is looked up.
  • Location: on iOS, if you start an outdoor workout that covers ground, Weighly uses your location to record its route, distance, and pace. It stays on your device, saved with the workout in Apple Health, and is never sent to us.
  • Workout goal alerts: if you set a target for a workout you record, Weighly asks to send you a notification when you reach it. That alert is created and delivered on your device, and nothing about it is sent anywhere. Allowing notifications for it also lets Weighly register your device's push token with us, as described above, so the reminders you have turned on can be delivered.
  • First-milestone reminder: if you allowed notifications during setup and left Reminders on, Weighly queues a single notification for the following evening saying your first milestone is waiting. It is created and delivered on your device, nothing about it is sent to us, and it is dropped once you log your first food or turn Reminders off.
  • Help and feedback: when you contact us through Help and Feedback, we receive the message you write and up to four photos you choose to attach, so we can respond and improve the app. Photos are re-encoded before they are sent, which removes any location or other metadata stored in them, though a photo or screenshot still shows whatever is in it. Feedback is kept for up to 12 months.
  • App analytics: we collect pseudonymous usage events (such as which screens you open or when a weight is logged) using Google Firebase Analytics, tied to your account's anonymous identifier so that you are counted once across your devices, and we use them only to see how the app is used and to improve it. These events never include your weight, body measurements, or other health figures. In the UK and outside the European Economic Area this is on by default and you can switch it off at any time in Settings under Usage Analytics; in the European Economic Area and Switzerland it stays off until you agree in the app, and you can change your choice at any time in Settings. This bullet describes analytics inside the app; analytics on our website is separate, cookie-based, never tied to your account, and described under Cookies and Website Analytics below.
  • Anonymous usage statistics: so we know how many people use Weighly and how many come back, the app tells our server when a small number of milestones happen, such as the app being opened for the first time that day, setup being finished, a first weight being logged, or the Premium page being shown, and whether an installation opens the app again on its first, seventh and thirtieth day. Each message carries only the name of the milestone, the app version, and the platform. It contains no identifier of any kind: no account, no installation identifier, no device identifier and no cookie. Our server adds one to that day's total and stores nothing else, not even the network address the message arrived from, which is used only to limit abusive traffic and is never kept with the count. So there is no record of you as an individual, and the totals cannot be tied to you, your device or your IP address. Because it identifies nobody, this is on by default; you can switch it off at any time in Settings under Anonymous Usage Statistics. These totals are not the app analytics described above, which have their own switch, and they are separate from website analytics too.
  • Crash and performance data: to keep the app stable, we collect crash reports and basic performance diagnostics using Google Firebase Crashlytics, linked to your account's identifier so that when you report a problem we can find the crash that caused it. Crash reports never include your weight, body measurements, or other health figures. This is on by default and you can turn it off in Settings.

Apple Health

On iOS, if you choose to connect Apple Health, Weighly reads your workouts, active and resting energy, heart rate, step count, workout distances, and the routes of outdoor workouts to show your activity, to personalise your daily calorie target, and to draw your route on a workout video you choose to share. If you record a workout in the app, Weighly also saves that workout to Apple Health. Weighly can also show a notification when a workout from Apple Watch or another app reaches Apple Health, with the calories burned and the change to that day's food budget; it is generated on your device from your Apple Health data and nothing is sent to us.

  • Connecting is optional. The app works without it, and you choose exactly which categories Weighly may read and write. Weighly asks for reading and writing in the same Health sheet, so you answer once. If you connected Health in an earlier version, iOS asks you only about what is new: saving the workouts you record, and reading outdoor workout routes.
  • Health data is read, written, and processed on your device only. It is never sent to our servers, to Firebase, or to any other third party, and it is never included in analytics or crash reports.
  • We never use Apple Health data or your workout location for advertising or marketing, for improving our service, or for any purpose beyond showing you your own activity, and we never sell it or disclose it to data brokers. Apple's rules for apps that use HealthKit prohibit all of this too.
  • What Weighly writes: when you record a workout in the app, Weighly saves it to Apple Health with the calories burned and, where they were measured, the distance covered and the route. It writes no other measurements about you, and never a heart rate, because your phone has no heart-rate sensor. Alongside the workout it records the details any workout carries: the activity, when it started and ended, whether it was indoors, and the device that saved it. The calories are an estimate, not a measurement.
  • You can review or withdraw Weighly's access at any time in the Health app (Profile → Apps) or in iOS Settings → Privacy & Security → Health. Withdrawing access does not affect the rest of the app.

Location

On iOS, Weighly uses your location for one thing: recording the route, distance, and pace of an outdoor workout you start in the app. Indoor workouts never ask for it, and neither do outdoor activities that do not cover ground.

  • Only during a workout: Weighly asks for permission when you start an outdoor workout that covers ground, not at launch and not during onboarding. It asks for While Using the App access, never for Always, and treats Always the same way if you choose it in iOS Settings.
  • Where it goes: while the workout is running, the fixes are held in a file inside the app's own storage on your device, and when you finish they are saved with the workout in Apple Health as a workout route. We never receive your location: it is not sent to our servers, to Firebase, or to any other third party, it never appears in analytics or crash reports, and it is never used for advertising or marketing. The one way a route leaves your device is if you send it yourself, because a workout image or video you export can have your route drawn on it.
  • In the background: recording continues while your screen is locked or you are in another app, so a workout is not cut short, and iOS shows the blue location indicator while it does. If you chose Allow Once, iOS ends that grant when you leave the app and the trail stops; the workout screen tells you when this happens. If the app is closed or crashes mid-workout, Weighly picks the workout up, and its location recording, the next time you open it, and ends a recording that has been left running for more than twelve hours. Otherwise recording and the indicator continue until you end the workout, so end it when you finish.
  • Precise or approximate: with approximate location, no route, distance, or pace can be recorded at all. The workout screen offers to switch to precise location for that one workout, and if you decline, the workout carries on without them.
  • Refusing and withdrawing: you can change Weighly's location access at any time in iOS Settings, under Weighly and then Location. If you refuse, workouts still record; you lose the route, distance, and pace, and nothing else. A distance goal is the exception: it needs location turned on, and precise location, or there is no way to measure it.

Our Website

This section covers visiting weighly.bitcraftery.com — it applies to you even if you never install the app.

  • Server logs: like almost every website, our server briefly processes standard technical data when you request a page — your IP address, the page requested, date and time, and your browser type — solely to deliver the page and keep the site secure. We do not build access logs of visitors ourselves. The site is hosted for us by DigitalOcean, and traffic passes through Cloudflare for security and performance; both process this technical data on our behalf as part of serving the site, on the lawful basis of our legitimate interests in running it securely.
  • Bot protection: Cloudflare may set a strictly necessary cookie, __cf_bm, to tell humans and abusive bots apart. It lasts about 30 minutes, identifies no one to us, and, being strictly necessary, needs no consent.
  • Nothing else: the website sets no other cookies and loads nothing from third parties unless you accept analytics, as described next.

Cookies and Website Analytics

When you first visit, the site asks whether we may use optional analytics cookies. Nothing analytics-related is loaded, and no analytics cookie is set, unless you choose Accept — declining, ignoring, or dismissing the banner all mean no. The site works identically either way.

  • If you accept, we load Google Analytics (Google's gtag.js), which sets first-party cookies: _ga (a random identifier that distinguishes your browser from others on this site; kept for 13 months) and _ga_<stream> (keeps track of your browsing session; kept for 13 months). These tell us things like which pages are visited and roughly where visitors come from. They identify your browser on our site only and are not used to follow you around the web.
  • Google processes this data on our behalf, partly outside the UK, and your IP address is processed transiently to derive an approximate location. Analytics event data is retained by Google Analytics for 2 months, then deleted. We have turned off the Google settings that would share analytics data for Google's advertising purposes, and the website has no adverts.
  • Website analytics is never linked to a Weighly account, and website and app analytics are never joined.
  • Your choice itself is remembered on your device (a small "weighly.cookieConsent" record in your browser's local storage, kept for up to 12 months). Storing it is strictly necessary — it is how a "no" is remembered.
  • You can change your mind at any time using the Cookie choices link in the footer of every page. Withdrawing consent stops measurement immediately and deletes the analytics cookies from your browser.

How We Use Your Information

  • To provide and secure your account and the app's features.
  • To send the reminders and notifications you enable.
  • To run food search and barcode lookup, and to grow the shared food database.
  • To record the route, distance, and pace of an outdoor workout you start in the app, and to save that workout to Apple Health.
  • To respond to your feedback and support requests.
  • To fix crashes, improve stability, and understand how the app is used so we can improve it.
  • To count, without identifying anyone, how many people use the app and how many come back.
  • With your consent, to measure how our website is used so we can improve it.
  • To meet our legal and regulatory obligations.

Legal Bases (UK and EU GDPR)

  • Performance of a contract: running your account and providing the app.
  • Consent: app analytics in the European Economic Area and Switzerland, website analytics cookies (required by the Privacy and Electronic Communications Regulations as well as UK GDPR), and, where required, notifications. Apple Health data is a special category of personal data, and your workout location is tied to it, so Weighly relies on the explicit consent you give in the iOS Health and Location prompts. You can withdraw consent at any time: in the app's Settings, in iOS Settings for Health and location, or via the Cookie choices link on our website.
  • Legitimate interests: keeping the app and website stable and secure (including the website's server logs and bot protection); responding to your support requests; counting, in aggregate and without identifiers, how many people use the app so we can see whether it is working (you can object by switching Anonymous Usage Statistics off in Settings); and, in the UK and outside the European Economic Area, understanding how the app is used so we can improve it. UK law (the Privacy and Electronic Communications Regulations, Schedule A1, since February 2026) allows this kind of statistical measurement with a way to object rather than a prior question, and you can object at any time by switching Usage Analytics off in Settings.
  • Legal obligation: where the law requires us to retain or disclose information.

Storage, Retention, and Security

  • On-device data remains until you delete it or remove the app.
  • Workout recording files: while a workout is being recorded, and while a finished one waits for you to say how hard it felt, Weighly keeps the session, route included, in a file inside its own storage on your device. Weighly marks these files so they are left out of iCloud backups, and clears them as soon as the workout is saved or discarded. If Weighly does not have permission to save to Apple Health, a finished workout is kept the same way so the Workout tab can offer to add it later; it stays until you add or delete it there, and at most the twenty most recent are kept. All of them go when you delete the app.
  • Workouts saved to Apple Health stay in Apple Health. They belong to the Health app, not to Weighly, so withdrawing Weighly's Health access or deleting the app does not remove them. A workout Weighly recorded can be deleted from inside the app, which also asks Apple Health to remove the energy, distance, and route saved with it; Weighly will not delete a workout it did not write. You can delete any workout in the Health app itself.
  • Account and server-side data is kept while your account is active; feedback is kept for up to 12 months.
  • Searched terms, scanned barcodes, and the food entries they produce are kept in the shared food database indefinitely — they are stored without your identity and cannot be traced back to you.
  • Anonymous usage statistics are kept only as daily totals per app version and platform, indefinitely, because they contain nothing about any individual.
  • Data sent to our servers is transmitted over encrypted connections (HTTPS).
  • Website analytics event data (if you accept analytics cookies) is retained for 2 months; the analytics cookies themselves last up to 13 months, and your consent choice is kept on your device for up to 12 months before we ask again.
  • Deleting your account removes your account and all associated server-side data, including installs, push tokens, feedback, any attached images, and your personal plan.

Who We Share It With

  • Apple, for Sign in with Apple and for delivering push notifications to iOS devices.
  • Google, for signing in with Google on Android and for delivering push notifications to Android devices through Firebase Cloud Messaging.
  • Google Firebase, which processes crash, performance, and analytics data on our behalf.
  • Google, which processes website analytics (Google Analytics) on our behalf if you accept analytics cookies on our website — the data described under Cookies and Website Analytics only, never anything from the app.
  • Anthropic, whose Claude API processes new food-search terms on our behalf to generate nutrition information (the search text only), and, if you ask for a personal plan, the setup answers you gave (age, sex, height, weight, goal, activity and eating habits) to write it. Never your identity: no name, email or account identifier is sent with either.
  • Open Food Facts, a public food database our servers query with the barcode number only.
  • DigitalOcean, which hosts our servers and website, and Cloudflare, which provides security and performance for the website — both process technical data (such as IP addresses) as part of serving it.
  • We do not share your data with advertisers or data brokers, and we do not sell it.

International Transfers

Our service providers — including Apple, Google (for sign-in, notifications, Firebase, and website analytics), DigitalOcean, Cloudflare, and Anthropic — may process data outside the United Kingdom and the European Economic Area, including in the United States. Where they do, the transfer is protected by appropriate safeguards: the UK Extension to the EU–US Data Privacy Framework where the provider is certified under it, and otherwise the UK Addendum to the EU Standard Contractual Clauses or the ICO's International Data Transfer Agreement.

Your Rights

  • You can access, correct, export, or delete your data.
  • You can turn off Weighly's access to Apple Health or to your location at any time in iOS Settings. Everything else in the app carries on working; only a distance goal for a workout you record needs location. Apple Health data and workout location never reach us, so there is nothing for us to hold, export, or delete on our side.
  • You can switch app analytics off (or, in the European Economic Area and Switzerland, withdraw your consent to it), switch anonymous usage statistics off, or disable crash reporting at any time in Settings, and withdraw website analytics consent via the Cookie choices link in the site footer.
  • You can delete your account and all associated data from within the app, using Delete Account and All Data in your Account settings.
  • If you are in the UK or EU, you can complain to your data protection authority (in the UK, the Information Commissioner's Office).

Tracking and Advertising

Weighly does not use the advertising identifier (IDFA), shows no adverts, and does not track you across other companies' apps or websites. You will not see an App Tracking Transparency prompt because we do not track. Our website offers optional Google Analytics, only with your consent: its cookies are first-party, they identify your browser on our site only, they are not used to follow you around the web, and we have disabled the Google settings that would use this data for advertising.

Children

Weighly is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us with personal information, please contact us and we will remove it. Weighly can be used from 13, and for anyone under 18 the same protections apply as to everyone else: location is used only during a workout you start yourself, it is off until then, iOS shows the blue indicator while it runs, and a route leaves the device only if you export a workout image or video yourself.

Changes to This Policy

We may update this Privacy Policy from time to time. We will revise the date above and, for significant changes, let you know within the app.

Contact Us

If you have any questions about this Privacy Policy or your data, please get in touch with BitCraftery at [email protected].

Weighly

Track your weight, see the trend, and keep the habit — privately.

Product

FeaturesScreenshotsPricingGet the appAbout BitCraftery

Help

Support & FAQ[email protected]

Legal

Privacy PolicyTerms of UseDelete Your Account
© 2026 Weighly by BitCraftery, a UK sole trader.Made in the UK 🇬🇧