MASTER DATA PROTOCOL AND PUBLIC DOMAIN DEDICATION

Last Updated: December 21, 2025
Declared Jurisdiction / Place of Establishment: Crosbyton, Texas, United States
Operator: Carson Alworth, operating as The Alworths (collectively, “The Operator,” “we,” “us,” “our”)

---

1. PREAMBLE, ACCEPTANCE, SCOPE, AND DEFINITIONS

1.1 Purpose and Operational Character

This Master Data Protocol and Public Domain Dedication (this “Protocol”) governs the relationship between The Operator and any individual or entity (“The Originator,” “you,” “your”) interacting with our websites, domains, applications, APIs, communications, services, and other digital or physical infrastructure (collectively, the “Infrastructure”).

This Protocol serves as the operational standard regarding privacy, data custody, risk allocation, and information exchange. By accessing or using the Infrastructure, The Originator acknowledges and agrees to the protocols defined herein.

If you do not agree to this Protocol, do not access or use the Infrastructure.

1.2 Amendments and Versioning

We may modify this Protocol from time to time to reflect operational, security, legal, or product changes. The “Last Updated” date indicates the effective date of the current version. Your continued use of the Infrastructure after changes become effective constitutes acceptance of the revised Protocol.

1.3 Defined Terms

For clarity, the following terms apply:

• “Data” means any information patterns, inputs, records, content, signals, metadata, telemetry, identifiers, logs, and communications transmitted to or through the Infrastructure, whether provided actively by you or collected passively through use.
• “Originator Data” means Data that originates from you (e.g., your submitted forms, messages, account inputs, payment initiation details, or other transmissions initiated by you).
• “Publicly Accessible Assets” means assets that we publish to the public on our domains or public repositories (including public articles, code snippets, design systems, and instructional materials), excluding any third-party materials and excluding private or access-restricted materials.
• “Delete / Deletion” means logical deletion and/or de-identification of records in active systems in accordance with Section 2.3, subject to technical constraints, backups, and legal retention requirements.
• “Third-Party Processors” means service providers we use to operate the Infrastructure (e.g., hosting, analytics, email delivery, payment processing), which may process Data on our behalf.

Headings are for convenience only and do not affect interpretation.

---

2. PROTOCOLS OF DATA CUSTODY AND ORIGIN CONTROL

2.1 Rejection of Information Property (Philosophical Declaration; Operational Posture)

The Operator fundamentally rejects the concept that abstract information, data patterns, or digital records constitute “property” capable of being owned by any party. We do not recognize “Intellectual Property” or “Data Ownership” as valid constructs for abstract ideas or shared information.

Clarification for legal interoperability: This Section states our philosophical and operational posture. Nothing in this Protocol prevents the existence of statutory, contractual, or common-law rights that may apply regardless of our posture (including rights associated with confidentiality, privacy, consumer protection, trade secrets, publicity, database rights, or copyright as a matter of law). Where such rights exist as a matter of law, this Protocol describes how we intend to operate and allocate permissions and risk.

2.2 Originator Authority (Source-Respecting Control)

While we reject the ownership of information, we recognize the Originator (You) as the source of specific data streams submitted to our Infrastructure.

• Voluntary Grant of Control: Solely as a matter of operational protocol, The Operator grants The Originator the authority to determine the persistence of data records that originated from them, as described in Section 2.3.
• No Property Claim: We claim no ownership over the Data residing on our servers, nor do we recognize The Originator as the “owner” of said Data. We act strictly as a temporary custodian of the information patterns necessary to execute a service.

Operational license to run the system: To provide the Infrastructure, you grant The Operator a non-exclusive, worldwide, royalty-free permission to host, process, transmit, transform, cache, and display Originator Data solely as necessary to (a) operate the Infrastructure, (b) provide requested services, (c) secure, debug, and improve operations, and (d) comply with law. This permission lasts only as long as needed for those purposes, subject to Section 2.3.

Your authority to provide Data: You represent that you have the right to provide any Originator Data you submit, including any necessary permissions from relevant individuals or entities, and that your submission does not violate any applicable law or binding obligation.

2.3 Custody and Deletion (Deletion Commands; Limits)

Upon request, we will execute the deletion of records associated with The Originator. We do this not because The Originator holds a property right to the Data, but because we choose to operate a system that respects the will of the source.

Process and verification: We may require reasonable verification of identity or control over the relevant email address, account, or authentication factor before executing deletion to reduce fraud, unauthorized deletion, or account takeover.

Scope of deletion: Deletion requests apply to Originator Data in our active systems that we can reasonably identify as associated with you.

Technical and legal limits (important):

• Backups and residual copies: Data may persist in encrypted backups, logs, disaster recovery systems, or residual caches for a limited period consistent with standard security and continuity practices. Where feasible, such data will be deleted or rendered inaccessible through routine backup rotation.
• Legal retention: We may retain certain records as required or permitted by law (e.g., tax, accounting, fraud prevention, security incident records, subpoena preservation, and compliance obligations).
• De-identified records: We may retain aggregated or de-identified telemetry that is not reasonably linkable to you.

