Votix Privacy Policy
Last updated:
Who we are and what this covers
Votix is an election campaign management platform developed by Black & White Studio, Dhaka, Bangladesh. This policy covers the Android worker app (com.cecms.workerapp), campaign web panel and Votix product website. Contact: info@blacknwhitestudio.com.
The campaign organisation operating your deployment decides which campaign records to collect, who may access them and how long to retain them. Black & White Studio provides the software and may provide hosting or support under that organisation’s agreement. Ask your campaign administrator for the organisation’s identity, hosting arrangements and additional privacy notice.
Information handled by Votix
- Worker accounts: name, email, phone where supplied, credentials, authentication tokens, assigned campaign and wards, roles and permissions.
- Voter and household records: official or campaign-entered names, voter numbers and other identifiers, contact details, addresses, age, gender, profession, household relationships, photos and survey responses where enabled. Records may include religion, political affiliation or assessed support preferences. These can be sensitive personal information.
- Field activity: assessments, visit outcomes, notes, revisit flags, tasks and completion reviews, worker attribution and timestamps, performance counts, and enabled polling-centre or incident reports.
- Messages: notification titles and text, image and voice attachments, recipients, read receipts and device push tokens.
- Technical information: app version, platform, connection and diagnostic information, app interactions and crash reports when telemetry is enabled.
Foreground location and permission choices
The current Android app requires location permission and enabled GPS to enter signed-in screens. Approximate location is accepted; granting precise location allows a more accurate fix. When Home becomes visible or resumes, the app attempts to obtain a current location and sends latitude, longitude, accuracy where available and capture time to the campaign server with the dashboard request. This supports campaign oversight of worker field activity.
The app also attempts to capture your current location when adding a voter, adding a holding, submitting a voter assessment or holding assessment/survey, creating an incident, or changing a task status. These requests include a location object with latitude, longitude, accuracy in metres where available, and the measurement time in UTC. When a new voter includes an inline assessment, the same location metadata is included with that assessment. The coordinates describe the submitting worker’s position, not the voter’s residence or a holding’s permanent address.
Submission capture accepts only fixes measured within the last two minutes. If permission, an enabled provider or a sufficiently recent fix is unavailable, the location object is omitted and the submission continues. This fallback does not remove the separate permission/GPS requirement for entering signed-in screens. Automatic retries reuse the captured metadata; manual retries with the same submission reference may reuse it while held in memory. The capture time identifies when the location was measured.
These field-submission changes implement Android request metadata. Backend validation, storage and processing are separate and depend on the deployed server; sending the metadata does not establish that it is stored or used by that server.
The reviewed app captures location during foreground Home use and these field submissions, and does not request background location permission. You can change permission in Android settings. Denying or revoking location permission, or disabling GPS, blocks signed-in screens until restored; the gate also offers sign out.
Photos, media and notifications
Where voter photos are enabled, you can take a photo through the device camera app or select an image using the system picker. Selected images are uploaded to the campaign server. The app does not need access to your entire photo library for this selection. Only submit photographs and reports you are authorised to collect.
Campaign messages may contain images and voice recordings. The app downloads attachments for display or playback and reports message reads to the campaign server. Downloaded notification media can remain in app-private storage for reuse. Android notification permission controls system notification display; campaign inbox access is separate.
How information is used and accessed
Information is used to authenticate workers, enforce assigned access, maintain campaign records, coordinate field work, deliver messages, record activity and produce operational reports. Authorised campaign administrators and users can access records within their permissions. Authorised report exports create copies outside the app that the campaign must manage.
Hosting and support providers may process information as needed to run and support a deployment. Google Firebase services support push delivery, remote configuration, analytics and crash reporting. Enquiry links to email or WhatsApp send the information you choose to provide through those services. Provider processing may involve servers outside your country; confirm your campaign’s hosting location and provider arrangements with its administrator.
Firebase and website analytics
The Android app integrates Firebase Cloud Messaging, Remote Config, Google Analytics for Firebase and Crashlytics. Push registration sends a device token, platform and app version to the campaign server and uses Firebase to route notifications. Remote Config manages feature availability, maintenance, minimum supported versions and telemetry settings.
Analytics and crash collection are initially disabled in the Android manifest, then controlled by app configuration; the current configuration defaults enable both. App telemetry records screen names and login/logout events and can include SDK-collected app/device identifiers, usage and diagnostic information. The app’s custom telemetry does not attach credentials, voter records or coordinates. This does not mean Firebase collects no device information. See Firebase privacy information and Google’s Privacy Policy.
The Votix product landing page uses Google Analytics to understand visits and page usage, which may use cookies or similar identifiers and browser/device information. These legal and deletion pages do not load that analytics script.
Storage and security
The app stores session credentials and campaign reference information in encrypted local storage using Android Keystore-backed protection. It also stores appearance/language preferences and app-private notification attachments. Android cloud backup and device-transfer backup of app data are disabled. Logout and session-expiry handling clear session data, response caches, notification attachments and the local campaign store; appearance preferences can remain.
The source also contains an encrypted database for voter records and queued entries. Its presence does not establish that offline workflows are enabled in your installed version. Current reviewed field screens require connectivity for submissions. Any enabled local campaign data must be included when handling device cleanup and deletion requests. No security measure guarantees absolute protection; protect your device and report lost access promptly.
Retention and your requests
Campaign server records, activity history, location records, exports and backups follow the campaign operator’s deployment and retention arrangements. No single server retention period is specified by this app source. Ask the operator for the applicable periods and any retention needed for security, audit or legal obligations. Firebase data follows the enabled service settings and provider retention practices.
You can request access, correction, account closure or deletion from the campaign administrator, or email Black & White Studio for help routing the request. See Votix account and data deletion for steps, scope and retention limitations. Signing out or uninstalling does not delete server records. Removing a worker account does not automatically remove campaign-owned voter records or work submitted about other people.
Intended users and policy changes
Votix is intended for authorised campaign staff and polling agents, not as a service directed to children. Operators must establish appropriate authority before collecting information about any person. This policy may be updated when features or data practices change; the date above identifies the latest revision. Contact info@blacknwhitestudio.com with privacy questions.