Legal
Cookie & Browser Storage Policy
Cookies, local storage, session storage and payment-security technologies.
Version 2026-09-17 · In effect from 17 September 2026
1. Current position
The IAP platform currently sets no first-party cookies of its own. It uses a small amount of first-party browser storage for sign-in and requested functionality. There is no analytics, advertising, behavioural tracking, session-recording technology or advertising pixel currently installed.
The rules for cookies also apply to similar technologies that store or access information on a device, including local storage and session storage.
2. First-party browser storage
| Name | Type | Purpose | Validity / lifetime | When set | Current status |
|---|---|---|---|---|---|
| iap_access_token | Local storage | Sign-in/access token | Token validity: 12 hours; remains until sign-out or browser storage is cleared | After successful sign-in | Essential authentication/security functionality. |
| iap_refresh_token | Local storage | Keeps the user signed in / refreshes access | Token validity: 30 days; remains until sign-out or storage is cleared | After successful sign-in | Essential authentication functionality. |
| iap_pending_request | Session storage | Preserves an unfinished help request while a signed-out user signs in | Current browser tab only; deleted after use | Only when a request is submitted while signed out | Essential to complete the user-requested booking flow. |
| iap_alerts_muted | Local storage | Remembers a Supplier choice to mute new-job alert sound | Until browser storage is cleared | Only when Supplier chooses to mute alerts | User-requested preference; not used for tracking. |
3. Stripe payment-security cookies
| Cookie | Provider | Purpose / activation |
|---|---|---|
| __stripe_mid | Stripe | Payment security/fraud prevention. Set when the customer reaches the Stripe payment stage, not on general marketing pages. |
| __stripe_sid | Stripe | Payment security/fraud prevention. Set when the customer reaches the Stripe payment stage, not on general marketing pages. |
Stripe controls these cookies under its own privacy/cookie practices. IAP integrates Stripe for card payments and uses these technologies only as part of the payment/security functionality.
4. Consent and strictly necessary use
There is currently no non-essential analytics, advertising or tracking technology installed that would require an analytics/advertising consent banner. Authentication/security storage and storage needed to complete a service requested by the user are used only for those functional purposes. The Supplier mute preference is created only when the Supplier actively chooses that setting.
If IAP later introduces analytics, advertising or another non-essential storage/access technology that requires consent, it will not be activated before the required choice is made and the platform will provide an appropriate method to accept/reject/manage preferences.
5. Other browser/network disclosures
OpenFreeMap map tiles are fetched directly by the visitor’s browser. This means the visitor’s IP address and the map area being viewed may reach OpenFreeMap. This is described in the Privacy Policy even though it is not an IAP cookie/browser-storage item.
6. Managing browser storage
You can use browser/device settings to clear local/session storage or cookies. Clearing authentication storage will sign you out and may remove saved preferences. Blocking functionality that is essential to the requested service can prevent parts of the platform from working. The platform also removes authentication storage when it expires, when you sign out, or when it otherwise ceases to be necessary, rather than relying on you to clear browser storage.
7. Changes and contact
IAP will review this policy whenever website integrations change. If analytics, advertising, chat, embedded content or other storage/access technologies are introduced, the technical audit and this policy must be updated before or at deployment. Contact: admin@picklebreakdown.co.uk.