Operator-owned records
Your apiary, hive, treatment, staff, customer, stock and report records remain your operating material.
Data ownership
Your operating records remain yours.
BuzzTech uses operator records to deliver the agreed software, workflow, reporting, support, AI and integration services. We do not publish operator data, real locations, customer details or commercially sensitive examples without permission.
Limited service use
Data is used to run the system, support your team, prepare agreed reports and connect approved integrations.
Public use requires approval
Case studies, screenshots, maps, customer examples and operator stories are not published without permission.
Demo-safe proof
Shared examples use fictional names, redacted values, representative reports and anonymised or synthetic locations.
Human-reviewed AI
AI-assisted drafts stay under human review before they become work instructions, records or external communication.
Export and continuity
Useful records, reports and export packs are available for operational continuity when agreed or requested.
Operator data charter
Trust needs clauses, not just sentiment.
The operating standard is simple: protect the business advantage inside the records while still making the system useful for support, reporting, compliance and continuous improvement.
- Support access is limited to helping deliver or troubleshoot the agreed service.
- Sensitive forms, declarations, staff notes and internal reports are treated as private operational material.
- AI-assisted work does not turn private operator records into public examples or public training material.
- Exports should preserve practical value: dates, sites, hives, actions, evidence, reports and useful history.
During setup
Agree what data is imported, who can access it, which reports matter and what must never be used publicly.
During support
Use the minimum practical context to diagnose issues, prepare reports or help a team complete the workflow.
During proof
Use demo-safe screenshots, anonymised maps and representative records unless a named case study is approved.
During transition
Keep continuity in view with practical exports, report packs and handover-friendly evidence.
Public proof standard
Show the workflow without exposing the operator.
A shared example can show field states, report structure, sensor exceptions, corrective action flow and batch evidence without revealing real apiary locations, customer names, stock position or commercially sensitive values.
Redaction ruleThe audience should understand how the workflow works, not who the operator is, where their sites are, or what their business position is.
Privacy-safe pilot
Plan the first workflow with ownership, exports and public proof agreed up front.
A good pilot names the workflow, the private records involved, the report or export that proves value, and the redaction rules for anything shown outside your business.
Privacy standardWe do not publish operator data, customer details, locations, screenshots or case examples without permission.