Data & Privacy
Your course data is not a sales tool.
Some platforms in this space have started quoting other courses' moisture levels and sensor data on sales calls. That is not how RootView works, and it never will be. Your readings, your program, and your operational decisions belong to you alone.
Your data · your course · no exceptionsNo cross-course sharing
We never share your sensor readings, VWC levels, disease pressure, spray records, or any other course data with other clubs, superintendents, or third parties. What happens on your greens stays on your greens.
Your trade secrets stay yours
Irrigation patterns, moisture targets, application timing, and the operational decisions behind your program are competitive knowledge. We do not surface your data, or insights derived from it, to anyone outside your authorized team.
Staff access only with permission
RootView staff have limited, role-based access for platform operations. We only sign into your account when you ask us to, for onboarding, troubleshooting, or support, and we treat that access as working on your behalf, not as a window into your program for anyone else.
We will never tell another superintendent what your VWC looks like
If a vendor can describe another club's rootzone moisture, spray history, or disease pressure on a phone call, that data is being shared, whether or not anyone used the word “benchmark.” That undermines trust in the whole category, and it puts your operational intelligence at risk.
RootView is built for superintendents who need accurate readings for their own turf, not a league table of who is wetter than whom. Aggregated industry research may inform our product over time, but identifiable course data is never disclosed to other customers, prospects, or partners.
What we do not do
- Share live or historical sensor data between courses
- Quote one club's moisture or EC levels to another club
- Use your program details in sales demos without your written consent
- Sell or license course-level datasets to third parties
- Let staff casually browse accounts outside an authorized support session
How RootView staff access your account
We need occasional access to deliver the product, pairing sensors, fixing a gateway, walking a new admin through the dashboard. That access is always initiated by you or tied to a support request you open. It is not standing permission to monitor your operation.
When we work inside your account, we are acting as an extension of your team for that task. We log support-related access, limit it to what the job requires, and we do not carry what we see into conversations with other courses.
Staff access is for
- Support and onboarding when you invite us in
- Debugging sensor connectivity or dashboard issues you report
- Configuration help during initial setup or seasonal changes
- No browsing course data without a ticket or explicit request from your team
- No using one course's readings to inform conversations with another
You own the data - we protect it
Your sensor readings, weather context, disease model outputs, and event logs are your course's property. The RootView AI assistant answers using only your data and shows the numbers behind every response. We store and process it to run the platform you subscribed to, not to build a cross-course intelligence product.
Access inside your organization is invite-only and role-based: course admins control who on staff can see what. Management groups operating multiple courses see only the courses they are explicitly assigned, never a neighbor's readings by default.
Questions about retention, export, or a specific support session? Contact us, we are happy to walk through how your data is handled in plain language.
Questions about your data?
Ask us directly.
If data handling is part of your vendor evaluation, tell us what you need to see. We will explain our practices, and we will never ask you to trust a handshake over another course's numbers.