I was buying a train ticket on Eurostar for my mother. I filled her name as the passenger. Scrolled down and used the 1Password data I have to fill my address and billing information. I proceed and pay. Later, when checking the ticket, I see it's on my name. 1Password changed the passenger details, and since the screen is small, I did not notice.
No 100% refund from Eurostar, but lesson learned.
I'm not leaving 1Password though. It's too convenient for my family.
I’ve had it do stuff like that and it’s very annoying when it’s an issue - which it sometimes is.
That and a lack of easy way to report a login page that doesn’t work perfectly would be my top annoyances (behind a 33% increase in a subscription that was already annoying me each time it came around).
We use Redis to store geocoding data from Google Geocoding API with a TTL of 30 days, per the policy. It's $4/1000 requests. There'd no business without the cache.
I was buying a train ticket on Eurostar for my mother. I filled her name as the passenger. Scrolled down and used the 1Password data I have to fill my address and billing information. I proceed and pay. Later, when checking the ticket, I see it's on my name. 1Password changed the passenger details, and since the screen is small, I did not notice.
No 100% refund from Eurostar, but lesson learned.
I'm not leaving 1Password though. It's too convenient for my family.