Privacy Policy
How the standard Almond service handles account, site, operational, and end-user data.
1. Roles and scope
This policy covers personal data Almond handles for its own accounts, service security, and operations. For personal data a customer or its agent places in a site, form, file, or record, the customer generally determines the purpose and means of processing and Almond generally acts as its processor or service provider. The customer's privacy policy, not this one alone, must explain the customer's site-level processing.
2. Data we process
| Category | Account identifiers such as name, email, optional profile image, password verifier, Google sign-in identifier, sessions, and authorization records. |
|---|---|
| Customer content | Published HTML, files, domains, collection definitions, submitted form fields, structured records, revisions, and export data chosen by the customer or its agent. |
| Operational data | Capability metadata, timestamps, usage counters, browser error messages and optional user-agent strings, and hashed client fingerprints used for abuse controls. Raw source IP addresses are not stored in the rate-limit table by the application. |
| Communications | Support, commercial, security, and legal communications provided to the operator. |
3. Why we process data
We process data to provide and secure accounts and sites, execute authorized publication and data operations, authenticate users and agents, maintain revisions and recovery functions, diagnose errors, prevent abuse, provide support, comply with law, and improve service reliability. Depending on context, the legal basis may be performance of a contract, legitimate interests in operating and securing the service, consent, or a legal obligation.
4. Agentic harnesses and third parties
Almond receives the requests a connected harness sends to it, but Almond does not control what that harness previously collected, inferred, retained, or disclosed. A harness may send customer or end-user data to model providers, tool providers, observability systems, or other services before or after calling Almond. The customer must evaluate those flows, configure retention and training controls, provide required notices, and enter any required agreements with those providers.
5. Disclosures and subprocessors
Data may be disclosed to infrastructure, authentication, domain, security, and support providers that help operate the service, and when required by law or a valid legal process. The standard deployment uses Convex for application compute, database, and file storage; Google only when a user chooses Google sign-in; and AWS services when managed custom-domain provisioning is used. A customer may request then-current subprocessor information through its contractual contact.
6. Retention and deletion
Data is retained while needed to provide the service, secure it, meet legal obligations, resolve disputes, and enforce agreements. Retention can differ by data type. Expired sessions, authorizations, and security counters are removed on operational schedules. Revisions, runtime errors, and customer records may persist until removed through available product controls, account deletion, or an agreed deletion request. Backups may age out separately. Customers are responsible for implementing site-level retention and handling end-user requests.
7. Security
Almond uses measures designed for the service's risk, including scoped capabilities, hashed credentials, tenant authorization checks, origin separation, rate limits, and restricted infrastructure identities. No system is completely secure. Customers must secure their harnesses, accounts, endpoints, credentials, generated applications, and downstream exports.
8. Rights and international transfers
Depending on location, a person may have rights to access, correct, delete, restrict, object to, or receive certain personal data. Site end users should first contact the customer operating that site because Almond may act only on that customer's instructions. Data may be processed where Almond and its providers operate, subject to contractual or other lawful transfer mechanisms where required.
9. Children and changes
The standard service is not directed to children and customers must not collect children's data without all required authority, safeguards, and agreements. We may update this policy and will revise the effective date when changes are material.