Employee Center Updates, Features, and Releases 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/updates-features-releases-policy

1. Purpose

This Updates, Features, and Releases Policy explains how Employee Center (“EC”) updates, features, bug fixes, improvements, polishing, releases, experiments, changes, and maintenance may be planned, prioritized, developed, deployed, delayed, modified, or removed.

EC is a private operational platform owned by Quintin N. Mahan. EC is developed, maintained, updated, improved, and released under the control of Quintin N. Mahan.

This policy is intended to make clear that EC updates, feature decisions, release timing, development priorities, bug-fix priorities, polishing priorities, rollout timing, and availability of features are controlled by Quintin N. Mahan.

2. Scope

This policy applies to:

• EC features;
• EC modules;
• EC dashboards;
• EC reports;
• EC workflows;
• EC automations;
• EC integrations;
• EC APIs;
• EC database changes;
• EC legal pages;
• EC certificates;
• EC admin tools;
• EC display tools;
• EC mobile/tablet views;
• EC bug fixes;
• EC maintenance;
• EC polishing;
• EC design changes;
• EC release schedules;
• EC experiments;
• EC previews;
• EC access changes;
• EC security changes;
• EC infrastructure changes.

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.

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 source code, EC features, EC updates, EC workflows, EC reports, EC dashboards, EC automations, EC integrations, EC data structures, EC release plans, EC roadmap items, or the EC Protected Materials.

4. Owner Control of Updates

Quintin N. Mahan controls EC updates.

No user, company, officer, employee, manager, buyer, successor, customer, vendor, or third party may require, control, block, delay, force, approve, deny, dictate, or schedule EC updates unless Quintin N. Mahan signs a separate written agreement stating otherwise.

Quintin N. Mahan may choose when to:

• add a feature;
• remove a feature;
• change a feature;
• delay a feature;
• polish a feature;
• fix a bug;
• defer a bug fix;
• release an update;
• pause an update;
• roll back an update;
• test an update;
• deploy an update;
• restrict a feature;
• expand a feature;
• discontinue a feature.

5. Development Priorities

Quintin N. Mahan may choose EC development priorities at his discretion.

Priorities may include:

• new features;
• bug fixes;
• security fixes;
• data cleanup;
• performance improvements;
• UI polishing;
• workflow improvements;
• integrations;
• automations;
• reports;
• dashboards;
• legal records;
• certificates;
• database work;
• infrastructure work;
• backups;
• evidence preservation and authorized transition support;
• admin tooling;
• employee tooling;
• support tooling;
• owner/admin needs.

No user or company is entitled to have a requested feature, bug fix, workflow, report, export, automation, dashboard, integration, polish item, or improvement prioritized ahead of other EC work.

6. Feature Requests

Users may submit feature requests, suggestions, bug reports, workflow ideas, report requests, dashboard requests, automation requests, or improvement ideas.

Feature requests are suggestions only.

Submitting a request does not create:

• an obligation to build it;
• an obligation to prioritize it;
• an obligation to release it;
• an ownership right;
• a payment right;
• a delivery deadline;
• a support obligation;
• a right to control EC development.

Quintin N. Mahan may use, modify, reject, defer, combine, redesign, or ignore feature requests at his discretion.

7. No Guaranteed Feature Availability

No EC feature is guaranteed to remain available.

EC features may be:

• added;
• changed;
• limited;
• removed;
• hidden;
• disabled;
• restricted;
• replaced;
• redesigned;
• merged;
• split;
• renamed;
• moved;
• paused;
• deprecated.

A feature being available at one time does not create a right to continued availability.

8. Features May Not Be Available to All Users

EC features may be made available to some users and not others.

Feature availability may depend on:

• role;
• permission level;
• admin status;
• company-authority status;
• department;
• device type;
• account type;
• module access;
• testing status;
• training status;
• rollout group;
• security risk;
• operational need;
• owner/admin decision.

A user not receiving access to a feature does not mean the feature is unavailable, defective, discriminatory, or required to be provided to that user.

9. Staged Rollouts and Testing

EC may use staged rollouts, limited testing, internal previews, beta features, trial features, admin-only features, display-only features, hidden features, or experimental features.

Quintin N. Mahan may test features with selected users, accounts, modules, devices, locations, or environments before making them available more broadly.

Test features may be unstable, incomplete, temporary, undocumented, or subject to change.

10. Release Schedule

EC updates run on Quintin N. Mahan’s schedule.

There is no guaranteed release calendar, release frequency, deployment window, update deadline, bug-fix deadline, feature-delivery deadline, or polishing deadline unless a separate written agreement signed by Quintin N. Mahan states otherwise.

Updates may occur:

• during business hours;
• after hours;
• overnight;
• on weekends;
• during maintenance windows;
• during emergencies;
• during owner/admin availability;
• when needed for security;
• when needed for legal preservation;
• when needed for evidence preservation and authorized transition support;
• when Quintin N. Mahan decides release is appropriate.

