What we collect, what we never do, and how we keep your data safe.
Plain English. No legalese. This is how we actually handle your data.
What we collect
Only what the system needs to work. Nothing more.
Sensor readings
Soil moisture, temperature, humidity, wind, nutrients, and every other measurement your nodes produce. These are the core of the service.
Account information
Your name, email, organisation, and property details. Enough to identify your account and contact you about your service.
Knowledge base uploads
Block notes, spray logs, observations, and any documents you choose to upload to help the AI understand your land better.
What we never do
Your data is yours. Full stop.
- We never sell your data. Not to aggregators, not to researchers, not to anyone.
- We never expose your raw data to other customers. No pooled data layer, no benchmarking feature that reveals your readings, notes, or blocks to anyone else. Your account is isolated end to end.
- We never hold it hostage. Export everything, any time, in standard formats, and delete it on request.
How we keep it separate
Per-account silo architecture. Your data cannot leak into another customer's view.
Every account's data lives in an isolated silo. Database-level row security policies enforce this, even if application code had a bug, the database itself prevents cross-account access.
AI embeddings (the vectors the AI uses to understand your knowledge base) are stored in per-account schemas. One customer's knowledge base is physically separate from another's.
This isn't a flag on a shared table. It's architectural isolation, enforced at every layer.
How we keep it safe
Encryption, identity management, and audit trails.
Encryption in transit
All data between your browser and our servers travels over TLS. Sensor data from gateway to cloud is encrypted end-to-end.
Encryption at rest
Database storage is encrypted at rest. Backups are encrypted. File uploads are encrypted in object storage.
Identity via Kinde
Authentication is handled by Kinde, a dedicated identity provider. We don't store passwords. Login, MFA, and session management are handled by specialists.
Audit logs
Every significant action, login, data export, configuration change, automated action, is logged with timestamp, actor, and detail. Logs are append-only and retained.
Support access that expires
When our staff help you set up, they enter on an ordinary grant with a written reason and an expiry. It shows on your People list, they see a countdown on every screen, and it lapses on its own. There is no standing back door.
What happens if you leave
Export everything. We delete on request.
You can export your full dataset, sensor readings, AI recommendations, knowledge base documents, account configuration, at any time. Standard formats, no proprietary lock-in.
If you cancel your subscription and request deletion, we remove your data from active systems. After a short retention period (to handle any billing or support issues), it's purged from backups too.
We don't hold your data hostage. If you leave, your data leaves with you.
Security contact
Responsible disclosure welcome.
If you find a security vulnerability in TerraCast, we want to hear about it. Report it to security@terracast.app and we'll acknowledge within 24 hours.
We don't run a formal bug bounty programme yet, but we'll work with you in good faith, credit you (if you want), and fix the issue promptly.
For general security questions, the same address works. We'd rather answer questions than have you wonder.