y
Continue

Privacy controls

Cookie Policy

This page explains how Yachtee uses cookies, local storage, session storage and similar browser technologies.

Necessary storage is required for Yachtee to work. Analytics and marketing attribution storage are optional and can be changed below. Analytics includes first-party blog measurement and consented Google Analytics 4 measurement. For broader data handling, read our Privacy Policy.

Your choices

You can accept all optional storage, use necessary storage only, or choose analytics and marketing attribution separately. The choice is stored in this browser so Yachtee can remember it.

No preference has been saved in this browser yet.

What we use

Cookies are small text files stored by your browser. Local storage and session storage are browser storage areas that help an app remember state. Yachtee uses these technologies for authentication, security, app preferences, public application sessions, first-party blog analytics, Google Analytics and campaign attribution.

Categories

Category
Purpose and examples
Necessary
Required for authentication, session recovery, account security, public application progress, auth redirects, onboarding state and requested app preferences. Examples include the httpOnly refresh-token cookie set by the auth API, role or onboarding state in browser storage, pending public application state and the cookie preference record.
Analytics
Optional analytics. When enabled, Yachtee stores first-party blog visitor IDs for article engagement, and loads Google Analytics 4 to measure page views and key launch funnels such as sign-in, onboarding, applications and checkout. GA4 may set cookies such as _ga and _ga_{container-id}, configured by Yachtee for up to 395 days. Raw IP addresses and full user agents are not stored in the Yachtee first-party blog analytics table.
Marketing attribution
Optional first-party campaign attribution. When enabled, Yachtee stores first-touch and last-touch campaign data in local storage and a first-party cookie for up to 90 days. This can include UTM parameters, external referrer, landing path and click IDs such as gclid, fbclid, msclkid or ttclid. The attribution payload may be attached to account creation during email-code verification.

Google Analytics

Yachtee uses Google Analytics 4 only after you grant analytics consent in this browser. Before that, the Google Analytics tag is not loaded. If you later turn analytics off, Yachtee sends a denied consent update and removes GA cookies it can access.

GA4 helps us understand aggregate site traffic, acquisition sources, page engagement and product funnels. Events are designed not to include email addresses, names, CV content or other direct profile details. Yachtee does not grant Google advertising storage, ad user data or ad personalization through this implementation.

Third parties

Yachtee uses third-party services that may receive technical information when their features are used or loaded. These include Stripe for payments, SendGrid for production email, Google Maps and Places for location search, Google Analytics for consented analytics, AWS for file storage and infrastructure, and AI providers for selected CV, profile and hiring-support features.

Third-party sites linked from Yachtee may use their own cookies or tracking technologies. Their policies control those external services.

Email tracking

Some non-transactional emails may include open pixels and tracked links so we can measure delivery, engagement and unsubscribes. You can unsubscribe from non-transactional email categories using the links in those emails or communication preferences in your account where available.

Browser controls

You can also delete cookies and site data through your browser. If you block or delete necessary storage, parts of Yachtee may stop working, you may be signed out, and saved application or onboarding progress may be lost.