What we collect, and what we don't

If you subscribe, we collect the email address you enter. If you write to us through a form, we get your message and whatever contact detail you include. There are no accounts here — no logins, no passwords, no profiles to build — and nothing to upload. Our host also logs the ordinary technical data every website sees, like your IP address and browser type, which helps keep the site up and blocks spam. That's the whole picture.

Your email address is used to send the weekly issue you signed up for. A message you send is used to reply to you. Technical logs are used to run and protect the site. We don't build advertising profiles on you, and we don't use any AI or automated system to make decisions about you.

To operate the site and its list, we share only what each service needs:

• MailerLite — stores our subscriber list and sends the newsletter.
• FormSubmit — relays messages and signups from our forms to our inbox.
• GitHub Pages — hosts this website.

Separately, this site earns through affiliate and referral links. When you click one, you leave our site for a partner — a card-affiliate network such as CardRatings, or a bank's own refer-a-friend program such as Chase or American Express. From that point you're on their site under their privacy policy, and they may pay us a commission if you're approved, at no extra cost to you. We only ever pass along a click, never your email or personal details.

Our own site keeps cookies minimal — what it needs to function, plus at most simple analytics to see which articles get read. We do not run advertising or third-party ad-tracking cookies. The one thing worth flagging: when you click an affiliate or referral link, that partner network (CardRatings, Chase, American Express, and the like) sets its own cookie so it can credit the referral to us. That cookie is set by them, on their terms, only when you choose to click. You can clear or block cookies in your browser whenever you like.

When you arrive from one of our posts, the link may carry a short code naming that post. We keep that code in your browser's local storage for up to 30 days so we can see which posts are useful. When you click an outbound link (like a card or checkout link), your browser sends us a small event noting which link and which post code. It doesn't include your name or email, and we don't use it to identify you. Our server briefly uses your IP address (for under an hour) only to block abuse, and doesn't store it with the event. If you buy a template, that post code is passed to Stripe with your order so we can tell which content led to the purchase. Clearing your browser's site data removes it.

We also use Cloudflare Web Analytics to count page views. It doesn't set cookies or track you across other sites.

If you buy a template, Stripe (our merchant of record) handles the payment and shares your email address and order details with us so we can deliver your download. We keep your email with your download link for 72 hours, then it's deleted automatically. Your order record also stays in our Stripe account for tax and accounting. Stripe's own privacy policy covers the payment itself.

• Every newsletter has a one-click unsubscribe link at the bottom — use it whenever you want out, no questions asked.
• To see what we hold or have it deleted, reach us using the contact below and we'll handle it.

The site is served over HTTPS. Because we hold no accounts and take no payments here, there are no passwords or card numbers on our side to lose. We keep the email list lean and don't hang on to data we don't use.

The simplest way to reach us about your data is to reply directly to any email we send you — those come to an inbox we actually read. Prefer to opt out first? Use the unsubscribe link in any issue. For an access or deletion request, reply to a newsletter email and just ask; we'll take it from there. You can also email help@travelfinancetips.com or use our contact form.