Catalyst Adaptive Systems

Before you sign in

Catalyst uses your founder-created account, password authentication and essential session/security records to provide and protect access. A later signature does not retroactively authorize earlier collection. Product telemetry is a separate later choice. Do not submit government ID or project secrets here.

Operator and privacy/grievance contact: Daniel Allen Dugas, operating Catalyst under the Catalyst Adaptive Systems brand · [email protected].

United States privacy notice · 1.2

1. Who operates this beta

Daniel Allen Dugas operates Catalyst under the brand Catalyst Adaptive Systems. Questions, copy requests, withdrawal of electronic-delivery consent, or requests concerning your information should be sent to [email protected]. This notice concerns account-provisioned private testers, not unrelated public-site analytics or marketing subscriptions.

2. Intake, signing, and essential security records

The intake collects your contact email, legal name, adopted typed signature, and your separate affirmative agreement, electronic-record, retention and eligibility choices. Provider configures your workspace/company name, purpose, testing department focus and display name before first login; you are not asked to configure those during legal intake. Your authenticated founder-provisioned tester account authorizes intake and is recorded as the identity basis for signing. Your contact email is supplied by you and is not independently verified by this process. Evidence includes the authenticated account, your entered legal name and signature, choices, server timestamps, available trusted request IP/browser information, exact agreement/notice/artifact versions and hashes, document-access evidence and the complete retained signed copy. This evidence is not notarization or government identity verification.

We do not ask for a government ID, Social Security number, full birth date, biometric signature, or precise location. Essential session cookies and security/transaction events are used to deliver intake, prevent abuse, and preserve your choices. Passwords, email codes, access tokens, and unsubmitted signature-field keystrokes must not be recorded in activity analytics.

3. Private-beta activity and content

With the separate beta-telemetry consent, we collect account-linked session IDs; pages/routes entered and exited; time spent; tab visibility changes; clicks and submissions; errors and run status; and the Genie prompts, other submitted inputs, and results needed to understand testing. Daniel and authorized personnel or service providers may review this information to diagnose problems and improve the product. Testing is not anonymous.

We do not record your microphone, camera, entire screen, or every keystroke through this consent. Any separately requested recording needs separate permission. Use synthetic or supplied sample data, not real sensitive records. Declining beta telemetry means not entering this instrumented private beta; it does not prevent viewing public information or requesting a conversation. Withdrawing consent stops future beta telemetry and private-beta participation; it does not erase a signed agreement or records we must lawfully retain.

4. Service providers and AI processing

Infrastructure, edge/hosting, email-delivery when configured, and AI service providers may process the information needed to perform their roles. Test prompts or submitted content and results may be processed by the AI services enabled for your beta. Before access, the intake provides a current provider disclosure identifying the services used for the signing path and private beta, together with the practices and limitations that have actually been verified. Any account-specific retention or training setting that has not been verified is disclosed as unverified rather than assumed. Do not assume information stays on Daniel's computer or that every provider has the same practices.

Intake identity, NDA documents, and signature records are not sent to AI models, added to Company Brain, or made available to departments for product reasoning. We do not sell tester personal information or use beta intake/telemetry for targeted advertising. Marketing messages and testimonials require separate choices.

5. Retention and access

Detailed beta telemetry and routine security logs are retained for up to 90 days unless a specific incident, dispute, or legal requirement calls for longer retention. Test-workspace content is removed within 90 days after participation ends, unless a shorter demo reset removes it first. Identifiable feedback is de-identified or removed on that schedule; non-identifying product findings and permitted feedback may be retained to improve Catalyst.

The signed agreement, exact accepted notices, and minimal signature evidence are kept separately from resettable demo data, normally for six years after participation ends. At that point continued retention must be reviewed and justified by continuing trade-secret obligations, a dispute, a legal hold, or another legal requirement; otherwise the records are securely deleted. This is an operating retention policy, not a claim that the law always requires six years. Deleted data may remain in access-restricted backups for up to 90 additional days and is not returned to ordinary use after restoration.

Access is limited to people and providers who need the information for these purposes. You can request a copy or correction, or request deletion subject to applicable law and the need to preserve contract/security evidence. We verify requests before releasing personal records. Withdrawal or account closure does not erase completed signatures or rewrite their history.

6. Electronic records: read before consenting

Your electronic-delivery consent covers this beta agreement, its acceptance receipt, this notice, and related beta-administration records. You may decline electronic signing and ask about a paper process before participating. You may request a paper or electronic copy at no charge by emailing the contact above; a postal address is requested only when needed to mail a paper copy. Provider must receive and verify any required paper acceptance before private access is enabled.

You may withdraw consent to future electronic records or update your delivery email by contacting Provider. Withdrawal does not invalidate an agreement already signed or cancel its confidentiality obligations. We will confirm the change within a reasonable time. Online participation may be paused while an alternative delivery/signing arrangement is made; there is no withdrawal fee.

You need an internet-connected device, a contact email address you supply (not independently verified during intake), a browser capable of displaying this intake, and a way to open and save the provided PDF (or retain the complete printable HTML version). Before consenting, open the supplied document in the same format used for your signed copy and confirm that you can access and retain it. We will notify you of material changes to technical requirements and request renewed consent where required.

A complete agreement and acceptance receipt will be available to download, save or print immediately after signing. No automatic email delivery is promised or required; this onboarding flow does not depend on a transactional-email provider. You may request an electronic or paper copy at no charge using the contact above, including after private-beta access ends.

7. Separate choices in the intake

(A) Agreement: I have read and agree to the Confidential Beta Testing Agreement v1.2.
(B) Electronic records: I consent to electronic signing and delivery for the records described above, and confirm I can access and retain the supplied document.
(C) Beta telemetry: I consent to the private-beta activity/content collection described in this notice.
(D) Eligibility: I am in the United States, am at least 18, have legal capacity to enter this agreement where I live, and am signing for myself.

No choices are preselected. There is no marketing opt-in in this required step.

Provider disclosure

Disclosure version live-local-1

Private-beta agreement, invitation, signature and telemetry-choice records are stored on Daniel's Catalyst host in protected local storage outside resettable tester workspaces. No automatic transactional email provider is required for signing; the complete signed copy is immediately downloadable in Catalyst. Public access is delivered through Catalyst's existing secure gateway/Cloudflare path. After access is granted, individual Catalyst product features may separately use their configured providers. The NDA intake itself does not send legal identity, signature or agreement records to AI models or Company Brain.

Cloudflare

Role
Public HTTPS edge/tunnel for the private Catalyst site
Data received
Network request metadata and encrypted web traffic necessary to deliver the site
Account / product
Catalyst private Demo access
Retention and training practices
Existing Catalyst edge/tunnel configuration; no additional hosting/compliance representation is made here
Checked on
2026-09-17
Primary documentation
Existing Catalyst deployment configuration
Limitations
Invite-only beta; no enterprise hosting or compliance claim is made.

OpenAI

Role
AI processing for Catalyst product features that invoke a hosted model after beta access is granted
Data received
Feature inputs/context submitted by the applicable Catalyst workflow; legal signing records are excluded
Account / product
Configured Catalyst model provider
Retention and training practices
Account-specific retention/training settings have not been verified for this beta and are disclosed here as unverified
Checked on
2026-09-17
Primary documentation
Current Catalyst product configuration
Limitations
Use synthetic/sample data only; do not submit sensitive production records.

Sign in · Agreement status · Contact and paper options