Employee Center Uptime, Availability, and Service Continuity 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/uptime-availability-service-continuity-policy

1. Purpose

This Uptime, Availability, and Service Continuity Policy explains that Employee Center (“EC”) is provided on a good-faith, best-effort availability basis unless a separate written agreement signed by Quintin N. Mahan states otherwise.

EC is a private operational platform owned by Quintin N. Mahan. EC may be affected by hardware failures, software failures, power outages, internet outages, network outages, vendor outages, third-party service outages, maintenance, security issues, updates, backups, migrations, device failures, or other events.

This policy is intended to make clear that EC access is not guaranteed 24/7, and no uptime service-level agreement is provided unless separately agreed in writing by Quintin N. Mahan.

2. Scope

This policy applies to:

• EC application access;
• EC dashboards;
• EC reports;
• EC tasks;
• EC timecards;
• EC directory;
• EC call logs;
• EC service reports;
• EC legal pages;
• EC certificates;
• EC APIs;
• EC integrations;
• EC automations;
• EC databases;
• EC file storage;
• EC backups;
• EC admin tools;
• EC display/wallboard tools;
• EC mobile/tablet views;
• EC connected devices;
• EC network-dependent features;
• EC third-party-dependent features.

3. Relationship to Other Policies

This policy 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;
• Support / Incident / Diagnostics Notice;
• Updates, Features, and Releases Policy.

If this policy 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 policy transfers ownership of EC, EC infrastructure, EC records, EC backups, EC source code, EC integrations, EC certificates, or the EC Protected Materials.

4. No 24/7 Availability Guarantee

EC access is not guaranteed 24 hours per day, 7 days per week.

Unless a separate written agreement signed by Quintin N. Mahan states otherwise, EC does not provide:

• guaranteed uptime;
• guaranteed response time;
• guaranteed repair time;
• guaranteed recovery time;
• guaranteed restoration time;
• guaranteed backup restoration time;
• guaranteed maintenance notice;
• guaranteed after-hours support;
• guaranteed continuous access;
• guaranteed uninterrupted operation;
• guaranteed availability of any specific feature, integration, automation, report, dashboard, API, certificate view, or legal page.

EC is provided on a conditional, as-available, best-effort basis.

5. Good-Faith Best Effort

Quintin N. Mahan may make a good-faith effort to keep EC available, functional, backed up, recoverable, and usable.

Good-faith effort may include:

• monitoring EC where practical;
• maintaining backups;
• restoring from backups when appropriate;
• troubleshooting failures;
• repairing software issues;
• repairing configuration issues;
• updating EC;
• improving reliability;
• addressing security issues;
• replacing failed components when practical;
• coordinating with vendors or providers when needed;
• prioritizing issues based on severity, risk, and available resources.

Good-faith effort is not a guarantee of uninterrupted access, immediate repair, complete recovery, or specific restoration timing.

6. Possible Causes of Downtime or Degraded Service

EC may be unavailable, slow, degraded, partially functional, or temporarily inaccessible due to events including:

• hardware failure;
• server failure;
• storage failure;
• disk failure;
• memory failure;
• database failure;
• software bugs;
• application errors;
• failed updates;
• failed migrations;
• failed backups;
• corrupted files;
• corrupted records;
• power outages;
• UPS/battery failure;
• internet outages;
• ISP outages;
• router failures;
• firewall failures;
• switch failures;
• DNS problems;
• reverse proxy problems;
• Tailscale/VPN problems;
• SSL/TLS certificate problems;
• domain problems;
• vendor outages;
• Zoho outages;
• Google outages;
• Google Voice outages;
• UniFi outages;
• GL.iNet device issues;
• SMS/modem failures;
• phone/caller ID integration failures;
• API changes;
• rate limits;
• third-party authentication failures;
• cyberattacks;
• malware;
• credential compromise;
• security incidents;
• maintenance;
• updates;
• backups;
• disaster events;
• weather events;
• building issues;
• equipment relocation;
• owner/admin unavailability;
• other events outside reasonable control.

7. Partial Availability

Some EC functions may remain available while others are unavailable.

For example:

• dashboards may work while reports are degraded;
• login may work while an integration is down;
• local data may work while a third-party API is down;
• legal pages may work while exports are disabled;
• timecards may work while call logs are delayed;
• tasks may work while network integrations are unavailable;
• EC may be available internally but not externally;
• EC may be available over Tailscale but not over ordinary internet access;
• EC may be available from some devices but not others.

Partial availability does not mean EC is defective or that all EC features must be restored at the same time.

8. Maintenance and Updates

EC may be taken offline, restarted, limited, placed into maintenance mode, or degraded for maintenance, updates, backups, migrations, troubleshooting, security work, legal-preservation work, infrastructure work, or owner/admin changes.

