Privacy Policy

Information we collect

• Account information. Forked supports email, Apple, and Google sign-in through WorkOS. We receive your account identifier, email address, email verification status, and name if supplied. For email sign-in, WorkOS processes the authentication information you enter in its hosted sign-in flow. Apple may provide a private relay email address. Forked does not receive your Apple or Google password.
• Recipes and photos. We store the titles, descriptions, ingredients, instructions, categories, servings, cooking times, and photos you save. Photos are uploaded only when you choose them for a recipe. Forked uses the system photo picker rather than requesting your entire photo library.
• Collections and invitations. We store collection names, ownership, memberships, recipes added to collections, and invitation records, including expiry and acceptance.
• Technical and security information. Our services process network requests, which include an IP address and request details. Authentication records, session identifiers, and operational logs help secure accounts and diagnose failures.
• Support messages. If you contact us, we receive your email address, message, and anything you attach.

Your device stores sign-in tokens in Keychain and caches account details, recipes, and photos for offline use. Cooking timers run on your device and can appear in local notifications and Live Activities.

When available, an Apple authorization token is also stored in Keychain. During account deletion, the app sends that token to our server, where it is stored encrypted while we revoke the Apple authorization. We remove the stored token after successful revocation.

The website uses essential session and request-security cookies. You can clear them through your browser settings.

How we use it

We use this information to sign you in, save and sync your cookbook, display photos, manage shared collections and invitations, respond to support requests, prevent unauthorized access, and maintain the service.

Forked does not sell your personal information or use your recipe content for advertising. The app does not include advertising or cross-app tracking tools.

Sharing and service providers

Recipes in your personal cookbook are available to your account. When you add a recipe to a shared collection, its members can view the recipe and photos and save an independent copy. Members can see names and membership information. Keep invitation links private because someone who receives a valid link can use it to join.

• WorkOS provides authentication and processes sign-in, profile, and session information.
• Apple or Google authenticates you when you choose that sign-in provider. Your use of that provider is also subject to its privacy policy.
• Laravel Cloud provides application hosting, database, and file storage for Forked.

We require providers processing personal information on our behalf to use it for the services they provide and protect it at least as described in this policy. Providers may process information in countries other than where you live.

We may disclose information when required by law or when necessary to protect users, investigate abuse, or defend legal rights.

Retention and deletion

We keep account information and saved content while your account remains active, unless you delete individual content first. To delete your account, open Account in Forked and choose Delete account.

When we accept your deletion request, we block account access and begin cleanup. A request does not mean cleanup has finished. The app provides a deletion status so you can check progress.

Completed deletion removes your account record, your original recipes and photos, collections you own, and your memberships from the live service, including originals shared in other people's collections. It also deletes your WorkOS user account. Background cleanup retries temporary failures before reporting completion.

If an Apple authorization token is unavailable, the app explains how to remove Forked's Apple sign-in authorization in your Apple account settings. Your Forked account deletion continues independently of that step.

Deleting an owned collection removes that collection for all members. Recipes owned by other members are not deleted. Independent copies that other people saved to their own cookbooks remain in their accounts. Content exported or captured outside Forked cannot be recalled.

Deletion status receipts and associated cleanup records are scheduled for removal 90 days after deletion completes. Pending cleanup records remain until the deletion can finish. We also retain limited session-revocation identifiers to prevent revoked credentials from regaining access; these records do not contain your recipe content.

Backup copies may remain until the hosting provider's configured backup retention period expires. Backups are used for recovery, not normal access to deleted content. Operational logs are retained for troubleshooting and security.

Support correspondence is kept as needed to resolve your request and related follow-up. Information may be kept longer when required by law or to resolve a specific security incident or legal dispute. Contact us for retention information that applies to your request.

Signing out clears Forked's cookbook and photo caches on that device. Signing out or deleting the app does not delete your server account. Offline devices may retain cached content until they reconnect or their local data is removed.

Your choices and security

You can edit or delete your recipes and photos, leave shared collections, and revoke invitations to collections you own. You can choose not to upload photos and change notification permissions in iOS Settings. To stop future collection associated with your account, delete your account and stop using the service. Contact us to withdraw any other consent you have given.

Email support@getforked.link to request access, correction, or deletion of personal information. Depending on where you live, you may also have rights to receive a copy, object to or restrict processing, or complain to a privacy regulator. We may need to verify your identity before acting on a request.

Forked uses encrypted network connections, Keychain storage for sign-in tokens, and access controls for private recipes and photos. No service can guarantee absolute security.

Forked is not directed at children under 13. If you believe a child has provided personal information, contact us so we can investigate and remove it.

Contact and updates

Contact Azat Akmyradov at support@getforked.link for questions about this policy or your information.

We will update this page and its effective date when our practices change, and provide additional notice or request consent when required.