Employee Center Owner Sale, Licensing, and Source Release Reservation Policy

No Raw Database Data Claim

For clarity, this document does not claim that Quintin N. Mahan owns raw facts, raw database rows, independent outside source records, CRS-owned operational records, customer-owned records, third-party-owned records, or customer relationships merely because such information is entered into, stored in, processed by, displayed through, backed up with, or exported from EC.

This document protects EC Protected Materials: the application, software, source code, schemas, database design, data model, relationships, indexes, workflows, dashboards, reports, queries, automations, integrations, APIs, access controls, credentials, hardware, infrastructure, legal records, certificate records, hashes, metadata systems, audit systems, methods, processes, techniques, trade secrets, documentation, and EC-created structural organization.

Version: 1.1
Effective Date: June 1, 2026
Platform: Employee Center / EC
Owner: Quintin N. Mahan
Legal Hub: /legal
Policies Hub: /legal/policies
Recommended Policy URL: /legal/policies/owner-sale-licensing-source-release-reservation-policy
Related Root Legal Documents: /legal/copyright-proprietary-notice, /legal/origin-authorship-development-history
Related Policy: /legal/policies/open-source-notices

1. Purpose

This policy states that Quintin N. Mahan reserves the right to sell, license, transfer, publish, release, commercialize, open-source, source-available release, privately license, publicly license, or otherwise distribute Employee Center (“EC”), or any portion of EC that he owns or controls, at any time, anywhere, to anyone, under any license, sale structure, release model, or distribution model selected by Quintin N. Mahan.

This policy is intended to make clear that CRS, CRS users, CRS officers, CRS employees, CRS buyers, CRS successors, CRS vendors, CRS creditors, or any other third party may not prevent, veto, control, delay, condition, or interfere with Quintin N. Mahan’s decision to sell, license, release, publish, open-source, transfer, or otherwise distribute EC-owned software source code, EC structure, EC schemas, EC workflows, EC documentation, EC tooling, EC examples, or EC-owned materials.

2. Owner Sale, Licensing, and Release Authority

Quintin N. Mahan may decide, at any time and at his sole discretion, to sell, license, transfer, release, publish, open-source, commercialize, or otherwise distribute EC or portions of EC under terms of his choosing.

This authority includes the right to sell, license, release, or distribute:

EC software source code;
EC application code;
EC repository contents;
EC architecture;
EC structure;
EC database design;
EC schemas;
EC migrations;
EC data model;
EC workflows;
EC automations;
EC integrations;
EC reports;
EC dashboard structures;
EC templates;
EC tools;
EC documentation;
EC deployment examples;
EC configuration examples;
EC legal framework examples;
EC certificate framework examples;
EC policy templates;
EC sanitized examples;
EC sanitized sample data;
EC future versions;
EC prior versions;
selected EC modules;
the entire EC codebase where lawfully controlled by Quintin N. Mahan.

3. Permitted Release or Sale Models

Quintin N. Mahan may choose any lawful release, sale, licensing, or distribution model.

This may include:

private sale;
public sale;
commercial license;
enterprise license;
customer license;
buyer license;
successor license;
dual license;
source-available license;
open-source license;
permissive open-source license;
copyleft open-source license;
noncommercial license;
paid commercial license;
free public release;
public repository release;
private repository access;
maintainer transfer;
community transfer;
foundation transfer;
archival release;
discontinued-project release;
successor-maintainer release;
custom license;
no-license public viewing repository;
selected-module release;
sanitized release;
redacted release;
documentation-only release;
tooling-only release;
schema/example release;
future-version release;
prior-version release.

No user or company is entitled to require a specific model.

No user or company is entitled to prevent a specific model.

4. Anywhere / Anytime Reservation

Quintin N. Mahan may sell, license, release, publish, distribute, transfer, or open-source EC-owned materials anywhere and at any time, subject to applicable law.

This may occur:

before a dispute;
during a dispute;
after a dispute;
before a CRS sale;
during a CRS sale;
after a CRS sale;
before a CRS change of control;
during a CRS change of control;
after a CRS change of control;
before employment separation;
during employment separation;
after employment separation;
after CRS refusal of Terms;
after attempted seizure;
after attempted lockout;
after evidence preservation and authorized transition support concerns;
after project discontinuation;
after a major version;
after sanitization;
after legal review;
after security review;
whenever Quintin N. Mahan decides release, sale, licensing, or distribution is appropriate.

No advance notice to CRS is required unless a separate written agreement signed by Quintin N. Mahan states otherwise.

5. No CRS Veto or Control

CRS does not control whether EC is sold, licensed, open-sourced, source-available, commercialized, dual-licensed, archived, transferred to a maintainer, transferred to a buyer, or released under another license.

CRS may not prevent, block, delay, veto, interfere with, condition, or retaliate against Quintin N. Mahan’s decision to sell, license, release, publish, open-source, transfer, or otherwise distribute EC-owned materials.

