Last updated: August 10, 2026
This Cookie Policy explains how 1811 Labs (Vatsal Sanghvi), operating UGC Pulse, uses cookies and similar technologies on the marketing site and signed-in product. It should be read with our Privacy Policy.
1. Technologies covered
A cookie is a small text record stored by a browser. Similar technologies include local storage, software-development-kit identifiers, pixels, tags, and device or session identifiers. They can remember a choice, maintain a session, protect a service, measure use, or report whether an email was opened.
A technology may be first-party, meaning it is set for a UGC Pulse domain, or third-party, meaning a provider receives or controls it. Blocking a technology may affect features that depend on it.
2. Categories
- Strictly necessary: needed for security, authentication, service delivery, load balancing, billing, or recording a privacy choice.
- Preferences: remember a setting or choice that is not essential to deliver the requested page.
- Analytics: help understand visits, navigation, feature use, reliability, and product performance.
- Session replay: may create masked recordings or heatmaps of interactions when Microsoft Clarity is activated.
UGC Pulse does not currently identify any advertising technologies in this marketing repository. The analytics tools below are not advertising technologies merely because they measure use. If we later add advertising or cross-context behavioral advertising, we will update this Policy and applicable controls before use.
3. Current marketing-site technologies
| Technology | Provider and purpose | Category | Duration | When used |
|---|---|---|---|---|
site_consent_v1 | UGC Pulse first-party cookie that records whether analytics was accepted or rejected and the choice version. | Strictly necessary preference record | 180 days | Written after a visitor uses the existing analytics choice control. It is not written when no choice is presented or made. |
_ga | Google Analytics 4 identifier used to distinguish browser instances and measure site use. | Analytics | Retained for up to two years under Google's default configuration. | GA4 is loaded only when a measurement identifier is configured for an authorized environment and the current consent logic permits loading. |
_ga_<measurement-id> | Google Analytics 4 property-specific session and state identifier. | Analytics | Retained for up to two years under Google's default configuration. |
The current marketing code does not show an analytics prompt when no optional analytics vendor is configured, because optional analytics is disabled in that state. When GA4 is configured under the current implementation, an existing consent control can accept or reject analytics before the Google tag loads.
4. Planned or conditional technologies
The following tools are planned or conditional. They are listed for transparency because they may be used in the signed-in product or a future marketing configuration. Listing them does not mean they are currently loaded on every page.
| Technology | Provider and purpose | Expected duration | Current status |
|---|---|---|---|
mp_<project-token>_mixpanel and related browser storage | Mixpanel identifiers for product usage, feature adoption, funnels, and diagnostics. | Depends on project configuration, commonly persistent for up to one year. | Mixpanel is not currently loaded by this marketing repository. Its signed-in product deployment and exact storage must be verified before activation. |
_clck, _clsk, and Microsoft-domain identifiers such as CLID, ANONCHK,MR, MUID, and SM | Microsoft Clarity usage analytics, heatmaps, and masked session replay. | Microsoft currently documents _clck for one year, _clsk for one day, and provider-domain identifiers from a session to about one year depending on purpose. | Microsoft Clarity is not currently loaded by this marketing repository. Replay masking, consent mode, and retention must be verified before activation. |
| Authentication cookie or local storage | The signed-in product may use Supabase-backed authentication or session storage to maintain login and security. | Session-based or until token expiry, logout, or account security action, depending on product configuration. | Not set by this marketing repository. Exact signed-in product storage must be documented from its deployed configuration. |
5. Third-party pages and emails
If you continue to a Dodo Payments checkout or another third-party page, that provider may set its own necessary, fraud-prevention, preference, or analytics technologies under its policy. Those technologies are not set by this marketing page merely because we link to the provider.
Emails sent through Autosend may use a small pixel or link identifier to report delivery, opens, or clicks when enabled. You can disable image loading in your email client and unsubscribe from marketing messages. Essential service messages may still be sent.
6. Your controls
- Use the available Cookie settings control to change an existing UGC Pulse analytics choice.
- Use browser settings to block, delete, or limit cookies and local storage. Blocking necessary storage can prevent login or other features.
- Use a provider's browser add-on, account setting, or vendor opt-out where available.
- Send a Global Privacy Control signal. We honor legally binding preference signals where applicable and technically supported.
- Contact hello@ugcpulse.app with a privacy or cookie request.
Deleting or blocking a browser identifier does not retroactively delete information already transmitted. A new identifier may be created if you later allow the technology again. To request deletion of information already held, use the rights process in our Privacy Policy.
7. Analytics without an on-page prompt
Depending on the tool, environment, location, and configuration, nonessential analytics may start without an on-page prompt. The absence of a pop-up does not remove any right you have under applicable law or turn a nonessential technology into a necessary one. You may use the controls above, and we will assess legally valid consent, objection, deletion, and opt-out requests.
Some jurisdictions require prior consent before nonessential technologies are activated. This Policy describes technologies and controls but does not by itself replace consent where local law requires it.
8. Changes and contact
Cookie names, purposes, and durations may change when a provider or configuration changes. We will update this Policy when a material change requires it. The date above shows the latest revision.
Questions may be sent to hello@ugcpulse.app.