Legal
Privacy
How velociti.me handles information you send through this site.
Updated 13 August 2026
Who we are
This website is the public site for Velociti. Current contact for site and Enterprise inquiries is WonderWave Technologies at marco@velociti.me and +852 9880 5017.
What this site collects
The Alpha form collects an email address. Optional fields, if you choose to provide them, are name, role, intended workflow, interest (individual, team, or enterprise), operating system, hardware or GPU notes, and whether you are willing to join an observed onboarding session. The Enterprise form collects contact email plus qualification fields: organization type, one target workflow, systems involved, a sensitive-data category label, and the desired outcome. Do not submit credentials, regulated records, private keys, or confidential files.
How submissions are stored
Validated Alpha waitlist and Enterprise form submissions are emailed to WonderWave Technologies at marco@velociti.me. Form contents are never sent to analytics.
What this site does not collect
The website does not ask for product account passwords, API keys, or files from your Velociti workspace. Product work stays local to the Velociti application you run.
Analytics
If a privacy-respecting analytics provider such as Plausible is configured, this site may record page views and named funnel events (for example hero clicks or form start/submit). Those events do not include field values from forms.
Cookies
Essential cookies or local storage may be used to operate the site. There are no advertising cookies. Optional analytics, if enabled, follows that provider’s cookie policy.
Retention and requests
Waitlist and Enterprise qualification records are kept only as long as needed to operate Alpha cohorts and Enterprise conversations. To access or delete a submission tied to your email, write to marco@velociti.me.
Product data
Inside the Velociti application, prompts, context, responses, and thinking are kept with the project on your machine. Project retrieval, approved procedural memory, and chat memory stay separate. Work is not used as training data.