No guarantee of irrecoverability: While we follow reasonable operational procedures, deletion does not guarantee absolute irrecoverability from all possible media in all circumstances.

---

3. PRIVACY STANDARD

This Section describes what we ingest, how we use it, and how we disclose it.

3.1 Information Ingestion

We ingest specific data patterns strictly for operational utility:

• Identity Strings: Name and email address inputs provided by The Originator.
• System Telemetry: Anonymized logs and device identifiers used for security hardening and infrastructure maintenance.
• Attribution Signals: Referral parameters (e.g., Click IDs) used to track system performance.

Additional categories that may be collected depending on your use:

• Communications: Messages you send us (email contents, support inquiries).
• Transactional signals: Payment status, timestamps, billing metadata, and limited processor tokens/receipts (we do not seek to store full payment card numbers; payment processors typically handle that directly).
• Security signals: IP addresses, user-agent strings, access times, authentication events, and abuse-prevention signals.
• Cookie / local storage identifiers: If enabled by our Infrastructure or third-party tools, for session integrity, preferences, security, and performance measurement.

3.2 Utilization of Records

Ingested records are processed for:

• Transmission of requested intelligence (newsletters, reports).
• Execution of financial settlements via third-party processors.
• Compliance with statutory requirements (e.g., tax reporting).

Additional operational purposes:

• Maintaining, operating, and improving Infrastructure performance and reliability;
• Detecting, preventing, and responding to security incidents, fraud, abuse, and prohibited conduct;
• Debugging and quality assurance;
• Enforcing this Protocol and protecting our rights, safety, and property and those of others.

3.3 Disclosure Protocol

We do not trade data records with third-party brokers. Records are shared only when:

• Required by infrastructure providers (e.g., Google Cloud, Stripe) to maintain system function.
• Compelled by force of law (e.g., court order or warrant).

Clarifications and expansions for legal stability:

• Service providers / processors: We may share Data with Third-Party Processors to host, store, deliver emails, process payments, monitor performance, prevent fraud, or provide analytics. Such providers are authorized to process Data only as necessary to provide their services to us and as permitted by their terms and applicable law.
• Legal compliance and protection: We may disclose Data if we believe in good faith that disclosure is necessary to comply with legal obligations, respond to lawful requests, protect the security or integrity of the Infrastructure, investigate potential violations, or protect rights, property, or safety.
• Business transfers: If The Operator undergoes a merger, acquisition, reorganization, sale of assets, bankruptcy, or similar event, Data may be transferred as part of that transaction, subject to this Protocol and applicable law.

3.4 Data Retention (Default)

We retain Data only as long as reasonably necessary to fulfill the purposes described in this Protocol, unless a longer retention period is required or permitted by law. Retention periods may vary based on the type of Data, operational needs, and legal obligations.

3.5 Your Choices and Requests

You may request:

• deletion as described in Section 2.3;
• access or correction of certain account/contact records we maintain (where applicable and where identity can be reasonably verified).

We may deny or limit requests where permitted by law or where fulfilling them would be unreasonably burdensome, compromise others’ rights, or undermine security.

3.6 International Use and Cross-Border Processing

The Operator is established in Texas, United States. If you access the Infrastructure from outside the United States, you understand that Data may be processed in the United States or other jurisdictions where we or our providers operate, and that the privacy laws of those jurisdictions may differ from those in your location.

3.7 Security Posture (No Absolute Guarantee)

We implement reasonable administrative, technical, and organizational measures intended to protect Data. However, no method of transmission or storage is perfectly secure. You acknowledge that we cannot guarantee absolute security.

3.8 Children / Minors

The Infrastructure is not directed to children under 13, and we do not knowingly collect personal information from children under 13. If you believe a child has provided Data to us, contact us so we can take reasonable steps to delete it.

3.9 “Do Not Track” and Similar Signals

Some browsers transmit “Do Not Track” or similar signals. The Infrastructure may not respond to such signals in a uniform way because there is no consistent industry standard.

---

4. PUBLIC DOMAIN DEDICATION (CC0)

4.1 Waiver of Rights (CC0 Intention)

Consistent with our rejection of “Intellectual Property,” Carson Alworth hereby waives all copyright and related rights to the Publicly Accessible Assets published on this domain to the fullest extent permitted by law.

This Section is intended to be interpreted as a CC0-style public domain dedication (“No Rights Reserved”) to the maximum extent permitted worldwide.

4.2 Public Domain Status (Permissions Granted)

All public articles, code snippets, design systems, and instructional materials published by The Operator are dedicated to the Public Domain. The Originator is free to copy, modify, distribute, and perform the work for any purpose, commercial or otherwise, without permission or attribution.

4.3 Limitations, Exclusions, and Third-Party Rights

This waiver applies to Publicly Accessible Assets only. It does not extend to:

• Private Client Architectures: Specific systems built under contract for private clients remain confidential to that relationship.
• Identity Verification: The personal names and likenesses of the operational staff are retained solely for the purpose of identity verification and fraud prevention.

Additional exclusions and clarifications (important):

