Privacy Policy
- Version
- 1.0
- Last revised
- 2026-05-09
- Effective
- 2026-05-09
This Privacy Policy explains how VoteEdge collects, uses, shares, and protects personal data in connection with our marketing website, our software-as-a-service platform, our election-day agent enrollment flow, and our public contact form.
Because the VoteEdge platform is sold to customers operating in multiple African markets, this policy is multi-jurisdictional. Where a national data protection statute imposes specific obligations, those obligations are referenced inline by their statutory citation, and a per-country annex at the end (clause 18) summarises the country-specific points.
1.Who we are
The VoteEdge platform is operated by VoteEdge (“VoteEdge”, “we”, “us”).
You can reach us at:
- General contact: hello@voteedgeng.com
- Privacy + data-subject rights: hello@voteedgeng.com
- Security incident reporting: hello@voteedgeng.com
- Phone: +234 706 155 1969
Our designated Data Protection Officer (or equivalent accountability lead, depending on the jurisdiction) is our Privacy Team, reachable at the email above.
2.Scope of this policy
This policy applies to personal data we process in connection with:
- visitors to our marketing website at
https://voteedgeng.comand its country sub-pages; - signed-in users of the VoteEdge application (Authorised Users acting on behalf of a Customer);
- field agents enrolled via the public election-day enrollment flow (see clause 3.4 and the field-agent annex at clause 18.6);
- inquirers who submit our public contact form;
- recipients of our transactional or operational email (renewal notices, password resets, expiry reminders).
This policy does not cover personal data processed by our Customers within their own Projects, where VoteEdge acts as a processor on the Customer’s instructions. For that processing, the Customer is the controller, and the Customer’s own privacy notice applies.
3.Categories of personal data we process
3.1Marketing-website visitor data
IP address, user agent, timestamps, and (where applicable) cookie identifiers used to remember preferences and to measure traffic. Where we use any non-essential cookies, we obtain consent — see the Cookie Policy.
3.2Authorised User account data
Email address, full name, phone number (optional), role assignments, password hash (we never see your plain password), session token, audit-log metadata of actions you take in the platform, multi-factor-authentication enrolment (where enabled), and locale + timezone preferences.
3.3Inquirer data (public contact form)
Name, email address, business or organisation name, country, free-text message, and (where supplied) preferred response channel.
3.4Field-agent enrollment data
Phone number, one-time passcode (transient), selfie photograph (biometric data), device fingerprint, IP address, and timestamp. The Customer running the relevant Project is the controller for this data; VoteEdge processes it on the Customer’s instructions. See clause 18.6 for the field-agent annex.
3.5Election-day operational data
For Authorised Users with field-collection or election-day roles: GPS coordinates during work shifts (used for geofence verification and audit), result-report content entered by the agent, and result-form photograph attachments.
3.6Communications data
In-app messages between Authorised Users on the same Project, supervisor remediation notes, and email metadata associated with operational notifications.
3.7Audit metadata
For every privileged action (user role grant, project extension, project archive, QC reject, permanent delete, login failure, password reset), we record the actor identifier, timestamp, IP address, and a structured metadata payload describing the action. This audit log is retained for the minimum retention period applicable to the relevant jurisdiction (see clause 10).
4.Lawful basis per processing operation
The table below states the lawful basis on which we process each category of personal data, in each jurisdiction. The named statute is in addition to any other lawful basis that may apply.
| Processing | Purpose | NG (NDPA s. 25) | GH (Act 843 s. 20) | KE (DPA s. 30) | ZA (POPIA s. 11) | RW (Law 058 art. 7) |
|---|---|---|---|---|---|---|
| Authorised User account | Authenticate users; provide platform access under the Customer Agreement. | Performance of contract (s. 25(b)); legitimate interest (s. 25(f)). | Performance of contract; lawful purpose (s. 20). | Performance of contract (s. 30(b)). | Performance of contract (s. 11(1)(b)). | Performance of contract (art. 7(1)(b)). |
| Field-agent enrollment (phone, OTP) | Verify the agent’s identity for election-day duties. | Consent (s. 25(a)); contract (s. 25(b)). | Consent (s. 20(c)). | Consent (s. 30(a)); contract (s. 30(b)). | Consent (s. 11(1)(a)). | Consent (art. 7(1)(a)). |
| Biometric (selfie) | On-the-day re-verification that the operator at the polling unit matches the enrolled agent. | Explicit consent (s. 30(2)(a)). | Explicit consent (s. 35(1)(a)). | Explicit consent (s. 44(1)). | Explicit consent (s. 27). | Explicit consent (art. 5(2)). |
| GPS during shifts | Geofence verification of in-precinct work; audit; safety. | Legitimate interest (s. 25(f)) balanced; consent at enrollment (s. 25(a)). | Lawful purpose (s. 20); consent. | Legitimate interest (s. 30(f)); consent. | Legitimate interest (s. 11(1)(f)). | Legitimate interest (art. 7(1)(f)). |
| Audit log of mutations | Security; integrity; dispute resolution; regulatory accountability. | Legal obligation (s. 25(c)); legitimate interest (s. 25(f)). | Lawful purpose (s. 20). | Legal obligation (s. 30(c)); legitimate interest. | Compliance with law (s. 11(1)(c)); legitimate interest. | Legal obligation (art. 7(1)(c)). |
| Operational email (renewal, expiry) | Manage the access window, contractual renewals, and security notices. | Performance of contract (s. 25(b)). | Performance of contract. | Performance of contract (s. 30(b)). | Performance of contract (s. 11(1)(b)). | Performance of contract (art. 7(1)(b)). |
| Inquirer (contact form) | Reply to a prospective customer’s enquiry. | Legitimate interest (s. 25(f)) — replying to enquiry. | Lawful purpose (s. 20). | Legitimate interest (s. 30(f)). | Legitimate interest (s. 11(1)(f)). | Legitimate interest (art. 7(1)(f)). |
| Sub-processor sharing | Operate hosting, email, SMS, object storage, and timestamping services. | Performance of contract; legitimate interest. | Lawful purpose; consent at agent enrollment. | Performance of contract. | Operator obligation (s. 21). | Performance of contract. |
Where we rely on legitimate interest, the interest is described in the table above. For each such row, we document the balancing test that confirms the interest is not overridden by the data subject’s rights and freedoms; that documentation is available to regulators on request.
Secondary analytical purpose (Campaign Diagnostic module). Where the Customer has licensed the optional Campaign Diagnostic module, the aggregated, de-identified survey responses for that Project are analysed to produce location-level findings and campaign recommendations for the Customer’s candidate. This analysis is performed on aggregated data only; it does not single out, re-identify, or target any individual respondent, and the survey instrument itself remains neutral and non-leading. This purpose is compatible with, and carried out under the same lawful basis as, the research purpose for which the responses were collected.
5.Special-category / sensitive personal data
We process two categories of special-category data:
5.1Biometric (field-agent selfie)
Collected only during field-agent enrollment, with the agent’s explicit, specific, informed consent. Treated as special-category personal data under Nigeria (NG · NDPA 2023, s. 30), Ghana (GH · Act 843, s. 35), Kenya (KE · DPA 2019, s. 44), South Africa (ZA · POPIA, s. 26), and Rwanda (RW · Law N° 058/2021, art. 5(2)).
Stored encrypted at rest. Used only to verify the agent at check-in on election day, not for marketing, profiling, or any other purpose. Deleted in line with the retention schedule in clause 10. The agent may withdraw consent at any time; withdrawal does not affect lawfulness of processing carried out before withdrawal, and may end the agent’s ability to act on election day.
5.2GPS during shifts
Treated as personal data of significant sensitivity given its inferential power about the agent’s location and movements. Collected only while the agent is on shift, disclosed transparently in the agent privacy notice, and retained for the audit period. Not used for non-electoral purposes; never sold; never used to profile the agent outside the employment context.
6.Children's data
The platform is not intended for children. We do not knowingly collect personal data from individuals under the age of 18. Authorised Users and field agents must be of legal age to contract for employment in their jurisdiction. If we learn that we have inadvertently collected personal data from a child, we will delete it.
The data protection laws of each jurisdiction impose specific obligations regarding children’s data: see (NG · NDPA 2023, s. 31), (KE · DPA 2019, s. 33), (ZA · POPIA, s. 34), (GH · Act 843, s. 32), and (RW · Law N° 058/2021, art. 14).
7.Sources of personal data
We collect personal data from the following sources:
- directly from the data subject (visit, sign-up, enrollment, contact form);
- from our Customers, who upload rosters of their Authorised Users and (in some markets) of polling agents;
- generated by our systems as a result of your use of the platform (audit logs, session metadata, derived analytics).
We do not buy personal data from data brokers, and we do not enrich personal data from third-party social or commercial databases.
8.Recipients
We share personal data with the following categories of recipient:
- VoteEdge personnel who need to access it to operate the platform, support you, or investigate a security or compliance event;
- the Customer running the relevant Project, in respect of personal data collected within that Project;
- sub-processors who provide hosting, object storage, email delivery, SMS delivery, error monitoring, and timestamping services on our behalf — see the Data Processing Agreement, Annex A;
- professional advisers (lawyers, accountants, auditors) under a duty of confidence;
- law-enforcement, regulatory, or governmental bodies in response to a binding legal request.
We do not sell personal data, and we do not share personal data with third parties for those parties’ own marketing purposes.
The current sub-processor list is available on request via the privacy contact above and is also enumerated in Annex A of the Data Processing Agreement.
9.Cross-border transfers
Some of our sub-processors process personal data in countries other than the country in which the data subject is located. When that occurs, we put in place appropriate transfer safeguards under the law of the originating country, namely:
- Nigeria (NG · NDPA 2023, s. 41): transfer to a country with adequate protection as recognised by the Nigeria Data Protection Commission, or (where such recognition has not been issued) under specific safeguards including binding corporate rules, standard contractual clauses, or the data subject’s explicit consent;
- Ghana (GH · Act 843, s. 47): transfer to a country with an adequate level of protection or under an authorisation from the Data Protection Commission;
- Kenya (KE · DPA 2019, ss. 48-49): transfer where appropriate safeguards are in place (including standard contractual clauses approved by the ODPC), or with the data subject’s explicit consent;
- South Africa (ZA · POPIA, s. 72): transfer to a recipient subject to a law, binding corporate rules, or binding agreement that provides an adequate level of protection, or with the data subject’s consent, or where the transfer is necessary for the conclusion or performance of a contract;
- Rwanda (RW · Law N° 058/2021, art. 48-49): transfer to a country with adequate protection or under specific safeguards approved by the supervisory authority.
The specific transfer instrument used for each sub-processor pair is documented internally and is available on request via the privacy contact above..
10.Retention
We retain personal data for the period necessary to fulfil the purposes described in this policy, plus any minimum statutory retention floor that applies in the relevant jurisdiction.
Project-level data follows the Customer Agreement’s retention schedule: a default minimum of one (1) year from expiry of the Access Window, subject to country-specific statutory minima below. We may, at our discretion and for operational, re-engagement, or audit purposes, retain Customer Data for longer than the contractual one-year minimum; the Customer may request earlier deletion at any point (subject to the country-specific minima below).
- Nigeria: 180 days (NDPC guidance under (NG · NDPA 2023, s. 24));
- Ghana: 365 days (DPC guidance under (GH · Act 843, s. 24));
- Kenya: 365 days (ODPC guidance under (KE · DPA 2019, s. 39));
- South Africa: 5 years (1825 days), the POPIA principle of minimum-necessary retention applied to our specific processing context ( (ZA · POPIA, s. 14));
- Rwanda: 365 days ( (RW · Law N° 058/2021, art. 14)).
Audit-log metadata is retained for the longer of the applicable statutory minimum and 7 years, unless a binding legal hold or open investigation requires longer retention.
11.Your data subject rights
Depending on your jurisdiction, you have rights in respect of your personal data. The table below summarises those rights and the statutory references that grant them.
| Right | NG (NDPA) | GH (Act 843) | KE (DPA 2019) | ZA (POPIA) | RW (Law 058) |
|---|---|---|---|---|---|
| Right of access (copy) | s. 34 | s. 35 | s. 26(a) | s. 23 | art. 21 |
| Rectification | s. 35 | s. 36 | s. 26(b) | s. 24 | art. 22 |
| Erasure | s. 34(2)(d) | s. 39 | s. 26(d) | s. 24(1)(b) | art. 23 |
| Restriction | s. 37 | limited; see s. 36 | s. 26(c) | s. 24(1)(c) | art. 26 |
| Data portability | s. 36 | not separately enumerated | s. 26(g) | limited | art. 25 |
| Object to processing | s. 36 | limited | s. 26(c) | s. 11(3) | art. 24 |
| Withdraw consent | s. 27 | s. 20(c) | s. 32 | s. 11(2)(b) | art. 7(2) |
| Object to automated decision | s. 37 | s. 41 | s. 35 | s. 71 | art. 27 |
| Lodge complaint with regulator | NDPC, s. 51 | DPC, s. 42 | ODPC, s. 62 | Information Regulator, s. 74 | NCSA, art. 36 |
Each right is exercisable subject to the limits, conditions, and exceptions stated in the relevant statute. Where a right is not explicitly enumerated in a particular statute, an analogous right may still be available under general principles of that statute.
12.How to exercise your rights
To exercise any of the rights described in clause 11, contact us at hello@voteedgeng.com with:
- your full name;
- the email address associated with your account or enrollment, if any;
- the country in which you are located;
- which right you wish to exercise and which personal data you are referring to;
- any documentation that helps us verify your identity (we will not act on requests we cannot reasonably verify, to protect against impersonation).
We respond within the response time required by the data protection law applicable to you:
- Nigeria: within one (1) month of receipt (NDPA s. 34(2) );
- Ghana: within forty (40) days of receipt for an access request (Act 843 s. 35(2));
- Kenya: within seven (7) days of receipt (DPA s. 26(2));
- South Africa: within a reasonable time and in accordance with the Promotion of Access to Information Act framework (Form 2);
- Rwanda: within thirty (30) days of receipt (Law N° 058/2021 art. 21(3) ).
Where your request is manifestly unfounded, excessive, or repetitive, we may refuse it or charge a reasonable fee, in accordance with the applicable statute. Where we refuse, we will tell you in writing why and how to seek redress.
13.Right to lodge a complaint
Without prejudice to your other rights, you may lodge a complaint with the data protection regulator of your jurisdiction:
- Nigeria: Nigeria Data Protection Commission (NDPC). Contact details available on the NDPC official website at ndpc.gov.ng.
- Ghana: Data Protection Commission of Ghana (DPC). Contact details available on the DPC Ghana official website at dataprotection.org.gh.
- Kenya: Office of the Data Protection Commissioner (ODPC). Contact details available on the ODPC official website at odpc.go.ke.
- South Africa: Information Regulator (South Africa). Contact details available on the Information Regulator official website at inforegulator.org.za.
- Rwanda: National Cyber Security Authority (NCSA), pending appointment of the supervisory authority specifically designated for data protection. Contact details available on the NCSA official website at cyber.gov.rw.
We encourage you to contact us first so we have the opportunity to address your concern.
14.Security
We design and operate the Platform in line with appropriate technical and organisational measures, having regard to the state of the art, the cost of implementation, the nature of the processing, and the risks to the rights and freedoms of data subjects. Our security commitments are set out in detail in the Data Processing Agreement, Annex B. They include:
- TLS in transit between your browser and our servers;
- at-rest encryption of stored personal data;
- role-based access control aligned to least-privilege principles;
- per-project tenant scoping enforced at the data-access layer;
- audit logging of every privileged mutation, with the actor identifier, timestamp, and IP recorded;
- hash-chain integrity for election-day result reports, allowing post-hoc verification that no row has been modified in place;
- multi-factor authentication available to all account holders;
- independent disaster-recovery procedures with documented restore drills.
We do not represent that our security measures are impenetrable or that no incident will occur. Where we have a reportable personal-data breach, we will notify the regulator and (where required) you within the timeframe required by the applicable statute (clause 15).
15.Breach notification
We notify the relevant regulator and (where required) the data subject within the timeframe required by each applicable statute:
- Nigeria (NG · NDPA 2023, s. 40): within 72 hours of becoming aware of the breach.
- Ghana (GH · Act 843, s. 30): without undue delay .
- Kenya (KE · DPA 2019, s. 43): within 72 hours of becoming aware of the breach.
- South Africa (ZA · POPIA, s. 22): as soon as reasonably possible after the breach has been discovered.
- Rwanda (RW · Law N° 058/2021, art. 30): within 48 hours of becoming aware of the breach .
16.Updates to this policy
We may update this policy from time to time. The version tag and last-revised date in the header reflect the current version. Where the change is material, we will give you notice in advance:
- by in-app message to logged-in users; and
- by email to the address associated with your account or enrollment.
For non-material clarifications, we may rely on publication on this page alone.
17.Contact us
For any privacy question, request, or complaint, please contact us at hello@voteedgeng.com.
18.Per-country annexes
The annexes below summarise the country-specific points that a data subject in each market is most likely to need.
18.1Nigeria
Statute: Nigeria Data Protection Act 2023 (NG · Nigeria Data Protection Act 2023 (NDPA)), which superseded the Nigeria Data Protection Regulation 2019 (NDPR). Both are still cited transitively while implementing regulations are issued.
Regulator: Nigeria Data Protection Commission (NDPC).
Lawful bases (s. 25): consent, contract, legal obligation, vital interests, public interest, legitimate interests.
Sensitive categories (s. 30): include biometric, genetic, health, racial or ethnic origin, political opinion, religion, sex life, and trade-union membership. Processing requires a specific exception (e.g. explicit consent under s. 30(2)(a)).
Response time: one (1) month from receipt of a data-subject request (s. 34(2)) .
Cross-border transfers (s. 41): permitted on the basis of NDPC adequacy recognition, or under specific safeguards including binding corporate rules, contractual clauses, or the data subject’s explicit consent.
Penalties (s. 53): for a data controller of major importance, the higher of ₦10 million (or 2% of annual gross revenue) per violation; for other data controllers, administrative fines as determined by the NDPC under its published Penalty Framework, taking into account the nature, scale, and severity of the non-compliance.
18.2Ghana
Statute: (GH · Data Protection Act 2012 (Act 843)).
Regulator: Data Protection Commission (DPC).
Lawful bases (s. 20): consent or otherwise authorised by law. The Act adopts a consent-centred default and requires careful documentation of any non-consent basis.
Sensitive categories (s. 35): include health, criminal-offence data, religious or philosophical beliefs, and trade-union membership. Biometric data is implicitly protected as part of identification data; counsel must verify the explicit categorisation under DPC regulations.
Response time: 40 days from receipt of an access request (s. 35(2)) .
Cross-border transfers (s. 47): permitted to a country with an adequate level of protection, or with DPC authorisation.
Registration: data controllers in Ghana are required to register with the DPC under (GH · Act 843, s. 46).
18.3Kenya
Statute: (KE · Data Protection Act 2019 (Act No. 24 of 2019)).
Regulator: Office of the Data Protection Commissioner (ODPC).
Lawful bases (s. 30): consent, contract, legal obligation, vital interests, public interest, legitimate interests, performance of a task carried out in the public interest, or for historical, statistical, or research purposes.
Sensitive categories (s. 44): include biometric data (s. 44(1)(g)), genetic data, health data, ethnic origin, religious belief, sexual orientation, and trade-union membership.
Response time: 7 days from receipt of a data-subject request (s. 26(2)).
Cross-border transfers (ss. 48-49): permitted where appropriate safeguards are in place, including standard contractual clauses approved by the ODPC, or with the data subject’s explicit consent.
Breach notification: within 72 hours of becoming aware of a breach (s. 43).
Registration: certain data controllers and processors are required to register with the ODPC under s. 18 (KE · DPA 2019, s. 18) and the Data Protection (Registration of Data Controllers and Data Processors) Regulations 2021.
18.4South Africa
Statute: (ZA · Protection of Personal Information Act 2013 (POPIA, Act 4 of 2013)).
Regulator: Information Regulator (South Africa).
Eight conditions for lawful processing (Chapter 3, Sections 8-25): (1) accountability, (2) processing limitation, (3) purpose specification, (4) further processing limitation, (5) information quality, (6) openness, (7) security safeguards, (8) data subject participation.
Special personal information (Chapter 3, Part B, ss. 26-33): includes biometric information (s. 26), religious or philosophical beliefs, race or ethnic origin, trade-union membership, political persuasion, health or sex life, criminal behaviour, and children’s personal information. Processing is prohibited unless an exception applies (e.g. explicit consent, s. 27).
Response time: as set out in the Promotion of Access to Information Act framework (Form 2); POPIA itself requires a “reasonable time” (s. 23).
Cross-border transfers (s. 72): permitted where the recipient is subject to a law, BCRs, or binding agreement that provides an adequate level of protection, or with the data subject’s consent, or where the transfer is necessary for the conclusion or performance of a contract.
Information Officer: POPIA s. 55 requires the appointment of an Information Officer; the head of a private body is the default Information Officer unless another person is designated and registered with the Information Regulator.
Penalties (s. 107): administrative fines up to R10 million, plus criminal sanctions for serious offences.
18.5Rwanda
Statute: (RW · Law N° 058/2021 of 13/10/2021 relating to the protection of personal data and privacy).
Regulator: the supervisory authority designated under the Law. At present the National Cyber Security Authority (NCSA) discharges supervisory functions in the absence of a separately designated authority .
Lawful bases (art. 7): consent, contract, legal obligation, vital interests, public interest, legitimate interests.
Sensitive categories (art. 5): include biometric data (art. 5(2)), genetic data, health data, racial or ethnic origin, religious belief, political opinion, and sexual orientation.
Response time: 30 days from receipt of a data-subject request .
Cross-border transfers (arts. 48-49): permitted to a country with an adequate level of protection or under specific safeguards approved by the supervisory authority.
18.6Field-agent privacy notice
This sub-section is the privacy notice referenced from the field-agent enrollment flow (the screen on which a prospective polling-unit agent is asked for a phone number, a one-time passcode, and a selfie photograph).
What we collect:
- your phone number, used to send and verify a one-time passcode (OTP);
- the OTP itself, retained transiently for verification and then discarded;
- a selfie photograph, processed as biometric data, used to confirm at the polling unit on election day that the operator on duty is the agent the Customer enrolled;
- a device fingerprint (browser type, screen resolution, timezone) and your IP address at the time of enrollment, used for fraud detection;
- (once on shift) your GPS coordinates, used for geofence verification and audit.
Who is the controller: the Customer running the relevant Project (typically a political party, candidate organisation, or research firm) is the data controller for this data. VoteEdge processes it on the Customer’s instructions as a data processor. The Customer is required to provide their own privacy notice covering this processing; this notice is supplementary.
What we do with it: identity verification, on-the-day check-in, payment of any fees, supervisor messaging, audit, and integrity of the result-transmission chain. We do not use this data for marketing, profiling, advertising, or any non-electoral purpose.
Lawful basis: your explicit consent (under the named statute applicable to your jurisdiction in the table at clause 4 above) plus, for non-biometric data, the performance of the contract between you and the Customer.
How long we keep it: phone, IP, device fingerprint, and audit metadata are kept for the jurisdiction-specific minimum retention floor stated in clause 10. The selfie is encrypted at rest and deleted at the end of the project’s retention window unless the Customer requests earlier deletion. The OTP is retained transiently and then discarded.
Who can see it: the Customer’s supervisors and authorised reviewers; the VoteEdge engineering team for the limited purpose of operating the platform; sub-processors as listed in clause 8 + DPA Annex A; and competent regulators or courts, only in response to a binding legal request.
Your rights: the rights set out in clause 11 apply, exercisable through the Customer (your controller) in the first instance. You may also reach VoteEdge directly at hello@voteedgeng.com and we will route your request to the relevant Customer.
Withdrawal of consent: you may withdraw your consent at any time. Withdrawal does not affect lawfulness of processing carried out before the withdrawal. Withdrawal may end your ability to act as an agent on the Project, because identity verification is a condition of the role.
Complaint: you may lodge a complaint with the regulator named for your country in clause 13.