Privacy Policy

Browser tools. Most tools process the file inside your browser tab using WebAssembly. The file is read from your device by the page itself, the result is produced on your device, and nothing is sent to our servers. We cannot see, store or recover these files, because they never reach us.

Server tools. A small number of tools need software that does not run in a browser: conversion between PDF and Word, Excel, PowerPoint, ePub, ODT, RTF or Pages documents, text recognition in scanned PDFs, PDF/A conversion, PDF repair, table extraction from PDF to CSV, HTML rendering to PDF or to an image, PSD, RAW and TIFF images, and conversion between ePub and MOBI. Background removal also uses our server, on any device, because its model is too heavy for a browser tab: the page uploads only a reduced 1024 × 1024 copy of the photo and gets back the outline of the subject; the original file stays on your device. The page of each such tool says that it uses our server. For these tools:

• The file is uploaded over an encrypted connection (HTTPS) to our processing server, a single machine we rent from Hetzner in Helsinki, Finland, inside the European Union, using a one-time upload link that expires after 15 minutes. The upload goes straight to that server and does not pass through Cloudflare.
• The file is processed by automated software only. No person opens or reviews it.
• The uploaded file is deleted automatically as soon as the job finishes, and the produced result within about two hours. A scheduled cleanup removes anything that was missed.
• The file is used for nothing else: not for training, not for analytics, not for anything beyond producing your result.
• To protect the service from abuse, the server keeps a short-lived count of jobs per IP address and rejects requests above an hourly limit. This count is not stored beyond the hour.

Tools that fetch data for you. The currency converter asks our server for exchange rates, which our server obtains from public sources and caches; your browser never contacts those sources directly. The redirect tracer asks our server to follow the chain of redirects for the URL you enter; that URL is sent to our server for the request and is not stored afterwards.

To understand which tools are used and whether they fail, the site records usage events on our own infrastructure, in one of two modes. Full statistics: in the European Economic Area, the United Kingdom and Switzerland after you choose "Accept" in the cookie banner, and everywhere else by default until you choose "Necessary only". Anonymous count: in those three regions until you answer the banner, and everywhere after "Necessary only".

The anonymous count records each event on its own: a page view (the page address, the type of page, the interface language, the domain you came from and the UTM campaign tags in the address), the result of a tool (success or failure with its error code), a tool that refused to start and why, a JavaScript error, how fast the page loaded, and your choice in the cookie banner; plus the country of the request, the device class (phone, tablet or computer), the operating system and the browser. It uses no cookies and nothing in your browser's storage, carries no identifier, no time from your device and no window width, and its events cannot be linked to one another.

Full statistics adds: a random tab identifier and an event number kept in the browser's session storage, the _aid cookie with a random device identifier, so that visits and returning visits can be counted, time spent on the page and how far it was scrolled, the window width, the steps of a tool (the type of file, its size range such as "1 to 10 MB", where the file came from, the start of processing and the download), the text typed into the site search (cleaned of anything that looks like an e-mail address, a number or a file name, and cut to 64 characters), the text of JavaScript errors (cleaned the same way), moves from one tool to the next, a change of interface language, installing the site as an app, and a mark that the visit comes from our own team.

Never collected: your IP address, neither raw nor as a hash; your region or city; the name or contents of a file; its exact size; the text you type into tool fields; passwords. The server looks at the IP address only in memory while answering a request, to recognise our own team's network, and writes it nowhere.

Your answer in the cookie banner is recorded as an anonymous event together with the address of the page where you gave it.

How long the data is kept:

• Raw events: 90 days.
• Sessions and the link between the sessions of one visitor, including the device identifier: 180 days.
• Summaries without any identifiers, such as counts per hour or per day: 25 months.
• The intake journal on our server, which holds events until they are processed: up to 72 hours.
• The web server's log of page requests, without IP addresses (browser and referring page): 2 days.
• Rejected records, without identifiers: 30 days.
• The web server's error log, which can contain an IP address: up to 15 days.

