← Back

Employee Center Terms And Conditions

01_terms/employee_center_terms_and_conditions.md

Employee Center Terms and Conditions

Revision: No Raw Database Data Claim / Login-Page Acceptance Gate / Certificate Email Attachment Revision 2026-05-31

Version: 1.0
Effective Date: June 1, 2026
Platform: Employee Center / EC
Owner: Quintin N. Mahan

Conspicuous Material Terms Summary

This summary is provided for conspicuous notice. The full Terms below control.

By signing in, checking the Terms acceptance checkbox, accessing, using, relying on, continuing to use, or declining use of EC after notice of these Terms:

1. Purpose and Scope

These Employee Center Terms and Conditions (“Terms”) govern access to and use of Employee Center, including the application, software, source code, object code, scripts, database schemas, database design, data model, indexes, relationships, workflows, dashboards, forms, reports, automations, integrations, APIs, infrastructure, hardware, configurations, credentials, service accounts, documentation, audit systems, legal records, certificate records, hashes, backups, and related platform materials collectively referred to as “EC.”

For clarity, EC does not include ownership of 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, displayed through, processed by, or exported from EC.

These Terms are intended to protect Quintin N. Mahan’s privately owned application, code, structure, methodology, trade secrets, credentials, hardware, infrastructure, and EC-created control layer while preserving the separate legal status of raw source records and underlying facts.

These Terms apply to all users, companies, employers, officers, supervisors, employees, contractors, agents, service accounts, display accounts, API accounts, integrations, vendors, customers, successors, buyers, assignees, transferees, creditors, receivers, trustees, and third parties that access, use, view, rely on, enter data into, import data into, upload files into, connect systems to, request features for, configure, test, continue using, or attempt to use EC.

For purposes of these Terms, “Owner” means Quintin N. Mahan.

For purposes of these Terms, “Company” includes Cash Register Systems, Inc. (“CRS”) and any company, employer, organization, successor, buyer, assignee, transferee, creditor, receiver, trustee, or third party seeking to access, use, rely on, acquire, control, or continue using EC.

2. Private Ownership of EC Protected Materials

EC Protected Materials are privately owned and controlled by Quintin N. Mahan.

EC Protected Materials include, without limitation:

No company, employer, supervisor, officer, employee, contractor, customer, vendor, user, successor, buyer, assignee, transferee, creditor, receiver, trustee, or third party receives any ownership interest in EC Protected Materials by accessing EC, using EC, entering data into EC, requesting features, relying on EC, benefiting from EC, assigning employees to use EC, connecting company systems to EC, paying wages, paying salaries, reimbursing expenses, using company time, using company premises, using company data, selling the company, buying the company, acquiring company assets, acquiring company customer relationships, or attempting to continue company operations.

Nothing in this section claims ownership of 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 stored in EC.

Any sale, assignment, transfer, exclusive license, source-code license, ownership transfer, or control transfer of EC Protected Materials must be made in a separate written agreement signed by Quintin N. Mahan.

3. Conditional, Non-Transferable License to Use EC

Access to EC is a limited, conditional, revocable, non-exclusive, non-transferable, non-assignable license granted by Quintin N. Mahan.

No person or company has any right, license, permission, or authorization to access or use EC unless that person and company accept these Terms or Quintin N. Mahan separately authorizes access in writing.

Use of EC is optional. Any person or company that does not agree to these Terms must not access or use EC.

The license granted under these Terms is permission to use EC only. It is not a sale, assignment, transfer, work-made-for-hire arrangement, ownership interest, permanent license, source-code license, database-ownership transfer, raw-data ownership transfer, hardware transfer, credential transfer, methodology transfer, trade-secret transfer, or infrastructure transfer.

The Owner may suspend, restrict, revoke, disable, block, or terminate EC access as provided in these Terms.

4. Acceptance by Access, Use, Continued Use, or Sign-In

By accessing EC, logging into EC, signing into EC, checking the Terms acceptance checkbox, viewing EC, using EC, entering data into EC, importing data into EC, uploading files into EC, requesting EC features, configuring EC, testing EC, relying on EC reports, using EC workflows, using EC outputs, connecting systems to EC, allowing company data to be processed by EC, or continuing to use EC after notice of these Terms, the user and the user’s company immediately accept and agree to these Terms.

Use of EC constitutes immediate agreement to all EC ownership, data, work product, hardware, licensing, assignment, contribution, access-control, fee, termination, venue, evidence, estoppel, covenant-not-to-sue, and enforcement provisions.

No separate handwritten signature, wet signature, purchase order, payment, or additional written acceptance is required for these Terms to apply, except where these Terms expressly require a separate written agreement signed by Quintin N. Mahan.

Any user or company that does not agree to these Terms must immediately stop using EC.

Refusal, non-acceptance, objection, attempted rejection, attempted modification, or attempted selective acceptance of these Terms means the user and company have no license, permission, authorization, or right to access EC.

Continued access or use after notice of these Terms constitutes acceptance.

5. Login-Page Terms Acceptance Gate

EC may require Terms acceptance on the sign-in flow before allowing normal access.

The ordinary sign-in page may remain the default page when the authenticated user already has a current valid acceptance for the active Terms version and hash.

When a user has no current acceptance, has declined, or the active Terms version/hash has changed, EC may route the user to a cloned Terms-acceptance sign-in page instead of the ordinary sign-in page.

The cloned Terms-acceptance sign-in page should preserve the ordinary sign-in layout while adding the Terms acceptance controls.

The cloned Terms-acceptance sign-in page must include a clear link to the active Employee Center Terms and Conditions.

The sign-in button on the cloned Terms-acceptance sign-in page must remain disabled until the required checkbox is checked.

The required red warning text must appear immediately above the checkbox until the checkbox is checked:

You must agree to the terms and conditions before signing in.

The red warning text should clear, hide, or otherwise stop displaying once the checkbox is checked.

The checkbox wording must be:

I agree to the Terms and Conditions.

The words “Terms and Conditions” must be an open link to the active Terms and Conditions page.

The checkbox may be hidden or omitted on the ordinary sign-in page after the user already has a current valid acceptance for the active Terms version/hash.

The checkbox may reappear or the user may be redirected to the cloned Terms-acceptance sign-in page when the active Terms version/hash changes or when no current valid acceptance exists.

The checkbox is client-side and UI gating only.

Binding acceptance must be recorded server-side only after successful authentication.

If username/password authentication fails, EC must not record Terms acceptance.

If authentication succeeds and the checkbox was checked, EC may record acceptance for the authenticated user account and, where applicable, company-level acceptance according to server-side company-authority rules.

If a user does not agree, the user must not sign in or use EC.

6. Decline; No Access Until Acceptance

The cloned Terms-acceptance sign-in page may include a Decline button.

If a user clicks Decline, EC may record the user’s Terms status as declined, refused, or non-accepted.

Decline should not authenticate the user into normal EC access.

Decline should not allow access to dashboards, tasks, timecards, directory, calls, reports, integrations, attachments, admin pages, APIs, display pages, or other EC operational areas.

Decline should update the user’s status and prevent access until the user later accepts the then-current Terms.

Decline may return the user to the ordinary sign-in page, the cloned Terms-acceptance sign-in page, or a no-access status message.

Decline does not transfer any EC Protected Materials to CRS, does not create any company right to access EC, does not create any company right to copy EC, does not create any company right to control EC, does not require Quintin N. Mahan to surrender EC Protected Materials, does not require source-code disclosure, and does not require credential disclosure.

Refusal or decline does not itself operate as an admission of all Terms by the declining party.

Instead, refusal or decline means EC does not authorize further access or use unless the user later accepts the then-current Terms or Quintin N. Mahan expressly authorizes access in writing.

No acceptance means no EC access.

7. Electronic Records, Acceptance Logs, Decline Logs, Certificates, and Hashes

EC may record electronic acceptance and decline events.

A valid acceptance record may include, without limitation:

A decline record may include, without limitation:

A checkbox checked before login is not by itself a binding acceptance record.

Binding acceptance attaches only after successful server-side authentication and server-side recording against the authenticated user account.

EC may generate individual and company acceptance certificates, hashes, PDFs, audit logs, and email notifications.

Acceptance/decline records may be used as evidence of notice, acceptance, refusal, non-acceptance, authority, timing, identity, and access authorization or lack of authorization.

8. Company Authority to Accept

Any person accepting these Terms on behalf of a company, employer, organization, or other legal entity represents and warrants that the person has authority to bind that entity.

If a person does not have authority to bind the entity, that person may not accept these Terms on behalf of the entity and may not authorize use of EC by that entity.

