Licenses and publication notices¶
Legible is a draft, open to reading, experimentation and contributions. Access to the site requires no registration or prior acceptance. Reuse of text and code follows the license accompanying each material.
Material licenses¶
| Material | License |
|---|---|
| Specification prose, documentation, site and translations | CC BY 4.0 |
| Articles and books | License stated in each work and the catalogue; the two current works use CC BY 4.0 |
| Original code, scripts, schemas, formats and vectors | Apache-2.0 |
| Geist fonts | SIL Open Font License 1.1 |
| KaTeX | MIT |
| Material for MkDocs theme and search and interface components | Their own licenses, identified in the third-party notices |
See the publication notices and license texts in the protocol repository. CC BY 4.0 permits adaptation and redistribution under its attribution conditions; Apache-2.0 includes its distribution conditions and warranty disclaimers. Third-party notices accompany their respective files. The interface and search component notices include the license texts and the corresponding sources for the Portuguese search resources distributed in this edition. These materials retain their own licenses, including MPL 1.1, MIT, Apache-2.0, 0BSD and W3C, as identified.
Original language and translations¶
Brazilian Portuguese is the editorial source for revisions. English editions are translations prepared and checked by AI against the Portuguese texts.
The rules of draft 0.4 of the Legible Protocol are defined in the Brazilian Portuguese specification. The English version is a translation and must express the same rules. If the two versions differ, the Portuguese text prevails: the translation must be corrected, and the related tests must follow the same rule.
Records, recognition and rights over works¶
The licenses stated in this publication apply to the materials it identifies. They do not automatically extend to third-party works or records mentioned in those materials. When incorporating third-party material into the project, we respect its license and preserve the required notices. Referencing a work in a Legible record does not change its permissions for use.
Recognize the benefit received from someone's work¶
When someone's work helps produce a result, the person who received that benefit can record what the work made possible. In Legible, this recognition is called a Nod.
NRC 0.2 describes a recognition commitment: those who adopt it commit to recording a Nod when they realize economic value through a sale or another exchange transaction that draws on a contribution declared under that convention. Recognition can remain private and need not involve payment.
Each formal Appoint in this edition identifies and adopts that convention. Before signing an Appoint, it is therefore important to know its full text. Simply reading, downloading or implementing the protocol requires neither issuing records nor making payments.
Sign and decide what to share¶
You can prepare a draft without signing it and sign a record without publishing it. When signing a Legible record, you adopt the declaration it contains as your own and make it in good faith. NCO expresses this commitment; its full text must be available before signing.
The signature allows readers to check which key signed the declaration and whether the content matches what was signed. Publishing the record, disclosing names or contact details, and sending content to an AI service still require their own decisions and permissions. Referencing external evidence also grants neither access nor permission to reuse it.
Submit improvements to the site or protocol¶
Besides using Legible in your work, you can propose improvements to the site's text, the specification or the code. These proposals are submitted through the project's GitHub repositories.
To incorporate a change, maintainers require DCO 1.1 certification and cryptographically signed commits. Under DCO, the submitter certifies that they can offer the material under the applicable license, subject to the conditions of that certification. The Git signature allows the commit's integrity and its attribution to the key used to be checked.
These requirements belong to the repository contribution process. They are not conditions for creating Legible records in other spaces. Third-party material or data included in a proposal requires a separate examination of its publication conditions. The contribution path provides the full instructions.
Experimental software and independent proposals¶
The catalogue states each implementation's development stage. Licenses establish the conditions of use, including their warranty and liability provisions within the limits of applicable law. Maintaining this publication does not mean operating other participants' installations or offering support with a guaranteed response time.
Fork conventions permit independent proposals with their own maintainers, without suggesting endorsement or official succession.
Spaces maintained by participants¶
The project publishes the protocol and maintains its own contribution collection. People and organizations using these record formats maintain their public or internal spaces through tools and conditions they choose. A Git provider operates its service; this does not remove the responsibilities of those deciding the content and conditions of their own publication.
Presenting a contribution does not, by itself, mean being hired or authorizing every reuse of the work. Likewise, recognizing a consequence does not replace a service or payment agreement. The name Open Legibility does not define a relationship's legal nature: its actual operation and the commitments made must be considered. This publication's licenses do not automatically extend to another space's materials.
Publication privacy¶
Notice updated on 5 November 2026. Diogo Carlotto, the maintainer of this publication in Brazil, is responsible for personal data processing decided by the project. The privacy contact is contact@legibleprotocol.com.
This site uses Cloudflare Pages with Web Analytics disabled.
When you visit the site¶
The site distributes static files, with no accounts or contribution submission form. The code in this edition includes no analytics or advertising trackers. Fonts, scripts and the search index are served by the site itself; internal search runs in the browser.
Cloudflare processes technical data to deliver and protect the site, such as IP addresses and request and traffic information. Disabling Web Analytics does not disable this processing. Infrastructure logs follow Cloudflare's conditions; this notice does not set a deletion period for logs outside the maintainer's control.
The browser may keep interface preferences, such as text size, in local storage. The text size control does not send this setting to the maintainer. You can restore the default size using the page buttons or remove site data in your browser settings. The project does not use this preference to track visits.
When you send a message¶
The addresses contact@legibleprotocol.com and security@legibleprotocol.com
forward messages through Cloudflare to a Google Gmail mailbox. These services
process email to transport and store it. The maintainer receives the sender's
address and information provided, such as a name, content and attachments,
to respond, follow up on contributions and handle security or privacy reports.
A private message does not become public just because it was sent to the project.
Send only what is necessary for the matter. The project does not request passwords, private keys or sensitive personal data through its contact channels. See also Google's privacy policy.
Purposes and retention¶
To handle contacts and maintain this publication's security and operation, the project relies on legitimate interests, limited to what is necessary and consistent with the expectations of those involved. Legal obligations and the exercise of rights may justify specific processing where actually applicable. Permission to disclose material or personal data must have a defined purpose. Sending an email or browsing does not mean consenting to any subsequent use. These conditions follow Brazil's LGPD.
Relevant correspondence may be retained to follow up on interactions and document the project's contributions and decisions for as long as necessary for those purposes. Unnecessary messages and data will be deleted. Deletion requests will be assessed in accordance with applicable law.
Providers and international processing¶
Cloudflare and Google use international infrastructure; data may be processed outside Brazil. Each provider's responsibilities depend on the operation, including processing they decide for their own services. See Cloudflare's information on the LGPD and its data processing addendum and the transfer frameworks described by Google. This information does not replace the legal requirements for each transfer.
External links, such as repositories on GitHub, lead to other services with their own privacy conditions.
Data in published materials¶
Before selecting other people's records, names and contacts, the project examines the need for disclosure, the applicable legal basis and the relevant permissions. Selected data remains public for as long as necessary for the editorial purpose that justifies disclosure. Correction or removal requests also cover downloads and copies maintained by the project.
A repository link does not copy all its content to the site. However, files selected and distributed here are copies maintained by the project. In Git, removing a file from the current version does not automatically remove it from history. Previously downloaded files and external copies are not recalled automatically. This does not relieve the project of taking appropriate measures for data under its responsibility.
Your rights and how to request assistance¶
Write to contact@legibleprotocol.com to request confirmation of processing, access, correction and information about sharing; anonymization, blocking or deletion of unnecessary, excessive or unlawfully processed data; and portability where applicable. Where processing relies on consent, you can request its withdrawal, information about refusing it and the corresponding deletion, subject to legal exceptions. You may also object to unlawful processing and petition Brazil's data protection authority, the ANPD.
Requests are handled free of charge within legal deadlines. Describe your request and, if possible, the material or interaction concerned. The maintainer may ask for proportionate identity verification to avoid disclosing data to someone else, without requiring unnecessary documents. The response will explain the action taken or any limitation. Avoid exposing personal data in a public issue. You do not need to create or sign a Legible record to make this request.
Removing content does not automatically revoke licenses already granted, which remain subject to their conditions and applicable law. This notice describes this publication and its contacts; spaces operated by other participants have their own responsible parties and conditions. Changes to the project's services or purposes must be accompanied by an updated notice.
Contact and security¶
GitHub organization · Protocol repository — invitation required · Website repository — invitation required · Books and papers on GitHub — invitation required · Contact
Report vulnerabilities through the private security channel.