Privacy Policy - Good Fork, LLC

Good Fork helps you save recipes, make them fit the way you eat, plan meals, shop for ingredients, and cook with less friction. This Privacy Policy explains what information Good Fork, LLC collects, how we use it, and the choices you have, including choices available to people in California, the European Economic Area and the United Kingdom.

"Good Fork," "we," "us," and "our" mean Good Fork, LLC, a Washington limited liability company. This policy applies to the Good Fork apps for iPhone, iPad, Apple Watch, Android and the web, getgoodfork.com and its subdomains, launch-update signups, and related services (together, the "Services").

Our approach to privacy

Good Fork is built by people who use meal-planning apps too, and we want to treat your information the way we would want our own treated.

We use data to run Good Fork, understand what is working, and make the app more useful for everyone. We are not interested in building an advertising profile about you or turning your personal information into the product, and we do not sell it.

Some features, including recipe imports and Remix, use AI. Your account information, household preferences and allergies, and photos or scans you upload directly to Good Fork use an AI configuration that is not used for model training. Requests from the EEA, UK, Switzerland and California, and requests whose region we cannot determine, also use that privacy configuration. Outside those regions, some recipe content imported from public web pages or social posts, text you type or paste, and grocery-matching text may be processed under a data-sharing configuration that can be used to improve AI systems, as explained in section 3.

The rest of this policy provides the details: what we collect, why we collect it, who processes it, how long we keep it, and the choices and rights available to you.

1. Information we collect

1.1 Information you give us

1.2 Information Collected Automatically

Device and technical information. Device type, operating system, app version, language, time zone, and basic performance measurements.

Approximate location, if you allow it. Good Fork's servers do not receive or store your coordinates. Your device may send approximate coordinates directly to Apple, Google or Open-Meteo for the features below:

• Weather. To show the week's weather on your meal plan, iPhone and iPad use Apple WeatherKit with Apple's reduced-accuracy location. Android and web use Open-Meteo with coordinates rounded to about 1 km. These services also receive the network information needed to serve the request, such as your IP address.

• Finding a store. If location is already allowed when you choose a store, the app fills in your ZIP code. Your coordinates go only to your phone's own lookup (Apple's on iPhone, Google's on Android), never to Good Fork's servers. Only the ZIP code goes to the store search, as if you had typed it, and only the store you choose, with its address, is saved with your household.

App diagnostics and telemetry. Expo receives pseudonymous, per-install app telemetry such as app starts, performance measurements, crashes and JavaScript errors, navigation and update events, device model, operating system, language, app/build version, a random per-install identifier, and the IP address used to connect. Good Fork does not attach your account, household or recipe ID to this Expo telemetry.

Good Fork product analytics. Our own funnel events use small labels such as method, source and counts without account identifiers. Remix analytics are different: they are linked to the account, household and recipe while active so we can understand the feature. When the account is deleted, those identifiers are removed; the records are retained for up to 24 months. Kid accounts are excluded from Good Fork's product and Remix analytics. Expo performance and crash telemetry may still include a Kid's installation, but Good Fork does not label that telemetry with the person's Good Fork account, household, recipe or role.

Website analytics. The website uses Google Analytics to understand visits. Visitors in the EEA (including EU territories), the UK and Switzerland, or whose country we cannot tell, are asked first, and nothing from Google loads unless they accept. Everyone else is not asked: analytics load unless their browser sends the Global Privacy Control signal or they have turned analytics off from "Cookie settings" in the footer of every page. See the Cookie Policy.

Server and security logs. Our hosting and infrastructure providers process IP addresses, request times, device information and security events to deliver, protect and troubleshoot the Services. We look up the country of an IP address, and in the United States its state, without storing it, to decide which AI configuration a request uses (section 3).

Age information from app stores. Where a law requires it, such as in Texas, the app asks Apple (Declared Age Range) or Google Play (Age Signals) for your age range when it opens. We never ask your age ourselves. The age range is used only on your device to apply our age rules (Terms of Service, section 2) and is never stored or logged.

For a teen Kid account in those places, we store a pseudonymous keyed hash (HMAC) of Apple's app transaction ID or Google Play's install ID, linked to the account, only so that a parent's withdrawn approval can reach the account. We do not store the store-reported age range, birth date or precise age, although the Kid role, this link record and an account pause can indicate that the account belongs to a minor. Apple withdrawal notices reach us through RevenueCat; Google withdrawal status is checked periodically. We delete the hash with the account or after 13 months without use.

2. How we use information

We use information to:

• provide accounts, saved recipes, households, meal plans, grocery lists, cooking-along features and timers;

• import recipes and bring them into Good Fork's format and your language, including with OCR and AI;

• apply Remix and fit recipes to your household's preferences;

