Privacy
What we hold, and what we cannot
An election tool that is vague about data is not worth trusting with one. This says what is stored, who can see it, and which questions the system is built to be unable to answer.
Last updated 23 September 2026
Who is responsible for what
Two different roles sit behind one screen, and they matter for your rights.
| Role | Who |
|---|---|
| The organization | The university, association, church, union or cooperative running the election. They decide who is on their roll and what an election is for. For that member data they are the controller. |
| Adventle | We operate the software and store the data on their instruction. For member data we are a processor. For your own administrator account — your name, email, sign-in history — we are the controller. |
If you are a voter and want your details corrected or removed, ask your organization first: it is their roll. We will act on their instruction, and we will also act on a direct request from you where the law requires it.
What we store
| Data | Why |
|---|---|
| Account details | Name, email, phone and a hashed password for each administrator. Needed to sign you in, to recover your account, and to record who did what. |
| Member roll | Name and at least one of phone, email or membership number for each member, plus anything extra the organization chose to upload. This is what invitations are sent to and what a voter is checked against. |
| Election records | Titles, positions, candidates, manifestos, schedules and the ballots cast. |
| Eligibility records | That a given member was entitled to vote in a given election, and whether they have voted. Never what they chose. |
| Audit trail | Every administrative action: who opened an election, changed its electorate, sent invitations, and when. |
| Technical records | Request logs, IP addresses and error reports, kept to run the service and investigate abuse. |
Ballot secrecy
This is the part that matters most, so it is stated precisely rather than reassuringly.
- A cast ballot carries no voter. There is no column on it pointing at a person, and no key elsewhere that would join the two back together.
- Turnout is still answerable because a separate record says that somebody voted. It does not say what they chose.
- The receipt a voter is given is derived from their voting permission, not from their selections. It can confirm a ballot was recorded. It cannot reveal, to them or to anybody else, how they voted — which is what stops it being useful to somebody buying votes.
- Voting codes and one-time codes are stored hashed. Nobody, including us, can read one back out.
We cannot tell you how somebody voted
Not through the interface, not from the database, and not if a court asks. The information does not exist in a form anybody can query. This is a property of how the data is stored, not a promise about how we behave.
Messages we send
Invitations, verification codes, password resets and election notices go out by email, SMS and WhatsApp through third-party gateways. To do that we pass them the recipient’s address or number and the message itself. We do not send marketing to a member roll, and we do not sell or rent contact details to anybody.
Delivery status is recorded against the invitation so an administrator can see who could not be reached.
Who else processes data
We use a small number of providers to run the service. Each receives only what its job needs.
| Provider | For |
|---|---|
| Hosting and database | Running the application and storing its data. |
| Email delivery | Sending invitations, verification links and password resets. |
| SMS and WhatsApp gateways | Sending codes and invitations to phones, and carrying USSD and WhatsApp votes. |
| Payment processor | Taking payment for your subscription. Card details go to them and never reach us. |
Where data lives, and for how long
Data may be processed outside the country your organization is in, because some of the providers above operate internationally. Where that happens we rely on the provider’s own contractual safeguards.
| Record | Kept |
|---|---|
| Member roll and elections | While the organization's account is active, and for as long as they choose to keep them. |
| Audit trail and results | Longer than the election, deliberately: a result that can be questioned years later needs a record that outlives the dispute. |
| Voting codes and one-time codes | Until used or expired, then unusable. The plaintext never existed in storage at all. |
| Technical logs | A short operational window, then discarded. |
When an organization closes its account we delete its data on request, except anything we are required to retain.
Your rights
Depending on where you are, you may have the right to ask for a copy of your data, to have it corrected, to have it deleted, to object to how it is used, or to complain to a data protection authority. In Ghana that is the Data Protection Commission.
One right has a limit worth saying plainly: we cannot give you a copy of your ballot, because no such record exists. That is the point of a secret ballot.
Security
- Passwords and voting codes are stored hashed, never in a readable form.
- Traffic is encrypted in transit.
- Access to an organization's data is scoped to that organization, and administrators have roles that limit what each of them can do.
- Administrative actions are recorded in an append-only audit trail.
No system is beyond compromise. If a breach affects your data we will tell your organization and, where required, the regulator.
Changes and contact
If this policy changes in a way that materially affects you, we will say so rather than quietly updating the date. Questions about your data can go to privacy@mandatevote.com, or through a support ticket from your dashboard.