Normal image editing
Selected images are handled by the browser runtime during normal use. QuokkaPix does not need a server-side image-processing upload for resize, crop, compression, conversion, background, metadata or PDF workflows.
Privacy Policy
Privacy Policy
This page explains what data QuokkaPix may handle, what stays on your device, and when third-party services may receive technical information.
What this policy covers
This policy applies to the QuokkaPix website, the image editor, and support requests. It describes technical data, local browser preferences, and messages that you choose to send us.
Image processing
The main QuokkaPix editing flows process images locally inside your browser on your device. During normal use, we do not upload your files to our own servers.
Browser storage and saved preferences
QuokkaPix may use localStorage to remember language, theme, tool settings, and saved workflow preferences on this device.
Analytics, ads, and third-party services
If Google Analytics is available, QuokkaPix may send technical product and agent events through gtag: tool, mode, selected file count, output type, result size, duration, status and error category. These analytics events are sanitized and must not include image bytes, file names, local paths or user-written text. Advertising scripts, when enabled, and Google Analytics may still receive normal browser request data such as IP address, browser type, referrer and cookie or device identifiers under their own policies. You can limit this with browser privacy settings, tracker blocking or the provider opt-out tools.
Agent, recipe, and payment endpoints
Public agent discovery files, recipe catalogs, rule catalogs, and Coinbase x402 payment endpoints are served by QuokkaPix so browsers and local agents can understand available workflows and paid agent batches can request an unlock token. These endpoints can create technical server logs such as request path, status code, user agent, coarse country header when available, payment challenge, unlock token status and verification or consumption status. They do not receive the local image bytes processed by the browser.
What local processing does not hide
Local image processing means the selected image bytes are not sent to our processing server during normal editing. It does not prevent your browser, network provider, analytics provider, advertising provider, payment facilitator, or the destination website where you later upload an export from seeing their own normal technical data.
Support email
If you contact support@quokkapix.com, we receive only the information that you include in your message so we can reply and help.
Practical privacy boundaries
QuokkaPix separates image processing from site delivery. The editor can run locally in the browser, while the website may still use normal web infrastructure such as hosting logs, advertising scripts, analytics, email support and agent payment endpoints.
| Area | Boundary | User control |
|---|---|---|
| Image pixels | Processed in the browser during normal use. | Keep originals on your device and download only the outputs you choose. |
| Browser preferences | Language, theme and tool choices can be stored locally. | Clear site data in the browser if you want to reset preferences. |
| Agent payments | Paid agent unlock endpoints can record technical payment and verification events. | Use payment endpoints only when an agent batch needs an unlock token. |
| Support email | Messages include only what you decide to send. | Avoid sending private image files unless support explicitly asks for a diagnostic example. |
What QuokkaPix does not do in normal editor use
- It does not require a user account for the browser editor.
- It does not host your selected source images as a normal processing step.
- It does not provide a public server-side image processing API.
- It does not remove visible private information that is part of the pixels, such as faces, addresses or text inside the image.
How local editing interacts with external services
Third-party scripts
Advertising, analytics and payment-related providers may receive technical request data when their scripts or endpoints are used. This is separate from sending source image files for processing.
Agent and x402 flows
Agent payment endpoints issue or verify unlock tokens for paid agent batches. They do not receive the local image bytes; the MCP runner and browser still pass files through the local file input.
Policy updates
We may update this policy when the product, connected services, or legal requirements change. The date above shows the latest revision.