Plain-language privacy
LiteralKit Privacy Policy
Most LiteralKit tools process text locally in your browser. Shakespeare Translator sends submitted text to LiteralKit's server and its configured AI provider only after you press Rewrite or Try another.
The LiteralKit privacy policy is the record of how this site handles text, analytics, advertising, and hosting logs. It is not a marketing page and it is not a promise that every conversion stays on your device. Analytics load only after you choose Allow analytics. Advertising scripts are currently disabled.
What the LiteralKit privacy policy covers
What the LiteralKit privacy policy covers is the production site at literalkit.com, the tools linked from the directory, the optional product-suggestion form, the inaccuracy-report email draft, Google Analytics after an explicit Allow, Vercel Speed Insights on the production domain, and the site's current advertising status. It does not cover other websites, browser extensions you install yourself, or destination apps where you paste a result. If a kind of processing is not described here, this site does not currently do it.
Read this page alongside About and the Terms. About explains how pages are published. Terms explain lawful use and the as-is nature of Unicode output. This page explains data handling. Questions that are not answered here can go to Contact or hello@literalkit.com.
Text conversion
Superscript and subscript conversion runs locally in browser JavaScript. There is no conversion API and no account. The same local design applies to the other converters and click-to-copy boards on the site, except where a page names a network step in its own copy. Your source string and the converted result live in the tab while it is open. Closing or reloading the tab clears that session text. LiteralKit does not keep a library of the strings you converted.
Local conversion is the default because these jobs are character maps, not remote models. A superscript digit, a Morse glyph, or a copied heart symbol does not need a server round-trip. The LiteralKit privacy policy treats that default as a product fact, not a slogan. If a future tool needs a network call, that tool will have to say so on its own page the way Shakespeare already does.
Shakespeare Translator
Shakespeare Translator is an AI-assisted creative-rewriting Beta. LiteralKit does not intentionally store normal source text or results, and it has no generation history. The configured provider route is selected for zero-data-retention/data-collection-denial requirements, while hosting and provider infrastructure process a request transiently.
Transient processing is not an archive. The Beta is for creative, low-stakes writing. Review the rewrite before you share it. Do not submit confidential, legal, medical, or financial text. Typing into the box does not send the string. A cancelled or abandoned draft stays in the browser.
If you choose Report inaccurate result, the page first shows what an editable email draft would contain. Nothing is sent unless you send that email yourself. If you send a report, it may include the source and result you chose to include; LiteralKit may retain the contents for up to 90 days to diagnose recurring quality issues, then redacts or deletes that text and keeps only non-text aggregate findings.
The draft exists so you can remove anything you do not want to leave your machine.
Product suggestions
When the suggestion form is enabled, it sends the suggestion text and the current page pathname that you voluntarily provide to LiteralKit's Feishu workspace. It does not collect screenshots, replay data, account details, or an email address.
Do not include personal or confidential information, or any other sensitive information, in a product suggestion. The pathname is included so the team can tell which tool the idea refers to. There is no user profile attached to the message. If you want a reply, you may put a contact method in the suggestion text yourself; the form does not harvest one in the background.
Google Analytics
Google Analytics loads only after you choose “Allow analytics.” Google may then process standard connection and device information, including your IP address, browser and device details, and approximate location, and may set first-party analytics cookies. Until that choice, the analytics script is not loaded for you.
LiteralKit measures page visits, tool engagement, examples, copy outcomes, and coarse count ranges. URLs are reduced to origin and pathname; external referrers are reduced to origin. Raw text and exact lengths are forbidden. The LiteralKit privacy policy treats those reductions as hard limits: the string you typed, and even how many characters it contained, is not an analytics event.
Your choice lasts 180 days. Use “Analytics choices” in the footer to change it. Withdrawing removes the analytics script and known first-party Google Analytics cookies before the page reloads. Changing your mind does not rewrite past reports that Google already received while analytics were allowed.
Vercel Speed Insights
On the production domain, Vercel Speed Insights measures aggregate real-user performance independently of the Google Analytics choice. Reported URLs exclude query strings and fragments. It is not part of the product funnel and is not used to identify you. It answers how quickly pages load, not what you converted or copied.
Speed Insights is a hosting-level performance signal. It is listed here because it runs on the production domain even when analytics are declined. It is not a second copy of Google Analytics and it is not a session replay product.
Advertising
LiteralKit currently does not load any advertising scripts and does not set advertising cookies. No ad vendor receives a page view through an advertising integration, and no display ad is inserted beside the input, result, Copy workflow, or elsewhere on the site.
The public ads.txt file is only a seller declaration reserved for possible future inventory. Its existence does not mean an advertising script is loading, an ad request is being made, or an advertising cookie is being set. The file is a plain-text record for advertising systems; it does not execute in your browser.
If display advertising is enabled later, the loader and this section change together. The active version of this page will then explain the vendor, cookie behavior, placement boundaries, and applicable advertising-consent controls. Until then, the analytics choice described above remains an analytics choice only; it does not enable advertising.
Questions about advertising can be sent to hello@literalkit.com.
Hosting logs
Vercel keeps deployment and runtime logs needed to operate the site. LiteralKit does not maintain a separate log database or in-product analytics dashboard. Those hosting logs can include ordinary request metadata used to keep the deployment healthy. They are not a product feature for inspecting the text you converted.
This page does not pretend that a hosted site leaves no infrastructure trace. It does say that LiteralKit does not add a second logging product on top of the host, and that conversion text is not written into a LiteralKit-operated archive of user strings.
Questions
Email hello@literalkit.com with privacy questions. Include the page URL and a short description of the concern. Do not send confidential source text unless the question cannot be asked without it. The LiteralKit privacy policy on this page is the authoritative description of current practice; if a practice changes, this page has to change with it.
Reading this page should leave a short picture: local conversion is the default, Shakespeare is the network rewrite after an explicit action, analytics wait for Allow, advertising scripts remain disabled, and there is no account in front of the tools.