About
The desk.
travelwith.cc is the brutally honest valuations desk for Indian travel credit cards. We rank 58 cards, value 70 points currencies in rupees, and log every devaluation — and the only thing we sell is the verdict.
01 · What this is
Pure editorial, on purpose
An independent desk for Indian points-and-miles geeks, focused purely on travel — miles, transfer partners, lounges, premium cards. Not cashback, not "10 best cards" listicles, not a lead-generation funnel wearing a blog's clothes.
Zero affiliate links. No display ads. No sponsored placements. Nobody pays for a rank, a verdict, or a kind word — that is a locked, written decision, and the methodology page spells out what happens if it ever changes (disclosure first, rankings untouched). When we say a card is a Cancel, no commercial relationship is whispering otherwise, because there isn't one.
We describe practices here, not personalities. There is no team page, no founder origin story, no stock photo of people pointing at a laptop. The site's credibility is designed to rest on things you can check — sourced data, published methodology, a public edit history — not on who is behind the keyboard.
02 · How it works
Curated data, computed pages
Everything the site shows is generated from a single set of hand-curated, version-controlled data files — card terms, currency valuations, transfer routes, lounge access, 249 dated tracker events. Every page, every rank, every ₹ figure is computed from that data at build time. To change what the site says, you have to change the data — and every change is a reviewable diff.
Every card cites its paperwork. All 58 of 58 card pages carry a Sources section — 145 official issuer documents (T&C, MITC, program pages) plus community corroboration, each with the date we last checked it. A fact we can't verify doesn't get invented; the page renders "not published" instead.
The data is guarded twice. A build-time audit is a hard gate — no build ships if a transfer ratio fails to parse, a valuation escapes its own floor–ceiling range, or a cross-reference dangles. And a daily data-quality watchdog re-audits what production is actually serving every morning and files a public report when anything drifts.
The whole operation — data, code, audit scripts, edit history — lives in version control: every number on this site traces to a dated commit that records what it said before. The repository itself is private; the record it keeps is what powers the corrections policy below.
How the numbers themselves are made — the ₹1-per-mile anchor, the ranking engine, the verdict scale — is disclosed in full on the methodology page.
03 · Corrections
Loudly, never silently
A wrong fee or an inverted transfer ratio is worse than no site at all, so the policy is simple: when we get something wrong, we fix it in the open. Every correction lands as a public commit that states what was wrong, and material errors are re-verified against the issuer's own documents before the fix ships. We do not quietly edit a number and hope nobody kept a screenshot. Two real examples from our own record:
- The Atlas closure date. Axis closing the Atlas to new applicants first surfaced as a rumour with a "1 September" cutoff — and our story initially carried that future date as if it were the event. QA caught it, the post was re-dated to when the closure was actually confirmed (early 2026), and the fix landed as commit d78647b — whose message says, verbatim, "correct fabricated future date". The git record keeps us honest even when it's embarrassing.
- The July 2026 re-verification. We re-checked every card against issuer PDFs and found ~35 factual errors in our own data — including ones where we'd been too harsh: an Amex reward rate understated by half, a "no fee waiver" claim that was false, a transfer route we said didn't exist that does. All fixed, all itemised — by card, by number — in the desk's own roadmap and research notes.
When the world changes rather than our data being wrong — an issuer nerfs a card, a program devalues — that isn't a correction, it's an event: it gets a dated, sourced entry in the tracker and the affected pages update the same day.
Spotted something wrong?
Tell us — you will be doing every reader after you a favour. The channel is the report form: four fields — the page, what's wrong, the correct fact, and (ideally) a source. It goes straight to the desk's daily sweep; no account, no email (this domain deliberately sends and receives none). If the issuer's own document backs you, the fix usually ships the same day.