Company acceptance binds the company and its officers, owners, employees, contractors, agents, service accounts, display accounts, API accounts, integrations, authorized users, successors, buyers, assignees, transferees, receivers, trustees, and any party attempting to continue company use of EC.

Each individual user must also accept these Terms personally as a condition of access. Company acceptance does not eliminate individual acceptance.

9. Existing EC Protected Materials; No Raw Database Data Claim

Existing EC Protected Materials are owned and controlled by Quintin N. Mahan to the maximum extent permitted by law.

For clarity, existing EC Protected Materials do not mean every database record or raw underlying fact. Quintin N. Mahan does not claim ownership of 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 exists in EC.

Existing EC Protected Materials include, without limitation, EC software, source code, schemas, database design, data model, relationships, indexes, workflows, dashboards, reports, queries, automations, integrations, APIs, access controls, credentials, hardware, infrastructure, audit systems, logs, legal records, certificate records, hashes, metadata systems, documentation, backups of EC Protected Materials, and EC-created structural organization.

Acceptance of these Terms, sign-in after notice of these Terms, checking the Terms acceptance checkbox, accessing EC, using EC, relying on EC, or continuing to use EC after notice of these Terms confirms, ratifies, and agrees to Quintin N. Mahan’s ownership, possession, retention, backup, preservation, use, development, modification, publication, licensing, sale, release, transfer, open-source release, commercialization, and control rights in EC Protected Materials to the maximum extent permitted by law.

Refusal, rejection, non-acceptance, objection, attempted modification, attempted selective acceptance, decline, or dispute of these Terms does not transfer any EC Protected Materials to CRS, does not create any company right to access EC, does not create any company right to copy EC, does not create any company right to control EC, does not require Quintin N. Mahan to surrender EC Protected Materials, does not require disclosure of source code, does not require disclosure of credentials, and does not impair Quintin N. Mahan’s existing and asserted ownership, possession, retention, preservation, use, development, modification, publication, licensing, sale, release, transfer, open-source release, commercialization, and control rights in EC Protected Materials.

Refusal or decline does not itself operate as an admission of all Terms by the declining party. Instead, refusal or decline means that EC does not authorize further access or use unless the user later accepts the then-current Terms or Quintin N. Mahan expressly authorizes access in writing.

Independent outside source records may remain separate from EC. A lawful right to an outside source record does not create ownership of EC Protected Materials.

10. No Agreement, No Access

Access to EC is conditioned on acceptance of these Terms unless Quintin N. Mahan expressly authorizes access in writing.

No acceptance means no access.

If a user or company refuses, declines, disputes, attempts to modify, attempts to selectively accept, or does not accept the then-current Terms, EC may deny, suspend, restrict, revoke, disable, block, or terminate access.

If the active Terms version/hash changes, prior acceptance does not authorize continued use unless EC determines the prior acceptance remains current or the user accepts the new active Terms version/hash.

EC may route users to the cloned Terms-acceptance sign-in page until the user accepts the active Terms.

A user who declines may remain in declined/no-access status until later acceptance.

Attempted access without current acceptance is unauthorized unless Quintin N. Mahan separately authorizes access in writing.

11. No Work-Made-for-Hire

All work performed on, in, through, for, connected to, or relating to EC belongs to Quintin N. Mahan unless Quintin N. Mahan signs a separate written assignment stating otherwise.

No EC-related work shall be treated as company-owned, jointly owned, work-made-for-hire, assigned to any company, or controlled by any company merely because:

Any transfer of EC-related work product requires a separate written agreement signed by Quintin N. Mahan.

This remains true even if the EC-related work was already performed or is later performed during business hours, on the clock, on paid time, at a company location, using company operational context, or by a person receiving hourly wages, salary, benefits, reimbursement, or other compensation from CRS or any company.

12. Business-Hours Work, Wages, Paid Labor, and Prior On-the-Clock Work

Any work performed on, in, through, for, connected to, or relating to EC remains the sole property of Quintin N. Mahan regardless of when, where, why, or by whom the work is performed.

This section applies both prospectively and retroactively to the maximum extent permitted by law.

All EC-related work already performed before the Effective Date of these Terms, including EC work already performed during business hours, on the clock, during paid time, while receiving hourly wages, salary, benefits, reimbursements, commissions, or other compensation from CRS or any company, remains EC work product owned solely by Quintin N. Mahan to the maximum extent permitted by law.

No company, employer, supervisor, officer, employee, contractor, user, customer, vendor, or third party receives any ownership interest, license right, control right, assignment, work-made-for-hire interest, shop right, implied license, joint ownership interest, or claim to EC merely because:

Any wages, salary, benefits, reimbursements, commissions, or compensation paid by CRS or any company to any employee, officer, contractor, user, or representative, whether before or after the Effective Date, are not payment for EC ownership, EC source code, EC software, EC data structures, EC workflows, EC dashboards, EC reports, EC automations, EC integrations, EC documentation, EC work product, EC Protected Materials rights, or EC intellectual property unless Quintin N. Mahan signs a separate written agreement expressly stating that such payment purchases or transfers those EC rights.

All EC-related work, including work already performed during business hours or paid time before the Effective Date, is treated as EC work product owned by Quintin N. Mahan to the maximum extent permitted by law.

To the extent any person or company may have or claim any right, title, interest, license, contribution right, copyright interest, database right, authorship claim, improvement right, shop right, implied license, work-made-for-hire claim, or other claim arising from EC-related work already performed or later performed during business hours, on the clock, paid time, company operations, or company employment, that person and company assign such right, title, and interest to Quintin N. Mahan to the maximum extent permitted by law.

To the extent any such right cannot legally be assigned outright, the person and company grant Quintin N. Mahan a perpetual, irrevocable, worldwide, royalty-free, fully paid, transferable, sublicensable license to possess, retain, copy, modify, maintain, improve, commercialize, distribute, use, integrate, preserve, and continue using such work as part of EC or any related system.

No company policy, employee handbook, supervisor instruction, payroll practice, hourly wage, salary, timecard record, business-hours work, on-the-clock work, company request, reimbursement, ordinary compensation, course of dealing, prior course of dealing, prior payment, prior wage payment, or company benefit shall modify this section or transfer any EC rights away from Quintin N. Mahan.

13. EC Work Product

All EC work product belongs to Quintin N. Mahan.

EC work product includes, without limitation:

No user, company, employer, supervisor, officer, employee, contractor, customer, vendor, or third party is entitled to ownership, royalties, compensation, veto rights, approval rights, control rights, or access rights because they requested, suggested, tested, used, configured, contributed to, or benefited from EC work product.

14. Feature Requests and Contributions

Any idea, request, suggestion, workflow, correction, bug report, feature request, configuration request, process improvement, data-model suggestion, report request, dashboard request, integration request, automation request, documentation request, operational process, or other contribution submitted, discussed, requested, tested, or implemented in connection with EC becomes part of EC.

The submitting party grants, assigns, transfers, and licenses to Quintin N. Mahan, to the maximum extent permitted by law, all rights necessary to use, modify, implement, expand, commercialize, remove, publish, document, integrate, sublicense, or otherwise exploit such contribution as part of EC or any related system.

No user or company is entitled to compensation, ownership, royalties, veto rights, approval rights, access rights, or control rights because they suggested, requested, tested, used, configured, contributed to, or benefited from an EC feature.

15. License to Process Inputs; No Assignment of Raw Records

Users and companies may enter, upload, import, transmit, generate, process, structure, correct, maintain, or use data and records through EC only for authorized EC-related purposes.

To operate EC, each user and company grants Quintin N. Mahan and EC a non-exclusive license to store, process, structure, normalize, reconcile, index, analyze, display, back up, secure, preserve, audit, export, migrate, troubleshoot, and maintain submitted inputs for lawful EC-related purposes.

This processing license is not an ownership transfer of raw records.

Nothing in this section assigns to Quintin N. Mahan ownership of 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 they are entered into, uploaded into, imported into, transmitted to, generated by, processed by, structured by, maintained in, corrected through, used by, connected to, or relied upon by EC.

Quintin N. Mahan retains ownership and control of the EC Protected Materials that receive, store, process, structure, index, relate, display, secure, audit, export, or otherwise operate upon such inputs, including EC software, source code, schemas, data model, relationships, workflows, dashboards, reports, automations, integrations, APIs, access controls, credentials, legal records, certificate records, hashes, metadata systems, methods, and trade secrets.

16. Existing Database Records; Rights Reserved Without Raw-Data Ownership Claim

Records, files, materials, imports, uploads, notes, operational records, customer records, company records, store records, contact records, service records, task records, time records, call records, equipment records, attachments, integration records, and API records may already exist in EC as of the Effective Date of these Terms.