CRS use of EC does not create a right to control EC sale, licensing, release, or distribution.

CRS reliance on EC does not create a right to control EC sale, licensing, release, or distribution.

CRS data entry into EC does not create a right to control EC sale, licensing, release, or distribution.

CRS business benefit from EC does not create a right to control EC sale, licensing, release, or distribution.

CRS employment of Quintin N. Mahan does not create a right to control EC sale, licensing, release, or distribution unless a separate written agreement signed by Quintin N. Mahan expressly states otherwise.

6. Source Code and Structure Reservation

Quintin N. Mahan specifically reserves the right to sell, license, release, publish, open-source, transfer, or otherwise distribute the EC software source code and EC structure.

For purposes of this policy, EC structure includes:

repository structure;
application architecture;
module organization;
route structure;
templates;
database schema;
data model;
migrations;
field structures;
relationship structures;
workflow structures;
automation structures;
report structures;
dashboard structures;
integration structures;
certificate structures;
legal-document structures;
policy framework structures;
deployment structures;
documentation structures.

This reservation applies whether EC remains private, becomes public, is sold, is licensed, is open-sourced, is source-available, is transferred to a maintainer, or is released under any other model selected by Quintin N. Mahan.

7. Scope of Potential Release

A release, sale, license, transfer, or distribution may include any EC-owned or EC-controlled materials selected by Quintin N. Mahan, including:

source code;
application code;
scripts;
templates;
schemas;
migrations;
documentation;
examples;
tooling;
deployment notes;
configuration examples;
non-secret sample data;
generated examples;
public documentation;
sanitized workflows;
sanitized reports;
sanitized dashboard examples;
sanitized policy templates;
sanitized certificate templates;
sanitized legal framework examples.

Quintin N. Mahan may determine the scope, timing, repository, buyer, license, branch, tag, release notes, documentation, exclusions, redactions, and maintainership model.

8. Exclusions From Sale or Public Release

Unless Quintin N. Mahan expressly decides otherwise and the sale, license, release, transfer, or distribution is lawful, a release should not include:

customer private data;
employee private data;
confidential CRS records;
payment card data;
bank data;
credentials;
API keys;
OAuth secrets;
passwords;
private keys;
tokens;
production environment files;
private backups;
private logs;
private legal certificates;
private evidence packages;
private customer communications;
sensitive attachments;
security-sensitive infrastructure details;
outside source records that are not EC-owned or EC-controlled;
materials prohibited from release by applicable law.

Selling, licensing, open-sourcing, or releasing EC code does not automatically sell, license, open-source, or release production EC data, private customer data, private employee data, credentials, backups, certificate records, or confidential evidence records.

9. EC Protected Materials Distinction

This policy does not require Quintin N. Mahan to release the EC Protected Materials publicly.

The EC Protected Materials may remain private, confidential, restricted, retained, preserved, licensed, migrated, sold where lawful, or separately controlled.

A code, structure, schema, or documentation release may be made without releasing:

production databases;
customer records;
employee records;
call logs;
timecards;
service history;
legal certificates;
audit logs;
backups;
secrets;
private attachments;
private operational history.

Quintin N. Mahan may release sanitized examples, sample records, mock data, seed data, demonstration datasets, or generalized structures where appropriate.

10. License Selection

Quintin N. Mahan may choose the license for any sale, release, or distribution.

Potential license approaches may include:

permissive open-source license;
copyleft open-source license;
source-available license;
noncommercial license;
commercial license;
enterprise license;
dual-license model;
contributor license agreement;
custom license;
no-license public viewing repository;
private-source license;
buyer-specific license;
successor-maintainer license.

No user or company is entitled to demand a specific license.

No user or company is entitled to prevent a specific license.

No user or company is entitled to require that EC remain closed source.

No user or company is entitled to require that EC become open source.

No user or company is entitled to require that EC be sold or not sold.

No user or company is entitled to require that EC be licensed or not licensed.

11. No Waiver by Remaining Private

If EC remains private, closed source, self-hosted, unreleased, unsold, or undistributed for any period of time, that does not waive Quintin N. Mahan’s right to later sell, license, release, publish, open-source, transfer, or otherwise distribute EC or portions of EC under terms of his choosing.

If EC is sold, licensed, or released in part, that does not require sale, licensing, or release of all EC materials.

If one EC version is sold, licensed, or released, that does not require sale, licensing, or release of future versions.

If one EC module is sold, licensed, or released, that does not require sale, licensing, or release of all modules.

If a sanitized version is sold, licensed, or released, that does not require sale, licensing, or release of production records, private data, or confidential materials.

12. Effect of Sale, License, or Release

If Quintin N. Mahan sells, licenses, releases, publishes, open-sources, transfers, or otherwise distributes EC or portions of EC, recipients receive only the rights stated in the applicable sale document, license, release terms, or written agreement.

The specific license or sale terms will govern the rights granted for the released or transferred version or materials.

