Tokenburner Labs LLC · 1213 S 71st St, West Allis, WI 53214, USA · legal@tokenburner.net Version 1.0 · Last updated: 3 September 2026
1. The short version
Write about us freely. Don’t pretend to be us.
You do not need our permission to review Tokenburner, criticise it, teach it, write about it, film it, compare it to something else, or say your tool works with it. That’s all normal and welcome.
What we ask is that nobody be confused about who made a thing. That’s the whole point of a trademark, and it’s the only thing this policy protects.
2. The marks
Tokenburner™ — the name. The Tokenburner logo and wordmark — our visual identity.
Together, the “Marks.” They are owned by Tokenburner Labs LLC. They were assigned to the company by its founder, together with the good will of the business in which they are used and which they symbolise, by a written Technology Assignment Agreement executed 28 August 2026 and effective 31 August 2026. Tokenburner Labs LLC is the successor to that business, which is ongoing and existing, and the company claims the benefit of all use of the Marks before that date. Rights in an unregistered mark arise from use, not from registration.
We hold no United States trademark registration, and we have applied for one. A United States trademark application for TOKENBURNER was filed on 3 September 2026 and carries serial number 50087740 — standard character mark, International Class 009, filed on an intent-to-use basis under 15 U.S.C. § 1051(b) by Tokenburner Labs LLC. An application is not a registration. Until one issues, the rights described below remain unregistered common-law rights and nothing on this page should be read as claiming otherwise.
(A register search recorded here on 28 August 2026 has been withdrawn. It used a query method later proved to return false negatives — a positive control for starbucks also returned “no results” — and it is superseded by the controlled search of 2 September 2026 described below.)
Assignment status, recorded 31 August 2026. All three instruments are now executed and § 7.3 is satisfied — Consent of Spouse 2026-08-28 05:29:19 UTC, Technology Assignment 2026-08-28 05:30 UTC, Action by Written Consent of the Sole Member 2026-08-31 18:47:51 UTC. The Effective Date of the package is 31 August 2026, being the date the last of the three was signed.
Two items remain, and neither goes to whether the assignment is effective — both go to how well it survives being attacked. (i) The capital-account credit of $2,754.00 has been booked on the Company’s books as of the Effective Date — journal entry JE-2026-001, dated 31 August 2026, balanced. The Consent of Spouse recites consideration “of the capital account credit,” and the whole reason the transfer is a contribution rather than a gift is that the credit is real; the recital now has an entry behind it. What remains is reconciling the underlying receipts before the confirmatory instrument is signed. (ii) Two elections on executed instruments have neither box ticked — the Consent of Spouse ¶ 4 independent-counsel election, and Exhibit A Part 4(d). Curable by a short written amendment signed by the same parties; worth doing, not urgent.
We use ™, not ®, and that’s deliberate. These are unregistered common-law marks. We have no granted United States trademark registration, and we won’t display ® unless and until we do — claiming a registration you don’t hold is a false statement, and in the US it can carry real consequences.
The canonical spelling is “Tokenburner” — one word, capital T, lowercase b. That matches the repository, the domain, and every other Tokenburner legal document, and it is the form to use everywhere including the Stripe statement descriptor and any future app-store listing.
What we searched, what it showed, and what it does not show. The United States register was searched on 2 September 2026 through two paths — the tmsearch.uspto.gov application using its CM: mark field tag, and the same search service endpoint directly — with seven queries on each path covering the wordmark in its solid, plural, stem, spaced and gerund forms, plus any mark combining a token-word with a burn-word. All fourteen target executions returned no records, across live and dead registrations. Five positive controls returned records, so the queries were reaching the database rather than failing silently. The method, the exact queries, the controls and the counts are recorded in our register-search evidence record of that date.
Three things that search does not tell you, which we would rather state than imply away. It says nothing about common-law rights: the four unregistered users in this field found on 26 August 2026 — tokenburner.dev, tokenburner.ai, the GitHub project at Lomnus-ai/TokenBurner, and tokenburners.com — are unaffected by a register search, their first-use dates remain unestablished, and they were not re-checked in that pass. It says nothing about registrability: because “token” is the billing unit in this market and this product is sold on cost visibility, descriptiveness risk remains moderate to high. And it is a knockout search, not a clearance opinion — phonetic equivalents, alternate spellings and design marks were not searched, and a register search is only ever true on its date.
So this policy claims what it can support and no more. We assert unregistered common-law rights in a name we use in commerce. We have filed an application (serial 50087740) and we do not claim a registration — an application confers no registered rights, and we will not use the ® symbol unless and until a registration issues. We do not assert priority over anyone whose first use we have not established.
3. Things you can do without asking
Refer to us by name
Use the name Tokenburner to refer to Tokenburner. Say your plugin works with it, your article is about it, your video reviews it, your course teaches it. Use the plain word in ordinary text — no logo, no special styling, no ™ symbol needed.
Keep it accurate and don’t imply we endorsed, sponsored, or partnered with you when we haven’t.
Link to us and talk about us
Link to tokenburner.net however you like. Write reviews — including bad ones. Compare us to competitors. Discuss us on any platform.
We will never use this policy to suppress criticism. If we ever send you a trademark complaint about something you wrote, it will be about confusion over source, not about your opinion of us.
Use screenshots
Screenshots of Tokenburner in reviews, tutorials, documentation, news coverage, courses, and conference talks are fine. You don’t need permission and you don’t owe us a fee.
Please don’t alter a screenshot in a way that misrepresents what the software does.
Name us in your own product’s compatibility claims
If you build something that works with Tokenburner, you may say so:
✅ “Works with Tokenburner” ✅ “Compatible with Tokenburner” ✅ “A theme for Tokenburner” ✅ “Unofficial Tokenburner integration”
A naming convention that’s always safe. Put your own name first and ours in the descriptive position: acme-tokenburner-theme, tokenburner-plugin-acme, “Acme Sync for Tokenburner”. Package identifiers on npm, crates.io, PyPI and similar registries follow the same rule — the ones to avoid are the bare identifier tokenburner and identifiers that read as our own official release. Anything following this convention needs no permission from us.
What you may not do is make the name the identity of your product — see § 4.
4. Things you need to not do
Don’t use our name or logo as, or as part of, the identity of your product, company, or service.
❌ “Tokenburner Pro” as your product name ❌ “TokenburnerKit”, “Tokenburner Cloud”, “Tokenburner for Teams” as your product ❌ Your company called “Tokenburner Consulting” ❌ Our logo as your app icon, favicon, or avatar
What this doesn’t reach. The ordinary English words “token” and “burn” aren’t ours, and neither is describing what your software does. If you’re using the words descriptively — “burns fewer tokens”, “token burn rate”, “a token-burn calculator” — that isn’t what this section is about, and we won’t treat it as such. This section is about names that stand in for us.
The test is simple: would a reasonable person think we made it, or blessed it? If yes, don’t.
Don’t imply endorsement, affiliation, partnership, or certification you don’t have. No “Official Tokenburner Partner,” no “Tokenburner Certified,” no badge that looks like one we issue.
Don’t set up a domain, handle, package, or listing that people would reasonably mistake for us. The test is confusion about source, not the presence of the word. A name that reads as our official channel — a download site, a support account, a package presenting itself as our release — is what this is about. Projects and accounts that already use a similar name, or that use “token burner” descriptively, are not what this addresses.
Don’t modify the logo to pass work off as ours. We publish no logo files and no brand kit today, so there is no authoritative version for us to tell you to use — and we are not going to write a rule about recolouring and clear space that we give you no way to comply with. What matters is section 4: don’t present anything as an official Tokenburner release or as endorsed by us. If you need a usable logo, ask at legal@tokenburner.net and we’ll send you one.
Don’t present any build as an official release. Ours are the only official Tokenburner releases. If you are permitted to distribute a modified build — whether under a licence we have published for it or under a right the law gives you — it must not carry our name or logo in a way that presents it as ours, and it must be obvious it isn’t ours. Keeping a copyright notice or an attribution that a code licence requires you to keep is not a breach of this policy.
Don’t use the Marks in a way that’s misleading, defamatory, or unlawful, or that attaches us to something we’d want no part of.
5. Buying our name in ads
Our concern is the ad, not the keyword. If you advertise against searches for our name, don’t let the ad itself confuse anyone — don’t use our name or logo in the ad’s headline, display URL, or body in a way that suggests the ad is ours or that you’re endorsed by or affiliated with us, and make sure the landing page is obviously yours.
Comparative advertising that’s clearly comparative is fine — “X vs Tokenburner” as honest comparison, from a page that’s obviously yours.
6. A licence to the software is not a licence to the name
Buying Tokenburner, holding a Licence Key, or being permitted to use the software gives you no rights in the Marks. Those are separate things and one has never implied the other.
The same goes for any open-source components inside Tokenburner: their licences cover their code, and none of them grant rights in our name or logo. See ToS § 16.
What we have not granted, and what we have. If you hold a licence to Tokenburner code, its terms — not this policy — tell you what you may do with that code; this policy tells you what you may do with the name and logo, and the two are separate instruments. Where a code licence we have published itself says something about our name — for example, permitting you to identify us as the origin of the software, or requiring you to keep our copyright notice in a redistribution — that licence governs for those uses and nothing in this policy cuts it down.
7. If we think something’s wrong
We’ll email you first. legal@tokenburner.net, describing what we think is confusing and what would fix it. Most of what we’d ever raise is a misunderstanding, and most is solved by a rename or a line of clarifying text.
You’ll get a reasonable time to fix it — normally at least 30 days for anything not causing active harm — before we do anything else. We’d rather have a conversation than a dispute, and we have no interest in being the company that sends aggressive letters to people writing about our product.
Two exceptions, so this promise doesn’t work against both of us. First, where something is causing live harm — a lookalike download page, a build carrying malware under our name, phishing, or an account impersonating our support — we’ll act immediately and talk afterwards. Second, this describes how we approach people; it does not govern reports we make to a registrar, registry, package repository, app store, or platform under that provider’s own rules and timescales, and using those channels is not us skipping this section.
8. Asking for permission, and questions
legal@tokenburner.net. Tell us what you want to do and where it’ll appear. We answer questions about this policy for free and we’re not precious about it.
On a press kit: not yet, deliberately. We publish no logo files, colour values, or clear-space rules at this version. A brand kit is worth publishing when people are actually asking for one; publishing official artwork before then invites uses we would later want to change. Ask us and we’ll send you what you need in the meantime.
9. Changes and reservation of rights
We may update this policy; the current version is always the one at tokenburner.net. Material changes get a new version number and date.
We reserve all rights in the Marks not expressly granted here. This policy is permission, not a transfer — nothing in it assigns, licenses beyond its terms, or exhausts any right we hold, and not enforcing something once doesn’t waive it.
Nothing here limits your rights under applicable law, including fair use, nominative use, comparative advertising, news reporting, commentary, and criticism.
Closed 2026-09-02: the register search is done and recorded — two paths, seven queries each, fourteen zero returns with five positive controls, live and dead, evidenced in the register-search record of that date. The assignment package is fully executed and effective 31 August 2026. The logo-modification rule no longer points at a page that does not exist, and the press-kit question is answered — not at this version. The application question is answered: TOKENBURNER was filed on 3 September 2026, serial 50087740, and is recorded in section 3. What deliberately remains open, and is stated there rather than hidden: the four unregistered users’ priority, and the moderate-to-high descriptiveness risk that is the likeliest ground of refusal.