Trust & policies
Acceptable use
Keep Agsemble safe, lawful, predictable, and appropriate for an early agricultural developer platform.
Permitted use
Use Agsemble to evaluate, prototype, test, and operate agricultural software within the limits of the selected plan and the licenses attached to provider-derived data.
Prohibited use
- Illegal, fraudulent, deceptive, infringing, abusive, or harmful activity
- Bypassing authentication, verification, rate limits, field-slot limits, or one-Sandbox-per-email controls
- Probing, scanning, disrupting, overloading, or attempting unauthorized access to Agsemble, another tenant, or an upstream provider
- Sharing API keys or recovery codes publicly, embedding them in a distributed mobile binary, or using another tenant's credentials
- Reselling or bulk redistributing raw provider data except where the displayed source license expressly permits it
- Submitting passwords, payment-card data, government identifiers, health data, biometric data, or other sensitive personal data in field metadata or observation notes
- Using agricultural outputs as the sole basis for a safety-critical, credit, insurance, land-title, regulatory, pesticide, or agronomic decision without qualified human review
Boundaries and provider data
Satellite-suggested boundaries are mapping aids, not cadastral parcels, ownership records, surveys, or legal boundaries. Preserve the source and license object when displaying, exporting, or transforming provider-derived data.
Enforcement
Agsemble may throttle, suspend, or terminate access needed to stop abuse, protect users or providers, meet legal obligations, or prevent material platform harm. When practical, Agsemble will provide notice and a way to export startup-owned data.