← Back to the briefing

Privacy

The news.gemboss.ai website (GemNews). Updated 2026-11-13.

What the website sends and receives

Anonymous counts

The events below are sent to the community server (community.gemboss.ai). Each event holds only these fields:

e
The event name (table below).
page
The page type: the briefing, a story, or the extension install page; not the page address.
dev
Phone or computer.
lang
The language the page is showing.
tz
Your browser time zone, so the server can infer the country. The time zone is not stored.
via
The channel of a shared link (for example WhatsApp), or the channel you pick in the share dialog.
ref
Only on page opens: the referral source group (for example Google or ChatGPT). The previous page address is not sent.
item
Only on prompt copies and Ask AI clicks: which story (its type and number). The prompt and question text are not sent.
pos
Only on Ask AI clicks: which question in the list (1 to 5).
ai
Only on Ask AI clicks: the assistant you picked (ChatGPT, Claude, Google AI Mode, Perplexity) or copying the question.
mode
Only on extension install invites and the discuss button: where the invite showed, which button was pressed, or whether discuss was clicked in the bottom bar or at the end of the story.

The events:

visit
Opening the briefing, a story, or the extension install page (other pages, such as the archive or this one, send nothing)
invite_shown
An extension install invite is shown
invite_click
Clicking a button in the install invite
installed_seen
The first time this browser sees the extension is installed
share_open
Opening the share dialog
share_pick
Picking a share channel
qr_show
Opening the QR code to read on a phone
connect_start
Pressing sign in
connect_done
Finishing sign in
discuss_click
Clicking "Discuss in GemCommunity" on a story
ext_cta
Clicking an "Add to Chrome" button on the extension install page, with which part of the page the button is in
prompt_copy
Pressing "Copy" on an AI prompt in a story
ask
Clicking a question under "Ask AI next" at the end of a story to open it in an AI assistant (or copy it)
tg_card_show
The "Follow GemNews on Telegram" card is shown
tg_card_hide
Pressing × to hide the Telegram card for 5 days
tg_menu
Pressing "Telegram" in the account menu (opens the Telegram page)
tg_open_link
Pressing the link that opens Telegram on the card or the Telegram page
tg_followed
The card or the Telegram page sees you just followed on Telegram

The server turns the time zone into a country code and drops the time zone, then only adds one to that day's counter for exactly the fields above: no cookies, no IP address or browser identification string stored, nothing tied to an account, so the counts cannot be joined into one person's journey. Your IP address is kept in the server's memory to limit floods: it is never written to disk or a database, and it is gone when the server restarts. The hosting provider may log it in ordinary request logs.

Google Analytics

Our server sends each event above to Google Analytics (Google LLC) for reporting. Every event carries its own random number that Google requires; events are grouped by minute, sent in shuffled order, and carry only the start of that minute as their time. So Google gets no ID that joins the events to each other or to you. Google receives the event name and the fields above, except the time zone: it gets the country code the server inferred instead. The sending happens from our server: the page has no Google Analytics code, sets no Google Analytics cookies, and Google does not receive your IP address through this.

Story reads

When you open a story in the reader, the website sends that story's ID and the language the reader is showing (Vietnamese, English or Chinese) to the community; if you reach the end, it sends that too. The server stores each read as a timestamped row. If you connected an account, the row is linked to it: that is your reading history in the community. If not, it is linked to a code made from your IP address, browser and the date with a secret key: the code changes every day and cannot be turned back into your IP, but reads on the same day share a code. To delete reading history linked to your account, email the address under Contact.

Feedback

When you send the Feedback form (bottom right), your answer goes to GemBoss's feedback service at feedback.gemboss.ai: the score and what you wrote, the random browser code (gfw:respondent, below), the page and language, whether you were on the website or in the extension and its version, and the tab and story you had open (its ID, title and link, and the ID of that read). Your browser's user agent (browser and system name and version) comes with the request; the feedback service stores it with the answer, along with what the browser says about itself (its brand and platform, whether it is a phone, touch points, window and screen size, pixel ratio and time zone), so the team can reproduce a problem you report. If you connected an account, the website first asks community.gemboss.ai for a short code that names your account (it works once, for two minutes; your token is never sent to the feedback service), so the team sees your name and email next to your answer, with your account ID and membership status; if the same account has signed in to GemFeedback, the answer is linked to it there. Without a connected account the answer has no name. Your IP address is kept only as a code made with a secret key, to limit how many answers one address can send in an hour, and cleared after that hour. Only the GemBoss team reads answers; the team may ask an AI assistant to read and sum them up (Anthropic's Claude, or OpenAI's GPT when Claude is unavailable), and it sees the answers and the account name, not the email. To have your answers deleted, email the address under Contact. At the end of each story, "Was this helpful?" with 👍 and 👎 (loaded from the same service when you near the end of the story): one tap sends your choice straight away to the same service; after a 👎 you can pick what was missing and write what you want to know, sent when you press Send. It carries the same details as above (the browser code, the story you are reading, what the browser says about itself, the short account code if you connected one). The service keeps one answer per browser per story: changing your choice replaces it.

Stored in your browser

