> For the complete documentation index, see [llms.txt](https://earthlinc.gitbook.io/protocol/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://earthlinc.gitbook.io/protocol/legal-and-policies/privacy-policy.md). # Privacy Policy *Version 1.0 · Effective July 4, 2026 · `earthlinc.earth`* This Privacy Policy explains what information we collect when you use the Earth LinC website, application, and related services at `earthlinc.earth` (the "**Service**"), how we use it, who we share it with, and the choices you have. The Service is operated by **Kong Group LLC** ("**Kong Group**," "**we**," "**us**," "**our**"). When a station is minted carrying a YuCROWN mission, that payment is a charitable **Drop** received by **YuCROWN Corporation**, a 501(c)(3) nonprofit organization ("**YuCROWN**"); where YuCROWN processes donor information, it does so as described in §6. By using the Service, you acknowledge the practices described in this Policy. Capitalized terms not defined here follow the Terms of Service and the Earth LinC Protocol Specification. > **One thing to understand before everything else:** part of what the Service does is record information **on a public blockchain**. On-chain information is **public, permanent, and cannot be edited or deleted — by you or by us.** §4 explains exactly what goes on-chain and what stays off-chain. Please read it before you Cast. *** ## 1. Information we collect **Information you provide** * **Account information** — your email address, display name, and any profile details you choose to add. * **Authored content** — the expression you compose into a Station (text, images, and other material you supply), and any message you attach to a Cast. * **Recipient information** — when you Cast, the name and email address of each recipient you choose, so the NaviStar can reach them. * **Payment information** — when you pay Kong Group (composing, plain mints, Casts) or make a Drop (a mission mint, to YuCROWN), your payment card or account details are collected **directly by our third-party payment processor**; we receive confirmation of the transaction, the amount, and limited billing details, but we do not store your full card number. * **Communications** — what you send us when you contact ****. **Information collected automatically** * **Usage information** — pages viewed, features used, actions taken (compose, Broadcast, mint, Cast, claim), timestamps, and referring pages. * **Device and log information** — IP address, browser type, operating system, device identifiers, and language settings. * **Cookies and similar technologies** — as described in §7. **Information created on-chain** * **Addresses** — the custody address that holds NaviStars on your behalf, or the self-custody address you connect. * **On-chain records** — the station you mint, the NaviStars minted by each Cast, the constellation links between them, the Realm structure (the Signet and its account), and the verified-fact layer. See §4. **Information from missions and verification** * Verified ecological action data (what was done, where, and when, as confirmed by an independent, accountable source) is recorded as part of the verified-fact layer. This is information about ecological actions, not about you — but once linked to a NaviStar you hold, it becomes part of your public on-chain record. We do not knowingly collect sensitive categories of personal information (such as health, biometric, or precise geolocation data), and we ask that you not include them in authored content. ## 2. How we use information We use the information we collect to: * provide the Service — compose Stations, deliver Broadcasts, mint and deliver NaviStars, maintain Realms, and operate custody and claims; * process payments — commercial payments (composing, plain mints, Casts) through Kong Group, and Drops (mission mints) to YuCROWN, each whole to its one destination (§6); * send the messages the Service requires — for example, the email telling a recipient a NaviStar has been Cast to them, claim instructions, and acknowledgments; * provide AI composition — the authored expression you supply is processed by AI tools to compose your Station's living page (§5, "AI processing"); * keep the Service safe — detect, investigate, and prevent fraud, abuse, and violations of the Acceptable Use & Content Policy; * comply with law — including tax, accounting, charitable-solicitation, and sanctions obligations; * improve the Service — understand usage in aggregate and fix what is broken; * communicate with you about the Service — and, only with your consent where required, send you updates or news. You can opt out of non-essential email at any time. We do **not** sell your personal information, and we do not use your authored content for advertising. ## 3. Legal bases (where GDPR applies) Where the EU or UK General Data Protection Regulation applies, we process personal information on these bases: **performance of a contract** (operating the Service you signed up for); **legitimate interests** (service security, improvement, and the delivery of Casts, balanced against your rights); **consent** (non-essential cookies and marketing email, which you may withdraw at any time); and **legal obligation** (tax, charitable, and sanctions compliance). ## 4. On-chain information — public and permanent This section is the heart of this Policy. **What goes on-chain when you mint, and when you Cast:** * the minted station — your station's permanent on-chain form; * the NaviStar itself (an ERC-1155 token on the Polygon network) and the address that holds it; * the verified-fact layer — the confirmed ecological action a mission mint carries (what, where, when — as verified); * the constellation link joining the NaviStars from one Station; * the Realm structure — the Signet and its account that make a holder's space sovereign. **What does NOT go on-chain:** * your name and email address; * recipients' names and email addresses; * payment details; * the authored page itself — the living page of a Station is stored off-chain; the NaviStar carries a **pointer** to it. **What "permanent" means for your privacy:** * On-chain records **cannot be edited or deleted** — not by you, not by us, not by anyone. Rights of erasure and rectification (under GDPR, CCPA, or similar laws) **cannot be applied to on-chain data**. We satisfy those rights for off-chain data (§8), and we design the system so that personal information stays off-chain. * An address is **pseudonymous, not anonymous**. It does not name you on its face, but if you publicly connect your identity to your address (or your Realm), anyone can read the full history of that address on the public chain. * Before you Cast, consider that the act is **irreversible**. If you are not comfortable with a permanent public record, use **Broadcast**, which is off-chain. ## 5. How we share information We share personal information only as follows: * **Service providers** — companies that process information for us under contract: payment processing, email delivery, hosting and infrastructure, and analytics. They may use the information only to provide their services to us. * **AI processing** — authored expression you compose is processed by **third-party AI service providers** to generate your Station's living page. We do not permit these providers to use your content to train their models \[**confirm against current provider terms**], and AI never touches the verified-fact layer (the protocol's integrity boundary). * **YuCROWN** — when you make a Drop (a mint carrying a YuCROWN mission), the information needed to receive and acknowledge a charitable contribution (your name, email, amount, and date) is shared with YuCROWN (§6). * **The public blockchain** — on-chain information (§4) is public by design, readable by anyone, forever. * **Recipients** — when you Cast, the recipient sees your name (as you provide it) and the Station you composed. * **Legal and safety** — when required by law, subpoena, or legal process, or when necessary to protect the rights, safety, or property of users, the public, Kong Group, or YuCROWN. * **Corporate events** — if Kong Group is involved in a merger, acquisition, or asset sale, personal information may transfer as part of that transaction, under this Policy's protections. We do not sell personal information, and we do not share it for cross-context behavioral advertising. ## 6. The two entities — who is responsible for what The Service involves two separate entities, and your information follows the same separation as the money: * **Kong Group** is the controller of the information described in this Policy — your account, content, usage, and commercial payment records (composing, plain mints, Casts). * **YuCROWN** is the controller of **donor records**: when you make a Drop (a mission mint), YuCROWN receives and keeps the information it needs to acknowledge your charitable contribution and meet its own legal obligations as a 501(c)(3) (donor name, contact, amount, date, and the acknowledgment itself). YuCROWN does not receive your commercial payment details, and Kong Group does not control YuCROWN's donor records. Questions about donor records can be sent to **** and will be routed to YuCROWN. ## 7. Cookies and similar technologies We use cookies and similar technologies to keep you signed in, remember preferences, measure how the Service is used, and protect against fraud. They fall into three groups: **essential** (required for the Service to function — always on), **functional** (preferences and settings), and **analytics** (aggregate usage measurement). Where the law requires consent for non-essential cookies, we ask for it, and you can withdraw it at any time in your settings. You can also control cookies through your browser. We do not use advertising cookies. ## 8. Your rights and choices Depending on where you live, you may have the right to **access**, **correct**, **delete**, **port**, or **restrict** the processing of your personal information, to **object** to certain processing, and to **withdraw consent**. To exercise any of these, email ****. We will verify your request and respond within the time the law requires. You also have the right to complain to your data-protection authority. Two honest limits: * **On-chain data cannot be deleted or corrected** (§4). Deletion requests are honored for off-chain data — your account, email, content, and records we hold — but the on-chain record remains, by design of the public blockchain itself. * **Receipted donations** must be retained by YuCROWN for the period nonprofit and tax law requires, even if you delete your account. **For California residents (CCPA/CPRA):** we do not sell or share personal information as those terms are defined in California law; we collect the categories listed in §1 for the purposes in §2; and you may exercise the rights above without discrimination, directly or through an authorized agent. ## 9. Data retention We keep personal information only as long as needed for the purposes in §2: account information for the life of your account; authored content while your Stations and pages are live; payment and donation records for the period tax and accounting law requires; support correspondence for as long as needed to resolve and document the matter. When information is no longer needed, we delete or de-identify it. On-chain information is permanent (§4). ## 10. Security We use administrative, technical, and physical safeguards appropriate to the information we hold — encryption in transit, access controls, and segregated processing of payments through our payment processor. Custodied NaviStars are held in managed custody infrastructure. No system is perfectly secure; if a breach affecting your personal information occurs, we will notify you and the authorities as the law requires. **If you move to self-custody, the security of your keys is yours alone — we cannot recover lost keys (Terms of Service §3).** ## 11. Children The Service is not directed to children under **\[18 / the age in your jurisdiction]**, and we do not knowingly collect personal information from them. If you believe a child has provided us personal information, contact **** and we will delete it (off-chain). ## 12. International transfers We are based in the **United States**, and information we collect is processed there and in the countries where our service providers operate. Where the law requires safeguards for international transfers (such as the EU Standard Contractual Clauses), we use them. The public blockchain is global by nature; on-chain information is replicated worldwide. ## 13. Changes to this Policy We may update this Policy from time to time. If we make material changes, we will provide reasonable notice — by posting the updated Policy with a new "Last updated" date or by notifying you through the Service. Your continued use after changes take effect means you acknowledge the updated Policy. ## 14. Contact Privacy questions and requests: ****. Kong Group LLC, 4 Pheasant Run, Holmdel, NJ 07733, United States. *** *Defined terms follow the Terms of Service and the Earth LinC Protocol Specification. Companion documents: Terms of Service · Donation Terms & Charitable Disclosures · Digital Asset / NaviStar Terms · Acceptable Use & Content Policy · Payment & Refund Policy · IP & DMCA Policy.* --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://earthlinc.gitbook.io/protocol/legal-and-policies/privacy-policy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.