INDIA-FIRST CARD CONTINUITY
Replace a card without losing track of subscriptions.
Rondo turns files you select into a reviewable checklist. Processing and derived progress stay in this browser; you make changes on each merchant’s own site.
Old card
•••• ————
Not configured
Replacement card
•••• ————
Set up card aliases to begin
WHAT RONDO DOES
A truthful, human-guided workflow
Discovery surfaces possible payment relationships from files you choose. Approval creates a checklist only. Completion means you report that you handled the update yourself.
- 1DiscoverSelected statement, email, issuer, or manual signals
- 2ReviewEvidence, confidence, and uncertainty stay visible
- 3ApproveExplicit consent for a guided checklist only
- 4ActOpen the merchant’s own site and authenticate there
LOCAL DISCOVERY
Build your private checklist
Only derived merchant suggestions and your progress are saved in this browser. Original file contents are discarded after parsing.
STEP 1
Card aliases
Enter nicknames and last four digits only. Never enter a full card number, CVV, OTP, password, or personal email.
STEP 2 · STATEMENT
Transaction CSV
Headers: date, description or merchant, amount, and optional card_last4.
STEP 2 · EMAIL
Selected email export
Choose selected CSV, EML, or MBOX files. Unknown sender domains are skipped.
STEP 2 · ISSUER
Issuer token list
Headers: merchant, optional card_last4, and optional token_status.
Add a merchant manually
Use a merchant name only. Manual entries are suggestions until you review the account.
Ready. Set up aliases, then choose a file or load the synthetic sample.
Stored locally: card nicknames/last four, derived merchant evidence, approvals, statuses, and an activity record. No original email or statement rows are stored.
GUIDED MIGRATION
Review possible subscriptions
Evidence suggests where to look; it does not prove an active subscription or saved card. Imported source files are not retained.
No automatic updater is connected.
Approval never sends card data and never changes a merchant account.
DURABLE LOCAL ORCHESTRATION
A long-horizon agent with human gates
The agent plans and tracks work across visits. It can organise evidence and reminders, but it pauses for your approval, merchant login, OTP, and payment changes.
Automation boundary: this local agent really organises and persists your migration tasks. Merchant, bank, email, and payment APIs are not connected, so sensitive actions remain with you.
MISSION CONTROL
Waiting to start
Set up cards and discover merchants, then start the agent.
- Tasks
- 0
- Runs
- 0
- Last check
- Never
DURABLE TIMELINE
Recent decisions
TASK QUEUE
Merchant work
SAFETY BY DESIGN
A private migration workspace in your browser
This site is static and processes selected files inside your browser. No application data is sent to Cloudflare or any API.
Working here
- Last-four card aliases
- Local CSV, EML, and MBOX parsing
- Deduplicated evidence and ranking
- Durable local agent planning with human gates
- Browser-local persistence, export, and deletion
Unavailable here
- Accounts or cloud data storage
- Full card numbers, CVV, OTP, or passwords
- Live Gmail, merchant, or banking connections
- Automatic payment updates
- Provider verification
Privacy boundary: browser storage is readable by anyone using this browser profile. Export carefully and delete the workspace on shared devices. Clearing site data also removes progress.