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.