Effective August 21, 2026 · Provider: Yeira Inc.

Additional Terms of Use

Terms for using almond.build with an AI agent, automation, or agentic harness.

The service boundary. Almond is an agent-agnostic, lightweight publishing and persistence process. It does not select, train, supervise, or control the AI model, agent, agentic harness, prompts, tools, or external systems that a customer connects. Those components remain separate services under the customer's direction.

1. Provider, agreement, and priority

Almond and almond.build are provided by Yeira Inc., a United States company (“Yeira,” “Almond,” “we,” or “us”). These Additional Terms supplement any general terms, order, or other agreement governing access to almond.build (together, the “Agreement”). By connecting an agentic harness, publishing a site, or using an Almond capability, the customer accepts these Additional Terms. A signed agreement controls if it expressly conflicts with this page.

2. What Almond provides

Almond provides a narrow process for publishing and retaining customer-directed websites, forms, files, structured records, revisions, operational diagnostics, protected fixed-endpoint actions, and related configuration. Almond exposes interfaces that compatible agents and tools may call. Almond is not the customer's AI provider, agent developer, external endpoint provider, system integrator, legal adviser, or compliance decision-maker.

3. Customer and harness responsibilities

The customer is responsible for selecting, configuring, authorizing, monitoring, and revoking its AI models, agents, harnesses, tools, and integrations. This includes responsibility for:

the prompts, instructions, context, credentials, permissions, and data supplied to them;
reviewing generated code, content, schemas, forms, and actions before and after publication;
ensuring the harness requests only necessary scopes and protects every capability, session, and recovery credential;
implementing human review, testing, logging, approval gates, spending limits, and emergency stops appropriate to the use case;
the accuracy, legality, accessibility, security, and regulatory status of customer content and collected data; and
the conduct of end users and notices, consents, policies, and response processes required for the customer's site.

4. Acceptable use

The customer must not use Almond to violate law or third-party rights, distribute malware, evade security controls, conduct deceptive or abusive activity, interfere with the service, probe another tenant, or publish content the customer lacks authority to use. High-impact decisions involving health, employment, housing, education, credit, insurance, legal services, public benefits, or similar rights require appropriate qualified human oversight and may not rely on Almond as the decision-maker.

5. Customer content

The customer retains its rights in customer content and grants Almond a limited right to host, copy, transmit, secure, and process that content only to provide, maintain, protect, and support the service. The customer represents that it has the rights and lawful basis needed for those activities. Public pages and public-read collections are intentionally available to anyone with the applicable URL. When the customer enables a protected server action, it also instructs Almond to transmit the action's explicitly projected fields to the customer-approved safe hostname. The customer is responsible for the recipient, purpose, notices, data minimization, endpoint credentials, provider terms, and downstream retention and behavior.

Third-party identity and remote media

If a user chooses Google sign-in, Google's terms and privacy policy also govern Google's service. The Almond account page loads Google Identity Services so the sign-in option can be offered. If a user or Google profile supplies a remote avatar URL, the browser requests that image from its host, which may receive the user's IP address and browser metadata. Account avatar requests are configured with a no-referrer policy. The customer and user must have authority to use any supplied image and should remove the URL if that external request is not appropriate.

6. Credentials and authorization

Agent and site capabilities act as authorization credentials. Actions performed with a valid credential may be treated as customer-authorized. Protected endpoint values are write-only and cannot be recovered through normal product interfaces; the customer must retain or rotate source credentials at the external provider. The customer must use least privilege, avoid placing credentials in published content or model outputs, and promptly revoke any credential that may be exposed. Almond may suspend credentials, triggers, dispatch, or activity that threatens the service or others.

7. Changes, availability, and output

Agent-generated output can be incomplete, insecure, inaccurate, or unsuitable. Publication, rollback, storage, domain, and export features may change and are not a substitute for the customer's own review, records, backup strategy, or business-continuity plan. Unless a signed agreement says otherwise, the service is provided on an as-available basis and no particular legal or industry certification is promised.

8. Indemnity and liability

To the extent permitted by law, the customer is responsible for claims arising from customer content, the customer's site, its end-user relationship, or its selection and operation of an agentic harness. Any warranty disclaimers, liability limits, indemnities, governing law, and dispute terms in the primary Agreement also apply here.

9. Contact and changes

Questions, legal notices, privacy requests, and security reports should be directed to Yeira Inc. through the contact method in the customer's order or account relationship. Material changes will be dated on this page. Continued use after the effective date constitutes acceptance where permitted by law.