Privacy policy

Cooklook is a recipe app. This explains what it stores, why, and how to get rid of it. It is written to be read, not to cover a wall.

Contact: jpdillon20@gmail.com

Who runs Cooklook

Cooklook is built and run by Virgo Digital LLC, based in Ann Arbor, Michigan, United States. If you have a question about your data, email the address above.

What Cooklook stores

Your account. An email address and a password. Passwords are hashed by our auth provider and nobody at Cooklook can read yours.

Your profile. A username, a display name, an optional short bio, and an optional photo. These are visible to other people using the app.

Your taste answers. The quiz you take when you sign up: how you eat, foods you avoid, cuisines you like, how many people you cook for, and how long you have on a weeknight.

What you make. Recipes, cookbooks, photos, videos, comments, likes, the recipes you save, your "want to cook" list, and a log of the meals you mark as cooked, including any photo, rating, or note you add.

Safety records. If you report something or block someone, we store that so the block keeps working and so a report can be reviewed.

Cooklook does not run ads, does not use third-party advertising or analytics trackers, and does not sell or rent your data to anyone.

Food restrictions and allergies

Some of the quiz answers describe allergies or medical diets. That is health information and it gets treated as such.

Those answers are private by default. They are not shown on your profile and other people using Cooklook cannot see them. Cooklook uses them for one thing: filtering your own feed so recipes you cannot eat do not show up. They are never used for advertising and never shared.

You can change or clear them at any time by retaking the taste quiz in settings.

What other people can see

Your username, display name, bio, avatar, and anything you publish publicly: recipes set to public, videos, comments, and public cookbooks.

Recipes and cookbooks you keep private stay private. Your cook log, your saved recipes, your want-to-cook list, and your taste answers are yours alone.

What stays on your phone

Unpublished recipe drafts are stored on your device, not on our servers. They are deleted when you publish the recipe, when you throw the draft away, or when you sign out. Cook mode timers and the prep checklist are also local.

Who else touches your data

Supabase hosts the database, authentication, and file storage. They process data on our behalf and do not use it for their own purposes.

[your email provider, for example Resend] sends account emails such as password reset codes. They receive your email address and nothing else.

Apple distributes the app. During the TestFlight beta, Apple gives us crash reports and any feedback you choose to send through TestFlight.

That is the whole list. If it changes, this page changes with it.

How long it is kept

As long as your account exists. Delete your account and it goes.

Reports you file and blocks you set may be kept after deletion in a form that no longer identifies you, because they protect other people.

Deleting your account

Settings, then delete account. This is permanent and immediate. It removes your profile, recipes, cookbooks, photos, videos, comments, likes, cook history, and taste answers.

You can also email jpdillon20@gmail.com and ask, and we will do it for you.

Your rights

Depending on where you live you may have the right to see a copy of your data, correct it, delete it, or object to how it is used. Email the address above and we will sort it out. We will not charge you and we will not make you jump through hoops.

If you are in the EEA or the UK, the legal basis for handling your account and your content is performance of a contract with you. For your dietary answers it is your explicit consent, given when you answer the quiz and withdrawable at any time by clearing them.

Children

Cooklook is not for people under 13, and we do not knowingly collect anything from them. If you believe a child has an account, email us and we will remove it.

Changes

If this policy changes in a way that matters, we will say so in the app before the change takes effect. The date at the top always reflects the current version.