Terms for evaluating the public beta.

These terms cover evaluation-only use of the Errorcore public beta.

Effective publication version: beta-terms-2026-08-13.1.

Evaluation-only beta.

Errorcore is offered only for testing and evaluation while the public beta is under review. Features, interfaces, data handling, limits, and availability may change, pause, or be withdrawn before launch. Do not rely on the beta as the sole system for incident response, compliance, evidence preservation, or business continuity.

Subject to these terms, Errorcore permits the organization to access the hosted service on a limited, non-exclusive, non-transferable, revocable basis solely for its internal evaluation during the public beta. That permission lasts only while Errorcore makes the beta available to the organization and ends when access is terminated or withdrawn. It is a hosted-service permission only and does not grant rights in the SDK or cloud implementation.

Authority and accounts.

A person who creates or uses an organization must be at least 18, act in a business or professional capacity, and have authority to evaluate the beta for that organization. Account details must be accurate, access must be limited to authorized members, and credentials must be protected. Account sharing or attempts to bypass organization boundaries are not permitted.

Customer data and permission to process it.

The customer retains ownership of the runtime evidence, configuration, and other data it submits. The customer authorizes Errorcore to host, copy, transmit, decrypt in the processing worker, scrub, transform, index, and display that data only as needed to operate, secure, and troubleshoot the service.

Lawful capture and scrubbing.

Customers are responsible for deciding what their software captures, providing required notices, obtaining required permissions, configuring scrubbing, and ensuring submitted data is lawful. Scrubbing is a risk-reduction control, not a guarantee that all personal, confidential, regulated, or secret values will be detected.

Acceptable use.

Users must not:

• Break the law, violate another person's rights, or process data without permission.
• Probe, disrupt, overload, reverse engineer, or bypass security, rate, tenant, or plan controls.
• Upload malware, secrets, payment-card data, health records, or other highly sensitive data not required for a controlled evaluation.
• Use another organization's credentials, data, or service access.
• Resell, sublicense, or present the beta as a generally available or certified service.

Product and feedback.

Errorcore and its software, documentation, branding, and service design remain the operator's property or that of its licensors. The evaluation permission does not transfer those rights. Feedback may be used to improve the service without identifying or disclosing the customer's confidential information.

The hosted service and public SDK are separate. The SDK is Source Available only under the PolyForm Strict license shipped with it. These service terms, account creation, API credentials, and the Free evaluation do not grant commercial or production SDK rights. Any commercial SDK license must arise under separate approved terms tied to an authorized paid subscription or an executed Order Form. Unapproved commercial terms are non-operative and cannot be accepted. See the licensing boundary.

Suspension and confidentiality.

Access may be limited or suspended to protect users, data, the service, or third parties; respond to legal requirements; investigate misuse; or address security and operational risk. Each side should protect non-public information received from the other and use it only for the evaluation, subject to disclosures required by law.

Rights that cannot be excluded.

Nothing in these terms is intended to exclude, restrict, or waive a right or remedy that applicable law does not allow the parties to exclude, restrict, or waive.

Recorded acceptance and acknowledgement.

Before first organization provisioning, an organization administrator must affirmatively accept the current evaluation Terms and acknowledge the current Privacy notice for that organization. Errorcore records the organization, acting user, canonical document key, version, digest, acceptance surface, database timestamp, request reference, idempotency reference, and legal bundle identifier. The server chooses the canonical versions and digests; a browser cannot nominate an older version. The rendered form is bound to an opaque server-owned bundle identifier, and stale forms are rejected rather than recorded against text the administrator did not review. Errorcore does not collect an IP address or user-agent solely to create this record.

Acceptance is never required to reach cancellation, billing-portal, privacy-request, or security-contact routes. Existing beta organizations are asked at their next privileged setup or provisioning action; ingestion is not interrupted merely because replacement commercial documents remain unapproved.