Why we use service providers
A modern farm platform may rely on cloud services for hosting, delivery, communications, payments, analytics and other specialised functions. Providers should process only information appropriate to their service and contractual role.
Public website
| Service | Function | Data potentially processed |
|---|---|---|
| KraalSense website | Public pages and forms | Connection and form details as required for delivery |
| Google advertising (optional) | Advertising scripts deferred until marketing consent | Information governed by Google’s services and policies; exact deployment needs audit |
Application infrastructure
The supplied KraalSense architecture references AWS services, including computing, storage, database and email infrastructure. Actual processing locations, active processors, backup scope and vendors should be taken from the deployed account configuration, not assumed from architectural diagrams or development files.
Communications and payments
Depending on configuration and jurisdiction, services may connect to email providers, messaging gateways and payment processors. The list of currently enabled third parties, their country, purpose and data categories must be confirmed by the owners of the production integrations.
AI features
KraalMind may call an external model provider for some tasks. Model names, data handling, regions, retention terms and contractual protections are implementation-dependent and should be verified before supplier-specific statements are published.
Provider review and updates
This document is deliberately conservative: no unverified supplier is described as contracted, certified, or in production. Once the production vendor register is approved, replace provisional descriptions with the provider, location, purpose and information handled.
Questions about this document? Email KraalSense or contact us.