Maintenance may be scheduled or unscheduled.

Advance notice may be provided when practical, but advance notice is not guaranteed.

Emergency maintenance may occur without notice.

9. Backups and Recovery

EC may maintain backups as described in the Data Retention and Backup Policy.

Backups are intended to support restoration, evidence preservation, continuity, and recovery where practical.

However, backups do not guarantee:

• zero data loss;
• immediate restoration;
• complete restoration;
• restoration to a specific moment;
• restoration of all files;
• restoration of every integration state;
• restoration of third-party services;
• restoration of corrupted source records;
• restoration of user-side devices or browser storage;
• restoration after every possible failure.

Recovery may depend on the nature of the failure, available backups, hardware condition, software condition, network access, third-party systems, available time, and owner/admin judgment.

10. Third-Party Dependencies

EC may depend on third-party systems and services.

These may include:

• internet service providers;
• power providers;
• DNS providers;
• domain registrars;
• SSL/TLS certificate providers;
• Zoho;
• Google Workspace;
• Google Voice;
• Gmail;
• Tailscale;
• UniFi;
• GL.iNet;
• SMS/modem providers;
• phone/caller ID systems;
• payment/accounting/customer systems;
• storage providers;
• hardware vendors;
• operating systems;
• package dependencies.

Quintin N. Mahan does not control third-party service availability, outages, policy changes, API changes, pricing changes, authentication changes, rate limits, or security incidents.

A third-party outage or change may affect EC availability or functionality.

11. Hardware and Infrastructure Limitations

EC may run on hardware, networks, servers, storage, devices, routers, Raspberry Pis, modems, phones, or other infrastructure controlled, maintained, or approved by Quintin N. Mahan.

Hardware and infrastructure can fail.

No user or company is guaranteed redundant hardware, redundant power, redundant internet, redundant storage, redundant routing, redundant compute, high availability, failover clustering, disaster recovery site, or enterprise-grade uptime unless a separate written agreement signed by Quintin N. Mahan states otherwise.

12. Power and Internet Outages

EC may be affected by power outages, internet outages, router failures, ISP failures, local network problems, wireless problems, carrier outages, or site-specific outages.

Quintin N. Mahan may attempt to restore EC access when practical, but power and internet availability are not guaranteed.

A loss of power or connectivity may prevent access to EC even if EC software itself is functioning correctly.

13. Security-Related Restrictions

EC access may be restricted, suspended, disabled, or limited for security reasons.

Security-related restrictions may occur because of:

• suspected compromise;
• credential exposure;
• suspicious login activity;
• excessive failed logins;
• suspicious exports;
• suspicious API activity;
• automation abuse;
• malware;
• phishing;
• attempted lockout;
• attempted seizure;
• attempted unauthorized database access;
• attempted backup deletion;
• legal preservation needs.

Security restrictions may affect availability but may be necessary to protect EC, EC records, users, customers, legal records, certificates, backups, and the EC Protected Materials.

14. No Liability for Unavailability

To the maximum extent permitted by law and unless a separate written agreement signed by Quintin N. Mahan states otherwise, Quintin N. Mahan is not liable for losses, damages, business interruption, lost profits, lost revenue, lost data, lost opportunity, delay, inconvenience, replacement-system costs, customer-impact costs, or other damages arising from EC downtime, degraded service, delayed service, failed integrations, unavailable features, maintenance, outages, or restoration delays.

15. User and Company Responsibility

Users and companies are responsible for maintaining reasonable fallback procedures for their own operations.

Fallback procedures may include:

• paper notes;
• offline records;
• local copies of critical information where authorized;
• phone calls;
• email;
• manual time records;
• manual service notes;
• manual customer support procedures;
• alternate communication methods;
• emergency procedures;
• third-party system access where authorized.

EC availability should not be the only procedure for time-sensitive or emergency operations unless a separate written agreement states otherwise.

16. Prioritization During Outages

During outages, degraded service, incidents, or recovery work, Quintin N. Mahan may prioritize issues based on owner/admin judgment.

Priorities may include:

• safety;
• security;
• data preservation;
• legal evidence preservation;
• backups;
• evidence preservation and authorized transition support;
• critical operations;
• authentication;
• database integrity;
• service reports;
• timecards;
• tasks;
• integrations;
• dashboards;
• reports;
• lower-priority UI polish;
• noncritical features.

No user or company is entitled to require a different priority order unless a separate written agreement signed by Quintin N. Mahan states otherwise.

17. Changes to This Policy

Quintin N. Mahan may update this Uptime, Availability, and Service Continuity 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.

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 Uptime, Availability, and Service Continuity Policy.