The public demo uses fictional records. Changes stay in this browser; no customer is contacted and no real workspace is changed.
Plain-language data boundaries
Privacy at MLPOINT
What happens when you visit the public site, try the sample, ask for pilot access, or enter an invited MLPOINT Event Command workspace.
A pilot access request stores the details you submit so MLPOINT can review and reply. It does not create an account, take payment, or add you to a marketing list.
Real operating records are accepted only after invitation. The product uses authenticated, role-based, workspace-scoped access.
Public website analytics
How the public site is measured
The public website uses Google Analytics and Google Tag Manager to understand page and action use.
Those services may use cookies or similar browser storage and may receive ordinary technical signals such as page, referrer, device, and broad interaction information. MLPOINT does not deliberately place your form name, email, company, or message into its conversion events.
Interactive demo telemetry
What the working sample records
The interactive demo may record a random browser session token and bounded non-content events such as a view or selected action; it does not send record content.
The editable sample state is fictional and stored in your browser. Resetting the sample clears that operating state. Do not paste real customer, staff, vendor, payment, health, or identity information into the public demo.
Pilot access requests
What MLPOINT keeps when you ask for access
A pilot access request stores the details you submit so MLPOINT can review and reply. It does not create an account, take payment, or add you to a marketing list.
The request can include your name, email, optional business/team, operation type, and optional note. MLPOINT stores the submission as an inquiry and uses an internal email alert to review and reply. Bounded technical details such as IP address, browser user agent, and anti-abuse status may be retained to protect the form and diagnose delivery failures.
Invited workspaces
When real operating records enter the product
Real operating records are accepted only after invitation. The product uses authenticated, role-based, workspace-scoped access.
A workspace contains the booking, event, preparation, run, and closeout information its authorised users enter. Access is issued through MLPOINT's controlled invitation process. During the founding pilot, MLPOINT confirms onboarding, support, retention, and offboarding expectations before real records are imported.
Gmail, Outlook, WhatsApp, payment collection, and automated customer messaging are not connected in the founding pilot.
Providers and retention
Who supports the service and how long records remain
MLPOINT uses hosting and infrastructure providers, an email delivery provider, Google's public-site analytics tools, and Supabase for invited Event Command workspaces. They process data only for the relevant hosting, delivery, measurement, or product function.
MLPOINT retains inquiry, security, and workspace records while needed for access review, delivery, support, dispute or security handling, and applicable legal obligations. Pilot retention and offboarding are currently managed with the customer rather than promised as an automatic deletion schedule.
Your choices
Ask before sharing something sensitive
Do not send passwords, payment-card data, government identity documents, or unnecessary sensitive personal information through the access form or public demo. Use the address below to ask what is appropriate for an invited workspace.
You may contact MLPOINT to request access to, correction or deletion of personal information associated with your inquiry or pilot. Some records may need to remain for security, contractual, or legal reasons.
Privacy contact
Ask a direct question.
Include the email address connected to your request or workspace so MLPOINT can identify the relevant record.