1. What this policy covers
This Cookie Policy explains cookies and related browser technologies used with PicFitly at picfitly.com. Read it with our Privacy Policy, which explains contact messages, service providers and your rights.
Our current website code does not set advertising, analytics, account or preference cookies, and does not store data in localStorage, sessionStorage or IndexedDB. It does use temporary page memory to process images and submit contact messages. Cloudflare’s infrastructure may use security cookies, and the website sends network error reporting instructions to supported browsers.
A routine response check on 8 September 2026 returned no Set-Cookie header. That check is not a guarantee that no visitor will receive a cookie: security measures can differ by request and browser, and a challenge may set a cookie later.
2. Cookies and similar technologies
A cookie is a small value saved by a browser and sent with later requests to the relevant website. Session cookies normally last for a browser session; persistent cookies have an expiry. A first-party cookie relates to the site being visited, while third-party contexts involve a different site. A provider such as Cloudflare can set a cookie while delivering our own domain.
Browser storage, cached files, temporary page memory and network reporting instructions are different technologies with different purposes. An image preview in memory is not a tracking cookie. The sections below explain the current uses instead of treating all browser data as the same thing.
3. Current cookies and browser storage
| Technology | Purpose and status | Duration |
|---|---|---|
| PicFitly application cookies | None currently set by our code. There are no login sessions, advertising cookies or saved cookie preferences. | Not applicable. |
| Cloudflare __cf_bm | May be used if Cloudflare bot protection applies. This is a conditional provider example, not a claim that it is set for every visit. | Cloudflare documents expiry after 30 minutes of inactivity. |
| Cloudflare cf_clearance | May record security challenge or detection state when Cloudflare protection requires it. | Depends on the active challenge configuration; see the expiry shown in your browser. |
| Temporary page memory | Holds selected images, results, tool settings and, on the contact page, the current message and retry reference. This does not identify you across separate browsing sessions. | Until cleared or the page state is discarded by the browser. Browser restoration behavior may vary. |
| Browser cache and downloads | The browser may cache site assets; downloads are files you explicitly save. These are not used by PicFitly to track visits. | Controlled by the browser and by you. |
| Network Error Logging configuration | Cloudflare response headers tell supported browsers where to send network failure reports. This is separate from cookies and advertising analytics. | The observed instruction lifetime is seven days and may be refreshed by later responses. This is not a promise about report retention. |
| localStorage, sessionStorage and IndexedDB | Not used by the current PicFitly application. | No application entries are created. |
Conditional security cookie names and lifetimes follow Cloudflare’s cookie documentation. The exact cookies visible to you depend on protection features and the requests you make. We have not installed an advertising platform, analytics tag, social-media embed or third-party consent manager.
4. Security and network failure reports
Cloudflare delivers and protects PicFitly. It can process technical request information even when a response sets no cookie. Supported browsers may also send connection failure reports to a Cloudflare reporting endpoint when instructed by the website’s response headers. Such reports concern network reliability; they are not image uploads or a visitor marketing profile.
The headers observed for the current site request no reports for successful connections. Failure reporting depends on browser support and network conditions. See Cloudflare’s Network Error Logging documentation and our Privacy Policy for the distinction between infrastructure data and local image processing.
The form’s submission limiter uses a daily IP-derived hash on the server. It does not set a rate-limiting cookie in your browser. Clearing cookies does not delete that server-side record or a previously sent message.
5. Optional cookies and consent
There are currently no optional advertising or analytics cookies to accept or reject, so the site does not display an optional-cookie consent panel. Continuing to browse is not treated as consent to introduce them.
If we introduce an optional feature using cookies or similar technologies, we will update this policy and provide the information and choices required by applicable law before activating it. Where prior consent is required, the feature will remain off until you choose to enable it, and there will be a way to withdraw that choice.
Security technologies are limited to the purpose for which they are used; describing a technology as a security tool is not a general permission to use it for advertising. The current site has no marketing tracking to opt out of.
6. How to control browser data
- View cookies: use your browser’s site information or privacy settings to inspect the cookies and site data associated with picfitly.com.
- Delete site data: remove the site’s cookies and cache in browser settings. Security checks may need to run again. Browser controls vary and may not clear every kind of network reporting state.
- Block cookies: use the browser’s cookie controls. Local image conversion has no application-cookie dependency, but blocking security cookies may stop a Cloudflare-protected request or trigger repeated challenges.
- Clear local work: use Clear all files in the image tool and close the tab when finished. Delete downloaded images or ZIP files separately if you no longer want them.
- Protect message drafts: the form does not save a draft in persistent application storage. Your browser may offer autofill or page restoration according to its own settings.
Cookie controls do not remove email already delivered or form data held on the server. For those requests, use the contact form. We do not sell or share data for targeted advertising, regardless of Do Not Track or Global Privacy Control signals; those signals are not a deletion request.
7. Other sites and services
Following an external link or opening your own email service takes you to a service with its own cookies and policies. Gmail is used to receive correspondence, but no Gmail content is embedded in the image tools. The fact that a provider uses cookies on its own website does not mean all of those cookies are present on PicFitly.
For provider information, see Cloudflare’s Privacy Policy and Google’s Privacy Policy. You can contact us about the use of these services without sending any image files.
8. Updates and contact
We will revise this page when cookies, browser technologies or related choices change. The date above identifies the current notice; it does not extend an existing cookie’s expiry or replace consent where consent is required.
For questions about cookies or privacy, use the contact form with the Privacy request topic.