Privacy Policy
Last updated: November 19, 2026
The short version
PixaFind searches your files on your own computer. It never uploads your files, photos or what is inside them. The AI models run on your hardware, not in the cloud.
A few things do use the internet, and this page lists each one. The biggest are anonymous usage counts, crash reports and masked screen recordings of the app. They are on by default, and you can turn them off in Settings. They never include what you type in search or what is inside your files.
What never leaves your computer
- Your files and photos
- The text inside your documents
- Your search index (embeddings and metadata), kept in your app data folder
Usage counts and crash reports
From version 0.6.13, the app sends two kinds of data to help us fix bugs and see which features people use. Both are on by default. You see the switch during setup, and you can turn it off at any time in Settings, under Data & Privacy. Off means nothing in this section is sent.
Usage counts go to PostHog, on servers in the United States. Each one is a fixed event name with a few numbers:
- The app started, or updated from an older version
- A search ran: the search mode, the number of words, the number of results and how long it took
- A result was opened, and its position in the list
- The upgrade button was clicked
- The app was installed, setup was finished, the first search ran, the free plan's folder or file limit was reached, the upgrade window opened, a plan was clicked, and each step of signing in or activating a licence, with whether it worked
- A model download started, finished or failed, its size in MB, how long it took and a short error code
- From version 0.7.14, during first setup and before an install ID exists: which setup screen you reached, and the first model download. Each of these counts gets a new random ID, so they cannot be linked to each other, to your install ID or to you. They start only after the first screen has shown the line about usage counts, and the switch turns them off
- From version 0.7.18, on that same first screen: one count that the app opened for the first time, with only the app version and operating system. On Windows also one count with the seconds between the installer finishing and that screen. Each gets its own random ID, the same as above
- Indexing finished: photos or documents, the file count as a range (such as 1,000 to 2,000, and capped at 500,000), how long it took, and whether the free limit stopped it
- An update failed, with a short error code, or an update did not finish and the old version started again, with both version numbers
- The app froze for 10 seconds or more, with how many seconds and the app version
- Whether the search was text or image, how many filters it used, and that the search hotkey opened the search window (at most once every 10 minutes)
- The number of folders you index, as a range, and how many minutes the app stayed open
- Once per install: your RAM as a range, the number of CPU cores, whether you have a GPU and which one the app uses for AI, the GPU maker (NVIDIA, AMD, Intel or other) and its video memory as a range. The GPU model name is never sent
- Your app version, operating system and chip type
- A random install ID, made on your computer. It holds no name, email or licence key
Usage counts never include your search words, file names, folder paths or file contents. We turn off location lookup for each event and PostHog discards your IP address.
From version 0.7.18, Settings, under Data & Privacy, lists every usage count the app sent since it started (the last 200), exactly as sent. The list stays in memory, is never saved and is never sent anywhere. Crash reports are not in that list yet.
While usage counts are on, the app adds the install ID to the Pro plan links it opens. If you then buy, our payments server sends one purchase count with that ID, the plan, the amount and currency, and your country. It never sends your email. It also sends a count, with the same ID, when a payment is refunded or disputed, when a subscription renews, and when one is cancelled or ends. This lets us see which steps in the app lead to a purchase. With usage counts off, the links carry no ID.
Your email, only if you give it. The first-run screen has an optional email field, empty by default. If you fill it in, the app sends only that address and the word "onboarding" to pay.pixafind.com, where we store the address, that word and the date. It is not linked to your install ID, usage counts or licence. We use it only to email you about PixaFind. Ask through the contact page and we delete it.
Crash reports go to Sentry. They hold the error message, where in our code it happened, your app version and operating system. An error message can name a file or folder, for example a file the app could not read. They never include your search words or file contents.
From version 0.7.12, if the app freezes, closes without shutting down, or an update does not finish, it saves a small note on your computer: what happened, the app version and how many seconds it froze. It holds no file names or paths. The next time the app starts it sends the note to Sentry (and freezes and failed updates to PostHog as usage counts), then deletes it. With the switch off, the note is deleted unsent.
A bug report you send yourself from the app always goes through, even with the switch off, because you chose to send it.
Versions before 0.6.13 have no switch. Their beta builds send crash reports and app log lines, which can name folders, files and the words you search for. Update to get the switch.
Screen recordings of the app
The app also records how you use the PixaFind window and sends the recording to PostHog, on servers in the United States. This is called a session replay. It shows clicks, scrolls and which screens you open, so we can see where the app is confusing or broken.
The app masks the recording before it leaves your computer. Recordings never include your file names, folder paths, search text or file contents. They cover only the PixaFind window, never the rest of your screen.
Recordings are on by default. Turn them off at any time in Settings, under Data & Privacy.
AI models
On first launch the app downloads its AI models from Hugging Face. After that they run offline on your CPU or GPU. The app never sends your files or searches to any AI service.
Updates
The app checks GitHub for a new version and downloads it from there. The check does not include personal data. GitHub sees your IP address, like any download.
Buying and activating PixaFind
When you buy, our payment provider (Dodo Payments, or Stripe for older orders) handles your card. We never see your card number. We receive your email and order details, and we email your licence key through Resend.
When you activate a licence, the app sends three things to pay.pixafind.com:
- Your licence key
- A one-way hash of your computer's ID, so we can count devices without knowing which computer it is
- Your operating system and chip type, such as windows/x86_64
We store your email, licence and activated devices in our licensing database, so we can enforce device limits and handle refunds. We also send ourselves an internal notification when a licence is activated.
Our payments server also counts each checkout or subscription that starts or fails, and each licence activation that works or fails. Each count gets a new random ID and holds no email, licence key or IP address.
To spot attacks, our payments server logs failed sign-in codes, invalid licence keys, rejected payment notifications and rate-limit hits. Each log line holds the type, the page, the time and a one-way hash of the IP address. The hash lets us group repeated attempts from one address, but we cannot turn it back into the address. We delete these lines after 30 days.
Signing in
Signing in is optional. When you sign in on pixafind.com, or from the app's Settings, we store your email, your sign-in sessions with the IP address and browser or app that started each one, and the PCs you activated. You see the same list on your account page and can sign any of them out there.
The app talks to our account server only after you click Sign in, plus one licence check at start-up while you stay signed in. It sends a one-way hash of your computer's ID and your operating system, the same as activation. Signing in from the app sends a random one-time id and a local port number to pay.pixafind.com.
Website
This website uses Google Analytics and PostHog to count visits. In the EU, EEA, UK and Switzerland, analytics cookies are set only after you accept the cookie banner. If you decline, or never answer it, nothing is stored in your browser, and PostHog counts the visit without cookies. Elsewhere the site sets analytics cookies when you visit. We guess your region from your browser's time zone, which never leaves your browser. If your browser sends Global Privacy Control, we ask first, the same as in the EU.
The site also records sessions through PostHog, on servers in the United States. A session recording shows how you move through pixafind.com: pages, scrolls, clicks and mouse movements. Everything you type into a form is hidden before it leaves your browser, and a recording never includes anything outside pixafind.com. PostHog also collects click and scroll heatmaps, the text of buttons and links you click, clicks that do nothing, page load speed, and page errors. Sometimes the site shows a short optional survey, and if you answer it, your answers go to PostHog too. We keep recordings for 30 days.
Outside the EU, EEA, UK and Switzerland this is on by default. You can turn it off with the Stop recording button below, or by sending Global Privacy Control, which makes the site ask first with a banner. In the EU, EEA, UK and Switzerland it is on only after you choose Accept on the banner.
Download buttons go through pay.pixafind.com, which counts the download and which operating system it is for, then sends you to the file on GitHub. We do not keep your IP address. When analytics cookies are on for you, the count also carries your anonymous site id, so we can tell how many site visitors went on to download. Buy and subscribe links work the same way: when analytics cookies are on for you, the link to checkout or sign-in carries that anonymous site id and the id of your current site visit, so we can tell which site visits led to a purchase and watch the recording of that visit, if one was made.
If you accept, or you are outside those countries and did not decline, the site also counts a few named clicks: download buttons, buy and subscribe links, and the Get PixaFind buttons, plus when the pricing section comes into view. Each named count holds only fixed labels, such as which plan or which button. If you decline, none of these are sent, and neither are the recordings and heatmaps above.
When you uninstall the app on Windows, it opens a short goodbye page. If you answer it, we receive the reason you picked, any words you type in the box, and the app version. Nothing is sent unless you press Send.
About a minute after you click a download button, the site may ask once whether PixaFind installed. It asks only if analytics are allowed under the rules above. If you answer, we receive the answer you picked, any words you type in the box, your computer's operating system and which download you clicked. Your browser remembers that it asked, so it does not ask again.
Newsletter
The release newsletter is optional. If you sign up, your browser sends your email address straight to Buttondown, the service that sends the emails, along with which signup form you used. Like any website you send a form to, Buttondown also receives your IP address and your browser's user agent. Buttondown first emails you a confirmation link, and nothing else is sent until you click it.
We keep open tracking and click tracking off, so we cannot see whether you open an email or which links you click. Every email has a one-click unsubscribe link. If analytics is on for you (see Website above), the site counts that a signup form was submitted and which one, never the address.
Journey counts
We want to know how many people get from the download button to a working app. We use counts for this, not a profile of you.
When you click a download button, our payments server sends one download count to PostHog. It holds:
- The operating system of the file
- Which button you clicked, such as the top of the page or the pricing section
- Which kind of page you were on, from a fixed list such as home, blog or compare. Never the full address
- The utm_source, utm_medium and utm_campaign tags, if the address of the page where you clicked has them
- Your country code, such as DE
- Whether the request looked like a bot
The download count never holds your email or your IP address.
If you accepted the cookie banner, or you are outside the EU, EEA, UK and Switzerland and did not decline, the download link also carries the random ID that PostHog gave your browser. This lets us link the download to your earlier visits to this website. If you declined, or never answered the banner where we ask, the link carries no ID. The ID is added only at the moment you click, and it is removed from the link right after.
Inside the app, before setup ends, the app sends the counts listed above under Usage counts: that it opened for the first time, on Windows the seconds since the installer finished, which setup screen you reached, and the first model download. Each gets a new random ID. None of them carries the website ID or anything from the download link, so we cannot link your download to your app.
We do not put a personal token in the installer file.
These counts are kept in PostHog only. On our current PostHog plan, events are kept for up to 7 years.
To stop them: decline the cookie banner where we show it, or turn on Global Privacy Control in your browser, which works everywhere. Then the download carries no ID. In the app, turn off usage counts in Settings, under Data & Privacy, or on the first setup screen.
Your choices
- Ask us to delete your purchase and activation records, or to see what we hold about you, through the contact page
- Uninstall the app at any time
- Turn off usage counts, crash reports and screen recordings in Settings, under Data & Privacy
Contact
Questions about this policy? Use our contact page or open an issue on GitHub.