MINESPACE INC. / PLATFORM NOTICES
Legal, privacy & responsible use.
Notice date November 19, 2026
Terms of use
CLARA is a software development and computational platform provided by MineSpace Inc. Access to the public service and any included examples is for lawful development, evaluation and permitted application use. You must have authority to act for any organization you represent and to use submitted materials.
You control your code, exports and publication decisions. Keep independent backups, review generated code and computational outputs, and verify third-party packages and endpoints before using them. CLARA is not certified for safety-critical or regulated decision-making. No uptime, fitness, accuracy or uninterrupted service is promised. To the extent permitted by applicable law, the service is provided as available and without warranties; nothing here limits rights or remedies that cannot lawfully be limited.
MineSpace may restrict access, decline publication or remove listings to protect users, comply with law or address abuse. Public release metadata may be copied by other registries or IPFS participants; withdrawal from this registry does not guarantee deletion from other systems. Material changes to these notices should be communicated before they take effect where required.
Privacy notice
Local workspaces store source, drafts, project settings, signing keys, documents, job results and trusted registry pins in browser storage. They are not automatically published or uploaded by local development. Server operations you explicitly choose send the corresponding data to the hosting service; public publication discloses signed release metadata. The server stores submitted application data and registry records until removed or otherwise managed by its operator. Local data remains until removed, browser storage is cleared, or the browser evicts it.
Optional usage analytics are off by default. A browser Global Privacy Control signal suppresses optional event reporting; use the deletion control to remove previously recorded counts. If enabled, a random browser identifier and limited feature event names are sent to the platform. The server derives a keyed identifier and stores daily counts, not source text, API request contents, document contents, signing keys or administrator tokens in its analytics table. Counts estimate browser installations, not individual people. Public MCP tool calls are counted in aggregate separately. Hosting infrastructure may maintain separate connection and access logs, including IP addresses, timestamps and request paths; their retention depends on host configuration.
The active analytics reporting window is 90 days, with older rows pruned on subsequent analytics service activity. You can stop optional counts and request deletion of this browser's analytics identifier in Settings. If deletion fails while offline, retry when connected. Export or remove local projects individually, or use your browser's site data settings to clear local storage; clearing storage may permanently remove private signing keys. The platform is not intended for children under 13; do not submit children's personal data.
Explicit DNS discovery sends only the domain query to Google Public DNS. Refreshing trusted peer registries connects directly to those chosen third-party hosts, which may receive your IP address and requested namespace. Public WORLD searches never send credentials. CONNECT private discovery sends the search query and a separately supplied scoped credential to each explicitly selected private registry over HTTPS; neither administrator tokens nor private discovery queries are sent to DNS. Third-party sites and IPFS gateways have their own privacy and retention practices. Public metadata can be redistributed. No advertising tracker is included in this release.
For privacy access, correction, deletion, appeal or other requests required by applicable law, contact MineSpace through its official website. Do not send credentials or sensitive source material in a request. Some records may need to be retained where required by law. Applicable rights vary by jurisdiction.
Private organization workspaces
Invited members acknowledge workspace terms to redeem an invitation. Existing invitation acceptance remains recorded against policy version 0.15.0; updated CONNECT notices are supplied here for operator review. MineSpace-hosted workspace storage contains organization labels, member labels and roles, hashed credentials, acceptance version, project content, revisions and timestamps. Workspace owners and hosting administrators can access stored projects; they are not end-to-end encrypted. Do not upload secrets or regulated personal data. Revocation blocks future server access but cannot erase copies already downloaded. Deletion removes active project content, while revision tombstones and host backups may remain. Ask the workspace administrator or MineSpace through its official website for access or deletion assistance. Separate optional feature counts do not contain project content.
CONNECT exchange and deployments
Encrypted exchange uses a user-supplied passphrase and authenticated encryption in the browser. The server stores ciphertext and organization/object identifiers, revision numbers, hashes and timestamps. Ordinary project synchronization remains unencrypted at the application layer; use HTTPS. Scoped workspace and application credentials are hashed, expiring and revocable. Application credential labels, release association, scopes, expiry and revocation status are stored for access control. The actual credential is shown only when issued and is not included in optional usage analytics. Private federation discloses search terms and project metadata to authorized peer hosts. Deployment stores the submitted compiled project and creates release-specific application data; public GET routes may disclose application responses. Revoking a release disables execution but does not immediately erase stored code or data. Keep your own keys, backups and passphrases; lost passphrases cannot be recovered. A compromised website or device can defeat browser-side encryption.
Acceptable use
Do not use CLARA to violate laws or third-party rights, distribute malware, exploit systems without authorization, impersonate publishers, publish stolen or confidential information, harass others, or evade access controls and resource limits. Do not upload personal or regulated data without appropriate authority, safeguards and a lawful basis. Do not automate requests in a way that disrupts the service. Public registry publication requires operator approval; signatures identify a signing key, not legal ownership or approval of the software.
Intellectual property and distribution
CLARA and MineSpace branding identify the MineSpace platform. All rights in MineSpace-owned materials are reserved except for permissions expressly granted in applicable written terms or licenses. Public visibility, accessible source and registry links do not by themselves grant an open-source license or rights to redistribute third-party software. Users retain rights in their own materials, subject to rights they grant others. By requesting public registry publication, you authorize display and distribution of submitted public metadata for discovery and verification. By approving a public application deployment, the hosting operator authorizes CLARA to serve its public application responses. Only publish code and content for which you hold appropriate rights. Do not publish code or metadata unless you hold the necessary rights.
Third-party technologies and trademarks remain subject to their respective owners' terms. WebAssembly, WebGPU, WebGL, SQLite, Python, MCP, IPFS and DNS are referenced to describe interoperability; no endorsement or affiliation is implied.
Security and limitations
FOUNDRY stores private release history, test labels and status for authorized organization members and the hosting administrator. Tests run against disposable data. FOUNDRY-staged candidates are not reachable until promotion; public releases registered directly with CONNECT can be reachable immediately. Promotion and rollback change routing only; release-specific databases remain stored. Preview and production pointing to the same release share that database.
CLARA uses bounded execution, signed release metadata, local key storage and replay checks where supported. None guarantees absence of vulnerabilities or establishes a publisher's legal identity. The hosted registry is administrator-managed; private access is not a multi-tenant identity service. Review endpoint destinations before opening them. Report vulnerabilities, suspected impersonation or rights violations through the official MineSpace website. Do not include passwords, private keys or sensitive data in reports.
Return to CLARA · Machine-readable notices
CLARA Projects
The example application stores task contents on the device by default. It does not send application usage telemetry or task contents to MineSpace in local mode; ordinary hosting access logs may still record requests for public assets. If you explicitly connect a hosted release, task data is submitted to that authorized application. Exports can include readable task contents or encrypted snapshots; passphrases are not uploaded. Keep credentials and passphrases private. Imports create new task records, not synchronization of existing records.
Names and enterprise analytics
MineSpace administers CLARA application-level namespace allocation. Unallocated names are reserved; assignment is not a transfer of trademark rights, domain names or legal ownership. No purchase or resale mechanism is offered here. Existing assignments and signed publisher records are preserved. Enterprise analytical jobs are retained until authorized deletion; backups may retain copies. The hosting administrator can access stored data. The enterprise service is not approved for physical control or safety-critical use. See namespace policy and enterprise specification.
AI training and agent data
CLARA AI processes only explicitly approved corpus inputs. Do not submit confidential, personal or regulated information without authorization and a suitable approved handling environment, and do not submit content you lack rights to use. The local model stores approved text, corpus metadata, learned state and agent profiles in browser storage; hosted mode stores the same information and model counts on the private server, readable by the hosting administrator. Neither is automatically end-to-end encrypted. Agent queries are not intentionally stored or added to training; infrastructure logs and administrative backups may still exist. Deleting a trained document removes the active record and clears the model before rebuilding from retained corpus. This is not a guarantee of forensic erasure from backups or exported models. Exported models may disclose training text; safeguard them. Optional automatic processing is controlled separately and processes approved items only. Public MCP exposes specifications, never corpus contents, private model state or agent queries. Operator-approved external imports disclose ordinary request metadata to the source. Machine-readable capabilities and limits.
Ledger and radio analysis
Signed records and exported snapshots are not encrypted. Do not enter secrets or personal data that cannot be disclosed or removed from distributed copies. Independent node operators control their own keys, data, backups and access. Use only radio recordings you are authorized to process and comply with applicable communications and privacy requirements. The reference node and receive-only analysis are not certified for critical-infrastructure or financial use.