Employee Center Acceptable Use 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.0
Effective Date: June 1, 2026
Platform: Employee Center / EC
Owner: Quintin N. Mahan
Legal Hub: /legal
Policy URL: /legal/acceptable-use-policy

1. Purpose

This Acceptable Use Policy explains how Employee Center (“EC”) may and may not be used.

EC is a private operational platform owned by Quintin N. Mahan. Access to EC is conditional, limited, revocable, and governed by the Employee Center Terms and Conditions.

This policy is intended to protect EC, EC users, EC records, EC customers, EC workflows, EC infrastructure, EC credentials, EC audit records, EC certificates, EC legal records, and the EC Protected Materials.

Unauthorized access or use is prohibited.

2. Scope

This policy applies to:

• all EC users;
• all administrators;
• all company-authority users;
• all display accounts;
• all service accounts;
• all API accounts;
• all integrations;
• all automations;
• all devices accessing EC;
• and any company, employee, contractor, agent, successor, buyer, or third party using or attempting to use EC.

This policy applies whether EC is accessed through a browser, mobile device, tablet, dashboard, API, automation, webhook, service account, database connection, report, export, or integration.

3. Relationship to the Terms and Conditions

This policy works together with the Employee Center Terms and Conditions.

If this Acceptable Use Policy conflicts with the Terms and Conditions, the Terms and Conditions control unless Quintin N. Mahan signs a separate written agreement stating otherwise.

Nothing in this policy transfers ownership of EC, EC source code, EC workflows, EC reports, EC dashboards, EC automations, EC integrations, EC data structures, EC databases, EC certificates, EC legal records, EC backups, EC hardware, EC infrastructure, or the EC Protected Materials.

4. Authorized Use

Users may use EC only for authorized EC-related operational purposes.

Authorized use may include:

• viewing assigned work;
• updating tasks;
• entering timecard information;
• reviewing schedules;
• using approved dashboards;
• viewing authorized customer, company, contact, or store records;
• creating or updating service records;
• creating service notes;
• completing service reports;
• uploading authorized attachments;
• using approved call-log records;
• using approved directory records;
• reviewing approved reports;
• using approved automations;
• using approved integrations;
• reviewing the Legal page;
• reviewing Terms and policy documents;
• reviewing the company acceptance certificate;
• reviewing the user’s own individual acceptance certificate.

Users may only access the portions of EC they are authorized to access.

5. Account Security

Each user is responsible for their own EC account.

Users may not:

• share passwords;
• share login links;
• share active sessions;
• use another person’s account;
• allow another person to use their account;
• impersonate another user;
• bypass login requirements;
• bypass multi-factor, session, role, or permission controls if enabled;
• attempt to access disabled, suspended, revoked, or deleted accounts;
• attempt to access EC after declining required Terms.

If a user believes their account, password, session, device, token, or credentials were lost, stolen, exposed, misused, or compromised, the user must report it promptly.

6. Prohibited Access

Users may not access, attempt to access, or help others access any EC account, module, record, report, dashboard, route, API, file, attachment, certificate, database, system, or integration that they are not authorized to use.

Users may not bypass or attempt to bypass:

• login controls;
• role permissions;
• admin restrictions;
• company-authority restrictions;
• certificate visibility rules;
• API restrictions;
• export restrictions;
• attachment restrictions;
• dashboard restrictions;
• database restrictions;
• network restrictions;
• Terms acceptance requirements;
• decline/no-access controls.

Unauthorized access or use is prohibited.

7. Prohibited Copying, Scraping, Exporting, or Cloning

Users may not copy, scrape, bulk export, mirror, clone, download, transfer, reproduce, or retain EC records except through authorized EC workflows.

Users may not:

• scrape customer records;
• bulk copy contact lists;
• export customer, company, contact, task, timecard, service, call-log, or report data outside approved workflows;
• copy EC dashboards;
• copy EC reports;
• copy EC workflows;
• copy EC automations;
• copy EC database structures;
• copy EC source code;
• copy EC schemas;
• copy EC generated certificates;
• copy EC legal records;
• copy EC backups;
• copy EC metadata;
• copy EC audit trails;
• copy EC integrations;
• create an unauthorized mirror of EC;
• create a replacement system by copying EC.

