InSync Privacy Policy

Effective date: October 2, 2026

InSync ("InSync," "we," "us") is an iOS app that helps you decide what to cook, with a partner or on your own. InSync is run by Cal Huesman, who is responsible for your information. This policy explains what information we collect, how we use it, who we share it with, and the choices you have. If you have questions, contact us at insyncapp.help@gmail.com.

1. Information we collect

Account information

• Your email address, if you sign in with a one-time code sent to your email
• Your Apple sign-in identifier and the email Apple shares with us (this may be a private relay address), if you use Sign in with Apple
• Your Google account identifier, name, and email, if you use Sign in with Google

Subscription information

• Whether you have InSync+, your plan, and its trial, renewal, and end dates. Apple handles payment; we never see your card details
• Whether your account has been given InSync+ at no charge (a "comped" account). We keep a short list of comped accounts, linked to the account.

Profile information you give us

• Display name
• A profile photo, if you add one
• Diet rules and allergies you choose (for example vegetarian, gluten-free, or peanut-free), including allergies you type in yourself
• Foods you want to avoid
• Your onboarding answers, for example who you usually cook with and for how many people, your cooking skill, how spicy you like food, how long you like to spend cooking, the kitchen gear you have, which meals you usually cook (breakfast, lunch, or dinner), your favorite foods and cuisines, how adventurous you are, your goals, and your weekly meal goal
• If you choose to answer, how you heard about InSync (a source like TikTok or a friend, plus optional words if you pick "Somewhere else"). We use it only to understand which channels work. It's never shared with your partner or third parties, and it's deleted when you delete your account.
• Your notification settings and the time you choose for the daily "Craving check" reminder

Diet rules, allergies, and foods to avoid are optional. They may reveal health-related information, such as a food allergy. We use them only to filter recipes for you and anyone you cook with in InSync. See "Consumer health data" below.

Activity in the app

• Your cravings and swipes for each round, and your plan for it (the meal, time, goal, effort, and any leftovers or occasion you add)
• Match results, meals you propose and pick, cooking progress, ratings, and notes
• Your cooked-meal history, streaks, weekly goal progress, stats, and achievements (worked out from the meals you cook)
• Badges you unlock. They're saved to your own account and stay with you across partners, one-phone mode, and Just me
• Your lists: favorites, To Cook, "never again," and "make again soon"
• Your grocery list: the items and amounts, which recipe each one is for, what you've checked off or marked as a pantry staple, and "Recently bought" (items you've marked as bought, and when)
• Cooking together on two phones: the step you're both on and the timers you start, pause, or cancel (who started them, how long they are, and when), so both phones stay in sync during that meal
• How you use InSync: paired with a partner, on one phone with a guest, or on your own ("Just me"). In one-phone mode we store the guest's name, food rules, allergies, foods to avoid, spice preference, ratings, and a guest photo if you add one

Pairing information

• Your invite code. Invite links include the code (for example insynccooktogether.github.io/join.html?code=ABC123), so anyone you send the link to can see it. Each code works only once. It stops working when it's used or cancelled, and an invite made while you're already paired expires after 7 days
• Your pairing history: who you paired with and when, and when a pairing ended, who ended it, and why (for example they left, went back to solo, or switched partners). When someone ends a pairing, the other person sees a short note about it, such as "Alex went back to solo". If your partner deletes their account, you see a one-time note with their first name, such as "Alex deleted their account"

Photos

• Meal photos and profile photos you choose to add. We only access the camera or photo library when you tap to add a photo, and only the photos you pick. Photos are kept in private storage, not public links.

Information kept only on your phone

• Before you sign in, your onboarding answers, a profile photo you picked, and any meal you save with "Save it for later" stay on your phone. After you sign in, they are saved to your account (the saved meal goes to your To Cook list).
• Copies of photos, so they load quickly and work offline
• Your Ask the chef chats (see below)
• Practice ("demo") rounds with a pretend partner, and your reminder schedule

Device and usage information

• A push notification token, if you allow notifications
• App version and basic in-app usage events (for example which screens were completed), stored in our own database to understand how the app is used and improve it
• Anonymous usage analytics through TelemetryDeck, and crash and error reports through Sentry (see "Service providers" below)

Security logs

• Short-lived counters of when certain actions happen from your account (for example Ask the chef questions and joining with an invite code), used only to set limits and stop abuse. They're cleared within about two days.

Server logs

• Like most online services, our providers keep basic logs when your phone or browser connects to them. Supabase (which runs our servers) and GitHub Pages (which hosts our website, including invite links) log IP addresses and basic device or browser information, such as the browser or app version and operating system, along with the time and the page or service requested.

Support messages

• Anything you send us when you contact support

AI cooking help ("Ask the chef")

