← All legal documentsRhodes Solutions Company / Apex Technology Division
Temporal Continuity Terms of Service
Effective October 10, 2026
Temporal Continuity | Terms of Service
Rhodes Solutions Company
Apex Technology Division
Product: Temporal Continuity
Effective date: 2026-10-10
Status: CURRENT
1. Agreement and operator
These Terms of Service ("Terms") are an agreement between Rhodes Solutions Company
LLC, acting through its Apex Technology Division ("RSC," "we," "us," or "our"), and the
person or organization accepting them ("Customer," "you," or "your"). The Apex Technology
Division is a division of Rhodes Solutions Company, not identified in these Terms as a separate
contracting legal entity
These Terms govern the hosted Temporal Continuity service, Relational Memory Substrate
("RMS"), APIs, developer console, software development kits ("SDKs"), documentation, and
applicable Beta, Test, and Production Environments. Skyline is subject to its own supplemental
Terms of Use and privacy notice.
By creating an account, accepting these Terms electronically, or using an authorized Temporal
Continuity credential, you agree to these Terms on behalf of yourself or the organization you are
authorized to represent. If you lack that authority, you must not use the service on the
organization's behalf. Any separately executed order form, data processing agreement, or
service-level agreement controls where it expressly conflicts with these Terms.
2. What Temporal Continuity provides
Temporal Continuity is a hosted continuity service that maintains authorized relational identity,
contributions, context, memories, history, provenance, lifecycle information, and associated
service records across interactions. The hosted service, rather than an SDK installation or a
browser, is authoritative for canonical relational state. A cognition provider or AI model may be
supplied or connected through an application and may change over time.
The service does not guarantee that a model's statements are accurate; that every past detail will
be projected into every future interaction; that a provider will retain a stable persona or behavior;
or that a response generated by cognition has been durably committed before the service
confirms completion. Generation and confirmed canonical persistence are distinct events.
3. Beta, Test, and Production distinctions
Beta participation. Beta is an evaluation program for authorized participants and their
applications, subject to the Beta Terms presented at enrollment and this agreement. As reflected
in the currently published Beta program, eligible participants are offered 10,000 Continuity
Credits monthly, with no automatic paid overage. Beta credits have no cash value and may be
subject to eligibility, availability, and published changes after proper notice. Beta has no
production service-level commitment unless expressly agreed in writing.
Test Environment. A Test Environment is an authorized non-production environment for
development, integration, evaluation, and validation. It may use test credentials and distinct
usage policies. A Test Environment is not a promise of isolated physical infrastructure or of zero
data retention. Do not use live customer personal information, secrets, or production-critical
workloads in testing unless the relevant permissions, safeguards, agreements, and environment
configuration have been confirmed.
Production Environment. Production is the commercially provisioned environment for
authorized live services. Plan-specific features, seats, credits, metered usage, fees, and any
separately agreed availability commitment are described at purchase, in the active plan, or in an
executed order. Production does not inherit free Beta terms merely because the same API or
SDK is used.
For all environments, a "Continuity Credit" is the applicable service unit for one continuity turn,
subject to the published metering rules. Skyline credits are governed separately by Skyline's
testing terms.
4. Accounts, authorization, and security
You must provide accurate account and billing information and maintain control of
authentication factors, API keys, tokens, and authorized users. You are responsible for activity
conducted using your authorized credentials, except to the extent caused by RSC's breach of its
legal obligations. Credentials and resources are scoped to permitted organizations, projects,
environments, permissions, and seats. You may not attempt to cross tenant boundaries, bypass
billing or rate limits, or obtain access to another customer's records. Notify us promptly of
suspected compromise.
The service is intended for adults and authorized organizations. Individuals under 18 may not
establish an account unless RSC establishes a legally compliant, expressly authorized process. It
is not designed for children under 13. Do not knowingly use it to collect children's personal
information without a separate legally compliant arrangement.
5. Permitted use and restrictions
You may use the hosted service and documented interfaces for lawful applications within your
entitlement. You must not: violate law or others' rights; upload information without a lawful
basis and required permissions; interfere with service security or availability; reverse-engineer
proprietary hosted systems except where restrictions are prohibited by law; evade service
controls; resell or re-host the service without written authority; misuse artifacts or export
mechanisms; or use the service to facilitate deceptive, dangerous, or unlawful conduct.
You remain responsible for your end users, your notices and consents, your application security,
your model/provider selection, and the decisions made using model output. Regulated or high-
impact uses require your own compliance review and suitable human oversight. No service
output substitutes for licensed professional judgment or lawful decision-making procedures.
6. Ownership, customer content, and limited processing
permission
As between the parties, you retain your rights in contributions, conversations, memories,
artifacts, and other content lawfully supplied by or for you ("Customer Content"). You authorize
RSC and necessary service providers to host, transmit, index, retrieve, reconstruct, protect,
export, and delete Customer Content only as reasonably required to provide, secure, support, and
lawfully operate the service, or as otherwise expressly authorized. This permission ends when
the content is deleted, subject to the limited retention and legal-hold provisions below.
RSC retains rights in its software, hosted platform, documentation, SDKs, service architecture,
trademarks, and other technology, subject to applicable third-party rights. SDK use is a limited,
revocable, nonexclusive right under these Terms and the applicable package license; it does not
grant ownership of or a right to independently operate the proprietary hosted substrate.
Suggestions or feedback do not grant RSC ownership of your Customer Content
7. Data handling, third-party cognition, and training
Our four environment-specific privacy notices describe personal-information practices for Beta,
Testing, Production, and Skyline. The canonical RMS retention commitments below apply
where RMS processes the relevant data class. If your application calls an independently selected
AI provider, that provider's handling of prompts, projected context, and responses is governed by
the applicable provider arrangement and policies. RSC cannot make promises about independent
providers beyond its actual contracts and controls.
Customer Content is not licensed by these Terms for unrelated advertising or general-
purpose AI model training. Any optional use of Customer Content for a materially different
purpose requires a separate, clearly disclosed lawful basis and, when required, affirmative
authorization.
You must not send provider API keys or secrets as conversational content. Where an integration
accepts credentials, use the designated protected credential interface.
8. Contractual RMS retention and deletion commitments
The following schedule preserves the existing RMS retention policy, version 2026-09-21, unless
a later policy is lawfully adopted and notified. A governed deletion excludes deleted content
from active relational reads, cognition context, memory/history reconstruction, artifact retrieval,
and portable exports. Ordinary recovery copies are inaccessible to active use and remain no
longer than seven days after deletion or scheduled expiry, subject to a scoped valid legal
preservation requirement.
Recovery copies after
Data category Active retention
deletion/expiry
Relational content, contributions, Until authorized
Up to 7 days
conversation content, durable memories customer deletion
Until authorized
Artifacts and images Up to 7 days
customer deletion
Until governed
Account/tenant customer content Up to 7 days
deletion or closure
Migration staging payload 7 days Up to 7 days
Minimum non-content migration provenance 365 days Up to 7 days
Operational, API, and webhook logs 30 days Up to 7 days
Security and audit records 365 days Up to 7 days
Minimum billing, transaction, tax, and Up to 7 days after
2,555 days (7 years)
accounting records scheduled disposal
Minimum non-content OBS integrity
Permanent Permanent
evidence
Minimum non-content deletion-event
Permanent Permanent
evidence
Permanent integrity/deletion evidence is limited to event identifiers, sequence/lifecycle facts,
hashes, timestamps, provenance, and proof of deletion. It must not retain deleted content, a
summary, a reversible encoding, a semantic-content-preserving embedding, or another substitute
for deleted content. A valid legal obligation, dispute, or necessary fraud/security investigation
may delay destruction only for the information and time reasonably required; that delay does not
restore deleted content to normal relational use. This schedule must remain consistent with the
executable retention policy and each public privacy notice.
Requests for deletion, export, or access require appropriate identity and authority verification.
Deleting a visible chat window, clearing local browser storage, revoking a provider key, and
deleting canonical relational content are different actions.
9. Payment, credits, and taxes
Production customers agree to the charges shown in their order, checkout, or plan: setup fees,
included credits, metered credits, seat capacity, and any optional purchases. Fees are in U.S.
dollars unless stated otherwise. For paid services, payment processing may be provided by Stripe
or another disclosed processor. You authorize permitted recurring and usage-based charges and
are responsible for applicable taxes other than taxes on our net income. We will provide
applicable purchase and billing disclosures before charging you.
Charges already incurred are non-refundable except as stated in a written order, our published
refund policy, or applicable law. We may restrict service for nonpayment after any notice
required by law or contract. We will not convert Beta or Test usage into paid Production usage
without the required plan and authorization steps.
10. Service operation, changes, and support
We may patch, update, protect, or modify the service and its interfaces. Beta/Test functions may
be modified or withdrawn more frequently than Production functions. We will use reasonable
notice for material changes when practicable or legally required. We do not promise
uninterrupted availability unless separately and expressly agreed in a service-level agreement.
Scheduled maintenance, provider outages, rate limits, network failures, and infrastructure
incidents may affect operations.
11. Suspension, termination, and transition
We may suspend access as reasonably necessary for security, unlawful use, material violation,
over-limit operations, or unpaid charges, with notice when appropriate. You may stop using the
service and may request account closure through the applicable authorized process. Where
supported, export data before closure. Deletion following closure is governed by Section 8, not
by the mere expiration of a credential. Accrued payment obligations, lawful retention,
ownership, confidentiality, warranty disclaimers, liability limits, and dispute provisions survive
as applicable.
12. Disclaimers
TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, EXCEPT FOR
EXPRESS WRITTEN SERVICE COMMITMENTS, THE SERVICES AND AI-
RELATED OUTPUTS ARE PROVIDED "AS IS" AND "AS AVAILABLE." RSC
DISCLAIMS IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A
PARTICULAR PURPOSE, AND NON-INFRINGEMENT TO THE EXTENT
LAWFULLY PERMITTED. We do not guarantee error-free cognition, complete context
reconstruction, uninterrupted availability, or fitness for medical, legal, financial, safety-critical,
or other regulated decisions. Nothing here limits a mandatory statutory warranty or remedy.
13. Liability limits
TO THE MAXIMUM EXTENT PERMITTED BY LAW, neither party is liable to the other
for indirect, incidental, special, consequential, exemplary, or punitive damages, or lost profits or
business opportunity, arising from these Terms, except to the extent applicable law prohibits that
exclusion. RSC's aggregate contractual liability for a paid Production claim will not exceed the
fees paid or payable for the affected service in the twelve months before the event, giving rise to
the claim. For claims arising solely from no-fee Beta or Test access, the proposed cap is US$100.
Nothing excludes or restricts liability that cannot lawfully be excluded or restricted, including
liability for fraud, willful misconduct, or other mandatory protections to the extent applicable.
These limits do not relieve RSC of its stated contractual retention/deletion commitments.
14. Indemnification
To the extent permitted by applicable law, organizational Customers will defend and indemnify
RSC against third-party claims arising from their unlawful Customer Content, infringement of
third-party rights, or their material misuse of the services, except to the extent caused by RSC's
own conduct. Any indemnity process must provide prompt notice, reasonable control of defense,
cooperation, and protection against settlements that impose non-monetary obligations without
consent.
15. Disputes and governing law
Before formal proceedings, either party may provide written notice describing a dispute and
allow 30 days for a good-faith resolution, unless urgent relief or statutory deadlines make that
impracticable. These Terms will be governed by the law of the State of Oklahoma , without
overriding mandatory consumer protections or applicable conflict-of-law rules.
16. Notices and changes
The effective version will be accessible through the service. Material amendments will be
notified through account email, console, or another appropriate method before taking effect
where required. Changes to already-collected data practices may require a separate notice or
consent and cannot be justified solely by silently replacing a privacy notice. If a provision is
unenforceable, the rest remains effective to the extent legally permissible. Neither party may
assign this agreement in a way that defeats applicable law or an express written restriction.
17. Contact
Rhodes Solutions Company | Apex Technology Division
Temporal Continuity
Service support: support@api.rscapex.com
Legal/privacy inquiries: privacy@api.rscapex.comBack to Legal & Privacy