NewsLoopVersion 1.0.0 · offline copyGuides

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:

Others may set cookies through your site: Google Analytics, AdSense and ad network code. That is what the cookie banner is for.

Ask visitors before using analytics cookies is on by default, and the EU and UK require it. While it is on:

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 ​

What the site keeps about readers ​

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:

  1. They open their account page, /account.
  2. 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:

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:

  1. The reader opens /account and clicks Edit your profile.
  2. 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:

When a reader asks you to delete their account:

  1. 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.
  2. Delete the account under System → Users (see Users and roles).
  3. 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.

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: