Privacy policy


  Last updated 24 May 2018   The terms “we,” “us,”, “our” or “I” refer to Weaningful. The term the “Site” or “blog” refers to The terms “user,” “you,” and “your” refer to site visitors, customers, and any other users of the site.



Who we are

  At, my aim is to teach parents about baby nutrition, share my findings on the subject, offer advice from my own experience with the weaning process and share recipes which I find nutritious, easy and relatively quick for busy parents. The aim of this Privacy Policy is to rest you assured that I am not using any data collected from you as a means of making profit by trading email lists or any sort of activities related to that. Do read on if you’re interested in how I collect data and what I do with it.  

What personal data we collect and why we collect it

  Cookies – not the type that you eat, I’m afraid (and even those can be very un-baby-friendly!). These are bits of data which are stored on a computer when someone is browsing the Internet through a web browser. They come in handy for people who shop online or help you remember the pages you recently visited, for example. At Weaningful, we collect personal data such as first name, email address or demographic information through these cookies. What do I do with it? I use it to study how my content is performing over time and to see where my readers are coming from for example, in order to provide better and more tailored content. 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.  

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: After approval of your comment, your profile picture is visible to the public in the context of your comment.  

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 tracing your interaction with the embedded content if you have an account and are logged in to that website. is a participant in the Amazon Services LLC Associates Program and the Amazon EU Associates Programme, affiliate advertising programs designed to provide a means for us to earn fees by linking to, and affiliated sites. Many posts on my blog contain advertisements or affiliate links, which means I will make a small commission if you buy any products that have been linked to on this blog. My experiences with a product do not represent the experiences of other people or the quality of the product. They only represent my experiences. Remember to always shop around and read product reviews before making any purchase, in order to be a more informed consumer.  

Analytics – When someone visits, I use a service called Google Analytics (you can Google it!), to collect log information and details on what each visitor is doing when landing on my blog. This is useful for me to see my most popular posts, my least popular ones and how users interact with my posts after they have read them. Google does not identify anyone by looking at this data. He can’t point at you particularly and say “You’ve been a bad parent! You’re not getting anything this Christmas!” (phew, thank God for that!)  

Facebook Pixel – this is a tracking method used by Facebook and I have it set up for retargeting purposes (meaning you might see an ad from my Facebook page because you visited this website sometime in the past). What the Pixel receives is this type of data:

  • Http Headers – Anything present in HTTP headers. HTTP Headers are a standard web protocol sent between any browser request and any server on the internet. HTTP Headers include IP addresses, information about the web browser, page location, document, referrer and person using the website.
  • Pixel-specific Data – Includes Pixel ID and the Facebook Cookie.
  • Button Click Data – Includes any buttons clicked by site visitors, the labels of those buttons and any pages visited as a result of the button clicks.
  • Optional Values – Developers and marketers can optionally choose to send additional information about the visit through conversion tracking. Example custom data events are conversion value, page type, and more.
  • Form Field Names – Includes website field names like ‘email’, ‘address’, ‘quantity’ for when you purchase a product or service. We don’t capture field values unless you include them as part of Advanced Matchingconversion tracking, or user properties.



Who we share your data with

  If you sign up through any of the forms on this blog (either hosted or pop-up) to receive a freebie or be kept up to date with the progress of my ebook for example, I collect your email address and possibly your first name too, depending on which form you signed up through. I use that email to send you the freebie and updates regarding new blog posts, tips on weaning, and eventually let you know when the ebook is finally published! My email marketing provider is MailChimp and they will deliver all my emails to you. They gather statistics regarding email opening rates and clicks and these help me figure out what works and what doesn’t in terms of the content of my newsletters. You can check out their privacy policy if you want to find out more. You can definitely opt out at any time by clicking on the Unsubscribe link at the bottom of each of my emails. This will stop all future emails from me to you (I hope I am not that annoying!).

  This blog hosts ads, which help me make a revenue. Third party vendors, including Google, use cookies to serve ads based on a user’s prior visits to your website. Google’s use of the DoubleClick cookie enables it and its partners to serve ads to your users based on their visit to your sites and/or other sites on the internet. Users may opt out of the use of the DoubleClick cookie for interest-based advertising by visiting Ad Settings.  

 As mentioned in the previous section, Facebook will also receive data based on you browsing this website. Check out their privacy policy for details.


How long we retain your data

  If you leave a comment, the comment and its metadata are retained indefinitely. This is so I can recognise and approve any follow-up comments automatically instead of holding them in a moderation queue. Google Analytics is currently set up to store your data for 50 months.  

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

  Like I mentioned above, Mailchimp is my email service provider of choice. They are located in the US, therefore if you are an European Union visitor and subscribe to my newsletter, your data will leave the EU and will be hosted on Mailchimp’s servers in the US. This does not mean it is less safe or the standards of safekeeping are different over the pond. Please consult their privacy policy for more info on how they protect their contacts’ data.  

For more information (and/or peace of mind)

You can contact me at any time using this email address: I’ll be more than happy to hear from you and give you a virtual pat on the back for reading this far into a privacy policy statement.