Privacy policy
Effective and last updated: 2 August 2026
Local-first by design. Transparent by policy.
This policy explains how all 15 Selfhood Studios extensions handle user data, and separately explains analytics on this marketing website.
The extensions require no Selfhood account and use no Selfhood sync, analytics, advertising, or telemetry service. Extension data is stored locally unless you deliberately use a feature that must contact a download origin or a third-party service you selected.
[ 01 ]The register
Per-extension data practices
- Data collected or handled
- Kuro handles the address and styling structure of ordinary pages it themes: stylesheet rules and variables; computed background, text, border, and accent colours; semantic element and region types; privacy-filtered representative selectors; media counts; open-shadow-root, frame, stylesheet, and coverage statistics; and the current theme identity and route pattern used to select a cached plan. It also handles the theme, palette, contrast, typography, site-rule, workspace-profile, automation, schedule, user-entered location, circadian-warmth, and interface settings you save; optional custom CSS and development pack overrides; generated local or remote theme plans and their diagnostics; the remote provider, model, design vision, custom endpoint, consent state, and API key or bearer token you choose to configure; and browser tab state needed to apply a theme.
- How collection occurs
- Kuro's declared content scripts match ordinary pages at <all_urls>. A document-start fallback and the selected theme engine read the current page's styles and structure, apply colour transformations, and watch relevant stylesheet, single-page-navigation, open-shadow-root, and dynamic-content changes while Kuro is enabled for that page. Kuro reads tab identifiers and addresses to select per-site settings, exact-route plans, and temporary overrides. Theme preferences, schedules, profiles, provider settings, credentials, and location coordinates come directly from values you enter or controls you change. Local site intelligence samples style facts from the rendered page; it does not need page text, form values, screenshots, query strings, fragments, or the raw DOM in its generated summary. A remote plan is not requested until remote mode is enabled, the required disclosure is accepted, and a manual or automatic planning action calls for it.
- How data is used
- Kuro uses this information only to determine whether and how to theme the current page; map colours and enforce the selected contrast and media policies; remember global, profile, site, route, and tab-specific choices; keep dynamic pages themed; activate or change themes according to time, system appearance, sunrise, sunset, and circadian settings; generate, validate, cache, replay, diagnose, and refine privacy-bounded theme plans; fetch page-owned stylesheet or image resources needed by the active engine; and show the toolbar popup, side-panel console, options, shortcuts, and optional context-menu controls. It is not used for advertising, unrelated profiling, eligibility or credit decisions, resale, or data-broker services.
- Handling and storage
- Settings, site rules, profiles, automation values, user-entered coordinates, provider and model configuration, consent records, generated plan cache entries, installation metadata, and provider tokens are kept in browser-managed extension storage. Provider tokens remain in chrome.storage.local, are excluded from settings export, and are not copied into browser sync. If you explicitly enable Kuro's browser-native settings sync, the settings object—including theme, profile, site, automation, location, and provider-selection fields but not the separately stored provider token—is also written to chrome.storage.sync under your browser account. The default theme-plan cache holds at most 200 entries for at most 90 days; both limits are adjustable. An exact-route replay copy may also live temporarily in that tab and origin's sessionStorage. Tab registry state, automatic-mode state, and temporary tab overrides are session-scoped. Kuro has no Selfhood Studios application backend, account, analytics, advertising, or telemetry service. Locally stored values are not separately encrypted by Kuro; they rely on browser-profile, operating-system, and device security.
- Retention and deletion
- Theme-plan cache entries expire after the configured age and are least-recently-used trimmed to the configured maximum; the defaults are 90 days and 200 entries. You can clear all cached plans or a site's plan, disable site intelligence, revoke remote-plan or site-identity consent, remove each provider token, reset settings, disable browser-native sync, clear a temporary tab override, or uninstall Kuro. Tab-scoped replay data and temporary state end when the relevant tab or session closes or are cleared when the theme or plan no longer applies. Other local or browser-synced settings remain until you change, reset, or delete them or uninstall the extension, subject to the browser account's own sync behaviour. A request already sent to OpenRouter, DeepSeek, or a custom endpoint follows that recipient's logs, account settings, contract, and retention policy; Selfhood Studios cannot retrieve or delete that copy.
- All parties data is shared with
- Kuro does not send extension data to Selfhood Studios. Local theming and deterministic site planning require no AI provider. Only after you enable Manual or Auto remote planning and explicitly consent does Kuro send a direct request to your selected endpoint: OpenRouter, DeepSeek, or the custom HTTPS endpoint you entered. The recipient receives the provider credential where required, provider and model choice, your design vision and theme preferences, an allow-list of privacy-filtered selectors, and a compact style summary containing colours, CSS-variable samples, semantic region and element types, font size and weight, area ratios, media counts, contrast findings, stylesheet and frame counts, coverage, and complexity. The summary excludes page text, form values, accessible labels, screenshots, query strings, fragments, and the raw DOM. Hostname and a parameter-redacted path pattern are included only if you separately enable Share site identity. The provider also receives ordinary connection metadata such as IP address, request time, and HTTP headers. When an engine must retrieve a cross-origin stylesheet or image already referenced by the page, that resource's origin receives a credential-free, no-referrer request from the browser; private and local network targets are rejected. Selfhood Studios receives information only if you deliberately send it for support or disclosure is legally required. Kuro does not sell or rent data or share it with advertisers or data brokers.
- Data collected or handled
- Prism handles the address and title of the page being inspected; page text excerpts, headings, links, forms, metadata, structured-data types, selectors, attributes, DOM and HTML snippets, accessibility roles and names, computed styles, design tokens, layout fingerprints, resource and timing information, Core Web Vitals, and visible-page or element screenshots when the selected feature needs them. It also handles audit findings and scores, muted-issue rules, preview edits, fix packs, exported reports, audit-history metadata, chat prompts and responses, AI tool traces, provider and model settings, custom endpoint addresses, and any provider API key you choose to save.
- How collection occurs
- Prism's declared content scripts match ordinary pages at <all_urls>. The vitals script starts at document_start and observes current-page performance measurements in memory; the main page bridge loads at document_idle. A full audit, element inspection, accessibility-tree read, token extraction, viewport capture, screenshot, preview edit, export, or AI tool read occurs when you open Prism and invoke the relevant user-facing workflow. Prism reads active-tab details through the tabs capability and does not request the chrome.history API. Running an audit saves a local history entry unless storage fails. If usable AI credentials are already configured, completing that user-started audit also automatically requests an executive summary from the configured provider. Chat sends what you type and, while the Attach page context setting is enabled, a compact current-page context summary. Vision, deep-analysis, responsive-critique, component-generation, and visual-history actions can additionally attach screenshots, element crops, audit evidence, or tool results.
- How data is used
- Prism uses this information only to audit accessibility, UX, SEO, performance, and security; measure page vitals; inspect elements and accessibility structure; extract and export design tokens; preview reversible fixes; generate and export audit reports or fix packs; preserve and compare audit history and visual regressions; emulate requested viewport sizes; and provide the AI summary, chat, vision, analysis, or code-generation action you request. It is not used for advertising, unrelated profiling, credit or eligibility decisions, resale, or data-broker services.
- Handling and storage
- Rule-based analysis runs in the inspected page and extension contexts. Prism stores settings, provider configurations and API keys, muted findings, and up to 60 audit-history entries in chrome.storage.local in the Chrome profile where it is installed. Compressed visual-history screenshots are stored in the extension's IndexedDB database with a least-recently-used limit of 10 screenshots per website origin. Current chat state, tool traces, live performance readings, page context, element-inspection results, and unapplied preview state are generally held in extension or page memory for the active session. The theme bootstrap also reads the prism-theme value from extension localStorage. Prism has no Selfhood Studios application backend, account, sync, analytics, advertising, or telemetry service. API keys and other locally stored values are not separately encrypted by Prism; they rely on Chrome-profile, operating-system, and device security.
- Retention and deletion
- Audit history is capped at the newest 60 entries. Visual-history screenshots are capped at 10 per website origin and the least recently accessed capture is evicted when that limit is exceeded. You can delete an individual history entry, clear all history and its linked captures, clear muted issues, reset settings, or remove saved provider credentials in Prism. Session-only page context, chat state, tool traces, inspection data, and performance observations are discarded when the relevant extension or page context closes, reloads, or is replaced. Other local settings remain until you reset or delete them or uninstall Prism. A copy already sent to an AI provider or custom endpoint follows that recipient's account settings, contract, logs, and privacy and retention policies; Selfhood Studios cannot retrieve or delete that copy.
- All parties data is shared with
- Prism does not send extension data to Selfhood Studios. When a configured AI workflow runs, Prism sends requests directly to the active endpoint: DeepSeek, OpenAI, OpenRouter, Anthropic, xAI, or the custom OpenAI-compatible URL you supplied, which may be a local service such as Ollama or LM Studio. Depending on the action, the recipient receives the API credential or authorization header, provider and model choice, system instructions, your prompt and recent conversation, the page address and title, compact page text and metadata, audit findings, DOM or accessibility evidence, computed-style or token information, AI tool results, and optional page screenshots or element crops required to answer. A configured cloud provider receives ordinary network metadata such as IP address, request time, and HTTP headers. If you configure an http endpoint, its payload is not protected by HTTPS; use http only for a trusted same-device or private-network service. Inspected websites do not receive Prism audit data merely because they are inspected, although any reversible preview you deliberately apply changes the current rendered DOM in that tab. Selfhood Studios receives information only if you deliberately send it for support or if disclosure is legally required. Prism does not sell or rent user data or share it with advertisers or data brokers.
- Data collected or handled
- Task prompts, saved prompts, steering messages, approvals, attached images and page context, dictated audio and transcripts; task-relevant tab titles and URLs, page text, links, form labels and structure, screenshots, selected browser-history results, download and tab metadata, console and network diagnostics, cookie names and flags but never cookie values, text submitted to websites, and website responses; with your consent, the address, title, and readable text of ordinary pages you yourself read, together with when and how long you read them; connected MCP server addresses, request headers you configure, the arguments of calls you approve, and the results those servers return; AI responses, provider-exposed reasoning, citations, action logs, and token, cost and usage data; provider, model, transcription, safety, and blocklist settings and API keys; conversations, memories, favorites, scheduled tasks, background-run records, inbox items, new-tab arrangement and wallpaper preferences, clock and location preferences, weather results, and optional ChatGPT, Claude, or SuperGrok plan and quota-window information.
- How collection occurs
- Nexus obtains data directly from what you type, import, attach, approve, or ask it to remember; from the microphone only after you start voice dictation; and from Chrome's debugger, tabs, history, downloads, storage, and website-access capabilities only when a feature or task you invoke needs that data. The optional reading library is off until you accept a one-time prompt shown on a page you have actually read; once accepted it records ordinary pages you read yourself, and never incognito windows, non-web pages, blocked or excluded sites, sign-in, checkout or signup pages, pages showing a password field, pages with almost no text, long pages you did not scroll, or pages the agent itself is driving. It also receives responses from the model endpoints, transcription endpoints, public sources, connected MCP servers, and websites used for your task. Optional subscription-usage cards make first-party requests using the provider session already signed in within Chrome. User-created scheduled tasks, and tasks whose side panel you closed, can continue or run later from the instruction saved locally.
- How data is used
- To answer questions; research public sources; navigate, read, click, type, submit, upload, download, and otherwise carry out the browser task you request; call the third-party MCP tools you have individually approved; show and export an auditable action trace with its sources and per-turn cost; resume, rerun, edit and re-ask, remember, or schedule work; search pages you chose to have remembered; provide voice input, favorites, world-clock weather, the new-tab launcher and gadgets, and provider-usage cards; enforce confirmations and blocked domains; and estimate model usage. Nexus does not use this data for advertising, unrelated profiling, credit or eligibility decisions, resale, or data-broker services.
- Handling and storage
- Settings, credentials, conversations, memories, favorites, saved prompts, scheduled tasks, background-run records, inbox items, connected-server definitions and their configured headers, the new-tab arrangement, and the model-usage ledger are stored in chrome.storage.local in the Chrome profile where Nexus is installed. The reading library and wallpaper images are stored in the extension's own IndexedDB database in that same profile. Weather responses are cached in extension localStorage. Dictation audio is processed in memory and is not saved to Nexus history. Nexus does not use Chrome Sync and has no Selfhood Studios application backend, account, analytics, advertising, or telemetry service. API keys, MCP request headers, and other local values are not separately encrypted by Nexus; they rely on Chrome profile, operating-system, and device security.
- Retention and deletion
- Local records remain until you delete them, replace them through import, reach a collection limit, or uninstall Nexus. Current limits are 200 conversations, 200 memories, 30 favorites, 100 saved prompts, 200 scheduled-task records, and 300 inbox items; older records may be displaced when a limit is reached. Reading-library pages are kept for a period you choose — 30, 90, or 180 days, or until a page limit of 2,000 by default — after which the oldest and least recently read are removed; you can also forget an individual page, forget every page from a site, or erase the library entirely. Background-run records are limited to the 20 most recent and are discarded a day after you have seen one, or a week if you never do. Weather is treated as fresh for one hour and then replaced when refreshed. Removing a local record does not delete copies already sent to a provider, MCP server, or website, exported files, downloads, browser history, notifications, or backups; those copies follow the recipient's or storage service's controls and retention policy.
- All parties data is shared with
- No Nexus task data is routinely shared with Selfhood Studios. Depending only on the feature you enable or invoke, direct recipients are: (1) your configured AI endpoint—Anthropic, OpenAI, Google Gemini, xAI, OpenRouter, NVIDIA Build, DeepSeek, local Ollama, local LM Studio, or another custom compatible endpoint—which receives its API credential plus the prompt, conversation, system instructions, task-relevant page content, attached images and page context, tool results, source URLs or excerpts, and screenshots needed for the request; (2) your configured transcription endpoint—OpenAI, OpenRouter, Deepgram, Groq, or another custom OpenAI-compatible endpoint—which receives recorded audio and the credential needed to transcribe it; (3) any MCP server you add, which receives the request headers you configured for it and the arguments of each call to a tool you individually approved, and whose returned content Nexus treats as untrusted data; (4) DuckDuckGo, which receives privacy-screened public-search queries, and the public page origins Nexus fetches for research; (5) websites you direct Nexus to visit or operate, which receive normal browser request data, your existing cookies or account session where applicable, and any content you instruct Nexus to submit; (6) Open-Meteo, which receives place names or coordinates, units, and forecast parameters for optional weather; (7) OpenAI/ChatGPT, Anthropic/Claude, and xAI/Grok, which receive credentialed first-party requests when you enable their optional subscription-usage cards; (8) Google's favicon service, which may receive a saved favorite's hostname when Nexus has no captured icon; and (9) Selfhood Studios only if you deliberately send specific information for support, or public authorities if disclosure is legally required. The reading library is never transmitted to Selfhood Studios or to any third party; its contents reach a model endpoint only when a task you run searches or opens a saved page. Remote recipients also receive ordinary connection metadata such as IP address, request time, and browser or HTTP headers. Cloud, website, and custom-endpoint recipients may log, retain, review, or otherwise process data according to your account and organization settings, product tier, agreement, and their own privacy policy. Nexus does not sell or rent user data or share it with advertisers or data brokers.
- Data collected or handled
- Images, canvas edits, masks, export settings, preferences, and any Google AI or OpenRouter API key you choose to save.
- How data is used
- To edit and export images locally and, only when you invoke an AI feature, to submit the image, prompt, and relevant edit context to your selected provider.
- All parties data is shared with
- No data is sent to Selfhood Studios. Optional AI requests go directly to Google AI or OpenRouter over HTTPS when you initiate them.
- Data collected or handled
- Download URLs and history, discovered page media and stream metadata, smart rules, local performance insights, and optional debrid or Usenet credentials.
- How data is used
- To find user-requested media, manage downloads, apply rules, display local statistics, and connect to services that you configure.
- All parties data is shared with
- No data is sent to Selfhood Studios. Requests go only to the download origin and any debrid or Usenet provider you configure. Credentials remain stored locally.
- Data collected or handled
- User-selected URLs, page content and research evidence, notes, decisions, thread metadata, and optional cloud-model API keys.
- How data is used
- To reconstruct research sessions, generate cited briefs, and let you resume a saved thread. On-device Gemini Nano is used by default where available.
- All parties data is shared with
- No data is sent to Selfhood Studios. If you opt into a cloud model, the content needed for that request goes directly to your chosen provider: Anthropic, OpenAI, OpenRouter, Groq, or DeepSeek.
- Data collected or handled
- Screenshots you capture, page context needed for a capture, annotations, redactions, guide text, and export preferences.
- How data is used
- To create, organize, search, redact, and export step-by-step guides on your device.
- All parties data is shared with
- No data is sent to Selfhood Studios or a hosted AI service. Optional enhancement runs locally through Ollama or in-browser WebLLM.
- Data collected or handled
- Bookmarks, saved URLs and page content, notes, tags, summaries, embeddings, knowledge-graph data, chat prompts, and an optional provider API key.
- How data is used
- To build and search your private knowledge base, create local summaries and embeddings, and answer cited questions about your saved material.
- All parties data is shared with
- No data is sent to Selfhood Studios. Processing is on-device by default; if you enable a cloud model, only the content required for your request goes directly to the provider you select.
- Data collected or handled
- Currently open tab titles and URLs, saved sessions, workspace names, checkpoints, preferences, and local usage statistics.
- How data is used
- To organize open tabs into sessions, restore workspaces, and display private productivity insights.
- All parties data is shared with
- No data is sent to Selfhood Studios or any third party. Momentum does not request browsing-history permission and works from open tabs only.
- Data collected or handled
- Saved tab titles, URLs, and favicons, session groups, folders, tags, notes, to-dos, automation rules, optional tab preview screenshots, on-device search embeddings, preferences, and any AI provider API key or sync passphrase you choose to save.
- How data is used
- To save and restore tab sessions, free memory, search and organize your saved tabs locally, and run user-created automation rules. Semantic search embeddings are computed on-device.
- All parties data is shared with
- No data is sent to Selfhood Studios. Shiori has no content scripts and no telemetry. Only if you enable optional AI are saved tab titles, URLs, and group titles sent directly to the provider you configure; optional sync uses Dexie Cloud under your control.
- Data collected or handled
- Screenshots you capture, visible page context needed for capture, edits, OCR text, labels, redaction results, design tokens, and library metadata.
- How data is used
- To capture, edit, search, redact, organize, and export screenshots locally.
- All parties data is shared with
- No data is sent to Selfhood Studios or any third party. OCR and AI labeling run on-device through Gemini Nano where available.
- Data collected or handled
- Tasks, notes, Kanban boards, focus sessions, schedules, blocklists, productivity statistics, preferences, and an optional DeepSeek API key.
- How data is used
- To provide local task management, focus timers, site blocking, notes, and private productivity analytics.
- All parties data is shared with
- No data is sent to Selfhood Studios. Only when you invoke the optional AI co-pilot is the prompt and relevant context sent directly to DeepSeek over HTTPS.
- Data collected or handled
- The page or selected text you choose to summarize, video transcript text on supported pages, your saved summaries and their sources, local usage statistics, preferences, and the Get TLDR API key you save.
- How data is used
- To extract the requested content in your browser and generate a summary through the Get TLDR service, then keep your summaries and usage stats in a local library.
- All parties data is shared with
- No data is sent to Selfhood Studios. Content you choose to summarize is sent over HTTPS to the Get TLDR service to produce the summary; your API key and saved summaries remain stored locally.
- Data collected or handled
- PDFs you open, annotations, form entries, saved signatures, on-device indexes, chats, generated artifacts, preferences, and any AI provider API key you choose to save.
- How data is used
- To read, annotate, organize, and transform PDFs locally, and—only when you invoke an AI feature—to answer cited questions, summarize, and generate artifacts from the document.
- All parties data is shared with
- No data is sent to Selfhood Studios and there is no Satori account or telemetry. Optional AI requests go directly to the provider you configure (a compatible cloud provider or a local Ollama setup); API keys are stored unencrypted in extension local storage.
- Data collected or handled
- YouTube page and player state needed for enabled controls, settings, timestamped notes, transcript text and highlights, local viewing analytics, custom segments, optional AI prompts and outputs, and any provider credentials you choose to save.
- How data is used
- To control playback and page presentation, skip or mark video segments, save notes and viewing preferences, search transcripts, display local insights, and run the AI action you request.
- All parties data is shared with
- No data is sent to Selfhood Studios and there is no Kiwami account or telemetry. Optional AI requests go directly to the cloud or local provider you configure. SponsorBlock, Return YouTube Dislike, and DeArrow features contact their public services only when enabled; settings, notes, analytics, and credentials remain in Chrome storage.
[ 02 ]Scope
Permissions and browsing activity
Each extension is designed to request the narrowest Chrome permissions needed for its current user-facing features. Optional access should be requested at the point a feature needs it rather than for unrelated or future functionality.
Some products handle URLs, page content, visible tabs, screenshots, or media metadata because those inputs are necessary for the feature the user invokes. That information is not used for advertising, profiling, credit decisions, or any undisclosed purpose. It is not sold or provided to data brokers.
[ 03 ]Retention
Local storage, retention, and deletion
Extension content and preferences are retained in browser-managed storage, including IndexedDB and chrome.storage.local, until you delete them, reset the extension, or uninstall it. A product may also use browser-native settings sync only when its register entry discloses that feature and you enable it. API keys and service credentials remain local until you remove them and are not included in Kuro's settings sync or export. We cannot retrieve or restore data that remains only in your browser profile.
Use an extension's delete, reset, or export controls where available before uninstalling. Uninstalling normally removes that extension's local data. Data sent to a provider at your request is retained under that provider's own policy; Selfhood Studios cannot access or delete it on your behalf.
[ 04 ]Third parties
Optional third-party services
Kuro themes and plans sites locally by default. Only after you enable Manual or Auto remote planning and explicitly consent may a privacy-filtered style summary go directly to OpenRouter, DeepSeek, or the custom endpoint you configured. Page text, form values, screenshots, query strings, fragments, and the raw DOM are excluded; site identity is included only through a separate opt-in. The Kuro entry above defines the full payload and controls.
Nexus direct model requests may go to Anthropic, OpenAI, Google Gemini, xAI, OpenRouter, DeepSeek, local Ollama, local LM Studio, or a custom compatible endpoint. Optional Nexus features may also contact OpenAI, OpenRouter, Deepgram, Groq, or a custom transcription endpoint; DuckDuckGo and selected public page origins; websites the user directs Nexus to operate; Open-Meteo; first-party ChatGPT, Claude, or Grok usage endpoints; and Google's favicon service. The Nexus entry above identifies the data each recipient may receive.
Depending on the other extension and your configuration, direct requests may be sent to Google AI, OpenRouter, Anthropic, OpenAI, xAI, Groq, DeepSeek, Get TLDR, Open-Meteo, SponsorBlock, Return YouTube Dislike, DeArrow, a debrid provider, a Usenet provider, or the origin from which you requested a download. These parties receive only the data needed to perform the action you requested and process it under their own privacy policies and terms.
Cloud AI is opt-in and requires you to choose or configure a provider. Gemini Nano, WebLLM, local embeddings, and OCR run on your device. Ollama runs on a local service on your computer. Those local processing paths do not send your content to Selfhood Studios.
[ 05 ]Security
Security
Remote requests containing user data or credentials must use secure transport such as HTTPS or WSS, except when a product explicitly permits and you deliberately configure a same-device development or local-model endpoint. Authentication information is not publicly disclosed. Local data remains protected by Chrome's extension isolation and the security of your browser, operating system, and device.
No security measure is absolute. Keep Chrome and your operating system updated, protect your device account, and revoke or replace a provider key if you believe it has been exposed.
[ 06 ]Compliance
Chrome Web Store Limited Use disclosure
Extension user data is used only to provide or improve the extension's disclosed single purpose and user-facing features. We do not sell extension user data, use it for personalized or interest-based advertising, transfer it to data brokers, or permit Selfhood Studios personnel or contractors to read it. Routine human access is not possible because we do not receive extension content. The limited exceptions are when you explicitly send specific data for support, access is necessary to investigate security or abuse, disclosure is required by law, or data is first aggregated and anonymized for lawful internal operations. A provider or other recipient identified in the per-extension register may receive and process only the data necessary to perform the feature or action you requested.
The use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements.
[ 07 ]Consent
Notice and consent
Each Chrome Web Store listing and its Privacy practices disclosure must accurately identify the data handled by that extension. Where a feature sends data to a third party, the extension must disclose the transfer before it begins and require an affirmative user action.
If an extension's data practices materially change, we will update this policy, the Store disclosures, and the in-product notice before the new handling begins, and obtain consent where required.
[ 08 ]This website
This website and Google Analytics
This marketing website uses Google Analytics to understand aggregate website usage, including page views, referrers, browser and operating system information, device type, and country of origin. Google Analytics may set cookies or use similar identifiers as described in Google's privacy documentation.
Google Analytics is part of this website only. It is not bundled into any Selfhood extension and cannot access content stored inside an extension. Website analytics are not combined with extension data, used for personalized advertising, or sold by Selfhood Studios.
[ 09 ]Contact
Contact and policy scope
For privacy questions, security reports, or requests concerning information you deliberately provided to us outside an extension, contact Selfhood Studios through the studio website. Because we do not receive extension-local content, we cannot inspect, export, or delete it remotely.
Contact Selfhood Studios ↗This policy supplements, but does not replace, disclosures shown in each extension and its Chrome Web Store listing. If those disclosures conflict with actual product behavior, the product and disclosures must be corrected; this policy does not authorize undisclosed data handling.