Privacy Policy

Information Chamber collects

Chamber currently collects information in the following categories:

• Account information such as name, email address, encrypted password, and account timestamps.
• Chamber content you create, including chamber names, category labels, weights, modifiers, source notes, and clarification responses.
• Feed and product activity, including sign-up, onboarding, feed views, article opens, dwell timing, scrolling, feedback actions, and session-level metadata used for product analytics.
• Preference and tuning data, such as read state, “more like this,” “less like this,” hidden sources, hidden topics, subscriptions, and sharing settings.
• Operational records, including asynchronous task payloads, OAuth applications or tokens created through the product, and logs needed to secure and operate the service.
• Model usage records that attribute token counts, model identifiers, provider names, and related metadata to account-level Chamber features.
• Standard technical data generated when you use the site, such as request logs, session cookies, and security-related metadata sent by your browser or device.

How Chamber uses information

• To create, maintain, personalize, and secure accounts and chambers.
• To compile feeds, attach sources, classify content, compute embeddings, refine future results, and show “why this is here” or similar explanatory product features.
• To measure onboarding, retention, reading activity, allocation health, and other internal product metrics.
• To prevent abuse, enforce the Terms of Service, troubleshoot failures, and protect the service and its users.
• To communicate with users about account, security, operational, or legal matters.
• To improve Chamber’s product quality, source discovery, feed matching, and editorial controls.

Model and third-party processing

Chamber uses third-party infrastructure to run the service. Based on the current implementation, that includes hosting, database and queue infrastructure, web-content retrieval, Google-hosted web fonts, and OpenAI-backed model features used through RubyLLM or a limited service integration where needed. Those providers may process data sent to them to perform Chamber’s instructions, secure their systems, or comply with law.

Chamber sends only the information reasonably needed for the relevant feature. For example, chamber specifications, clarification answers, content text, and related metadata may be processed when Chamber parses a prompt, discovers sources, classifies content, or generates embeddings.

When Chamber shares information

• With vendors or service providers that help operate, host, secure, analyze, or improve Chamber.
• With other users or the public when you choose a shareable chamber setting such as link-only or public.
• With your authorized OAuth applications or integrations, if you choose to connect them.
• When needed to comply with law, enforce rights, investigate abuse, or protect users, Chamber, or the public.
• In connection with a merger, acquisition, financing, restructuring, sale of assets, or similar business transaction.

Chamber does not state here that it sells personal information or serves third-party advertising cookies, because the current product does not implement those features.

Cookies and similar technologies

Chamber uses cookies and local browser storage needed for sign-in, CSRF protection, session continuity, and normal product operation. Chamber may also use first-party analytics events tied to your account or session to understand product usage. Chamber does not currently present a separate advertising-cookie flow because the app does not currently implement third-party ad targeting.

Retention

Chamber keeps information for as long as reasonably necessary to operate the service, maintain account history, secure the platform, resolve disputes, and meet legal obligations. Different records may be retained for different periods. Shared chambers, analytics records, feedback signals, and operational logs may remain in backups or derived records for a period after deletion from active systems.

Your choices

• You can edit account profile fields and change your password from the product where those controls are available.
• You can control whether a chamber stays private, becomes link-only, or becomes public.
• You can avoid optional model-backed features by not submitting chambers or feedback that would trigger them, but core product behavior depends on those workflows.
• You can use browser controls to manage cookies, although blocking required cookies may prevent Chamber from functioning correctly.

Children’s privacy

Chamber is not directed to children under 13, and Chamber should not be used to knowingly submit personal information about children under 13.

Changes to this policy

Chamber may update this Privacy Policy from time to time. When Chamber makes a material change, Chamber may update the effective date above and use reasonable product or account notice where appropriate.