Cookies and Skippership

Learn how Skippership tracks sessions using local storage instead of cookies and how cookies are used on our website.

Skippership does not use cookies for tracking your website visitors. Instead, we store all tracking information directly in the browser’s local storage. This approach ensures user privacy while enabling accurate session tracking.

Local Storage

Each visitor’s session data is saved under keys that include your project’s tracker ID (YOUR_TRACKER_ID). These keys store:

  • Last active time of the visitor
  • Session start date and time
  • Unique identifiers for the visitor session and events
  • A persistent visitor ID

Example local storage keys (replace YOUR_TRACKER_ID with your actual tracker ID):

  • __YOUR_TRACKER_ID_last_visitor_active_time → The last time the visitor interacted with your site
  • __YOUR_TRACKER_ID_visitor_session_date → Timestamp of the session start
  • __YOUR_TRACKER_ID_visitor_session_event_uuid → Unique ID for each event in the session
  • __YOUR_TRACKER_ID_visitor_session_uuid → Unique ID for the session
  • __YOUR_TRACKER_ID_visitor_uuid → Unique visitor ID

Using local storage allows Skippership to track sessions, replay user actions, and provide insights, all without storing personal data in cookies.

Cookies on Skippership.com

While Skippership tracking does not rely on cookies, our own website uses a few cookies for operational and functional purposes:

  • _ga, _ga_DZ9PPD1YTW, _ga_T9FBV7RJ5T → Google Analytics cookies for site performance and visitor statistics
  • cookieyes-consent → Stores your consent preferences for cookies on the website
  • TawkConnectionTime and twk_uuid_6887cc91670c54192a8b44ff → Used by Tawk.to for live chat functionality and session management

All cookies on Skippership.com are either strictly necessary or functional. None of them are used to track visitors across external sites or to capture sensitive personal data.