Cookie Policy
Cookies and similar technologies used by Ihsan Power.
1. Overview
This Cookie Policy describes the cookies and similar technologies actually used by the Ihsan Power web application. Cookie Policy Version: 1.0. Effective Date: 24 August 2026.
We do not currently embed Google Analytics, Google Tag Manager, Firebase Analytics, Meta Pixel, Microsoft Clarity, or advertising SDKs in the Ihsan Power web app. Optional analytics and marketing categories exist so preferences are ready if those technologies are introduced later — they will not load without consent.
2. Strictly necessary
These are required for security and core operation and do not depend on optional consent.
| Name | Purpose | Duration |
|---|---|---|
.IhsanPower.Session |
Session management and signed-in state (stores auth tokens server-side in session). | Up to 2 hours idle |
.AspNetCore.Antiforgery.* |
CSRF protection for forms. | Session |
.IhsanPower.CookieConsent |
Stores cookie category preferences (version + flags only; no personal profile data). | 12 months |
.IhsanPower.ConsentId |
Privacy-preserving anonymous consent identifier for recording preferences. | 12 months |
3. Functional
- localStorage key
ihsanpower-sidebar-sections— remembers sidebar section open/closed state. Used only when Functional consent is granted. - Google Fonts — optional UI font loading from Google. Loaded only when Functional consent is granted; otherwise system fonts are used.
- Chart.js / Leaflet (CDN) — loaded on specific authenticated feature pages (analytics charts, outage map) for product functionality. Treated as functional enhancements.
- PWA service worker cache — caches static assets for performance/offline shell; operational, not advertising.
4. Analytics
No first-party or third-party analytics tracking SDK is currently active in the web application. If analytics are enabled in future, they will appear in this category and will require Analytics consent before initialization.
5. Marketing
No advertising, remarketing or marketing pixels are currently embedded in the web application. Optional marketing email/SMS consent is managed separately under Account → Privacy and is not bundled into cookie “Accept all”.
6. Payment provider domains
Checkout may redirect you to payment providers (for example Flutterwave, Paystack or Nomba). Those providers may set their own cookies on their domains. That processing is governed by their policies.
7. Managing preferences
On first visit (or after a material consent-version change) you can:
- Accept All — enable optional Functional, Analytics and Marketing categories (where configured).
- Reject Optional — keep Strictly Necessary only.
- Manage Preferences — choose categories individually.
Re-open settings anytime via Cookie Settings in the footer, or Account → Privacy.