Website analytics
Page-view telemetry and event-name-only conversion signals for public website pages.
Source: Vercel Web Analytics and the website analytics allowlist.
Privacy Policy
Privacy Policy
This policy explains what Valdris.ai collects through the public website, intake form, analytics layer, and private operator app.
Last updated: August 27, 2026
Data Collected
Current collection surfaces.
Valdris.ai collects only the data needed to operate the public website, qualify intake, run the private operator app, and keep the system reliable.
Advertising measurement
Page URLs, referring URLs, browser and device data, network request data, cookie identifiers, PageView events, and standard Lead events for confirmed contact submissions used for advertising attribution and campaign measurement.
Source: Meta Pixel on public /website routes unless the visitor has opted out.
Intake form
Name, work email, company, website, role, company type, team size, active work level, delivery pain, founder-router moments, handoff details, weekly workflows, system of record, work-start surface, OS Owner candidate, budget fit, authority path, timing, and selected lead path.
Source: Submitted by the visitor through /website/contact and stored in the private Neon Postgres lead tracker.
Private operator app
Authorized-user account context, source references, operating records, source-map links, sync status, and validation evidence needed to run the internal operator system.
Source: Private app use and approved source integrations.
Operational logs
Safe event type, route or surface, deployment target, control state, timestamp, and sanitized monitoring metadata.
Source: App health, intake, sync, deployment, and monitoring events.
Not Collected
No hidden form or replay layer.
The current website uses Vercel Web Analytics. Meta Pixel loads by default unless the visitor has opted out through the notice or Privacy choices. Valdris does not add submitted intake fields to custom analytics or advertising event parameters.
No session replay is installed.
No intake form fields are sent as custom analytics payloads.
No analytics event includes submitted name, email, company, or freeform intake text.
Valdris does not add intake form field values to custom Meta Pixel event parameters.
Valdris does not sell submitted intake information.
No payment information is collected by the current website.
No public client outcome materials are published by the current website.
Use
Why the data is used.
Data use is tied to intake, operating reliability, private app operation, and source-of-truth evidence handling.
Respond to intake submissions and qualification requests.
Route an inquiry into discovery, Build discussion, clarification, parked follow-up, or no-fit closeout.
Operate and secure the private operator app.
Maintain source maps, evidence trails, validation records, and approval logs.
Improve website usability through page-view and event-name-only analytics.
Measure advertising attribution and accepted contact conversions through Meta Pixel PageView and standard Lead events.
Debug reliability issues without storing raw secrets or submitted form bodies in monitoring metadata.
Sharing
Service providers and source systems.
Valdris.ai does not add submitted intake fields to custom analytics or advertising event parameters. Provider access is limited to hosting, analytics, advertising measurement, authentication, source systems, operations, and support.
Vercel
Hosting, deployment, runtime logs, and privacy-conscious web analytics for the public website and app.
Clerk
Authentication for private app routes when authentication environment variables are configured.
Neon
Private Postgres storage for validated contact intake and internal operator records.
Meta
Page-view, standard Lead, browser, cookie, and related technical measurement for advertising attribution and campaign performance through Meta Pixel.
Approved source and execution systems
Source-of-truth, execution, code, deployment, and evidence tracking when approved integrations are used.
Service providers
Infrastructure, security, operations, and support needed to run the website and private operator system.
Retention
Retention follows operating need.
Intake submissions are kept only as long as needed for qualification, follow-up, operating records, legal obligations, or dispute prevention.
Analytics data follows Vercel Web Analytics retention and processing controls.
Meta Pixel data follows Meta Business Tools terms, account settings, and retention controls.
Private operator app records remain in the relevant source system or app record while they are needed for operating truth, auditability, or approved source history.
Secrets and credential values are not intentionally stored in website analytics, monitoring metadata, internal tracking records, or public pages.
Requests
Access, correction, and deletion.
Request access to personal information submitted through the website.
Request correction of inaccurate submitted information.
Request deletion of submitted intake information when Valdris no longer needs it for a legitimate operating reason.
Opt out of Meta Pixel or resume it through Privacy choices.
Ask questions about how the current website or private operator app handles personal information.
Privacy request path
Send privacy requests to nicholas@valdris.ai or use the contact page.