Quintin N. Mahan does not claim ownership of those raw database records or underlying facts merely because they already exist in EC.

A company may retain whatever rights it has in independent outside source records, raw operational facts, raw customer records, customer relationships, and third-party-owned records.

Quintin N. Mahan retains ownership and control of EC Protected Materials associated with those records, including EC software, source code, schemas, database design, data model, relationships, indexes, workflows, dashboards, reports, queries, automations, integrations, APIs, audit systems, logs, legal records, certificate records, hashes, metadata systems, documentation, backups of EC Protected Materials, and EC-created structural organization.

Acceptance of these Terms confirms that prior use, reliance, data entry, database population, business benefit, employee use, company use, or customer use does not transfer EC Protected Materials to CRS and does not give CRS control over EC design, code, structure, methodology, feature decisions, hardware, credentials, repository access, or owner administration.

17. EC Protected Materials

For purposes of these Terms, EC Protected Materials means the EC application, code, structure, methodology, trade secrets, owner-controlled hardware, owner-controlled credentials, owner-controlled infrastructure, and EC-created control layer.

EC Protected Materials include, without limitation:

EC Protected Materials expressly exclude raw facts, raw database rows, independent outside source records, CRS-owned operational records, customer-owned records, third-party-owned records, and customer relationships merely because such information is entered into, stored in, processed by, displayed through, or exported from EC.

18. Source Records, Raw Records, and Underlying Facts Are Separate

These Terms do not transfer to Quintin N. Mahan ownership of independent source records, raw facts, raw database rows, 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.

CRS or a lawful successor to CRS may retain whatever rights it has in independent source records and raw operational facts outside EC.

Customers and third parties may retain whatever rights they have in their own records and information.

Those rights do not create ownership or control of EC Protected Materials.

A lawful right to a source record, customer record, operational record, or underlying fact does not create any right to EC source code, EC software, EC schemas, EC database design, EC data model, EC relationships, EC indexes, EC workflows, EC dashboards, EC reports, EC query logic, EC automations, EC integrations, EC metadata systems, EC audit systems, EC certificates, EC legal records, EC hashes, EC backups of protected materials, EC credentials, EC hardware, EC infrastructure, EC methodology, or EC trade secrets.

19. Customer Records, Operational Records, and Raw Business Facts

The parties acknowledge that EC may store, structure, index, normalize, reconcile, display, process, and export business information, including customer records, store records, contacts, phone numbers, email addresses, addresses, service history, equipment records, call records, task records, notes, support history, tax/location data, and related operational information.

These Terms do not claim ownership of CRS customer relationships, raw customer records, raw operational records, raw business facts, or third-party-owned information merely because that information is stored in EC.

CRS may retain whatever rights it has in CRS-owned operational records and customer relationships.

Customers and third parties may retain whatever rights they have in their own information.

Quintin N. Mahan retains ownership and control of the EC Protected Materials that receive, store, structure, index, relate, display, process, secure, audit, export, and report upon such information, including EC source code, schemas, data model, relationships, indexes, workflows, dashboards, reports, automations, integrations, audit systems, certificate systems, metadata systems, access controls, credentials, hardware, infrastructure, methodology, and trade secrets.

The rights retained by Quintin N. Mahan under these Terms may be used for lawful EC-related purposes involving EC Protected Materials, including, without limitation:

Nothing in this section authorizes unlawful use of raw CRS-owned records, customer-owned records, third-party-owned records, customer relationships, or raw database contents.

21. No Customer Transfer, Customer-List, or Customer-Marketing Right Created by These Terms

These Terms do not create a right for Quintin N. Mahan to market to CRS customers using raw CRS customer records merely because those records are stored in EC.

These Terms do not create a right for Quintin N. Mahan to claim ownership of CRS customer relationships.

These Terms do not create a evidence-preservation transfer, customer-list transfer, goodwill transfer, or business-succession right.

Any customer relationship, customer-contact, customer-service, customer-transition, or post-employment business issue must rest on a separate lawful basis outside this section and outside any raw-data ownership theory.

This section does not reduce, impair, waive, or postpone Quintin N. Mahan’s ownership, control, retention, protection, development, modification, licensing, sale, release, publication, open-source release, commercialization, enforcement, or defense rights in EC Protected Materials.

22. Hardware, Devices, Infrastructure, and Connected Systems

All hardware, devices, servers, computers, tablets, phones, Raspberry Pis, modems, routers, switches, storage devices, displays, relays, sensors, adapters, cables, peripherals, virtual machines, cloud resources, network resources, service accounts, credentials, tokens, keys, APIs, integrations, and infrastructure purchased by, owned by, controlled by, configured by, deployed by, or maintained by Quintin N. Mahan for EC are EC property and belong solely to Quintin N. Mahan.

Any hardware, device, account, system, credential, integration, or infrastructure provided, contributed, dedicated, connected, configured, assigned, or used for EC becomes EC-controlled infrastructure to the maximum extent permitted by law, unless expressly excluded in a separate written agreement signed by Quintin N. Mahan before connection, configuration, deployment, or use.

To the extent any company-owned hardware or system cannot be transferred by these Terms alone, the company grants Quintin N. Mahan an irrevocable, perpetual, royalty-free license and access right to possess, access, configure, maintain, secure, back up, export data from, disconnect, disable EC services on, or continue operating EC through that hardware or system as necessary to protect EC, preserve EC data, maintain continuity, enforce these Terms, prevent unauthorized use, or avoid loss of EC-related records.

A separate Hardware Schedule may be attached to these Terms and incorporated by reference.

23. Hardware Schedule and Presumption of EC Property

Any hardware, device, account, system, credential, service account, API key, token, storage device, virtual machine, server, modem, router, Pi, phone, display, or infrastructure listed in the Hardware Schedule shall be presumed EC property or EC-controlled infrastructure.

The Hardware Schedule may be updated by Quintin N. Mahan as EC hardware, infrastructure, devices, or accounts are added, replaced, removed, migrated, or reconfigured.

A company or user disputing an item listed in the Hardware Schedule must provide written objection within ten calendar days of notice of the schedule or update. Failure to object within ten calendar days constitutes acceptance of the schedule or update.

Dispute of the Hardware Schedule does not transfer ownership of EC, affect EC data rights, affect EC work product rights, or authorize continued use of EC after access is revoked.

24. Credentials, Tokens, API Keys, and Service Accounts

All EC credentials, tokens, API keys, service accounts, passwords, certificates, SSH keys, OAuth credentials, webhook secrets, encryption keys, signing keys, integration credentials, automation credentials, and related access mechanisms created, configured, maintained, or used for EC are EC-controlled security materials.

No user or company may copy, export, disclose, retain, rotate, revoke, reset, seize, disable, misuse, or interfere with EC-controlled security materials without written permission from Quintin N. Mahan.

Attempted seizure, copying, revocation, disabling, or misuse of EC-controlled security materials is a material breach of these Terms.

25. Employment-Associated Free License

During the period that Quintin N. Mahan remains actively employed by Cash Register Systems, Inc. (“CRS”), CRS receives a no-cost, conditional, revocable EC license only because of Quintin N. Mahan’s active employment relationship with CRS.

This no-cost license is not a sale, assignment, transfer, permanent license, work-made-for-hire arrangement, ownership transfer, source-code license, database ownership transfer, hardware transfer, or waiver of EC ownership.

The no-cost license remains subject to full compliance with these Terms.

26. Employment Change Event

Upon any Employment Change Event, the no-cost license immediately terminates without further notice.

An Employment Change Event includes, without limitation:

  1. termination of Quintin N. Mahan’s employment for any reason;
  2. resignation;
  3. layoff;
  4. suspension;
  5. unpaid leave;
  6. reduction of authority affecting EC operation;
  7. removal from EC administration or CRS technology authority;
  8. attempted restriction of Quintin N. Mahan’s access to EC;
  9. CRS disputing Quintin N. Mahan’s ownership of EC;
  10. CRS directing that EC development, access, administration, or ownership be limited contrary to these Terms;
  11. CRS attempting to seize, copy, replace, transfer, or claim EC;
  12. CRS attempting to continue using EC while rejecting these Terms;
  13. CRS attempting to disable, revoke, or interfere with EC credentials, integrations, infrastructure, data, backups, or service accounts;
  14. CRS attempting to require EC work without accepting these Terms;
  15. CRS attempting to force continued free access after the basis for free access has changed;
  16. any material change in employment status, authority, compensation, role, or relationship that materially changes the basis on which EC was provided to CRS without a separate platform fee.

27. Post-Employment Service Fee