• show weather for the week you're planning and fill in your ZIP code when you choose a store, if you allow location;

• search for products and stores and send items to retailers you choose;

• process subscriptions, restore purchases and maintain your plan;

• send account emails and the launch updates you ask for;

• operate, secure, debug, measure and improve the Services, including our ingredient library: ingredient names from recipes that do not match the library may be reviewed by our staff, without your account details;

• prevent fraud, abuse and unauthorized access; and

• comply with legal obligations, including app-store age checks where the law requires them, and enforce our agreements.

2.1 Legal bases (EEA and UK)

3. Recipe imports, images, OCR and AI

When you ask Good Fork to read a recipe, a cookbook page, a social post, a file from another app or other source, we process the text, link, file or image needed to do it.

AI providers. Customer-facing AI features use OpenAI to read, format, translate, clean up and Remix recipes and to match grocery items to store products. Anthropic is used for some internal staff tools; customer content is not routed there. Good Fork does not add your name, email or Good Fork account identifier to AI requests.

Two configurations. We use two configurations with our AI provider: one in which content is never used to train models, and one, under a data-sharing arrangement, in which the provider may use content to train and improve its models. Which one a request uses depends on where you are and what is sent:

Never used for training, wherever you are: photos and scans you upload directly to Good Fork; scanned PDFs; Remix content, including household recipes, preferences, dislikes and allergies; repairs of scanned recipes; account information; and staff-tool processing.

In the EEA, the UK, Switzerland and California: everything you send uses the configuration that is not used for training. We determine the request region from the request's IP address. If the region cannot be determined, we use the same privacy configuration.

Everywhere else: content imported from public web pages and social posts - including public page text, structured data, captions, transcripts and public images - as well as recipe text you type or paste, fixes and translations of those imports, and grocery ingredient/product text may use the data-sharing configuration. Good Fork does not add your account identifiers, but text you provide can itself contain personal information, so do not include personal information you do not want processed.

For AI prompts, Good Fork sends only the source page's origin and path, without its query string. For public social-post retrieval, we remove common tracking codes while keeping identifiers needed to retrieve the post. A website that Good Fork fetches to import a recipe may still receive the full URL you provided.

California. Requests identified as coming from California use the configuration that is not used for training. We determine California routing from the request's IP address using offline DB-IP data; DB-IP does not receive the request. See section 9.1 for California privacy rights.

Social posts. To read a public social post you import, we send a cleaned version of its link to a service that retrieves public posts. We remove common tracking parameters and keep only parameters needed to identify the post. The source link saved with your recipe is also cleaned of common tracking codes.

Images. Photos and images in your recipes are stored privately for your household and deleted when the household is deleted. A photo you take for a scan is held briefly while it is read and deleted within a day if you do not keep the recipe.

4. How we share information

Good Fork does not sell personal information for money. We disclose information only as described in this policy, including to companies and services that help operate Good Fork and to third parties you choose to interact with, such as retailers and affiliate links.

The following companies and services receive information when needed to provide the Services or when you choose to use their features:

Affiliate links. Good Fork works with an affiliate link provider. Some retailer product links pass through the provider's redirect on the way to the store. When you tap one, the provider automatically receives information needed for the web request, such as your IP address, browser or in-app-browser details, language headers, its own cookies, and the retailer product link. Good Fork sends the provider its affiliate key, the product page, and a retailer/product identifier - not your name, email, Good Fork account or household ID, or shopping list. Good Fork receives aggregate merchant-level reports such as clicks, sales and commissions, not user-level personal information.

We may also disclose information when the law requires it, to protect rights and safety, to investigate abuse or fraud, or as part of a merger, financing, acquisition or sale of assets.

5. Household sharing

You can invite people to your household. Members see the household's shared recipes, meal plans, grocery lists, preferences and members' names. The Chef can also see members' email addresses; each member can see their own email address. The Chef controls membership and roles. Sharing content with a household does not transfer ownership of that content to other members. If an adult leaves or is removed, content they chose to add to the shared household can remain available to the remaining household without the departed member's account attribution, under the household's normal controls. Removing a Kid deletes the Kid account. If the last adult deletes their account, Kid accounts are deleted first and the household is deleted when its last member is gone.

6. Retailer connections

If you connect a retailer account such as Kroger, Good Fork exchanges the data needed to search products, check availability and add items to your cart. Store searches use ZIP code; product searches use search terms, store identifiers and product identifiers; cart additions use product codes and quantities with your retailer authorization. Kroger access and refresh tokens are stored encrypted. Disconnecting or deleting your Good Fork account deletes Good Fork's stored token copies, but does not separately revoke the authorization held by Kroger; that authorization remains subject to Kroger's expiration and account controls. Retailer product images may load directly from retailer image hosts, which receive your IP address when serving the image.

