Download for Windows

Privacy

Last updated 21 September 2026

ChatExport exists because message histories are some of the most sensitive data a person owns. The short version of this policy: we do not have your messages, and we cannot get them.

Who is responsible

The data controller for this website is Bokart Krzysztof Kowalski, Konstancińska 3A lok. 62, 02-942 Warszawa, Poland, tax ID (NIP) 5213411818. Anything on this page can be raised at support@getchatexport.com, where a person answers rather than a ticket queue.

That responsibility covers three things and no more: the visit counts described below, the emails you send us, and an address typed into the sample request form. What the app does on your computer is not one of them, because none of it reaches us. In practice the only thing we could be holding about you is an email you wrote, or an address you asked us to keep, and you can ask what it says, have it corrected, or have it deleted.

If you think any of that is handled badly, the supervisory authority for a controller established in Poland is the President of the Personal Data Protection Office (UODO, uodo.gov.pl), and you can complain to the authority in your own country as well.

The app

ChatExport runs entirely on your computer. It reads the iPhone backup that Apple's own software wrote to your disk, and writes the export file where you tell it to. That is the whole data flow.

  • Your messages, photos and attachments are never uploaded anywhere.
  • There is no account, no login and no licence server contacting us as you work.
  • There is no telemetry, usage tracking or crash reporting turned on by default.
  • The app writes local log files describing what it did: which backup it opened, how many messages it read, what failed. Those files stay on your machine, and you decide whether to attach one to a support email.
  • You can verify all of this: disconnect from the internet and export a conversation. Nothing about the process changes.

Where that leaves us legally

Because the processing happens entirely on your own computer, no personal data from the app ever reaches us. There is nothing we could process on your behalf, and nothing to hand to a third party. The messages inside an export stay yours to answer for, exactly like any other file on your PC. A law firm or a business running ChatExport at work treats it the way it treats any other program installed locally.

This website

getchatexport.com is a set of static files. There is no code of ours running behind its pages. The two small functions that send licence keys and the sample documents run elsewhere, on Vercel, and the one database we keep holds visit counts and nothing else; each is described below.

  • Browsing this site sets no cookies, so there is nothing to ask you about. This site used to open with a cookie banner. It does not any more, because the tools behind it were replaced with ones that store nothing on your device. A banner asking permission to do nothing would be theatre.
  • The payment window is the exception, and only if you open it. Paddle's checkout is fetched when you click Buy and never before, so a visit that buys nothing never contacts it at all. Once it is open it stores on your device what a payment needs in order to work. That is the checkout doing its job rather than us measuring you.
  • One tool remembers what you type, in your browser and nowhere else. The exhibit list generator under /tools keeps the list you are filling in, so that a refresh does not lose an hour of typing. Nothing is written until you type something; what is written stays on your device, never reaches us and is not synced anywhere; and the button on the page deletes it. With the checkout, that makes two things reached from this site that write anything to your device, and there is no third.
  • Visits are counted by Umami and by Ahrefs. Two of them for now, while we work out which one to keep. Each is sent the page you are on, the site that linked you here if any, your rough country, and whether you are on a phone or a desktop. Your IP address reaches their servers, as it does with any request on the internet, and is used there to work out that country and then discarded.
  • There were three until 30 August 2026. Plausible counted visits here the same way the other two do. Its trial ended, so it was removed, and with it the request every page on this site was making to it.
  • Since 31 August 2026 we also count for ourselves. Every page sends one short message to /api/hit, which is an address on this domain, and it is written to a database on the same account that hosts these files. It reaches no third party at all. We built it because a counter belonging to somebody else sits on every content blocker's list and can be switched off without telling us, and honest numbers are worth more to us than large ones.
  • What our own counter keeps, field by field. The page and its language, the host of the site that linked you here, a tag if the link we posted carried one, your country as our network reports it, whether you are on a phone or a desktop, and which family your operating system and browser belong to. Your IP address is used to work out that country and to build the day's fingerprint, and is stored nowhere. The address of the page you came from is shortened to its host inside your browser, so the rest of it never reaches us. The browser identification string becomes those two words and is then thrown away. The fingerprint uses a random secret that we generate each morning and delete two days later, so nothing here recognises you tomorrow either.
  • Nothing identifies you tomorrow. Neither of them writes an identifier to your browser. To avoid counting one person twice in a day they derive a fingerprint on their own servers from your address and browser, mixed with a secret that is thrown away and replaced every 24 hours. After that the same visitor is a new visitor, and the same person on another website was never connectable in the first place.
  • We count seven things on purpose, in Umami and in our own database. Which of the sample export files gets opened, whether someone uses a contact link, whether the download button is clicked, whether one of the free tools under /tools is actually used rather than only read, and then the three steps of buying: the click on Buy, the payment window actually opening, and a payment going through. The download also records the name of the installer file, the language of the page it was clicked from and which of the buttons it was, so we can see which version people take and which page persuaded them. The tool records only which of the three it was, never what you typed into it, the path or the result, and never a word of an exhibit list, all of which stay in your browser; it is the one of the seven that goes to Umami alone. The three about buying record the language of the page and whether it was the pricing page or the buy page, and nothing else. No amount, no currency and no transaction number, so none of them can be joined to what you actually paid: what happened to your money is Paddle's record and stays there. All seven are numbers against a page, with nothing attached that could point back at a person.
  • The app is not measured at all. All of this stops at this website. Nothing you do inside ChatExport is counted, timed, recorded or reported, and the app makes no network requests of its own.
  • There is no session recording, no heatmap and no replay of your visit. There was one until July 2026 (Microsoft Clarity); it has been removed.
  • No advertising scripts are loaded and we do not run remarketing.
  • Any content blocker stops both of those scripts, and nothing on the site depends on them. Our own counter is not a third-party script, so a blocker usually leaves it alone; blocking the address above stops that one too, and the pages work identically either way.
  • Fonts and every other asset are served from this domain, so apart from those two counting requests no third party learns that you were here.
  • The company hosting these files keeps ordinary server logs, which include IP addresses, for a short period. That is standard for any website and we do not build profiles from it.

