Privacy Policy

Last updated: September 24, 2026

This Privacy Policy explains how [[PROVIDER]] ("Smoozi," "we," "our," or "us") collects, uses, stores, shares, and protects information when users access the Smoozi website, platform, and related services.

Smoozi provides proprietary B2B decision-support software for observing AI-assisted product-development workflows and supporting product judgment, review, and acceptance.

1. Scope

This Privacy Policy applies to information processed through:

• the Smoozi website and public marketing pages;
• Smoozi application and workspace surfaces;
• connectors and observer components;
• support and operational communications; and
• related analytics, diagnostics, security, and billing-support systems.

2. Information We Collect

Smoozi may collect information provided directly by users, information generated through use of the service, and information received from authorized service providers.

Account information

This may include:

• name;
• email address;
• company or organization information;
• account role;
• authentication and account-security information;
• subscription plan and status;
• communication preferences; and
• account settings.

Customer Data and connected production information

This may include:

• connected production conversations and history;
• agent replies and tool results;
• instructions and product records;
• authorized project artifacts such as files, diffs, logs, tests, and similar workspace evidence;
• decisions, corrections, Product DNA, and Founder DNA; and
• other content a customer connects or otherwise authorizes.

Technical and usage information

This may include:

• IP address;
• browser and device information;
• operating system;
• session identifiers;
• timestamps;
• referral and campaign information;
• pages and features used;
• interaction events;
• error information;
• security events; and
• platform-performance information.

Support and diagnostic information

When users contact support or when Smoozi investigates a technical, account, subscription, or operational issue, Smoozi may process:

• support communications;
• account and workspace identifiers;
• relevant workflow state;
• recent application activity;
• error and diagnostic records;
• browser and device information; and
• limited subscription or billing information relevant to the issue.

Payment-related information

Subscription payments are processed through authorized third-party billing providers.

Smoozi may receive limited billing information such as:

• plan;
• subscription status;
• billing dates;
• amount and currency;
• invoice or transaction identifiers;
• refund status;
• payment status; and
• chargeback status.

Complete payment-card numbers, card-security codes, and banking credentials are submitted to and processed by the applicable billing provider and are not stored by Smoozi as ordinary platform data.

3. How We Use Information

Smoozi may use information to:

• create and maintain accounts;
• authenticate users and protect account security;
• provide observation, review, and related workspace workflows;
• continuously observe connected production systems and correlate activity across tools, agents, vendors, and time;
• generate customer-specific findings, memories, evals, evidence, and outputs;
• provide AI-assisted platform features;
• administer software subscriptions;
• provide customer support;
• investigate technical, account, or billing issues;
• maintain reliability and diagnose errors;
• measure website and product usage;
• attribute campaigns and measure conversions;
• prevent fraud, abuse, and unauthorized access;
• improve usability and workflow efficiency;
• communicate about the service;
• enforce the Terms of Service;
• improve Smoozi through product analytics and the Shared Reliability Library under the controls described in this Policy; and
• comply with applicable legal obligations.

Smoozi does not sell or broker customer personal information as a separate product.

4. Processing Roles and Legal Bases

Depending on the information involved and applicable law, Smoozi may act as a controller, processor, business, or service provider with respect to personal information.

For Customer Data and operational information submitted or connected by business customers, the customer generally determines what information is submitted and which Smoozi workflows are used. Smoozi processes that information to provide the selected software functionality.

For account administration, subscriptions, security, analytics, support, fraud prevention, service operations, and Smoozi's own business administration, Smoozi may determine the relevant processing purposes.

Where applicable law requires a legal basis, Smoozi may rely on:

• performance of a contract or steps requested before entering a contract;
• legitimate interests in operating, securing, supporting, and improving the service;
• compliance with legal obligations; and
• consent where consent is required.

Consent-based choices may be changed through controls provided by Smoozi where available. Withdrawal of consent does not affect processing that lawfully occurred before withdrawal.

5. Customer Data, Product DNA, and Founder DNA

Customer Data is provided, connected, and managed by customers and their authorized users.

Those users are responsible for obtaining any rights, notices, permissions, and authorizations required to upload, process, connect, or distribute that information through Smoozi.

Product DNA is scoped to the authorized project or organization.

Founder DNA is separately scoped to the individual whose judgment it represents.

Smoozi may continuously derive Founder DNA from that person's language, corrections, repeated choices, and accepted outcomes as part of ordinary service operation.

Smoozi does not silently merge private Founder DNA into organization-wide memory or disclose it to unrelated customers.

Available controls and the Customer Agreement will govern inspection, correction, export, deletion, transfer, and retention.

Deleting a person's Founder DNA does not automatically delete the project's separately owned Product DNA or approved decision history.

Neither layer is used to train a shared third-party model or improve Smoozi for other customers without a separate, explicit authorization.

6. Shared Reliability Library

By default, Smoozi may derive limited, de-identified Shared Reliability Records from detected failures, prevented errors, bounded corrections, and verified outcomes.

Eligible records are limited to transformed or generalized signals such as warning and failure categories, redacted structural conditions, evaluation outcomes, correction classes, reliability events, recurrence, and outcome evidence.

They may be used across customers to improve Smoozi's Reliability Pattern Library, evals, detectors, warnings, support playbooks, and product reliability.

Shared Reliability Records exclude raw source code, raw files, raw prompts or transcripts, credentials, secrets, customer and project names, direct personal identifiers, and unredacted Product DNA or Founder DNA.

We apply data minimization, de-identification, rarity controls, and reasonable technical and organizational measures designed to reduce the likelihood that a record can be linked to a customer, project, or person.

No de-identification method can guarantee zero re-identification risk. We will not attempt to re-identify Shared Reliability Records or disclose them as customer-level data.

Shared Reliability Library contribution is enabled by default under the applicable Customer Agreement and lawful-basis framework; it is not presented as consent.

An authorized administrator can disable future contribution at any time in settings or by contacting [[PRIVACY EMAIL]].

Disabling does not affect processing required to provide, secure, diagnose, or support the Services, or the customer's local learning capabilities.

It stops creation of new Shared Reliability Records for that workspace within a reasonable processing period. Information already irreversibly aggregated into shared statistics or validated reliability patterns may not be capable of isolation or removal.

Contribution of raw content, free text, source code, transcripts, Product DNA, Founder DNA, rare identifying patterns, or content-derived examples for shared-model training remains off by default and requires a separate explicit opt-in or written agreement.

7. Cookies, Analytics, and Advertising Technologies

Smoozi uses essential cookies and similar technologies for authentication, account security, session management, consent records, and core service operation.

Smoozi also uses analytics and attribution technologies on public marketing pages.

Google Analytics

Smoozi uses Google Analytics 4 ("GA4") on public marketing pages for site measurement, traffic analysis, campaign attribution, conversion measurement, and website performance analysis. Smoozi's current GA4 measurement ID is G-6X2W1B04XT.

GA4 is activated only after the user allows Analytics & performance cookies.

Google may process browser and device information, IP address, approximate location, pages viewed, interaction events, referral and campaign information, and Google Analytics identifiers for these purposes.

Google Analytics is not used to analyze authenticated workspace content. Smoozi does not intentionally send Google Customer Data, Product DNA, Founder DNA, prompts, transcripts, uploaded files, payment-card data, authentication credentials, or authenticated workspace content.

Smoozi does not authorize behavioral advertising or remarketing unless the live cookie inventory and banner expressly identify the active provider and purpose.

Users may review or change available choices through Cookie Preferences in the Smoozi website footer.

External checkout

Smoozi Cookie Preferences apply to technologies controlled by Smoozi on Smoozi-operated pages.

A third-party billing provider's checkout page may use its own cookies and similar technologies under that provider's privacy and cookie notices. Smoozi Cookie Preferences do not control technologies set independently on an external provider's domain.

8. Product Analytics, Operational Logging, and Session Replay

Smoozi uses first-party logging and PostHog to support product analytics, service reliability, error diagnosis, account support, and security.

Operational records may include timestamps, application events, workflow actions, account or workspace identifiers, device or browser information, and technical error information.

Public marketing pages

PostHog product analytics may be used on public marketing pages after the user allows Analytics & performance cookies.

Authenticated workspaces

Authenticated workspaces may use PostHog session replay and diagnostic tools to help Smoozi investigate:

• technical problems;
• support requests;
• workflow errors;
• subscription or billing issues;
• reliability problems; and
• security incidents.

Session replay may reconstruct visible on-screen interactions, controls, and application state that occurred during a workspace session. This allows authorized Smoozi personnel to investigate technical issues and provide support when the cause of a problem cannot be determined from error logs alone.

Authenticated-workspace diagnostics are operational support functionality and are separate from optional public-page cookie settings.

Session replay is disabled on designated sensitive pages and workflows, including payment-entry, billing, checkout, and certain workspace-setup flows where configured.

Authorized Smoozi personnel may access relevant diagnostic information only where reasonably necessary for support, service reliability, security, billing reconciliation, fraud prevention, or dispute handling.

Smoozi does not intentionally include complete payment-card numbers, card-security codes, banking credentials, passwords, authentication secrets, private tokens, or raw uploaded-file contents in analytics event properties or diagnostic configuration.

Raw source code, prompts, transcripts, notes, support-message bodies, email contents, and raw URL query strings are not intended to be sent as analytics event properties.

Visible workspace content may appear within diagnostic replay where necessary for the replay to reflect the application state being investigated.

Sensitive inputs and designated content surfaces must be masked or blocked before capture. By default, Smoozi does not configure replay to capture raw source code, prompts, transcripts, file contents, credentials, secrets, Product DNA, Founder DNA, payment details, request or response bodies, or authentication headers.

Server-side diagnostics

Smoozi may send technical error or failure events from server-side processes, including scheduled jobs, billing integrations, and support integrations, to its diagnostic systems.

These server-side events are not session replay and do not by themselves reconstruct a user workspace screen.

9. AI Systems and Data Processing

Smoozi uses AI-assisted systems and third-party AI infrastructure as part of its software functionality.

AI systems may process Customer Data, Product DNA, Founder DNA, workflow, and related operational information where necessary to provide features such as:

• observation and interpretation;
• classification and retrieval;
• evaluation and review support;
• workflow assistance;
• AI-assisted customer support and diagnostics; and
• other related product functionality.

Smoozi does not use customer-uploaded or connected content to train public foundation models unless the customer gives separate, explicit authorization.

Third-party AI infrastructure providers may process information only as necessary to provide the relevant functionality, subject to Smoozi's arrangements with those providers.

Customer may also direct Smoozi to send Customer Data to a model, gateway, or other provider that Customer supplies or already uses, including customer-funded or bring-your-own-key arrangements. In that case, the provider's processing is governed by Customer's instructions and that provider's terms.

AI-assisted processing does not change user-selected workspace controls unless the product expressly provides a feature that does so.

10. Third-Party Service Providers and Data Sharing

Smoozi uses third-party providers to operate the service, including providers for:

• hosting and infrastructure;
• authentication;
• communications and email delivery;
• analytics;
• error tracking and session replay;
• AI infrastructure;
• billing and payment processing;
• customer support; and
• security and operational services.

These providers may process information to the extent necessary to provide their services or as otherwise permitted by applicable law and their agreements with Smoozi.

Google processes analytics information as described in Section 7.

PostHog processes analytics and diagnostic information as described in Section 8.

Billing providers process payment and buyer information under their own terms and privacy notices.

Smoozi may also disclose information:

• where required by law, legal process, or valid governmental request;
• to protect Smoozi, its users, or third parties from fraud, abuse, security threats, or unlawful activity;
• in connection with a merger, acquisition, financing, reorganization, sale of assets, or similar business transaction; or
• with the user's direction or authorization.

Smoozi does not sell platform user data to third-party advertisers.

Where applicable privacy law treats certain advertising technology as "sharing," targeted advertising, or a similar regulated activity, users may exercise applicable choices or opt-out rights through controls made available by Smoozi.

11. Payment Information

Smoozi's authorized billing providers process payments for Smoozi software subscriptions.

Smoozi may receive limited subscription, invoice, transaction, refund, payment-status, and chargeback information necessary to administer accounts, provide support, reconcile billing, and resolve disputes.

Complete payment-card and banking credentials remain with the applicable billing provider.

12. Data Retention and Account Deletion

Smoozi retains information for as long as reasonably necessary to operate the service, maintain active accounts, provide support, protect security, satisfy applicable obligations, and administer the account lifecycle described below.

Active accounts

Account and workspace information is retained while an account remains active and according to applicable product settings.

Canceling a paid subscription does not by itself delete the underlying workspace data.

Account deletion

Users may request account deletion through available account settings.

A deletion request disables account access.

The account remains recoverable for 30 days from the original deletion request.

Smoozi-held account, workspace, Customer Data, Product DNA, Founder DNA, workflow, and uploaded-file data attributable to the deleted account is scheduled for physical deletion by day 90 from the original deletion request.

After physical deletion, Smoozi may retain limited information where required by applicable law, necessary for security or fraud prevention, or reasonably necessary to establish, exercise, or defend legal claims.

External billing-provider records remain subject to the billing provider's own retention obligations and policies.

Shared Reliability Records that have already been irreversibly aggregated or de-identified may not be capable of isolation or removal after contribution.

Support records

Support conversations may be archived after 30 days of inactivity and purged from Smoozi's active support systems after six months, subject to limited retention necessary for unresolved disputes, security matters, or applicable legal obligations.

13. Security

Smoozi uses commercially reasonable administrative, technical, and organizational safeguards designed to protect platform information.

Access to production systems, support data, and diagnostic tools is limited to authorized personnel with a business need relating to service operation, support, reliability, security, billing reconciliation, or dispute handling.

Workspaces are designed to expose information only through authorized accounts and workflows.

While Smoozi uses commercially reasonable safeguards, no online service or storage system can be guaranteed to be completely secure.

14. Privacy Rights and Choices

Depending on the user's location and applicable law, users may have rights regarding personal information, including rights to:

• request access to personal information;
• request correction of inaccurate information;
• request deletion;
• object to or restrict certain processing;
• withdraw consent where processing is based on consent;
• request portability of certain information; and
• opt out of certain targeted advertising, sale, or sharing activities where applicable.

These rights may be subject to applicable limitations or exceptions.

Users may manage available cookie and advertising choices through Cookie Preferences.

Users may contact Smoozi to exercise applicable privacy rights.

Smoozi may request reasonable information to verify the identity and authority of the person making a request before acting on it.

15. International Processing

Smoozi primarily serves users in the United States and may process information in countries where Smoozi or its service providers operate, including on customer-controlled devices where local Smoozi software is installed.

Privacy and data-protection laws may differ between those countries and the user's location.

Where required by applicable law, Smoozi uses appropriate mechanisms for international processing or transfers of personal information.

Business customers remain responsible for ensuring that information they submit to Smoozi has been collected and provided in accordance with laws applicable to their own activities.

16. Children

Smoozi is a B2B service and is not intended for use by children.

Users must not knowingly submit personal information relating to children where doing so is not lawful or necessary for an authorized business workflow.

17. Changes to This Privacy Policy

Smoozi may update this Privacy Policy to reflect changes to the service, technology, providers, or applicable requirements.

The current version will be posted with an updated Last updated date.

Where required by applicable law or appropriate because of a material change, Smoozi may provide additional notice.

A change to this Privacy Policy does not retroactively create consent for optional data contribution.

18. Contact

For privacy-related questions or requests, contact [[PRIVACY EMAIL]].

The identity and address of the responsible provider are: [[PROVIDER AND ADDRESS]].