After an Employment Change Event, any continued CRS access to EC may become a paid monthly service at $10.00 per active, enabled, invited, provisioned, display, service, API, integration, or user account per month, unless Quintin N. Mahan signs a different written rate, waives the fee in writing, or applicable law prohibits the charge.

The first month’s service fee becomes due upon the Employment Change Event if EC access continues after that event.

Future monthly service fees are due monthly in advance while access remains enabled.

Payment grants only conditional access for the paid period.

Payment does not transfer ownership of EC, EC software, EC source code, EC data, EC work product, EC-derived data, EC-created data, EC-maintained data, EC-structured data, EC-normalized data, EC-enriched data, EC metadata, EC audit trails, EC reports, EC dashboards, EC automations, EC integrations, EC schemas, EC workflows, EC hardware, EC credentials, EC backups, EC infrastructure, or related EC materials.

Payment of the service fee does not require Quintin N. Mahan to continue providing access if access is suspended, revoked, or terminated under these Terms.

Failure to pay permits access suspension or termination to the maximum extent permitted by law and these Terms.

28. Post-Employment EC Protected Materials Rights

Upon any Employment Change Event, Quintin N. Mahan retains ownership, possession, control, protection, preservation, backup, lawful-use, development, modification, licensing, sale, release, publication, open-source release, commercialization, and enforcement rights in EC Protected Materials to the maximum extent permitted by law.

This includes, without limitation:

Continued CRS access after an Employment Change Event does not reduce, reverse, impair, or limit Quintin N. Mahan’s ownership or control of EC Protected Materials.

This section does not claim ownership of raw database records, raw CRS-owned operational records, raw customer records, raw customer relationships, independent outside source records, or third-party-owned records merely because such information is stored in EC.

29. Distress Event

A Distress Event includes, without limitation:

  1. the company ceasing ordinary business operations;
  2. the company becoming insolvent;
  3. the company being unable to pay debts as they become due;
  4. the company winding down;
  5. the company dissolving;
  6. the company liquidating;
  7. the company filing for bankruptcy;
  8. the company entering receivership;
  9. the company making an assignment for the benefit of creditors;
  10. the company selling substantially all assets;
  11. a creditor, receiver, trustee, purchaser, assignee, or third party attempting to take control of EC Protected Materials;
  12. the company attempting to seize, restrict, revoke, impair, copy, transfer, or claim ownership of EC Protected Materials;
  13. the company attempting to deny Quintin N. Mahan owner access to EC Protected Materials;
  14. the company materially breaching these Terms;
  15. the company attempting to force disclosure of EC source code, credentials, repository access, hardware control, methodology, or trade secrets;
  16. or the company attempting to continue using EC without accepted Terms or a separate written agreement.

Upon a Distress Event, Quintin N. Mahan may suspend, restrict, revoke, disable, block, terminate, preserve, secure, back up, protect, audit, export evidence from, or otherwise take lawful owner-protection actions involving EC Protected Materials.

A Distress Event does not automatically transfer ownership of raw database records, CRS-owned operational records, customer records, customer relationships, independent outside source records, or third-party-owned records to Quintin N. Mahan merely because such information is stored in EC.

30. Sale, Change of Control, or Transfer of CRS; New License Required

Any sale, transfer, merger, acquisition, ownership change, control change, reorganization, assignment, asset sale, sale of substantially all assets, transfer of goodwill, transfer of customer relationships, transfer of operational records, successor transaction, or attempted transfer of CRS or its business does not transfer any EC license, EC access right, EC software right, EC hardware right, EC infrastructure right, EC credential, EC account, EC integration, EC backup of protected materials, EC report, EC workflow, EC dashboard, EC source code, EC schema, EC data model, EC metadata system, EC methodology, EC trade secret, or EC Protected Materials right to any buyer, successor, transferee, assignee, new owner, creditor, receiver, trustee, purchaser, or third party.

CRS’s license to access EC is personal, conditional, revocable, non-exclusive, non-transferable, and non-assignable. A new owner, successor, buyer, transferee, assignee, or purchaser of CRS receives no right to access or use EC unless Quintin N. Mahan separately grants a new license in writing or through a new EC acceptance process authorized by Quintin N. Mahan.

Upon any sale, transfer, merger, acquisition, ownership change, control change, asset sale, sale of substantially all assets, successor transaction, or attempted transfer of CRS, Quintin N. Mahan may immediately revoke, suspend, restrict, condition, or terminate EC access for CRS, the buyer, the successor, the transferee, the assignee, the new owner, and all related users, service accounts, integrations, APIs, dashboards, and connected systems.

Any continued access by a buyer, successor, transferee, assignee, new owner, purchaser, creditor, receiver, trustee, or third party requires new licensure from Quintin N. Mahan. Quintin N. Mahan may approve, deny, condition, price, limit, or revoke such licensure in his sole discretion.

This section does not transfer to Quintin N. Mahan ownership of independent CRS source records, raw CRS operational records, CRS customer relationships, customer-owned records, or third-party-owned records merely because such information is stored in EC.

31. Revocation and Termination Rights

Quintin N. Mahan may immediately suspend, restrict, revoke, disable, block, or terminate EC access for any reason related to:

Revocation of access does not waive or reduce Quintin N. Mahan’s ownership, license rights, data rights, hardware rights, infrastructure rights, payment rights, confidentiality rights, or legal remedies.

32. No Unauthorized-Access Claim Against Owner

The parties acknowledge that Quintin N. Mahan is the owner, operator, developer, administrator, and rights holder of EC.

Quintin N. Mahan’s access to, possession of, retention of, backup of, export of, migration of, analysis of, maintenance of, use of, or continued control over EC, EC systems, EC databases, EC data, EC metadata, EC backups, EC logs, EC records, EC-derived data, EC-created data, EC-maintained data, EC work product, EC hardware, EC infrastructure, EC credentials, EC service accounts, EC configurations, and EC security materials shall not be treated as unauthorized access, theft, conversion, misappropriation, computer abuse, breach of duty, breach of loyalty, interference, tortious interference, or misuse when performed for lawful EC-related purposes involving EC-owned, EC-controlled, EC-administered, or EC-authorized systems, records, accounts, infrastructure, backups, or materials.

This section applies during employment, after employment, after an Employment Change Event, after a Distress Event, after sale or change of control of CRS, after refusal of these Terms, after termination of company access, and during any ownership, access, or payment dispute.

Nothing in this section authorizes unlawful access to third-party systems, systems not owned or controlled by Quintin N. Mahan, credentials not lawfully held, or independent outside source records outside EC except as permitted by law, by valid authorization, or by separate written agreement.

Nothing in this section limits non-waivable rights or claims that cannot legally be waived.

33. No Company Ownership by Use, Reliance, Benefit, Wages, Data Entry, or Sale

Company use of EC does not make EC Protected Materials a company asset.

Company reliance on EC does not make EC Protected Materials a company asset.

Company employees entering data into EC does not make EC Protected Materials a company asset.

Company officers requesting features does not make EC Protected Materials a company asset.

Company operations benefiting from EC does not make EC Protected Materials a company asset.

Company hardware connecting to EC does not make EC Protected Materials a company asset.

Company data being processed by EC does not make EC Protected Materials a company asset.

Company payment of wages, salary, reimbursement, benefits, or unrelated compensation does not make EC Protected Materials a company asset.

Company direction regarding ordinary business operations does not create company ownership of EC Protected Materials or control over EC design, code, structure, methodology, features, hardware, credentials, repository access, or owner administration.

Company sale, transfer, merger, acquisition, ownership change, control change, asset sale, or successor transaction does not make EC Protected Materials a company asset and does not transfer EC Protected Materials to a buyer, successor, transferee, assignee, or new owner.

Nothing in this section prevents CRS from asserting whatever rights it has in raw CRS-owned operational records, independent outside source records, or customer relationships. Such rights do not create ownership or control of EC Protected Materials.

EC Protected Materials remain privately owned by Quintin N. Mahan.

34. Data Export Rights

A company permitted to use EC may request a commercially reasonable export of its raw operational records in a usable format, subject to technical feasibility, security, access control, payment status, compliance with these Terms, and any separate written agreement.

Any export right does not include:

A company’s right to receive an export does not create ownership of EC Protected Materials and does not restrict Quintin N. Mahan’s right to preserve EC legal records, acceptance/decline records, certificate records, hashes, audit trails, access records, security logs, and backups of EC Protected Materials.

35. Restrictions on Users and Companies

No user or company may, without written permission from Quintin N. Mahan:

Violation of this section is a material breach of these Terms.

36. Confidentiality and Non-Disclosure

