We use first-party analytics to understand our website’s reach, campaign performance and the steps towards expressing interest. The website works whether or not you accept optional analytics.
Anonymous timestamped counts
Without optional analytics consent, we count approved page loads and actions with a server timestamp, event category, approved page or media name, and broad source and campaign labels. These events have no browser or session identifier. A random event receipt prevents a retry from counting twice; it does not identify a browser across events. Repeat visits and refreshes can count again.
PDF opens and downloads refer to website link clicks, not proof of saving or reading. Music starts, player-ended events, share-menu openings and form starts are separate signals. Direct PDF links shared outside website pages are not measured by the browser tracker.
Optional session analytics
If you accept optional analytics, first-party local storage holds random browser and session identifiers. Sessions are shared across tabs and renew after 30 minutes of inactivity. Permission and the browser identifier expire after 180 days. The server stores hashes of identifiers, session start and last activity times, approved page/action history, and broad attribution labels.
This lets us estimate unique and returning browsers and measure a consented journey from viewing the interest form to starting it and receiving a server-confirmed submission. Analytics does not store names, email addresses, phone numbers, employer or branch answers, comments, membership declarations, or submission reference numbers. Interest-form records remain separate.
Form progress tracks only broad stages such as contact, employment and declaration. Errors use broad categories such as validation or network failure, without field values or error-message text. Article time and scroll milestones require consent and are not proof of reading.
Because this upgrade connects approved activity into sessions, previous optional permission is not silently reused. Existing visitors are asked to make a fresh choice.
Campaign attribution
We use broad referral categories and approved campaign query parameters: utm_source, utm_medium, utm_campaign and utm_content. Campaign/message labels must be short letters, numbers, underscores or hyphens. Full referring URLs and arbitrary query strings are not stored. These labels should identify a channel or campaign batch, never a person. Attribution persists between pages only after consent and retains the session’s initial source. Otherwise, a later page may be unattributed.
Your choices and exclusion
The “Privacy settings” button lets you accept, decline, withdraw or exclude this browser entirely. Declining leaves anonymous counts enabled. Withdrawing requests deletion of matching browser-linked detailed events and session records; anonymous aggregate counters cannot identify an individual contribution. If a network blocks deletion, contact us. Retention limits still apply.
The exclusion preference uses local storage and a first-party cookie lasting up to one year. Apply it on each browser and hostname you use. Recognised signed-in owner visits, Do Not Track and Global Privacy Control are excluded. Known automated browsers are filtered, but no count is a perfect census.
Retention and access
Detailed timestamped events and upgraded sessions are retained for up to 90 days. Historical daily aggregate totals and older optional daily-presence records are retained for up to 180 days. Pruning occurs on later analytics requests. Reports display Nigerian time (WAT, UTC+1); event timestamps are stored in UTC. Earlier daily-only records cannot be converted into exact hourly history.
Only the authorised site owner can access analytics reports and aggregate exports. Unique browsers are not unique people; clearing storage or changing devices may create another browser. Consent coverage is displayed so optional session metrics are not mistaken for all visitors.
What we do not collect
No raw IP addresses, fingerprints, precise location, full referring URLs or personal form fields are saved in analytics. We use no third-party analytics service. The hosting provider may process operational logs separately to deliver and secure the website.
Questions or privacy requests: info@save-union.org.