Cookie Policy
Last updated: 2 July 2026
CrewAhead may use cookies and similar browser technologies to operate the platform, maintain security, remember necessary settings and support core user sessions.
This policy explains what cookies and similar technologies are, which categories CrewAhead currently uses, and how you can manage them. Not every technology described will be active at all times; the categories below describe the platform's current implementation.
What cookies and similar technologies are
Cookies are small text files that a website stores on your browser. They allow limited information to be remembered between visits or during a browsing session.
Similar technologies include browser storage mechanisms such as localStorage and sessionStorage. These are not cookies, but they serve comparable purposes for storing limited information locally in your browser.
CrewAhead uses both cookies and browser storage, depending on what each feature needs.
Essential or strictly necessary technologies
Essential technologies are required for the platform to operate and to keep your account secure. They may be used for:
- authenticating you when you sign in;
- maintaining your signed-in session while you use the platform;
- enabling server-side routing checks to verify your access rights for protected routes;
- remembering temporary information needed for a page or workflow to function.
Specifically, CrewAhead stores your access token in your browser's localStorage and also mirrors it to a short-lived cookie (named ca_at) so that server-side routing checks can confirm your session. The refresh token is stored in localStorage only.
Preference and browser-storage technologies
CrewAhead uses browser storage to remember choices that make the platform easier to use. These are not stored as cookies, but they are stored locally in your browser.
- localStorage may be used for interface preferences such as sidebar state and other UI settings, as well as for authentication tokens, user profile cache, and recent navigation or filter choices.
- sessionStorage may be used temporarily during multi-step workflows to keep form state while you complete the workflow.
CrewAhead is a dark-only platform. It does not currently offer a theme selector, and therefore does not store a theme choice as a cookie.
Analytics and measurement
CrewAhead does not currently use analytics cookies or similar tracking technologies to measure platform usage. If CrewAhead introduces or materially changes analytics or measurement technologies, this policy will be updated to reflect the relevant provider and purpose.
Third-party services
CrewAhead does not currently use third-party advertising cookies. Some platform features rely on third-party services that may apply their own technical storage when you use them:
- Social authentication providers (such as Google, Facebook, or LinkedIn) may set their own cookies or use their own storage when you choose to sign in through them.
- Payment processors (such as Stripe or Razorpay) may use their own cookies or storage when you make a payment on the platform.
Any such use is governed by the third party's own terms and privacy or cookie policies. CrewAhead does not control these technologies.
Disabling essential technologies may affect platform use
Blocking or deleting essential cookies, or clearing stored authentication data, may sign you out, prevent account access, interrupt form submission, or reduce platform functionality.
Managing cookies and browser storage
You can normally inspect, delete, block, or clear cookies and browser storage through your browser settings. The exact menu and options depend on your browser and device.
Please note that blocking or deleting essential platform data may sign you out, prevent account access, interrupt form submission, reset local preferences, or reduce functionality.
Retention
The duration of a cookie or similar technology depends on its purpose. Some expire when your browser session ends, while others may remain for a limited period until they expire or are deleted. For example, the access-token cookie used for middleware checks is set to expire after seven days.
Changes to this policy
CrewAhead may update this policy when platform technology or legal requirements change. The current revision date is displayed at the top of this page. You should review the latest version periodically.
Questions
If you have questions about this Cookie Policy, contact crewsahead@gmail.com or Contact CrewAhead.