Employee Center AI / Automation Use Notice

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/ai-automation-notice

1. Purpose

This AI / Automation Use Notice explains how Employee Center (“EC”) may use automations, scripts, rules, scheduled jobs, AI-assisted tools, user-triggered commands, SMS commands, device automations, and system-to-system workflows.

EC is a private operational platform owned by Quintin N. Mahan. EC may use automation to support operations, reporting, service workflows, notifications, legal records, acceptance certificates, data processing, evidence preservation and authorized transition support, and system monitoring.

This Notice is intended to provide transparency that some EC actions may be automated, logged, attributed, reviewed, preserved, or used as evidence.

2. Scope

This Notice applies to:

EC automations;
scheduled jobs;
background workers;
webhook automations;
SMS command systems;
Tasker workflows;
Shortcuts workflows;
scripts;
rule-based processing;
AI-assisted summaries;
AI-assisted classification;
AI-assisted drafting;
data normalization;
data enrichment;
report generation;
dashboard updates;
notification workflows;
certificate generation;
legal/evidence workflows;
API-triggered workflows;
service-account actions;
device-triggered actions.

This Notice applies whether an automation is triggered by a user, administrator, service account, webhook, API event, schedule, SMS message, phone event, network event, device event, file event, or system condition.

3. Relationship to Other Policies

This Notice works together with:

Employee Center Terms and Conditions;
Acceptable Use Policy;
Privacy Notice;
Cookie and Local Storage Notice;
Data Security Policy;
Data Retention and Backup Policy;
API and Integrations Policy.

If this Notice conflicts with the Employee Center Terms and Conditions, the Terms and Conditions control unless Quintin N. Mahan signs a separate written agreement stating otherwise.

Nothing in this Notice transfers ownership of EC, EC automations, EC scripts, EC workflows, EC AI-assisted outputs, EC generated records, EC logs, EC certificates, EC reports, EC dashboards, EC backups, or the EC Protected Materials.

4. Types of Automation EC May Use

EC may use automation for:

task routing;
status updates;
notifications;
reminders;
timecard processing;
call-log processing;
SMS/modem command handling;
caller ID logging;
service-report processing;
attachment handling;
directory cleanup;
data import/export;
data synchronization;
API/webhook processing;
network/device monitoring;
report generation;
dashboard updates;
legal acceptance workflows;
certificate generation;
PDF generation;
email notices;
exhibit generation;
backup jobs;
audit logging;
security monitoring;
evidence preservation and authorized transition support workflows.

5. AI-Assisted Features

EC may use AI-assisted tools or AI-assisted workflows to support authorized EC-related purposes.

AI-assisted features may include:

summaries;
draft text;
classification;
routing suggestions;
search assistance;
report assistance;
data cleanup suggestions;
duplicate detection suggestions;
service-note assistance;
customer-support assistance;
legal/evidence organization assistance;
automation logic suggestions;
troubleshooting assistance.

AI-assisted outputs may be imperfect and may require human review.

Users should not treat AI-assisted output as guaranteed accurate, complete, legally sufficient, or final unless reviewed and approved by an authorized person.

6. Human Review

Some EC automation outputs may be final system actions, while others may require human review.

Human review may be required for:

customer-facing communications;
legal records;
HR-sensitive records;
billing/accounting decisions;
customer-impacting decisions;
access revocation decisions;
data deletion decisions;
final service reports;
final statements of fact;
external notices;
enforcement actions;
unusual automation results.

EC may mark certain outputs as draft, suggested, pending review, approved, rejected, or final.

7. User-Triggered Automations

When a user triggers an automation, EC may attribute the action to that user.

User-triggered actions may include:

clicking a button;
submitting a form;
sending a command;
approving a workflow;
starting an export;
sending a report;
generating a certificate;
requesting an automation;
triggering an API action;
sending an SMS command;
using a dashboard control.

