000%
PRIVACY NOTICE

How DV Labs handles information submitted through this site.

Last updated: September 22, 2026

Information you provide

DV Labs may collect information you choose to submit through contact, consultation, project, partnership, investor-interest, access-request or support forms. That can include your name, email, phone number, organization, project context, scheduling preferences and the content of your request.

Information stored on your device

Some public experiences use browser storage for preferences or local-only state, such as sound, tutorial state, bookmarks, watchlists, draft blueprints or pending checkout correlation. Clearing browser storage can remove those local preferences.

Accounts and workspaces

Nexus and other authenticated experiences can store account, project, message, file, meeting, payment-correlation or workflow information needed to operate the client relationship. Access to private workspaces is separate from ordinary public browsing.

How information is used

Information is used to respond to requests, evaluate fit, schedule consultations, prepare or deliver work, operate client workspaces, verify commercial state, improve DV systems and maintain operational records. DV Labs does not treat a public form submission as permission to expose confidential information publicly.

Service providers

Current workflows can use service providers such as Supabase for application data and authentication, Stripe for hosted payment processing, and email infrastructure for transactional or relationship communication. Those providers process information under their own terms and privacy practices.

Retention, access and questions

Retention depends on the relationship and purpose of the record. If you want to ask about, correct or request deletion of information associated with a public inquiry, contact DV Labs. Some records may need to be retained for legitimate business, security, accounting or legal reasons.

This notice describes the DV Labs public website and shared operating surfaces at a high level. Individual products, client deployments or regulated use cases can require separate privacy terms.