Wyrd — Privacy Policy

Last updated: September 2026 (version 1.0)

Wyrd is a Chrome extension that lets you type your own keywords in the address bar to open or search websites. This page explains what it stores, where, and what it never does.

The short version

Wyrd has no server and no accounts. It does not send your data to the developer, it contains no analytics or tracking, and it loads no code from the internet. Everything it stores stays inside your own browser, with three exceptions that you control: a token you entered for a shared list is sent to that list's host when the list is read or added to, a shortcut you choose to add to a shared list goes to that list, and — only if you set up the optional AI helper — a text you have read and chosen to send goes to the AI provider you configured.

Wyrd makes network requests in exactly four situations, and all four start with something you chose to do:

Reading a shared list you previewed or subscribed to. Wyrd downloads that list from the address you gave it.
Adding, changing, removing or categorising shortcuts in a shared list kept on GitHub, when you ask for that and have given Wyrd a GitHub token that may write to it.
Sending the "Copy for an AI" text to an AI provider you set up yourself, when you press Send in that box. Off by default; nothing is sent until you have configured a provider and pressed Send.
Looking up a word with Define, if you unlocked Define & translate: the one word you selected is sent to the Free Dictionary API (api.dictionaryapi.dev) to fetch its entry. Translations are made by Chrome on your computer and are not sent anywhere.

Reading a starter pack you asked for is the first kind: one download of the pack's address, like previewing a list.

If you never preview or subscribe to a shared list and never set up the AI helper, Wyrd makes no network requests at all. The details are in "Shared lists and the network" and "The AI helper" below.

What Wyrd stores, and where

Synced through your own Chrome sync (if you have Chrome sync turned on):

your shortcuts (each keyword and the link or links it opens). A suggestion you Add becomes an ordinary shortcut, so it is synced like any other.
your fallback-search setting, and your naming setting if you made one (the pattern and the prefix rules Wyrd uses to propose keywords)
which view of the manager you chose — Personal, Family & Friends or Teams. It is a display preference stored with those settings: it only decides how much the manager page shows and offers. It changes nothing about what is stored, sent or routed, and switching never deletes anything.
what a click on the toolbar icon does — show the box that saves the page in front, or open the manager or the directory (settings.iconClick, a display preference stored with the same settings; earlier test builds used settings.iconOpens).
whether the manager and the directory follow the system colours or are light or dark (settings.theme, a display preference stored with the same settings).
your shared-list subscriptions, in the order you gave them: for each one the address you pasted, the namespace, the name you gave it, the kind of list, which way of signing in you chose (browser sign-in, token, or none) and a random id. Not the list's contents and never a token. Note that some list addresses are themselves secret (for example a Google Sheets "Publish to the web" link); such an address is synced like the rest.
a random private token that lets Wyrd recognise requests coming from your own address bar when you use it without the > prefix. It is synced because Chrome syncs your search-engine entries, and the entry you create for Wyrd contains this token, so the token has to follow it to your other computers. It never leaves your own Chrome sync.

These are kept in Chrome's sync storage, which Google provides as part of Chrome and ties to your Google account so your shortcuts appear on your other computers. Google's handling of Chrome sync data is covered by Google's own privacy policy. The developer of Wyrd has no access to it.

On this computer only (never synced):

