Privacy Policy

1. How your files are handled

When you add a file and press compress, all of this happens on your own machine:

• Your browser reads the file from your disk. It is not sent anywhere.
• The compression runs in the page itself — WebAssembly code your browser downloaded along with the rest of the tool, in the same way it downloaded the buttons.
• The result is written straight back to your downloads folder.

There is no upload step in the product. Not a hidden one, not a temporary one — the file never becomes a network request.

The client name you type for automatic file naming is in the same position: it is used in your browser to build the download's name and is never sent to us.

When you close the tab, the files leave the page's memory with it. Nothing is queued, cached or kept for later.

2. What we do collect

You need an account to use the tool, and an account means we store some things about you. There are three, and this is all of them.

Your account

• Your email address, and the name you give when you sign up.
• Your daily limit, your role, and whether the account is active.

Used to sign you in and to know whose daily limit is whose.

Usage records — one row per compressed file

• Whether it was a PDF or an image.
• Which slot it was compressed for — flight ticket, hotel booking, bank statement, photo, and so on.
• Its size before, its size after, and the size limit you set.
• The date and time, and which account it belongs to.

Used to count your files against your daily limit, and to give whoever reviews a limit-increase request something to review. That row does not contain the file, any part of the file, or its name.

Limit-increase requests

• Your current limit, the limit you asked for, and the reason you typed if you typed one.
• The decision, and any note the reviewer wrote.

The same thing as one list

• File contents: never collected.
• File names: never collected.
• Client names you type: never collected — they are used in your browser and stay there.
• Email address: collected.
• Your name: collected.
• Per-file usage records — type, slot, sizes, timestamp: collected.
• Limit-increase requests you send: collected.
• Payment details: none. The service is free and there is nothing to bill.

3. Cookies, and where your login lives

TravelPdfPro does not set any cookies today.

Staying signed in needs something stored in your browser, and for us that is local storage, not a cookie: the authentication library keeps your session token there so you are not asked to log in again on every page. Logging out removes it, and so does clearing your browser's data for this site.

If that ever changes — and the advertising section below is the way it would — this page changes with it.

4. Services we use

• Supabase — our authentication and database provider. Your account, your usage records and your limit-increase requests are stored in a Supabase project in the Singapore region. Their privacy policy is at supabase.com/privacy.
• Google Fonts — used by the app at /app, not by these pages. The marketing pages, this one included, serve their fonts from our own server and make no third-party request at all. The app's page still loads two typefaces from Google's font service, and loading them tells Google the IP address and browser of whoever opened it. We intend to serve those from our own server too.

That is the whole list. No other company receives anything from this product today.

5. Advertising and analytics — none today, likely later

There is currently no advertising, no analytics and no tracking pixel anywhere on this site or in the app. Nothing counts your visits and nothing follows you between pages.

We expect that to change. The tool is free, and advertising is how we intend to keep it free. When it happens it is likely to be Google AdSense for the advertising, and an analytics or measurement service — Google Analytics or the Meta pixel, for example — for the numbers. Those services set their own cookies and receive their own data, typically your IP address, which pages you looked at, and an identifier that lets them recognise a returning browser.

Two commitments about that, made now rather than later:

• This page is updated before any of it goes live — naming the services and what they take, not a vague line about "third parties we may work with".
• None of it touches section 1. Advertising sits beside the tool and cannot see what the tool is doing: your documents are not uploaded regardless of what else is on the page, because there is no upload to intercept.

6. Your data, and getting rid of it

Email info@travelpdfpro.com and we will:

• Tell you what we hold — your account details, your usage records and any limit-increase requests.
• Correct anything that is wrong.
• Delete your account. That removes your account record and, with it, every usage record and every limit-increase request attached to it. They are removed together by the database itself, so nothing is left behind under your name.

There is no self-service delete button in the app yet, so this is done by hand — write to us and we will confirm when it is done.

What we cannot delete is what we never had. Your documents were never on our side, so there is nothing of them to remove.

7. Changes to this policy

When this policy changes, the date at the top changes with it. If the change is a real one — a new service receiving data, advertising going live — the section that covers it will say what changed, not just carry a newer date.

8. Questions

Anything on this page, or anything it does not answer: info@travelpdfpro.com. More ways to reach us, and what to expect, are on the contact page.