This deterministic view identifies text that differs between two frozen public releases. It adds no generated interpretation; the complete archived and current documents remain authoritative.
4 documents with section or orientation changes13 documents without section or orientation changesSeptember 10, 2026 current effective date
OperalonOS is provided by Nightvault FZE solely for legitimate business and professional use.
02
One Base Plan applies to one Workspace; plans and active Boosts renew monthly until cancelled.
03
Paid access or a paid change activates only after authenticated Stripe confirmation.
04
Customers control their data, users, connected services, instructions, and decisions made using AI Output.
V13 orientation5 evidence lines
01
OperalonOS is provided by Nightvault FZE solely for legitimate business and professional use.
02
One Base Plan applies to one Workspace; plans and active Boosts renew monthly until cancelled.
03
Paid access or a paid change activates only after authenticated Stripe confirmation.
04
Customers control their data, users, connected services, instructions, and decisions made using AI Output.
05
Recurring Base Plan and Boost Fees may be adjusted at most once in a rolling 12-month period after the first paid year, with at least 60 days' advance notice and a cancellation route.
Nightvault may adjust the recurring Base Plan Fee and any recurring Boost Fee for an affected Workspace no more than once in any rolling 12-month period and not earlier than 12 months after that Workspace's initial paid activation or its previous adjustment under this section. An adjustment must be reasonable, made in good faith, and apply only prospectively to a Billing Period beginning on or after its stated effective date. It may reflect inflation or a material change in infrastructure, third-party provider, security, compliance, personnel, support, or other operating costs reasonably required to provide, protect, support, and improve the Services. It does not change a Fee already paid or due for a Billing Period that began before the effective date.
02
Nightvault will give the Customer at least 60 days' advance notice through the Customer's designated billing contact and a durable authenticated Workspace or billing notice. The notice will identify the affected plan or Boost, the current and new recurring Fee, the percentage change, the effective date, the applicable reason category, and how to cancel before the new Fee first applies. The Customer may cancel the affected subscription before that date and avoid the adjusted recurring charge. Merely posting a new price, changing a website, or issuing an invoice is not notice under this section.
03
A price expressly fixed for a committed term in a negotiated Subscription Order will not change during that committed term unless the Order contains an exact agreed indexation formula or the parties enter a separate bilateral amendment. If the Customer's accepted Agreement does not contain this exact adjustment mechanism, or the Agreement or applicable law requires renewed consent, Nightvault will not charge the new Fee until the required affirmative acceptance or bilateral amendment is recorded. Silence, inactivity, or continued use alone is not renewed assent.
04
Taxes, Customer-requested upgrades or downgrades, newly purchased products or add-ons, usage charges separately accepted by the Customer, and project Fees under a Configuration SOW are not adjustments under this section and remain subject to their own disclosure and authorization rules.
Controlled Configuration is a separate, discretionary review path for tightly scoped changes within the supported, shared OperalonOS product. It is not custom software development, staff augmentation, managed operations, a dedicated engineering team, or a Base Plan or Boost entitlement.
02
An authorized Customer sponsor may submit a sanitized request only after the affected Workspace completes two full, consecutive, successfully paid monthly billing periods verified in Nightvault's authenticated billing record, while its paid Base Plan remains active and in good standing. Trial, free, paused, suspended, refunded, charged-back, failed, or disputed periods do not count, and the calibration period cannot be waived for an individual Customer.
03
Eligibility permits a request only. It does not guarantee review, approval, a proposal, capacity, timing, or delivery. Approved work requires a separately scoped and priced Configuration SOW that incorporates the Controlled Configuration Services Addendum. A request, discussion, estimate, payment, or ordinary subscription does not authorize project work.
Prospective protection: The Business Terms permit a reasonable recurring Base Plan or Boost Fee adjustment no more than once in a rolling 12-month period, after the first 12 paid months, with at least 60 days' advance notice. The current paid period and a negotiated fixed-price committed term remain protected. The notice must show the old and new Fee, percentage change, effective date, reason category, and cancellation route.
02
Controlled Configuration project Fees are not Base Plan or Boost adjustments. They are separately quoted and become payable only under an accepted Configuration SOW or Change Order.
A Subscription Order governs paid access to OperalonOS. It does not include or authorize Controlled Configuration. Any approved Controlled Configuration project requires its own Configuration SOW under the Controlled Configuration Services Addendum, with separate scope, Fees, acceptance criteria, authority, and commencement conditions.
This Addendum governs only Controlled Configuration Services that Nightvault FZE agrees to provide under a mutually accepted Configuration SOW. Publication, eligibility, a request, discussion, estimate, proposal, payment, or access to a feature does not require Nightvault to perform services.
02
The then-current OperalonOS Business Terms, applicable DPA and activated Security Addendum continue to govern. This Addendum controls only Controlled Configuration Services. A Configuration SOW supplies only project-specific scope, Deliverables, Fees, dates, dependencies, acceptance criteria, and authorized contacts; it cannot amend protected legal, privacy, security, liability, intellectual-property, suspension, termination, governing-law, or dispute terms.
Eligibility and discretionary reviewChanged section
The affected Workspace must complete two full, consecutive, successfully paid monthly billing periods verified in Nightvault's authenticated billing record, while its paid Base Plan is active and in good standing. Trial, free, paused, suspended, refunded, charged-back, failed, or disputed periods do not count. The calibration period cannot be waived for an individual Customer.
02
Eligibility permits an authorized Customer sponsor to submit a sanitized request for review. Nightvault may accept, decline, defer, narrow, or request clarification in its reasonable discretion. Eligibility does not guarantee review, approval, proposal, capacity, priority, timing, or delivery.
OperalonOS remains a shared, Nightvault-controlled product. Controlled Configuration does not provide a customer-specific fork, separate codebase, source-code access or license, escrow, on-premises or Customer-controlled deployment, dedicated engineering team, staff augmentation, managed operations, a separate Customer product, exclusivity, perpetual maintenance, or control of the product roadmap.
02
Nightvault retains final control over feasibility, architecture, implementation method, reusable components, security, release sequencing, testing, deployment, supportability, product evolution, suspension of unsafe work, and retirement of configurations, subject to the Agreement and mandatory law.
Sanitized request and data boundaryChanged section
A pre-SOW request must contain only the minimum business objective, current workflow, desired outcome, affected OperalonOS area, and non-sensitive constraints needed for triage. It must not contain Customer Personal Data, Customer Confidential Information, credentials, secrets, payment-card data, production exports, or re-identifiable customer records.
02
Customer Materials may be supplied only after a SOW identifies the permitted data, purpose, environment, access, retention, deletion, and security controls. A request or SOW does not expand supported data categories, providers, processing locations, certifications, audit rights, or security commitments.
No project begins until both parties accept an exact Configuration SOW and Nightvault confirms that eligibility, authority, payment authorization, scope, capacity, security, privacy, provider, environment, and release conditions are satisfied. Nightvault may refuse to commence or may contain an unsafe technical act when a required condition is absent.
02
Each SOW must identify the affected Workspace, business objective, in-scope work, exclusions, Deliverables, dependencies, responsibilities, approved environments and providers, objective acceptance criteria, review period, Fees, invoice triggers, payment terms, target dates, support classification, and authorized representatives.
Controlled Configuration is separately priced. No Base Plan or Boost Fee includes project work. Fees, taxes, invoice triggers, expenses, and payment dates are those expressly stated in the accepted SOW. Subscription Fee adjustments under the Business Terms do not reprice a Configuration SOW.
02
A change to scope, Deliverables, dates, dependencies, acceptance criteria, project Fees, or another permitted project field requires a mutually accepted written Change Order before implementation. A new preference, use case, or requirement is a change request, not a defect.
Nightvault will identify each Deliverable and provide the agreed test access and validation evidence. The Customer must test against the objective acceptance criteria during the SOW review period and give a specific written rejection describing each reproducible non-conformity. Nightvault will use commercially reasonable efforts to correct verified non-conformities within the agreed scope.
02
Silence does not amend the Agreement or waive rights. Any deemed-acceptance mechanism must be expressly stated in the SOW, be permitted by the Agreement and applicable law, and begin only after complete delivery and test access are verifiably available.
The Customer retains its rights in Customer Data and pre-existing Customer Materials. Nightvault and its licensors retain all rights in OperalonOS, software, models, workflows, interfaces, documentation, designs, tools, reusable components, methods, know-how, configurations, improvements, derivative technology, and materials of general application.
02
Unless a SOW expressly identifies a separable non-software Deliverable and an agreed assignment, each Deliverable is Nightvault technology licensed to the Customer only for authorized use with the Services during the applicable subscription. No source code, exclusivity, product fork, or restriction on Nightvault using general skills, ideas, patterns, and reusable technology is granted.
Third parties and Customer authorityChanged section
The Customer is responsible for lawful instructions and for obtaining and maintaining the permissions, accounts, licenses, notices, consents, and authority required for its systems, data, providers, personnel, and Customer-controlled actions. Nightvault does not control third-party availability, terms, APIs, or product changes.
02
Nightvault will not execute an action inside a Customer-controlled production account unless the exact actor, account, action, scope, timing, and authority required by the SOW and Agreement have been verified.
Support, compatibility, maintenance, migration, and target dates apply only as expressly stated in the SOW or applicable Service Level Schedule. No perpetual support or backward-compatibility obligation is implied.
02
Nightvault may improve, replace, migrate, suspend, or retire a configuration when reasonably required by product architecture, security, law, provider changes, or maintainability, subject to the Agreement, the SOW, applicable notice obligations, and mandatory rights.
Term, termination, and continuing termsChanged section
This Addendum applies while an incorporated SOW remains in effect. Termination or expiry of the related subscription or SOW ends the Customer's right to use affected configuration Deliverables except where the SOW expressly provides otherwise. Accrued payment obligations and provisions intended by their nature to survive continue according to the Agreement.
02
A project termination, refund, credit, suspension, or remedy is available only as expressly provided by the Agreement, this Addendum, the accepted SOW, or mandatory law. A request, estimate, invoice, or payment does not create an unstated remedy or delivery commitment.
General questions may be sent to contact@operalonos.com. The public contact form is not Controlled Configuration intake. Contractual notices must use the notice route in the Agreement or accepted SOW. Do not send credentials, secrets, payment-card information, Customer Personal Data, or production records by email or through a general inquiry.