I'm a human being, this is my side-hustle, I have 1 full-time job and 0 lawyers. In other words, I don't (yet) have the resources to be a good steward of your data. This is why I try to limit the amount of data that I store about you.
Please pay attention to the how any recipes you create are licensed. To improve transparency, they are (at the time of this writing) all open-source using the MIT license. This means that they are public by design. Please don't assume recipes are private. They are not. This is the best feature of pooldash, but it is likely the most unusual.
Many software companies have business models that assume user-data is a new kind of gold. Personally, I think it's more like uranium, and I'm not equipped to handle it. I plan to monetize this software by charging users to unlock pro features. I don't show 3rd-party ads in the product, so I don't have a lot of incentive to share your personal info with 3rd parties. However, this is the internet, and it's complicated.
At the time of writing, this website is hosted in datacenters all over the world owned & operated by Amazon Web Services. I'm not "sharing" your data with them, but it lives on their servers. Most websites are hosted in 3rd-party datacenters (aka "The Cloud"), so this isn't unusual.
Of course, I also perform my work on an Apple computer... and I occassionally back my devices up to iCloud. Does that mean I share your data with Apple? Not really... but sort-of.
I use Gmail, and I sometimes get automated alerts about PoolDash operational metrics. Does that mean I share your data with Google? Good question.
For all of the above, you should assume the answer is "Yes, my data is shared with that 3rd party." There are numerous other providers that I use for other reasons (payment-processing, etc...). Just assume everyone has your data.
Well-meaning companies get hacked all the time. I'm a decent engineer, but still, I might get hacked in a way that exposes your personal data. If this happens, I'll do my best to alert all of you as soon as I know... but you should just assume that it will happen, and not enter any _really_ sensitive information into this product. I mean, honestly, it's a swimming pool app with a forum & some weird recipe-remixing features.
Just assume that whatever personal information you enter will be public, but only to hackers, and they'll use it in the worst way possible... and then be pleasantly surprised if that doesn't happen. Anyways, below is some legalese copy-pasted-adapted from other privacy policies on the internet: