Loading
Loading
Effective date: [EFFECTIVE DATE]
This Cookie Policy explains how [LEGAL COMPANY NAME] ("Tool Trader", "we", "us" or "our") uses cookies and similar storage technologies in the Tool Trader website and progressive web app, and how related device storage supports mobile features. Read it together with our Privacy Policy, which explains how personal information is used, shared and retained.
Cookies are small pieces of information that a website stores in your browser and that your browser can send back with later requests. They help a service recognise a session, keep you signed in and protect requests.
We also use browser session storage, local storage and service-worker caches. Session storage holds information for a browser-tab session. Local storage can retain preferences between visits until the application or your browser removes them. Service-worker caches store resources that help the PWA load efficiently and provide its available offline experience.
These technologies have different storage and deletion behaviour. Clearing cookies alone may not clear local storage, PWA caches or native app data.
The website and PWA use a session cookie to associate browser requests with your session. This supports sign-in, account access and transaction flows. A request-security token, including an XSRF-TOKEN cookie where used, helps protect authenticated requests against cross-site request forgery.
If you choose Remember me, a separate authentication cookie can support sign-in between visits. Its lifetime and the session cookie's lifetime depend on the application's configured settings. Signing out invalidates the relevant account session; deleting cookies can also sign you out.
A short-lived clear_sw_cache signal can instruct the PWA to clear stored caches after a session change. The application removes that signal after handling it.
Session and remembered-sign-in cookie names and retention periods: [SESSION COOKIE NAME AND RETENTION PERIOD; REMEMBER-ME COOKIE RETENTION PERIOD]
The marketplace can store your selected browsing location and recent selections so that it can show nearby tools and avoid repeatedly asking you to select an area. Browser storage entries used for this feature include tt_geo and tt_geo_recents. Stored information can include a location label, coordinates and an account reference where applicable.
Device location is requested when you choose the current-location feature. You can search manually instead. Location search and related provider processing are described in the Privacy Policy. Clearing browser storage may reset your location selection.
Browser storage supports returning to the appropriate screen, completing a listing flow, avoiding repeated notices and recording whether an onboarding or verification prompt has already been shown. Examples include tooltrader_onboarding_seen, tooltrader_tutorial_seen and verification-prompt entries.
Temporary session entries can also support payment authentication and return navigation, including payment-provider authentication steps. These entries help the interface resume the relevant flow; they do not replace the server's authoritative booking, order or payment record.
If you enable supported web push notifications, Firebase Cloud Messaging uses a browser subscription and token to deliver notifications. Browser storage can hold the notification token and your response to a permission prompt, including tooltrader_fcm_token and tooltrader_fcm_push_not_now.
You can manage notification permissions in your browser or device settings and use the notification settings available in the platform. Removing a stored token does not automatically remove your browser's permission; these are separate controls.
The PWA service worker can cache application resources to support loading and the available offline screen. Cached resources do not mean that payments, bookings or other transactions can be completed without a connection. The platform still needs server and provider responses for those actions.
The native mobile app also uses device storage for authentication, onboarding and preferences. Guest marketplace locations are stored separately from signed-in account selections. These native storage entries are not necessarily browser cookies. Embedded payment or verification pages may use browser storage or cookies under the relevant provider's policy.
Features such as payments, seller onboarding, identity verification, maps and messaging involve third-party providers. Depending on the feature you use and the provider's implementation, these providers may use cookies, device identifiers or other storage technologies for security, authentication and service delivery.
Third-party cookie inventory: [THIRD-PARTY COOKIE NAMES, DOMAINS, PURPOSES AND RETENTION PERIODS]
Cookies and similar technologies used to provide a requested sign-in or security function should be distinguished from optional measurement or advertising technologies. The applicable consent requirements depend on the purpose and the laws that apply to the service.
Optional analytics, advertising and other non-essential technologies: [ENABLED OPTIONAL TOOLS, PURPOSES, PROVIDERS AND RETENTION PERIODS]
Available consent and withdrawal controls: [COOKIE CONSENT OPTIONS AND HOW TO CHANGE OR WITHDRAW THEM, WHERE APPLICABLE]
Accepting the User Agreement or Terms of Service does not replace any separate consent required for optional storage or tracking. Device-location and push-notification permissions are also separate choices.
Use your browser's privacy or site-data settings to view, block or delete cookies and other site storage. You can usually change third-party cookie settings separately. To remove PWA caches or permissions, use the browser's controls for the Tool Trader site or installed web app.
In the mobile app, device settings can control location, camera, photos, microphone and notification permissions. Native app storage may require separate app-data controls; clearing a browser's cookies does not necessarily clear native app storage.
Blocking or removing storage can sign you out, reset preferences, interrupt payment-return navigation or prevent features from working correctly. It does not delete server-side accounts, transaction history or records held by providers. Contact us for privacy requests relating to those records.
Session storage normally ends with the browser-tab session, subject to browser restore behaviour. Persistent cookies expire according to their configuration. Local storage can remain until removed, and PWA caches can remain until refreshed or cleared by the application or browser. Some account-related entries are cleared on sign-out.
Provider cookies follow the relevant provider's retention settings. The cookie and storage details above should be read alongside the Privacy Policy's information-retention section; removing a device entry does not determine how long a related server record is kept.
We may update this policy as our features or storage technologies change. The effective date appears at the beginning. Where required, we will provide notice of material changes.
For questions about cookies, device storage or related privacy choices, contact us using the details below.
Company: [LEGAL COMPANY NAME]
Business address: [REGISTERED BUSINESS ADDRESS]
Privacy email: [PRIVACY EMAIL]
Support email: [SUPPORT EMAIL]
