kkyryl

this message validates a feature we are working on. :)

this sounds like a great idea from the rational standpoint, but our data says otherwise. we've seen a conversion increase and generally more people started buying when we enabled monthly prices and again when we made them default. I have a few theories to back it up – but generally speaking pricing perception is emotional, not rational. looking at our prices you'd assume no one buys monthly, but about 40-50% of people do :)

fixed that too. thank you again.

that's the thing about quick fixes lol :)

actually, quite a few rules we have can be somewhat replicated in Gmail, but it's not as easy to actually act on the selection.

I went ahead and added more options there: in addition to 6 months (previous lowest) I added 3 months, 1 month, 2 weeks, 1 week. Would that be it?

(and that link has a 30% discount in it in case you decide to subscribe)

Hmm, makes sense. I went ahead and added it under pricing. Thank you :)

Free plan allows you to clean (remove, trash, label etc) 1000 emails

All job servers are stateless by design and easily disposable/replaceable with a fresh build so we don't back them up. we don't back up user data either – it's deleted within 24 fours (or immediately on request). the only thing backed up is a table with refresh tokens which are encrypted and decryption keys are not backed up with it.

yes, that is correct. we actually started without keeping refresh tokens and only using access tokens – but they expire really fast and google api randomly stops accepting them so we had to start keeping refresh tokens as well.

they are encrypted and can only be decrypted by "scan" and "action" (delete, trash, etc) jobs, job servers are not exposed to the outside and can only be accessed via the private network via ssh using access keys and only from a specific node which has those keys. keys are password protected. access to that specific node is restricted to a set of known public ip addresses. database and job servers are different servers of course. database servers are also only accessible within the private network.

the only thing that's publicly exposed is a load balancer. to access anything else we log in to the "gateway" instance which we access by ip only and it does not have any domain name associated with it.

with all that – I am very open to ideas about protecting that further.