Buying

The seller is Paddle, acting as merchant of record (Paddle.com Inc. for US buyers, Paddle.com (Canada) Ltd. in Canada, Paddle.com Market Limited of London elsewhere), and Paddle is the data controller for the order and payment data: card details, billing address, invoicing. Their policy is at paddle.com/privacy. We never see your card number.

What reaches us from a purchase is the buyer's name, e-mail address, country and order details, used to generate and send the licence key and to handle refunds and complaints. The key itself carries the buyer's name and e-mail and shows them only inside the program, on your computer; the function that signs keys keeps no database and no register of keys. Licence data stays for the lifetime of the licence, settlement records for as long as tax law requires, and for European buyers the seller is the UK entity, which holds an EU adequacy decision.

The sample request form

The download and pricing pages carry one form, and it is the only thing on this site that asks you for anything: an e-mail address, so that the sample documents and a short checklist for court can be sent to it. What happens to the address, step by step:

  • It goes to a small function of ours hosted on Vercel, which sends you one e-mail asking you to confirm it. Nothing else is sent until you open the link in that e-mail, and a link not opened within two days stops working. That is what stops somebody else entering your address for you.
  • When you confirm, the same function sends the documents and the checklist, and that is the end of it. It keeps no database and no list, and the address is not written to its logs.
  • Both e-mails go out through Resend, the service that also delivers licence keys. Resend keeps its own sending log for a limited time, under its policy at resend.com/legal/privacy-policy.
  • Only if you tick the box asking to hear about new releases is the address kept, in a list at Resend, and used for a few e-mails a year at most, each with a way to leave the list. The box is unticked unless you tick it.
  • Whether you ticked it or not, you can ask what we hold and have it deleted by writing to support@getchatexport.com.

Email

If you write to support@getchatexport.com, we keep that message so we can answer it. Please do not send us screenshots of private conversations unless a support question genuinely requires it. If it does, send the smallest excerpt that shows the problem.

Changes

If this policy changes, the date at the top changes with it. If a future version of ChatExport ever adds something that sends data anywhere, an optional update check for example, it will be off unless you turn it on, and it will be described here first.

Contact

Questions about any of this: support@getchatexport.com.