We count the traffic, not you
Nothing on this site is behind a login, and nothing you type into a tool leaves your device. We count page views in aggregate; the newsletter and Google sign-in are optional, and you can undo both.
The short version
- Analytics: Google Analytics and Cloudflare Web Analytics, in aggregate only. No ads, no profile.
- Newsletter: your email address and nothing else. Double opt-in, one-click unsubscribe.
- Signing in: optional. It syncs your saved card list between your devices, and that is all it does.
- The tools: your spend, cards and balances are worked out in your browser and never uploaded.
What we collect: aggregate traffic, and nothing else about you
No name, no phone number, no PAN, no income, and nothing is behind a login. Every page, ranking and calculator on this site is readable by a complete stranger, and nothing sends what you type to a server unless you press a button. Three buttons can: the error report sends only what you type into it; the newsletter box sends one thing, your email address, because that is the product; and Google sign-in, which exists only to sync your saved card list, sends your Google address and that list. The first two limit themselves with a one-way hash of your IP address for a day; the address itself is never stored.
We do measure traffic, and we'd rather be straight about it. Two tools do that, and this is the whole list:
- Google Analytics (GA4). Used only in aggregate: how many people land on which page, roughly from
where, on what kind of device. It sets a couple of cookies (the
_gafamily) to tell a returning visit from a new one, and Google, as the processor, receives your page views and an approximate location derived from your IP address. This is the one place the site is not cookie-free. We use it to decide what's worth writing next, never to build a profile of you, and never for advertising. - Cloudflare Web Analytics. A cookieless beacon for page-view counts and load times, added automatically by Cloudflare. It sets no cookies, stores nothing in your browser, does not fingerprint you and does not follow you across sites.
Neither one sees anything you put into the tools. Your spend, the cards you hold and your points balances are worked
out on your device (see below), and where a tool puts them into the page address, we strip that
#fragment before analytics reads the address. Beyond those two beacons, the site's own JavaScript makes
four kinds of network request: fetching the search index from this same domain when you open search; asking our own
server on this same domain whether you are signed in, on the handful of pages that offer
card sync; and, only if you submit them, sending an error report or a newsletter signup. The
one third-party script on the site is Google's sign-in library, and it loads only on those same sync
pages. There is no advertising and no affiliate link anywhere on the site, ever.
The rest of the policy
The newsletter: one address, one list, one click out
If you sign up for the weekly digest, we store your email address and nothing else: no name, no card list, no reading history, and never anything you typed into the calculator or the points portfolio. It lives in our own database on Cloudflare (the same service that runs this site), alongside the date you signed up, which sign-up you used (the footer box, the box on a card or comparison page, or signing in), whether you asked for instant devaluation alerts, and the confirmation status below. We run no customer-data platform, and there is no profile attached to the address.
Double opt-in, always. Entering an address only creates an unconfirmed entry and sends exactly one email asking you to confirm it. Nothing else is ever sent until you click that link, which is what stops anyone typing a stranger's address into the box and signing them up. Don't confirm, and the address never hears from us again.
One-click unsubscribe, in every email. No login, no "are you sure", no survey. When you leave we keep the address on a do-not-send list rather than deleting it, so a later signup form or an imported file can't quietly put you back; that record exists to keep mail away from you, not to send it. Want it erased outright? Ask us and it goes.
We never sell, share, rent or pass on the list: not to banks, not to advertisers, not to anyone.
The only third party that ever touches your address is the email provider that delivers the mail for us. The emails
carry no tracking pixel and nothing per reader: links back to the site carry one campaign tag per issue (for
example utm_campaign=digest-2026-11-02), the same for every reader, so our analytics can count visits
from the email without knowing who sent them. We do not measure who opened what.
Signing in: optional, and it buys one thing, sync
A few pages (my wallet, the lounge map and the transfer partners page) remember which cards you hold so they can answer for your wallet instead of every card. That list normally lives in this browser and is lost when you clear it. Signing in with Google is how you make it follow you to a second device, and that is the only thing it does. Nothing on this site is behind it: skip it and every page works exactly the same.
What we store, in full: your Google account's email address, the name on that account (as Google
states it, trimmed; it greets you on your account page and appears nowhere else), the identifier Google gives us for
that account, and your list of card names in short form (strings like axis-atlas) with the time it last
changed. If you opt into instant alerts, one more record per alert we actually email you (your address and which
event it was; that is how "at most one a day" is enforced). That is the entire record. No profile photo, no reading
history, no spend, no balances, and nothing typed into any calculator. We ask Google for the email and
profile permissions and nothing more: no access to your Gmail, Drive, contacts or anything else, and we
never post anywhere for you.
If you send us a data point. Two forms collect facts we cannot work out ourselves: when a transfer landed, and what a bank offered to keep you. Sending one needs an account, because every count we publish prints its number of contributors beside its number of reports, and that needs distinguishable people. What is stored is the report itself (a route or a card, the dates, the numbers, a fixed category) and, instead of your account, a one-way hash of it. That hash is why a published count can say "4 contributors" without the table holding anything that points back at you. The one free-text box on each form is read by us and nobody else: it is never returned or shown anywhere. Delete your account and your reports go with it, which also takes them out of the published counts.
Two cookies, both ours, and neither is a tracker. Signing in sets __Host-tw_session,
an HttpOnly, Secure, SameSite=Lax cookie that carries only your account identifier, a session id and an expiry,
signed so it cannot be forged, and valid for at most 30 days. It is never read by analytics, carries nothing about
what you browse, and is sent only to this domain. Signing out cancels the session on our server, not just
in your browser, so a copied cookie stops working. During sign-in, which has to leave the page and come back, we
also set tw_return for ten minutes: it holds the address of the page you came from, so your account
page can offer the way back. That is its entire contents, and it expires the moment you return.
Where Google's script loads. There is a "Sign in" control in the header of every page; that is how you find this feature at all. It does nothing until you click it: Google's sign-in library is fetched when you open it, never on page load. The exception is the handful of pages listed above, where your saved cards are what the page is for and Google's One Tap may appear when you arrive. On an article, a news post or a card page, nothing of Google's runs unless you ask for it. Once it does run it may set cookies on google.com under Google's terms; that part is between you and Google.
Leaving. Sign out and the browser stops syncing; your cards stay on the device, because losing your list for clicking "sign out" would be an absurd punishment, and signing out also cancels the session on our server. Deleting the account outright is self-serve, in the account section of my wallet: it asks you to type a phrase and to confirm with Google once more (an action you can't undo deserves a fresh proof it is you), then one step removes everything: cards, profile, session records (deleted, not just marked inactive, which would keep the identifier), the newsletter entry, the alert record and any data points you sent. If you were subscribed we keep a one-way hash of the address so nothing can ever quietly re-add it to a mailing list; it cannot be turned back into who you were. Signing in again afterwards starts a fresh, empty account. Signing in with a verified Google address also subscribes you to the Monday email (one tap at the foot of any issue ends it). It never switches on instant alerts, and it never re-subscribes an address that has unsubscribed.
The tools: your numbers stay on your device
The calculator, my wallet (its score and points balances included) and the lounge map's "my cards" mode all run entirely in your browser. Your spend, the cards you hold and your points balances are worked out in the open tab and, where a tool remembers anything at all, saved to this browser's local storage on this device: never uploaded, never logged, never seen by us. The one exception is the card list itself, and only if you choose to sign in to sync it; your spend and your balances never leave, signed in or not.
The wallet score and points portfolio offer share links. Those work by putting your inputs into the link itself; your data travels only if you copy that link and give it to someone. Clearing your browser data erases everything these tools know.
Disclaimer: not financial advice
Everything on this site (every ranking, verdict, points value and rupee figure) is editorial opinion built on published card terms, not financial, legal or tax advice, and not a recommendation to apply for, keep or cancel any product. Our maths assumes a standard spending pattern; yours is different, and a card that is a Keep for the model can be a Cancel for you.
Check with the bank before acting. Fees, earn rates, transfer ratios and lounge access change without notice, which is why the devaluation tracker exists. The bank's current fee document (MITC) and terms are the only documents that bind it; if this site and the bank's paperwork ever disagree, the paperwork wins, and we want to hear about it.
We hold no position in any bank, take no affiliate commissions and carry no advertising; see about us for the full stance.
Quoting us: credit us, link us
You are welcome to quote this site's numbers, verdicts and charts, with credit to travelwith.cc and a link to the page you're citing. Our facts are built on banks' published documents and community sources, each cited where used; the data and code behind the site are version-controlled, and every correction is dated. Please don't republish wholesale or strip the sources: the sources are the product. The full terms are on the terms and data licence page.