Last Updated: February 17, 2025
Welcome to Forktastic. This Privacy Policy explains how Forktastic ("we," "us," or "our") collects, uses, shares, and protects your personal information when you use our products and services.
This policy applies to all Forktastic products, including:
Throughout this policy, we use the following terms:
By using any Forktastic product, you agree to the collection and use of information in accordance with this policy. If you do not agree, please do not use our Service.
We collect different types of information depending on how you interact with our Service.
When you create a Forktastic account, we collect:
When you use Forktastic to extract and save recipes, we collect:
Important: The raw HTML is processed in memory, is NOT permanently stored, and is discarded after processing (typically within 30 seconds). Only the structured recipe data is saved to your account.
The Forktastic browser extension operates in two distinct modes:
When you browse the web with the extension installed, a content script scans each page for JSON-LD structured data (Recipe schema markup). This scanning happens entirely within your browser. During passive detection, no data is transmitted to our servers. We do not collect your browsing history, page content from non-recipe pages, or track the websites you visit. The extension icon simply updates to indicate whether a recipe was detected on the current page.
When you explicitly click to extract a recipe (or have auto-extract enabled), the full HTML content of the current web page is transmitted to our server via an encrypted HTTPS connection. Our server uses AI to extract structured recipe data. The raw HTML is processed in memory, is NOT permanently stored, and is discarded after processing (typically within 30 seconds). Only the structured recipe data is saved.
The extension stores the following data locally on your device using chrome.storage.local:
We use RevenueCat to manage subscriptions. When you subscribe to Forktastic:
We collect usage data to improve our Service:
We automatically collect certain technical information when you use our Service, including browser type and version, operating system, device type, language preferences, and referring URLs. This information helps us optimize our Service for different platforms and troubleshoot technical issues.
The Forktastic browser extension requests specific permissions to function. Here is a detailed explanation of each permission and why it is needed:
| Permission | Why It's Needed |
|---|---|
| <all_urls> | Recipes are published across millions of websites. To detect recipe markup on any page, our content script requires this permission. The script scans for JSON-LD structured data locally within your browser. During detection, no data is transmitted. We do not collect browsing history, page content from non-recipe pages, or track the websites you visit. |
| activeTab | Allows access to the content of the current tab only when you interact with the extension (e.g., clicking the extension icon or the "Extract Recipe" button). This is used to read the page HTML for recipe extraction. |
| storage | Stores your authentication tokens, extension preferences, and recent recipe identifiers locally on your device. This data never leaves your browser unless you initiate an action. |
| scripting | Injects the content script that performs local JSON-LD recipe detection on web pages. The script runs passively and only communicates with the extension's background service worker. |
| tabs | Updates the extension icon badge and state based on whether a recipe was detected on the current page. Also used for navigation to the web app when needed. |
| host_permissions (api.revenuecat.com) | Allows the extension to check your subscription status with RevenueCat. Only your anonymous user identifier and subscription status are transmitted. |
We use the information we collect for the following purposes:
We process your information only for the purposes described in this policy. We do not use your recipe content to train AI models or for any purpose other than providing the Service to you.
Here is a detailed explanation of how recipe data flows through our system:
The extension's content script scans the current page for JSON-LD Recipe schema markup. This happens entirely in your browser with no network calls. If recipe markup is found, the extension icon updates to indicate a recipe is available.
When you click "Extract Recipe," the full page HTML is sent to our API server (api.forktastic.com) over an encrypted HTTPS connection. Our server passes the HTML to AWS Bedrock (AI service) which extracts structured recipe data including title, ingredients, instructions, nutrition, and timing information. The raw HTML is processed in memory and discarded within approximately 30 seconds. It is never written to permanent storage.
Recipe images are converted to WebP format and stored on Cloudflare R2 via presigned URLs generated by Supabase Edge Functions. Images are associated with your recipe and accessible only through your authenticated account.
The structured recipe data (title, ingredients, instructions, nutrition, source URL, and image URLs) is stored in our Supabase PostgreSQL database, linked to your user account. You can view, edit, organize, and delete your saved recipes at any time through the web app or extension.
We do NOT sell your personal data. We share information with third-party services only as necessary to provide the Forktastic Service. Below is a comprehensive list of third-party services we use:
| Service | Purpose | Data Shared | Privacy Policy |
|---|---|---|---|
| Supabase | Authentication, database, edge functions | Email, hashed password, recipes, user ID | supabase.com/privacy |
| AWS (Bedrock, Lambda, API Gateway) | AI recipe extraction, API hosting | Page HTML (during extraction only), email (waitlist) | aws.amazon.com/privacy |
| RevenueCat | Subscription management | Anonymous user ID, subscription status | revenuecat.com/privacy |
| Cloudflare R2 | Recipe image storage | Recipe images (WebP format) | cloudflare.com/privacypolicy |
| Google Analytics 4 | Website analytics | Anonymized page views, events, device info | policies.google.com/privacy |
| Vercel | Website hosting, analytics | Web vitals, performance metrics | vercel.com/legal/privacy-policy |
We may also share information when required by law, to protect our rights, or in connection with a merger, acquisition, or sale of assets (in which case you will be notified).
We take the security of your data seriously and implement the following measures:
chrome.storage.localWhen you sign in through the web app (app.forktastic.com), the extension uses an auth bridge mechanism to synchronize your login state. A content script on app.forktastic.com securely forwards authentication tokens to the extension's background service worker via the browser's internal messaging API. This communication stays within your browser and does not transmit tokens to any external server.
We retain your data only for as long as necessary to provide the Service and fulfill the purposes described in this policy.
| Data Type | Retention Period |
|---|---|
| Raw page HTML | Discarded immediately after processing (~30 seconds) |
| Authentication tokens | Until logout or token expiry |
| Recipes and images | Until user deletes them or account is deleted |
| Waitlist email addresses | Until unsubscribe or 2 years, whichever comes first |
| Contact form submissions | 1 year after resolution |
| Google Analytics data | 14 months (GA4 default retention) |
| Extension local storage | Until extension uninstall or logout |
Account Deletion: When you request account deletion, all associated data (recipes, images, account information) is permanently purged from our systems within 30 days of your request. Local extension data is cleared upon logout or extension uninstall.
You have the following rights regarding your personal data:
To exercise any of these rights, contact us at privacy@forktastic.com. We will respond to your request within 30 days.
If you are located in the European Union or European Economic Area, you have additional rights under the General Data Protection Regulation (GDPR). We process your data under the following legal bases (Article 6):
In addition to the rights listed in Section 9, EU/EEA users have the right to:
Your data may be transferred to and processed in countries outside the EU/EEA, including the United States. Our third-party service providers maintain appropriate safeguards for cross-border data transfers, including Standard Contractual Clauses (SCCs) approved by the European Commission.
If you are a California resident, you have rights under the California Consumer Privacy Act (CCPA) and the California Privacy Rights Act (CPRA).
We do not sell your personal information. We do not share your personal information for cross-context behavioral advertising purposes.
To exercise your rights, contact us at privacy@forktastic.com. We will respond within 45 days of receiving your verifiable request.
Forktastic is not directed at children under the age of 13 (or 16 in the European Union). We do not knowingly collect personal information from children. If we become aware that we have collected personal data from a child without parental consent, we will take steps to promptly delete that information.
If you believe a child has provided us with personal data, please contact us at privacy@forktastic.com.
We may update this Privacy Policy from time to time to reflect changes in our practices, technologies, legal requirements, or other factors. When we make material changes, we will notify you by:
We encourage you to review this policy periodically. Your continued use of the Service after changes are posted constitutes your acceptance of the updated policy.
If you have questions about this Privacy Policy or our data practices, please contact us: