Trust Center

Rights & Licensing tools: your files and answers stay in your browser

Fonts are read with JavaScript on your device; the Compatibility Checker and Attribution Generator run the rules on your device too. Nothing you drop or type into these tools is uploaded.

Check it yourself: open your browser's developer tools → Network tab, then drop a font or run a check. You will see no request carrying your file or your answers.

Pre-publish (URL) tools: what is sent, and where

To check a web page, your browser sends the page URL — in the body of a request to this site's own /api/fetch endpoint, not in the address bar. Our server fetches that public URL (plus the canonical URL and og:image it points to), and returns the page to your browser, where all the checks run. The link check sends each link and resource URL found on the page the same way, one request each, and our server only asks those URLs for their status. The robots.txt and sitemap checks fetch the site's robots.txt and sitemap files the same way, and status-check a capped sample of the URLs listed in the sitemap. Our code does not store or log the URLs or the page. Requests to our site pass through Cloudflare, which hosts it.

Our fetcher identifies itself as CheckBeforePublish-Preflight/1.0, sends no cookies, only reads public http(s) pages on the standard ports, and refuses private, internal and reserved network addresses (including after redirects). Pages larger than 2 MB are only partly checked, and this is shown in the results.

For every tool

The site's Content-Security-Policy only allows the page to connect back to this site, so it cannot send your data to any other service. Every check is a fixed, documented rule — no AI model is used.

Analytics (when enabled) only receive counts and fixed categories such as "OFL", "conflict" or "Fix before publishing: 2". Never font files, font names, license text, titles, creators, page content, URLs or file names.

Pre-publish result states

Fix before publishing

A problem the live page showed, that will cause a visible issue (for example no og:image, a canonical to a 404, conflicting robots tags).

Review

Something that may be intentional or is a judgement call (for example noindex, a long title, a canonical to another URL).

Passed

We observed it on the live page and it met the rule. It says nothing about checks that did not run.

Not checked

We could not observe it (it timed out, was blocked, or is outside the check). Never counted as passed.

Rights & Licensing evidence statuses

Verified evidence

The evidence itself says this — e.g. the font file contains this license text. It does not mean you hold the right, or that the declaration is genuine.

Not verified

We have no evidence for this — e.g. the file has no license field, or you typed the license yourself. Missing evidence is not permission.

Unsupported

We can't read this kind of file or question yet, so nothing was checked.

Needs review

The evidence is unclear, contradictory or outside what the rules cover. A person should look at it.

What we never verify

• Whether you bought, were given, or hold any license (receipts, seats, pageview tiers, app or client rights).
• Whether the metadata in a font file is genuine, or whether a work really carries the Creative Commons license you entered.
• What a license URL inside a file currently says — we never fetch it.
• Trademark, patent, privacy or publicity rights, and laws specific to your country.

This is not legal advice. Results are evidence-based guidance built from the license texts cited below. For high-stakes or unusual uses, ask a qualified professional.

Font formats and checks

Embedding flags (OS/2 fsType) are only used for document/PDF embedding and to spot contradictions — never to answer whether commercial use is allowed.

Creative Commons coverage

Tools covered: CC0 1.0 (public domain dedication), Public Domain Mark 1.0, CC BY, CC BY-SA, CC BY-NC, CC BY-ND, CC BY-NC-SA, CC BY-NC-ND. Version 4.0 and 3.0 (unported) are fully covered; 2.x and 1.0 ShareAlike version rules follow CC's compatibility page; jurisdiction-ported licenses are marked Needs review.

Rule sources (ruleset 1.1.0)

• CC BY 4.0 Legal Code — §3(a)(1): retain creator, copyright notice, license notice, disclaimer notice, URI where practicable; indicate modifications; indicate the license with text/URI. §3(a)(4): the Adapter's License must not prevent recipients complying. §2(a)(5)(B): no downstream restrictions or technological measures. (last verified 2026-09-18)
• CC BY-SA 4.0 Legal Code — §1(a): synching music in timed relation with a moving image always produces Adapted Material. §3(b)(1): if You Share Adapted Material, the Adapter's License must be a CC license with the same License Elements, this version or later, or a BY-SA Compatible License. §3(b)(3): no additional terms that restrict rights under the Adapter's License. (last verified 2026-09-18)
• CC BY-NC 4.0 Legal Code — §1(i): NonCommercial means not primarily intended for or directed towards commercial advantage or monetary compensation. §2(a)(1): reproduce/Share the material and produce/Share Adapted Material for NonCommercial purposes only. (last verified 2026-09-18)
• CC BY-ND 4.0 Legal Code — §2(a)(1)(B): produce and reproduce, but not Share, Adapted Material. §3(a)(1): "You do not have permission under this Public License to Share Adapted Material." (last verified 2026-09-18)
• CC BY-NC-SA 4.0 Legal Code — §3(b)(1): Adapter's License must be a CC license with the same License Elements, this version or later, or a BY-NC-SA Compatible License. (last verified 2026-09-18)
• CC BY-ND 3.0 Unported Legal Code — §3 License Grant covers reproducing the Work, incorporating it into Collections and distributing it; it grants no right to make Adaptations (all rights not expressly granted are reserved). §1: a Collection is not an Adaptation. (last verified 2026-09-18)
• CC 3.0 Unported Legal Code (BY-SA / BY-NC / BY-ND), §1 and §4(a) — §1: a work that constitutes a Collection will not be considered an Adaptation; synchronization of a musical work in timed relation with a moving image is an Adaptation. §4(a): incorporating the Work in a Collection does not require the Collection apart from the Work to be made subject to the License. (last verified 2026-09-18)
• Creative Commons — ShareAlike compatible licenses — BY-SA 4.0 / BY-NC-SA 4.0: same license 4.0 or later, ported 4.0+, or a designated compatible license. BY-SA 3.0: 3.0 or later (or ported 3.0+). BY-NC-SA 2.0/2.5/3.0 and BY-SA 2.0/2.5: the same or a later version of that license. Version 1.0: no compatibility mechanism; contributions must use 1.0. (last verified 2026-09-18)
• CC FAQ — Can I combine material under different Creative Commons licenses? (and compatibility chart) — If the combination does not create an adaptation, any CC content may be combined with attribution and NC compliance. ND licenses do not permit remixing except private use (pre-4.0: not at all). Remix chart: BY-SA cannot be remixed with BY-NC or BY-NC-SA; any ND license cannot be remixed; PD/CC0/BY combine with all non-ND licenses. (last verified 2026-09-18)
• CC FAQ — collections that include CC-licensed works — All CC licenses allow inclusion in collections; the collection's license does not change the license of the original material; NC material cannot be used commercially inside a collection either. (last verified 2026-09-18)
• CC FAQ — When is my use considered an adaptation? — Under CC licenses, synching music in timed relation with a moving image is always considered an adaptation. (last verified 2026-09-18)
• CC0 1.0 Universal Legal Code — Waiver of copyright and related rights; §4(a): no trademark or patent rights held by the Affirmer are waived; §4(c): the Affirmer disclaims responsibility for clearing rights of other persons that may apply to the Work. (last verified 2026-09-18)
• Public Domain Mark 1.0 — PDM marks a work as free of known copyright restrictions; the deed notes the work may not be free of known copyright restrictions in all jurisdictions. (last verified 2026-09-18)
• OpenType 1.9.1 spec — OS/2 table, fsType — Bits 0–3 usage permissions (valid values 0 installable, 2 restricted license, 4 preview & print, 8 editable); 0x0100 no subsetting; 0x0200 bitmap embedding only; versions 0–1 ignore bits 4–15; versions 0–2: if several of bits 0–3 are set the least-restrictive permission takes precedence; version 3+: mutually exclusive. fsType indicates font *embedding* licensing rights. (last verified 2026-09-18)
• OpenType 1.9.1 spec — name table — Name ID 0 copyright, 7 trademark, 8 manufacturer, 9 designer, 11/12 vendor/designer URL, 13 License Description, 14 License Info URL. (last verified 2026-09-18)
• SIL Open Font License 1.1 — Permission to use, study, copy, merge, embed, modify, redistribute and sell copies, subject to: (1) not sold by itself; (2) bundled/redistributed with the copyright notice and license; (3) Modified Versions may not use Reserved Font Names; (5) the font stays under the OFL, which does not apply to documents created with it. "Modified Version" includes changing formats or porting. (last verified 2026-09-18)
• Apache License 2.0 — §2 copyright license to reproduce, prepare derivative works, distribute; §4 redistribution conditions (include license, state changes, keep notices/NOTICE file). (last verified 2026-09-18)
• MIT License (SPDX reference text) — Permission to use, copy, modify, merge, publish, distribute, sublicense and sell, provided the copyright and permission notice are included. (last verified 2026-09-18)
• W3C WOFF File Format 1.0 — Signature 0x774F4646 'wOFF'; table directory with compLength/origLength; tables compressed with zlib compress2() when compLength < origLength. (last verified 2026-09-18)