Effective 5 October 2026
Use the system with the human in command.
Growth Studio is an unsigned release candidate for drafting, planning, learning, and evaluation. It does not grant permission to publish, spend, contact people, or change external systems.
Starlight Intelligence terms of use details
These terms cover starlightintelligence.ai, its public APIs and MCP endpoint, Memory Studio, the optional cloud curator, and the Starlight Growth Studio beta candidate. The operator is Frank Riemer / Starlight, Amsterdam. The public release has no checkout. Cloud execution remains unavailable until its activation dependencies pass; the portable workspace needs no account. Starlight products follow customer-owned runtime, data and keys, BYOK and self-service. Hourly consulting and support retainers are not offered. Hosted licensing or authentication is a proposal, not an approved change to this business boundary. Academy remains free.
Release-candidate scope
The package may help research, draft, structure, evaluate, and prepare work. It is not a managed employee, professional adviser, certification authority, publishing service, model provider, or guarantee of commercial results. Compatibility labels describe the documented adapter state and do not promise that a third-party host will accept or continue supporting it.
Your responsibility and authority
- You are responsible for the sources, instructions, accounts, credentials, permissions, outputs, and external actions used with the package.
- A named human must review material claims, rights, privacy, safety, cost, destination, and account context before an external side effect.
- Do not use the service to violate law, rights, contracts, platform rules, security boundaries, or another person's privacy.
- Do not upload secrets or confidential information to public routes or place them in plugin files, prompts, logs, or evidence drafts.
Open-source package
The files identified as MIT-licensed are provided under the bundled MIT license. Starlight names, marks, site copy, paid services, and other materials are not relicensed merely because the starter package contains MIT code. Third-party runtimes, models, connectors, and sources remain under their own terms.
Cloud curator
The curator is available only to members it has been activated for, with a limit of five attempts per UTC day. A failed run still counts as an attempt. Its output is generated and unverified: it has no browsing, account access, or publishing tools, and it does not check facts. Starlight may suspend or end curator access at any time.
A run receipt records lifecycle state and does not verify generated claims. An interrupted request can leave its outcome unresolved. Checking a receipt does not retry the model or refund an attempt.
Portable workspace and device recovery
Keep an exported copy of work you need. Optional device recovery stores plaintext in this browser, survives sign-out and is not isolated by account. People with access to this browser may be able to read it. Browser clearing, storage limits or device loss can remove saved work; device recovery is not a cloud backup.
Evidence and credentials
A learning export is a self-attested evidence draft, not a credential, compliance record, endorsement, or canonical capability receipt. Only an explicitly described evaluation process may promote evidence, and the human reviewer retains the final decision.
Availability, changes, and rollback
The release may change, fail, or be withdrawn. Review version notes before updating, preserve work you need, and use the documented rollback path. Starlight may limit requests that threaten security or availability.
Disclaimers and liability
To the extent permitted by applicable law, the public release is provided without warranties of accuracy, fitness, availability, non-infringement, compatibility, or results. Starlight is not responsible for third-party services or for decisions and external actions taken from generated or compiled output. Nothing here excludes liability that applicable law does not allow to be excluded.
Contact and changes
Questions may be sent to frank@frankx.ai. Material changes will update the effective date. Paid commerce, managed execution, or provider-credential handling will require additional terms before launch.
