Skip to content
starfeed.com

Privacy policy

Updated

This page describes what starfeed.com does with information about visitors, as the site works today. There are no accounts or logins, and most of the site can be read without giving us anything. Personal data reaches us when you subscribe to the email digest, turn on notifications, send a contribution, post or rate in Fan Talk, start a plan for automated access or email us, and through the server, analytics and advertising described below.

1Who we are

starfeed.com is independently operated and not affiliated with any company.

starfeed.com decides what data this site collects and why, and is responsible for it. Questions and requests about your data: starfeed.com@gmail.com.

2What we process

Only what is listed here. The “Every visit” groups apply to everyone; the others only if you use that feature.

Every visit: server log

  • Like most web servers, ours logs each request: IP address, time, the full address requested (including anything after “?”), status, referring page, browser identifier (user agent) and response time.
  • So the log can hold, next to your IP address, search terms you type, the star IDs your browser sends to build your feed, and the token in links from our emails.

Every visit: anonymous page counts

  • Our own counter records the page path (without anything after “?”), the referring site (domain only, for search engines, social networks and other sites), device type, site language and section, and your country as reported by Cloudflare. These are kept only as hourly and daily totals.
  • To count unique visitors per day, it keeps a hash of your IP address and user agent mixed with the date and a server secret. A new hash is made each day, so visits on different days cannot be linked through it.
  • The counter sets no cookie and stores nothing in your browser. It ignores known bots and automated browsers.

Google Analytics and AdSense

  • Google Analytics runs on all pages. Google AdSense loads only after your first tap, click, key press, mouse-wheel turn or mouse movement. It never loads on account or payment pages and does not load on pages kept out of search results (if it already loaded on an earlier page, it can stay active when you move on to such a page within the site). Both set cookies, but in the EEA, the UK and Switzerland advertising and analytics cookies are set only with your consent. See “Cookies and browser storage”, “Advertising” and “Service providers”.
  • Google's consent tool, which shows the consent message where the law requires one, loads on every page except this privacy policy. This page never loads AdSense or Taboola either. Taboola's script loads on most other pages shortly after the page has finished loading, and shows recommendations on article and star pages; see “Recommendations from Taboola”.

If you subscribe to the email digest

  • Your email address, the language, categories and stars you choose (up to 20 stars), and your delivery hour.
  • Status and dates: sign-up, confirmation, unsubscribe and last send.
  • A random token used in your confirm, settings and unsubscribe links. The confirm link works for 24 hours; the settings and unsubscribe links do not expire.
  • Where you signed up (for example the footer or a star page) and the country of your connection, a two-letter code from Cloudflare.
  • A shortened hash of your IP address combined with the date, used to allow at most 10 sign-ups per hour from one IP address. The address itself is not stored, but we treat the hash as personal data.
  • A log of each email we send you: date, type (confirmation, digest or notice), number of items, the sending service's message ID and the delivery result.

