Lifetime is implied to be the lifetime of the company as is the case with LITERALLY EVERYTHING.

From an economic view: In this case as soon as you hit 13 months without filen going bankrupt you are literally free compared to the 200GB plan with Google Drive which you would still be stuck paying $4 CAD/month for 200GB long after the lifetime plan has paid for itself (assuming they don't increase monthly rates as time goes on, which they always do).

Go ahead and pay monthly if you want but you'll be in exactly the same position if a company goes under, except you would have paid a hell of a lot more than 35 Euro by that point.

Ya it seems like accessibility via other protocols is in development... After reading more into today it sounds like rclone is being actively worked on at least.

They stated on their blog webDAV syncing won't be compatible with their E2EE though.

Ya the "lifetime of the service" is always mentioned (you're still SOL if a service ends and you've been paying monthly, you just would have massively overpaid in the meantime); and I agree when its a large premium for a "lifetime". But in this case considering it would only need to stay viable for 13 months in order to get your ROI on 35 euro invested compared to a monthly subscription (GDrive is $4 CAD/month for 200GB) that is also known for randomly deleting your data/accounts without warning (GDrive), I think its worth the risk. If in 5 years they go under you can always migrate to another service and you saved 5 years - 13 months of monthly payments. And ofc basic data storage practices still should be followed. Min 3 copies, one offsite.

Interesting about the SAF functionality and worth noting for anyone wanting it for that use; I wonder if its on their roadmap at all. As I said, I'm using this as an offsite backup so should work fine for that.

As an aside do you have a recommendation for solid SAF functionality with Keepass (esp on linux)? I currently use gdrive linked through gnome accounts in order to sync my keepass file across all my devices since I haven't found a better option but KeepassXC constantly overwrites the file with temp files (randomly generated string file names) which causes errors when I try to open it on KeepassDX on my phone since the database file is no longer there but replaced with a temp file. Not sure if its due to Gdrive constantly revoking file manager permissions or what.

I mean, not a great source... That's just a link to a forum post and the only thing they reference for it "not being secure" was a github PR from 2021... Not saying its great they had teething issues, but that's literally a year within starting up and they fixed all those issues right away, and had an independent audit done. So I kinda feel like using it to say they're not secure now isn't very useful. But if you have something showing their current deployment is insecure please share.

They did a complete infrastructure overhaul at the start of 2023 too moving to their own hardware and such so I imagine more might have changed since 2021 than just those issues.

This is literally client-side encryption using fully open source programs... If you "do not trust it to be e2e", verify the code yourself. Doing your own encryption on top would be redundant.