Privacy policy
For the Wordleverse Chrome extension and the Wordleverse / Qorble APIs it uses. Effective November 13, 2026.
What this covers
This policy describes data the extension keeps in your browser and data it sends to the Wordleverse or Qorble site you connect to. It does not replace the privacy practices of the game websites you visit, or of your browser.
What is collected
In your browser, the extension stores:
- The API token from Connect (or a short-lived, results-only guest token if you are not signed in), plus basic token metadata such as type and expiry.
- A random device identifier, used only so “browser sign-in” can name and replace the token for this installation.
- Which Wordleverse or Qorble site you chose in Settings, and whether you prefer the queue bar minimized.
- Temporary queue and bar state for the current browser session.
When you use the extension, it may send the following to the Wordleverse or Qorble site you chose:
- Authentication. Connect and sign-in exchange a token with our servers. We store a hash of the token, not the secret itself.
- Results you choose to save. On supported game sites the extension can detect official share or result text and asks before saving it. If you confirm, it sends the result text, the game, the date, your time zone, the site’s host name, and that the source was the extension. The full page URL is included in that request so the game can be identified; the stored result keeps the host name, not the full URL.
- Tab URLs. If you open the bar on a page, the extension looks that tab’s URL up against the catalog so it can show the right game (or a submit form). That lookup is a request to our API; the URL is not saved as a result.
- Guest identity. If you use the extension without an account, we attach the activity to a guest record for this browser (a cookie on our site and/or a guest token in the extension).
- Staff screenshots (optional, staff accounts only). A signed-in staff account can capture the visible tab and upload the image as a screenshot for a game. Those images are then shown on the public game page until staff remove them.
- Abuse-detection records. When a result is saved, we also record the request’s IP address, a coarse browser and operating-system family, and the game, for a short period, so the site owner can investigate abuse. These records are not used to identify or merge people automatically, and they are not shown on the public site.
The extension does not include a third-party analytics or advertising SDK. Favorites, ratings, and “done” marks are sent only if you connect with a signed-in account and use those bar actions.
Where it is stored
Tokens, the device identifier, and bar preferences live in your browser (the token is stored locally on this device; your site choice is saved in the browser’s synced extension settings, which may follow your browser account if you have that turned on).
Results, tokens (as hashes), guest records, and account data are stored on the Wordleverse or Qorble servers for the site you connected to. Staff screenshots are stored with the game’s public media.
How long we keep it
- Guest API tokens expire after 7 days. The extension can refresh a still-valid guest token, which starts that window again.
- Guest records (and their results, ratings, and favorites) last 180 days from last activity if you do not sign in. After that they are deleted. If you sign in, those results move to your account and the guest record is closed.
- Signed-in results stay with your account until the account is deleted. There is not currently a separate control to delete one saved result.
- Personal API tokens stay until you disconnect, revoke the token in Settings, or delete your account. They do not expire on their own.
- Abuse-detection records are removed after 30 days.
- Staff screenshots remain on the public game page until a staff member deletes them.
Sharing
We do not sell this data. The extension talks only to the Wordleverse or Qorble site you selected in Settings, not to other companies’ APIs. Game sites you play on have their own policies; the extension reads share text on those pages only to offer to save a result with you, and it does not send your result to those sites.
If a staff member uploads a screenshot, that image is published on the game’s page on Wordleverse, where anyone can see it.
Permissions, and why
- Identity — the Connect flow (signing in or connecting as a guest).
- Storage — to keep your token, site choice, and bar preferences.
- Tabs, scripting, and web navigation — to show the queue bar, follow a game site if it redirects, look up the current tab, and (for staff) capture the visible tab.
- Active tab — to work with the tab you are using when you click the extension.
- Access to Wordleverse / Qorble sites and a short list of supported game sites — so Connect, the bar, and result saving can run there without asking every time.
- Optional access to all sites — only if you allow it, so the queue bar can appear on other game sites you open from a Wordleverse queue, or so you can point Settings at a custom site. The extension still only injects the bar in a tab started from a Wordleverse queue, and only on that game’s site.
Your choices
- Connect or use the extension as a guest; you can sign in later so guest results move to your account.
- The extension asks before saving a detected result.
- Disconnect from the extension toolbar, or revoke the token under Settings.
- You can decline or later remove the optional “all sites” permission in the extension’s Settings or in Chrome’s extension details.
- You can delete your Wordleverse account, which removes that account’s results and API tokens. Submitted games stay in the catalog with the credit marked as a deleted user.
Contact
Questions about this policy or a request about your data: [email protected].
If we change this policy we will update this page and the effective date.