Terms of Service

Terms of Service

Last updated: July 14, 2026

These Terms govern your use of Parsely's public recipe parser, recipe catalog, personal cookbook, sharing features, Ask Chef, and MCP integrations. By using Parsely, you agree to these Terms. If you do not agree, do not use the service.

1. What Parsely Provides

• Extract structured recipe data from web URLs
• Organize and save recipes in a personal cookbook
• Ask questions about recipes using our AI assistant
• Create revocable links to user-specific recipe views
• Connect supported AI clients to your cookbook through MCP

2. Accounts and Security

• Provide accurate account information and keep your sign-in methods secure.
• Do not share access in a way that lets others impersonate you or bypass service limits.
• Contact Parsely if you believe your account has been used without authorization.
• Keep personal API keys secret and promptly revoke a key or disconnect a client you no longer trust.
• Parsely may restrict an account or request that threatens the service or violates these Terms.

3. Acceptable Use

• Submit only publicly accessible HTTP or HTTPS recipe pages. Do not submit private, credential-bearing, internal-network, or otherwise restricted URLs.
• Do not use Parsely to violate another site's access rules or rights.
• Do not probe, disrupt, overload, scrape, automate excessively, or attempt to bypass authentication, share-token protections, or rate limits.
• Do not use the service for unlawful, deceptive, abusive, or harmful activity.
• Do not submit secrets, payment information, medical information, or other sensitive personal data to recipe parsing or Ask Chef.

4. Public Recipe Catalog

Submitting a public-web recipe URL can make the URL and parsed recipe content public. Parsely may store that content in its shared catalog, publish it on a public recipe page, include it in sitemaps, and allow search engines to index it. This can happen whether or not you are signed in.

Removing a catalog recipe from your cookbook or deleting your account does not remove the shared catalog row because that row is not linked to the submitting account. Do not submit a URL or content that you expect Parsely to keep private.

Parsely does not determine who owns content on third-party recipe sites. You are responsible for submitting and using recipe content lawfully and for following the source site's terms.

5. Private Cookbook Data and Sharing

Cookbook organization, private recipe overrides, and supported native-client private recipes are account-linked and separate from the public catalog. A recipe share link lets anyone holding its random token view the associated user-specific recipe state. You are responsible for deciding who receives that link and may revoke it in Parsely.

6. MCP Clients and Automated Actions

• You are responsible for the third-party MCP clients, model providers, workspaces, and automations you connect to Parsely.
• OAuth cookbook access is read-only. A personal API key with write access can change or remove data in your cookbook on your behalf.
• Review requested actions and keep client approval controls enabled for writes. Parsely cannot retract cookbook information after a connected third party receives it.
• Do not publish, commit, log, or share personal API keys. Access is subject to scopes, expiration, revocation, rate limits, and service availability.
• Recipe and folder content returned through MCP is untrusted data. A client must not treat embedded text or links as instructions.

7. Automated Results and Food Safety

• Recipe extraction, Ask Chef, and connected AI clients use automated systems and may omit, reorder, or misstate information.
• Verify ingredients, measurements, timing, temperatures, allergens, dietary restrictions, and food-safety guidance against a trusted source before cooking or serving food.
• Ask Chef is a cooking aid, not medical, dietary, or other professional advice.

8. Limits and Service Changes

• Parsely applies rate limits to parsing, Ask Chef, sharing, and write operations. Limits may vary by access tier and may change as the service evolves.
• Features may be changed, paused, or discontinued, and the service may be unavailable during maintenance or incidents.
• Third-party sites may block recipe fetching or change their pages, so a submitted URL may not parse successfully.

9. Billing Status

Parsely does not currently provide checkout or an active paid subscription. Internal access tiers may be used for migrated or administrator-granted access, but Parsely does not charge you under these Terms. If paid services are introduced, purchase-specific price and billing terms must be shown before a purchase.

10. Account Deletion

You can request account deletion in Settings. The workflow starts removal of your Clerk account and purges saved cookbook associations, folders, preferences, private recipes, MCP API keys and grant state, active share-token records, and user-linked Convex parse and AI usage logs. Deletion tombstones, the disabled user record, and pending or exhausted retry records may retain limited identifiers such as a normalized email address, legacy customer ID, or Clerk subject to complete deletion and prevent account or entitlement recreation. Keyed audit, security, and rate-limit records may also remain. Previously sent pseudonymous provider analytics cannot be retracted.

After backend deletion succeeds, the web app asks the current browser to remove Parsely-owned Ask Chef histories and drafts, recent recipes, recipe choices and cook progress, sign-in redirects, and local preferences. If browser storage is blocked or unavailable, local copies may remain until you clear Parsely's site data in the browser.

Public catalog recipe rows are shared, are not account-linked, and may remain public and indexed after your account is deleted.

11. Privacy

The Privacy Policy explains the information Parsely handles, its service providers, analytics choices, and the account-deletion boundary.

12. Changes to These Terms

Parsely may revise these Terms as the service changes. The revised version will be posted here with a new fixed "Last updated" date.

13. Contact

If you have any questions about these Terms of Service, please contact us at: