Cookie Policy

Cookies are small text files that a website places on your device when you visit. They are widely used to make websites work efficiently, to remember your preferences, to authenticate users, and to provide aggregate information to the site owner.

Throughout this Policy, the term "cookies" also covers similar technologies — including local storage, session storage, IndexedDB, tracking pixels, beacons, SDK identifiers, and server-side tagging — to the extent any of those are in use on the Services. Where a technology is functionally equivalent to a cookie, we treat it identically for the purposes of this Policy and applicable law.

We use cookies and similar technologies for three purposes: to deliver core functionality of the Services (strictly necessary), to measure how the Services are performing in aggregate (analytics), and — if the client ever introduces them — to support marketing campaigns. Today, TRC does not use marketing or advertising cookies.

We group cookies into the categories listed below. The CCPA distinguishes between "sale" and "sharing" of personal information; for the avoidance of doubt, no cookie on the Services results in a "sale" or in "sharing" for cross-context behavioral advertising.

• Strictly necessary cookies — required to deliver core site functionality such as remembering your language preference. These cannot be disabled without breaking the site.
• Analytics / performance cookies — help us understand how visitors interact with the Services in aggregate so we can improve them. We use Vercel Analytics and Vercel Speed Insights, which collect non-identifying, aggregate metrics.
• Marketing / advertising cookies — TRC does not currently set any. If we ever do, we will request your opt-in consent first via a cookie banner and update this Policy.

The cookies and storage keys in the table below are first-party and essential. You can block them via your browser, but the Services may not function as expected.

• NEXT_LOCALE (first-party, cookie, active) — remembers your language preference (en or es). Set by the next-intl library when you change languages, with SameSite=Lax. Duration: 1 year. Purpose: localization.
• trc_cookie_consent (first-party, cookie + localStorage, active) — records your choice in the cookie banner so you are not asked again. Set with SameSite=Lax and Secure on HTTPS. Duration: 1 year, or until the consent schema version changes. Purpose: storing your consent preference.
• __Host-trc_session (first-party, cookie, not yet in use) — will be set if and when student authentication is enabled, to maintain your signed-in session in the future portal. Duration when introduced: session-only, or up to 30 days if "remember me" is selected. Purpose: authentication.

We use Vercel Analytics and Vercel Speed Insights. Both are designed to be cookieless: when they are active they send anonymous, aggregate event beacons to Vercel's servers and do not store any cookie, local-storage key, or other persistent identifier on your device.

This means there are no entries to list under "analytics cookies" — there are no analytics cookies on this site. The data Vercel receives includes the URL of the page you viewed, your approximate region derived from your IP, your browser type, and the timing metrics that make up Core Web Vitals (LCP, INP, CLS, TTFB, FCP). It does not include your IP address in full, your name, or any identifier we could use to recognize you on a later visit.

When you turn off the Analytics toggle in our cookie banner — or when your browser sends a Global Privacy Control (GPC) signal — we stop loading the Vercel scripts entirely, so no beacon is sent at all.

TRC does not currently set marketing or advertising cookies. We do not use Google Ads remarketing, Meta Pixel, LinkedIn Insight Tag, TikTok Pixel, or similar advertising technologies on the Services.

If we ever introduce any such technology, we will (a) update this Cookie Policy to list it, (b) request your opt-in consent through a clearly visible cookie banner before any non-essential cookie is set, and (c) honor Global Privacy Control as an opt-out signal where state law requires.

We do not currently embed third-party widgets that set their own cookies (no Twitter timelines, no Facebook Like boxes, no YouTube embeds with tracking). If a teaching cohort embeds a third-party video or quiz that sets its own cookie, the cohort mentor will inform you and that provider's own privacy policy will apply to those cookies.

You can refuse, accept, or delete cookies at any time through your browser settings. Below are quick links to the cookie controls of the major browsers — instructions can change, so refer to your browser's documentation for the latest steps.

• Google Chrome — Settings → Privacy and security → Cookies and other site data.
• Mozilla Firefox — Settings → Privacy & Security → Cookies and Site Data.
• Apple Safari (desktop) — Settings → Privacy → Manage Website Data.
• Apple Safari (iOS) — Settings → Safari → Block All Cookies.
• Microsoft Edge — Settings → Cookies and site permissions → Manage and delete cookies and site data.
• Brave — Settings → Shields → Cookies.

Our Services honor the Global Privacy Control (GPC) browser signal as a valid opt-out of any future sale or sharing of personal information and of any future targeted advertising, in jurisdictions where state law requires us to do so.

Many browsers also send a legacy "Do Not Track" (DNT) HTTP header. There is no industry consensus on how DNT should be honored. We do not respond to DNT separately; we honor the more specific GPC signal as described above.

If you disable all cookies, you can still browse the Services but some features will not work as expected: your language preference will reset on every visit, and we will not be able to keep you signed in to a future student portal. Disabling analytics cookies has no effect on the functionality of the Services for you; it only reduces the aggregate data we use to improve them.

Consistent with our Privacy Policy, our Services are directed to students aged sixteen (16) and older. We do not knowingly collect personal information from children under thirteen (13) through cookies or any other technology.

We may update this Cookie Policy when our use of cookies changes — for example, when we add a new analytics provider or remove an existing one. The "Last updated" date at the top of this page reflects the most recent revision. Material changes will be communicated via a notice on the Services for at least seven (7) days before they take effect.

If you have questions about this Cookie Policy, email [email protected] or write to us at the postal address in our Privacy Policy.