A public release does not grant rights beyond the released materials and selected license.

A sale, license, or release does not grant CRS ownership of unreleased EC materials, private EC data, private backups, credentials, legal records, certificate records, or the EC Protected Materials unless a separate written agreement signed by Quintin N. Mahan expressly states otherwise.

13. Community, Buyer, or Successor Maintainer

Quintin N. Mahan may allow a community, maintainer, successor project, fork, foundation, vendor, buyer, contractor, or individual maintainer to continue development of a released or transferred EC version.

This may be done under a sale agreement, license, repository model, governance model, or maintainer structure selected by Quintin N. Mahan.

CRS has no automatic right to act as maintainer, successor maintainer, repository owner, release manager, foundation, steward, license authority, purchaser, or assignee.

14. No Right to Force Sale or Release

This policy reserves sale, licensing, release, and distribution authority to Quintin N. Mahan.

It does not give any user or company the right to force EC to be sold.

It does not give any user or company the right to force EC to become open source.

It does not give any user or company the right to demand source code.

It does not give any user or company the right to demand repository access.

It does not give any user or company the right to demand release under a preferred license.

It does not give any user or company the right to compel publication, sale, transfer, licensing, or distribution.

15. No Right to Prevent Sale or Release

No user or company may use EC access, employment status, management status, CRS ownership, customer relationships, operational reliance, buyer status, successor status, or data-entry history to prevent Quintin N. Mahan from lawfully selling, licensing, releasing, publishing, open-sourcing, transferring, or otherwise distributing EC-owned materials.

If CRS objects to a sale, license, release, or distribution, CRS must identify a lawful, specific, non-EC-owned confidential item or legal restriction.

General reliance on EC is not enough to prevent sale, licensing, release, publication, open-source release, transfer, or distribution of EC-owned materials.

16. Sanitization and Redaction

Before sale, licensing, release, transfer, or distribution, Quintin N. Mahan may sanitize or redact materials.

Sanitization may include removing:

credentials;
secrets;
private URLs;
production hostnames;
private IPs;
customer names;
customer records;
employee records;
payment data;
tokens;
logs;
private attachments;
evidence packages;
private backup paths;
security-sensitive details.

Quintin N. Mahan may decide what redaction or sanitization is appropriate.

17. Relationship to Open Source Notices

This policy works together with the EC Open Source Notices.

The Open Source Notices explain that EC may use third-party or open-source components.

This policy explains that Quintin N. Mahan may also choose to sell, license, release, publish, open-source, source-available release, commercially license, dual-license, or otherwise distribute EC-owned materials under terms selected by Quintin N. Mahan.

Use of open-source dependencies does not make EC open source.

A decision by Quintin N. Mahan is required for EC-owned materials to be released, licensed, sold, or transferred.

18. Relationship to Copyright and Proprietary Notice

This policy works together with the Copyright and Proprietary Notice.

The Copyright and Proprietary Notice preserves current ownership and proprietary rights.

This policy preserves Quintin N. Mahan’s right to later sell, license, release, publish, open-source, source-available release, commercially license, dual-license, transfer, or otherwise distribute EC-owned materials under terms of his choosing.

A future public release does not mean EC was previously owned by CRS.

A future sale does not mean EC was previously owned by CRS.

A future license does not mean EC was previously owned by CRS.

A future public release, sale, or license does not waive ownership of unreleased materials.

19. Relationship to Origin and Authorship Page

This policy works together with the Origin, Authorship, and Development History page.

That page documents the self-initiated, self-built, privately hosted, privately controlled origin and development history of EC.

This policy reserves the owner’s right to decide whether EC remains private, is sold, is licensed, becomes source-available, becomes open source, becomes commercialized, is transferred to another maintainer, or is distributed under any other lawful model selected by Quintin N. Mahan.

20. Enforcement

Any attempt to block, interfere with, falsely claim ownership over, or misuse an EC sale, licensing, release, open-source, source-available, transfer, publication, or distribution decision may result in:

access restriction;
access suspension;
access revocation;
preservation of evidence;
legal enforcement;
injunctive relief;
recovery of costs or fees where available.

21. Changes to This Policy

Quintin N. Mahan may update this Owner Sale, Licensing, and Source Release Reservation Policy by publishing a new active version in EC.

The current active version will be displayed through the Legal hub or Policies hub.

Older versions may remain stored in Postgres for audit, evidence, legal history, and historical review.

22. Contact / Owner

Employee Center is owned by Quintin N. Mahan.

Legal and policy documents are available from:

/legal

Policy documents may be organized at:

/legal/policies

The current Terms and Conditions are available from:

/legal/terms-and-conditions

The Copyright and Proprietary Notice is available from:

/legal/copyright-proprietary-notice

The Open Source Notices may be available from:

/legal/policies/open-source-notices

End of Employee Center Owner Sale, Licensing, and Source Release Reservation Policy.

EC Owner Open Source Release Reservation Policy