Cookie Policy
Browser storage, essential account operations and an unconfirmed tracking inventory.
- Document version
- 0.2
- Prepared
- 31 October 2026
- Effective date
- [To be confirmed]
Draft document, not yet effective
Not approved, not effective and not evidence of regulatory compliance. Reading these pages does not constitute acceptance.
Questions about these terms: support@panovaax.com
1. Operator and document status
This preliminary document is prepared for PanovaaX Technologies Ltd, the proposed operator of PanovaaX. It is a first draft for founder and Nigerian legal counsel review, not an approved policy or a representation of regulatory compliance. It does not take effect merely because it is displayed or read.
PanovaaX connects organisations, their people and participating merchants and service providers through lifestyle benefits, everyday services and experiences. The features and contractual responsibilities described here must be checked against the services actually offered at launch.
Confirmation required before operative publication
Confirm the exact registered contracting entity, CAC number, registered and service addresses, legal contact, effective date and authorised signatory. No binding effective date has been set.
2. Scope and terminology
This draft covers cookies and related technologies used in the website and platform, including browser local storage, session storage and comparable identifiers. Not all browser storage is a cookie, but technologies serving similar purposes need an appropriate transparency and consent assessment.
The policy must be based on a production inventory. It must not state that PanovaaX uses no cookies, no tracking or only essential technologies without checking the hosting layer and third-party providers.
Confirmation required before operative publication
Confirm the live technology inventory, provider names, storage keys, purposes, recipients and actual durations.
3. Essential account and security storage
The current platform uses browser-held authentication/session information and account continuity features. Theme preference and related interface settings may also use local storage. Whether a particular technology is strictly necessary must be assessed for its actual purpose, not assumed because it is convenient.
Session and security information should not be repurposed for marketing without a separate lawful assessment. A browser setting may affect account continuity or sign-in, but this does not justify conditioning access on unrelated tracking consent.
Confirmation required before operative publication
List each account, security and preference technology, lifespan, responsible provider and lawful basis. Verify Remember me and sign-out/closure behaviour.
4. Website traffic and other providers
Public traffic reporting is designed to record allowlisted page views and clicks without personal identifiers or form values. Signup totals are calculated separately. This purpose-limited approach does not establish that hosting or other providers collect no technical information.
External services, fonts, media or other integrations may receive technical request information. There is no verified advertising or non-essential tracking inventory in this draft. New measurement, profiling or advertising technologies need review before deployment.
Confirmation required before operative publication
Audit network requests, cookies and storage on public, signed-in and payment pages. Classify any non-essential tools and disclose their providers and purposes.
5. Consent and choices
Where consent is required under applicable Nigerian data protection law and guidance, obtain it before activating the relevant non-essential technology. Choices should be understandable, specific and genuinely optional, with withdrawal as accessible as giving consent. Silence or simply reading this policy is not consent.
Browser settings may allow removal or blocking of storage, and should be distinguished from the platform's own consent controls. Clearing essential session storage may require signing in again. Do not promise a preference centre or cookie banner that is not yet implemented.
Confirmation required before operative publication
Confirm whether a consent interface is required after the inventory, implement prior blocking where needed, document consent and withdrawal, and verify that refusal does not enable optional tools.
6. Duration, disclosure and review
Technology duration must be disclosed from verified configuration and actual behaviour, including renewal or session expiry where relevant. No cookie lifetime is invented here. The inventory should be revisited when providers or platform functionality change.
Personal information associated with these tools is also subject to the Privacy Policy and applicable rights. Requests and complaints need a verified privacy contact; no placeholder should become the operative contact.
Confirmation required before operative publication
Approve storage durations, review ownership, privacy contact and the final inventory before publication.
7. Changes, effective date and acceptance
This draft is version 0.2, updated on 31 October 2026 with confirmed contact channels and current platform safeguards. Its effective date is not confirmed. Approved terms should identify the applicable version, explain material changes and use reasonable notice and explicit acceptance where the law or relationship requires it.
Visiting a page, viewing a preview or remaining silent does not create a recorded acceptance under this draft. Existing business contracts and mandatory law are not replaced by these preliminary pages.
Confirmation required before operative publication
Before activation, approve an acceptance mechanism, delivery of a retainable copy, change notices and treatment of participants who do not accept revised terms.