NDA policy
Confidential target, customer, contract, revenue, or live deal data should not be shared until mutually acceptable NDA or equivalent confidentiality terms are in place. Request NDA review by email or through the contact page.
Compliance
Controls for confidential transaction analytics.
This page states the operating policies a deal team usually needs before sending customer revenue files: NDA coverage, subprocessors, retention and deletion, IP ownership, model/data use, conflicts, and information barriers.Policy coverage
NDA coverage, retention, ownership, model use, conflicts, and barriers stay explicit.
Subprocessor policy
No confidential deal files should be uploaded through the public website. Engagement-specific subprocessors, access purpose, and available SOC 2 or equivalent evidence are disclosed before file transfer.
Retention and deletion
Default retention is the engagement period plus 30 days unless the engagement letter states otherwise. Deletion requests are targeted within 10 business days, with written confirmation after completion.
IP ownership
Client owns client data, final outputs, and transaction-specific work product. Wysdome claims no ownership rights in client data or transaction-specific outputs beyond rights needed to perform the engagement, and retains only its pre-existing templates, methods, know-how, and platform IP.
Model-training policy
Wysdome's default policy is not to use client data or transaction outputs for model training. Engagement-specific AI or API use, including data-use restrictions, should be reviewed and approved in the applicable written terms.
Conflicts
If Wysdome is asked to support simultaneous mandates involving the same target, it will disclose the conflict where permitted, decline one side, or establish a written conflict protocol before proceeding.
Information barriers
Each engagement should have a separate workspace, limited team access, project code, file naming convention, and access review. Cross-client reuse of deal data is prohibited.
Subprocessors
Confidential file subprocessors are engagement-specific.
Wysdome does not provide a public website upload path for live deal files. The confidential-file vendor schedule should be agreed before file transfer.Public website host
Access purpose
Public website traffic and non-confidential site operation only; no live deal-file upload path.
Status
Security posture to be confirmed before confidential use.
Business email / calendar provider
Access purpose
Business contact information and non-confidential scheduling or service inquiries.
Status
Vendor security documentation available through provider trust resources where applicable.
Secure storage / portal provider
Access purpose
Confidential files only if listed in the signed engagement-specific subprocessor schedule.
Status
SOC 2 or equivalent evidence requested before use for confidential deal files.
AI API provider, if approved
Access purpose
No client data unless expressly approved in writing for a defined workflow.
Status
Engagement-specific data-use and model-training restrictions should be reviewed before written approval.
Data and AI
Handling rules and AI disclosure stay separate from regulated advice.
Data handling
Do not submit confidential customer lists, contracts, tax IDs, payment data, or live deal files through public email.
Sensitive materials should move only after confidentiality expectations and an intake method are established.
Access should be limited to the agreed engagement team and the minimum data needed for the requested analysis.
Retention, deletion, subprocessors, and model/data-handling terms should be addressed in the applicable written agreement.
Platform outputs are analytical support for client review; they are not investment, legal, tax, accounting, credit, valuation, or securities advice.
AI disclosure
AI may assist with anomaly flagging, draft buyer questions, field classification, and documentation where permitted.
AI does not make investment, credit, valuation, legal, tax, accounting, or securities recommendations.
Human review is required before output delivery.
Source data and formulas remain reviewable; AI output is not treated as authoritative.
Wysdome's default policy is not to use client data or transaction outputs for model training; engagement-specific AI/API terms may be reviewed and approved in writing.
Scope and operations
Coverage, currency, cadence, escalation, and capacity are stated up front.
Geography and currency
US and international targets can be reviewed if files can be mapped to agreed English-language field definitions.
Multi-currency analysis requires transaction currency, reporting currency, period date, and an agreed FX source or management FX policy.
Outputs can show local currency, reporting currency, and constant-currency views where data supports it.
Local accounting, tax, employment, privacy, sanctions, and regulatory conclusions are outside Wysdome's scope.
Communication cadence
Standard cadence is kickoff, source receipt confirmation, exception check-in, first-pass delivery, and revision review. Active fire drills can use daily check-ins if scoped.
Point of contact
Each engagement should name one client-side point of contact and one Wysdome point of contact for data, scope, and delivery decisions.
Escalation path
Questions or disputed outputs should be escalated directly to support@wysdome.com. Urgent post-delivery issues are triaged within 1 business day.
Capacity
Wysdome targets a limited founder-led load of 2 to 3 simultaneous active transaction workstreams. If at capacity, new requests are waitlisted or scheduled by urgency.