Cookie Policy

RShift uses necessary sign-in and edge-security mechanisms, and browser storage for your chosen locale and in-progress work. The marketing website’s aggregate analytics and the signed-in application’s analytics have separate configurations. Where PostHog is enabled in the application, it stores analytics state in localStorage and can associate permitted feature events with an account or organization. PostHog session recording is off by default, with an optional mode and feature-flag gate. This is analytics storage even when no analytics cookie is set; the common optional-storage controls apply where consent is required.

OAuth and Stripe pages can use their own necessary mechanisms under the respective provider’s controls. Clear cookies or local/session storage using browser settings; removing authentication storage can prevent sign-in. Clearing browser drafts can remove unsaved work.

Planner.li uses necessary authentication and application storage plus Adobe Fonts delivery. Website cookie controls and clearing browser storage affect that browser; desktop content, local agent transcripts and operating-system credential storage are managed through the app or device. Removing authentication storage can sign you out. Planner.li has no advertising networks or cross-context advertising trackers.

Enola websites use no advertising cookies or third-party advertising trackers. Necessary invitation, sign-in and security mechanisms support requested account access. Provider pages and enabled messaging platforms use their own mechanisms. Browser controls can remove cookies but do not delete account, conversation or messaging-consent records; use the deletion commands in the Enola privacy provisions above.

The public website does not intentionally set advertising or analytics cookies. Infrastructure may use strictly necessary delivery and security mechanisms. Blocking them can affect delivery; browser settings provide removal and blocking controls.

Public websites use no own advertising or analytics cookies. Necessary delivery/security mechanisms and Adobe Fonts requests remain part of delivery. Account sign-in, chosen interface storage, connected providers and secure checkout can use necessary mechanisms for those requested features, with their respective browser/provider controls.

Public websites use no own advertising or analytics cookies. Necessary delivery/security mechanisms and Adobe Fonts requests remain part of delivery. Account sign-in, chosen interface storage, connected providers and secure checkout can use necessary mechanisms for those requested features, with their respective browser/provider controls.

Inference.Pay uses necessary Clerk sign-in/session and Cloudflare delivery/security mechanisms, browser caching and chosen interface preferences. Adobe Fonts and external checkout providers receive delivery requests. It uses no advertising/cross-site tracking pixels, session replay or non-essential analytics cookies. Browser/provider controls manage these mechanisms; removing sessions can prevent account access.

Bots.Pay uses Clerk __session / __client_uat authentication, Cloudflare __cf_bm where needed for security, chosen local interface preferences and Adobe Fonts requests. Public marketing analytics are aggregate and cookieless, with no persistent visitor identifier or stored analytics IP address. Account processing remains identifiable. Bearer-token API requests do not require cookies. Stripe, PayPal and GitHub pages use their own mechanisms and controls. Removing browser sessions can sign you out; it does not delete hosted agents or balances.

AIEvals sets no own advertising or analytics cookies and uses no advertising pixels, session replay or cross-site analytics. Necessary hosting/security mechanisms, browser caching and Adobe Fonts requests support delivery. Browser settings manage storage; blocking necessary mechanisms may affect the website.

AI Agent Pay uses necessary authentication/security mechanisms and chosen interface storage. External sign-in, merchant and checkout pages use their own policies and controls. Browser controls can remove cookies or preferences; they do not revoke an approved transaction or erase required order records.

4dub uses necessary sign-in cookies lasting up to seven days and short-lived edge/network-security cookies. It uses no advertising or analytics cookies and no browser storage for tracking. Necessary-only use does not require an optional-cookie banner. Cookie-free event analytics can still be linked to a signed-in account, as described in the privacy provisions. Adobe Fonts and Iconify requests expose normal delivery metadata; plain service emails have no tracking pixels. Browser settings control cookies, with sign-in affected if necessary sessions are removed.

nnu.us uses necessary Clerk authentication, Cloudflare security/delivery and chosen interface preferences. nnu_i18n_redirected remembers language. The opaque nnu_capture_intent cookie supports the Save-to-NNU handoff for approximately 15 minutes; source metadata is staged on the server and the cookie contains no source URL or note. A legacy pending short-link draft in browser storage expires after one hour and is removed after activation.

Cloudflare’s aggregate performance beacon is cookie-free. Server-side Library telemetry uses a pseudonymous Space key and excludes URLs, queries, private text and contact/account/resource identifiers. Adobe Fonts receives ordinary connection metadata. nnu.us uses no advertising cookies or cross-site behavioral advertising. Blocking authentication or handoff storage prevents the related feature; browser controls can clear preferences and pending drafts. Third-party sign-in and payment pages apply their own controls.

Necessary browser mechanisms support sign-in, security and chosen preferences. Limited aggregate website measurement excludes terminal content, files, secrets and prompts. Browser storage controls apply to that browser; connected-host credentials and application records must be managed through the relevant account, device or provider controls.

heap.page uses necessary Clerk sign-in, Cloudflare security and chosen progress, filter, follow and navigation preferences. Cookie-free server measurement uses route/event/status/hour aggregates rather than a browser tracking identifier. Stripe’s selected checkout has its own necessary mechanisms. The current product uses no advertising networks, advertising cookies or session replay. Clearing browser storage can remove saved progress or a pending action and can sign you out.

Adobe Fonts receives ordinary request metadata. Outseek uses no third-party advertising/social cookies, email-open pixels or session replay. Clear browser storage to remove local records; this can disrupt sign-in, pending actions, source access or checkout recovery. Global Privacy Control suppresses optional conversion measurement.

Tokens.Pay uses necessary Clerk authentication (__session and __client_uat where applicable), Cloudflare security such as __cf_bm where needed, and chosen interface preferences. Public-site analytics are aggregate and cookie-free; the optional RShift consent-based visitor-identification mode is not used. Adobe Fonts receives ordinary connection metadata. APIs use bearer credentials rather than browser cookies. Selected Stripe or PayPal checkout pages apply their own necessary controls. There are no advertising cookies, cross-site trackers, marketing pixels or session replay. Browser controls can remove authentication and preferences, which can prevent account features.

Reading the public catalogue does not require an account or model request. Dashboard and Profile use Clerk’s necessary authentication; APIs use the credentials you provide. Cloudflare delivers and secures the service, and Adobe Fonts receives ordinary connection metadata. The website sets no advertising or analytics cookies. Browser controls can clear sign-in state and preferences; deleting those does not delete hosted documents or account records. A selected external checkout or destination applies its own controls.

Serialize’s public tools do not persist tool inputs or results in browser storage. When a visitor changes the advertising preference, the site stores a first-party localStorage value named serialize.advertising.disabled on serialize.dev to remember that preference. Removing this value or clearing site data removes the preference. If browser storage is unavailable, the tool pages do not request advertising.

Where advertising is enabled, Google AdSense and its partners may use cookies or other identifiers subject to applicable regional privacy choices. Visitors can disable Serialize advertising for future page loads at https://serialize.dev/how-it-works/#privacy, or use ?privacy=1 on an individual tool URL. This site preference does not withdraw a choice previously made through a Google consent message or delete previously stored third-party cookies. Use the configured Google privacy message to review those choices, and browser controls to manage stored cookies. Advertising preferences do not disable application assets, Adobe Fonts or network requests that visitors explicitly run.

The legacy Inspector separately stores saved Recipes and named schema profiles on the device. Clearing its application storage removes those records. Hosting, security and externally requested resources receive ordinary connection metadata. A choice on gridheap.com does not automatically set a preference on serialize.dev.