Terms of service candidate

These candidate terms test whether the product design leaves room for a responsible domestic and international launch. They are not an active user contract and do not claim an App Store release, production account system, subscription, or cloud service.

Production terms must identify the operator and effective date before registration, purchase, or first activation, preserve the accepted version, and record a valid user choice. Browsing this Portal is not acceptance of future terms.

• Capture, organize, browse, use, export, and delete personal Context on iPhone, iPad, and Mac.
• Optional account, encrypted sync, recovery, AI task, and support capabilities selected by the user.
• Web controls for account security, devices, permissions, and privacy requests.
• Actual features, regions, requirements, and limits must be described in the released product. Candidate screenshots are not feature commitments.

• Users should provide information they may lawfully use and protect their devices, credentials, and recovery materials.
• An account or management title does not grant access to all family, team, or customer Context; access requires an explicit role, scope, and authorization.
• Signing out, revoking a device, deleting a cloud copy, erasing local content, and deleting an account are different actions.
• Full-account deletion and cloud-copy deletion are separate workflows. The engineering candidate implements the former request and state machine, while real-provider deletion, regional timing, and completion notices remain production acceptance gates.

Users retain rights in content they lawfully own. Production terms may require a limited, non-exclusive permission solely to deliver features the user activates. It must not transfer ownership or become a blanket permission for third-party model training or advertising.

Users are responsible for having authority to store and use information about other people. Shared spaces require clear member, exit, and handover rules.

• AI classifications, links, summaries, and answers are candidates that may be inaccurate, incomplete, or outdated. Users remain responsible for checking sources and making decisions.
• ClariZest may assist with organizing information for medical, legal, financial, employment, safety, or other high-risk matters, but is not a substitute for a qualified professional or accountable decision maker.
• Models should receive only the minimum content selected for the current task. Provider, region, retention, and training choices must be disclosed before activation.
• Users may not use the service to violate rights, bypass authorization, distribute malicious code, commit fraud, or handle content prohibited by law.

Local features, hosted sync, models, identity, stores, and support have different dependencies. Production terms must address maintenance, outages, degradation, recovery, and shutdown. This candidate offers no uptime or service-level commitment.

Third-party services have their own terms. Critical dependencies and redirects should be clear before the user chooses them.

• No production price, free allowance, trial, tax, renewal, or refund policy is confirmed.
• Before sale, each region and channel must disclose price, billing cycle, renewal, cancellation, and entitlement changes.
• Account deletion does not necessarily cancel a store-managed subscription; the deletion flow must warn users before confirmation.
• Basic export, deletion, local encryption, and data-ownership controls must not be removed by subscription tier.

Security, unlawful use, or necessary maintenance may justify limited action, but production terms must state reasons, scope, notice, appeal, and restoration. A management title or higher payment tier must not silently expand access.

Service shutdown requires a reasonable export and exit process. Deletion states and any legal-retention or backup-expiry exceptions must remain visible.

The candidate build is provided in its current state and must not handle production or mission-critical data. Production warranties, liability limits, indemnities, governing law, venue, arbitration, mandatory consumer rights, and regional addenda are unresolved.

An authorized operator and qualified legal counsel must review these terms against the real business, launch regions, and data flow. No limitation may exclude liability that applicable law does not permit it to exclude.

Contracting partyProduction confirmation required

To be confirmedLegal name, address, contact details, and authority.

Regional rulesProduction confirmation required

To be confirmedConsumer rights, governing law, disputes, and addenda.

Commercial termsProduction confirmation required

To be confirmedPrice, tax, trials, renewal, cancellation, refunds, and shutdown.

Acceptance recordNot configured

Not liveVersion presentation, valid choice, audit record, and material-change notice.