Skip to RecipeFork content

Public notice

Privacy Notice

This notice explains the information RecipeFork handles and the choices available to you.

Information

Information RecipeFork handles

RecipeFork may handle:

  • account and profile information, including identifiers received from the authentication provider, display name, handle, status, roles, and preferences;
  • content and activity you provide, including recipes, drafts, cookbooks, photos, comments, reactions, saves, follows, collaboration activity, cooking records, and reports;
  • consent receipts, export and deletion requests, and related verification or review records;
  • request metadata, device or browser information, security signals, basic service and product-operation events such as authenticated profile identifiers and action outcomes, diagnostics, and audit records needed to operate and protect the service.

Use and disclosure

How information is used and disclosed

We use information to authenticate users; provide RecipeFork features; preserve visibility, attribution, and fork lineage; respond to support, safety, export, and deletion requests; prevent abuse; secure and diagnose the service; meet applicable obligations; and improve the product if optional analytics is enabled in a future release. Service, security, fraud-prevention, and basic product-operation records are handled even while optional analytics is off.

Public content may be visible to other people and search engines. Private content is intended to remain within the applicable account or collaboration controls. A user-chosen fork is an independent version; removing a source account does not necessarily remove another person's fork or the attribution and lineage explaining its origin.

Current provider roles include Vercel for hosting, Clerk for authentication, and Supabase for application data storage. Google may process authentication information if you choose Google sign-in. Sentry may process diagnostics when it is configured. PostHog is available as an optional product-analytics provider, but optional product analytics is unavailable in this release. Providers may process information for the functions they perform. We may also disclose information when reasonably necessary to protect users or the service, investigate misuse, respond to valid legal process, or complete a business reorganization subject to appropriate information handling.

RecipeFork does not sell user recipes or grant paid campaigns a right to use them merely because they are stored or published.

Your controls

Your choices and requests

Optional product analytics is unavailable in this release. RecipeFork preserves a saved privacy choice so it remains available for future review, but that choice does not activate optional analytics while the feature is disabled. The Cookies & Device Storage notice explains the current tracking and browser-storage details.

You can review or correct available profile information in settings. Available signed-in settings may also let you request an account export or account-deletion review. If the needed control is not available, contact support@cayv.com.

A deletion request is not immediate erasure. RecipeFork may require identity or authority verification and will review the request before an account change. Eligible private work may be removed when a request is completed. Records needed for fork attribution and lineage, security, fraud prevention, rights, safety, legal obligations, disputes, or financial recordkeeping may remain; shared work may require transfer or archival treatment.

Depending on where you live, you may have additional rights. Contact us to make a request; verification may be required.

Data care

Retention, security, and children

We retain information while reasonably needed for its product, account, security, support, safety, legal, or operational purpose. Different records have different needs, and provider-held information may follow provider configuration and contracts. We do not promise one fixed period.

We use administrative, technical, and organizational measures intended to protect information, but no service can guarantee absolute security.

Accounts are not for children under 13. If you believe a child under 13 has provided personal information through RecipeFork, contact support@cayv.com so we can review the report and address any required removal or parental handling. This rule is not a claim that RecipeFork currently operates an age-verification system.

Updates

Changes to this notice

When this notice changes, we will update the effective date above. Before a material change takes effect, RecipeFork will provide a prominent notice on the site so you can review it.

Privacy Notice | RecipeFork