RecipeBlog Privacy Policy
Effective Date: August1, 2017

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.

General information
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
We generate two types of Emails. 1. System changes, and policy changes 2. Periodical and other informative emails You cannot opt out of type 1 emails but you can from type 2. We won’t ever ask for your password or other account information. If you receive any such email,kindly send it to us so that we can look in to it. Disclosure of your information By default, we don’t share your personal information outside the company. We won’t ever sell your personal information. We may share your personal information with third parties in limited circumstances, including: (1) with your consent; (2) to a vendor or partner who meets our data protection standards; or (3) when we have a good faith belief it is required by law, such as pursuant to a court order or other legal process. If we’re going to share your personal data in response to any legal process, we’ll give you prior notice so you can challenge it (for example by seeking court intervention), unless we’re prohibited from doing so by law or court order. We will object to requests for information about users of our site that we believe to be improper. If we merge or be aquired by another company such that your information will become subject to a different privacy policy, we’ll notify you before the transfer. You can opt out of sharing your personal info by deleting your account during the notice period.

We use cookies and tracking codes such as pixels and local storage to recognize you when you return to our Services. We use them in various ways, for example to log you in , evaluate email effectiveness, show relevant ads, and personalize information. We respect Do Not Track (“DNT”) settings in browsers. By logging in you are opting to allow RecipeBlog to ignore the DNT setting and to use cookies in order to provide you a personalized experience.
Some third-party services that we use, such as Google Analytics, may place their own cookies in your browser. This Privacy Policy covers use of cookies by RecipeBlog only and not the use of cookies by third parties.

Data Storage
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.

Data security
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 protected]