Privacy policy

• Invitations and waitlist requests: your email address, any information you choose to include in a request or reply, and invitation and waitlist status. The administrator may use contact information you have previously provided to send you a direct invitation. You do not need an account or invitation to request a place on the waitlist.
• Information you provide: account and contact details such as your email and handle, profile information, recipes and imported content, meal plans, shopping lists, cooking notes, ratings, preferences, beta feedback, and support messages. Dietary preferences may reveal health or other sensitive information. Provide only what you want used for the service.
• Information from using Forkmade: account and content identifiers, activity and sharing records, IP address, browser and device information, and diagnostic and security logs. Usage and error records may be associated with your account.
• Information from other sources: recipe information from sources you choose to import. The beta is free; we do not collect payment information for beta participation.

We use information to manage waitlist requests and invitations, select testers, administer beta access, provide and personalize Forkmade, save and share content at your direction, respond to feedback, analyze usage, improve reliability, prevent abuse, and meet legal obligations. We may send invitations, messages about your waitlist request, sign-in emails, and necessary beta or service updates. A waitlist request is not consent to promotional emails. We do not sell personal information, share it for targeted advertising, run ads, or send marketing emails.

Public recipe pages can be viewed without an account. A recipe marked public is shared with visitors, including its handle, attribution, and source links. Imported recipes start private. Sharing a recipe or list does not invite its recipient to the beta or permit account registration.

During prototype testing, we ask search engines not to index the site. This does not restrict access to public recipes or valid share links, guarantee that search engines will comply, or remove existing copies.

Anyone who receives a valid shopping-list share link can view the list until you revoke the link. Shared content may be copied, and registered participants may fork public recipes; changing visibility, revoking a link, or deleting an original does not recall existing copies or lawful forks. Avoid putting personal information in shared content. Private content may still be processed as described below.

We disclose information to service providers supporting hosting, storage, authentication, email, support, usage analysis, error monitoring. The information they receive depends on the services they provide.

We may also disclose information to comply with law or legal process, enforce our terms, or protect rights, safety, and service security. If the business is sold or reorganized, information may transfer as part of that transaction, subject to this policy and applicable law.

Forkmade currently does not send user content to AI providers. Any future AI processing will be limited to recipe or plan data that cannot reasonably be linked to a person, including through details within the content. Personal information will not be sent. We will not attempt to reidentify that data and will require the same of AI providers. We will update this policy, provide required notices, and obtain required consent before introducing new processing.

Cookies and browser storage support sign-in, preferences, and service functionality. You can manage them in your browser; blocking them may prevent some features from working.

When you generate a meal plan without an account, we process your selected preferences and keep the draft preferences and public recipe version identifiers in a browser cookie for up to 24 hours. This cookie is sent back to our server when you use the site. The draft becomes a saved account plan only when you sign in and save it.

We do not use advertising cookies or third-party tracking tools that follow your activity across unrelated sites. Do Not Track signals do not change our processing. We honor other privacy preference signals where legally required.

We retain information as needed to provide the service, resolve disputes, maintain security, and meet legal obligations. Retention depends on the information, account activity, waitlist or invitation status, and those purposes. You may withdraw your waitlist request or decline further invitations by emailing us. We may reset or delete test content during or at the end of the beta as described in the terms of use. Deletion may be subject to lawful recordkeeping needs and backup retention, subject to applicable deletion requirements. Existing shared copies and forks are addressed in the terms of use.

We use safeguards designed to protect information, but no system is completely secure. Contact us if you suspect unauthorized access.

You can update your profile and preferences, change recipe visibility, and revoke sharing links in the app. To request access, correction, a copy, or deletion of your personal information or account, or to withdraw from the waitlist or decline invitations, email ryan.benhase@gmail.com.

Depending on applicable law, you may also have rights to restrict or object to processing, withdraw consent, appeal a decision, or complain to a regulator. We may verify your identity and will handle requests, exceptions, and appeals as required by law. We do not discriminate against you for exercising protected privacy rights. Deleting information may prevent us from providing related features.

The Forkmade beta and waitlist are intended for adults 18 and older in the United States. We do not knowingly collect personal information from children under 13; contact us if you believe a child has provided it. Information may be processed in the U.S. and other countries where our providers operate.

We will update the effective date when this policy changes and provide notice of material changes by email or a prominent site notice. We will obtain consent where required before using previously collected information in a materially different way.