Privacy ​
This page explains what NewsLoop stores about your readers, which cookies it uses, and the tools readers have to see, download and delete their data. The settings are under System → Site settings → Privacy & analytics, and the newsletter's under Readers → Newsletter. This guide is not legal advice: check what the law asks of you where you publish.
Cookies ​
A reader who is not signed in can read your whole site without getting a cookie from NewsLoop. A cookie is only set when a reader:
- signs in, or uses a form, such as a comment, the contact form or the newsletter sign-up (a session cookie, which the form needs to work);
- opens a subscribers-only article while you offer a few free ones a month (a cookie that counts them; see Ads and memberships).
Others may set cookies through your site: Google Analytics, AdSense and ad network code. That is what the cookie banner is for.
Cookie consent ​
Ask visitors before using analytics cookies is on by default, and the EU and UK require it. While it is on:
- Google Analytics, AdSense and ad network code do not load until the reader clicks Accept on the banner.
- A reader who clicks No thanks reads everything as before.
- Picture ads set no cookies, so they always show.
- The banner only appears when there is something to ask about: a Google Analytics ID, or ads from other companies.
The banner shows your Consent message, with a link to the Privacy policy address when you set one. The reader's choice is kept in their own browser, not on your server. The built-in themes have no link to change the choice later; a theme can add one (a link with data-nf-consent-open).
In the EU and UK, Google also asks you to use a certified consent tool for AdSense. You can switch on Google's own under Privacy & messaging in AdSense.
Statistics ​
- Readers → Statistics counts views without cookies and without storing addresses.
- Plausible sets no cookies, so it runs without asking.
- Google Analytics 4 sets cookies, so it waits for consent. It is loaded with IP anonymisation turned on.
What the site keeps about readers ​
- Accounts: name, email address, the password in a form that cannot be read back, the public profile, and Google, Apple or passkey sign-ins.
- Sign-ins: each sign-in and failed attempt, with the network address and browser, in the activity log. Entries are removed after a year.
- Comments: the name and email typed, the text, and the network address and browser of whoever wrote it, signed in or not.
- Saved and liked articles.
- Newsletter: the email address, name, language, when the reader confirmed or left, and a scrambled (hashed) form of the network address they signed up from, as a record of their consent.
- Notifications: for each phone or browser that accepted them, a token from Firebase, the topics chosen and the language.
- Memberships and payments: the plan, its dates and every invoice. Card details are typed on the payment company's own page and never reach your server.
- Paywall: to stop endless free articles from one place, a scrambled form of the network address is counted, never the address itself.
Contact form messages are emailed to your Contact email and not kept on the site.
Download my data ​
A signed-in reader can download everything the site keeps about them, without any work for you:
- They open their account page,
/account. - Under Your data, they click Download my data.
They get one file, my-data- plus the date, in JSON, a format other services can read. It holds:
- their account, public profile, roles, and whether two-step sign-in is on;
- Google or Apple sign-ins, passkey names, and devices registered for notifications;
- their comments, and saved and liked articles;
- newsletter sign-ups under their account or their email address;
- memberships and payments;
- how many articles they wrote. Articles belong to the site, so they are counted, not copied.
Left out on purpose: anything that would let someone else sign in as them (passwords, two-step secrets, recovery codes, passkey keys and tokens), data about other people, and records kept for the site's security (network addresses on comments, the hashed consent address and the activity log).
This answers data requests under the GDPR and similar laws. The app has no download button: readers use the website. Staff can use the same button.
Deleting an account ​
On the website:
- The reader opens
/accountand clicks Edit your profile. - At the bottom, they click Delete account, type their Password and confirm.
In the app: Profile → Delete account, as the app stores require (see Mobile app). Readers who signed up with Google or Apple confirm without a password. Staff accounts cannot be deleted from the app.
In both places, a membership is stopped at the payment company first, so nobody is charged for an account that no longer exists. If the payment company cannot be reached, the account stays and the reader is asked to try again.
What happens to their data:
- Removed: the account, sign-in methods, passkeys, app sign-ins, saved and liked articles, and memberships.
- Kept, no longer linked to the account: comments, under the name the reader gave; payments and invoices, which you may need for your accounts; their newsletter subscription; and notifications on their phone or browser, which keep working without an account.
When a reader asks you to delete their account:
- If they have a membership, end it under Money → Memberships → Members. Deleting an account from the admin does not stop it at the payment company.
- Delete the account under System → Users (see Users and roles).
- If they ask, delete their comments under Newsroom → Comments, and remove their address under Readers → Newsletter → Subscribers. Removing a subscriber deletes the address for good.
Newsletter consent ​
- Ask new subscribers to confirm by email (double opt-in) is on by default. Keep it on: it is required in the EU, and it keeps typos and fake sign-ups off your list.
- Signing up with an address that is already on the list gives the same answer, so the form does not reveal who subscribes.
- Every newsletter has a one-click unsubscribe link, as Gmail and Yahoo require. Opening the link in a browser shows a button to confirm.
- Signed-in readers can also click Stop the newsletter on their account page, or turn it off in the app.
- Readers who leave stay on the list as unsubscribed, so they are never emailed again.
- Add subscribers is only for people who agreed to get your newsletter.
- With Mailchimp connected, every sign-up and departure is copied there too.
See Newsletter, push notifications and statistics.
Notifications ​
Website readers are only asked about notifications when you turn on Offer notifications to website readers. The browser asks for permission only after the reader says yes on your site. In the app, the phone asks for permission.
The app ​
The app shows no ads and does not track readers: it contains no ads SDK and shows no tracking prompt. Its settings link to your Privacy policy address as Privacy policy. See What the stores ask.
Fonts in the app ​
The app downloads the fonts chosen in the app builder from Google Fonts the first time it needs them, then keeps them on the phone. Google then sees the phone's IP address, as with any download, so name Google Fonts in your app's privacy policy. See Outside services.
Your privacy page ​
Make a page under Organise → Pages, such as /privacy, and put its address in Privacy policy address. Things to cover:
- who runs the site, and how readers can reach you about their data;
- the cookies used: the session cookie when signed in or using a form, the free-article counter if you use it, and those of Google Analytics, AdSense or ad networks if you use them;
- what you keep, from What the site keeps about readers, and for how long;
- the companies that receive data: your payment companies, analytics, AdSense and ad networks, Firebase for notifications, your email provider and Mailchimp, as far as you use them;
- that readers can download their data and delete their account themselves, and unsubscribe from any newsletter;
- your server's own logs, which your host or you keep.