What we collect, and why.

Contact asks for your name, email address, and note. Discuss a pilot asks for name, email, office or firm, and a short description of the proposed use. Role, AUM range, review volume, and referrer are optional.

The Contact note and a shortened user-agent string are delivered to the partner inbox through Resend; Contact does not create a public-inquiry database row. Introduction records store the submitted business fields, a privately salted IP hash, and a shortened user-agent string in Supabase, and send the full form submission to the partner inbox so the team can respond. The raw IP is not stored in the introduction row. The same private salt and connection address feed a separate hash used by the atomic public-form abuse control.

An invited pilot member provides account details, engagement details, uploaded documents, questions, and review activity. Diligence OS uses those records to authenticate the member, run the selected workflow, retrieve supporting passages, prepare work for a human operator to review, show an approved memorandum, and keep an audit trail.

Raw document text is not placed in public URLs, product analytics, or customer-visible error messages. External model and retrieval providers may receive document-derived text only when the House policy contains the required provider-privacy evidence.

The current code integrates Vercel for hosting and AI Gateway routing, Supabase for authentication, database, and private storage, Resend for email, PostHog for limited product and intake analytics, Sentry for error monitoring, Claude models for language-model processing, and Voyage for embeddings and reranking. The signed pilot documents and deployment inventory confirm which providers apply to a specific pilot.

The public introduction event sent to analytics contains an opaque per-form request identifier, categorical business ranges, and booleans rather than the submitted name, email address, office name, referrer name, or free-text note.

Source records support an expiry date, but the current code does not assign one when no deployment default is configured. A supervised pilot must not begin until its written retention period, source-expiry configuration, and scheduled deletion sweep are verified together. We do not present a 90-day policy as an enforced control without that receipt.

The code does not yet enforce a fixed deletion schedule for introduction records. That is a disclosed pilot limitation, not a hidden promise. We retain those records while evaluating and responding to the request and for reasonable security and recordkeeping needs. You may use the Contact form to ask about access, correction, or deletion. We verify the requester and assess the exact record, applicable law, and signed commitments before acting; no fixed response period is promised on this candidate page.

The public forms are optional. Do not place confidential deal documents or sensitive personal information in a public note. Upload pilot documents only through an authorized engagement and under the handling instructions agreed for that pilot.

We may update this notice when the product or provider list changes. Material changes will be reflected on this page before the affected handling is used for a new pilot.