11. Maintenance and Downtime

EC may be unavailable, degraded, limited, restarted, paused, or placed into maintenance mode for updates, maintenance, troubleshooting, backups, migrations, infrastructure changes, security changes, database changes, or incident response.

Maintenance may be scheduled or unscheduled.

EC may not always provide advance notice before maintenance, especially where immediate changes are needed for security, preservation, stability, or owner/admin control.

12. Bug Fixes

Quintin N. Mahan may decide which bugs to investigate, prioritize, fix, defer, work around, document, or leave unresolved.

Bug-fix priority may depend on:

• severity;
• security risk;
• data risk;
• customer impact;
• operational impact;
• legal risk;
• evidence impact;
• frequency;
• complexity;
• available time;
• available resources;
• dependencies;
• owner/admin judgment.

A reported bug does not create a right to immediate repair.

13. Polishing and Design Changes

EC may be polished, redesigned, reorganized, simplified, expanded, or changed over time.

Polishing and design decisions are controlled by Quintin N. Mahan.

Users may not require EC to maintain a prior layout, color, workflow, button placement, report format, dashboard format, naming convention, route, screen, or user experience.

14. Security and Emergency Updates

Quintin N. Mahan may deploy security, preservation, legal, stability, or emergency updates without advance notice.

Emergency updates may include:

• access restrictions;
• account suspensions;
• credential rotations;
• API disabling;
• webhook disabling;
• export restrictions;
• backup changes;
• database fixes;
• legal-record preservation;
• certificate preservation;
• log preservation;
• infrastructure changes;
• rollback actions;
• incident-response changes.

15. Database Changes and Migrations

EC updates may include database changes, schema changes, migrations, table changes, column changes, indexes, constraints, audit fields, legal-record fields, certificate fields, or data cleanup.

Database changes may be performed for:

• new features;
• bug fixes;
• security;
• performance;
• data integrity;
• legal records;
• acceptance certificates;
• backups;
• reports;
• integrations;
• evidence preservation and authorized transition support;
• owner/admin needs.

Users and companies may not interfere with EC database changes or require rollback except through lawful process or written agreement signed by Quintin N. Mahan.

16. Integrations and Third-Party Changes

EC integrations may change because of EC decisions or third-party changes.

Third-party services may change APIs, rate limits, authentication, pricing, availability, permissions, data formats, terms, or behavior.

Quintin N. Mahan may modify, disable, delay, replace, or remove EC integrations when third-party changes affect EC.

No user or company is entitled to continued operation of a specific third-party integration unless a separate written agreement signed by Quintin N. Mahan states otherwise.

17. Rollbacks and Reversions

Quintin N. Mahan may roll back, revert, disable, patch, or replace EC updates.

A rollback may occur because of:

• bugs;
• security risk;
• performance issues;
• data integrity concerns;
• user confusion;
• integration failure;
• broken workflows;
• incomplete testing;
• legal-preservation concerns;
• owner/admin decision.

Rollback does not waive ownership, control, or release authority.

18. No Roadmap Obligation

Any roadmap, idea list, development note, planned feature, discussion, message, task, issue, comment, or future feature reference is non-binding unless a separate written agreement signed by Quintin N. Mahan states otherwise.

Quintin N. Mahan may change the EC roadmap at any time.

19. No User Control Over Releases

Users and companies may not require EC to release, delay, block, revert, prioritize, or maintain any feature, bug fix, update, integration, dashboard, report, automation, certificate feature, legal feature, or infrastructure change.

Users and companies may not use access, management authority, employment status, company ownership, business need, customer need, or operational reliance to control EC update decisions.

20. No Service-Level Commitment

Unless a separate written agreement signed by Quintin N. Mahan states otherwise, EC does not provide a guaranteed uptime commitment, support response time, release timeline, bug-fix timeline, maintenance schedule, feature-delivery schedule, or update frequency.

21. Ownership of Updates and Improvements

All EC updates, features, fixes, improvements, releases, experiments, patches, migrations, automations, integrations, reports, dashboards, legal workflows, certificate workflows, and related work product are owned by Quintin N. Mahan unless a separate written agreement signed by Quintin N. Mahan expressly states otherwise.

No user or company receives ownership of EC updates or improvements because they requested, suggested, tested, used, relied on, paid wages during, or benefited from them.

22. Enforcement

Violation of this policy may result in:

• access restriction;
• access suspension;
• access revocation;
• owner/admin review;
• preservation of evidence;
• disabling of affected features;
• disabling of affected integrations;
• legal enforcement;
• injunctive relief;
• recovery of costs or fees where available.

23. Changes to This Policy

Quintin N. Mahan may update this Updates, Features, and Releases 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.

24. 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 Updates, Features, and Releases Policy.