Last updated: October 1, 2026
This Privacy Policy explains how Recipe Clipper ("Recipe Clipper", "we", "us", or "our") handles information when you use the Recipe Clipper Chrome extension and its related cookbook service.
Recipe and website content. When you explicitly activate the extension on the current browser tab, Recipe Clipper accesses that page to extract recipe information. This may include the recipe title, source URL, ingredients, preparation steps, and an image displayed on the page. Recipe Clipper does not continuously monitor your browsing activity or collect your browsing history.
Account and authentication information. If you choose to sign in or create an account, the cookbook service processes your username and password. Your password is submitted directly to the cookbook website and is not read or stored by the Chrome extension. The service stores a salted password hash rather than the password in readable form. After a successful sign-in, the extension stores an authentication token in Chrome's local extension storage so it can access your cookbook account.
Technical information. When the extension communicates with the cookbook service, the service and its hosting provider may process technical information normally included in web requests and server logs, such as IP address, request date and time, requested endpoint, browser information, and error or security events. This information is used to operate, secure, and troubleshoot the service, not to build a browsing profile or serve advertising.
Recipe extraction, review, editing, and print preparation are performed locally in your browser. Recipe Clipper may store the current extracted or edited recipe in the extension's local storage so that it can be displayed in the editor or print view. This locally stored recipe remains until it is replaced or the extension's stored data is cleared.
The authentication token is stored locally by the extension. It is sent only to the Recipe Clipper cookbook service over HTTPS when an authenticated request is required. An expired or rejected token is removed when the extension detects that the session is no longer valid. You can also remove locally stored extension data through Chrome or by uninstalling the extension.
Recipe Clipper sends information to cartedebucate.onrender.com only when needed for an action you request:
Merely extracting, reviewing, editing, printing, or saving a recipe as a PDF does not send the full recipe to the cookbook service. When you are signed in, the recipe's source URL may still be sent automatically for the duplicate check described above.
We use the information described above only to:
The cookbook service is hosted by Render. Render may process stored data and technical request information as necessary to provide its hosting and infrastructure services. You can read Render's Privacy Policy for more information about its practices.
We do not sell user data. We do not use or transfer user data for personalized advertising, retargeting, credit decisions, or sale to data brokers. We do not allow people to read user data except when you give explicit consent for support, when necessary for security or abuse investigation, when required by law, or when data has been aggregated and anonymized for internal operations.
We may disclose information when reasonably necessary to comply with applicable law, protect users or the service, investigate fraud or abuse, or complete a merger, acquisition, or sale of assets subject to any consent required by law.
Recipes saved to your cookbook are retained until you delete them or request their deletion. Account information is retained while your account is active or as needed to provide and secure the service. Technical logs are retained according to operational and hosting requirements for security, reliability, and troubleshooting purposes.
You can manage or delete saved recipes through the cookbook website. To request access to, correction of, or deletion of your account and associated data, contact us using the email address below.
Recipe Clipper uses HTTPS to transmit information between the extension and the cookbook service. Passwords are stored as salted hashes, and authentication tokens are handled as confidential information. No method of transmission or storage is completely secure, but we use reasonable measures designed to protect the information handled by the service.
You can use Recipe Clipper to extract, edit, and print recipes without signing in. Signing in is required only for account features such as duplicate checking and saving recipes to your cookbook. You can choose not to use those features, clear the extension's local data in Chrome, delete saved recipes, or request deletion of your account.
Recipe Clipper's use of information received from Chrome APIs complies with the Chrome Web Store User Data Policy, including the Limited Use requirements. Such information is used only to provide or improve Recipe Clipper's user-facing features and related security and reliability.
We may update this Privacy Policy when Recipe Clipper's features or data practices change. The updated policy will be posted on this page with a revised "Last updated" date.
For privacy questions or data requests, contact: ancamariadaczo@gmail.com