Privacy Policy

MY-BOOK is a blogging platform run by myproject.ai (opens in a new tab) (“MAI”, “we”, “us”). MY-BOOK is part of the myproject.ai family of services and uses the same myproject.ai account and sign-in.

We decide how and why your personal data is used on MY-BOOK, which makes us the controller of that data under data protection law.

If you have a question about this policy or your data, please get in touch through our contact page. We reply to privacy requests within one month.

We only collect what we need to run MY-BOOK, keep it safe and give authors honest numbers.

Your account

You sign up and sign in through the shared myproject.ai sign-in. We receive your name, email address and mobile number, plus any profile details you add in Settings: bio, address details, profile and cover pictures, author headline, areas of expertise, website and social links. We use them to run your account, show your author profile and keep your account secure. If you choose to sign in with Google or LinkedIn, that service shares your name, email address and profile picture with us.

Posts and drafts

We store the posts, drafts, images and series you create, their version history, the co-authors, editors and reviewers you invite, and any publishing schedule you set. Published posts and your author profile are public.

Comments

We store your comments and replies, which appear publicly with your name and picture, any reports you make, and moderation details such as the result of automatic spam checks. To fight spam we keep a scrambled (hashed) form of the network address a comment came from, never the address itself.

Likes, saves and follows

We record the posts you like or save, the authors you follow and whether you want an email when they publish. Authors can see who liked their posts and who follows them.

Reading analytics

When you open a post we record a view so authors get honest numbers: which post, when you first and last opened it, how far you scrolled (25%, 50%, 75% or 100%), how long you spent actively reading, and where the visit came from (a search engine, social media, the name of another website, or direct). When you share a post we record the channel you used, such as WhatsApp or copy link.

So that the same reader isn't counted twice, we recognise repeat visits like this:

• if you're signed in, by your account;
• if you accept analytics, by a random visitor ID kept in your browser, which we scramble with a secret key before storing it;
• otherwise, by an anonymous daily code our server makes from your network address, browser details and the date. It changes every day and is never stored on your device.

Visits from bots, and authors reading their own posts, aren't counted. Authors only see totals and charts, never who read what.

Newsletter and emails

If you subscribe, we keep your email address, the emails and topics you've chosen, and a record of your consent: when and where you subscribed, the wording you agreed to and a scrambled form of your network address. We also keep a log of the emails we send you, delivery reports from our email provider (for example delivered, bounced or marked as spam) and the result of checking that your address can receive email. Our newsletter consent page has the details.

Messages to us

If you use our contact form, we keep your name, email address, topic, message and network address so we can reply and prevent abuse.

Technical and security logs

Like any website, our servers process network addresses, browser details and request logs to deliver pages, apply limits that stop abuse and fix problems. Each sign-in session records the network address and browser it was last used from, so we can keep your account secure. We also log important account and admin actions for security.

AI features

If you use our AI writing tools, the text you send is processed by an AI provider to produce suggestions. The Listen feature turns published posts into audio using an AI text-to-speech provider. No reader data is sent for either feature.

Data protection law says we need a lawful basis for each way we use personal data. We rely on:

• Contract: to run your account and the features you use, such as publishing, commenting, likes, saves, follows and collaboration.
• Legitimate interests: to keep MY-BOOK secure and free of spam, moderate comments, count visits with the anonymous daily code, give authors total figures, email you about activity on your posts and new posts from authors you follow, and improve MY-BOOK. We balance these interests against your rights, and you can object at any time.
• Consent: for newsletter emails and for the analytics visitor ID kept in your browser. You can withdraw your consent at any time.
• Legal obligation: where the law requires us to keep or share information, for example to respond to a valid legal request.

We keep personal data only for as long as we need it. These periods are built into our systems:

When a post is deleted, its comments, likes, saves, reading records and statistics are deleted with it. What we store in your browser is covered in our Cookie Policy.

• The public: published posts, author profiles, comments, and like and follower counts can be seen by anyone, including search engines.
• Service providers: companies that host our servers, database and images, send and check our emails, and provide AI processing. They act on our instructions under contract and may only use the data to provide their service to us.
• Other myproject.ai services: your account is shared across myproject.ai services because they use one sign-in.
• Sign-in providers: Google or LinkedIn, if you choose to sign in with them.
• Legal and safety reasons: if the law requires it, or to protect people, prevent fraud or defend our legal rights.

Google Search Console receives nothing from readers. It works the other way round: Google reports total search figures for our pages (searches, clicks, impressions and positions), which we show to authors and admins.

We don't sell your personal data, and we don't use advertising networks or third-party tracking. Videos in posts come from YouTube or Vimeo: the player only loads when you press play, and YouTube preview images come from YouTube's servers. Once a video plays, the video service handles your data under its own policy.

Some of our service providers may store or process data outside the UK and the European Economic Area. When that happens, we make sure appropriate safeguards are in place, such as UK adequacy regulations, the UK International Data Transfer Agreement or Addendum, or the EU Standard Contractual Clauses. Contact us if you'd like more information.

Under the UK GDPR, and the EU GDPR if you live in the European Union, you have the right to:

• Access your data and get a copy of it.
• Correct data that's wrong or incomplete. You can edit most of your details yourself in Settings.
• Delete your data, sometimes called the right to be forgotten.
• Object to uses based on legitimate interests, including the anonymous daily visit count.
• Restrict how we use your data while a concern is being sorted out.
• Take your data with you (portability): get the data you gave us in a common, machine-readable format.
• Withdraw consent at any time, by unsubscribing from emails or changing your cookie settings. This doesn't affect anything we did before.

To use any of these rights, contact us through our contact page. We may ask you to confirm your identity first. It's free, and we'll reply within one month, or tell you if a complex request needs up to two more months. Our data handling page explains how exports and deletion work.

If you're unhappy with how we've handled your data, you can complain to the Information Commissioner's Office (ICO), the UK's data protection regulator, at ico.org.uk (opens in a new tab). If you live in the EU, you can contact your local data protection authority. We'd appreciate the chance to put things right first.

MY-BOOK is for adults and teenagers aged 13 or over. It isn't designed for children under 13 and we don't knowingly collect their data. If you think a child under 13 has given us personal data, please contact us and we'll delete it.

We'll update this page and the date at the top whenever we change this policy. If a change is significant, we'll tell you before it takes effect, by email or with a notice on MY-BOOK.