• Before your first question, we ask for your OK to send information to Anthropic. If you tap "Not now," nothing is sent and we'll ask again next time.
• If you use Ask the chef, we send your question, the last few messages of that chat, the recipe you're asking about (its ingredients, steps, and the number of servings), and the food rules of the people cooking (diet rules, allergies, foods to avoid, and spice preference; for you and your partner or one-phone guest) to Anthropic, which writes the answer. We don't send your name, email, or photos.
• We don't store your chats on our servers. Each recipe's chat stays on your phone and is cleared after a day without a new message. We keep only a count of how many questions you asked, to apply the daily limit. If a question can't be answered, it doesn't count.
• If you tap "Report this answer," we save that question, the answer, and any note you add, so we can review it. Reports are linked to your account.
• Answers come from AI and can be wrong. Always check ingredient labels if you have allergies.

2. Information we do not collect

• We do not collect your location, contacts, or health data from Apple Health.
• We do not show ads.
• We do not sell your personal information or share it for advertising.
• We do not track you across other companies' apps or websites.

3. How we use information

• To run the app: sign you in, pair you with your partner (or set up one-phone or Just me use), match your cravings, suggest meals, run cook mode (including keeping two phones in sync), keep your grocery list, and save your history, stats, badges, and achievements
• To filter out meals that don't fit your diet rules, allergies, foods you avoid, kitchen gear, or the meal you're planning
• To send notifications you allow, such as when your partner picks their cravings, your match is ready, a meal is proposed, a pick changes, or a pairing ends, and the reminders you turn on (the Craving check, your monthly recap, and your free trial ending). Some reminders are scheduled on your phone. When your partner starts a round, we may send your phone a silent notification that only removes that day's Craving check reminder
• To answer your Ask the chef questions, if you choose to use it
• To keep the app secure, prevent abuse, and fix problems
• To understand how the app is used and improve it
• To respond to you when you contact us
• To comply with law

4. Who can see your information

