Security and confidence
Security is a process, not a badge.
Trust in a voting platform should come from clear controls, careful operation and records that can be reviewed — not from a logo on a page.
Talk to us about your requirementsClear about what we can — and cannot — claim.
We do not claim IBBI approval, government certification or guaranteed statutory compliance.
Security depends on configuration, operation and the process adopted by the organiser.
We will always be specific about what a control does, rather than hide behind a slogan.
Our approach
Four principles that shape the platform.
These principles guide the way a voting event is set up, accessed, recorded and reviewed.
Access is part of the design
Participants access the voting event through the route defined by the organiser, with roles and permissions tied to the event.
Controlled participation
The participant list and voting window help define who can take part and when a vote can be recorded.
A record of activity
Key actions are captured in a structured activity trail to support review, questions and internal documentation.
Results you can review
Voting outcomes are presented with participation information, so the result can be read in context.
What we design for
Confidence comes from the details.
A serious voting process has many small control points. We focus on making those points visible, understandable and hard to overlook.
Discuss a specific requirementControlled access
Participant access is tied to the voting event and the role defined by the organiser.
Event-level settings
The organiser sets the voting window, participants and applicable rules for the matter.
Clear roles
Organisers, participants and support users should see only what their role requires.
Reviewable activity
Key actions are recorded in a structured trail to support questions and internal review.
Result context
Outcomes are presented with participation and voting-share information, not as an isolated number.
Responsible reporting
Reports are designed to be read and circulated, with the limits of the data made clear.
Due diligence
Questions worth asking any voting provider.
The right platform for a formal process should be able to answer practical questions clearly. We have included these because they matter more than a long list of security adjectives.
- 01Who can access a voting event, and how is that access tied to the participant?
- 02What controls determine when a vote can be recorded or changed?
- 03What activity is recorded, and who can review it?
- 04How is enquiry data handled, and where is it stored?
- 05What happens if a participant cannot access the system during the voting window?
- 06What reports are produced, and what do they include?
- 07How are security issues reported, investigated and communicated?
- 08What arrangements exist for data retention and deletion?
The answers will depend on the specific service, configuration and operating arrangements. We are happy to discuss ours in context.
About this website
The public site is intentionally simple.
This website is a static public site. It does not host the voting application and does not accept case documents or voting data.
Enquiries made through this site are used to respond to your request. Please do not send confidential case material through the contact form.
The voting application is separate. Access, data handling and operational security arrangements for a voting event are covered during onboarding and in the applicable service terms.
Read the privacy noticeSecurity and records
Have a specific security or record-keeping requirement?
Tell us what your team needs to review, retain or explain. We will be straightforward about what the platform can support.