This does not prevent authorized users from using normal EC screens, approved reports, approved exports, or authorized business workflows.

8. No Reverse Engineering or System Interference

Users may not reverse engineer, decompile, disassemble, inspect, probe, attack, interfere with, or attempt to derive EC source code, EC database design, EC schemas, EC workflows, EC automations, EC reports, EC dashboards, EC integration logic, EC API logic, EC certificate logic, or EC security logic.

Users may not:

• test EC security without authorization;
• scan EC systems without authorization;
• attempt privilege escalation;
• attempt database access outside authorized tools;
• attempt server access outside authorized tools;
• tamper with routes or requests;
• manipulate forms or API calls to bypass restrictions;
• exploit bugs;
• interfere with EC availability;
• disable EC services;
• disrupt EC automations;
• disrupt EC backups;
• interfere with EC certificates, hashes, audit logs, or legal records.

9. No Credential, Token, or Key Misuse

Users may not access, copy, export, reset, rotate, revoke, disclose, transfer, use, or interfere with EC credentials unless expressly authorized by Quintin N. Mahan.

Protected credentials include:

• passwords;
• API keys;
• OAuth tokens;
• SSH keys;
• database credentials;
• service-account credentials;
• webhook secrets;
• email integration credentials;
• Zoho credentials;
• Google credentials;
• modem/SMS credentials;
• device credentials;
• backup credentials;
• server credentials;
• repository credentials.

Users may not take or use credentials to lock out Quintin N. Mahan, seize EC, clone EC, transfer EC, disable EC, or move EC to another system.

10. No Tampering with Records

Users may not alter, falsify, delete, conceal, corrupt, backdate, manipulate, or interfere with EC records except through authorized workflows.

This includes:

• customer records;
• company records;
• contact records;
• task records;
• timecard records;
• service reports;
• call logs;
• notes;
• attachments;
• audit logs;
• metadata;
• acceptance records;
• decline records;
• certificate records;
• certificate PDFs;
• Terms versions;
• policy versions;
• generated exhibits;
• backup records;
• API logs;
• automation logs;
• security logs.

Users must not create false records, misleading records, or intentionally incomplete records.

11. No Self-Help, Seizure, or Lockout

Users and companies may not use self-help to seize, disable, transfer, copy, lock out, redirect, or take control of EC.

Prohibited self-help includes:

• taking EC credentials;
• changing EC passwords without authorization;
• revoking Quintin N. Mahan’s access;
• copying repositories;
• copying databases;
• redirecting EC domains;
• taking EC backups;
• removing EC devices;
• disabling EC servers;
• moving EC to another host;
• changing API tokens;
• deleting audit logs;
• disabling certificate generation;
• disabling Terms records;
• blocking EC owner/admin access;
• attempting to transfer EC to a buyer, successor, or third party.

Disputes must be handled through lawful process, not by technical seizure or lockout.

12. Customer, Company, and Contact Data

Users may access customer, company, contact, store, equipment, service, and operational data only for authorized EC-related purposes.

Users may not use EC data for:

• personal purposes;
• harassment;
• retaliation;
• outside sales;
• unauthorized solicitation;
• unauthorized exports;
• unauthorized transfer to another system;
• unauthorized marketing;
• personal disputes;
• identity misuse;
• credential attacks;
• non-EC business purposes.

Users must treat EC customer and operational data as confidential unless the data is clearly public or disclosure is authorized.

13. Attachments and Files

Users may upload, view, download, or use attachments only for authorized EC-related purposes.

Users may not upload:

• malware;
• spyware;
• credential harvesters;
• intentionally corrupted files;
• unlawful content;
• irrelevant personal files;
• confidential third-party material they are not authorized to provide;
• false or misleading evidence;
• files intended to disrupt EC.