• Third-party content: Public pages may include third-party materials (e.g., logos, libraries, fonts, screenshots, or embedded media) that are not authored by The Operator. Those materials are not covered by this dedication and remain subject to their respective licenses/rights.
• Trademarks and branding: This dedication does not grant rights in trademarks, service marks, trade dress, or brand identifiers of The Operator or any third party, except to the extent such rights are inseparable from the Publicly Accessible Assets as a matter of law.
• Privacy/publicity rights: This dedication does not grant rights to use any person’s name, likeness, or persona beyond what is permitted by law.
• Patents: To the extent any patent rights could be implicated (if any), no patent license is granted by this dedication unless a license is required by law and cannot be disclaimed.

4.4 Fallback License Where Waiver Is Not Fully Effective

In jurisdictions where a complete public domain dedication, waiver of moral rights, or waiver of related rights is not fully recognized, The Operator grants every person a perpetual, worldwide, royalty-free, non-exclusive, unconditional license to exercise all rights in the Publicly Accessible Assets for any purpose, without attribution, to the maximum extent permitted by applicable law.

---

5. DISCLAIMERS AND LIABILITY

5.1 “AS IS” Provision

All services, code, and information are provided “AS IS” without warranty of any kind. The Operator provides no guarantees regarding the security, reliability, or availability of the Infrastructure.

To the maximum extent permitted by law, The Operator disclaims all warranties and conditions, whether express, implied, or statutory, including implied warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, and quiet enjoyment.

5.2 No Professional Advice

Any information provided through the Infrastructure (including writings, templates, examples, or commentary) is for general informational purposes only and does not constitute legal, tax, financial, medical, or other professional advice. You are responsible for obtaining professional advice appropriate to your situation.

5.3 Limitation of Liability

The Operator shall not be liable for any damages arising from the use of our assets. By accessing this system, The Originator accepts all risks associated with digital information exchange.

Expanded limitation (to the maximum extent permitted by law):

• The Operator will not be liable for any indirect, incidental, special, consequential, exemplary, or punitive damages, or any loss of profits, revenue, data, goodwill, or business opportunities, even if advised of the possibility.
• To the extent liability cannot be excluded, The Operator’s total cumulative liability for all claims arising out of or relating to the Infrastructure or this Protocol will not exceed the greater of (a) the amount you paid to The Operator for the applicable service in the 12 months preceding the event giving rise to the claim, or (b) $100 USD.

Some jurisdictions do not allow certain limitations, so parts of this Section may not apply to you; in that case, liability is limited to the greatest extent permitted by law.

---

6. ACCEPTABLE USE, ENFORCEMENT, AND TERMINATION (OPERATIONAL SAFETY)

6.1 Acceptable Use

You agree not to:

• probe, scan, or test the vulnerability of the Infrastructure;
• attempt unauthorized access to accounts, systems, or Data;
• interfere with service availability (e.g., denial-of-service);
• use the Infrastructure to transmit malware, exploit code, or unlawful content;
• use the Infrastructure in a way that violates applicable law or infringes others’ rights.

6.2 Enforcement and Suspension

We may monitor, investigate, restrict, suspend, or terminate access to the Infrastructure if we reasonably believe it is necessary to protect security, prevent abuse, comply with law, or enforce this Protocol.

6.3 Termination Effects

Upon termination, your permission to access the Infrastructure ends. Sections intended to survive (including disclaimers, limitations of liability, public domain dedication terms, and dispute provisions) will survive termination.

---

7. GOVERNING LAW AND DISPUTE FORUM

This Protocol is established in Crosbyton, Texas. Any disputes regarding the interpretation of these protocols shall be resolved in accordance with the laws of the State of Texas, without regard to conflict-of-laws principles.

Forum / venue: To the extent any dispute is not resolved informally, the parties agree that any legal action arising out of or relating to this Protocol or the Infrastructure shall be brought in the state or federal courts located in Texas, and each party consents to personal jurisdiction and venue in those courts.

Time limit to bring claims: To the maximum extent permitted by law, any claim must be brought within one (1) year after the events giving rise to the claim, or it is permanently barred.

---

8. MISCELLANEOUS LEGAL STABILIZERS

8.1 Severability

If any provision of this Protocol is held to be invalid or unenforceable, the remaining provisions will remain in full force and effect, and the invalid provision will be modified to the minimum extent necessary to make it enforceable while best reflecting the original intent.

8.2 No Waiver

Failure to enforce any provision of this Protocol is not a waiver of our right to do so later.

8.3 Assignment

You may not assign or transfer your rights or obligations under this Protocol without our prior written consent. We may assign this Protocol in connection with a merger, acquisition, reorganization, or sale of assets.

8.4 Force Majeure

We are not liable for any failure or delay caused by events beyond our reasonable control, including outages, acts of government, natural disasters, labor disputes, network failures, or third-party provider disruptions.

8.5 Entire Protocol

This Protocol constitutes the entire understanding between you and The Operator regarding the Infrastructure to the extent it addresses the same subject matter, and it supersedes prior or contemporaneous communications on those subjects.

---

9. CONTACT

To execute a deletion command or query these protocols, contact the operator:

Carson Alworth
Crosbyton, TX 79322
Email: carson@carsonalworth.com