All EC source code, schemas, workflows, automations, configurations, credentials, API keys, tokens, documentation, dashboards, reports, database structures, operational logic, system architecture, EC security materials, EC metadata, EC work product, and EC Protected Materials materials are confidential and proprietary.

No user or company may copy, export, screenshot, scrape, reverse engineer, reproduce, transfer, disclose, publish, modify, bypass, replicate, or attempt to recreate EC or any EC material without written permission from Quintin N. Mahan.

Users and companies shall take reasonable steps to protect EC confidential information from unauthorized use, access, disclosure, copying, or transfer.

Nothing in these Terms authorizes unlawful use, disclosure, sale, or mishandling of payment card data, social security numbers, tax identification numbers, protected health information, employee payroll records, legally restricted personal information, or other legally protected data.

Quintin N. Mahan may retain and use EC data as provided in these Terms, but shall use reasonable safeguards appropriate to the sensitivity of the information.

Users shall not enter unnecessary sensitive personal information into EC unless EC is specifically configured for that purpose.

Users and companies remain responsible for ensuring that they do not enter unlawful, unnecessary, excessive, or improperly obtained data into EC.

38. Data Preservation and Backups

Quintin N. Mahan may create, maintain, retain, migrate, restore, analyze, and preserve EC backups, snapshots, exports, logs, archives, audit records, and historical data as necessary or useful for EC operation, security, continuity, enforcement, defense, business transition, customer-service continuity, system recovery, or legal compliance.

No user or company may require destruction of EC backups, EC logs, EC audit records, EC metadata, EC-derived data, EC-created records, EC-maintained records, or EC historical records except as required by applicable law or by a separate written agreement signed by Quintin N. Mahan.

39. Availability; No Guaranteed Access

EC is provided on a conditional-access basis.

Except as expressly stated in a separate written agreement signed by Quintin N. Mahan, EC is provided without any guaranteed uptime, availability, support level, response time, feature commitment, roadmap commitment, or continued access obligation.

Quintin N. Mahan may modify, disable, replace, suspend, restrict, or discontinue EC features, modules, dashboards, reports, workflows, automations, integrations, APIs, or access methods at any time.

40. No Waiver by Delay or Continued Operation

No delay, failure to enforce, continued access, continued operation, continued employment, continued business use, continued support, or temporary permission shall waive Quintin N. Mahan’s rights under these Terms.

Any waiver must be in a separate written agreement signed by Quintin N. Mahan.

A waiver of one breach is not a waiver of any other breach.

41. Modification of Terms

Quintin N. Mahan reserves the sole and exclusive right to amend, modify, replace, add to, remove from, suspend, or update these Terms at any time, in his sole discretion, without requiring prior authorization, approval, consent, vote, signature, or agreement from any user, company, employer, officer, supervisor, employee, contractor, customer, vendor, or third party.

Updated Terms become effective upon posting within EC, presentation at login, delivery by electronic notice, publication in the EC Terms page, or continued availability through EC.

For material updates, EC may provide notice by login presentation, Legal page update, banner, electronic notice, required renewed acceptance, or other reasonable EC notice method selected by Quintin N. Mahan.

Accessing, logging into, viewing, using, entering data into, importing data into, uploading files into, relying on, requesting features for, configuring, testing, connecting to, or continuing to use EC after updated Terms are posted or made available constitutes acceptance of the updated Terms to the maximum extent permitted by law.

Any user or company that does not agree to updated Terms must immediately stop using EC, must not continue access, and may have access suspended or revoked.

No user, company, employer, officer, supervisor, employee, contractor, customer, vendor, or third party may modify these Terms, reject selected provisions, impose alternate terms, or condition EC use on different terms unless Quintin N. Mahan signs a separate written agreement expressly approving that modification.

The version of the Terms posted, presented, or made available by EC at the time of access or use controls that access or use.

42. Fees, Costs, and Collection

If Quintin N. Mahan must enforce these Terms, collect post-employment service fees, stop unauthorized access, defend EC ownership, preserve EC data, recover EC hardware, prevent misuse, respond to a claim arising from a user’s or company’s breach, or obtain injunctive relief, Quintin N. Mahan may recover all available costs, expenses, attorney fees, expert fees, filing fees, service fees, collection costs, and other enforcement costs to the maximum extent permitted by law.

Post-employment service fees accrue monthly in advance.

Unpaid fees may result in immediate access suspension or termination.

Suspension or termination for nonpayment does not waive the unpaid fees.

43. Indemnification

To the maximum extent permitted by law, any company using EC shall defend, indemnify, and hold harmless Quintin N. Mahan from claims, losses, damages, liabilities, costs, expenses, attorney fees, expert fees, penalties, and demands arising from:

This indemnification applies only to the extent permitted by law and does not require indemnification for Quintin N. Mahan’s own intentional unlawful conduct, willful misconduct, or other liability that cannot legally be shifted or waived.

44. Injunctive Relief

Quintin N. Mahan may seek temporary, preliminary, emergency, or permanent injunctive relief for any actual or threatened:

The parties agree that unauthorized access to EC, attempted copying of EC, attempted seizure of EC, misuse of EC data, disclosure of EC confidential information, interference with EC access, or destruction of EC records may cause irreparable harm for which money damages may be inadequate.

45. New Mexico Law; Torrance County State-Court Venue

These Terms, EC access, EC use, EC ownership, EC data rights, EC work product rights, EC hardware rights, EC licensing, EC fees, EC suspension, EC termination, EC-derived data, EC-created data, EC-maintained data, user contributions, company contributions, and any dispute arising out of or relating to EC shall be governed by New Mexico law, without regard to conflict-of-law rules.

To the fullest extent permitted by law, any dispute, claim, controversy, demand, lawsuit, petition, request for injunctive relief, request for declaratory relief, collection action, ownership dispute, data-rights dispute, access dispute, post-employment access dispute, nonpayment dispute, or other legal proceeding arising out of or relating to EC or these Terms shall be brought exclusively in the appropriate New Mexico state court serving Torrance County, New Mexico.

The parties agree that proper venue shall be Torrance County, New Mexico, including the Seventh Judicial District Court, Torrance County, New Mexico, or the appropriate Torrance County limited-jurisdiction court if the matter falls within that court’s jurisdiction.

Each user and company using EC consents to personal jurisdiction and venue in the New Mexico state courts serving Torrance County, New Mexico, and waives any objection based on inconvenient forum, improper venue, lack of personal jurisdiction, or preference for another county, state, federal court, arbitration forum, administrative forum, or private dispute-resolution forum, except where such waiver is prohibited by law.

No EC dispute shall be required to proceed in arbitration unless Quintin N. Mahan expressly agrees in a separate written agreement signed by him.

To the fullest extent permitted by law, each user and company waives any right to remove, transfer, compel arbitration, or relocate an EC-related dispute away from the New Mexico state courts serving Torrance County, New Mexico.

46. Acknowledgments; Estoppel; No Inconsistent Position

By accepting these Terms, signing in, checking the Terms acceptance checkbox, accessing EC, using EC, relying on EC, or continuing to use EC after notice of these Terms, each user and company acknowledges and agrees that:

Refusal or decline of these Terms may be logged as evidence of notice, refusal, non-acceptance, access revocation, and lack of authorization to continue using EC, but refusal or decline alone is not treated as an admission of all Terms by the declining party.

To the maximum extent permitted by law, each user and company that accepts, accesses, uses, relies on, or continues to use EC after notice of these Terms is estopped from taking any position inconsistent with these acknowledgments in any lawsuit, administrative proceeding, employment dispute, ownership dispute, access dispute, source-code dispute, credential dispute, injunction proceeding, arbitration, bankruptcy, receivership, sale, transfer, or successor transaction.

47. Covenant Not to Sue Over EC Protected Materials Ownership, Possession, or Retention

To the maximum extent permitted by law, each user and company that accepts, accesses, uses, relies on, or continues to use EC after notice of these Terms covenants not to sue, threaten to sue, assert, assist, encourage, assign, transfer, support, or maintain any claim against Quintin N. Mahan based on positions inconsistent with the accepted EC access terms, including claims based on:

This covenant does not prevent claims based solely on intentional unlawful conduct, willful misconduct, non-waivable statutory rights, lawful process, or independent outside source-record rights, provided such claims do not seek to seize, copy, clone, transfer, control, or impair EC Protected Materials contrary to these Terms.

This covenant does not prevent CRS from asserting whatever rights it has in raw CRS-owned operational records, independent outside source records, or customer relationships, provided CRS does not claim ownership or control of EC Protected Materials.

If any user or company brings a claim in violation of this covenant, Quintin N. Mahan may use these Terms as a complete or partial defense and may seek dismissal, injunctive relief, attorney fees, costs, sanctions where available, and all other relief permitted by law.

