Skip to main content
Validraft

Privacy notice

How Validraft handles personal and engagement data.

This notice explains how Validraft expects to collect, use, share, retain, and protect personal data. It also explains the difference between personal data and confidential strategy materials.

Last updated: June 16, 2026

Categories

Data we may collect

Validraft collects information that you provide directly, information generated by using the website or workspace, and information needed to provide, secure, bill, and support the service.

Account and contact data

Name, email address, company name, role, billing contact, sign-in identifiers, and workspace membership.

Brief and engagement data

Strategy descriptions, hypotheses, instruments, parameters, constraints, data assumptions, files, messages, and feasibility notes you submit.

Report and workspace data

Generated reports, run metadata, monitoring summaries, status updates, messages, support history, and dashboard activity.

Commercial and billing data

Quote requests, invoices, payment status, VAT or tax identifiers, purchase history, and plan or add-on information.

Technical and security data

IP address, device and browser information, log events, authentication events, diagnostics, fraud-prevention signals, and basic usage analytics.

Please do not submit special-category personal data, unnecessary personal financial details, passwords, broker credentials, API keys, or third-party confidential material unless we have expressly agreed to receive it.

Purposes and legal bases

How we use personal data

The exact legal basis depends on the context. The table below describes the expected purposes and likely bases for a pre-launch Validraft service.

PurposeWhat this meansLikely legal basis

Responding to requests and briefs

To review feasibility, answer questions, prepare quotes, and communicate with you.

Pre-contract steps, contract performance, or legitimate interests.

Providing Validraft services

To run scoped validation work, prepare reports, maintain workspaces, and provide support.

Contract performance or legitimate interests.

Security and service reliability

To authenticate users, prevent abuse, investigate errors, protect confidential materials, and maintain audit trails.

Legitimate interests and, where required, legal obligations.

Billing and records

To issue invoices, process payments, manage accounting, and keep business records.

Contract performance and legal obligations.

Product improvement

To improve the website, workspace, intake flow, reporting process, and support experience.

Legitimate interests, using aggregated or minimized data where practical.

Marketing communications

To send updates only where permitted or requested, and to manage unsubscribe preferences.

Consent or legitimate interests, depending on context and applicable law.

Confidential materials

How strategy materials are treated

A trading hypothesis, parameter set, data assumption, report, or run artifact may be commercially sensitive even when it is not personal data. We treat client strategy materials as confidential by default and keep them scoped to the relevant engagement.

  • We do not publish client-specific strategy details without permission.
  • We do not add client hypotheses to a public template library.
  • We do not use your strategy logic for cross-client benchmarking or marketing unless separately agreed.
  • For standard briefs, confidentiality is part of the operating model. For sensitive work, an NDA can be put in place before detailed materials are exchanged.

NDA path

When an NDA makes sense

An NDA, or Non-Disclosure Agreement, is a written confidentiality agreement that defines what information is confidential, who may access it, what it may be used for, how long the duty lasts, and what happens if confidential information is misused.

Tier A / standard

Usually no separate NDA is required. Materials are treated as confidential by default, and an NDA is available on request.

Tier B / business

Recommended where the brief includes investor-facing materials, proprietary signals, commercial datasets, or manager-level research.

Tier C / institutional

May be required before we review custom data, source logic, vendor extracts, portfolio constraints, or internal documents.

The practical rule is simple: you can submit a normal brief without a heavy legal step. If the material is sensitive, institutional, or commercially proprietary, ask for an NDA before sending the details.

Processors

Who we may share data with

We do not sell client personal data. We may share data with service providers and professional advisers where needed to operate, secure, bill, support, or legally protect the service.

  • Hosting, infrastructure, database, authentication, storage, email, analytics, support, billing, and payment providers needed to operate the service.
  • Professional advisers, accountants, legal counsel, auditors, insurers, or regulators where necessary.
  • Data vendors or technical providers where needed to perform a scoped engagement, subject to applicable terms and confidentiality controls.
  • A successor entity if Validraft is involved in a merger, acquisition, restructuring, or asset transfer.

Location

International data transfers

Some providers may process or access data outside your country or outside the European Economic Area. Where GDPR applies, international transfers should rely on an adequacy decision, standard contractual clauses, or another recognized safeguard where required.

Storage

How long we keep data

  • Briefs, engagement records, reports, and workspace records are kept while your account or engagement remains active and for a reasonable period afterward for audit, support, dispute, legal, and accounting purposes.
  • Billing and tax records may be retained for the period required by applicable accounting and tax law.
  • Security logs are generally kept for shorter periods unless needed to investigate abuse, incidents, or legal claims.
  • You may request deletion, but we may retain information where required for legal obligations, dispute handling, security, or legitimate business records.

Website tracking

Cookies and similar technologies

Validraft may use strictly necessary cookies or local storage for authentication, security, session continuity, theme preferences, and workspace operation. Optional analytics, marketing, or tracking cookies should not be used without a proper consent mechanism where legally required.

Before public launch, this section should be synchronized with the actual cookie banner, analytics stack, and consent records used in production.

Safeguards

Security measures

No system is perfectly secure, but Validraft is designed around engagement isolation and limited access to sensitive materials.

  • TLS encryption in transit for website, workspace, brief intake, and report delivery.
  • Authenticated workspace access for reports and engagement updates.
  • Least-privilege internal access to engagement materials.
  • Operational separation between client engagements.
  • No public reuse of client strategy logic or client-specific materials without permission.

GDPR rights

Your privacy rights

Depending on your location and the basis for processing, you may have rights over your personal data. These rights may be limited in some circumstances, for example where we must keep records for legal, security, accounting, or dispute reasons.

  • Access personal data we hold about you.
  • Ask us to correct inaccurate or incomplete data.
  • Ask for deletion where the law allows it.
  • Object to or restrict certain processing.
  • Request portability for data you provided, where applicable.
  • Withdraw consent where processing is based on consent.
  • Complain to a competent data protection authority.

We may need to verify your identity before responding to a privacy request. Requests can be sent to legal@validraft.net.

Contact

Privacy, support, and general requests

The legal boundary for Validraft services is described in the legal notice.