How CookPDF Handles Files
CookPDF · 7/16/2026
Last updated: 07/17/2026
Effective date: 07/16/2026
Last updated: 07/16/2026
CookPDF clearly distinguishes two flows: standard PDF tools process on your device; AI features send the necessary data to the third-party AI service provider used by CookPDF when the user actively requests it.
1. PDF tools that process on your device
With standard PDF tools such as merge, split, organize, edit, or operations provided in the browser, files are read and processed on your computer, phone, or tablet. Files are not uploaded to CookPDF servers to perform the main operation.
The browser still connects to CookPDF to load the interface, application code, fonts, and website resources. Common technical data such as IP address, browser type, and error logs may be generated when accessing the website, but this does not mean PDF content is uploaded.
2. Cache, autosave, and session recovery
To avoid losing work when reloading the page or reopening a tab, CookPDF may store files, editing state, and related history in the local storage area the browser grants to the website, such as IndexedDB or cache memory.
This data resides on your device and in your browser profile. The data may persist until you delete the session, choose to start over, replace the file, the browser cleans it up on its own, or you delete the website data. CookPDF may apply local storage limits to protect browser performance.
3. AI tasks and service providers
When you actively choose PDF Assistant, PDF Q&A, PDF Summary, PDF Translate, PDF Question Generator, or another AI task, the necessary data is sent to the third-party AI service provider used by CookPDF to generate results. The data may include extracted files or text, questions, instructions, language, task selection, and the necessary conversation context.
The third-party AI service provider used by CookPDF processes data according to the configuration, agreements, and policies applicable to the service that CookPDF uses. CookPDF does not assert a retention period or training policy different from the actual conditions of the third-party AI service provider connection used by CookPDF. You should not send confidential documents or sensitive data unless necessary.
4. AI task history and recovery
CookPDF may store conversation history and AI session state locally in the browser so users can continue their most recent task. When you continue a conversation or switch to another AI task, the necessary context may be sent again to the third-party AI service provider used by CookPDF. Deleting website data or starting a new session may lose the local history.
5. Payment data
If you purchase a plan, the payment process is carried out through PayPal or Airwallex. CookPDF receives the information needed to confirm the transaction and plan benefits; sensitive payment information is handled according to the interface, terms, and policies of the chosen provider.
6. Data protection
The website connection uses HTTPS. HTTPS protects data during transmission but does not replace protecting your device and account. Lock your device, protect your login credentials, keep a copy of your original files, and delete browser data on shared devices.
7. How users control their data
- Delete files or sessions in the interface where the function is provided.
- Choose to start over to remove the cached session.
- Delete cookies and CookPDF website data in your browser settings.
- Do not use AI tasks if you do not want the necessary data sent to the third-party AI service provider used by CookPDF.
- Contact support@cookpdf.io or legal@cookpdf.io when you need help.
8. Changes to the processing method
If CookPDF changes its processing method or an important provider, this content and the notices on the relevant functions will be updated before or at the same time the change takes effect.