48. Acceptance Logs, Audit Trails, and Electronic Evidence

EC acceptance records, login records, audit trails, access logs, email notices, Terms hashes, Terms version records, IP address records, user-agent records, database records, system logs, backup records, export records, and related electronic records are EC business records and may be used as evidence of notice, access, use, acceptance, refusal, authority, identity, attribution, timing, and agreement.

Each user and company agrees that EC may retain these records for evidentiary, audit, enforcement, security, ownership, access-control, data-preservation, and dispute-defense purposes.

Each user and company agrees not to object to the admissibility, authenticity, attribution, or evidentiary use of EC acceptance records, login records, audit trails, Terms version records, Terms hashes, or related electronic records solely because they are electronic, system-generated, maintained by EC, or retained by Quintin N. Mahan.

Each user and company agrees that a Terms hash, version record, timestamp, user account, IP address, user agent, checkbox record, email notice, and login record may be used together to prove the Terms presented and accepted or refused.

49. Independent Consideration and Bargained-For Exchange

The parties acknowledge that these Terms are supported by adequate and independent consideration, including but not limited to:

The parties agree that EC access is optional and that any user or company unwilling to accept these Terms may avoid them by not signing in, not accessing, and not using EC.

50. Preservation, Litigation Hold, and No Destruction of EC Evidence

Upon any dispute, threatened dispute, employment change, access revocation, refusal of Terms, CRS sale or change of control, CRS dissolution, data dispute, ownership dispute, or anticipated litigation involving EC, each user and company shall preserve all EC-related records in their possession, custody, or control.

No user or company may delete, alter, wipe, corrupt, destroy, conceal, encrypt against the Owner, transfer, overwrite, reset, rotate, disable, revoke, or impair EC data, EC credentials, EC logs, EC backups, EC exports, EC audit trails, EC acceptance records, EC emails, EC service accounts, EC integrations, EC infrastructure, EC hardware, or EC-related evidence.

Any attempt to destroy, alter, conceal, disable, revoke, or impair EC records, EC credentials, EC logs, EC backups, EC acceptance records, or EC-related evidence is a material breach of these Terms and may support injunctive relief, sanctions where available, adverse inference, attorney fees, costs, and any other remedy permitted by law.

51. No Self-Help; No Seizure; No Lockout

No user or company may use self-help to seize, copy, disable, lock out, transfer, claim, migrate, replace, interfere with, or take control of EC, EC source code, EC databases, EC backups, EC hardware, EC infrastructure, EC credentials, EC service accounts, EC integrations, EC data, EC metadata, EC reports, EC dashboards, EC workflows, EC automations, or the EC Protected Materials.

Any dispute regarding EC must be resolved under these Terms and in the court specified by these Terms.

Pending resolution, Quintin N. Mahan retains control of EC, EC credentials, EC infrastructure, EC backups, EC source code, EC systems, and the EC Protected Materials to the maximum extent permitted by law.

52. Jury Trial Waiver

To the maximum extent permitted by law, each user and company knowingly, voluntarily, and intentionally waives any right to trial by jury in any dispute, claim, lawsuit, petition, counterclaim, cross-claim, collection action, injunction proceeding, declaratory action, ownership dispute, data-rights dispute, access dispute, employment-related EC dispute, post-employment access dispute, nonpayment dispute, or other legal proceeding arising out of or relating to EC or these Terms.

Any such dispute shall be tried to the court and not to a jury to the maximum extent permitted by law.

If this waiver is found unenforceable as to any claim, the remaining Terms remain enforceable.

53. Cumulative Remedies; Specific Performance

All remedies under these Terms are cumulative and not exclusive.

Quintin N. Mahan may seek specific performance, declaratory relief, injunctive relief, damages, fees, costs, collection remedies, access termination, account disablement, credential rotation, data preservation, hardware recovery, and any other remedy available at law or equity.

The exercise of one remedy does not waive any other remedy.

54. No Reliance on Oral Statements or Contrary Instructions

No user or company may rely on any oral statement, supervisor instruction, company policy, employee handbook, operational custom, payroll practice, reimbursement, meeting discussion, email, chat message, text message, course of dealing, or informal understanding to claim ownership of EC or to alter these Terms.

Only a separate written agreement signed by Quintin N. Mahan may modify EC ownership, EC data rights, EC work product rights, EC hardware rights, EC licensing, EC access, or EC Protected Materials rights.

55. Opportunity to Decline; Voluntary Use

Use of EC is voluntary and conditional.

Any user or company that does not agree to these Terms may avoid these Terms by not signing in, not accessing EC, not using EC, and not relying on EC.

Continued access, sign-in, use, or reliance after notice of these Terms is voluntary acceptance of these Terms.

Refusal, rejection, non-acceptance, objection, attempted modification, attempted selective acceptance, or attempted use without acceptance triggers the access restrictions, ownership acknowledgments, and existing-data vesting provisions stated in these Terms.

56. Severability and Reformation

If any provision of these Terms is found invalid, unlawful, overbroad, or unenforceable, that provision shall be limited, narrowed, reformed, or severed to the minimum extent necessary to make the remaining Terms enforceable.

The invalidity of one provision does not invalidate the rest of the Terms.

The intent of these Terms is to give Quintin N. Mahan the maximum lawful ownership, license, control, access, retention, use, enforcement, evidentiary, and protection rights over EC, EC data, EC work product, EC infrastructure, EC hardware, EC logs, EC acceptance records, and EC-related materials.

57. Entire Agreement for EC Access

These Terms constitute the entire agreement governing EC access and use unless modified by a separate written agreement signed by Quintin N. Mahan.

No verbal statement, supervisor instruction, company policy, employee handbook, operational practice, payment, reimbursement, feature request, continued business use, company custom, or course of dealing shall modify these Terms or transfer ownership of EC.

Any exception to these Terms must be in a separate written agreement signed by Quintin N. Mahan.

58. Company Acceptance

By signing, checking a box, electronically accepting, signing in, accessing, using, or continuing to use EC, the company representative certifies that they are authorized to accept these Terms on behalf of the company.

The company agrees that EC Protected Materials are privately owned by Quintin N. Mahan, that company access is conditional, that use is voluntary, and that all EC ownership, access, business-hours work, paid-labor, work product, hardware, credential, feature-control, methodology, source-code, sale/change-of-control, confidentiality, evidentiary, estoppel, covenant-not-to-sue, modification, venue, and enforcement provisions apply to the company and its users.

The company further agrees that acceptance or refusal of these Terms does not transfer EC Protected Materials to CRS, does not give CRS control over EC Protected Materials, does not require disclosure of EC source code, does not require disclosure of EC credentials, and does not restrict Quintin N. Mahan’s right to modify, develop, implement, remove, publish, license, sell, release, open-source, or commercialize EC code, EC structure, EC methodology, EC hardware, or other EC Protected Materials.

The company also agrees that any sale, transfer, merger, acquisition, ownership change, control change, asset sale, or successor transaction does not transfer EC access or any EC Protected Materials rights to a buyer, successor, transferee, assignee, new owner, or third party.

This section does not claim ownership of raw database records, raw CRS-owned operational records, independent outside source records, customer records, customer relationships, or third-party-owned records merely because such information is stored in EC.

59. Individual User Acceptance

By signing, checking a box, clicking, logging in, accessing, or continuing to use EC, the individual user agrees to these Terms personally.

The individual user agrees that EC Protected Materials are privately owned by Quintin N. Mahan, that EC access is conditional, that use without agreement is not authorized, and that acceptance or refusal of these Terms does not transfer EC Protected Materials to CRS or any user.

This section does not claim ownership of raw database records, raw CRS-owned operational records, independent outside source records, customer records, customer relationships, or third-party-owned records merely because such information is stored in EC.

60. Login Notice and Checkbox Language

The cloned Terms-acceptance sign-in page should display Terms notice in clear language near the sign-in controls.

Required red notice text, displayed immediately above the checkbox until the checkbox is checked:

You must agree to the terms and conditions before signing in.

Required checkbox wording:

I agree to the Terms and Conditions.

The words “Terms and Conditions” must link to the active Terms and Conditions page.

The sign-in button must remain disabled until the checkbox is checked.

Once the checkbox is checked, the red warning text should clear, hide, or otherwise stop displaying.

The ordinary sign-in page may omit the checkbox for users whose current acceptance is already valid for the active Terms version/hash.

When the active Terms version/hash changes, or when the user has no current acceptance or has declined, EC may redirect the user to the cloned Terms-acceptance sign-in page until acceptance is completed.

