Skip to content
OnboardUX
  • Solutions
  • Demo
  • How it works
  • For FDEs
  • Security
  • Resources
GitHubDesign partner
SolutionsDemoHow it worksFor FDEsSecurityResourcesGitHubDesign partner
  1. Home
  2. Legal
  3. Privacy policy

LEGAL & TRUST

Privacy policy

Draft information about how the public website may handle personal data. Material business and legal facts are unresolved.

Status
Draft — not approved for production
Last reviewed
2026-08-14
This development copy contains explicit business and legal placeholders. It must be reviewed by qualified counsel and completed before production launch.

Who would be responsible

The data controller for this website has not been approved. The production policy must identify[LEGAL ENTITY NAME — REQUIRED BEFORE PRODUCTION], its relevant address, and [PRIVACY CONTACT — REQUIRED BEFORE PRODUCTION].

Current development-site behavior

The website application is designed to be privacy-minimal. In its current form, it:

  • does not run behavioral analytics, advertising pixels, session replay, or fingerprinting;
  • does not set non-essential cookies or persist demo state in browser storage;
  • uses fictional demo data rather than customer or product data; and
  • shows a disabled contact form that has no action, API, or delivery provider.

A production hosting provider may process ordinary network and security information when serving a request. The approved provider, categories, purposes, legal bases, recipients, and logs must be documented in [PRODUCTION DATA INVENTORY — REQUIRED BEFORE PRODUCTION].

Information and purposes

No production-purpose inventory has been approved. Before launch, this section must state each category of personal data, whether it is provided directly or collected automatically, the precise purpose, and [LEGAL BASIS BY PURPOSE — REQUIRED BEFORE PRODUCTION].

If the contact form is enabled later, its name, work email, company, optional role, and message fields require a notice at collection and a separately reviewed backend, provider, access model, and deletion process. Visitors must be told not to submit confidential client information.

Retention, sharing, and transfers

No retention promise is made by this draft. Production periods and deletion criteria belong in[RETENTION SCHEDULE — REQUIRED BEFORE PRODUCTION]. Actual vendors must be listed on the subprocessor page before they process website data.

International transfers, safeguards, and processing locations remain[TRANSFER MECHANISM AND LOCATIONS — REQUIRED BEFORE PRODUCTION].

Your rights and choices

Applicable rights, identity-verification steps, authorized-agent rules, appeal routes, and response handling depend on the approved entity and jurisdictions. See Privacy choices. A usable request method remains[PRIVACY REQUEST METHOD — REQUIRED BEFORE PRODUCTION].

Children, security, and changes

The age/minors position is [MINORS POSITION — REQUIRED BEFORE PRODUCTION]. The final policy must describe available safeguards accurately without treating architecture as a certification. Its effective date and change-notice process remain[EFFECTIVE DATE AND NOTICE PROCESS — REQUIRED BEFORE PRODUCTION].

OnboardUX

The post-implementation layer for custom software and AI systems.

[LEGAL ENTITY NAME — REQUIRED BEFORE PRODUCTION]

Product

  • Solutions
  • Demo
  • For FDEs
  • Delivery leaders
  • Plans

Developers

  • GitHub
  • Getting started
  • CLI status
  • Resources

Trust

  • Security
  • DPA
  • Subprocessors
  • Vulnerability disclosure
  • Accessibility

Legal

  • Privacy
  • Terms
  • Cookies
  • Acceptable use
  • Privacy choices
  • Company details
© 2026 Onboard UX. Draft website.No advertising trackers or non-essential storage.