Users are responsible for automations they intentionally trigger or authorize.

8. Service-Account and System Automations

Some automations may run under service accounts, system accounts, scheduled jobs, or background workers.

These actions may be attributed to:

a service account;
an integration;
a schedule;
a webhook;
a device;
a system process;
an automation name;
an originating user where available.

Service-account or system actions may still be logged, audited, reviewed, preserved, and linked to related EC records.

9. SMS Commands and Device Automations

EC may support SMS command systems, modem workflows, Tasker workflows, Shortcuts workflows, Raspberry Pi actions, phone/caller ID events, or other device-triggered automations.

Such automations may support:

status checks;
alerts;
call-log capture;
modem/caller ID events;
network/device status;
emergency workflows;
command execution;
reporting;
diagnostics;
fallback operations.

EC may log command text, sender information, timestamps, device identifiers, processing results, errors, and linked EC actions.

Unauthorized command use is prohibited.

10. Automation Logs

EC may log automation activity.

Logs may include:

automation name;
trigger type;
triggering user;
triggering service account;
source system;
timestamp;
input data;
output data;
processing status;
error messages;
linked EC records;
affected records;
approval status;
IP address;
user agent;
device identifier;
webhook metadata;
API metadata;
SMS sender where applicable.

Automation logs may be retained for security, troubleshooting, reporting, evidence, evidence preservation and authorized transition support, legal defense, and enforcement.

11. Prohibited Automation Use

Users may not use automations to:

bypass permissions;
bypass approvals;
impersonate another user;
create false records;
alter records without authorization;
delete records without authorization;
export records without authorization;
scrape data;
overload EC;
disable EC;
interfere with logs;
interfere with legal records;
interfere with certificates;
interfere with backups;
trigger unauthorized customer communications;
run personal automations against EC without approval;
connect unauthorized devices or scripts;
use EC commands for non-EC purposes;
use automation to seize, clone, transfer, or lock out EC.

12. Data Used by Automations

Automations may use EC data, including:

user data;
customer data;
company data;
contact data;
task data;
timecard data;
service data;
call-log data;
attachment metadata;
API data;
webhook data;
audit logs;
legal records;
certificate records;
network/device data;
system status data.

Automation outputs and automation-generated records may become part of EC and the EC Protected Materials.

13. Notifications and Emails

Automations may send notifications, emails, alerts, reports, or other messages.

Legal acceptance/certificate emails are sent only as specified in the Terms and API/Integrations Policy.

For legal acceptance and certificate emails, the required default envelope is:

FROM: support@crsabq.com
TO: mahanquintin@gmail.com

Users do not receive acceptance/certificate emails by default.

14. Errors and Limitations

Automations may fail, delay, duplicate, misclassify, misroute, or produce incomplete results.

Automation errors may occur because of:

user error;
bad input data;
third-party outages;
API changes;
network issues;
credential issues;
device failures;
rate limits;
webhook errors;
SMS/modem issues;
incomplete logic;
AI-assisted output limitations;
system downtime.

Users should report suspected automation errors promptly.

15. No Guaranteed Automation Availability

EC may add, remove, change, suspend, disable, replace, or limit automations at any time.

No user or company is entitled to continued access to a specific automation, SMS command, device workflow, AI-assisted feature, dashboard action, or background job unless a separate written agreement signed by Quintin N. Mahan states otherwise.

16. Security and Abuse Protection

EC may restrict or disable automations that appear unsafe, abusive, unauthorized, excessive, misconfigured, broken, or harmful.

EC may:

rate-limit automation triggers;
block commands;
disable scripts;
revoke service-account access;
rotate credentials;
preserve logs;
require approval;
require human review;
suspend accounts;
disable integrations;
preserve evidence.

17. Changes to This Notice

Quintin N. Mahan may update this AI / Automation Use Notice 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.

18. 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 AI / Automation Use Notice.

EC AI Automation Notice