Privacy Policy

Last updated: October 2026

Hexloom Labs ("we") builds digital software tools. This policy covers what happens to your data when you use a Hexloom Labs product.

What we don't collect

Our tools process your files entirely in your browser. Files you open or create in a Hexloom Labs tool are never sent to our servers. The exceptions are a paid service you order from us, described under Paid services below, and the Hexloom API, described under Hexloom API below.

What we do collect

Standard web server logs (IP address, browser type, page requested) via our hosting provider, kept only as long as needed for security and abuse prevention. If you subscribe to Hexloom Pro, payment is handled entirely by Stripe — we receive confirmation that you subscribed, plus the Stripe customer and subscription identifiers, and never see or store your card details. To recognise your subscription across our tools we set one first-party cookie (hx_pro) on hexloomlabs.com and its subdomains; it holds a signed token with those identifiers and expires after 30 days unless refreshed. Our tools check it by sending it to hexloomlabs.com when a page loads or when you reach a free limit, depending on the tool; no file data is ever part of that request. While a checkout tab is open, the tool page repeats the check every 3 seconds, for up to 30 minutes, so Pro unlocks when payment completes. We also count how many people use each tool, guide and service page. The page sends each count to hexloomlabs.com as one small request at the moment it happens (the tool, guide and service pages send none from browsers that report themselves as automated): when a page loads; when a job has finished and its result is offered for download (once per batch, not while you add files or while they are processed), when a calculator first shows its result, when a bought kit's download page opens, or when an order's files finish uploading; when Merge PDF or Doc Scrubber shows its free-limit message or its button is used; and when the Pro button or a service's pay button is used. Our server also counts a checkout when it is started. Each count carries the tool name, the event name, the page path and where you came from. Where you came from is the host name of the site that linked to the page, or, when the page address carries a ?ref= or utm_source= tag, that short tag instead; a job that processed files, an order's upload or a calculator result also sends a size class for how many files it held (1-2, 3-5, 6-10 or 11 or more; a calculator result counts as one), never names, contents or sizes. To tell visitors apart for a single day we keep only a one-way hash of your IP address, built with a random salt that is replaced every day (yesterday's salt and hashes are deleted the first time the counter runs on the next day); the IP address itself is never stored, no cookie is set (the count ignores any cookie your browser sends with the request), and no file data is part of the request. To stop abuse of the sign-up, restore and checkout forms we also count their requests per hashed IP address for ten minutes, then discard the count. If you ask to restore Pro in another browser, we look up the email address you enter in Stripe, send one restore link to it if an active subscription exists, and keep nothing from the request. The Hexloom Tools and Doc Scrubber browser extensions make the same Pro check when a tool opens or when you reach a free limit, depending on the tool, and that check is counted in the same way.

Email

If you contact us, we use your email only to reply to you. If you sign up for updates, we keep your email address and the list you chose, and send a confirmation email first; nothing is sent until you click it. We use it only to send the updates you signed up for (news about a tool or guide), at most once a week. The one exception is the Hexloom Pro note you can ask for on the Merge PDF page when you reach its free limit: you get that note when you confirm, one follow-up about 3 days later and a last one about 7 days after you confirm, and nothing more. We stop that series if you buy Hexloom Pro with the same email address. For that series we also keep the date you confirmed and which note you reached, and before each follow-up we ask Stripe whether that address holds Hexloom Pro. Every email has an unsubscribe link. Unsubscribing stops the mail from that list; to have the address deleted, write to us through the support page.

Paid services

When you buy a service, you send us your files, either through the upload form on the service page or by email, and we process them with an AI-assisted process. We receive the files and your email address through our mailbox provider, Cloudflare. Cloudflare Email Routing forwards each message to a mailbox we operate, and our own mailbox keeps a copy of the message, attachments included, for up to 90 days before it is deleted automatically. Files sent through the upload form go straight into private Cloudflare R2 storage, together with the email address you give and the notes you type (up to 1000 characters), and a storage lifecycle rule deletes each file automatically 14 days after upload. When an upload is complete, the upload form also sends a notice to our mailbox through our email provider, Resend, with your email address, your notes, the order reference, and the name and size of each file; that notice is a mail message, so the 14-day storage rule does not apply to it and it is kept like any other message to our mailbox, as described in this section. To stop abuse of the upload form we also keep, for each hour, a count of the files sent from your IP address, stored under a hash of it; it sits in the same private storage and the same 14-day rule deletes it. Files sent by email are handled as described above. We keep the files only to do the job. The copy stored by the mail system is deleted automatically after 90 days at most (messages over 512 KB are stored cut off). The forwarded copy and our working copies have no automatic expiry; we delete them when you ask, through the support page, and we aim to do so within 7 days of your request. We do not read them for any other purpose, sell them, or use them to train any model. This is different from the browser tools, which never send files to our servers.

Hexloom API

Hexloom API (hexloomlabs.com/api/v1): unlike the browser tools, the API receives the files you send. Each file is held in memory for the length of the request and is not stored or logged by us; Cloudflare, which hosts the API, keeps its usual request logs (time, path, status, size, IP and request headers; key and secret headers are masked). If you buy through RapidAPI, RapidAPI handles your account and payment under its own policy. The “never sent to our servers” statement applies to the in-browser tools.

Third parties

We use Stripe for payments, Resend for sending email, and Cloudflare for hosting and for its own page-load analytics, which run on our pages. Each has its own privacy policy governing the data they process on our behalf.

If you press play on a demo video (Merge PDF, Photo Scrubber and Doc Scrubber each have one), your browser loads the video from YouTube (youtube-nocookie.com, run by Google), which then receives your IP address and browser details. Nothing from YouTube loads before you press play.

Contact

Privacy contact: hello@hexloomlabs.com. You can also use the support page.