Cookie Policy
This policy explains how Pillar uses cookies and similar browser-storage technologies when you use the Pillar field service management platform.
Last updated: February 2026
1. What are cookies
Cookies are small text files that websites store on your device when you visit them. They help the site remember information about your visit, such as whether you are logged in or what preferences you have set. Some data is stored in your browser's localStorage instead of traditional cookies -- localStorage works similarly but persists until explicitly cleared.
2. How we use cookies and browser storage
Essential cookies
These cookies are required for the platform to function. They handle authentication and session management using secure, HttpOnly cookies that are not accessible to client-side scripts. Without these cookies, you cannot log in to or use Pillar.
- Access token -- Authenticates your session with the server. Issued as a secure, HttpOnly JWT cookie. Expires after 15 minutes and is automatically refreshed.
- Refresh token -- Used to obtain a new access token without requiring you to log in again. Issued as a secure, HttpOnly cookie. Expires after 7 days.
Functional storage (localStorage)
These values are stored in your browser's localStorage to remember your interface preferences across sessions. They do not contain personal data and are never sent to our servers automatically.
- Theme -- Your display preference (light, dark, or system). Persists until you change it.
- Active view -- The role view you last selected (e.g., Owner, Dispatcher, Technician). Persists until you switch views.
- Sidebar state -- Whether the navigation sidebar is expanded or collapsed. Persists until you change it.
Analytics cookies
We may use analytics tools to understand how the platform is used and to identify areas for improvement. If analytics cookies are active, they collect anonymized usage data such as pages visited, session duration, and feature adoption. You can opt out of analytics cookies through your browser settings.
3. Third-party cookies
Certain features of Pillar integrate with third-party services that may set their own cookies. Pillar does not control these cookies. The third parties involved are:
- Stripe -- Handles payment processing for invoices and subscriptions. Stripe may set cookies to support fraud detection and secure payment collection. See Stripe's Privacy Policy for details.
- Google Maps -- Provides map views, geocoding, and route planning within the platform. Google may set cookies when map features are loaded. See Google's Privacy Policy for details.
4. Managing cookies
Most browsers allow you to control cookies through their settings. You can typically view, delete, or block cookies for specific sites. Consult your browser's help documentation for instructions on managing cookies.
Important: Disabling essential cookies (the access token and refresh token) will prevent you from logging in to Pillar. The platform requires these cookies to authenticate your session.
Clearing localStorage will reset your theme, active view, and sidebar preferences to their defaults. This will not affect your account or data.
5. Cookie and storage reference
The following table lists the specific cookies and localStorage values used by Pillar.
| Name | Type | Duration | Purpose |
|---|---|---|---|
| access_token | HttpOnly cookie | 15 minutes | Authenticates your session with the Pillar API |
| refresh_token | HttpOnly cookie | 7 days | Refreshes the access token without requiring re-login |
| theme | localStorage | Persistent | Stores your display preference (light, dark, or system) |
| active_view | localStorage | Persistent | Remembers which role view you last selected |
| sidebar_collapsed | localStorage | Persistent | Stores whether the navigation sidebar is expanded or collapsed |
6. Contact
If you have questions about this cookie policy or how Pillar uses browser storage, contact us at admin@pillarfsm.com.