Users may not delete or alter attachments to hide activity, conceal records, or impair audits, disputes, support, evidence preservation and authorized transition support, or legal preservation.

14. Automations, APIs, and Integrations

Users may use EC automations, APIs, webhooks, service accounts, and integrations only as authorized.

Users may not:

• trigger automations for unauthorized purposes;
• bypass approval workflows;
• misuse SMS commands;
• misuse API endpoints;
• send false webhook data;
• impersonate another system;
• overload EC with automated requests;
• use automations to delete or corrupt records;
• use integrations to export data without authorization;
• use service accounts for personal access;
• interfere with Zoho, Google, Google Voice, UniFi, GL.iNet, SMS/modem, or other EC integrations.

EC may log API calls, integration events, automation actions, service-account activity, webhook payloads, timestamps, IP addresses, user agents, and related metadata.

15. Reports, Dashboards, and Exports

Reports, dashboards, and exports may be used only for authorized EC-related purposes.

Users may not:

• remove ownership notices;
• republish EC reports as their own;
• copy dashboard designs;
• export reports for unauthorized use;
• distribute reports outside authorized recipients;
• use reports to build a competing system;
• use exports to bypass EC access controls;
• use reports or exports after access is revoked.

Approved exports remain subject to the Terms and this policy.

16. Legal Documents, Certificates, and Acceptance Records

Users may access EC legal documents and certificate records only as permitted by EC.

Each authenticated user may be allowed to view:

• the current company acceptance certificate, if one exists;
• that user’s own individual acceptance certificate;
• current Legal hub documents;
• current active Terms and policies.

Users may not access, copy, modify, delete, interfere with, or misuse:

• another user’s individual acceptance certificate;
• owner/admin legal records;
• Terms history records;
• acceptance records;
• decline records;
• certificate hashes;
• certificate PDFs;
• Exhibit A;
• Exhibit B;
• Exhibit C;
• generated legal exhibits;
• legal audit logs.

17. Monitoring, Logs, and Evidence

EC may monitor, log, record, audit, preserve, and review EC activity.

Logged information may include:

• user identity;
• company identity;
• role;
• authority level;
• login activity;
• session activity;
• IP address;
• user agent;
• device/browser information;
• page access;
• module access;
• record changes;
• exports;
• imports;
• API calls;
• automation activity;
• attachment activity;
• certificate views;
• Terms/policy views;
• acceptance events;
• decline events;
• errors;
• security events.

Logs may be used for security, troubleshooting, business operations, evidence preservation and authorized transition support, evidence, legal defense, enforcement, and preservation.

18. Security Issues and Reporting

Users must promptly report suspected EC security issues, including:

• account compromise;
• lost or stolen devices;
• exposed credentials;
• unauthorized access;
• suspicious exports;
• unexpected admin access;
• missing records;
• altered records;
• automation misuse;
• API misuse;
• malware;
• phishing;
• attempted lockout;
• attempted system seizure.

Reports should be made to the appropriate EC owner/admin contact designated by Quintin N. Mahan.

19. Enforcement

Violation of this policy may result in:

• warning;
• account suspension;
• account revocation;
• role reduction;
• blocked login;
• blocked API access;
• blocked automation access;
• preservation of logs;
• owner/admin review;
• management notification;
• denial of future EC access;
• legal enforcement;
• injunctive relief;
• recovery of costs or fees where available.

EC may preserve evidence of violations.

20. No Waiver

Failure to immediately enforce this policy does not waive any right of Quintin N. Mahan.

Continued EC access after a violation does not create ownership, permission, waiver, or a right to continued access.

21. Changes to This Policy

Quintin N. Mahan may update this Acceptable Use Policy by publishing a new active version in EC.

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

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

22. Contact / Owner

Employee Center is owned by Quintin N. Mahan.

Legal and policy documents are available from:

/legal

The current Terms and Conditions are available from:

/legal/terms-and-conditions

End of Acceptable Use Policy.