The checkbox itself is not the final legal record. The legal record is the server-side acceptance record created only after successful authentication.

61. Hardware Schedule

A Hardware Schedule may be attached to or maintained inside EC as an exhibit to these Terms.

The Hardware Schedule may identify EC hardware, infrastructure, accounts, credentials, integrations, connected systems, service accounts, storage, backup systems, servers, modems, routers, Raspberry Pis, displays, phones, tablets, virtual machines, and other EC-controlled resources.

Items listed in the Hardware Schedule are presumed EC property or EC-controlled infrastructure unless expressly excluded in a separate written agreement signed by Quintin N. Mahan.

62. Survival

The provisions of these Terms that by their nature should survive termination, refusal, non-acceptance, access revocation, employment termination, CRS dissolution, CRS sale, CRS change of control, nonpayment, or discontinuation of EC use shall survive.

Surviving provisions include, without limitation:

No survival provision converts raw database records, raw CRS-owned operational records, independent outside source records, customer records, customer relationships, or third-party-owned records into EC Protected Materials merely because such information is stored in EC.

63. Data Contribution Authority and Warranty

Each user and company represents and warrants that they have the right, authority, permission, and lawful basis to enter, import, upload, transmit, connect, synchronize, process, maintain, correct, structure, or permit data to exist in EC.

Each user and company represents and warrants that they have the right and authority to grant, assign, confirm, acknowledge, or license the EC-related rights stated in these Terms.

Each user and company is responsible for ensuring that data entered into EC is accurate enough for the user’s intended operational use, lawfully obtained, lawfully provided, and not entered in violation of any legal restriction known to that user or company.

If any user or company lacked authority to enter, import, upload, transmit, connect, synchronize, process, maintain, correct, structure, or permit data to exist in EC, the user and company remain responsible for the consequences of that unauthorized contribution and shall not use their own lack of authority as a basis to claim ownership of EC, demand surrender of EC, impair EC access, impair EC backups, or defeat Quintin N. Mahan’s EC ownership, retention, preservation, and defense rights.

64. No Challenge to EC Protected Materials Ownership and Control

To the maximum extent permitted by law, each user and company that accepts, accesses, uses, relies on, or continues to use EC after notice of these Terms agrees not to challenge, contest, impair, deny, interfere with, or assist any third party in challenging Quintin N. Mahan’s ownership, possession, control, retention, backup, preservation, use, development, modification, licensing, sale, release, publication, open-source release, commercialization, or operation of:

This section does not prevent a company from asserting whatever rights it has in raw CRS-owned operational records, independent source records, customer records, customer relationships, or third-party-owned records, provided the company does not claim ownership or control of EC Protected Materials.

This section does not waive non-waivable rights or bar lawful process.

65. Contractual Claim Deadline

To the maximum extent permitted by law, any claim, lawsuit, petition, demand, counterclaim, cross-claim, or proceeding against Quintin N. Mahan arising out of or relating to EC, these Terms, EC access, EC ownership, EC data rights, EC work product, EC hardware, EC credentials, EC fees, EC suspension, EC termination, EC-derived data, EC-created data, EC-maintained data, EC backups, EC logs, EC acceptance records, or the EC Protected Materials must be brought within one year after the event giving rise to the claim.

Any such claim not brought within one year is waived, released, and barred to the maximum extent permitted by law.

This section does not shorten any claim deadline where shortening is prohibited by law, and it does not limit Quintin N. Mahan’s right to enforce EC ownership, EC data rights, confidentiality, access restrictions, payment obligations, preservation obligations, or injunctive relief.

66. Limitation of Liability; As-Is Access

EC is provided on an as-is, as-available, conditional-access basis unless a separate written agreement signed by Quintin N. Mahan states otherwise.

To the maximum extent permitted by law, Quintin N. Mahan shall not be liable for indirect, incidental, special, consequential, exemplary, punitive, reliance, expectation, business-interruption, lost-profit, lost-revenue, lost-goodwill, lost-data, lost-opportunity, replacement-system, cover, migration, conversion, or similar damages arising out of or relating to EC, these Terms, EC access, EC suspension, EC termination, EC changes, EC ownership, EC data rights, EC export limitations, EC availability, EC errors, EC downtime, EC security measures, EC revocation, or discontinuation of EC use.

To the maximum extent permitted by law, Quintin N. Mahan’s total liability for any EC-related claim shall not exceed the amount actually paid to Quintin N. Mahan specifically for EC platform access during the three months immediately preceding the event giving rise to the claim.

If no separate EC platform fee was paid to Quintin N. Mahan during that period, the liability cap is zero dollars to the maximum extent permitted by law.

Nothing in this section limits liability that cannot legally be limited, including liability for intentional unlawful conduct, willful misconduct, or other non-waivable obligations to the extent such liability cannot be excluded or capped by law.

This limitation does not limit Quintin N. Mahan’s right to seek fees, costs, collection, injunctive relief, specific performance, data preservation, hardware recovery, access termination, or enforcement of EC ownership and EC Protected Materials rights.

67. Decline Records and Access Revocation Evidence

If a user selects a decline option, refuses the Terms, attempts to proceed without checking the Terms acceptance checkbox, or otherwise rejects the Terms, EC may create a decline or refusal record.

The decline or refusal record may include:

Such records may be used to prove notice, refusal, non-authorization, access revocation, and lack of permission to use EC.

68. Order of Precedence

If any EC screen, email, policy, handbook, supervisor instruction, workflow note, help text, documentation, or operational practice conflicts with these Terms, these Terms control unless Quintin N. Mahan signs a separate written agreement expressly modifying these Terms.

If any shorter login notice or summary conflicts with the full Terms, the full Terms control.

The Conspicuous Material Terms Summary is provided for notice and explanation, but the full Terms control.

69. Company Authority Acceptance by Authorized Account

If a user account is designated in EC as having company authority, then that user’s acceptance of these Terms after authenticated sign-in may be recorded as both individual acceptance and company-level acceptance on behalf of the company.

Company-level acceptance shall be based on the authenticated server-side user record, not merely on an email address typed into the login form.

A company-authority user who signs in, checks the Terms acceptance checkbox, and continues into EC represents and warrants that they are authorized to bind the company to these Terms.

For a company-authority user, EC may create two separate acceptance records from the same authenticated checkbox acceptance event:

  1. an individual acceptance record for the user personally; and
  2. a company-level acceptance record for the company.

For a company-authority user, EC may send two separate acceptance notices to Quintin N. Mahan:

  1. an individual acceptance notice; and
  2. a company-level acceptance notice.

Each acceptance notice may include the full Terms accepted, the Terms version, Terms hash, root Legal index hash, Policy Library index hash, full Legal bundle hash where practical, acceptance timestamp, user identity, company identity, authority level, IP address, user agent, checkbox text, acceptance method, and related audit metadata.

For users who are not designated in EC as company-authority users, EC may record only individual acceptance unless Quintin N. Mahan separately authorizes company-level acceptance.

70. System-Generated Exhibit A; Company Officer Acceptance Certificate

If an authenticated company-authority user accepts these Terms, EC may automatically generate Exhibit A — Company Officer Acceptance Certificate from the company-level acceptance record.

For CRS, if Kendra’s authenticated EC user account is marked server-side as a company-authority account, then her authenticated sign-in and Terms checkbox acceptance may generate:

  1. an individual acceptance record for Kendra personally;
  2. a company-level acceptance record for Cash Register Systems, Inc.; and
  3. Exhibit A — Company Officer Acceptance Certificate.

Exhibit A may include, without limitation:

Company-level acceptance and Exhibit A generation shall be based on the authenticated server-side user record, not merely on an email address typed into the login form.

A company-authority user who signs in, checks the Terms acceptance checkbox, and continues into EC represents and warrants that they are authorized to bind the company to these Terms.

The generated Exhibit A record may be used as evidence of company-level notice, acceptance, authority, assent, Terms version, Terms hash, acceptance timing, and the material terms accepted.

71. Acceptance, Decline, Certificate, and Warning Emails

EC may generate email notices for acceptance, decline, company acceptance, certificate creation, owner notification, day-30 warning, day-31 lockout, restoration, owner LOCKOUT, and related legal/audit events.

Except for day-30 and day-31 warning emails and any expressly specified restoration warning layout, acceptance/decline/certificate/owner-notification emails should use Google Workspace service credentials controlled by Quintin N. Mahan.

For acceptance, decline, certificate, and owner-notification functions, the email envelope should be:

FROM: qmahan@crsabq.com
TO: mahanquintin@gmail.com
CC: none
BCC: none
MAIL TRANSPORT: Google Workspace service credentials