In your browser, on this device only (localStorage unless marked sessionStorage):

gcn:gcn.token
A session token, only if you connect an account.
gcn:gcn.feed
The last briefing fetched, so the page shows text at once; if you connected an account it includes your name and member-only parts.
gcn:gcn.theme
Light or dark theme.
gcn:gcn.lang
The language you picked.
gcn:gcn.rate
How many times and on how many days you opened it (for the extension rating prompt; the website does not show that prompt).
gcn:gcn.saved
Stories you starred, up to 200.
gcn:gcn.savedSync
The sync state of saved stories with your account.
gcn:gcn.welcomed
When you closed the welcome note shown after install (if any).
gcn:gcn.invite
Whether you clicked or postponed the extension install invite.
gcn:gcn.markets
The markets you picked in Holidays (US, UK, EU, Australia, Asia).
gcn:gcn.holidayHide
Which holiday cards you closed and at which step, so each shows again only at the next step.
gcn:gcn.here
A random ID used only for the live-now count (see what is sent). It is separate from every other ID and not linked to your account.
gcn:gcn.giftHide
Which gift cards you hid and until when, so each shows again only after that date.
gcn:gems.device
When gems are on and you are signed in: a random key for this browser, sent with your spins and finished reads so one device cannot earn gems for more than 2 accounts. The server keeps only a hash; your gems are not stored here.
gcn:gift.open
When you sign in from the gift wheel (sessionStorage): reopen the wheel when you come back.
gcn:gcn.extInstalled
Whether this browser has the extension (yes/no), so the extension page shows the right button from the first frame.
gcn:gcn.seenInstalled
Whether this browser was already reported as having the extension (yes/no).
gcn:gcn.src
The channel that first brought you to the website (the share code on the link, the referrer group, or the link's utm parameters), when, and whether it was handed to the extension. No address, no identifier.
gcn:connect.state
During sign in (sessionStorage, cleared when the tab closes): a code that blocks forged sign-ins.
gcn:connect.back
During sign in (sessionStorage): the page to return to.
gfw:respondent
The Feedback button: a random code for this browser, sent with your feedback so two answers from one person count as one person. If you connected an account, your feedback also carries your account name (see Feedback).
gfw:draft:gemnews-content
The Feedback button: what you have filled in so far, so closing and reopening keeps it; removed when you press Send. Sent (to feedback.gemboss.ai) only when you press Send.
gfw:inline:gemnews-article-helpful
The "Was this helpful?" row at the end of a story: the 👍 or 👎 you gave each story (and whether you finished the answer, and when), so it shows when you open the story again. The newest 200 stories; never the reasons or words you wrote.
gfw:last:gemnews-content
The Feedback button: the stars you gave last time, so next time it opens at the comment box (you can still go back and re-rate).
gcn:gcn.tg
The Telegram card and page: the follow code and Telegram link in use (kept up to 25 days), the code's language (once you follow: the language the bot was last told, and when telling it last failed), whether you follow or stopped, until when the card is hidden, the first day the page ran this feature, and the last time the server said the feature is off.
gcn:ext.cta
On the extension install page (sessionStorage), only when the page reloads itself to switch language: the install button you just clicked, so that click is counted once on the new page.
gcn:connect.done
After sign in (sessionStorage): a marker so "finished sign in" is counted once.
gcn:gcn.pubEvents
A copy of the public events list (in the language shown), kept for up to an hour before it is fetched again.
gcn:gcn.peHide
Which events or event cards you hid with × (the event ID and when you pressed it, or until when a card stays hidden). It stays in this browser.
gcn:gcn.since
"New since your last visit": when you last visited, the last time the page was open, and the IDs of the new stories you opened during this visit. It stays in this browser and is never sent anywhere.
gcn:gcn.rail
On a computer: whether the left menu is open or collapsed.
gcn:gcn.panel
On a computer: whether the right panel is open or collapsed, which widgets you turned on, off or folded, and the order you set. It stays in this browser.
gcn:gcn.sideCls
A copy of the two choices above (left menu, right panel), so the page opens in the right layout without jumping.
gcn:gcn.sideW
On a computer: the right panel's width, if you dragged its edge. Only in this browser.
gcn:gcn.wset
The settings you saved for each side-panel widget (for example Latest stories: the kinds of story and how many), and what you put in your own widgets (the links in Quick links, the date in Your countdown). Only in this browser.
gcn:gcn.clocks
Market clocks widget: the cities you chose. Only in this browser.
gcn:gcn.roas
Break-even ROAS widget: the price and cost you typed. Only in this browser.
gcn:gcn.askAi
"Ask AI next" at the end of a story: the assistant you picked last time, so the next question opens in it straight away (Change clears it). Only in this browser.

Beyond what the sections above describe (sending, counting, reads, feedback, sign in), none of this leaves your browser. Clearing this site's data in your browser removes all of it.

Sign in

Connecting your GemCommunity account stores a token in this browser. Signing out from the account menu revokes that token on the server.

Chrome extension

The GemNews extension has its own policy at news.gemboss.ai/ext/privacy.

Contact

Questions about this page or your data, or requests to delete data: email chris.chimen@gmail.com.