Cookies and browser storage used for this: fk_consent and fk_geo (your banner choice and whether the banner is needed where you are), _aid (only with full statistics, 400 days), pk_internal (only for our own team: one year after signing in to the site's admin panel, 30 days after opening a special link), and pk:tab and pk:seq in session storage (only with full statistics; they live while the tab is open). The cookie policy lists every item.

The embeddable widget version of our tools sends no usage events at all.

The site can also load Microsoft Clarity. In the European Economic Area, the United Kingdom and Switzerland it loads only after you accept analytics in the banner; elsewhere it loads by default until you switch it off. Clarity records how pages are used: clicks, scrolling, mouse movement, page navigation and the browser and device type, and it can replay a session as an anonymised recording. Text you type into tool forms is not part of what we need from Clarity, and files you process never pass through it, because Clarity only observes the page, not the file.

Clarity sets its own cookies (_clck, _clsk, CLID, ANONCHK, MR, MUID, SM) and processes the data under Microsoft's privacy statement. Choosing "Necessary only" switches Clarity off wherever you are, and the embeddable widget version of our tools never loads it at all.

PulsarKit is funded by advertising. At the moment no advertising network is loaded on any page and no advertising cookies are set. When an advertising provider is added, this policy will name it and link to its own policy. In the European Economic Area, the United Kingdom and Switzerland nothing will be personalised and no advertising cookie will be set until you accept in the banner; a refusal there means plain, non-personalised advertising. Elsewhere advertising will be personalised by default, and "Cookie settings" in the footer turns that off.

Several features keep data on your own device, using cookies, local storage or the browser's IndexedDB. None of it is sent to us, except the cookies our own analytics reads, described in section 2. The cookie policy lists every item; the main ones are:

• fk_consent: your cookie banner choice, kept for 180 days.
• Your theme (light or dark) and interface preferences.
• Drafts of forms in tools such as the invoice, resume, business card and Markdown editor, kept for up to 30 days so that a reload does not lose your work.
• Saved tool chains and the file hand-off between tools, which lets you send a result straight into the next tool.
• Downloaded processing engines and models (for example OCR language data), cached so that the next run does not download them again.

You can delete all of this at any time through your browser's site data settings.

The site is delivered through Cloudflare, a content delivery network that sits in front of our server, and the server itself is rented from Hetzner in Helsinki, Finland. Cloudflare processes the technical details of each request (including the IP address) to serve the pages and to protect against abuse, under its own privacy terms, and tells us the country of the request, which is the country used in our analytics; Hetzner provides the machine and the network it runs on, under its own terms.

Some browser tools download large processing models on first use directly from public package and model registries, such as jsDelivr for the OCR engine. Those services see the download request, including your IP address, exactly as they would when any website loads a public file. The file you are processing is never part of that request.

The site does not embed social media buttons, external fonts or third-party scripts other than the ones described above.

We have no user accounts, so there are no passwords, e-mail addresses or profiles to keep. We do not sell or share usage data with anyone. We do not send newsletters. We do not use your files for anything other than producing the result you asked for.

Under the General Data Protection Regulation and similar laws you have the right to access, correct or erase personal data about you, to object to or restrict its processing, and to complain to your data protection authority. The site keeps no name, e-mail address or IP address of yours: full statistics is tied only to the random device identifier in the _aid cookie, which we cannot connect to you without your help, and the anonymous count is tied to nothing at all. Files are gone within about two hours, and raw events after 90 days.

Consent for analytics can be withdrawn at any time: "Cookie settings" in the footer reopens the banner on every page. Withdrawing consent stops Clarity immediately, deletes the cookies it set, removes the _aid identifier and the tab identifiers, and switches our own statistics to the anonymous count.

If you believe we hold data about you, or you have any other question about privacy, write to support@pulsarkit.com.

The site is a general-purpose utility and is not directed at children under 16. We do not knowingly collect personal data from children; since we collect no names, contact details or IP addresses, there is normally nothing we could find, but you are welcome to contact us with any concern.

When something about the way the site handles data changes, for example if an advertising provider is added, this page is updated and the date at the top changes. Substantial changes are also noted on the About page.