Privacy policy
The GemSpace Chrome extension (called GemNews until November 2026, and GemCommunity News until October 2026), version 1.0.4 and later. Updated 2026-11-16.
What the extension does not do
- It does not read, change or track the websites you visit. It installs no content script, and the only site it has permission to contact is GemCommunity's own server, community.gemboss.ai. From version 1.21.0, if you connect your store, the Your store widget also asks GemBoss (admin.gemboss.ai) for that store's numbers, as described below.
- It does not collect your browsing history, location, contacts or the content of pages you visit.
- It has no ad code and no third-party analytics, and we do not sell data.
What it keeps on your device
In Chrome's extension storage (chrome.storage.local), on this device. From version 1.32.0 a few settings also follow your Chrome account: the last item says which.
- Latest briefing: A copy of the last feed, so a new tab shows text straight away.
- Session token: Only if you connect your account yourself. It tells the server which account is asking.
- Display choices: Light or dark, language, and the server address (community.gemboss.ai). From version 1.32.0, light or dark and language also follow your Chrome account (last item).
- Saved items: Items you star, up to 200. Each is a copy of the card: title, link, cover image address, date. The full text is kept only for pieces that are free for everyone.
- Rating prompt counters: How many new tabs you have opened, on how many days, the last day, and whether you answered or dismissed the prompt. These never leave your device. The prompt's button opens the extension's reviews page on the Chrome Web Store.
- Saved items sync: Connected accounts only, version 1.0.5 and later: which saved items are still waiting to be added to or removed from your account, and when they last synced.
- Welcome note: When you closed the short note shown after install, so it does not come back.
- Feedback form: Version 1.2.6 and later, in the new tab page's own storage (localStorage) rather than chrome.storage: a random ID made for this browser, so several answers from you count as one person; a note you started but did not send; and the score you gave last time. Version 1.23.0 and later: the 👍 or 👎 you gave each story (and whether you finished the answer, and when), so the story shows it when you open it again; for the newest 200 stories, never the reasons or words you wrote.
- Install ID: Version 1.4.0 and later: a random ID made for this install, and the last day each daily signal below was sent. It is not linked to your account.
- Live visitors ID: Version 1.17.0 and later: a random ID made only for the "live now" count (/api/ext/here below). It is separate from the install ID and is not linked to your account.
- Your interests: Version 1.6.4 and later: your answers to the four optional questions shown once (from version 1.9.1, on the third day you use GemSpace rather than right after install; before that, after install or after updating from a version before 1.6.4) (where you sell, how long you have been selling, monthly sales if you chose to say, the topics you want to follow, what you want most right now, and an optional one-line note), and whether you answered, skipped or have not seen them yet. They choose what the For you tab shows. Version 1.6.5 and later: with a connected account, answers saved on that account can be copied here.
- Install channel: Version 1.4.6 and later: a short label the space.gemboss.ai website hands over the first time it sees the extension: the share code on the link, the referrer group, or the utm parameters of the link that brought you to the website (for example "ref:google" or "utm:facebook/paid/vn"). Accepted once; no address, no identifier.
- Telegram follow: Version 1.6.7 and later: the follow code and Telegram link the Telegram card shows (kept up to 25 days), the language it was made for (once you follow, from version 1.6.9: the language the bot was last told, and when telling it last failed), whether you follow or sent /stop, until when the card is hidden after you press ×, the first day this version ran, and the last time the server said the feature is off.
- New since your last visit: Version 1.6.8 and later: when you last opened GemSpace, the last time a new tab was open, and the IDs of the new items you opened during this visit, so the home page can say what is new since your last visit. It never leaves your device.
- Public events: Version 1.8.0 and later: a copy of the public events list (Shopify webinars, meetups and conferences) in your display language, kept for up to an hour before it is fetched again, and which events or event cards you hid with × (the event ID and when you pressed it, or until when a card stays hidden). From version 1.32.0 the parts named in the last item also follow your Chrome account; the rest never leaves your device.
- Layout: Version 1.10.0 and later, on a computer: whether the left menu is open or collapsed, and for the right panel whether it is open or collapsed, which widgets you turned on, off or folded and their order (also copied to the new tab page's own storage, localStorage, so the page opens in that layout without jumping). From version 1.31.0, also the right panel's width if you drag its edge, in that same localStorage. From version 1.32.0, also whether you were last on News or on the Board (a new tab opens there again), and which new menu items you have opened (so their New label goes away). From version 1.32.0 the parts named in the last item also follow your Chrome account; the rest never leaves your device.
- Board: Version 1.26.0 and later, extension only: your Board (notes, checklists, the articles you pin, where each item sits, and each widget's settings) is kept in the extension's storage, and the images you add are kept in the browser's IndexedDB, both on this computer only. Nothing on the Board is sent anywhere.
- Widgets: Version 1.11.0 and later: the cities you chose for Market clocks, and the price and cost you typed into Break-even ROAS. Version 1.25.0 and later: the settings you saved for a widget (for example which numbers Your store shows, or the kinds of story in Latest stories); from 1.28.0 also what you put in your own widgets (the links in Quick links, the date in Your countdown). From version 1.32.0 the parts named in the last item also follow your Chrome account; the rest never leaves your device. The extension (not the website) also keeps a count per day of which side-panel widgets were shown and how many times each was clicked, with widget names and numbers only; that count is sent once with the next day's signal (/api/ext/ping below) and then deleted. The Ad lookup widget keeps nothing: the address you type only goes to the Meta Ad Library page you open.
- Competitors: Version 1.14.0 and later: when you last saw each followed store's changes (so new ones can be marked), and a copy of your list from the server, kept up to 10 minutes so a new tab shows it straight away.
- Update bar: Version 1.8.3 and later: when you press Update now, the positions of your open GemSpace tabs (tab and window numbers, kept for up to two minutes) so they can be reopened after the update, and the version you came from, so the next new tab can say what changed; if you press Later, which version and until when. It never leaves your device.
- Ask AI next: Version 1.22.0 and later: which AI assistant you picked under "Ask AI next" at the end of a story, so the next question opens in it straight away (Change clears it). It never leaves your device. When you click a question, your browser opens that assistant's site (ChatGPT, Claude, Google or Perplexity) with the question and a link to the story; GemSpace itself sends nothing.
- Your store: Version 1.21.0 and later, only if you connect your store: the read-only key GemBoss gave this extension for that store, the store's name and address, and a copy of its latest numbers so a new tab shows them straight away, replaced at each refresh and deleted when you disconnect. While you are connecting, a random code for each press of Connect: no longer accepted after 30 minutes, and removed the next time a new tab opens.
- Settings that follow your Chrome account: Version 1.32.0 and later: the right panel layout, widget settings (quick links, countdown, market clocks, ROAS), the left menu, light or dark, language, markets and the cards you closed are also copied to the Chrome sync storage for extensions, so your other computers signed in to the same Chrome account look the same. Google Chrome Sync carries them; GemSpace's server never receives them. Turn off Chrome sync for extensions, or use another Chrome profile, to keep them on one device. Saved items, the Board and the panel width stay as described above.
What it sends, and where
Every request goes to https://community.gemboss.ai, except the list of changes in a new version and the cover images (version 1.12.0 and later), which come from https://space.gemboss.ai, the Feedback form, which goes to https://feedback.gemboss.ai (the last two items), and the Your store widget, which reads from https://admin.gemboss.ai:
/api/ext/feed: Gets the briefing: every 30 minutes in the background, and when you open a new tab and the stored copy is more than 5 minutes old. The request can include your display language and, if you connected an account, your session token./api/ext/search?q=…: When you type two or more characters in the search box, the text you typed is sent so the server can search the whole community. This happens for guests and for connected accounts. The server does not save your search text in its database. The text is part of the web address, so it can appear in the request logs of our hosting provider./api/ext/saved: Version 1.0.5 and later, connected accounts only. Your saved items are stored on your account so they show up on your other computers. For each item the server keeps its ID, the card copy (title, subtitle, link, cover image address, label, dates) and when you saved it. It does not keep the article text. Guests' saved items stay on the device./api/ext/cover/…,/api/ext/me/avatar: Cover images for free Hot News pieces, and your own profile picture when you are connected./api/ext/views,/api/ext/views/read: Version 1.2.0 and later. When you open a piece in the extension's reader, the extension sends that piece's ID. If you scroll to the end and have been reading for at least 10 seconds, it sends that too. From version 1.2.5 it also sends the language the reader is showing (Vietnamese, English or Chinese). This is how the community counts how many people read each piece. If you connected an account, the read is linked to it through your session token. If not, the server makes a code from your IP address, browser and the date, using a secret key. The code changes every day and cannot be turned back into your IP address. If gems are on and you are signed in, a read of 45 seconds or more can also add a gem to your account; the extension sends nothing extra for this./api/ext/ping: Version 1.4.0 and later. At most once a day while Chrome is running with the extension on, and at most once a day when you open a new tab, the extension sends the random install ID above, which of those two signals it is (or "installed" / "updated" right after an install or update), the extension version, its interface language, and your browser's first language. From version 1.4.1 it also sends up to three of your browser's preferred languages. From version 1.4.6 it also sends the install channel above, if the website handed one over, so installs can be counted per channel; the signal that receives a channel is sent right away even if one was already sent that day. From version 1.11.0 it also sends, for one finished day, which side-panel widgets were shown and how many times each was clicked: widget names and counts only, never which article, store address or number you typed. The extension deletes that day's count once the server has it. The server also reads the browser name, its main version and the operating system from the request's user agent (for example Chrome 156 on Mac). This is how we count how many installs are in use and which languages they read in. It is the same whether or not you connected an account, and it is never linked to your account. A copy of the extension loaded from a folder on a computer (a GemBoss team test build, not an install from the Chrome Web Store) also sends a "test build" mark, so the server does not count it as a user; the extension reads its own install type with chrome.management.getSelf(), which needs no extra permission. An install from the store never sends this mark./api/ext/survey: Version 1.6.4 and later. Right after install (from version 1.9.1: on the third day you use GemSpace; for installs from before version 1.6.4: the first time you open a new tab after updating), the extension asks four optional questions, once, and once more a few days later if you skip them. When the questions open, after each question you answer, when you finish and when you skip, it sends the random install ID above, the extension version, its interface language, the state (shown, partly answered, finished or skipped), how many questions you answered, and your answers so far: the choices above and the optional note (up to 280 characters). No email, no name, no location, no cookie. Version 1.6.5 and later: if you connected a GemCommunity account, the request also carries your session token (as saved items do), so the answers are linked to that account; right after you connect, the extension sends one request so that the answers this browser sent before are linked too. While this browser has no finished answers, the extension asks the server for the answers saved on your account (right after you connect, then at most once a day); if there are some, it uses them and does not ask you again. Change your answers any time from the menu: Your interests./api/ext/bye: Version 1.4.0 and later. When you uninstall the extension, Chrome opens this address in a tab, with the install ID and the interface language. The server marks that install as uninstalled and shows a short page whose address does not contain the ID. For 30 minutes a cookie on that page holds the install ID, so the page can ask once why you removed it. If you answer, the server keeps your choice and anything you write (up to 500 characters) with that install./api/ext/feedback-identity: Version 1.2.9 and later, connected accounts only, and only when you send the Feedback form. The extension asks for a short code that names your account to GemBoss's feedback service. The code works once and expires after two minutes. Your session token is never sent to the feedback service./api/news/gifts: Version 1.6.0 and later. When you open a new tab, the extension asks whether a gift card is running today, sending only the display language. It sends no install ID, no token and nothing about you. If you hide the card, the date it hides until stays in your browser. The gift wheel itself runs on space.gemboss.ai, not in the extension./api/news/tg/code,/api/news/tg/status,/api/news/tg/lang: Version 1.6.7 and later. From the second day after install, a small card offers to follow GemSpace on Telegram. From version 1.7.1, the last screen of the welcome questions after install offers the same, with the same code, asked for when you reach the last question. From version 1.7.0, Telegram in the menu opens the guide page space.gemboss.ai/telegram (a page of the website, covered by its privacy page) in a new tab. The first time the card is about to show, the extension asks for a follow code, sending the display language and the random install ID above (no time zone); if you connected an account, also your session token (as saved items do), so the follow is linked to that account. The code is reused for up to 25 days, and a new one is asked for when you change the language before you follow. From version 1.6.9, once you follow, changing the language keeps the code and sends only the code and the new language (/api/news/tg/lang), so the bot writes in the language you chose; if that fails, it is sent again the next time a new tab opens. While the card (or that last screen) is open, every 6 seconds for at most 3 minutes each time it shows, the extension asks whether that code has been used to follow; that request carries only the code. The QR code is drawn on your device; the link is not sent to any QR service. Nothing is sent to Telegram until you scan the code or open the link yourself./api/news/public-events: Version 1.8.0 and later. Shortly after a new tab opens, and again when the copy on your device is more than an hour old, the extension asks for the list of upcoming public events (Shopify webinars, meetups and conferences, and GemCommunity's own events), sending only the display language. It sends no install ID, no token, no cookie and nothing about you. Event pictures are GemCommunity's own copies, loaded from community.gemboss.ai (or its image store on r2.dev), never from the organiser's site. Add to calendar builds the calendar file on your device; Google Calendar, Register and Subscribe in your calendar open Google, the organiser's page or your calendar app only when you press them./api/ext/audit: Version 1.19.0 and later. Only when you run Store audit in AI Workflows: the extension sends the store address you typed and your display language, without any account token or install ID. The server asks the audit service to read that store's public pages and returns the report; the extension then asks for the result every 2 seconds until it is ready, at most 4 minutes. Nothing is saved to an account, and the address is not linked to you./api/ext/watch: Version 1.14.0 and later. When you follow a competitor store in the Competitors widget, the extension sends its address with the random install ID above (and your session token if you connected an account, so the list follows your account). While the Competitors widget is on and showing in the open panel, the extension also asks for your list with the same ID, at most every 10 minutes; with the widget off or folded it asks nothing. The server keeps your list (up to 3 stores) and answers with what a shopper visiting those stores can see: whether a sale is running and its typical discount, and changes in the last 7 days (sale started or ended, price changes, new products, new landing pages, new ads). The server passes on only the store address, to check that store's public pages and the Meta Ad Library. An address it refuses (a marketplace, a private or wholesale area, not a store) is not kept. When you connect an account, this install's list moves into it: a store the account already follows is merged, and stores over the limit are removed. You can stop following a store at any time, even when the feature is switched off. Stores you stop following, and the list of an install that was uninstalled, are deleted after 30 days; deleting your account deletes its list. Since 15 November 2026, only when you use the Assistant, its read pass (see /api/ext/assistant-token below) can read this same list and these same answers; reading never changes the list./api/ext/here: Version 1.17.0 and later, and on space.gemboss.ai. While a GemSpace tab is visible on your screen, it sends the live visitors ID above every 15 seconds, and again when the tab comes back into view; a hidden tab sends nothing. When the tab is hidden or closed, it sends that ID once more with a note that you left, so you stop being counted right away. Each request also carries a random tab ID that lives only in the memory of that tab, so leaving one GemSpace tab does not remove a device that still has another one open. Nothing else: no token, no cookie, no install ID. The server keeps, in memory only and for 45 seconds, that ID and the IP address the request came from (to count at most 10 devices per address, so the number cannot be pumped up), then forgets both. It answers with how many people are here right now: devices with GemSpace open plus people with the GemCommunity app open. It writes nothing to its database./api/news/tg/remind,/api/news/tg/reminders: Version 1.8.2 and later. Events with a start time more than an hour away have a Remind me on Telegram button. If you follow GemSpace on Telegram, pressing it sends only your follow code and that event's ID, and the GemCommunity bot messages you once, 1 hour before the event starts; Undo sends the same two things to cancel it. The first time a page shows such a button while you follow, the extension asks once which events already have a reminder, sending only the follow code. If you do not follow yet, the Telegram card opens first; once you follow, the reminder is sent the same way. No install ID, no token, no cookie, and nothing new is stored on your device.admin.gemboss.ai/api/ext/glance: Version 1.21.0 and later, only if you connect your store in the Your store widget. Pressing Connect opens admin.gemboss.ai/ext/connect, where you sign in to GemBoss and press Connect GemSpace; GemBoss then gives the extension a read-only key for that one store, valid for 90 days. While the Your store widget is on and showing in the open panel, the extension sends that key to this address, at most every 5 minutes; with the widget off or folded it asks nothing. It sends no install ID, no community token and nothing about your browsing. GemBoss answers with the store's name, currency and time zone and, for today, yesterday until the same time and the 7 days before: sales, orders and average order value from the store's Shopify orders, and visits and conversion rate counted by GemBoss; or, if the store granted GemBoss its Shopify Analytics, all of them from Shopify Analytics. The key reads nothing else and cannot change anything. Disconnect sends the key once more, to revoke it. Ask Claude in the widget opens claude.ai in a new tab with a question that already holds the numbers the widget shows (in the link); Claude, run by Anthropic, receives them only if you press Send there, under your own Claude account./api/ext/assistant-token: Version 1.30.0 and later, only when you use the Assistant in the side panel. When you send a question, the extension asks for a 30-minute read pass with the random install ID above (and your session token if you connected an account, so the assistant reads what your account can read). It then sends your question, the earlier questions and answers of this chat, today's date, your time zone and your reading language, with that pass, to the bridge you started on your own computer (127.0.0.1, port 8792). The bridge runs your own Claude Code or Codex, which uses the pass to read GemCommunity News (lists of stories, search, single stories) and, since 15 November 2026, the competitor stores you follow in the Competitors widget, with what the widget already shows you about them (sale, typical discount, changes in the last 7 days). It reads nothing else. It sends your question, and what it read with the pass (so your list of competitors too, when it reads it), to Anthropic or OpenAI under your own account and its terms. GemSpace does not receive your questions or the answers, keeps no chat, and uses no AI key of its own. The server keeps nothing about a pass; it expires by itself.claude.ai,chatgpt.com: Version 1.27.0 and later, only when you press Ask in Claude or Ask in ChatGPT in the side panel's Assistant. The extension opens that site in a new tab with your question in the link, together with the numbers the Your store widget shows (if you connected a store) and the titles and links of the newest stories. Claude (run by Anthropic) receives them only if you press Send there; ChatGPT (run by OpenAI) sends the question as soon as the page opens. Either one runs under your own account. GemSpace keeps nothing of it.space.gemboss.ai/changelog.json: Version 1.8.3 and later. Only while Chrome has downloaded a new version that is not applied yet, the update bar fetches the public list of changes, so it can show what the new version brings and whether it asks for any new access. A plain request with nothing of yours: no install ID, no token, no cookie.space.gemboss.ai/img: Version 1.12.0 and later. Cover images of articles and events load as small copies from here instead of the full-size originals. The request names only the public image (its address and a width); it carries nothing of yours beyond what any web request does (your IP address and browser), and nothing is stored about it.feedback.gemboss.ai: Version 1.2.6 and later. Each time you open a new tab, the extension loads the Feedback form's steps from here; that request carries nothing of yours beyond what any web request does (your IP address and browser), and nothing is stored for it. Your answer goes only when you press Send. It sends your answers (the score and what you wrote), the random browser ID above, the page and language, whether you were in the extension or on the website, and the short web name (slug) of the piece you had open. From version 1.2.9 it also sends the version, the tab, more about that piece (its ID, kind, title and link, and the ID of that read), and 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. With every request comes your browser's user agent (the browser and system name and version); from 2026-10-09 the feedback service stores it with the answer, so the team can reproduce a problem you report. From version 1.2.9, if you connected an account, the short code above goes with it, so the team sees your name, email, account ID and membership status next to your answer. Without a connected account the answer has no name. Version 1.23.0 and later: at the end of a story, "Was this helpful?" with 👍 and 👎. Its steps load from here when you near the end of a story (a request that carries nothing of yours beyond what any web request does). One tap sends your choice straight away; after a 👎 you can pick what was missing and write what you want to know, sent when you press Send. It goes with the same details as a Feedback answer (the random browser code, the story's short web name, ID, type, title and link, the version, what the browser says about itself and, with a connected account, the short account code). The service keeps one answer per browser per story: changing your choice replaces it.
Images. Cover images are stored on Cloudflare R2 and load from addresses ending in r2.dev. An article or a profile picture can also point to an image on another website; your browser then loads it from there. As with any image on the web, the site serving it sees your IP address. On 2026-09-27 every cover in the feed was on r2.dev and no article in the feed contained other images.
Links. When you click a source (for example a post on X) it opens in a normal tab, and that website's own privacy policy applies. Links into the community carry your chosen language. Version 1.2.4 and later: links the extension makes to the space.gemboss.ai website carry a short channel tag. That is a piece you share (for example ?via=wa for WhatsApp), the "Open web version" link (?via=ext) and the "Open on phone" QR code (?via=qr). The website uses the tag to count, anonymously, how many of those links are opened per channel. A shared members-only piece links to the community site and carries no tag. Apart from the daily install signal and the survey answers described above, the extension sends no counting data; the code that sends the website counts exists only on the website.
What the server keeps
- For a connected install: A SHA-256 hash of the session token (never the token itself), the extension ID, when it was connected and when it was last used.
- Saved items: As described above, for connected accounts on 1.0.5 and later.
- Reads: Version 1.2.0 and later. For each read in the extension: which piece, when, whether you reached the end, the reader language (from 1.2.5), and either your account (if connected) or the one-day code described above. Community admins see totals per piece, not who read what.
- Installs: Version 1.4.0 and later. For each install ID: when it was first and last seen, the last day a new tab was opened, which days it sent a signal, the version, the interface and browser languages, the browser name, main version and operating system, the install channel if the website handed one over (version 1.4.6 and later), the day Chrome reported it uninstalled, and why, if you answered. No account or IP address is stored with it. If a GemBoss team member marks their own browser as a team install, the server stores that mark too. A test build (loaded from a folder, or running in an automated Chrome without a window) is stored with a "test build" mark and counted as a team install. Admins see totals only.
- Survey answers: Version 1.6.4 and later. For each install ID that saw the questions: the latest answers, how far you got and when, linked to the install. Version 1.6.5 and later: if you connected an account, they are also linked to that account, and admins see your account name and email next to the answers. Without an account, admins see the answers with no name or email. Team installs are left out of the totals.
- Telegram follow: Version 1.6.7 and later. For each follow code: the language, install ID and account (if connected) it was made with, and, once you start the GemCommunity bot in Telegram with it, your Telegram chat so the bot can send each new article as 3 insights and a link. Send /stop in Telegram and the bot sends nothing more. The bot writes in the language of your follow: from version 1.6.9 it changes when you change the language in GemSpace, or in your GemCommunity account if the follow is linked to that account; the latest change wins.
- Event reminders: Version 1.8.2 and later. For each reminder you set: which follow it belongs to, the event ID, when to send it (1 hour before the start) and when it was sent. Nothing else. Undo, or Stop event reminders in Telegram, removes reminders not yet sent.
- Your store key (GemBoss): Version 1.21.0 and later. GemBoss keeps a SHA-256 hash of the key (never the key itself), which store it reads, the GemBoss account that connected it, when it was last used and when it expires. Disconnect revokes it; it ends by itself after 90 days.
- IP addresses: Used to count requests for rate limiting (kept in memory for a few minutes, not written to our database) and, for reads without a connected account, to make the one-day code above. The IP address itself is not stored. Our hosting provider may log IP addresses as part of normal request logs.
- Feedback (feedback.gemboss.ai): Each answer with the details listed above. Your IP address is kept only as a code made with a secret key, used to limit how many answers one address can send in an hour and cleared after that hour. If the same GemCommunity account has also signed in to GemFeedback, the answer is linked to that GemFeedback account. Only the GemBoss team can read 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), which sees the answers and the account name, not the email. The short account code is not stored on community.gemboss.ai; the feedback service keeps its ID so it cannot be used twice. To have your answers deleted, email the address below.
What websites can send to the extension
Chrome blocks every site except three. community.gemboss.ai sends two things: the session token, when you click "Connect account" on the connect page, and the language you picked on the site, so the extension matches it. From version 1.2.1, the website can only ask whether the extension is installed: news.gemboss.ai and gemnews.ops.gemboss.ai, and from version 1.32.0 also its new names space.gemboss.ai and gemspace.ops.gemboss.ai. The extension answers yes and its version number, and refuses anything else from those addresses. The website counts that answer anonymously, once per browser. From version 1.4.6, those addresses can also hand over the install channel (the short label described above); the extension accepts it only once, when it has none yet, and still refuses anything else. From version 1.4.1, community.gemboss.ai can also ask for the install ID described above. Only a page for the GemBoss team asks, so team members can mark their own browsers and keep them out of the counts. From version 1.21.0, admin.gemboss.ai can send one thing: the read-only key for your store, when you press Connect GemSpace on its connect page after pressing Connect in the Your store widget. The extension accepts it only from that page and only while the Connect you pressed is still waiting (up to 30 minutes), and refuses anything else from that address.
How to stop it and delete your data
- Disconnect: In the extension's options page, click Disconnect. The token is deleted from your device. Saved items on your account stay until you remove them.
- Revoke from the server: Open the list of connected installs and revoke them one by one.
- Remove saved items from your account: While connected, remove the star from an item and the removal syncs to your account. To delete all of it at once, email chris.chimen@gmail.com.
- Disconnect your store: In the Your store widget, press Disconnect. The key and the copy of your numbers are deleted from your device, and the key is revoked at GemBoss.
- Uninstall: Chrome deletes everything the extension stored on your device, and opens a short page that marks the install as uninstalled. Anything on the server (token record, saved items, install record, survey answers) stays until you revoke it, remove it, or ask us to delete it.
About the content
Hot News is written by AI from public posts and news sources and reviewed by an editor. If a piece quotes you, uses your image or names you and you want it removed or corrected, see content removal and corrections.
Contact
Questions about this policy or your data: email chris.chimen@gmail.com.