Cookie Policy
Last updated: September 11, 2026 · Version 2026-09-11
The short version. We set no advertising cookies, no analytics cookies, and no cross-site tracking of any kind. There is no Google Analytics, no Meta pixel, no advertising network, and no session-recording tool on this site. Browser storage holds sign-in state, a cached public feature configuration and, if one exists, your analytics preference. These records are described below. They do not authorize advertising or tracking.
This policy explains what the Power website (power-extension.com) stores in your browser and why. It forms part of our Terms of Use and Privacy Policy. We are Azamat Smailov, a sole proprietor carrying on business as GENZAI (Ontario Business Identification Number 1001692014), 113 Kingslake Rd, North York, Ontario M2J 3E9, Canada · +1 437 258 2280 · privacy@power-extension.com.
1. What we actually store
| What | Where | Set by | Why | How long |
|---|---|---|---|---|
Your sign-in session (an access token and a refresh token, under a key beginning sb-) | Local storage, not a cookie | Supabase, our authentication provider | So you stay signed in between page loads instead of entering a one-time code on every screen | Until you sign out or clear your browser storage; the access token itself expires within an hour and is renewed |
Public feature configuration (pwx.pixels.v1) | Local storage | Power | Cache the public configuration used to decide whether an optional choice is available; it is not a visitor identifier | Replaced when refreshed, or removed when you clear site storage |
Optional analytics preference (pwx.consent.analytics.v2; older versioned records may remain) | Local storage | Power | Remember a granted/denied choice if you have made one; a historical generic choice is not reused to authorize a newly introduced tracking purpose | Until replaced or you clear site storage |
The public configuration can be cached before sign-in. Signing out clears authentication; it does not necessarily remove the separate configuration and preference records.
Local storage is not a cookie. It is a separate browser store, it is never attached to network requests automatically, and normal website scripts from a different origin cannot read it. Software with access to your browser profile or authorized browser capabilities may have broader access. We mention it here because what matters to you is what is kept on your device, not the technical name for it.
2. What we do not do
- No advertising or marketing cookies. We run no ad network and no retargeting.
- No analytics or measurement cookies. There is no Google Analytics, Plausible, PostHog, Hotjar, Clarity, Mixpanel, Segment, or equivalent on this site.
- No social media pixels or share-button trackers.
- No session recording, heatmaps, or fingerprinting scripts.
- No selling or sharing of browsing behaviour. We have none to sell.
3. Sign-up information, which is not a cookie
The current wait-list form sends the product, source page path without query parameters and browser language with your sign-up. It does not use cookies to follow you around the site, and it does not add a referring URL, campaign tags, screen size, time zone, full user-agent string or a location lookup to the current sign-up record. Network services still receive the information needed to deliver and secure their requests.
Earlier sign-ups may retain additional context such as campaign tags or approximate region. Those existing records are covered by §2 and §7 of the Privacy Policy, along with your access, correction and deletion options. Updating this site does not erase them.
4. Third parties that see a request when you load a page
Loading a page contacts the services that deliver its content or account functions. Website product videos and posters are served as ordinary media files from our site, without an embedded YouTube, Instagram or TikTok player. Playing them does not enable analytics. The following providers can receive requests:
| Who | What they receive | Why |
|---|---|---|
| Vercel (our host) | Standard web-server request data, including your IP address, requested file/path and browser details, for delivery and security logs | Hosting |
Google Fonts (fonts.googleapis.com, fonts.gstatic.com) | Your IP address and browser details, because your browser fetches the font files directly from Google | The site's typeface. Google states it does not use these requests to build advertising profiles, but the request does reach Google, so we name it rather than leave it out |
| Supabase | Network/browser request data when an account function or public configuration is requested; your email and sign-in tokens when you sign in | Authentication, account functions and any public configuration request |
If you would rather Google never saw the request, a content blocker or a browser that blocks third-party font requests will stop it; the site remains fully usable with a fallback typeface.
5. Why there is no cookie banner
Canadian privacy law (PIPEDA) requires meaningful consent for collecting personal information, and consent can be implied where the purpose is obvious and the information is not sensitive — such as keeping you signed in on a site you deliberately signed in to. It does not impose a blanket "accept cookies" pop-up for storage that is strictly necessary to provide what you asked for.
Advertising and analytics tags are disabled in this release, including when a cached public configuration contains a provider identifier. An old preference cannot activate a new tracking purpose. Before optional tracking is introduced, we will identify its providers and purposes, update this policy and ask for a fresh choice, off by default. You can browse the public site without accepting optional tracking. The absence of a cookie banner does not remove the privacy choices required for other data collection.
6. Controlling what is stored
You can clear local storage and cookies for this site at any time in your browser settings (usually under "Privacy", "Site settings", or "Clear browsing data"). Clearing it signs you out and removes cached configuration and preferences for this site. Extension data is stored separately; do not clear extension storage unless you intend to remove its local work.
Blocking storage entirely will prevent you from staying signed in, but browsing the public pages will still work.
7. The extension is covered elsewhere
This policy is about the website. The Power browser extension separately stores personal-app source, versions/data, drafts, recovery/support records, page placements, optional encrypted vault records, chats, task logs and settings. Approved AI/browser actions can disclose relevant information to external services. That is a different set of facts with different consequences, and it is described in §2a of the Privacy Policy — please read that section before installing.
8. Changes and contact
We will post any change here with a new date and version. Questions, or a request to delete what we hold about you: privacy@power-extension.com, or write to Azamat Smailov, sole proprietor carrying on business as GENZAI (Ontario BIN 1001692014), 113 Kingslake Rd, North York, Ontario M2J 3E9, Canada.
If you are not satisfied with our answer, you may complain to the Office of the Privacy Commissioner of Canada (priv.gc.ca · 1-800-282-1376).