This notice describes the Why Not PO? movement platform. The operating organisation’s legal identity and contact details must be supplied before production registration opens.
What the platform collects
Accounts use your name, email address, an encrypted password hash, verification records, and security sessions. Volunteer applications include selected roles, skills, availability, and your submitted country and location. The platform does not request precise GPS coordinates, voter-card details, ethnicity, or religion.
Optional profile and recognition
Registration may include a phone number, country, state, local government, region, city and volunteer interests. These fields are optional and private. Providing a phone number does not verify it or subscribe you to communications. Account preferences separately control public attribution and leaderboard participation.
Public rankings show only your chosen public name, points and badges. Learning attempts and contribution reviews remain private. Hosted share cards stop working when you opt out, change your public name, or are suspended. Downloaded images and third-party copies cannot be recalled. Account export includes these records; deletion requests clear optional profile preferences, learning attempts and hosted cards while organisers review remaining records.
A language cookie remembers your interface choice. Browser storage records whether the Telegram invitation has been shown or dismissed. No Telegram content is loaded until you follow its link; clicking does not establish membership.
Why it is used
Your information supports membership verification, volunteer application review, chapter coordination, reference moderation, event reservations, contribution receipts, and account security. The platform does not build behavioural political targeting profiles.
Who can see it
Authorised organisers can review membership applications. Chapter coordinators can access assigned chapter volunteers. Finance staff can access donor and payment records. Public transparency reports omit donor identities and private payee details. Published volunteer references are moderated before release.
Content-writing drafts, editor notes, and revision history remain restricted to the contributor and authorised editors. A published article displays its contributor byline, article text, category, tags, and publication date publicly.
Forum posts and comments under published articles display your chosen public handle, submitted text, dates, edit status, and moderation placeholders. Your email, legal name, location, and WNPO registration ID remain private. Moderators retain revisions, flags, and action reasons for accountability, and your account export includes your authored discussion content.
Election reporting
Assigned field reporters can submit polling-unit counts, observations, and result-sheet evidence. Reporter identities, assignments, original documents, and review notes remain private. Public pages show independently reviewed results and separately redacted evidence. The platform does not collect voter identities, individual voting preferences, or live reporter coordinates.
Optional device drafts include pending attachments in browser storage, are bound to the reporting account, and are cleared on logout. A valid session for that account is checked before submission. Published corrections retain source history; account deletion requests are reviewed alongside the need to preserve election evidence and audit records.
WhatsApp is optional
A separate opt-in is required before receiving an invitation. Your phone number may be visible within WhatsApp according to its community settings. Leaving this website does not automatically leave the WhatsApp community; you can leave directly or request manual removal.
Service providers
Ask search runs on this platform. When enabled, local models match questions to public posts and prepare stored explanations of those posts. Ordinary searches do not send questions to an external model provider. Search URLs can be shared and may remain in browser history and ordinary server access logs. Explanations of public posts are stored separately from private assistant conversations.
The platform uses a hosting provider, transactional email delivery, Paystack hosted payments, private object storage, and OpenAI for the optional Ask the Record assistant. Card details are entered on Paystack, not stored by this website. Only when using the optional generated-answer tool, assistant questions and retrieved public sources are sent to OpenAI with provider storage disabled. OpenAI may retain API content temporarily for abuse monitoring under its data controls. These providers may process data in other countries; production operators must document their providers and applicable arrangements.
Suggestions and assistant sessions
Suggestions are private. Providing a name or email is optional, and contact permission is required when an email is supplied. Optional contact details are removed twelve months after a suggestion is closed. Assistant conversation history stays in your browser session and short-lived server memory for up to twenty minutes. The database stores only model, token, duration, result status, and timestamp records, without questions or generated answers.
Account notifications
Signed-in members receive private in-app notifications for published work, movement or chapter updates, forum replies, and decisions about their own contributions. Notification preferences and read status are stored with the account. Notifications are not sent by email, SMS, or push messaging. Expired notifications are removed after 180 days, and account exports and deletion requests include this information.
Retention and your choices
You can export your account information and request deletion from the member portal. Volunteer and account information should be deleted or anonymised when no longer needed. Financial records required by applicable obligations are handled separately. Organisers must document their retention schedule before collecting production registrations.
Cookies and security
Essential cookies maintain sign-in and account security. A local preference remembers your reading theme and selected comparison post IDs. If you choose an offline research pack, your browser stores the selected public archive pages on this device. Account, administration, API, and payment-receipt pages are excluded from offline storage. No advertising cookies or third-party tracking pixels are installed. Privileged accounts require two-factor authentication.