Your partner. When you pair, your partner can see your display name, your profile photo (only while you're paired), your diet rules, allergies, and foods to avoid (so the meals you cook together fit both of you), your top cravings after you both lock in (not your "not tonight" picks or individual swipes), meals you propose and pick together, cooking progress (including the step and timers when you cook together on two phones), ratings, notes, meal photos for meals you cooked together, and the To Cook, Make again and grocery items you add (shown to both of you with who added each). Your favorites and your Never again list are never shown to your partner, though a Never again dish won't be suggested to the two of you. If you end the pairing, they see a short note that you did and why. After you unpair, your former partner can still view the shared meal history from your time together, but can't see anything new, can't add to it, and can't see your profile photo. The list and grocery items you added stay yours and leave their view.

On one phone or on your own. In one-phone mode, the guest's information stays in your account. With Just me, your activity isn't shared with anyone. If you later add a second phone with a code, the person who joins is asked whether they're your guest. If they say yes, they take the guest's place: they can see the meals, ratings and photos from your one-phone days, and the guest's food rules, allergies and foods to avoid are added to their profile (nothing they already had is removed; the app tells them what was added), and the guest's name fills in theirs if it's empty. Meals from before the guest was set up, and meals you logged on your own, stay yours. If they say no, or if you were using Just me, you two start a fresh shared history and they don't see your earlier meals.

When you share. If you choose to share a match or recap card, or an invite link, it goes only where you send it through your iPhone's share sheet. Recap cards include first names only if you turn that on.

Service providers who help us run InSync. They get only what they need to provide their service to us:

• Supabase: our database, file storage, sign-in, server functions, and the one-time sign-in code emails (we don't use any other email provider). It stores the information described in this policy and keeps server logs with IP addresses.
• Apple: Sign in with Apple, push notifications, and App Store purchases. If you delete your account, we tell Apple to end InSync's Sign in with Apple link to your Apple ID.
• Google: Sign in with Google, if you choose it. It receives what's needed to sign you in.
• RevenueCat, which manages InSync+ subscriptions. It receives your InSync account ID, your App Store purchase details, and basic device information (such as device model and iOS version), not your recipes, cravings, or photos.
• Anthropic, which provides the AI that answers Ask the chef questions. It receives only what's listed under "AI cooking help" above, and only when you ask a question after giving your OK. Under Anthropic's commercial terms, Anthropic doesn't use this information to train its models. Anthropic may keep it for a limited time under its own policies, for example to prevent abuse.
• TelemetryDeck, for anonymous usage analytics. It receives app events like "round started" or "cook started," with plain details such as the meal type, which recipe, a star rating, the app version, device type, iOS version, and language and region settings. It never gets your name, email, account ID, or anything you type; it tells users apart only by an anonymous code made on your phone.
• Sentry, for crash and error reports. When something goes wrong, it receives technical details about the error, the app version, device model, and iOS version, and a small sample of performance timings. We set it up not to send your name, email, account ID, screenshots, or what's on your screen.
• GitHub, which hosts our website (insynccooktogether.github.io). It receives your IP address and basic browser information when you visit the website or open an invite link, including the invite code in that link.

TelemetryDeck and Sentry, like any online service, see your IP address when your phone connects to them.

Legal reasons. We may share information if required by law, to protect the rights and safety of our users or others, or in connection with a sale or transfer of the app.

5. How long we keep information

We keep your information while your account is active. You can delete your account anytime in the app (Profile, then About, then Delete account).

When you delete your account, we delete your account, profile, diet rules and allergies, profile photos (including a one-phone guest's photo), the meal photos you uploaded (including photos you added to meals you shared, so they're removed from your partner's history too), private picks, favorites, your To Cook, Make again and Never again lists, grocery list, badges, push tokens, your Just me and one-phone meals, rounds and weekly goals, a one-phone guest's name, food rules and allergies, and your in-app usage (analytics) events. Records of meals you cooked with a partner may remain in your former partner's history without your name or account on them; your former partner sees a one-time note that you deleted your account. Reports you sent about an AI answer are kept so we can review them, and are unlinked from your account.

Deleting your account doesn't cancel an App Store subscription. To stop being charged, cancel in your Apple ID account settings (Settings, then your name, then Subscriptions).

Deleted information may stay in our database provider's backups for up to 30 days before it's gone for good. We don't keep Ask the chef conversations. Security counters, including the daily question count, are cleared within about two days. Server logs are kept by Supabase and GitHub for a limited time under their own policies. Information kept only on your phone is removed when you delete the app. We may keep limited information when required by law or to prevent abuse.

6. Consumer health data

Your allergies, diet rules, and foods to avoid (and those you enter for a one-phone guest) may count as health data under some laws, because they can say something about your health.

• We use them only to filter recipes, so InSync doesn't suggest meals that don't fit, and to shape Ask the chef answers if you use it.
• We share them only with Supabase, which stores them for us, and with Anthropic, only when you use Ask the chef. Your partner's copy of InSync also uses them, so the meals you cook together fit both of you.
• We never sell them, and we never use them for ads.
• They're optional. You can change or remove them anytime in the app, and they're deleted when you delete your account.

7. Security

We use industry-standard safeguards, including access rules that limit each person to their own data and their current partner's shared data, private storage for photos, and limits that stop abuse. No method of storage or transmission is 100% secure.

8. Children

InSync is not intended for children under 13, and we do not knowingly collect information from children under 13. If you believe a child has given us information, contact us and we will delete it.

9. Where information is stored

Our service providers store information in the United States and the European Union (TelemetryDeck, our anonymous usage analytics, is based in Germany). If you use InSync from outside the U.S., your information will be transferred to and processed in the U.S.

10. Your choices and rights

• Edit your profile, profile photo, diet rules, allergies, and foods to avoid in the app
• Choose which notifications you get in the app (Profile, then Notifications), or turn them all off in iOS Settings
• Say "Not now" to Ask the chef, or just don't use it
• Unpair anytime
• Delete photos you uploaded, or delete your whole account, in the app
• Request a copy of your information, or ask us to correct or delete it, by contacting us

Depending on where you live (for example California or the European Union), you may have additional rights. We will respond to requests as required by applicable law.

11. UK and EEA users

If you're in the UK or the European Economic Area, Cal Huesman is the controller of your information. You can reach us at insyncapp.help@gmail.com.

Why we're allowed to use your information (legal bases)

• Contract: to provide InSync to you, including your account, pairing, matches, cook mode, grocery list, history, and InSync+
• Legitimate interests: to keep InSync secure, prevent abuse, fix crashes, understand how the app is used, and improve it. We only rely on this when it doesn't override your rights
• Consent: for Ask the chef (we ask before your first question) and for optional allergy and diet information. You can withdraw consent anytime by removing that information or not using Ask the chef; this doesn't affect what we did before
• Legal obligation: when the law requires us to keep or share information

Your rights. You can ask to access, correct, delete, or export your information, object to how we use it (including anything based on legitimate interests), restrict how we use it, and withdraw consent. Contact us at insyncapp.help@gmail.com. You can also complain to the UK Information Commissioner's Office (ICO) or your local data protection authority.

Where it's stored. Your information is stored and processed in the United States (anonymous usage analytics in the European Union). When we or our providers transfer it there, we rely on safeguards the law allows, such as standard contractual clauses.

How long it's kept. As described in "How long we keep information" above: while your account is active, then deleted when you delete your account (backups within 30 days), with the exceptions listed there.

12. Other people's information

Only add someone else's information to InSync, such as a one-phone guest's name, food rules, allergies, or photo, or photos of other people, if they're OK with it.

13. Do Not Track

Some browsers send a "Do Not Track" signal. There's no common standard for it, so InSync doesn't respond to it. We don't track you across other companies' apps or websites either way.

14. Changes to this policy

We may update this policy. If we make significant changes, we will let you know in the app. The effective date at the top shows when it was last updated.

15. Contact

InSync is run by Cal Huesman. Questions or requests: insyncapp.help@gmail.com