Cookies Policy
How PriceBag uses browser storage and other technologies that may store or access information on your device.
Last updated: 12 October 2026
About this policy
Cookies are small pieces of information a website may place in a browser. Similar technologies include browser storage and scripts or resources that access information on a device. This policy describes the technologies found in the PriceBag application source; it is not a legal compliance statement. On the same browser origin, a one-time migration also checks a prior pc_* consent or preference key and moves valid data to its pb_* key without expanding the saved consent.
The consent interface offers only the preference-storage category implemented by this application. Analytics, advertising and affiliate tracking are not present in the inspected source.
Shared information and technologies
Necessary sign-in session — Supabase Auth stores session information in browser local storage so customers and retailers can remain signed in. The application does not set a fixed local-storage expiry; authentication session expiry and refresh behavior is controlled by Supabase and the live project settings were not verified. Signing out removes the authentication session.
Necessary consent choice — the app stores the necessary/preference category choice on this device under pb_consent. It contains the policy version, saved and expiry times, and the preference-storage choice. It expires after 180 days; a policy-version change also requires a new choice. This record is local browser storage and is not sent to PriceBag servers by the consent interface.
Optional preference storage — only after you allow this category, the app reads and writes pb_currency (currency), pb_compare (up to three product slugs), and pb_theme (theme) in local storage. These values remain until changed or browser site data is cleared. If you reject or withdraw this category, the app stops reading and writing these keys and attempts to remove them. The theme setting for a signed-in account may also be saved separately to the account profile as part of that account feature.
Password-recovery marker — during password recovery, the app temporarily stores pb_recovery in session storage and removes it after the flow. During the same-origin transition it also recognizes and clears the previous pc_recovery marker. Session storage is limited to the browser tab and is cleared when that tab session ends.
The application source contains no code that reads or writes browser cookies directly. Supabase Auth uses browser local storage. Cookie behavior of the live hosting and service providers has not been independently verified.
Customers
Customers use the sign-in and consent storage described above. If preference storage is allowed, currency, comparison-list and theme choices are saved locally. Saved products, price alerts and retailer-link visits are application records, not cookies. A retailer-link visit records the offer and time; it includes your account ID when signed in and may be recorded without an account ID when signed out. Search history was not found in the inspected application code. See the Privacy Policy for these records.
Retailers and merchants
Retailers use the same Supabase sign-in and consent storage. If preference storage is allowed, currency, comparison-list and theme choices are saved locally. Store profiles, uploaded store images, product listings, prices and availability are submitted to the application and stored through its database or image-storage service; they are not browser cookies. See the Privacy Policy for these records.
Third-party content and external websites
The site requests DM Sans and Manrope font resources from Google Fonts and loads a decorative home-page image from Unsplash. These are external content requests, not confirmed cookies or advertising trackers. Requests disclose connection information such as an IP address; exact provider-side logging, retention and cookie behavior were not verified. Links to provider privacy notices appear below.
Supabase handles authentication, database requests and image storage when configured. The alert-email function sends messages through Resend when deployed and scheduled; whether it is active in the live environment is unverified. These application requests and emails are not browser cookies.
Retailer links open the URL supplied for an offer. No affiliate parameters, affiliate redirect service, or affiliate SDK were found. Retailer websites may use their own technologies after you leave PriceBag.
Analytics, advertising and consent
No analytics or advertising scripts, pixels, SDKs, or affiliate-tracking technology were found in the inspected application source. Preference storage is the only optional browser-storage category currently implemented. The banner offers Accept all, Reject optional and Customize preferences; optional preference storage is off unless you choose to allow it.
External fonts and the home-page image are still requested from their providers; the consent setting does not block those content requests. Applicable rules for these requests and the deployed hosting configuration require separate review. This policy does not determine legal requirements or establish compliance.
Your controls
Use Privacy settings in the footer to reopen the preferences interface; in retailer and administrator portals, use the Privacy settings control. Save a different choice at any time to change or withdraw preference-storage permission. Rejecting or withdrawing preference storage attempts to delete its local keys while retaining authentication and consent storage. Clearing all browser site data also removes the Supabase sign-in session and may sign you out; it does not delete application account records.
Worldwide visitors and policy maintenance
PriceBag is intended for people in multiple countries, and privacy rules can depend on where you are. The service operator should obtain qualified legal review of Ghana's Data Protection Act, 2012 (Act 843), EU data-protection and ePrivacy requirements, and UK GDPR and PECR requirements where applicable. This policy does not determine which laws apply or claim compliance.
This Cookies Policy covers browser storage and similar technologies. The Privacy Policy covers broader account, retailer, message and activity data. We will update this page when the implementation changes; it is not automatically monitored.