Food & Beverage
Beauty & Fragrances
Office & Stationery
Consumer Electronics and Home Appliances
Fashion & Accessories
Vehicles
Property
Business, Industrial & Agriculture Essentials
Services
Animals
Cookie & Personalization Notice
This notice explains how Ap Ki Shop uses cookies, local storage, session storage, pixels, tags and similar technologies across the marketplace, seller tools, checkout flows, public pages and recommendation features. It also explains, at a practical level, how on-site personalization and product discovery features use session, consent and interaction signals to improve relevance, ranking context and user experience.
This is the operative public Cookie & Personalization Notice for Ap Ki Shop unless and until a later version is published.
21, Street, Bheem Street, 1st Floor, Nila Gumbund, Lahore, Pakistan.
This notice applies to Home Users, Commercial Sellers, buyers, visitors and anyone using the Ap Ki Shop website, tools or recommendation features.
This notice sits alongside the Privacy Policy and Terms Of Service and focuses specifically on device-side technologies and personalization controls.
Necessary Technologies
Some technologies are needed for core functions such as login continuity, security, request integrity, session handling, checkout continuity and remembering whether a consent preference has already been recorded.
Personalization Controls
Ap Ki Shop currently stores a personalization preference and related recommendation identifiers in browser storage so recommendation features can respect user choice and operate more consistently.
Measurement And Marketing
The current codebase also includes third-party analytics and marketing integrations, including Google tag and Meta Pixel style tracking, which should be understood as separate from first-party recommendation storage.
User Choice
Users can accept or reject on-site personalization through the platform banner, and can also use browser controls to clear or block cookies, local storage and similar technologies.
Why This Notice Matters
Ap Ki Shop is not a static brochure site. It is a multi-vendor digital marketplace that relies on identity, session, trust, discovery and recommendation signals to function properly. That means a proper cookie notice must explain not only generic browser cookies, but also the first-party identifiers, consent state, session-level memory and ranking context that the current platform actually uses.
What This Notice Covers
This notice focuses on technologies that store information on your device or access information from your device, and on the way Ap Ki Shop uses those signals to support navigation, security, measurement and optional relevance features.
Cookies and similar technologies
For this notice, Cookie Technologies includes browser cookies, local storage, session storage, tracking pixels, similar identifiers, and comparable tools that store or read information on your browser or device.
Marketplace-wide scope
This notice applies to the main marketplace, public pages, recommendation widgets, seller tools, listing pages, category and search pages, checkout flows and associated platform features.
Personalization explained
On Ap Ki Shop, personalization means using certain session, browsing, interaction, affinity, category or broad location-context signals to help make product discovery and ranking more relevant for a user or browsing session.
Relationship to the Privacy Policy
This notice is narrower than the Privacy Policy. The Privacy Policy covers personal data more broadly, while this page focuses on device-side technologies, recommendation memory and user choice around optional tracking and personalization.
Categories Of Cookie Technologies Used On Ap Ki Shop
Different technologies do different jobs. Some are genuinely required for core site operation, while others support measurement, content relevance, advertising or convenience.
Strictly necessary technologies
These are used for core site operation, request integrity, login continuity, shopping and checkout continuity, basic security, and remembering already-recorded consent choices. Without these, important parts of the marketplace may not function safely or correctly.
Functional and personalization technologies
These help the platform remember relevant preferences, session-level browsing context, recently viewed content, category affinity and optional recommendation state so users can receive a more coherent product-discovery experience.
Measurement and analytics technologies
These help Ap Ki Shop and its providers understand traffic, engagement, performance, demand patterns, page behaviour, recommendation quality and other operational metrics that support platform improvement.
Advertising and marketing technologies
These can be used to attribute campaign performance, understand whether a visit or registration followed a promotion, measure conversions, or support more relevant off-site or cross-platform marketing activity where such use is enabled.
Current First-Party Technologies Identified In The Codebase
The following identifiers or storage entries are currently visible in the platform code and form part of the first-party cookie and personalization layer operated by Ap Ki Shop.
apk_consent_personalization
This value is stored in browser local storage to remember whether the user has granted, denied or not yet made a personalization choice. It supports the on-site consent banner and related recommendation behaviour.
apk_consent_token
This local-storage value is used in the recommendation event flow as a validation token associated with a recorded consent state. Under the current settings, token validation is configured with a server-side maximum age of about 1 hour.
apk_anon_id
This first-party anonymous identifier is stored both as a cookie and in local storage to help connect personalization consent and recommendation events for users who are not signed in. The current cookie version is set for about 365 days.
apk_session_id
This value is stored in browser session storage and is used by the client-side recommendation tracker as a current-session identifier. It generally lasts only for the relevant session or tab lifetime.
apk_recs_sid
This first-party cookie supports session-level recommendation context used by the session-personalization layer. Under current settings, its lifetime is about 6 hours.
blog_vid
This first-party blog visitor cookie is used for view uniqueness and related blog analytics or view counting logic. The current cookie lifetime is about 365 days.
Authentication and security cookies
Platform operation also relies on session and security cookies such as the user session cookie and CSRF/request-protection cookie. These support sign-in continuity, authenticated actions and form/request integrity across the marketplace.
Session and checkout continuity
Core Django session infrastructure and related browser state are used for actions such as basket continuity, view state, request flow and account operation. Under the current settings, the main session cookie age is configured at about 2 weeks, subject to browser and session behaviour.
Third-Party Technologies Currently Visible In The Templates
The current codebase also contains third-party measurement and marketing integrations. Their exact provider-side cookie names and final durations may vary over time and should be understood together with the relevant third-party notices.
Google tag / analytics integration
The base template includes Google tag loading for analytics and related site measurement. Depending on active provider configuration, that may involve analytics cookies, identifiers or related device-side technologies controlled wholly or partly by Google.
Meta Pixel style marketing tracking
The base template also includes Meta Pixel style tracking, including page-view style marketing events and registration/subscription-style events on parts of the account flow. Depending on active provider configuration, this may involve measurement or marketing identifiers controlled wholly or partly by Meta.
Provider-controlled behaviour
Some third-party technologies do not rely only on Apkishop-named cookies. Providers may use their own cookies, browser identifiers, local storage or request-side signals, and the exact names or durations can change independently of this codebase.
Separate provider notices
Where third-party providers control parts of the relevant technology stack, their own cookie, privacy or advertising notices may also apply. This notice explains Apkishop's use context, but it does not replace those provider-specific documents.
How On-Site Personalization And Recommendation Context Currently Work
Ap Ki Shop uses a mixture of consent state, anonymous identifiers, session-level memory and marketplace signals to support product discovery, ranking context and recommendation behaviour.
Recommendation signals
Ranking and recommendation logic may consider signals such as price, price distance, recency, popularity views, favorites, clicks, rating quality, review volume, category match, user or session affinity, widget context and reason context. These are designed to help shoppers find relevant items faster.
Consent-linked event ingestion
Under the current recommendation implementation, ordinary recommendation events are not ingested unless the personalization consent state is granted. Consent updates themselves may still be recorded so the platform can remember the user's current choice.
Session and cohort context
Even where full personalization is not active, the codebase contains session-level and cohort-level mechanisms that can remember recent listing views, category affinity and broad context such as geo bucket, device bucket and time bucket for discovery and trending logic.
No guaranteed exposure
Personalization and recommendation tools help ordering and discovery, but they do not guarantee any seller a fixed ranking position, fixed traffic level, fixed visibility window or guaranteed sales outcome.
User Choice And Control
Users should be able to understand what choices exist, what happens if those choices are changed, and which platform functions may be affected if certain device-side technologies are blocked or cleared.
Banner choice
Ap Ki Shop currently presents an on-site consent banner for personalization, allowing users to accept or reject personalization. The recorded state is then stored in local storage and synchronised with the recommendation consent endpoint.
Browser and device controls
Users may also manage cookies, local storage and session storage through their browser or device settings. Clearing those technologies may remove remembered preferences, sign-in continuity, session memory and parts of the personalization state.
Withdrawing optional choice
If a user changes an optional personalization choice from granted to denied, future personalization-linked recommendation event collection is intended to stop within that consent-controlled recommendation layer. Some necessary technologies may still operate for security and core service delivery.
Effect of disabling technologies
If necessary technologies are blocked, important features such as account continuity, form security, basket continuity, session consistency or other marketplace features may not function properly or may function less reliably.
Durations, Retention And Related Server-Side Handling
Some technologies are purely browser-side, while others are linked to server-side logs or recommendation records. The following points summarize the main code-backed lifetimes currently visible in the project.
Browser-side durations
The current codebase sets apk_anon_id for about 365 days, apk_recs_sid for about 6 hours, blog_vid for about 365 days, and the platform session cookie age for about 2 weeks. Session storage values such as apk_session_id generally end with the relevant browser session.
Consent token timing
The recommendation consent token currently has a server-side maximum validation age of about 3600 seconds, or about 1 hour, even though the browser-side storage entry may remain present until it is replaced or cleared.
Recommendation event retention
The current recommendation cleanup settings retain recommendation events and related recommendation logs for about 90 days, and retain aggregate recommendation statistics for about 365 days, subject to operational cleanup routines and storage backend behaviour.
Third-party durations may differ
Third-party analytics or marketing providers may apply their own storage periods, expiry windows or identifier refresh rules. Those durations are not always fully visible from source code alone and may change over time depending on provider configuration.
Rights, Contact And Updates
Where Cookie Technologies involve personal data or consent-based decision points, users should have a clear route to contact the platform and understand how this notice may change over time.
Privacy rights
Where applicable law gives users privacy or data-protection rights, requests relating to access, correction, deletion, restriction, objection or consent withdrawal should be made in conjunction with the Privacy Policy and directed to the contact details below.
International processing context
Ap Ki Shop operates from Pakistan and may use infrastructure or service providers in more than one jurisdiction. Technologies described in this notice may therefore be linked to cross-border processing depending on the service being used.
Updates to this notice
We may update this notice from time to time to reflect legal, operational or technical changes, including new integrations, revised durations, updated recommendation controls or changes to platform consent mechanisms.
Contact
Questions about cookies, personalization settings, browser-side identifiers or related privacy matters should be sent to info@apkishop.com.
Need More Context?
This notice explains device-side technologies and on-site personalization at a practical level. For broader personal-data information, please read the Privacy Policy. For platform rights, responsibilities and marketplace rules, please read the Terms Of Service.
Ap Ki Shop continues to evolve. As new cookie technologies, analytics providers, advertising tools or recommendation controls are introduced or retired, this notice should be reviewed and updated to keep it accurate and clear.