Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

The information is transmitted via HTTPS to the carrier. Once your session on Leaky ends, the data is gone -- there is no data store.


Interesting -- so are you ruling out the possibility of storing the data in the future for features like periodically checking for updates in my rate? That sounds like a killer feature (that I would even be willing to pay a subscription for), but then I'd also want to be damn sure that you're storing that data well.

EDIT: in fact, for a subscription based service, you could figure out the optimal pricing quite easily. If the annual price of your subscription were less than the typical insurance savings by having it monitored, you'd have a hell of a business model.


Yeah -- we'd certainly love to, but we didn't think that we'd be able to securely store the data at the moment -- so we didn't want to risk it. That's absolutely a feature that we'd like to implement though!


Protip: Consumers don't care about security.


That implies you're keeping such information with my session (across requests). Is that the case? I may just be misunderstanding.

If so, you need to encrypt it first. Storing sensitive data in the user's session is akin to writing it to disk in plaintext.




Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: