Cookies and consent transparency
Cookie Policy
Last updated: May 15, 2026. This page is written in plain English to describe the current static website and future compliance expectations without pretending that inactive services are already live.
Overview
This Cookie Policy explains how My Number Path uses cookies, browser storage and similar technologies. The current website application does not intentionally set non-essential cookies, does not store consent choices and does not load advertising, analytics, retargeting, affiliate, Stripe or email marketing scripts.
What cookies are
Cookies are small text files that a website or service can ask your browser to store. They can be used for essential security, remembering settings, measuring usage, showing ads, tracking referrals or supporting checkout and account features.
What browser storage is
Browser storage includes technologies such as localStorage, sessionStorage and IndexedDB. These can store data in your browser without using traditional cookies. The current My Number Path application does not intentionally use these storage APIs.
Current cookie status
My Number Path currently has no intentional first-party non-essential cookies. The application code does not call document.cookie, localStorage, sessionStorage or IndexedDB. Calculator results are displayed on the page after local browser processing and are not saved by the application.
Why no cookie banner is currently shown
No visible cookie banner is shown because the current site does not intentionally set non-essential cookies or load services that require marketing, advertising or analytics consent. Adding a fake banner would be misleading because there are no active non-essential services for the banner to control.
If analytics, advertising, affiliate tracking, embedded media, Stripe checkout, email marketing or other non-essential services are activated later, a consent mechanism will be added before those services are loaded where required.
Strictly necessary cookies
The My Number Path application does not currently set its own strictly necessary cookies. Hosting or security providers may sometimes set technical cookies or use similar signals to deliver the site, protect against abuse or route traffic. Those provider-level practices are separate from application-level cookies and should be reviewed in the hosting dashboard.
Functional cookies
Functional cookies remember preferences such as language, theme or interface choices. My Number Path does not currently set functional cookies.
Analytics cookies
Analytics cookies measure visits, page views, events and user behavior. Google Analytics and Cloudflare Web Analytics scripts are not currently active in the codebase. Analytics cookies should not be added until the Privacy Policy, Cookie Policy and consent controls are updated.
Advertising cookies
Advertising cookies can personalize or measure ads, limit ad frequency and support ad fraud prevention. AdSense and other ad network scripts are not active now. If ads are added later, consent and disclosure requirements must be reviewed before scripts load.
Affiliate tracking cookies
Affiliate cookies may be set by merchants or affiliate networks after a visitor clicks a monetized link. The current codebase does not intentionally include active affiliate tracking links or affiliate scripts. Any future affiliate usage should be clearly disclosed.
Email marketing cookies
Email providers sometimes use signup forms, tracking pixels, preference cookies or automation tags. My Number Path currently has disabled email placeholder forms only and no live email marketing backend.
Payment-related cookies
Payment processors such as Stripe may use cookies or similar technologies for checkout, fraud prevention and payment security. Stripe checkout is not active now, and Stripe scripts are not loaded by the site.
Embedded content cookies
Embedded videos, maps, social posts, widgets or iframes can set third-party cookies. The current codebase does not intentionally use iframe embeds or external widgets.
Cloudflare-related technical cookies if applicable
If the site is served through Cloudflare, Cloudflare may use technical security or routing mechanisms depending on account settings and threat conditions. The codebase itself does not add Cloudflare Web Analytics or Cloudflare tracking scripts.
Google Search Console note if applicable
Google Search Console verification may be used to prove site ownership and submit sitemaps. Verification by DNS or meta tag does not by itself set visitor cookies. If any Google script-based feature is added later, this policy should be updated.
Future consent management
Before non-essential cookies or tracking scripts are added, My Number Path should implement a consent banner or consent management platform that blocks non-essential services until a valid choice is made where required.
How consent will work when non-essential cookies are added
A future consent tool should clearly separate essential, functional, analytics, advertising and affiliate categories; provide accept and reject options; avoid pre-ticked optional consent; store consent choices only when the banner is active; and allow withdrawal or changes later.
Reject, accept and withdraw consent principles for future use
When a consent mechanism is added, rejecting optional cookies should not block access to core content. Accepting should be affirmative and understandable. Withdrawing should be as easy as giving consent, usually through a persistent cookie settings link.
Browser cookie controls
You can use your browser settings to delete or block cookies. Browser controls may affect features on many sites. Because My Number Path currently does not intentionally set application cookies, there may be no My Number Path application cookies to remove.
Do Not Track / Global Privacy Control
The current site does not run behavioral advertising or sale/share tracking. If future services support Global Privacy Control or similar opt-out signals, the implementation should document how those signals are honored.
Current active cookies/storage table
| Technology | Current status | Purpose |
|---|---|---|
| Application cookies | None intentionally set | Not used by the current application |
| localStorage | Not intentionally used | No application storage |
| sessionStorage | Not intentionally used | No application storage |
| IndexedDB | Not intentionally used | No application storage |
| Hosting/security provider cookies | Possible depending on provider settings | Technical delivery, routing or security if enabled by the provider |
Future cookie table placeholder
If AdSense, analytics, affiliate tracking, email marketing, Stripe checkout or embedded media are activated, this page should add a provider-by-provider cookie table showing cookie names where known, provider, purpose, duration, category and consent status.
Updates
This policy should be updated after any third-party script, cookie, storage mechanism, checkout provider, email service, analytics service, ad network, affiliate network or embedded media service is added.