CookifyPrivacy Policy
Effective November 6, 2026
Cookify has no servers, no accounts and no analytics, and its developer doesn't receive your data. Your data stays in your browser unless you send it somewhere yourself: to an API, to your own Google Drive or to an export file.
What Cookify stores
Cookify keeps the following in your browser's extension storage. It doesn't add its own encryption to this storage.
| Data | What it is |
|---|---|
| Cookies and tokens | The cookies and JWT tokens you save in Cookify. |
| Saved logins | The login request Cookify remembers so it can renew a token. It can include the username and password you sent to your API. |
| API workspace | Saved APIs and environment addresses, favorites, open tabs, request drafts, templates, recent requests and preferences. |
| API documents | Cached copies of the OpenAPI documents of the Swagger UI pages you open. |
| Google account | Your email address and profile picture, only if you connect Google Drive sync. |
How Cookify uses web pages
Cookify's scripts run on the pages you open so they can detect Swagger UI. This happens in your browser. Cookify keeps data only for Swagger UI pages, and it doesn't record your browsing history.
Cookify doesn't read the cookies in your browser. It only sets or removes a cookie when you choose to apply or delete one.
When data leaves your browser
- Your APIs: When you send a request, it goes directly from your browser to the address you chose, with the values and token you set for it.
- Google Drive (optional): If you connect sync, Cookify stores a copy of your cookies, tokens, saved logins and API workspace in a private app folder in your own Google Drive. Cookify doesn't add its own encryption to this copy, so it's protected by your Google account. Google handles it under the Google Privacy Policy.
- Export files: An export holds your data, including tokens, cookie values and saved logins, and you decide where to keep it. With a password, the file is encrypted with AES-256. Without one, anyone who has the file can read it.
Google user data
When you connect sync, Cookify asks Google for access to its own app folder in your Drive (drive.appdata) and for your basic profile (openid, email, profile). It can't see your other Drive files.
Cookify uses this data only to show which account is connected and to save and read your sync data. It isn't sent to the developer or anyone else, and it isn't used for advertising.
Cookify's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
What Cookify doesn't do
- It doesn't sell or share your data.
- It doesn't show ads.
- It doesn't use analytics or tracking.
- It doesn't send your data to any server run by the developer.
Keeping and deleting your data
- In your browser: Your data stays until you delete it. Removing the extension deletes what it stored in your browser.
- In Google Drive: Disconnecting stops sync but doesn't delete the copy. To delete it, open Google Drive on a computer, go to Settings > Manage apps, open the Options menu next to Cookify and delete its hidden app data.
- Export files: Delete them like any other file.
Changes
If this policy changes, the new version will be published on this page with a new effective date.
Contact
Cookify is made by Emre Demircan (emrecpp). For privacy questions, open an issue on GitHub. Issues are public, so don't include tokens or other private data.