Security & data governance
Political data requires serious infrastructure.
Grasshopper is designed around the assumption that every record is sensitive. This page explains, plainly, how deployments, access and data are handled.
Private by architecture
Not one shared workspace for everyone.
Customer deployments can be isolated from one another, rather than placing unrelated political organisations in a single shared operational workspace. Each licensed organisation works in its own deployment with its own users and data.
Access control
Only the access each role needs.
Access is defined by role and by territory. Users receive only the operational access required for their responsibilities.
- National AdminWhole deployment
- OrganizerTheir constituency
- Team LeadTheir districts and team
- CanvasserTheir assigned walks
Data ownership & control
Your organisation stays in control of its data.
Organisations remain responsible for, and in control of, the data they lawfully provide to their deployment.
Imports
Administrators decide what data enters the deployment, with a review step.
Exports
Exports are restricted to authorised roles.
User access
Invitation-only accounts, created and removed by your administrators.
Administration
Your organisation configures roles, territories and structure.
Retention & deletion
Retention and deletion are configured with your organisation.
Auditability
Know who changed what, and when.
Important operational changes can be recorded, so administrators can understand who changed information and when.
Deployment
One platform. Separate deployments.
Users and data in one deployment are not visible to another.
Need a technical review before deployment?
We'll walk your technical or legal advisers through how a deployment is set up.