Who We Are
Cukebook (Culinary Nutrition for Kidneys, Inc.) is a culinary nutrition platform that gives people with kidney disease the opportunity to thrive.
Our Cukebook mission is to make culinary nutrition a mainstay of kidney health.
We want Cukebook to be a go-to resource for people who want to learn HOW to cook kidney-friendly and WHY cooking this way impacts their lives positively.
Cukebook is a registered corporation in the state of Massachusetts. Our mailing address is:
Culinary Nutrition for Kidneys, Inc.
11 Blakeley Ave.
Somerville, MA 02145
USA
Our website address is: https://www.cukebook.org.
You can reach us via email at: anthony@cukebook.org or lauren@cukebook.org
Comments
When visitors leave comments on the site we collect the data shown in the comments form, and also the visitor’s IP address and browser user agent string to help spam detection.
An anonymized string created from your email address (also called a hash) may be provided to the Gravatar service to see if you are using it. The Gravatar service privacy policy is available here: https://automattic.com/privacy/. After approval of your comment, your profile picture is visible to the public in the context of your comment.
Media
If you upload images to the website, you should avoid uploading images with embedded location data (EXIF GPS) included. Visitors to the website can download and extract any location data from images on the website.
Cookies
If you leave a comment on our site you may opt-in to saving your name, email address and website in cookies. These are for your convenience so that you do not have to fill in your details again when you leave another comment. These cookies will last for one year.
If you have an account and you log in to this site, we will set a temporary cookie to determine if your browser accepts cookies. This cookie contains no personal data and is discarded when you close your browser.
When you log in, we will also set up several cookies to save your login information and your screen display choices. Login cookies last for two days, and screen options cookies last for a year. If you select “Remember Me”, your login will persist for two weeks. If you log out of your account, the login cookies will be removed.
If you edit or publish an article, an additional cookie will be saved in your browser. This cookie includes no personal data and simply indicates the post ID of the article you just edited. It expires after 1 day.
Embedded Content From Other Websites
Articles on this site may include embedded content (e.g. videos, images, articles, etc.). Embedded content from other websites behaves in the exact same way as if the visitor has visited the other website.
These websites may collect data about you, use cookies, embed additional third-party tracking, and monitor your interaction with that embedded content, including tracking your interaction with the embedded content if you have an account and are logged in to that website.
Analytics
We use Google Analytics for tracking visitors and aggregating information about the traffic to our website. The Google Analytics privacy policy can be found here. You can learn more about how to opt-out of tracking in Google Analytics here.
Marketing Campaigns
We use email marketing to communicate with customers and potential customers from time to time.
We may also send you “system” emails, such as password reset requests or payment notifications/receipts even if you have not opted-in to email marketing lists.
All marketing emails sent by us will include an unsubscribe link in the footer of the email. Emails sent to you may also include standard tracking, including open and click activities.
We may utilize social media and web advertising campaigns. These service providers use cookies on our sites and/or pixel tracking to serve ads across the different platforms.
- Google AdSense & DoubleClick (privacy policy | opt out)
- Twitter (privacy policy | opt out)
- Facebook (privacy policy | opt out)
What Rights You Have Over Your Data
If you have an account on this site, or have left comments, you can request to receive an exported file of the personal data we hold about you, including any data you have provided to us. You can also request that we erase any personal data we hold about you. This does not include any data we are obliged to keep for administrative, legal, or security purposes.
Where we send your data
Visitor comments may be checked through an automated spam detection service.
Protecting Your Data
The security and reliability of our service is our number one priority.
See wordpress.org/about/security for details on the security of the WordPress core itself.
Prevention is best when it comes to security, and as a first step, we follow all WordPress Code Standards in the plugins that we use.
Every Cukebook employee and contractor goes through background checks and an onboarding process that includes a trial period where access to customer data is provided only when working directly under the supervision of another staff member.
All staff only have access to systems that are directly required to complete the functions of their job. We use dual factor authentication for all critical systems and communications services, and automatically log all staff activity using an internal logging tool.
All staff (including any contractors) undergo initial training to ensure proper understanding of all security-related processes. Staff regularly attend industry conferences and otherwise stay informed of best practices and relevant trends. Staff review and agree, in writing, to all policies and procedures annually.
We only use third-party services, such as WPMUDEV, that are fully vetted and adhere to the highest levels of privacy and security practices.
Data Breach Procedures
Should any event occur where customer data has been lost, stolen, or potentially compromised, our policy is to alert our customers via email no later than 48 hours of our team becoming aware of the event. We will also report such incident to any required data protection authority. We will work closely with any customers affected to determine next steps such as any end-user notifications, needed patches, and how to avoid any similar event in the future.