7. Retention

Deleting your account. You can delete your account in Settings or request deletion by emailing privacy@getgoodfork.com. We delete your Good Fork profile, membership, stored retailer tokens, agreement record, age-assurance link records, sessions and other account-linked records; we request deletion of your RevenueCat customer record and disconnect Sign in with Apple. If you were alone in your household, the household and its content are deleted. In a shared household, content you contributed can remain without your account link. Some de-identified or unlinked analytics, staff audit records, provider logs and backups can remain under the retention rules above or the provider's own retention schedule. Deleting your Good Fork account does not cancel a subscription; cancel it through the channel where you purchased it. Deleting or disconnecting Good Fork also does not necessarily revoke authorizations held by Google, Facebook, Kroger or other third-party services.

8. International data transfers

The Services and our providers may process information in the United States and other countries. If you use the Services from the EEA or UK, your information may be transferred to countries that do not provide the same level of protection as your own. Where required, we use lawful transfer mechanisms and safeguards, which may include the European Commission's Standard Contractual Clauses, the UK International Data Transfer Addendum, adequacy decisions, or other mechanisms available under applicable law. Ask privacy@getgoodfork.com for details.

9. Your privacy rights

You can update your information, manage your household, disconnect retailers, change allergy and dietary information, turn off location in your device settings, unsubscribe from emails with one click, and delete your account, all in the app or from our emails.

To make a privacy request, email privacy@getgoodfork.com with the subject "Privacy request." We verify requests as the law allows and respond within the time it requires.

9.1 California residents (CCPA / CPRA)

If the CCPA/CPRA applies to Good Fork, California residents may have rights to know and access, delete, and correct personal information; to opt out of sale or sharing; to limit certain uses of sensitive personal information; and not to be discriminated against for exercising those rights. Good Fork does not sell personal information for money. The affiliate-link data flow is described in section 4. Regardless of whether those statutes require it, you can turn off website analytics from "Cookie settings" in the Site footer, and we honor Global Privacy Control for website analytics. Requests from California never use the AI configuration that may train models (section 3). Email privacy@getgoodfork.com with the subject "California Privacy Request."

9.2 EEA and UK residents (GDPR / UK GDPR)

You may have the right to access, rectify, erase, restrict and port your personal information; to object to processing based on legitimate interests; to withdraw consent at any time without affecting earlier processing (for allergy information, by removing it from your household settings; for website analytics, in Cookie settings); and to complain to your local supervisory authority, such as the ICO in the UK. Email privacy@getgoodfork.com with the subject "GDPR Privacy Request."

10. Security

We use administrative, technical and organizational safeguards suited to the information we handle, including access controls, encryption in transit, encrypted storage of retailer tokens, and private storage of household photos. No system is completely secure.

11. Children

Good Fork accounts are for people 13 and older. Your own account (Chef or Sous Chef) is for people 18 and over; we do not ask for a birth date or precise age. Teens 13 to 17 can use Good Fork only as a Kid, in a household whose Chef invited them as a Kid or switched them to Kid and confirmed: "I'm their parent or guardian, or I have their permission, and they're 13 or older." We record which Chef confirmed and when. Kid accounts do not receive marketing, are excluded from Good Fork product and Remix analytics, are not asked for location access, and cannot connect retailer accounts. They may still be included in Expo's pseudonymous performance and crash telemetry, which is not labeled with a Good Fork account ID or role. Children under 13 cannot have an account; parents and guardians can manage Kid Friendly recipes and younger children's favorites from their own account. Where a law requires app-store age checks, see section 1.2. If you believe a child under 13 has provided personal information to Good Fork, email privacy@getgoodfork.com and we will delete it.

12. Changes to this policy

We will post any update with a new "Last updated" date. For a material change, we will tell you in the app or by email before it takes effect, as the law requires.

13. Contact

Privacy requests and questions: privacy@getgoodfork.com. General support: hello@getgoodfork.com. Good Fork, LLC is the data controller for personal information processed under this policy. Mailing address: Good Fork, LLC, c/o Registered Agents Inc, 100 N Howard St, Ste R, Spokane, WA 99201, United States.

If you have a privacy concern, please contact us first at privacy@getgoodfork.com so we can try to resolve it. Depending on where you live, you may also have the right to complain to a privacy regulator. EEA residents may lodge a complaint with the data protection authority in their country of residence, work, or the alleged infringement. UK residents may complain to the Information Commissioner’s Office (ICO). California residents may submit an applicable privacy complaint to the California Privacy Protection Agency. U.S. consumers may also report concerns to the Federal Trade Commission at ReportFraud.ftc.gov.