This Privacy Policy describes how Productility LLC, a Utah limited liability company ("Productility," "we," "us," or "our") collects, uses, discloses and protects personal information in connection with the Productility mobile application, the productility.app website and related services (together, the "Services"). By using the Services, you acknowledge that you have read and understood this Privacy Policy.
1. Information We Collect
We collect the following categories of information.
| Category | Description | Source and storage |
|---|---|---|
| Account information | Email address, username and password (stored only in hashed form), and optionally a display name, biography and profile photograph | Provided by you. Stored on our servers |
| Health and fitness information | Food and nutrition logs, recipes, meal plans, leftovers, foods or recipes you ask to see less of, workouts, exercise sets and weights, body-weight entries, and setup information such as sex, birth year, height, weight, activity level and goals | Provided by you. Stored on your device and, while you are signed in, in your account backup on our servers. Entries in a shared diary are also stored on our servers so everyone in that diary can see them |
| Apple Health information | If you turn on Apple Health in the app: the workouts, body weight, water and food you log, which the app saves to Apple Health, and the body weight and active energy the app reads from Apple Health | Exchanged on your device through Apple Health, only for the types you allow, and you can turn it off in the app or change what it may access in the Health app at any time. Information read from Apple Health stays on your device: it is not sent to our servers, included in your account backup or shared with anyone, and it is never used for advertising or marketing |
| Notes and settings | Notes, reminders, shopping lists, stores and staples (items you always have), and app preferences | Provided by you. Stored on your device and in your account backup while you are signed in. A shared diary's shopping list is also stored on our servers so everyone in that diary can see it |
| Photographs and videos | Media you attach to notes, workouts or recipes | Stored only on your device. They are not sent to our servers, and neither we nor anyone working on our behalf can see them. If we introduce a backup for them, it will be end-to-end encrypted so that only you can open them |
| Food label photographs | Photographs you take of a product's packaging and Nutrition Facts panel in order to add a food that is not yet in our database, and the food information read from them | Sent to our servers and to OpenAI so that the label can be read, and stored on our servers so that our staff can check the food before it is added to the shared database. Photographs of anything other than food are refused and are not kept. The photographs are deleted when you delete your account. A food approved by our staff remains in the database with no link to you |
| Uploaded diaries, workouts and recipes | Screenshots, photographs and files you choose in Import food or Upload workout, and the text, links or pictures you add with Use the real recipe | Export files in a format the app recognizes are read on your device and are not sent. Screenshots, photographs and other files are sent to our servers and to OpenAI so that their contents can be read, and are not stored on our servers. What is read from them is added to your app only after you review it |
| Community content | Posts, photographs, videos, captions, comments, likes, saves, follows, blocks and reports, and Levels (activity streaks and counts) | Provided by you through Hub. Stored on our servers |
| Recipe import information | Links you submit, the recipe content derived from them, and the date you accepted the recipe import terms | Stored on our servers. We keep a record of which accounts imported each link, so that only members who imported a recipe can share it to Hub, and so that our team can review recipes shared there. For videos with no written recipe, we also record which ones were read for your account and when, to count them toward the monthly limit in our Terms of Service. These records are never shown to other members and are deleted when you delete your account |
| Ingredient match feedback | When you save an imported recipe: each ingredient line, the food it was matched to, and the food and amount you saved it with. If you send a report with "Something's off?": what you reported, the ingredient it is about, and any note you write | Stored on our servers under a one-way tag, which we use only to tell one member's changes from another's and to set aside changes from a source whose changes keep failing our automated checks. It is not stored with your name, email address or account. We use it to improve how ingredients are matched to foods. A change you make that passes automated checks may be applied to other members' imports; it never identifies you. Your feedback and reports are deleted when you delete your account. An improvement already learned from them is kept: it holds a line of a public recipe and a food, and nothing about you |
| Membership information | Email verification status, and the status of your subscription as reported by the App Store or Google Play through RevenueCat, including whether a free trial is in progress and when the current period ends | Stored on our servers. We do not receive your payment details |
| Free days of Premium | If you start the free days of Premium: when they end, and the recipe links you import during them (to keep them to the limit in our Terms of Service). To give each person the free days only once, we also keep a one-way fingerprint (a cryptographic hash) of your email address, worked out so that addresses delivering to the same inbox give the same fingerprint (for example, ignoring "+" additions, and dots in Gmail addresses). Your device also keeps a note in its secure storage that it has had the free days | The end date and links are stored on our servers with your account. The fingerprint is stored on our servers apart from your account: it does not contain your email address, cannot be turned back into it, and can only be used to check whether an address we are given has had the free days. It is kept after you delete your account, so that deleting and signing up again does not give the free days again. The note on your device stays on your device and is never sent to us; it may remain after you delete the app |
| Usage information | The days you use the app while signed in, and your device platform (iOS or Android) and app version on those days | Recorded on our servers when the app connects while you are signed in. Used only in aggregate, for example to count how many people used the app in a given week. Deleted with your account |
| Support requests | Your name, email address, message and any details you include when you contact support through our website or by email, and our replies. When you send a bug report or idea from the app, also the screen it was sent from, your phone model and app version, and your username and email address if you are signed in | Provided by you. Stored on our servers so that we can respond and keep a record of the conversation. Support requests are read and answered by a person; we do not use automated or AI systems to handle them |
| Beta access requests | Your email address and the kind of phone you use (iPhone or Android) when you ask to join the beta on our website, and the date you asked | Provided by you. Stored on our servers so that we can invite you to the beta and tell you when Productility launches. We do not send you anything else, and you can ask us at any time to take you off the list |
| Search and scan queries | Food search terms and product barcodes | Processed to return results and not associated with your account. We keep only an aggregate count of scans per product |
| Device push token | A token issued for your device by its notification service, and your device platform (iOS or Android) | Sent to our servers while you are signed in and have allowed notifications, so that we can send push notifications such as shared diary invitations. Removed when you sign out, delete your account or the token stops working |
| Crash reports | When the app closes unexpectedly or hits an error: the error and where in the app it happened, the app version, the device model and operating system version, and the screens and server requests (without their contents) that led up to it. Crash reports contain no account information, IP address, screenshots, or text you typed or tapped | Sent by the app to Sentry. Used only to find and fix problems |
| Technical information | Internet Protocol (IP) address | Held briefly in server memory to prevent abuse and enforce rate limits. When you use the website contact form or beta request form, a one-way hash of it is kept for up to 24 hours for the same purpose. It is not otherwise stored |
Device permissions. With your permission, the Services access your device's camera (to photograph meals, record exercise and scan barcodes), photo library (to attach media), microphone (to record audio with exercise videos), notifications (to deliver reminders and push notifications) and Apple Health (to save and read the health information described above). Each permission is optional and can be withdrawn at any time in your device settings, although the related feature will not work without it.
Information we do not collect. We do not collect precise location, contacts or advertising identifiers, and we do not track you across other companies' apps or websites. We do not use third-party analytics or advertising tools, and our website does not use advertising or analytics cookies.
2. How We Use Information
We use personal information to:
- provide, maintain and improve the Services;
- understand how the Services are used, in aggregate across all users (for example, how many people are active or return after signing up);
- back up and restore your data across your devices;
- calculate nutrition and training targets and estimates;
- operate Hub, including displaying your profile and content to other users according to your settings;
- process recipe imports;
- respond to your support requests;
- invite you to the beta and tell you when Productility launches, if you asked us to;
- send account communications, such as email verification and password-reset codes;
- protect the security and integrity of the Services, prevent fraud and abuse, and enforce our Terms of Service; and
- comply with legal obligations.
We do not sell personal information, and we do not use it for targeted advertising.
3. Information Visible to Other Users
- At all times: your username and profile photograph appear alongside any content you post or comment on.
- With a public profile: your display name, biography, public cookbook, followers and following lists, and Levels are also visible.
- With a private profile: only your username and profile photograph are visible. Your cookbook, connections, Levels, display name and biography are hidden from other users.
- In a shared diary: the other members of a shared food diary can see and add to its entries, including the day totals and the portions each member records, and they share its shopping list. They also see your username and profile photograph. They cannot see your other diaries, targets or logs, and you can leave a shared diary at any time.
- Never: your email address; food and exercise logs outside a diary you share; notes; body-weight entries; setup information; and any content you have not posted. A workout you share by link carries its exercises, sets and reps only; your weights are never included.
When you block a user, neither of you can view the other's profile, posts or comments.
Community safety. To keep Hub safe, new posts and comments are screened automatically against a word list: abusive language is refused, and likely spam is flagged for review. New posts are also checked automatically by OpenAI's moderation service, which reads the post's text and pictures, including frames from any video; a post it finds unsafe is held, visible only to you, until our team reviews it. The text of each post or comment and the posting username are then passed to our moderation team, who may remove content that violates our Terms of Service. When you submit a report, the reported content, the reason you selected, and your username and email address are recorded in our support system so that a member of our team can review the report and follow up with you if needed. Reports are reviewed and decided by people, never by automated or AI systems, and the reported user is never told who submitted a report.
4. Recipe Imports
Recipe import uses artificial intelligence to extract recipes from publicly available online content. When you first save an imported recipe, it is added to Hub anonymously: other members never see your name or that you imported it, with credit to the original creator. You are asked to agree to this before your first import. Any changes you make to the recipe afterwards remain in your private cookbook. When you save an imported recipe, the app also tells us which ingredient matches you kept and which you changed, as described in Section 1, so that matching improves over time. Recipes you create yourself are never shared unless you choose to post them.
5. How We Share Information
We share personal information only as described below.
Service providers. We engage the following providers to operate the Services. Each receives only the information necessary to perform its function and is bound to use it solely on our behalf.
| Provider | Information received | Purpose |
|---|---|---|
| OpenAI | The publicly available video, audio, caption and text of a recipe link you import, the ingredient lines of imported recipes with the foods matched to them, and the food label photographs you take to add a food; the screenshots, photographs and files you upload in Import food or Upload workout that the app cannot read on your device, and the text, pages or pictures you add with Use the real recipe; and the text and pictures of new Hub posts. No account information is sent, and requests to read your uploads ask OpenAI not to store the result | Extracting recipes from imported videos and pages, matching ingredients to foods in our catalog, reading nutrition labels from your photographs, reading the food diaries, workouts and recipes you upload, and screening Hub posts for unsafe content |
| Jina AI | The address of a public recipe page or link you import, or a recipe page that a post you import links to. No account information is sent | Reading the public content of recipe pages and links you import |
| Open Food Facts | Product barcodes not yet in our database, without any user identifier | Retrieving product nutrition information |
| Resend | Your email address and username | Delivering verification and password-reset emails |
| Expo | Your device push token and the text of the notification, such as a shared diary invitation or comment; and, when the app checks for an update, your device platform, app version and a random identifier for this installation of the app | Delivering push notifications to your device, and delivering app updates |
| Sentry | Crash reports, as described above | Recording app crashes and errors so we can fix them |
| Cloudflare | Website requests and support messages, including your name and email address when you contact support; community reports and the text of new posts and comments, for review by our team; traffic between the app and our servers | Hosting this website, receiving support email, storing support conversations, operating our report and moderation tools, and securely connecting the app to our servers |
| DigitalOcean | Information stored on our servers | Hosting the servers that run the Services |
| Apple Inc. (and Google LLC for the Android app) | Purchase and subscription status | Processing in-app purchases. We do not receive your payment card details |
| RevenueCat | Your account ID and your subscription's purchase, renewal and expiry details from Apple or Google | Managing Premium subscriptions and telling our servers when one starts, renews or ends. We do not receive your payment card details |
To process a recipe import, our servers also retrieve the public content at the link you submit (for example, from TikTok, Instagram, YouTube, Facebook, Pinterest or X), or at a recipe page that a post you import links to.
Legal requirements and protection of rights. We may disclose information if we believe in good faith that disclosure is necessary to comply with applicable law, regulation, legal process or a governmental request; to enforce our Terms of Service; or to protect the rights, property or safety of Productility, our users or the public.
Business transfers. If Productility is involved in a merger, acquisition, financing or sale of all or part of its assets, personal information may be transferred as part of that transaction. Any successor will remain bound by the commitments in this Privacy Policy with respect to information collected before the transfer.
6. Data Retention
We retain personal information for as long as your account remains active or as needed to provide the Services. The fingerprint kept for the free days of Premium is kept indefinitely, as described in Section 1, so that they can only be had once. Sign-in sessions expire after 30 days, and email verification and password-reset codes expire within minutes. When you delete a Hub post or comment, or return a recipe to your private cookbook, the associated photographs and videos are deleted from our servers unless they are still in use elsewhere, for example in another post or as your profile photograph. Support conversations are kept for as long as needed to assist you and to maintain a record of the request. Beta access requests are kept so that we can invite you and tell you when Productility launches. Reports and moderation records are kept for as long as needed to review them and to maintain a record of the decisions made. We may retain limited information where required by law or to resolve disputes.
7. Account Deletion
You may delete your account at any time in the app under Profile > Account > Delete account. Deletion is confirmed with your password. Deleting your account permanently removes your account information, sign-in sessions, account backup, any backed-up photographs and videos, food label photographs of foods not yet approved, and your Hub posts, comments, likes, follows and Levels. Recipes previously added to Hub through anonymous import are not linked to your account and therefore remain available. Food you logged in a shared diary stays in that diary and remains visible to its other members. Deleting your account does not cancel an App Store or Google Play subscription or free trial, which must be cancelled in your store account settings. Information stored on your device remains there until you delete the app. Deletion does not remove the fingerprint kept for the free days of Premium (see Section 1), which does not contain your email address and is not linked to anything else.
8. Your Choices and Rights
You may:
- use the Services without an account, in which case your information remains on your device;
- make your Hub profile private, block other users, delete your posts and comments, return recipes to your private cookbook, or leave a shared diary;
- manage reminders and notifications in the app or in your device settings; and
- request access to, correction of, or deletion of your personal information by contacting us at support@productility.app. We will respond within 30 days.
Depending on where you live, including the European Economic Area, the United Kingdom and California, you may have additional rights, such as the right to object to or restrict certain processing, the right to data portability, and the right to lodge a complaint with a data protection authority. We will not discriminate against you for exercising any of these rights.
9. Data Security
We use reasonable administrative, technical and organizational measures to protect personal information. Passwords are stored only in hashed form, and data in transit between the app, this website and our servers is encrypted with HTTPS. However, no method of transmission or storage is completely secure, and we cannot guarantee absolute security. We encourage you to use a password that is unique to your Productility account.
10. Children's Privacy
The Services are intended for users aged 16 and older, and the setup process asks for your birth year. We do not knowingly collect personal information from anyone under 16. If you believe a person under 16 has provided us with personal information, please contact us and we will delete it.
11. International Data Transfers
Our servers are located in the United States. If you access the Services from another country, your information will be transferred to, stored in and processed in the United States, where data protection laws may differ from those of your jurisdiction. We take appropriate measures to ensure that your information remains protected as described in this Privacy Policy.
12. Changes to This Privacy Policy
We may update this Privacy Policy from time to time. When we do, we will revise the effective date above and, for material changes, notify you in the app before they take effect. Continuing to use the Services after a change takes effect constitutes acceptance of the updated Privacy Policy.
13. Contact Us
For questions about this Privacy Policy or to exercise your rights, please contact:
- Productility LLC
- Draper, Utah, United States
- support@productility.app