Pixseer privacy policy
Updated 5 September 2026 · macOS, Windows, Linux and website demo
This policy covers both the Pixseer app for macOS, Windows and Linux and the pixseer.app website. It is written from what the software actually does, not from a template. Where a claim is about code, you can check it: Pixseer’s network calls are listed in section 4 with the hosts they contact.
1. Who is responsible
The data controller is:
Pixseer is developed and licensed by Adam Havlíček, trading as ADMOX
A sole trader (OSVČ) established in the Czech Republic.
Registered business address: Malhostovice 42, 666 03 Malhostovice, Czech Republic.
Business identification number (IČO): 19654511.
Registered in the Czech Trade Register (živnostenský rejstřík). Responsible trade-licensing authority: Městský úřad Tišnov.
Legal and privacy: adam@admox.xyz · Support and refunds: support@pixseer.app
We are a one-person business. There is no data team, no CRM, and no analytics warehouse. We have not appointed a data protection officer, because we are not required to.
2. The short version
- Pixseer is local-first. Your images, prompts, metadata, tags, notes, favourites and settings are stored on your computer. Core library browsing does not upload them to us. Optional services you choose, including AI backends and remote computers, are described in section 4.
- There are no accounts. You never create one, and we never hold a password.
- The app contains no analytics and no telemetry. The desktop app does not send us usage analytics, session recordings or crash reports.
- We never sell or rent personal data, and we do not use it for advertising or profiling.
- The app makes network requests in only a handful of situations, all listed in section 4. Three of them happen without you asking: the update check on start, the licence re-check on start, and a background prefetch of the help videos for your interface language a few seconds after launch.
- The website uses self-hosted, cookieless analytics. It sets no tracking cookies. The demo uses local storage for its functionality and your choices. See section 6.
- Your purchase is handled by Lemon Squeezy as merchant of record. They hold your payment details, not us. See section 5.
3. What stays on your computer and never reaches us
All of the following is stored locally, and none of it is transmitted to us:
The app uses the following folders for the current desktop releases. On Linux, $XDG_DATA_HOME defaults to ~/.local/share and $XDG_CACHE_HOME defaults to ~/.cache. On Windows, %APPDATA% and %LOCALAPPDATA% refer to your own user profile.
| Platform | App data | Settings and saved library data |
|---|---|---|
| macOS | ~/Library/Application Support/Pixseer/ | ~/Library/Application Support/xyz.admox.pixseer/store/ |
| Windows | %APPDATA%/Pixseer/ | %APPDATA%/xyz.admox.pixseer/store/ |
| Linux | $XDG_DATA_HOME/xyz.admox.pixseer/ | $XDG_DATA_HOME/xyz.admox.pixseer/store/ |
| What | Where |
|---|---|
| Your images, sidecars and exports | The folders you choose; these are separate from app data. |
| Notes, favourites, tags, pinned and saved folders, settings and assistant history | The settings folder above, with local webview storage used by the interface. |
| Library index: file rows, generated tags, embeddings and search text | index.db and its SQLite companion files in the app-data folder above. |
| Optional AI models and inference runtimes | ai/, models/ and bin/ under app data, depending on the model you install. |
| Help videos | help-videos/ |
| Licence key and activation record | license.json under app data. File permissions differ by operating system; see section 13. |
| API keys, access tokens and connected-site sessions | Local settings, app-data files or the system webview’s storage. They are used to contact the service you configured; they are not sent to us. |
| Thumbnail cache | macOS: ~/Library/Caches/xyz.admox.pixseer/thumbs/Windows: %LOCALAPPDATA%/xyz.admox.pixseer/thumbs/Linux: $XDG_CACHE_HOME/xyz.admox.pixseer/thumbs/ |
| Temporary previews, pasted images and working copies | Your system temporary directory, or a custom temporary folder you select in Settings. |
| SSH connection settings | Local app settings. Pixseer uses your system SSH client, existing keys, known-hosts file and agent. |
| SSH connection-sharing sockets | ~/.pixseer/ssh/ on macOS and Linux. Windows uses separate SSH connections and does not create these sockets. |
Paths below the app-data folder are relative to the platform row above. Windows accepts these paths with backslashes too. The system webview may also keep cookies and interface storage in its own per-user data directory; uninstalling the executable alone does not necessarily remove that data. Cloud-synced folders and backups you configure are managed by your operating system or backup provider, not by Pixseer.
The library index is a cache. Every row can be rebuilt from your files, so deleting it loses nothing but time.
4. When the app talks to the internet, and what it sends
Requests go directly from your computer to the named service. Our update and help files are served from our Cloudflare-backed download domain; third-party lookups and AI requests are not relayed through a Pixseer content server. As with any internet request, the service you contact necessarily sees your IP address.
4.1 Update check (automatic, on every launch)
Pixseer requests the update manifest at https://updates.pixseer.app/latest.json when it starts, and shows a banner when a compatible update is published for your platform. The current manifest provides in-app updates for macOS on Apple Silicon and Windows x64. Linux users install a newer.deb from the download page; a Linux in-app update is not currently published. The manifest is a static file on Cloudflare R2 served through Cloudflare. The request contains no licence key, no identifier and no information about you or your library. The server sees your IP address, your user agent and the time.
We are being precise here: this check happens automatically and the current version has no setting to switch it off. Installing an update is always your decision. In-app updater downloads are checked against an embedded signing key before installation. A manually downloaded installer follows the installation and verification process of its platform.
4.2 Licence activation and re-check (Lemon Squeezy)
- When you activate, Pixseer sends your licence key and a device label to
https://api.lemonsqueezy.com/v1/licenses/activate. The device label is your operating-system user name and computer name, in the formuser@hostname. On Windows these come fromUSERNAMEandCOMPUTERNAME; macOS and Linux use the user name and short hostname. Its only purpose is to let you recognise your own activations when you manage them. It is not a hardware fingerprint. - On every launch, Pixseer re-checks the key and activation with the same provider. If the network is unavailable, nothing happens and you keep working.
- When you deactivate, Pixseer asks the provider to release the slot.
The provider’s reply to those calls includes the name and email address on the order. Pixseer reads only what it needs from the reply and stores only your licence key, the activation id and two timestamps. The name and email are not saved, not logged and not sent anywhere.
4.3 Looking up images, posts and models (only when you ask)
When you paste a link, drop in a file to identify, or open a model’s details, Pixseer fetches publicly available data from the site involved. Depending on what you asked for, that can include the URL you gave it, an image or post identifier, or a file hash used to identify a model. If you have entered an API token for a site, it is sent to that site to authorise your request.
Sites Pixseer can contact this way include CivitAI, Hugging Face, Pixiv, X (Twitter), Reddit, Tumblr, Patreon, Pinterest, DeviantArt, LiblibAI, Tusiart and Tensor.art, together with their media and API hosts. Each has its own privacy policy, which governs that traffic.
4.4 Downloading optional on-device AI models
Nothing AI-related is bundled in the download. If you turn on on-device AI, Pixseer fetches model files from Hugging Face and the ONNX Runtime library from GitHub (the Microsoft onnxruntime releases). Other optional local backends can use separately downloaded model files and runtimes such as llama.cpp, or an Ollama installation you manage. These are ordinary file downloads. Once they are on your computer, that AI runs entirely offline and no image or text leaves your machine.
4.5 Help videos (automatic prefetch, on every launch)
Help videos are not bundled either. They are downloaded from https://updates.pixseer.app/help/v1/<language>/… and cached locally. A few seconds after launch, Pixseer quietly prefetches the whole set for your interface language so that Help plays instantly, and it stops silently if you are offline. Opening a video that is not cached yet downloads that one on demand.
These requests reveal your IP and, because the path contains the language code, the interface language you are using. They carry no licence key and no identifier.
4.6 AI backends that you configure (never on by default)
Pixseer has no AI account and no AI credits of its own. If you want cloud AI, you supply the backend. There are three shapes:
- On-device models. Nothing leaves your computer.
- An OpenAI-compatible API. You give Pixseer a base URL and your own API key. Pixseer then sends the text, conversation context or image needed for the feature to that endpoint, using your key. That can be a commercial provider or gateway, for example OpenRouter or OpenAI, or a server on your own network.
- An AI command-line tool you already have installed, for example Claude Code, Codex or Gemini. Pixseer runs the tool on your computer. The tool then talks to its own vendor under your subscription, and that vendor’s terms and privacy policy apply.
In all three cases the choice, the account, the cost and the data handling on the provider’s side are yours. We receive nothing.
4.7 Browsing your own machines over SSH
If you connect Pixseer to another computer of yours, for example a machine running ComfyUI, it uses the system ssh binary with your existing keys and agent. The SSH client must be installed and available; on Windows this can be the Windows OpenSSH client. The connection goes from your computer to your machine. We are not involved, and there is no relay or proxy of ours in the path.
4.8 Local assistant tools and integrations
If you enable the local MCP integration, a client you configure can connect to a token-protected endpoint on your own computer. The client can receive the library information exposed by the tools it uses. If that client uses a cloud AI provider, information it passes onward is handled under that provider’s policy. Local assistant conversation history and tool records can remain in your app settings. We do not receive those conversations or run a relay for them.
4.9 Installation dependencies
On Windows, the installer may fetch Microsoft Edge WebView2 from Microsoft if the required runtime is missing. On Linux, your package manager may contact its configured repositories to install dependencies. Those operating-system and installer requests follow the respective provider’s privacy policy and are separate from Pixseer’s library processing.
4.10 Feedback and support
The in-app feedback option opens your email client with a pre-filled message addressed to us (adam@admox.xyz). Nothing is sent from the app itself: you decide whether to send it, and you can see and edit the message first. If you do send it, we receive whatever you wrote, plus your email address, and we keep it only as long as we need it to help you.
5. Buying Pixseer
Purchases go through our store on Lemon Squeezy, which acts as merchant of record. Lemon Squeezy is operated by Sold through Link, LLC (formerly Lemon Squeezy, LLC), a Stripe company, in the United States.
- Lemon Squeezy collects and processes your payment and billing details, determines and remits sales tax and EU VAT, issues the invoice, and holds the card data. We never see your card details. Their privacy policy and buyer terms govern that processing, and for the payment transaction they act as their own controller.
- We receive the order information we need to fulfil and support the sale: your name, your email address, your country and any tax number for tax purposes, the order and product identifiers, the amount paid, and your licence key and its activations. We access this in the Lemon Squeezy dashboard. We do not copy it into a database of our own.
- Their platform sends our website a webhook when an order is created or refunded, or a licence key is created. Our server verifies the signature and writes only the event name and its identifier to its log. It does not store your email address or any other order detail in an order database. On a refund, the handler also looks up and disables the order’s licence keys through Lemon Squeezy and logs the relevant identifiers and outcome.
- Lemon Squeezy processes data internationally, including in the United States. Its privacy policy describes where it processes data and the safeguards that apply to international transfers.
6. The website (pixseer.app)
6.1 Analytics
The site loads Umami, an open-source analytics tool that we host ourselves at umami.admox.xyz. It is configured in its default cookieless mode:
- it sets no cookies and stores nothing on your device;
- it records page views with the page URL, the referrer, and coarse browser, operating system, device-type, screen-size and country information;
- it does not build a cross-site profile, and the data is not shared with anyone or used for advertising;
- because it is self-hosted, the data stays on our own server and is not sent to a third-party analytics company.
These analytics use no tracking cookies. The demo separately uses browser storage for its functionality and your choices, described below.
6.2 The “try it” demo
The site has a drop zone that reads the metadata out of an image you drag onto it. That parsing happens entirely in your browser. The image is never uploaded to our server, and it never leaves your computer.
The demo allows three successful personal-image previews per browser. A local counter remembers this limit between visits. Your image and its embedded metadata stay in memory for the current page session and are discarded when the page closes or reloads. The website also stores your appearance choice, demo notes, favourites, tags and settings in local storage. Session storage remembers the last decorative image set and loading animation so the next visit can vary them. These settings are not advertising identifiers.
On the production website, an anonymous event is sent when a preview is used or when the limit is reached. It contains only the event name and preview count. The receiving server can also record a coarse country code and a shortened browser user-agent. No image, filename, prompt, note, tag, unique visitor identifier or licence key is included. Clearing this site’s browser storage removes your saved demo settings and counter.
6.3 Fonts, scripts and embeds
Web fonts are downloaded at build time and served from our own domain, so your browser does not contact a font provider. The typography helper scripts are also served from our own domain. The site loads no ad networks, no social pixels, no chat widget, no error-tracking service and no third-party embeds. Apart from the analytics script in 6.1, everything the site loads comes from us.
6.4 Server logs and hosting
The site runs on a server we operate, with Cloudflare in front of it. Like any web server, it keeps standard access logs which include IP addresses, requested paths, timestamps and user agents. We use them to run and secure the site, and we keep them only as long as we need them for that.
The app download itself is served from Cloudflare R2. Downloading it requires no form, no email address and no account.
7. Legal bases for processing (GDPR Article 6)
| What we process | Why | Legal basis |
|---|---|---|
| Licence key and device label, at activation and re-check | to deliver and protect the licence you bought | performance of a contract, Art. 6(1)(b) |
| Order data we see in the Lemon Squeezy dashboard (name, email, country, order and licence details) | to fulfil the sale, provide support, and handle refunds | performance of a contract, Art. 6(1)(b) |
| Rejecting licence keys that were not bought from our store, and disabling refunded or abused keys | to prevent piracy and payment fraud | legitimate interests, Art. 6(1)(f) |
| The update check, the help-video prefetch, and the signature verification of downloads | to deliver the updates and help content included in your purchase, and to keep them tamper-proof | performance of a contract and legitimate interests, Art. 6(1)(b) and (f) |
| Requests to third-party sites and AI backends that you trigger | to carry out the action you asked for | performance of a contract at your request, Art. 6(1)(b), and your instruction for optional features |
| Cookieless website analytics | to understand, in aggregate, whether the site works | legitimate interests, Art. 6(1)(f) |
| The “try it” abuse beacon | to detect circumvention of the free-look limit | legitimate interests, Art. 6(1)(f) |
| Web server and Cloudflare access logs | to operate and secure the site | legitimate interests, Art. 6(1)(f) |
| Emails you send us | to answer you | performance of a contract or legitimate interests, Art. 6(1)(b) or (f) |
| Keeping records of sales for accounting and tax | because the law requires it | legal obligation, Art. 6(1)(c), mainly discharged by Lemon Squeezy as merchant of record |
We do not rely on consent for anything the app does automatically, because nothing the app does automatically is optional tracking. We do not process special-category data, and we do not carry out automated decision-making that has a legal effect on you.
8. What we never collect
To be blunt about the things people usually worry about, we do not:
- collect, upload, scan, index or view your images, prompts, tags or notes;
- collect any analytics, usage statistics, feature counters, session recordings or crash reports from the app;
- collect a hardware fingerprint, advertising identifier, MAC address or serial number;
- collect your file names, folder paths or library size;
- collect the contents of your AI prompts or AI responses;
- hold your card number, IBAN or full billing address;
- hold a password of yours, because there is no account;
- store the name or email address that the licensing provider returns to the app;
- use cookies for tracking, on the website or anywhere else;
- sell, rent, share or trade personal data, or run advertising;
- use your data to train any AI model.
If we ever want to add optional diagnostics, it will be opt-in, clearly described, and this policy will be updated before the feature ships.
9. Who else is involved
The parties involved depend on which features and platform you use:
| Party | Role | What they get |
|---|---|---|
| Lemon Squeezy (Sold through Link, LLC, US) | merchant of record, payments, tax, licence keys | payment and billing details, your email and name, order and licence data, activation device labels |
| Cloudflare (US/EU) | serves the website, the updater manifest, the app download and the help videos | IP addresses and request metadata for those requests |
| Our own server (EU) | runs the website and our self-hosted analytics | access logs, cookieless analytics events |
| Hugging Face, GitHub (US) | host the optional AI models and the inference runtime you may download | your IP and which files you requested |
| Image and model sites you use (CivitAI, Pixiv, X, Reddit, Tumblr, Patreon, Pinterest, DeviantArt, LiblibAI, Tusiart, Tensor.art) | you fetch public data from them | your IP, the URL or hash you looked up, and any token you set for that site |
| Microsoft and your Linux distribution’s package repositories, where needed | provide operating-system webview or installation dependencies | request metadata for downloads and any diagnostics governed by their own policies |
| The AI provider you configure, if any | processes what you send it | whatever the feature sends, under your own account |
We have not appointed any of them as a processor acting on our behalf for your app content, because none of them receives your app content from us.
10. How long things are kept
- On your computer: for as long as you keep it. Uninstalling Pixseer may leave app data, settings, webview storage and caches behind. To remove those, close Pixseer and remove the relevant folders from section 3, together with its webview storage. Your original images, exports, backups and any files in folders you chose remain separate. Deactivate the licence before uninstalling if you want to release its activation slot; deleting
license.jsonalone does not deactivate the server-side record. - Order and licence records: held at Lemon Squeezy for as long as they need them for accounting, tax and dispute handling. Any records we are legally required to retain are kept for the applicable accounting, tax or dispute-handling period; that period depends on the type of record.
- Support email: kept while we are helping you, and then for a limited period in case you come back to the same issue.
- Website analytics and server logs: kept only as long as we need them to operate and secure the site and to understand aggregate traffic.
If you want the exact retention period that applies to something of yours, ask at adam@admox.xyz and we will tell you.
11. Your rights
Under the GDPR you have the right to ask us to give you a copy of your personal data, correct it, delete it, restrict how we use it, or transfer it, and to object to processing we base on legitimate interests. Where we ever rely on consent, you can withdraw it at any time.
Write to adam@admox.xyz and we will answer within one month. We may need to confirm you are the person the data relates to, usually by replying from the email address on the order.
Two practical notes:
- Because Pixseer stores your content only on your computer, an access or deletion request to us is unlikely to produce much: we have your order and licence record and any emails you sent, and little else. You can delete the app-side data yourself at any time by removing the folders listed in section 3.
- For payment and billing data, you may also need to contact Lemon Squeezy directly, since they hold it as merchant of record.
You may complain to a supervisory authority. In the Czech Republic that is the Office for Personal Data Protection (Úřad pro ochranu osobních údajů, uoou.gov.cz). You may also complain to the authority in your own EU country.
12. Children
Pixseer is not aimed at children and is intended for people old enough to buy software and to be responsible for the content they choose to manage with it. We do not knowingly collect data from children.
13. Security
Licence keys and connected-site tokens are stored locally; local storage is not a promise of encryption. On macOS and Linux, Pixseer attempts to restrict the licence file to its owner with 0600 permissions. On Windows, access follows the permissions inherited from your user-profile folder; Unix mode bits do not apply. Keep your operating-system account and backups secure.
Apple signing, notarisation and the hardened runtime apply to the macOS build only. They are not Windows or Linux security certifications. The in-app updater verifies its signed update artifacts before installation; this is separate from operating-system installer signing and does not describe manually installed Linux packages. Our website webhook verifies its signature with a constant-time comparison before handling events.
14. Changes to this policy
We may update this policy. The date at the top changes when we do, and material changes will be announced on the website and, where relevant, in the app. The current version is always on this page.
15. Contact
ADMOX (Adam Havlíček), Czech Republic
Privacy and legal: adam@admox.xyz
Support: support@pixseer.app
Web: pixseer.app
Related documents: the licence agreement and the refund policy. The third-party notices ship in the app under About, Open-source licenses.
Related: License agreement · Refund policy · Support