Nehraq BETA Program Policy

BETA Program Policy

Effective date: June 23, 2026

This BETA Program Policy applies to early access, preview, pilot, prototype, evaluation, and BETA use of Nehraq. It supplements the Terms of Service, Privacy Policy, and any written agreement between Nehraq and your organization.

BETA access is intended for evaluation and controlled onboarding. Do not rely on BETA features as your sole system of record, sole legal-defense mechanism, sole compliance control, or sole production safety layer unless Nehraq has separately authorized that use in writing.

1. BETA eligibility

BETA access is not guaranteed. Nehraq may approve, deny, delay, limit, suspend, or revoke BETA access based on workspace risk, company-domain eligibility, use case, capacity, security review, legal review, customer readiness, or product fit.

2. Company-domain requirement

BETA registration requires a real organization work email. Public email providers, disposable email services, aliases that cannot reasonably identify an organization, or misleading domains may be rejected. Nehraq may require additional verification before activating a workspace.

3. BETA feature status

BETA features may be incomplete, experimental, changed without notice, temporarily unavailable, or removed. Interfaces, workflows, evidence formats, routing behavior, security controls, and reports may change as Nehraq improves the product.

4. Appropriate BETA use

BETA users should use Nehraq to evaluate:

AI agent registration and identity workflows;
authority-boundary design;
approval and escalation paths;
evidence receipt structure;
incident replay and claim-readiness concepts;
workspace onboarding and operational fit.

5. Restricted BETA use

Unless separately authorized in writing, BETA users should not:

connect BETA workflows to irreversible production actions;
use BETA features as the only approval control for money movement, regulated decisions, employment decisions, healthcare decisions, or legal commitments;
upload unnecessary secrets, credentials, regulated records, or highly sensitive information;
represent BETA outputs as certified legal, regulatory, insurance, or audit determinations;
stress test, attack, scrape, or reverse engineer BETA systems without written authorization.

6. Evidence and liability limitations

Nehraq is designed to improve traceability, reviewability, and defensibility of AI agent activity. During BETA, evidence records may be simulated, incomplete, preview-only, browser-stored, or dependent on customer configuration. Nehraq does not guarantee that BETA evidence records will be accepted by a regulator, court, insurer, auditor, or counterparty.

7. Feedback

BETA users may provide comments, ideas, bug reports, workflow suggestions, screenshots, or other feedback. Nehraq may use feedback to improve products, services, documentation, pricing, positioning, security, and workflows without compensation or obligation unless separately agreed in writing.

8. Availability and support

BETA availability and support may be limited. Nehraq may provide support through email, workspace communication, scheduled review, or other channels. BETA access does not include guaranteed uptime, response times, service credits, or production support commitments unless stated in a signed agreement.

9. Data handling in BETA

BETA users should limit submitted data to what is necessary for evaluation. Organizations are responsible for ensuring that submitted information is authorized, appropriate, and compliant with their internal policies and applicable obligations.

10. Security review and workspace approval

Nehraq may require security, legal, compliance, or operational review before enabling certain features, integrations, exports, or workspace access. High-risk use cases may require manual approval or additional controls before activation.

11. Changes, suspension, and termination

Nehraq may change, pause, limit, or end the BETA program at any time. Nehraq may suspend a BETA workspace if use appears unsafe, unauthorized, misleading, non-compliant, abusive, or inconsistent with this policy.

12. Transition from BETA

If Nehraq offers general availability, paid plans, enterprise pilots, or production deployments, BETA users may be required to accept updated terms, complete additional verification, sign a customer agreement, or migrate data to a production environment.

13. Contact

Questions about the BETA Program Policy should be directed through the official Nehraq support or legal contact channel provided in your access correspondence, workspace, or customer agreement.