STARLOOS / 0.9.0

Private-pilot data notice.

A technical disclosure for the operator to complete before commercial publication.

Operator identity, jurisdiction, contact details, legal basis, retention policy, and applicable rights processes must be supplied and reviewed before inviting real customers. This template is not a privacy compliance certification.

Data handled by the application

Private workspaces contain tasks, selected source documents, approved memory, agent instructions, files, tool events, usage records and invitation metadata. Session credentials use an HTTP-only cookie. The interface stores only its motion preference locally; it does not store provider keys in browser storage.

Where the data goes

The desktop stores workspace data in its operating-system user-data folder (shown under Model & runtime). The older legacy launcher uses a local .starloos/ directory. Cloud mode stores workspace data in the operator’s Redis service. Model-driven missions send selected material and relevant tool results to the configured model provider. Website retrieval contacts the requested public sites. Search queries go to the configured search provider. Approved MCP actions send their arguments to the chosen connector. Review each service’s terms and retention policies.

The OpenAI adapter requests store:false; that alone is not a guarantee of zero retention under every provider policy. The package does not configure a data-processing agreement or regional compliance program.

Controls and retention

Export workspace data and files from Settings and File vault. Individual knowledge and memory records can be deleted, and finished mission history archived. A snapshot already included in an active mission remains until that run ends. Deleting a source does not retract data already sent to a model or connector. Backups and external-service records require separate operator deletion procedures.

Internal limits constrain retained run and ledger counts; they are not a contractual retention schedule. The operator must define a documented retention and access-request process, backups, security controls, and a support contact before public use.

No on-chain personal data

This release does not send transactions, prompts or memory to a blockchain.

Desktop edition

The local desktop edition stores agents and files on your computer. Cloud model requests go to the provider you configure. Keys stay in memory by default; explicitly remembered cloud keys use a passphrase-encrypted local vault, not an OS keychain. An optional local Ollama model must be installed separately. The website does not receive local model keys.

Desktop access requests

The access form collects your name, email, platform, intended use and consent so the site operator can review access. No wallet data, secret keys or model prompts are required. Email is not automatically verified and no email is automatically sent. Keep your private receipt confidential.

Requests expire after 30 days. Expired records are removed on the next queue read or mutation; the operator must run regular cleanup if no one accesses the queue. Owners can delete individual records sooner. Rate-limit keys use hashed network identifiers with short expiry. Download authorizations record file IDs and timestamps, not successful completion of a download.

Operator identity, contact details, infrastructure agreements and jurisdiction-specific policy must be finalized before a public rollout. The application is a private-alpha tool, not a substitute for those responsibilities.