← All legal documentsRhodes Solutions Company / Apex Technology Division
Temporal Continuity Production Privacy Notice
Effective October 10, 2026
Temporal Continuity | Production Privacy
Notice
Rhodes Solutions Company | Apex Technology Division
Environment: Temporal Continuity Production Service
Effective: 2026-10-10
Status: OPERATIONAL
1. Scope and who is responsible
This notice explains the personal-information practices associated with the commercial
Temporal Continuity Production API and developer console operated by Rhodes Solutions
Company, Apex Technology Division ("RSC"). It does not replace the applicable Temporal
Continuity Terms of Service, a signed order form, or a data processing agreement ("DPA").
Beta, non-production Testing, and Skyline have separate privacy notices.
Allocation of roles matters. For a customer's own application's end-user conversation and
relational content, the customer generally determines the purposes and means of use and RSC
performs service processing under customer instructions, subject to the parties' agreement and
applicable law. For RSC's own account administration, service security, commercial
transactions, and compliance activities, RSC may determine its own purposes and is responsible
for those activities under applicable law. The parties should document controller/processor or
business/service-provider roles in a DPA when needed. These roles do not arise solely from a
label in this notice.
2. Categories and sources of information
Category Examples Sources
Name if provided, email, Firebase account ID, Customer, authorized
Account and contact
organization/project/environment IDs, user roles, users, authentication
data
support correspondence services
Environment type, permissions, key Customer
Service configuration
identifiers/hashes, billing entitlements, webhook administrators; service
and credentials
settings, SDK/API versions records
Customer or its
Conversation contributions, durable memories,
Relational customer applications,
context projections, history, associated identifiers,
content authorized users,
provenance, submitted artifacts/images
service processing
Migration/export Staging payloads, original-source labels, migration Customer or its
data facts and export manifests integration
Usage, operational, API request identifiers, timestamps, rate limits, Service, hosting,
and security audit events, errors, measured usage, verification authentication,
information status, IP/device data where infrastructure records network providers
Category Examples Sources
it
Plan, seats, subscription and transaction identifiers, Customer, RSC,
Billing information billed continuity credits, invoices, payment status, payment processor
refund/tax/accounting metadata (e.g., Stripe)
Payment card details are generally submitted to the payment processor, Stripe, through its
checkout, rather than to Rhodes Solutions Company. Customer-provided relational content may
itself contain personal, confidential, or sensitive information; customers control what they submit
and must have lawful authority to do so.
3. How and why information is processed
We process the information necessary to provision and administer the service; verify tenant
ownership and permissions; preserve authorized relationships, contributions, memories, and
provenance; project context and return responses; manage migrations, exports, and deletion;
enforce plan credits and metering; reconcile payments; detect abuse; secure systems;
troubleshoot incidents; respond to support requests; and comply with legal obligations. We may
use minimized, non-content operational metrics to monitor reliability and capacity. We do not
treat customers' authorization to obtain continuity as blanket permission to publish their content,
target advertisements to them, or train unrelated general-purpose models.
Where applicable, lawful grounds may include performing the service contract, meeting legal
obligations, protecting legitimate security and integrity interests, processing under a customer
instruction, or obtaining consent for an optional distinct purpose. These grounds and any
required right to object depend on the jurisdiction and RSC's actual role.
4. Disclosures, processors, and independent cognition
Production data may be processed by cloud hosting, storage, authentication, security, support,
and payment-service providers necessary to perform these functions, including Google Cloud, an
authorized object-storage provider for artifacts, and Stripe for applicable purchases. We may
disclose limited information under valid legal process, for proportionate security/abuse
responses, or for lawful corporate transactions subject to applicable protections.
Temporal Continuity does not automatically own the customer's cognition provider. A
customer application that independently invokes an AI model or selects a third-party provider
controls that integration and associated disclosures under its provider contract, subject to
applicable processing arrangements. An authorized context projection can contain earlier
relational information; sending that projection to another provider may disclose it to that
provider. The customer is responsible for informing its end users and choosing providers
lawfully.
We do not license customer relational content for unrelated data brokerage or behavioral
advertising in these Production Terms.
5. Retention, deletion, and permanent non-content records
RMS retention policy version 2026-09-21 is contractually reflected in Temporal Continuity's
Terms. The current canonical classes are:
Recovery after
Data category Active period
deletion/expiry
Relational contributions, conversational Until authorized customer
Up to 7 days
content, durable memories deletion
Customer artifacts/images Until authorized deletion Up to 7 days
Until governed deletion or
Account/tenant customer content Up to 7 days
tenant closure
Migration staging payloads 7 days Up to 7 days
Minimum non-content migration
365 days Up to 7 days
provenance
API, operational and webhook logs 30 days Up to 7 days
Security and audit records 365 days Up to 7 days
Billing, transaction, tax and accounting Up to 7 days after
2,555 days (7 years)
records scheduled disposal
Minimum non-content canonical OBS
Permanent Permanent
integrity records
Minimum non-content deletion-event
Permanent Permanent
evidence
Authorized deletion excludes governed content from active reads, cognition context,
reconstruction, artifact retrieval, and exports; inaccessible recovery copies may remain for no
more than seven days unless subject to a valid, limited preservation obligation. Permanent
integrity records preserve minimal event facts and not deleted content, summaries, reversible
encodings, or semantic substitutes. Claims that deletion is "instant everywhere" or that "all
records disappear" would be inconsistent with this schedule.
Other service metadata, including Google authentication profiles, support tickets, payment
processor records, and processor-side records, may have separate retention and account-
closure procedures. Closing an account, revoking an API credential, ending a subscription,
deleting a visible interface, and deleting canonical relational content are distinct operations.
6. Access, correction, export, deletion, and privacy rights
Authorized customer administrators may use available service endpoints and console
functionality to request or perform export and deletion. A person whose data was submitted by a
customer application should ordinarily direct their request first to that application's operator, who
controls the relationship and authorization. We support that customer as required by the
applicable agreement and law.
Depending on where you live and which laws apply, you may have rights to access, know,
correct, delete, obtain a portable copy, limit or object to certain processing, opt out of certain
sales/sharing or profiling, withdraw consent, or appeal a refusal. No specific state law is assumed
to apply merely because this notice lists potential rights. Contact privacy@api.rscapex.com
with sufficient information to identify the account and request; we will verify authority and
provide the response/appeal process required by applicable law. We will not ask for complete
passwords, API secrets, or unnecessary sensitive evidence in an ordinary privacy request.
7. Security and incident response
The service uses scoped credentials and tenant authorization, controlled storage, audit records,
and technical safeguards designed to reduce risk. Customers remain responsible for their
applications' access controls, user notices, credential hygiene, and provider choices. No platform
can guarantee absolute security. When an incident triggers a contractual or legal notification
obligation, we will follow that obligation and provide information through the designated
customer or account channel.
8. International processing, children, and sensitive uses
The service may be accessible from outside the United States and may rely on providers with
international operations. Before offering the service to jurisdictions requiring particular lawful
bases, contractual transfer safeguards, a representative, or a DPA, those requirements must be
evaluated and documented.
Temporal Continuity is intended for adults and authorized organizations. It is not directed to
children under 13. Customers processing children’s health, biometric, financial, or other
protected information must assess applicable restrictions and execute any required arrangements
before uploading. No general HIPAA, PCI-DSS, FERPA, GDPR, or other sector-specific
certification is represented by this notice.
9. Notice changes and contact
Material changes to the kinds of data collected, purposes, disclosures, or retention schedule will
be dated, presented as required, and not retroactively used to justify undisclosed new purposes
without a lawful basis or needed consent. The contractually governed RMS retention schedule
must be versioned consistently across Terms, Privacy Notices, and executable policy.
Rhodes Solutions Company | Apex Technology Division | Temporal Continuity Production
Service and billing: support@api.rscapex.com
Privacy and data protection: privacy@api.rscapex.comBack to Legal & Privacy