Last updated August 25, 2026
LiteralKit Terms of Use
The LiteralKit terms of use describe the basic conditions for using LiteralKit and its free web tools. They are not a professional-services contract and they are not a warranty that a copied character will look the same in every app. Read them with the Privacy page, which explains how text, analytics, and ads are handled, and with About, which explains how pages are published.
What the LiteralKit terms of use cover
What the LiteralKit terms of use cover is lawful use of the directory, the as-is nature of Unicode and mapped output, the Shakespeare rewrite limit, the absence of professional advice, the rights you keep in text you enter, and the fact that tools can change. They do not cover other websites, fonts you install yourself, or the terms of a destination app where you paste a result.
These pages are utilities for text, symbols, and notation. A generator maps characters. A collection copies a Unicode sign. A translator on this site is a constrained mapper or, for Shakespeare, a creative rewrite. None of that is a substitute for a typesetter, a lab notebook, a contract, or a fluent translation bureau.
Using the tools
You may use LiteralKit for lawful personal, educational, and commercial tasks. Do not interfere with the site, attempt to bypass security controls, or use it to violate another person's rights.
Lawful use includes writing a homework note, labeling a chart, decorating a social bio, or preparing a slide. It does not include attacking the site, scraping in a way that degrades the service for other visitors, or using a mapped string to impersonate a person or to evade a platform rule that you are otherwise bound by. These terms do not grant a license to a typeface file, because this site does not ship typeface files. A mapped Unicode string is not a downloaded font.
You do not need an account to convert, copy, or read a collection. There is no paid tier in front of Copy. Advertising, when it appears on the production domain, is kept outside the input, result, and Copy workflow. How ads and analytics cookies work is described on the Privacy page, not restated as a second privacy policy here. If you do not want to use a tool, close the tab. These terms do not require you to keep using the site.
Automated access that is ordinary indexing by a public search engine is expected. Automated access that is designed to overload the host, harvest the dictionaries as a hidden API, or impersonate a browser in order to bypass a control is not. LiteralKit can rate-limit, block, or withdraw a route when that is required to keep the remaining tools available. That operational choice is not a waiver of any other condition on this page.
What the LiteralKit terms of use do not cover
The LiteralKit terms of use do not license a font file, an icon set, or a trademark you see in a destination app. They do not make LiteralKit a party to the terms of Instagram, TikTok, Discord, Google Docs, or any other place you paste. They do not promise that a Unicode character is appropriate for a legal instrument, a lab report, or a published edition. They do not create an SLA, a support contract, or a governing-law clause beyond the practical fact that this is a free website of utilities.
If a third-party script fails, an ad does not load, or a rewrite times out, the rest of the local tools should still convert in the browser. A failed network feature is not a failure of a local map. A local map that leaves a character unchanged is not a defect; it is the honest leftover the coverage note already describes on that tool's page.
Results and compatibility
Outputs are provided as-is. Unicode support, appearance, normalization, search behavior, and accessibility can vary by font, device, and destination app. Review important output before relying on it.
A superscript digit, a Morse glyph, or a copied heart can render as a missing-glyph box in a font that does not cover that code point. Search engines and some messengers normalize lookalikes. Screen readers may speak a Unicode name you did not intend as a pronunciation. These terms put that variance on the page so you can check the paste in the destination that actually matters, instead of assuming the preview here is a contract with every app.
AI-assisted rewriting
Shakespeare Translator is for creative, low-stakes writing. It is not a historical translation service, does not verify meaning, and may be unavailable or return no result. Review results before sharing or relying on them; do not use it for legal, medical, financial, safety, or professional procedural text.
The rewrite is a network call after an explicit action. It can fail, stall, or return a line that is merely Shakespeare-flavored rather than period-accurate. That is expected Beta behavior, not a breach of these terms. If the page is unavailable, use another tool or write the line yourself.
No professional advice
LiteralKit does not validate equations, chemistry, legal notation, publishing standards, or other professional requirements. Use an appropriate specialist tool or qualified reviewer when accuracy has material consequences.
A mapped superscript is not a math engine. A chemistry-looking subscript is not a validated formula. A copied legal-looking mark is not counsel. These terms exist in part to say that plainly: if a mistake in the paste would matter, have a person who owns that domain check it.
Your text
You keep any rights you have in text you enter. Superscript and subscript conversion run locally. Shakespeare Translator sends text only after an explicit rewrite action, and LiteralKit does not claim ownership of the submitted text or resulting rewrite.
Local conversion does not transfer copyright to LiteralKit. Shakespeare's rewrite also does not transfer copyright to LiteralKit. You are responsible for having the right to enter the string and to publish the result. Do not paste confidential source text into a network rewrite. Details of what is stored, and what is not, live on the Privacy page rather than in these terms.
Availability and changes
Tools may change, move, or be withdrawn. LiteralKit may update the LiteralKit terms of use as the site, third-party services, and advertising model develop.
A URL that exists today can move tomorrow. A mapping can be corrected when Unicode coverage is better understood. Advertising and analytics choices can change when vendors change. When the LiteralKit terms of use change in a way that affects how you may use the tools, this page is the place that change will be written. The date in the eyebrow is the last editorial pass, not a promise that every tool is frozen.
Contact
Questions about these terms can be sent to hello@literalkit.com. Include the tool URL and a short description. Do not send confidential source text unless the question cannot be asked without it. The Contact page is the same channel for a mapping error or an accessibility problem.
Reading the LiteralKit terms of use should leave a short picture: use the tools lawfully, check the paste, treat Shakespeare as a creative Beta, do not treat mapped notation as professional advice, and keep the rights you already have in your own text.
Advertising, hosting, and destination apps
Display advertising on the production domain is a support method, not part of the converted string. Ads are kept outside the primary input, the result, and Copy. A labeled unit next to the article is not a claim that the mapped characters are an advertisement. Cookie and opt-out details live on the Privacy page. These terms only say that using the site may involve seeing those units, and that declining analytics does not by itself decline advertising cookies.
Hosting, DNS, and CDN logs are ordinary infrastructure. They are not a LiteralKit-operated archive of the strings you converted. A paste into another app is governed by that app. If Discord, a school portal, or a printer restyles or strips a character, that is a destination limitation, not a hidden rewrite performed here after Copy. Keep a plain-text original when the line will be used as a record.
Compatibility testing is your job after Copy. Try the exact character in the exact font, theme, and export path. If a mark is essential to a grade, a filing, or a safety label, use the destination's native notation or an editor that encodes structure, not only a copied code point. That instruction is repeated on tool pages as coverage notes; it is repeated here so a legal-looking heading is not mistaken for a guarantee.
Related pages stay specific. About is editorial method. Privacy is data handling. Contact is corrections. The tool directory is the map of converters and boards. These terms are only the conditions of use. If a sentence on a tool page is stricter than a sentence here—for example a leftover that stays plain, or a rewrite that requires Rewrite—the stricter sentence on that tool is the one that governs that action.
LiteralKit publishes small utilities. LiteralKit does not publish a font store. LiteralKit does not sell the mapped string. LiteralKit does not certify that a paste will satisfy a teacher, a printer, or a platform moderator. Those sentences are the same idea as the coverage notes on each tool, restated as conditions of use so a visitor who never opens About still sees them.
If you only remember one line from the LiteralKit terms of use, remember this: copy is as-is Unicode or an as-is rewrite, you check the destination, and Shakespeare is the network exception after Rewrite. Everything else on this page is detail around that line. The LiteralKit terms are short because the tools are short. The LiteralKit terms are written in the same plain voice as the coverage notes. The LiteralKit terms do not replace a specialist review when a paste has material consequences.