For certificate emails, the email body must not state or imply mailbox cleanup, sent-copy cleanup, deletion, purging, removal, or internal message-retention handling.

Certificate email body must include this line:

Attached Certificate of Acceptance for EC Terms and Conditions for: {{ username }}

Certificate emails must attach the generated PDF certificate.

For ordinary individual user acceptance, attach the generated individual acceptance certificate PDF.

For Kendra or Chuck company-authority acceptance, attach both generated certificates:

For certificate emails, the email body must include the stored EC database/audit output for the acceptance event.

At minimum, the stored DB/audit output should include, where applicable:

The Google Workspace service credentials must be used only for authorized EC legal/audit/certificate/owner-notification delivery.

EC may perform internal sent-message copy cleanup for qmahan@crsabq.com after sending, to the extent technically available through the Google Workspace service credential implementation. That internal cleanup must not be described in the email body, email subject, certificate PDF, or DB output sent to mahanquintin@gmail.com.

Internal sent-message copy cleanup must not delete the EC certificate record, EC acceptance record, EC decline record, generated certificate PDF, certificate hash, Terms hash, incorporated bundle hash, audit log, or owner-controlled EC legal/audit evidence.

Day-30 and day-31 company-acceptance warning emails must remain in the original Zoho layout/transport specified in the active Terms gate and owner lockout addendum.

If Google Workspace service credential email delivery fails for certificate/acceptance/decline/owner-notification functions, EC may queue an owner-only local notification/audit record for direct owner review and should not silently discard the event.

No CC or BCC should be used unless Quintin N. Mahan later signs a separate written instruction.

72. Continuous Legal Page Availability and Versioned Terms Records Inside EC

Employee Center shall maintain a general Legal page inside EC.

The intended Legal hub URL is:

/legal

The Legal page may list the current Employee Center Terms and Conditions and may later list additional policies, including cookie policies, privacy notices, acceptable-use policies, data policies, security notices, copyright notices, open-source notices, or other EC legal/policy documents.

The intended current Terms URL is:

/legal/terms-and-conditions

Before acceptance or before sign-in completion, the current active Terms shall be available from the EC login page, Terms acceptance area, or Legal page when a user is required to accept the current active Terms version.

After acceptance, the Legal page shall be available from inside EC through the user Profile page, including a Legal link or section at the bottom of the Profile page. The Profile page is the required authenticated location because every EC user has access to that page.

The Legal page shall link to the current active Terms and Conditions page.

The current Terms link shall display only the most recent active Terms version.

Older Terms versions shall not be overwritten or deleted. Older Terms versions shall remain stored in Postgres for audit, evidence, acceptance-record review, version comparison, and owner/admin legal review.

EC may provide owner/admin access to historical Terms versions, prior hashes, prior effective dates, generated snapshots, and acceptance records. EC may also allow a user to review the exact Terms version previously accepted by that user from the Profile page, Legal page, or legal acceptance record, if Quintin N. Mahan enables that feature.

The purpose of this section is to provide continuing notice and prevent any user or company from claiming that EC legal documents, including the Terms, were hidden, unavailable, inaccessible, or not reasonably available for review after acceptance.

Temporary downtime, maintenance, network interruption, user-side access problems, browser issues, device issues, account lockout caused by refusal or non-acceptance, or other temporary technical limitations do not waive the Terms, EC ownership, EC Protected Materials rights, acceptance records, decline records, access restrictions, or any rights reserved by Quintin N. Mahan.

Each EC acceptance record may store the Legal URL, Terms URL, Terms version, Terms effective date, Terms SHA-256 hash, and full Terms snapshot accepted.

Every EC page shall display a footer containing a copyright notice.

The required footer text is:

© 2026 Quintin N. Mahan. All rights reserved.

The footer may also include:

Employee Center is privately owned by Quintin N. Mahan.

The footer shall appear on all pages using the EC layout, including dashboards, admin pages, reports, tasks, timecards, directory pages, call logs, service reports, legal pages, profile pages, and other authenticated EC pages.

The footer notice is intended to provide continuing notice of copyright, ownership, and reservation of rights.

The footer is separate from the post-acceptance legal-document access location. After acceptance, the authenticated legal-document access location is the user Profile page, including a Legal link or section at the bottom of the Profile page that points to /legal.

A missing footer on an isolated page, print view, exported file, email rendering, API response, mobile view, temporary error page, or technical exception does not waive Quintin N. Mahan’s copyright, ownership, EC Protected Materials rights, Terms, or reserved rights.

All rights in EC are reserved by Quintin N. Mahan.

No copyright notice, missing notice, abbreviated notice, formatting variation, footer placement, link placement, or display issue waives Quintin N. Mahan’s ownership, copyright, data, work product, infrastructure, credential, backup, retention, access-control, or EC Protected Materials rights.

EC users and companies acknowledge that EC is proprietary, privately owned, and provided only under conditional access.

75. Acceptance State, Hash Changes, and Sign-In Routing

EC may hide or omit the Terms checkbox on the ordinary sign-in page when the user has a current valid acceptance for the active Terms version/hash.

EC may redirect a user to the cloned Terms-acceptance sign-in page when:

A user may not reach normal EC operational pages until the active Terms acceptance requirement is satisfied.

The cloned Terms-acceptance sign-in page may preserve the ordinary sign-in layout while adding the red warning text, Terms link, checkbox, disabled sign-in button behavior, and Decline button.

After successful authentication and acceptance, EC should route the user into the normal EC application or back to the ordinary sign-in/access flow.

No acceptance means no EC access.

76. Acceptance Certificates; PDF Records; Certificate Hashes

EC may generate an acceptance certificate for each Terms acceptance event.

For each individual user acceptance, EC may generate an individual acceptance database record, certificate database record, PDF certificate, certificate text hash, certificate PDF hash, Terms snapshot hash, and audit metadata.

For a company-authority user acceptance, EC may additionally generate a company-level acceptance database record, Exhibit A, company-level acceptance certificate PDF, certificate hashes, Terms snapshot hash, and audit metadata.

The certificate PDF and certificate database row preserve evidence of notice, acceptance, authority, Terms version, Terms hash, accepted text, acceptance timing, and EC-generated proof of acceptance.

Certificate emails must attach the generated PDF certificate.

For Kendra or Chuck company-authority acceptance, EC must generate and attach two certificate PDFs to the owner-directed certificate email: one individual acceptance certificate and one company acceptance certificate.

Certificate emails must include the stored DB/audit output for the acceptance event, including Terms version, Terms hash, incorporated legal/policy bundle hash, active addendum hash, acceptance record IDs, certificate IDs, certificate PDF hashes, timestamp, IP address, user agent, checkbox text, Terms URL, and audit event ID.

After authenticated access, EC may display certificate links from the Legal page, Terms page, or Profile page.

Each authenticated user may view the current company-level acceptance certificate / Exhibit A for Cash Register Systems, Inc., if one exists, and that user’s own individual Terms acceptance certificate.

A normal user shall not view another individual user’s certificate unless Quintin N. Mahan grants owner/admin access.

Owner/admin users may view all company-level certificates, individual certificates, acceptance records, decline records, Terms versions, hashes, generated PDFs, emails, and audit metadata.

Employee Center (“EC”) includes a Legal hub and Policy Library that are incorporated into these Terms and Conditions by reference.

By accepting these Terms, accessing EC, continuing to use EC after notice, or using an authenticated EC account, the user agrees to the current active versions of:

The Legal hub is available at:

/legal

The Policy Library is available at:

/legal/policies

The current active Terms are available at:

/legal/terms-and-conditions

The Legal hub and Policy Library may include, without limitation:

EC may update, add, remove, revise, replace, reorganize, archive, or republish Legal documents and Policy Library documents at any time.

Material updates may become effective upon posting, login presentation, electronic notice, Legal page update, Policy Library update, required renewed acceptance, or continued use after notice, depending on the nature of the update and the method selected by Quintin N. Mahan.

Any user or company that does not agree to the current active Legal documents or Policy Library documents must stop using EC and may have access suspended or revoked.

The current active version of each document will control current access and use unless a separate written agreement signed by Quintin N. Mahan states otherwise.

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

EC may generate and retain hashes, version records, bundle indexes, certificate records, PDFs, timestamps, IP addresses, user agents, acceptance records, decline records, access records, email notices, and other evidence showing what Legal documents and Policy Library documents were active at the time of acceptance, access, use, refusal, decline, dispute, or trigger event.

EC may generate and retain:

If a Legal document, supplemental Legal document, or Policy Library document conflicts with these Terms and Conditions, these Terms and Conditions control unless a separate written agreement signed by Quintin N. Mahan expressly states otherwise.

End of Terms and Conditions.