We use Google Analytics cookies to see which pages people use. No ads, no tracking across other sites. How we handle data

Privacy Policy

Effective date: September 14, 2026

Kitchenfolk is a place to find, save, cook, and share recipes. This policy explains what information we collect, how we use it, and the choices you have.

Kitchenfolk is operated by Brendan Paige. For privacy questions or requests, contact hello@kitchenfolk.co.

Information we collect

Account information. When you create an account, we collect your email address, authentication information, and the profile details you provide. These may include your display name, profile photo, biography, and links to your website or social accounts. Authentication is handled through Supabase.

Recipes and contributions. We collect the recipes, ingredients, instructions, photos, recipe versions, ratings, reviews, and other content you submit. Uploaded files may contain metadata, such as the device or location associated with a photo. Remove metadata you do not want to share before uploading.

Your recipe book and activity. We store your saved recipes, collections, private notes, imported recipes and their source links, cooking status and history, and the creators you follow. We also record account setup progress, including steps completed or skipped. Some cooking preferences and session progress may be stored on your device.

Messages and reports. If you contact us or report content, we collect your message, contact information, relevant links, and any attachments you provide.

Technical information. Our hosting and service providers process information needed to deliver and protect the site. This can include your IP address, browser and device information, request times, pages requested, and error or security logs.

How we use information

We use information to:

  • Create and manage accounts, authenticate sign-ins, and send account or security messages.
  • Display recipes and profiles, save your recipe book, and support cooking and recipe versions.
  • Show ratings, reviews, follows, and other community features.
  • Understand completion of account setup and improve the service.
  • Measure how the site is used, so we can see what works and what to fix.
  • Respond to support requests, privacy requests, and content reports.
  • Detect abuse, investigate problems, protect the service, and enforce our Terms.
  • Meet legal obligations and resolve disputes.

Creating an account does not subscribe you to a marketing newsletter. Following a creator does not give that creator your account email address. Any newsletter signup or sharing of your email with a creator requires a separate choice.

What is public and what is private

Public information. Your public profile, published recipes and their photos, public recipe versions, ratings, and reviews can be seen by other people, including visitors without accounts. Follow relationships and follower counts are public. Public content may appear in search engines, shared-link previews, and Kitchenfolk’s editorial features. As described in our Terms, we may use attributed public recipe content to promote Kitchenfolk on our own channels.

Private information. Your account email is not displayed as part of your public profile. Private recipe records, imported recipes, collections, saved-recipe activity, and private notes are not made available to other members through those features. Authorized administrators and service providers may access information when needed to operate the service, provide support, investigate abuse, or meet legal obligations.

Recipe photos. Photos on a recipe, including step photos, follow that recipe’s visibility: while it is private, only you can view them, and once it is published anyone can. Photos are delivered through links that expire within 24 hours, so if you make a published recipe private, people who already loaded its photos may be able to view them until those links expire. Your profile photo is part of your public profile.

Only share personal information in public content if you are comfortable making it public. Other people may retain copies of content they have already seen or shared.

Service providers and other disclosures

We use service providers to operate Kitchenfolk. Supabase provides authentication, database, and image storage services. Cloudflare provides hosting and delivery infrastructure. Google Fonts supplies the typefaces the site is set in, so loading a page asks your browser to fetch font files from Google, which receives your IP address and browser information as part of that request. Google Analytics measures how the site is used, as described below. These providers process information for the services they supply.

We may also disclose information:

  • When you ask us to, or choose a feature that shares information.
  • When reasonably necessary to meet legal obligations, respond to valid legal process, protect safety, or investigate fraud or abuse.
  • To process copyright complaints and counter-notices, including sharing relevant notice details with the other party.
  • In connection with a merger, acquisition, or transfer of the service, subject to applicable privacy obligations.

We do not sell your personal information or share it for cross-context behavioral advertising. We do not give creators your email address simply because you saved, reviewed, or followed their work.

Browser storage and tracking

Kitchenfolk uses browser storage and similar essential technologies to support sign-in, preferences, and site operation. Hosting providers may also use essential technologies for security and delivery.

We use Google Analytics to understand how the site is used: which pages people open, how they arrived, roughly where they are, and whether they come back. It sets cookies in your browser and sends that information to Google, which processes it for us. We have not turned on Google’s advertising features, and we do not use advertising pixels or cross-site advertising tracking.

Analytics only runs if you accept it. On your first visit a bar asks; nothing is loaded until you choose, and declining is remembered. You can change your answer at any time with “Cookie choices” in the footer.

You can opt out of Google Analytics in every site you visit with Google’s browser add-on, or block analytics cookies in your browser. We do not change the site’s behavior in response to a browser’s Do Not Track signal. We do not authorize third parties to track your activity across unrelated websites through Kitchenfolk for advertising purposes.

You can manage cookies and local storage through your browser. Clearing or blocking them may sign you out or prevent some features from working.

Where information is processed

Our primary Supabase project is hosted in Canada. Information may also be processed in the United States and other countries where we or our service providers operate. Those countries may have different privacy laws from your own. Where applicable law requires safeguards for international transfers, we will use the required safeguards.

How long we keep information

We keep account information and content for as long as needed to provide the features you use. We retain support, security, and dispute records only as long as reasonably needed for their purpose or required by law.

When you request deletion, we remove or de-identify information we no longer need, subject to legal obligations and legitimate security or dispute-related retention. Where we retain information for one of those reasons, we limit its use to that purpose.

Deleting information from active systems may not immediately remove cached copies. Public content may also remain in copies held by others. Existing recipe versions are addressed in our Terms; this does not override rights you may have to deletion of personal information.

Your choices and requests

You can edit your profile in account settings and use the available controls to manage your recipes, reviews, saves, and follows. You can also delete your account yourself from your profile settings, which removes your profile, recipes and their photos, reviews, saves, collections, notes, and follows.

To request access to, correction of, or deletion of your personal information, or a copy of information associated with your account, email hello@kitchenfolk.co. You can also use this address if you need help deleting your account. Please contact us from your account email when possible and describe what you want us to do. Do not send your password.

We may need to verify your identity before acting on a request. If we cannot fulfill a request, we will explain why. Depending on where you live and which laws apply, you may have additional rights, including portability, objection or restriction, appeal of a denied request, or a complaint to your privacy regulator. We will handle applicable rights requests within the deadlines required by law. To ask us to reconsider a decision, reply to our response or contact hello@kitchenfolk.co.

Security

We use access controls and other measures intended to protect information. No website or storage system can guarantee complete security. Keep your sign-in credentials secure and contact hello@kitchenfolk.co if you believe your account has been compromised.

Children

Kitchenfolk is not directed to children under 13, and children under 13 may not create accounts or submit personal information. We do not knowingly collect personal information from children under 13. If you believe a child has provided information to us, contact hello@kitchenfolk.co so we can investigate and take appropriate action, including deletion.

Other websites

Recipes and profiles may link to external websites. When you visit those sites, their privacy policies apply. Importing a recipe asks Kitchenfolk to retrieve information from the source website; that site may record the request. We do not send your Kitchenfolk account email to the source site as part of an import.

Changes to this policy

We will post updates here and change the effective date. For material changes, we will provide an additional notice on the site or by email as appropriate. Where required, we will obtain consent before applying a change.