RecipeBlog believes that personal privacy is and should forever be an important aspect of open Internet. We will respect your privacy in all matters related to RecipeBlog.
This policy sets out our privacy practices and explains how we handle the information we collect when you visit and use our pages, services, and other content.
What we may collect
We store information about what RecipeBlog pages you visit, information about your device (such as device or browser type), information you send us (such as an email address used to sign up or communicate with us), and referral information. When you use RecipeBlog Services, we may aquire and store your IP address. We may use this data to fight spam and other abuse; to personalize RecipeBlog Services; or to generate aggregate, non-identifying data about how users access RecipeBlog. When you create your RecipeBlog account, and authenticate via a third-party service like Google or Facebook, we may recieve, store, and periodically update the contact lists associated with that third-party account, so you can connect with existing contacts from that service who are on RecipeBlog.
When you upload your recipes and posts to RecipeBlog, we reserve the right to display them in other products owned by the parent company of RecipeBlog. However we will give you prior notification if and when this happens.Also you will retain the rights to your recipe.
Email from RecipeBlog
RecipeBlog uses third-party vendors and hosting partners, for hardware, software, networking, storage, and related technology we need to run RecipeBlog. Modifying your personal information or deleting your account If you have a RecipeBlog account, you can access and modify your personal information, or delete your account here.
To protect personal data from accidental or malicious destruction, we may not immediately delete residual copies from our active servers and may not remove information from our backup systems.
If you delete your account, your account and content may be unrecoverable.
We use encryption (HTTPS/TLS) to protect data transmitted to and from our main portal . Subdomains are currently not HTTPS protected. We are working towards a future where all pages in our portal are HTTPS. Even then, no data transmission over the Internet is 100% safe, so we can’t guarantee explicit security. You use the Service at your own risk, and you’re responsible for taking reasonable measures to secure your account (like using a strong password).
Changes to this Policy
RecipeBlog may periodically update this Policy. We’ll inform you about major changes . The most current version of the policy will always be here and we will archive former versions of the policy which will be available on request.
We welcome questions, concerns, and feedback about this policy at email@example.com