A passport scan is the one credential your user cannot rotate after a leak. Apps built on Lovable exposed passport details and more than 200,000 private messages. The Hacker News reports that a stolen Fireworks AI key led to the Cursor data breach and a trojanized Claude Code extension.
The rule I keep on payment platforms: the server decides access per record against the session identity. Ids get enumerated, and any key that has left your own infrastructure counts as burned, so narrow the scope and schedule the rotation. If you shipped an MVP fast, I review the account and data-access paths and put real server-side checks in, and that scope is days, not months. Tell me the endpoint you trust least and you get cost and timeline within a day.