Last updated: 25 October 2026. This Cookie & Browser Storage Policy describes cookies and similar technologies used by PIQSA. Cookies are only one type of browser storage; authentication may also use local storage or session storage. Exact technologies can change as features and providers are updated, so this notice must remain aligned with the live production configuration. Essential sign-in and security storage may be needed for account features. Optional analytics, embedded content or advertising technologies must be disclosed based on what is actually deployed and the choices required by applicable law.
Cookie Policy
Cookie Policy. Dedicated PIQSA page definition and reusable interface template.
This section is a UI scaffold. Real records and write actions require tested backend integration before being described as operational.
Get ready for the next step
Browse the other planning sections or prepare your questions for the Prep IQ team.
Last updated: 25 October 2026. This Cookie & Browser Storage Policy describes cookies and similar technologies used by PIQSA. Cookies are only one type of browser storage; authentication may also use local storage or session storage. Exact technologies can change as features and providers are updated, so this notice must remain aligned with the live production configuration. Essential sign-in and security storage may be needed for account features. Optional analytics, embedded content or advertising technologies must be disclosed based on what is actually deployed and the choices required by applicable law.
Step 1
1. Essential cookies and session storage
PIQSA may use essential browser storage to maintain sign-in, protect a session, remember necessary preferences and support basic reliability. The Supabase authentication client used by this app can persist a login session in browser storage. Disabling such storage may prevent sign-in, saved profiles, applications or private document workflows from functioning. Do not use a shared computer for private account work; sign out and close the browser when finished. The lifetime of a storage item can depend on session state, provider settings, browser behaviour and user action, so this policy does not invent a universal lifetime for every item.
Use sign-out on shared devices.
Keep your browser and operating system updated.
Clear site data if you need to end a locally persisted session, then sign in again if necessary.
Step 2
2. Analytics and third-party features
If analytics, embedded media, maps, chat, payment or other third-party features are enabled, those providers may process technical identifiers or use their own storage under their policies. PIQSA should name the provider and purpose where required; optional tracking must not be described as essential merely because it is convenient. Technologies should be activated only in a way consistent with applicable privacy and consent requirements. When a provider or tracker is added, materially changed or removed, this notice and any related preference interface should be updated to match production behaviour.
Review a third-party provider's notice before using its embedded service.
Where a site-level choice is presented, the underlying implementation should respect that choice.
A link does not make PIQSA the operator of an external website.
Step 3
3. Your choices
You can manage or delete cookies and browser storage through your browser's privacy settings. Blocking all storage may disable authentication or preferences. Browser-level controls are different from a site-level consent mechanism; where law requires site-level choice, browser settings alone may not substitute for it. The site must not promise a preference centre or opt-out control unless it is implemented and tested. If a banner is shown, it should explain the available choices and permit changes or withdrawal where applicable. For questions, contact info@prepiqedu.in with “Cookie / Storage Question — PIQSA”; never paste session tokens or authentication cookies into a support request.
Use browser settings to inspect, block or clear storage.
Report a consent control that appears not to work.
Recheck this notice after authentication or tracking changes.
Step 4
4. Third-party storage and future changes
Authentication, fonts, embedded media, payment or support functions can connect to providers that receive technical request data or use their own storage. PIQSA should identify provider and purpose where required and should not imply all third-party activity is controlled by browser settings on this domain. Before adding analytics, advertising pixels, session replay or new embeds, the product owner should assess purpose, data flows, retention, consent requirements and the effect on minors; revise the notice and controls before activation where required. The live implementation, not a planned feature list, determines what this notice should disclose.
Review the notice for embedded services you use.
Report unexpected tracking or consent behaviour.
Re-audit after a material deployment or vendor change.
Step 5
5. Support and safe troubleshooting
For questions about storage or preferences, email info@prepiqedu.in with “Cookie / Storage Question — PIQSA”. Include the affected page and browser where known, but never paste session tokens, authentication cookies or the full contents of local storage into support. If a consent-choice interface exists, use it to change or withdraw choices and report any failure. You may clear site data through browser settings, knowing this can sign you out and remove local preferences. Keep this notice consistent with the actual authentication and tracking configuration.
Never share session tokens in a screenshot or support message.
Clear site data if you believe a local session should end.
Report a preference choice that does not persist.
Review requirement: Keep this notice aligned with an actual browser/storage/network audit before adding analytics, ad pixels, session replay, chat embeds or other third-party scripts.
Frequently asked questions
Are cookies and local storage the same?
No. Cookies may be sent with web requests, whereas local/session storage is managed separately by the browser. Both can store information but work differently.
Can I block all storage and keep using the student portal?
Not necessarily. Essential authentication storage may be required for a secure session. Public pages may still be available, but account features can stop working.
Can I paste a cookie or session token into a support request?
No. Tokens may allow account access. Describe the issue and affected page instead, and do not share passwords or OTPs.
Does the policy prove an optional cookie banner is implemented?
No. Disclosures and controls must match actual production behaviour; a visible banner alone does not prove consent is handled correctly.