usage counts: for each keyword, an all-time total, the date it was last used and a count per day. Only the keyword is counted — never what you typed after it, and never the pages you visited. Per-day counts older than a year are dropped automatically, and deleting a shortcut deletes its counts.
automatic backups: full copies of your shortcut list (the last 20)
the change history of your shortcut list (the last 1000 changes), which keeps the previous address of a keyword you changed or deleted, and which the history view (> dance/history) shows
the history of your shared lists as this computer saw it (listHistory, the last 1000 changes): for each change a refresh brought, the list, the keyword and its old and new address. A list you unsubscribe from, or lose access to, takes its entries with it. A list kept in a Google Form sheet also brings its own past (the earlier answers in the sheet); that is kept with the list's downloaded contents and deleted with them
which target the toolbar box saved to last (popupTarget: "my shortcuts" or a list's random id)
page titles shown next to your shortcuts in the manager: the title Wyrd looked up for the address (Look up titles), or the title of a suggestion you Add. The Suggest button reads a stored title to shape the proposed keyword; it never stores one
the Ignored list: for each suggestion you chose not to see again, the address of the site or page, the keyword that was proposed and the date
whether Show details is switched on in the manager
the categories you gave your own shortcuts (categories: keyword → category, for example HR/Pay). A category is a label that groups a shortcut in the directory; it is kept on this computer only, follows a rename of the keyword and is deleted with the shortcut. It is not part of an export or a backup.
the directory's display preference (homePrefs): which category groups you closed. Apart from categories you apply there from "Copy for an AI" (the item above) and the Appearance setting it shares with the manager (in the synced settings, above), that is the only thing the directory ever writes (see "The directory" below).
for each shared list you subscribed to: the shortcuts, descriptions, categories (with the order and the short descriptions of categories the list declares), name, "contribute" link, naming rules, the namespace the list recommends for itself, and the title and intro line it gives the directory, as last downloaded from it, the address they were read from, when it was last read and checked, its status and status message, since when it has been refused (if it is), and notes about entries that were skipped
"what changed" notes: on every refresh, also while the manager is closed, Wyrd records which keywords of a list were added, changed (with the previous link) or removed. A note is kept until you dismiss it or remove the list, and is deleted if the list's shortcuts are removed because access was withdrawn. The very first read of a list produces no note.
tokens you entered for shared lists. A token is stored unencrypted in the browser's local extension storage on this computer, together with the exact list address it was entered for; it is protected the same way as the rest of your Chrome profile, and no better. It is never synced, never included in an export or a backup, never written to a log, and never shown again after you enter it. Wyrd uses a token only for the address it was entered for: after an address change, and once after updating from an earlier build that stored tokens without their address, the token is discarded and has to be entered again.
the AI helper's settings, if you set it up (aiKey): the provider, the base address, the model name and the API key you typed. The key is stored unencrypted in the browser's local extension storage on this computer, like a list token: never synced, never in an export or a backup, never written to a log, never shown again (the manager only tells you that a key is saved), and sent only in the request header of the one request described under "The AI helper" below. Remove in that card deletes all four values.

Because backups are full copies and the change history keeps previous addresses, both can still contain a shortcut you have since deleted, until it is pushed out by newer entries or you clear them (see "Deleting your data").

Browsing history (optional)

Wyrd does not have access to your browsing history unless you grant it. Chrome asks for that permission only when you click Scan my history or Look up titles in the manager.

When granted, Wyrd reads this browser's history on your computer, inside the extension's own page, for two purposes:

Suggestions. When you click Scan my history, Wyrd reads up to the last 60 days of history to propose shortcuts for sites and searches you repeat. Scan results are held in memory and are gone when you close the page.
Page titles. To show a page title next to a shortcut, Wyrd searches all of the history this browser has kept, but only for the sites your existing shortcuts point to. This runs when you click Look up titles, and also without a click each time you switch Show details on while history access is granted.

The history is never transmitted anywhere. The only things saved are the page titles and the Ignored list described above, and any suggestion you explicitly Add, which becomes an ordinary (synced) shortcut.

You can withdraw the permission at any time with Remove history access in the manager, which also offers to delete the saved page titles and the Ignored list.

Shared lists and the network (optional)

A shared list is a file of keywords and links kept by someone else — a Google Sheet, a file in a GitHub repository, or a file at any https:// address. Wyrd has no server of its own; it reads the file directly from wherever it is kept. Nothing described in this section happens unless you press Preview for a list or subscribe to one.

1. Reading a list you subscribed to

What is sent: one GET request to the address you subscribed to. For a GitHub file or a Google Sheet this is the matching download address of that same file (GitHub's raw file or its API; Google's CSV export of that one tab).
When: when you press Preview or subscribe; when a subscription of yours arrives on this computer through Chrome sync; every 6 hours while Chrome is running; when the browser starts; when you press Refresh in the manager; once, about an hour after a list was first refused; and right after a commit you made to a GitHub list from Wyrd. Renaming or reordering a subscription makes no request. (The address and the sign-in method of a subscription cannot be edited; you remove it and subscribe again.)
Always https. Other addresses are refused, http://localhost included. Requests are sent without a Referer, and each waits at most 10 seconds.
More than one GET in one case: when a GitHub file is read with a token and GitHub answers "not found", Wyrd asks again — up to 3 GETs in all — because in an address a branch name that contains / cannot be told apart from a folder.
What goes with it, depending on what you chose for that list:
- browser sign-in — the sign-in (cookies) your browser already has for that host, as if you had opened the address in a tab;
- token — an Authorization header containing the token you entered, sent to that list's host only, with no cookies; redirects are not followed, so the token cannot be passed on to another site;
- none — no cookies and no token.
And nothing else. No request body, no parameters added by Wyrd, and never your shortcuts, your browsing history, your usage counts, or any identifier made by Wyrd. The random token of the no-prefix mode is never part of these requests.
What the host sees: the host of the list (for example Google, GitHub or your company's server) receives the request as it would for any web page: your IP address, the time, the headers a browser normally sends (such as the browser version and language; they can also show that the request comes from the Wyrd extension), and your sign-in or token if you chose to use one. It can therefore tell that you, or someone at your address, reads that list and how often. What it does with that is covered by that host's own privacy policy.
What comes back is treated as data, never as code. Only http and https links and @aliases are accepted from it; everything else is skipped, and so are links with a user name in the address (https://user@host/) and entries containing invisible text-direction characters. The accepted keywords, links and descriptions are stored on this computer as described above. Other columns of a sheet (for example the e-mail addresses a Google Form may record) are downloaded as part of the file but are ignored and not stored.

2. Adding, changing, removing or categorising shortcuts in a list kept on GitHub

Only when all of these are true: the list is a file in a GitHub repository, you entered a GitHub token that may write to that repository, and you add, change or remove one of that list's keywords from Wyrd — or apply categories to several of them at once with Sort the uncategorised, Tidy up or the Apply box of Copy for an AI. Wyrd then, at api.github.com only and with that token in the Authorization header (no cookies, redirects not followed, no Referer):

downloads the current file (asked again, up to 3 GETs, when the branch name may contain a /, as above),
uploads the file with that one change — an entry added, changed or removed (the keyword, the link, the description and the category you typed), or the category cells of the keywords you ticked — as one commit on the list's branch. The commit message is Wyrd: add "<keyword>" (or update / remove) and contains the keyword only, or Wyrd: categorise N shortcuts and contains a count only. GitHub records the commit under the account that owns the token, and everyone who can read the repository can see it,
reads the list once more so the new keyword works at once.

If someone else committed at the same moment, Wyrd repeats those steps once. Nothing else of yours is sent: no other shortcut, no history, no usage. A file Wyrd could not rewrite without altering other people's entries (a JSON file with duplicate keys, or with numbers that would come out differently) is not changed at all. Only Wyrd's own pages can ask its background worker to store a token or make a commit; a request from any other sender is refused.

Opening a "contribute" link

A list can publish a link where additions go, typically a Google Form. When you fill in Wyrd's add form for such a list, Wyrd opens that link in a new browser tab with the keyword, link, description and category you just typed placed in the address, so that the form appears filled in. Wyrd itself sends nothing in the background; the page that opens receives those four values the way any page receives its address, as soon as the tab opens. On a Google Form nothing is recorded until you press Submit; what another kind of intake page does with the values is up to its owner. What a form records (possibly your e-mail address) is likewise decided by its owner. For a GitHub list without a write token, Wyrd opens the file's edit page on github.com instead, with nothing filled in.

Permissions used for shared lists

alarms — the 6-hour timer for re-reading your lists, and the single retry about an hour after a list was first refused. Nothing else.
Site access, one host at a time. Wyrd's package declares that it may ask for access to https sites; it holds none until you press Preview for a list or save an AI provider. Chrome then asks you to allow that list's host (for a Google Sheet: docs.google.com and googleusercontent.com; for a GitHub file: github.com and raw.githubusercontent.com, or api.github.com when a token is used) or the provider's host. Wyrd uses this access only to download that list, for api.github.com to commit an addition as described above, and for the provider's host to send the one request described under "The AI helper". It does not use it to read or change pages you visit: Wyrd contains no content scripts and does not inject anything into websites. The grant is per computer and does not sync. Cancelling a preview gives the access back, and so does removing the list (see "Deleting your data"). You can also withdraw it at any time in Chrome (chrome://extensions → Wyrd → Details → Site access); the list then stops updating.

When access to a list is refused

The first time a list's host refuses (not found, signed out, a sign-in page instead of the file), Wyrd keeps the shortcuts it last downloaded, marks the list stale and tries once more about an hour later. A second refusal then — or, before that, a Refresh you press yourself that is refused again — deletes that list's downloaded shortcuts from this computer. A refused token (the host answers 401 or 403 to it) deletes them at once.

A shared list can change where a keyword leads

A shared list is input you choose to trust; Wyrd still checks every entry. Whoever can edit a list you subscribe to can change where its keywords point, for you and every other subscriber. Your own keywords always take priority over any list — the first place that defines a keyword decides, so a list cannot take over a keyword of yours even for input your own shortcut does not handle — and Wyrd records what each refresh changed, also while the manager is closed. Subscribe only to lists whose editors you trust.

Wyrd cannot see your other tabs unless you turn on Collections (below): the tabs permission is optional, and it never reads or changes the content of any page.

A click on its toolbar icon opens a small box that saves the page in front as a keyword. For that box Wyrd has Chrome's activeTab permission: only when you click the icon, Chrome lets the box see the address and the title of the tab in front (that one tab, until it navigates away). The box reads them once, to fill in its Keyword suggestions and its Address field, which you can edit. Nothing is stored and nothing is sent unless you press Save; then Wyrd stores the keyword with the address as you left it, and the page title (see "page titles" above), exactly as if you had typed them into the manager. Closing the box keeps nothing. Chrome's own pages (settings, the new-tab page) do not show their address even then. The background part of Wyrd never looks at a tab. If you save to a shared list, what is sent is described under "Shared lists and the network": one commit of that entry to a GitHub list, or a form that opens filled in for you to submit.

If you would rather the click did not look at the page at all, choose in the manager (Settings) that it opens the manager or the directory instead; then the click reads nothing, stores nothing and sends nothing.

The Suggest button next to the Add box (and in each list's Add to this list form) proposes a keyword for the address you typed. It is computed inside the extension from that address, the date, the title Wyrd already holds for exactly that address (see "page titles" above; nothing is fetched) and naming rules (yours, or those a subscribed list published). Naming rules are plain text and are never run as code or as patterns. Pressing Suggest stores nothing.

The directory (`> /home`)

Wyrd has a page of its own, home.html, that lists every keyword you can type — your own shortcuts and those of the lists you subscribed to, grouped by list and by category, with a search box. It opens with > /home (or > /team, scrolled to the shared lists), from the Open the landing page link in the manager, from a bookmark, or from the toolbar icon if you chose that in the manager's View card.

It is an extension page rendered from the data described above, which Wyrd already holds in your browser. It fetches nothing and loads nothing from the internet: no image, font, script or frame from a list's host or anywhere else (the test home.html loads nothing from anywhere in test/home.test.js checks that the page has no http(s) src, href or url() and that its script contains no fetch). Text from a list is shown as text, never as HTML, and a list entry is shown as a link only when it is a plain web address. Opening the page, searching on it or opening a shortcut from it sends nothing anywhere (opening a shortcut opens that link, exactly as typing the keyword would; the page itself keeps no count of it). Of its own the page writes two things: its display preference homePrefs (which category groups you closed), on this computer only, and the Appearance setting (settings.theme: follow the system, light or dark) it shares with the manager, with your other synced settings. Its Copy for an AI dialog is the same one as the manager's (one shared script, sort-dialog.js), so it can also write the categories you apply there: for your own shortcuts, into categories on this computer; for a GitHub list with a saved write token, in the Teams view, as the one commit described under "Adding, changing, removing or categorising shortcuts in a list kept on GitHub"; and, in the Teams view with the AI helper set up in the manager, Send sends the lines shown to the provider you chose (see "The AI helper"). Those are the same two messages to the service worker the manager sends, carrying the same things and nothing more; the directory has no token, key or naming settings of its own. Categories, whether yours or a list's, are labels that group shortcuts on this page; they hide nothing and change no permission: whoever can read a list can read all of it.

Sorting help and "Copy for an AI" (no network)

Wyrd helps you put shortcuts into categories. All of it runs inside the extension, on this computer, from data Wyrd already holds:

Suggested categories come from naming rules (the built-in ones, or a list's own) and from the categories of the shortcuts next to the new one on the same site. Nothing is looked up anywhere.
Sort the uncategorised and Tidy up show you a proposal first; Apply writes only the rows you ticked — to this computer for your own shortcuts, or as the one GitHub commit described above for a list with a token. A Google Sheet cannot be written to: Wyrd gives you keyword,category lines to paste into the sheet yourself.
Copy for an AI builds a text and shows you every line of it before you copy or download it. It contains a fixed instruction, the categories of that one list (or of your own shortcuts) with their blurbs, and one line per shortcut: the keyword, the site's host name, the description, the page title Wyrd saved for one of your own shortcuts, and the category it has now. It never contains a link's full address (no path, no query string, no fragment — so no id, ticket number or token that a link may carry), no access token or key, no usage count, nothing from your history and nothing from any other list. Wyrd sends this text nowhere: you carry it, on the clipboard or as a downloaded file, to whatever AI chat you choose, and that chat's own terms apply to it. What the model answers is pasted back by you, parsed as plain text, checked against the category rules and shown as a preview; nothing is written until you tick and press Apply.

The AI helper (optional, off by default)

The Teams view of the manager has a card "AI helper (optional)". Until you fill it in and press Save, it does nothing, and Wyrd makes no request of this kind. This is the third and last kind of network request Wyrd can make.

What is sent. Exactly the lines shown in the "Copy for an AI" box (see the previous section for what they contain, and what they never contain) and the model name you typed, with fixed request parameters. The key you saved travels in the request's Authorization or x-api-key header. Nothing else: no cookies, no Referer, no other shortcut, no history, no usage, no other list.
When. Only when you press Send in that box, once per press. Nothing is sent when you save the settings, when you open the box, or in the background.
To whom. To the base address you typed — an OpenAI-compatible API, the Anthropic API, or any server that speaks one of those — and to nobody else. Wyrd has no AI provider, key or server of its own and is not a party to that request: the provider's own privacy terms cover what it does with the text. The address must be https; redirects are not followed (the request fails instead), so the text and the key can only ever reach the host you named. Chrome asks you once, when you save, for access to that host, and Wyrd checks that grant before every request.
A model on this computer. The one exception to https in Wyrd: an address whose host is exactly localhost or 127.0.0.1 may be http (Ollama's default is http://localhost:11434). Such a request goes to a program running on your own computer and never leaves it, which is why https — protection on the way — is not needed there; Chrome asks for no site access for it either. Any other http address is refused before anything is sent.
The answer is shown to you in the Apply box and never applied on its own. It is treated as text: read for keyword,category lines, checked against the category rules, and shown as a preview of what would change. An answer larger than 512 KB is not read, and a request that takes longer than 30 seconds is abandoned.
The key is stored on this computer only, as described under "What Wyrd stores" (aiKey, unencrypted, like a list token), and is never put in a message, an error text or a log line.
Removing it. Press Remove in the card (twice): the provider, the address, the model and the key are deleted from this computer, and the site access is given back to Chrome unless one of your lists uses the same host. Switching the manager to Family & Friends or Personal hides the card and the Send button but keeps the settings; Remove deletes them. Removing the extension deletes them too. You can also withdraw the host access at any time under chrome://extensions → Wyrd → Details → Site access; Send then fails until you save the settings again.

Copy share link puts an address like http://wyrd.invalid/?q=alpha%2Froadmap on your clipboard. It contains a list's namespace and a keyword, never a token and never the destination. Making or copying it sends nothing. It is not a public short link: it only does something in a browser that has Wyrd and that list, where Wyrd shows its confirmation page first. The namespace in the link is the one the list recommends for itself, if it does, otherwise yours. If the receiver gave the list another name, Wyrd looks the keyword up in the receiver's shared lists only — never in their personal or built-in keywords — and still asks for confirmation. All of that happens inside the receiver's browser; nothing is sent.

Features you unlock

A first install uses only the basics. Collections, Advanced collections, Reminders, your own right-click searches and Define & translate are off until you switch them on (on the Features page, or the "click here" where you would use them). Which ones are on is kept with your synced settings. A feature that needs a permission asks Chrome for it on that click, and gives it back when you switch the feature off (unless another feature you use needs it).

Right-click search

Wyrd adds "Wyrd search" to the menu you get when you right-click selected text. Chrome hands Wyrd the selected text only when you pick one of its items; Wyrd then opens a new tab with that search, exactly as if you had typed it after >. It counts as a use of the keyword (usage counts stay on this computer). Wyrd does not see what you select otherwise.

Define & translate (optional)

If you unlock it, "Define" and "Translate" in that menu show a card in the page you right-clicked in. For that Wyrd has Chrome's optional scripting permission, used only then, only in that tab, and only to show the card: it does not read the page. For a single word the card asks the Free Dictionary API (api.dictionaryapi.dev) for that word's entry; nothing else is sent, and no cookies go with it. For a sentence the card can translate it with Chrome's built-in translator, which runs on your computer (Chrome may download a language model from Google once). Nothing from the card is stored.

Reminders (optional)

If you unlock them, the reminders you set (a keyword, a date, how often) are kept in Chrome sync with your shortcuts, so they follow you to your other computers. They are checked on this computer; nothing is sent.

Starter packs

A starter pack is a list of suggested keywords you choose to read, from an address you give (or a website's link, which only fills in that address). Reading it asks Chrome for access to that one site and downloads the pack once, without your sign-in. Nothing is added to your keywords until you tick entries and press Add.

Collections (optional access to your open tabs)

Collections save the tabs of a window (or of every window) under a name, so you can reopen them later (> /clear, > /sess). To read the address and title of your open tabs Wyrd needs Chrome's tabs permission, which Chrome describes as "Read your browsing history". Wyrd does not have it at install: Chrome asks only when you press Turn on Collections, and Turn off on the collections page gives it back.

With it, Wyrd reads your open tabs only when you sweep them (> /clear, > /clearall), save one (> /save), close duplicates (> /dedupe, which looks at their addresses and keeps the copies it closes as a collection, like a sweep) or pick tabs for a new collection. What it keeps is the address, title, pinned state and window of each swept tab, and the address of its icon (never loaded). Collections are stored in chrome.storage.local on this computer: they are not synced and are not sent anywhere. The collections page and the side panel show a letter instead of each site's icon, so opening them contacts no site. Reopening a collection opens its pages, exactly as if you had opened them yourself.

What Wyrd never does

It does not transmit any data to the developer. There is no developer server to send it to.
It does not sell, share or transfer data. The only parties that ever receive a request from Wyrd are the hosts of the lists and starter packs you asked it to read, the AI provider you set up (if you did), and, with Define switched on, the Free Dictionary API; they receive only what is described above.
It has no analytics, telemetry, advertising or tracking.
It does not load or run remote code; all code is in the installed package. Shared lists are data (keywords, links, descriptions), are validated, and are never executed. An AI model's answer is data too: it is read as text, validated, previewed, and never executed.
It does not read the content of the websites you visit. The only thing it ever puts into a page is the Define card you asked for, in that one page.

Apart from those, the only websites contacted are the ones you ask for: using a keyword opens the link saved for it (by you, or in a list you subscribed to), exactly as if you had typed that address yourself. The address wyrd.invalid, used for the optional no-prefix mode, is not a real website. It can never resolve, and Wyrd handles it inside Chrome. A request for it that does not carry your private token can only run an ordinary web search; anything that would use one of your shortcuts shows a confirmation page first.

Deleting your data

Everything: remove the extension in chrome://extensions. Chrome deletes all of the extension's stored data. If you registered Wyrd as a search engine in Chrome's settings, remove that entry too.
A shared list: remove the subscription in the manager. The shortcuts downloaded from it, its status and notes, and its token are deleted from this computer, and the subscription disappears from your other computers through Chrome sync (their copies are deleted when that change arrives). Wyrd also gives back Chrome's permission for that list's site on this computer, unless another of your lists needs it; on your other computers withdraw it under Site access (chrome://extensions → Wyrd → Details). Removing a subscription does not undo anything you submitted to a form or committed to GitHub; that is in the hands of the list's owner. A token should also be revoked where it was issued (for GitHub: Settings → Developer settings) if you no longer need it.
The AI helper: press Remove in "AI helper (optional)" (Teams view of the manager): the provider, address, model and key are deleted from this computer and the site access is given back. A key should also be revoked where it was issued if you no longer need it.
Collections: delete each one on the collections page (Delete, pressed twice); Turn off there gives back the access to your open tabs.
Reminders: delete each in the side panel (×, pressed twice).
Features: switch any off on the Features page; the permission it needed goes back to Chrome.
History-related data: click Remove history access in the manager and accept the offer to clear the saved page titles and the Ignored list.
Usage counts, backups, change history: each has its own button in the manager — Clear usage stats, Clear backups and Clear change history — which deletes all of it from this computer. Without that, the address of a deleted shortcut stays in backups and the change history until newer entries push it out (20 snapshots, 1000 changes). Clear change history also deletes the shared lists' history as this computer saw it.
Individual items: shortcuts can be deleted in the manager (which also deletes that keyword's usage counts and its category), and ignored suggestions can be restored from the Ignored list. The category of a shortcut can be cleared in its edit row; the directory's display preference is reset by removing the extension.

Changes

If Wyrd's handling of data changes, this page will be updated and the date at the top will change.

Contact

Questions about this policy can be sent to the publisher contact shown on Wyrd's Chrome Web Store listing.