Employee Center Support / Incident / Diagnostics 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/support-incident-notice
1. Purpose
This Support / Incident / Diagnostics Notice explains how Employee Center (“EC”) may handle support requests, incidents, diagnostics, troubleshooting, error reports, screenshots, attachments, logs, and related records.
EC is a private operational platform owned by Quintin N. Mahan. EC may collect, preserve, review, and use support and diagnostic information to operate EC, resolve issues, protect security, maintain evidence preservation and authorized transition support, preserve evidence, and enforce EC policies.
2. Scope
This Notice applies to:
- support requests;
- bug reports;
- help requests;
- service issues;
- incident reports;
- security reports;
- diagnostic records;
- screenshots;
- attachments;
- uploaded files;
- error logs;
- crash logs;
- browser information;
- device information;
- network information;
- user reports;
- admin notes;
- troubleshooting steps;
- support communications;
- incident timelines;
- investigation records;
- preservation records.
This Notice applies whether the issue is reported by a user, detected by EC, created by an integration, generated by an automation, identified by an admin, or discovered during maintenance.
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;
- AI / Automation Use Notice.
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 diagnostics, EC support records, EC logs, EC screenshots, EC attachments, EC incident records, EC backups, or the EC Protected Materials.
4. Support Records EC May Collect
EC may collect or preserve support-related information, including:
- user name;
- user email;
- role;
- company;
- module involved;
- page or route involved;
- time of report;
- description of issue;
- screenshots;
- uploaded files;
- browser type;
- device type;
- operating system;
- IP address;
- user agent;
- session metadata;
- error messages;
- stack traces;
- request IDs;
- API responses;
- affected records;
- troubleshooting notes;
- resolution notes;
- admin comments;
- follow-up actions.
5. Incident Records EC May Collect
For incidents, EC may collect or preserve additional records, including:
- incident type;
- incident timeline;
- affected users;
- affected systems;
- affected records;
- suspected cause;
- known impact;
- security events;
- access logs;
- export logs;
- API logs;
- automation logs;
- webhook logs;
- integration logs;
- backup status;
- credential status;
- containment actions;
- restoration actions;
- notifications;
- evidence records;
- legal preservation notes.
6. Screenshots and Attachments
Users may submit screenshots, files, images, PDFs, logs, or other attachments for support, diagnostics, or incident review.
Users should avoid submitting unnecessary sensitive information.
Attachments may be retained, reviewed, logged, backed up, and preserved as part of EC support, diagnostics, evidence, or legal records.
Users should not submit false, misleading, altered, malicious, or irrelevant attachments.
7. Diagnostics and Logs
EC may use diagnostics and logs to identify, troubleshoot, reproduce, resolve, or investigate issues.
Diagnostics may include:
- application logs;
- server logs;
- database logs;
- browser logs;
- API logs;
- webhook logs;
- automation logs;
- integration logs;
- authentication logs;
- session logs;
- error logs;
- security logs;
- certificate access logs;
- Terms acceptance logs;
- export/import logs;
- backup logs.
Logs may be preserved for security, troubleshooting, business operations, evidence, legal defense, enforcement, and evidence preservation and authorized transition support.
8. Support Access
Owner/admin users may access EC support and diagnostic records as needed to operate, maintain, secure, troubleshoot, audit, preserve, or defend EC.
Support access may include access to:
- user-reported issues;
- affected records;
- account metadata;
- logs;
- attachments;
- screenshots;
- integrations;
- automation records;
- certificates;
- legal records;
- backups;
- configuration;
- system status.
Support access does not transfer EC ownership or create any right to copy, seize, or control EC.
9. Security and Abuse Reports
Users should report suspected security or abuse issues promptly.
Reportable issues may include:
- unauthorized access;
- suspicious logins;
- credential exposure;
- missing or altered records;
- unexpected exports;
- suspicious certificate access;
- broken permissions;
- automation misuse;
- API misuse;
- phishing;
- malware;
- attempted lockout;
- attempted system seizure;
- attempted backup deletion;
- attempted credential takeover.
EC may investigate, preserve evidence, restrict access, rotate credentials, disable integrations, or take other protective action.
10. Troubleshooting Actions
To troubleshoot, EC may take actions including:
- reviewing logs;
- reviewing affected records;
- reproducing issues;
- checking user permissions;
- checking role configuration;
- checking integrations;
- checking automation history;
- checking API/webhook activity;
- checking device/network status;
- checking backups;
- restoring from backups;
- creating test records;
- correcting records through authorized workflows;
- disabling broken features;
- restricting access;
- rotating credentials;
- patching EC.
11. Support Communications
Support communications may occur through EC, email, chat, phone, SMS, task notes, service notes, or other approved channels.
Support communications may be logged, preserved, attached to EC records, or used for troubleshooting, evidence, legal defense, evidence preservation and authorized transition support, and policy enforcement.
12. No Guaranteed Support Availability
EC support, maintenance, troubleshooting, diagnostics, automations, integrations, and incident response are provided as available unless a separate written agreement signed by Quintin N. Mahan states otherwise.
EC may prioritize issues based on severity, security risk, customer impact, legal risk, operational impact, owner/admin judgment, or available resources.
13. Incident Response
If EC detects or suspects an incident, EC may:
- preserve logs;
- preserve affected records;
- preserve backups;
- suspend accounts;
- revoke sessions;
- rotate credentials;
- disable integrations;
- disable automations;
- restrict exports;
- restore from backups;
- create forensic copies;
- review affected records;
- notify appropriate parties where required;
- enforce EC policies;
- seek legal relief.
EC may delay or limit technical details where disclosure could increase risk, interfere with investigation, expose credentials, reveal security weaknesses, or impair EC protection.
14. Retention
Support, diagnostic, and incident records may be retained for operational, security, evidence, legal, continuity, audit, and owner/admin defense purposes.
Retained records may include:
- support tickets;
- issue reports;
- screenshots;
- attachments;
- diagnostic logs;
- incident timelines;
- resolution notes;
- error records;
- admin notes;
- investigation records;
- preserved records;
- backup references;
- communication records.
Retention may continue after the issue is resolved, after a user leaves, after access is revoked, after a dispute, or after a trigger event described in the Terms.
15. Prohibited Conduct
Users may not:
- submit false support reports;
- submit malicious files;
- conceal relevant facts;
- delete diagnostic records;
- alter screenshots;
- falsify logs;
- interfere with support review;
- block owner/admin troubleshooting access;
- misuse support channels;
- use support access to bypass permissions;
- use incident response to seize or control EC;
- use support records for harassment, retaliation, or unauthorized disclosure.
16. Changes to This Notice
Quintin N. Mahan may update this Support / Incident / Diagnostics 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.
17. 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 Support / Incident / Diagnostics Notice.