Terms of Service

1. Acceptance

By accessing or using FieldHash, you agree to these Terms of Service. If you use FieldHash on behalf of an organization, you represent that you have authority to bind that organization. If you do not agree, do not use the service.

Enterprise pilots or deployments may be governed by a separate written agreement, statement of work, data processing addendum, or order form. If those terms conflict with these public terms, the signed agreement controls for that deployment.

2. Description of Service

FieldHash provides three governed control surfaces plus an evidence layer:

• FieldHash Governed Memory: a control layer for evaluating candidate memory, enforcing approved/current state, suppressing stale, rejected, out-of-scope, superseded, or rolled-back influence, and constructing governed model-input packets.
• FieldHash Governed Actions: a control layer for evaluating tool or action candidates, enforcing configured authorization signals, suppressing revoked, stale, out-of-scope, or unauthorized action candidates, and constructing governed action packets where configured.
• FieldHash Governed Precedent: a control layer for bounded reuse of reviewed authority decisions, with scope, expiry, evidence, policy, and tracked dependency checks where configured.
• FieldHash Ledger: evidence tooling for selected governance events, including evidence packets, packet hashes, checkpoint references, certificates, transparency anchors, customer-owned exports, and audit packets where configured.

Features, integrations, model routes, deployment regions, retention settings, and ledger capabilities may vary by customer configuration and agreement.

3. Accounts and Access

You are responsible for maintaining account security and for all activity under your credentials. You must provide accurate information, keep credentials secure, and promptly notify us of unauthorized access.

We may suspend or restrict access if we reasonably believe an account, integration, or deployment presents a security, legal, operational, or abuse risk.

4. Customer Content and Responsibilities

You retain ownership of content you submit to FieldHash, including records, prompts, documents, candidate memories, governance metadata, and customer data. You grant FieldHash the rights needed to process that content to provide, secure, support, and improve the service, subject to any enterprise agreement.

You are responsible for ensuring that you have the rights, permissions, notices, and lawful bases needed to submit content to FieldHash and to route it through configured model providers, memory stores, integrations, and ledger/evidence tooling.

5. AI Outputs and Professional Review

FieldHash may use AI models to generate, transform, route, summarize, or evaluate information. AI outputs may be inaccurate, incomplete, stale, or unsuitable for a particular use. You are responsible for reviewing outputs before relying on them.

FieldHash does not provide legal, compliance, medical, financial, security-certification, or other regulated professional advice. FieldHash evidence packets and ledger artifacts are review aids for your qualified professionals, not a substitute for their judgment.

6. Governance and Ledger Limitations

FieldHash is designed to make memory influence, governed action selection, and reviewed-precedent reuse more controllable and reviewable. It does not guarantee that every incorrect, stale, unauthorized, or invalidly reused record, action, or precedent will be detected, nor that every deployment will satisfy a specific law, standard, or internal policy.

Ledger artifacts are reviewer-verifiable records under documented assumptions, not tamper-proof records. Stronger tamper evidence and operator resistance require appropriate configuration, key custody, anchor or log retention outside the operator boundary, infrastructure controls, and customer procedures.

Post-quantum cryptography, local-model routing, VPC/on-prem processing, EU-region deployment, SIEM/GRC export, and customer-owned audit logs apply only where specifically configured and agreed.

7. Acceptable Use

You agree not to:

• Use FieldHash for unlawful, harmful, deceptive, or abusive purposes.
• Attempt to gain unauthorized access to FieldHash, customer systems, model providers, integrations, or other users' data.
• Interfere with, disrupt, overload, scan, or attack the service or connected infrastructure.
• Upload malicious code, exploit payloads, or content intended to compromise systems.
• Use FieldHash outputs as the sole basis for high-stakes decisions without appropriate human review.
• Remove, alter, or misrepresent audit, provenance, or ledger metadata in a way that creates a false record.

8. Intellectual Property

FieldHash, including its software, design, documentation, methods, interfaces, trademarks, and proprietary materials, is owned by FieldHash, Inc. or its licensors and is protected by intellectual property laws.

Except for rights expressly granted in a written agreement, these terms do not grant you ownership of FieldHash technology or permission to copy, modify, reverse engineer, resell, or create derivative works from the service.

9. Confidentiality and Security Review

Pilot materials, private demos, architecture notes, traces, benchmark artifacts, deployment details, and non-public evidence packages may be confidential. Do not disclose non-public FieldHash materials unless permitted by written agreement.

If you discover a vulnerability or security issue, contact us promptly and do not exploit, publicly disclose, or access data beyond what is necessary to report the issue.

10. Fees and Enterprise Pilots

Fees, pilot scope, deployment configuration, support levels, data handling, and service commitments are governed by the applicable order form, statement of work, or written agreement. Public website materials do not create a service-level commitment unless incorporated into a signed agreement.

11. Disclaimers

FieldHash is provided "as is" and "as available" unless a separate written agreement states otherwise. To the maximum extent permitted by law, we disclaim implied warranties, including merchantability, fitness for a particular purpose, non-infringement, uninterrupted operation, error-free operation, and compliance with any particular law or standard.

12. Limitation of Liability

To the maximum extent permitted by law, FieldHash is not liable for indirect, incidental, special, consequential, exemplary, or punitive damages, or for lost profits, lost revenue, lost data, business interruption, or substitute services arising from your use of FieldHash.

Any liability cap or exceptions in a signed enterprise agreement will control for that customer relationship.

13. Changes to Terms

We may update these terms from time to time. Continued use of FieldHash after the effective date of updated terms constitutes acceptance, unless a separate written agreement provides otherwise.

14. Contact

For questions about these terms, contact: support@fieldhash.ai