Last updated: 2026-08-30
ReplyKey is a Chrome extension that expands a typed shortcut into text you saved. This page describes what the current ReplyKey extension and the ReplyKey server at this host actually do.
When you type in a text box or an editable field, ReplyKey’s content script may read the current field so it can look for a shortcut (for example ;thx) and replace it with a saved snippet. That read happens in the browser on your computer. It is used only for that expansion.
ReplyKey does not send the field text, the page text, or your keystrokes to the ReplyKey server. After an expansion, the extension only tells itself that an expansion happened, and whether the snippet was one you created. It does not attach the words you typed.
ReplyKey stores the following in chrome.storage.local on this browser:
Snippet contents are not uploaded to the ReplyKey server.
If the extension is built with the ReplyKey HTTPS server address, and the owner-machine flag is off, the extension may POST JSON to /api/event. The body it sends is:
type — one of install_start (first install), activation (first expansion), value_delivered (first expansion of a snippet you created), or paid_intent (you clicked through to paid)install_id — the random id stored on this deviceat — a timestampexternal — set to true by the extensionThese are anonymous usage events. They are not a sale. A click on unlock is not treated as payment.
If you paste a license in settings and click unlock, the extension POSTs that license string to /api/license/verify. The server checks whether that license is already marked paid. The verify request does not include snippet text or field text.
When /api/event receives a request, the server writes the JSON fields above and may also store ordinary HTTP request data that the browser sends: the User-Agent header, the Origin header, and a Cookie header if one is present. The extension does not put page content, snippet bodies, or field text into that request. The server does not have a separate analytics product beyond this event file.
Paid checkout runs on Stripe’s site through a Stripe Payment Link. Stripe processes the information Stripe needs to charge you (for example card or other payment details). ReplyKey does not collect card numbers in the extension.
After Stripe confirms a paid checkout, ReplyKey may receive a signed webhook or look up the Checkout Session id on the success page. From that confirmation ReplyKey stores a license string derived from Stripe object ids, the amount in cents, an optional client reference id if Stripe sent one, and a timestamp. ReplyKey uses this to mark a license as paid and to count a sale only after Stripe confirms it.
There is no coded retention period and no automatic deletion job. Event lines are appended to a file on the ReplyKey server. Paid license records are stored in a file on the ReplyKey server. They remain until the operator removes those files or the host disk is replaced.
Data in Chrome local storage stays until you remove the extension or clear that extension’s storage. There is no in-product control that deletes your server-side event or license records.
ReplyKey uses the data above to expand shortcuts, to unlock a paid license after Stripe confirms payment, and to count installs and use for operating the product. ReplyKey does not sell this data. Snippet contents are not shared. Payment card data is handled by Stripe, not by the ReplyKey extension.
If the owner-machine flag is on, the extension does not send usage events. The server also excludes some events from third-party metrics (for example owner, localhost, automation, and health checks) when those marks are present. Exclusion from metrics is not the same as never writing a request.
Use the contact email shown on the Chrome Web Store listing for ReplyKey.