Privacy policy

Two different sets of people appear below, and they are treated differently.

• Our customers, meaning the publisher that connects a site, and the editors and writers they give accounts to. We hold their email addresses and we serve them their own numbers.
• Their readers, meaning the public visiting the publisher's website. We never receive anything that identifies an individual reader. What we read from Google Analytics is already aggregated: how many views a page path received, and how many sessions. No identifiers, no profiles, no individual behaviour.

• Content metadata from the customer's WordPress site, read from the public WordPress REST API: post titles, links, publication times, author names, categories and tags. This is information the site already publishes to anyone who visits it. We do not read drafts, private posts, comments, or anything behind the site's login.
• Traffic analytics from Google Analytics, read with the customer's authorization and only for the property they choose. Specifically: page paths, view counts and session counts, by day. This is covered in its own section below.
• Account information for the people we give logins to: email address, display name, job title, role, and the addresses on the briefing mailing list. Passwords are handled by our authentication provider and we never see them.

That is the whole list. There is no WPNewsroom tracking script, no pixel, and no cookie placed on any customer's website. We add nothing to the pages your readers load.

WPNewsroom's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

In practice, that means all of the following.

• We request one scope, analytics.readonly. It is a read scope. WPNewsroom cannot change a Google Analytics property, cannot delete anything, and cannot create anything.
• We use the data for one purpose: producing the reports the customer sees in the app and in their morning email. It is not used to build advertising profiles, it is not used to train machine learning models, and it is not used for any purpose the customer has not been shown.
• We do not sell it, and we do not transfer it to anyone else except the service providers listed below who store or deliver it on our behalf.
• No person on our side reads a customer's Google data except where the customer has asked us to (for example, to investigate a number that looks wrong), where it is necessary for security, or where the law requires it.
• Authorization is revocable at any time, by the customer, without asking us. Removing WPNewsroom at your Google Account permissions page stops all future access immediately. Tell us as well and we will delete what we already hold.

We join the two sources together. Content metadata says who wrote what, and when. Analytics says which paths earned attention. Putting them side by side is the entire product: which stories are climbing, which older stories have started moving again, and how publishing volume compares with traffic earned, per writer.

Those readings are shown in the app to signed-in accounts belonging to that publisher, and summarised in an email sent to the addresses the publisher nominates. Nothing else happens to it.

We use a small number of service providers. They process data on our instructions, and none of them are permitted to use it for their own purposes.

• Supabase, which hosts the database and handles account sign-in.
• Vercel, which hosts and serves the application.
• Resend, which delivers the briefing emails.
• Google, as the source of the analytics data.

We do not sell personal information, and we do not share it for advertising. There is no advertising in this product.

Content metadata and the daily traffic readings are kept for as long as the publisher is a customer, because the product's whole value is the comparison with earlier days. Account records are kept until the account is removed.

When a customer leaves, we delete their content metadata, their analytics readings and their account records within 30 days of being asked, and we revoke our own stored Google credentials for them immediately. Backups age out on their own cycle, which is no longer than 30 days.

Data is encrypted in transit. Access to the production database is limited to the people who operate the service. The application will not serve a publisher's numbers to an account that is not on that publisher's allowlist, and that check runs on the server on every request rather than in the browser.

No system is perfect, and we would rather say that than claim otherwise. If you find a problem, the address below reaches a person.

• Ask us what we hold about you, and we will tell you.
• Ask us to correct or delete it, and we will, unless we are required to keep it.
• Revoke the Google connection at any time, as described above.
• Come off the briefing mailing list at any time. Ask us, or ask whoever administers your newsroom's account.

The application sets one cookie, which keeps you signed in. It is not used for tracking or advertising. This marketing site sets no cookies at all.

WPNewsroom is a tool for newsrooms. It is not directed at children, and we do not knowingly hold data about anyone under 16.

If we change what we collect or what we do with it, we will update this page and change the date at the top. Material changes will be emailed to customers rather than left here to be discovered.

Write to info@wpnewsroom.com about anything on this page, including a request to see or delete what we hold. A person reads that address.