If you turn on notifications

  • When you turn on notifications (from the notification prompt or by following a star), your browser gives us a push address (a link at your browser maker's push service) and two encryption keys.
  • We store them with the stars you follow (up to 200), your language, your time zone, your notification settings and delivery counters, plus a log of what we sent and when, tied to a shortened hash of the push address. No IP address or browser details are stored with them.

If you send a contribution

  • Translations, schedule tips, alternative names, correction suggestions, star requests, “translation looks wrong” flags and reports, with the star or story they concern, your language and the time.
  • The random device ID kept in your browser (sf_device) and an IP hash made the same way as for sign-ups. Both are used to allow at most 30 contributions per hour and to count requests and reports from different devices.
  • Translations, schedule tips and alternative names are shown publicly, without any identifier. Correction suggestions go to the operator queue; applied corrections are listed with the corrected value and any source link in the star's revision history. Star requests appear in the public list of recent requests with the star's name, Wikidata ID and number of requests, and nothing about who sent them.

If you post, rate or report in Fan Talk

  • The first time you post, rate or report, your browser gets a random identity. It is kept in a signed cookie (sf_uid) and, for networks that strip cookies, as the same signed token in your browser's storage. You appear under a pseudonym such as BrightOtter4821, which you can change.
  • What you post (the text, an optional link, the star's room and its language), the ratings you give from 1 to 5 and the reports you send with their reason, each with the time. Posts and pseudonyms are public and may appear in search results. Ratings count towards public totals and averages.
  • For abuse limits we keep a hash of your IP address mixed with a server secret and the date, so it changes every day. We clear it after 7 days (30 days for reports). The IP address itself is not stored.
  • Before a post appears, a keyword filter and an AI model check it against the community guidelines. The AI model receives the post text, the star, the room's language, the domain of any link, the text being replied to and report reasons. It does not receive your pseudonym, identity, IP address or email address.

If you start a plan for automated access (API, MCP or pages)

  • Creem (creem.io) runs the checkout and processes payments as merchant of record, and sends us your email address and, if you enter one, a company name. You enter your card details at Creem, and only Creem handles them. starfeed.com never receives card or bank details.
  • We use your email address to send your key, to answer you, and to send notices about your plan: a reminder before your free trial ends, usage and quota notices, usage charges and your monthly usage limit, and changes to prices, the terms or the licence.
  • We keep request counts per key and a hash of the key, never the key itself. For the usage charges of the Developer plan, we send Creem only the number of billable requests per key and period, never what you requested.
  • If you ask for a sign-in link on the My keys page, we use the email address you enter only to find your keys and, if there are any, to email a one-time link to the address we have on file. We do not keep the address you typed; to limit abuse we keep only a keyed hash of the mailbox in a counter that is cleared after a few days. The link signs you in on that device for up to 2 hours.
  • Plans: Licensing and API access. Terms: Terms of Service.

What we never collect

  • No accounts, passwords, names, phone numbers, postal addresses or payment details, except what you choose to give us yourself in an email or in a copyright or rights notice, such as your name and contact details. We use that only to handle your request.
  • No precise location. Our own records hold only the country of your connection, and your time zone if you turn on notifications. Google Analytics estimates a rough location, such as a city, from your IP address.
  • No raw IP addresses in our database. They appear only in the short-lived server log.
  • Your email address, IP address and device or Fan Talk identity are never sent to AI models. AI is used on public news text, headlines and star names, and to check Fan Talk posts as described above.
  • We do not sell or rent subscriber data.

3Cookies and browser storage

Cookies are small pieces of data a site asks your browser to keep and send back. Browser storage (localStorage and sessionStorage) stays on your device and is sent to us only when a feature needs it. This is the full list.

Cookies from starfeed.com

sf_lang
Remembers your language edition, so the site opens in that language.
sfh
Today's date, written by a script on the page. Our server checks it to tell browsers from scrapers that do not run scripts. It identifies no one.
sf_sub
Your subscription token. It may be set when you confirm the digest or open its settings page, so that following a star can also add it to your digest. Sent only to our subscription service and not readable by scripts.
sfrsc
A technical cookie our server deletes at once. It holds no data.
sf_uid
Your Fan Talk and ratings identity: a random ID signed by our server. Set the first time you post, rate or report. Sent only to the Fan Talk and ratings services and not readable by scripts.
sf_uh
A marker without any ID that tells the page you have a Fan Talk identity, so it asks for your own ratings only then.
__Secure-sf_acct
Sign-in for the My keys page, set when you open an emailed sign-in link. Signed by the server and sent only to the My keys service; scripts cannot read it.
sf_dns
Set when you use the “Do Not Sell or Share My Personal Information” link. While it is set, Taboola recommendations are not loaded in this browser. It identifies no one.

Cookies from Google

_ga, _ga_<ID>
Google Analytics: tells visitors and visits apart to measure how the site is used.
__gads, __gpi, __eoi
Google AdSense: delivers and measures ads and limits how often you see the same ad.
FCCDCF
Google's consent message: stores the choices you made in it, so it does not ask again.
FCNEC
Google's consent message: measures how the message works.
Cookies on Google domains
Google's advertising cookies (for example on doubleclick.net), used to personalise and measure ads across sites.

Cookies and storage from Taboola

t_gid, t_pt_gid, taboola_fp_td_user_id, taboola_select, trc_cookie_storage
Taboola: identifiers used to choose, personalise and measure recommendations, including across other sites that use Taboola. Set only after the checks described under “Recommendations from Taboola”.
taboola_session_id, _tb_sess_r, _tb_t_ppg, abLdr, abMbl, tb_click_param
Taboola: session, page-view and click information and loader settings.
datadome
Bot protection used by Taboola.
taboola global:*, trc_cache, tbl-session-referrer, tb_id, eng_mt.*, __tbwt (browser storage)
Taboola: kept in your browser's storage for the same purposes.

Cookies from Cloudflare

__cf_bm, cf_clearance
Set only when Cloudflare checks a browser for bot traffic, to remember the result.

Browser storage (stays on your device)

sf_device
A random ID your browser creates. Sent with each contribution and report.
sf_following
The stars you follow. Sent to our server to build your feed.
sf_saved, sf_read
Stories you saved (latest 300) and stories you have read (latest 500). Not sent.
sf_mtflag, sf_reported
Items you have flagged or reported, used only to show the buttons' state. Not sent.
sf_interests, sf_onboard
Interest categories you picked for the front page. Sent as your digest categories if you subscribe from the short sign-up box.
sf_topics, sf_topics_skip
The topics you picked (or a note that you skipped the topic picker), used to put those topics first on the front page. Sent with your email only if you subscribe.
sf_push_prompt, sf_push_topics, sf_push_muted, sf_push_synced
How often the notification prompt has been shown and whether you answered it (with a page-view count used to decide when to show it), your notification topics and muted stars, and a marker of the last sync with our server.
sf_sub_pending, sf_subbar_dismissed, sf_exit_shown
When you last signed up, closed the sign-up bar or were shown the sign-up pop-up, so we do not keep asking.
sf_hot_tab, sf_region
Your last tab and region on the hot issues page.
sf_uid_t
The same signed identity token as sf_uid, kept in case a network strips cookies. Sent as a header with Fan Talk and rating requests.
sf_my_ratings
Your latest ratings (up to 400), so the stars show your choice. Not sent.
sfg (sessionStorage)
A timestamp written by the bot-check page to prevent reload loops.

4Advertising

starfeed.com shows ads served by Google AdSense. Google and its partners use cookies and similar identifiers to show ads, including ads based on your earlier visits to this and other websites, to limit repeats and to measure results.

AdSense loads only after your first tap, click, key press, mouse-wheel turn or mouse movement, never on account or payment pages and not on pages kept out of search results (if it already loaded on an earlier page, it can stay active when you move on to such a page). In the EEA, the UK and Switzerland, advertising cookies are set only with your consent.

With each ad request Google receives the page address, your IP address, browser details and its cookies. Google explains how it uses this in How Google uses information from sites or apps that use its services.

You can turn off personalised ads in Google's Ads Settings. Blocking or deleting cookies in your browser also limits them. We never give advertisers your email address.

Google's consent message records your choices about ads. In the EEA, the UK and Switzerland it asks for your consent before personalised ads and advertising cookies (see Your rights in the EEA, the UK and Switzerland). In US states with privacy laws you can opt out of the sale or sharing of your data for personalised ads (see Your rights in US states). AdSense never loads on this privacy policy page.

5Recommendations from Taboola

On article and star pages (news articles, hot issue and story pages, and the pages about each star, such as the profile, today, schedule, history, date archive and fan talk pages), a block of recommended stories from Taboola can appear after the page's content, in its own box marked by Taboola. It links to other stories on starfeed.com and to sponsored content on other websites, and starfeed.com is paid for the sponsored part. On other pages, such as the home page, the first page of each menu section and search, Taboola's script runs without showing anything, to count visits and to choose recommendations.

Taboola's script loads on every page shortly after the page has finished loading, except this privacy policy page, the My keys and payment confirmation pages, the email digest settings pages and error pages (if it already loaded on an earlier page, it can stay active when you move on to one of those pages within the site, but never on this page). Unlike AdSense, it does not wait for a tap or click.

Taboola receives the page address, your IP address, browser details and its own cookies and identifiers, and uses them to choose, personalise and measure recommendations, including on the basis of your visits to other sites that use Taboola. Its cookies are listed under Cookies and browser storage.

In the EEA, the UK and Switzerland, Taboola loads only after Google's consent message has recorded your choice, and Taboola (IAB vendor 42) reads that choice. If you do not consent, Taboola says it shows recommendations based on the page only, without personal data. If the consent message cannot load, for example because it is blocked, Taboola is not loaded.

In US states with privacy laws, Taboola is not loaded if you use the “Do Not Sell or Share My Personal Information” link at the bottom of our pages. If your browser sends a Global Privacy Control signal, Taboola is not loaded where a US state privacy law applies or where we cannot tell whether one does. If you opt out with Google's own link instead, Taboola still loads but receives your opt-out in the signal of Google's consent message. Otherwise Taboola reads your choices from that signal.

Taboola explains its processing in Taboola's privacy policy. You can opt out of Taboola's personalised recommendations or ask Taboola for your data on Taboola's request page. You can also use the industry opt-out pages of the Network Advertising Initiative and the Digital Advertising Alliance, and in Europe Your Online Choices, to turn off interest-based ads from the companies that take part.

6Service providers

These companies handle data for the site. Each keeps it under its own policies, which our code does not control, and some process it outside your country, including in the United States.

Services your browser contacts directly

  • Push services: if you turn on notifications, your browser's push service (for example Google for Chrome, Mozilla for Firefox, Apple for Safari, Microsoft for Edge) delivers them. Messages are encrypted for your browser; the service sees the push address, timing and size.
  • Wikidata: the star search on the request page sends your search term to wikidata.org (Wikimedia Foundation) straight from your browser, along with your IP address and browser details.
  • Other image hosts: most images come through our server, but some load directly from the site that hosts them, which then sees your IP address and browser details.

7How long we keep data

This is what the system does today. Where nothing deletes data automatically, we say so.

8Your choices and rights

9Your rights in the EEA, the UK and Switzerland

If you are in the European Economic Area, the United Kingdom or Switzerland, the GDPR (or the UK GDPR or the Swiss data protection act) applies to how we handle your data. starfeed.com is the controller; see Who we are.

Legal bases. We run and protect the site (server log, bot checks, abuse limits, anonymous page counts) and answer your emails on the basis of our legitimate interest in a working, secure site. The email digest and notifications rely on your consent, which you give when you confirm the sign-up or allow notifications. Fan Talk, ratings, contributions and plans for automated access are provided because you ask for them, and payment records are kept to meet tax obligations. Google Analytics, personalised ads from Google and its partners and personalised recommendations from Taboola rely on your consent.

Consent message. You see a consent message from Google (Privacy & messaging, a consent management platform certified under the IAB Transparency and Consent Framework). It names the partners, including Google and Taboola, and their purposes, and you can consent, refuse or choose per purpose and partner. Until you answer, Google Analytics and advertising cookies are not set and Taboola is not loaded. If you refuse, you can still read everything; Google may show non-personalised or limited ads, and Taboola recommendations based on the page only.

Withdraw or change your consent at any time with “Privacy settings” at the bottom of any page except this one. Withdrawing does not affect processing that took place before.

International transfers. We and the providers listed under Service providers may process data outside the EEA, the UK and Switzerland, including in the United States. Where the law requires it, these transfers rely on an adequacy decision (for example for companies certified under the EU-US Data Privacy Framework) or on standard contractual clauses offered by the provider.

10Your rights in US states (including California)

This section applies if you live in California or another US state with a consumer privacy law, and is our notice at collection. It covers the last 12 months.

Categories we collect: identifiers (IP address, cookie and device IDs, and your email address or push address if you subscribe), internet activity (pages viewed, referring pages, interactions with ads and recommendations), approximate location (country; Google estimates a city), commercial information if you buy a plan, what you post in Fan Talk, and interests you pick. Sources and purposes are described under What we process; retention under How long we keep data.

We do not sell personal information for money. Letting Google, its advertising partners and Taboola collect identifiers and browsing activity on our pages for personalised ads and recommendations may count as “selling” or “sharing” under California law, and as “targeted advertising” in other states. We do not knowingly sell or share the data of consumers under 16, and we do not use sensitive personal information to infer anything about you.

How to opt out: use “Do Not Sell or Share My Personal Information” at the bottom of any page except this one. Google also shows its own link for this in the states where its message applies; it records your choice for Google's ads and passes it to Taboola in the signal of its consent message. When you use our link, this browser stops loading Taboola, and where Google's confirmation form opens you can confirm the opt-out for Google too.

Global Privacy Control: where a US state privacy law applies, we treat a GPC signal from your browser as a request to opt out of sale and sharing. Taboola is then not loaded (also when we cannot tell whether such a law applies to you), and Google says it limits its ad processing for such requests in the states where the law requires it.

11Children

The email digest, Fan Talk and ratings are not intended for children under 14, and we do not knowingly collect their data. If you think a child under 14 has subscribed, posted or rated, tell us via starfeed.com@gmail.com and we will delete the record.

12Changes to this policy

When we change how starfeed.com handles data, we update this page and the date at the top.

All sections

Also

Language