Privacy Policy
This privacy policy explains how MAVLINX handles inquiry data, project details, CRM setup information, workflow requirements, analytics/tracking data, AI-assisted workflow inputs, support records, and system delivery information.
MAVLINX installs business-control systems. That means some projects require practical operational data so we can diagnose the business gap, map the workflow, install the system, route actions, and support handover.
MAVLINX Privacy Policy explains how inquiry, project, workflow, and system data is handled.
What this Privacy Policy covers
This policy applies to data shared through MAVLINX websites, forms, inquiry routes, recommendation funnels, install requests, CRM setup requests, funnel requests, similar-system requests, support communication, and project delivery workflows.
Website and inquiry use
Applies when visitors submit forms, request recommendations, compare pricing, ask for installation, or share business requirements.
Project delivery use
Applies when MAVLINX uses project details to map workflows, configure systems, test routes, create dashboards, or support handover.
Third-party tool use
Applies where delivery involves tools such as WordPress, Elementor, forms, Google Sheets, Apps Script, dashboards, email, analytics, ads platforms, or AI tools.
Practical legal note
This page is written as an operational privacy policy for MAVLINX website and project use. It should be reviewed by a qualified legal professional for jurisdiction-specific compliance, especially for clients or users covered by specific data protection laws.
Information MAVLINX may collect
The type of information collected depends on how you interact with MAVLINX and what system you request.
Identity and contact information
Name, business name, email address, phone number, WhatsApp number, country, city, role, and preferred communication route.
Inquiry and recommendation data
Business type, current problem, urgency, budget range, system need, project stage, traffic source, and answers submitted through recommendation or request forms.
Project and workflow data
Scope notes, business processes, lead routes, CRM fields, staff roles, pipeline stages, forms, dashboards, automation requirements, content structure, and handover requirements.
Website, CRM, and system access details
Where necessary and approved by the client, MAVLINX may receive access details, account invitations, system screenshots, technical settings, plugin lists, form structures, or workspace details for delivery.
Analytics and tracking information
Website usage data, page visits, form source, campaign source, device/browser information, referral source, conversion events, and similar technical data may be collected through analytics or platform tools.
Communication and support records
Emails, form submissions, support requests, project notes, clarification messages, meeting notes, and delivery-related communication may be retained for service continuity and dispute prevention.
How MAVLINX uses information
MAVLINX uses information for practical business-system delivery, inquiry routing, project communication, support, and improvement.
To classify requests
Information helps identify whether the need is website installation, CRM automation, AI-assisted workflow, SEO classification, paid lead capture, dashboard setup, or custom system design.
To deliver systems
Project data is used to scope, build, configure, test, improve, and hand over MAVLINX systems according to the agreed scope.
To communicate
Contact details are used to respond to inquiries, confirm requirements, send updates, request clarification, provide support, and manage project communication.
To route leads and actions
Form and CRM data may be used to create routing logic, assignment rules, status fields, notifications, dashboards, or workflow views.
To improve performance
Analytics and campaign-related data may be reviewed to improve page clarity, form conversion, routing logic, tracking, SEO classification, or paid lead capture routes.
To protect delivery records
Project notes and communication records may be retained to confirm scope, track decisions, prevent confusion, support maintenance, and manage disputes.
Third-party tools and client-owned systems
MAVLINX often installs systems using client-owned or third-party infrastructure. Those platforms may process data under their own policies and settings.
Websites and forms
WordPress, Elementor, website forms, plugin tools, hosting providers, email services, and form submission systems may process visitor or lead data depending on the setup.
CRM and workflow tools
Google Sheets, Apps Script, dashboards, email notifications, WhatsApp links, and workflow tools may be used to support lead capture, status tracking, and reporting.
Analytics and advertising tools
Analytics, tracking pixels, search tools, ad platforms, campaign reports, and conversion tracking systems may collect technical and performance data.
AI-assisted tools
Where AI-assisted workflow support is used, inputs may be processed by selected AI tools or platforms depending on the agreed workflow and client approval.
Client-owned infrastructure
Where systems are installed inside client-owned accounts, the client remains responsible for user access, platform permissions, billing, platform compliance, internal staff use, and third-party account security unless a signed proposal states otherwise.
AI-assisted workflow data handling
MAVLINX may design AI-assisted workflow layers for intake classification, summaries, SOP-based drafting, response support, knowledge organization, and decision support.
Human review remains necessary
AI-assisted outputs should be reviewed by humans before business use, especially where client communication, legal, financial, operational, or sensitive decisions are involved.
Input control matters
Clients should avoid sharing unnecessary sensitive information in AI workflows unless the scope, tool, purpose, and risk have been reviewed.
No autonomous-business claim
AI-assisted operations are used as workflow support and decision support, not as a fully autonomous replacement for staff, management, or business judgment.
Access, updates, and deletion requests
Users and clients may request reasonable access, correction, or deletion of personal data held by MAVLINX, subject to legal, operational, contractual, tax, dispute, backup, or security limitations.
Access and correction
You may request correction of inaccurate contact or inquiry information where MAVLINX controls the relevant record.
Deletion requests
You may request deletion of certain data. MAVLINX may retain records where needed for project delivery, billing, legal obligations, dispute handling, fraud prevention, or legitimate operational records.
Retention period
Data may be kept for as long as needed to handle inquiries, deliver services, maintain records, provide support, comply with obligations, or protect legitimate business interests.
Client account data
Where data is stored inside client-owned tools, the client may need to manage access, deletion, retention, user permissions, and platform-specific controls directly.
Security and legal limits
MAVLINX uses reasonable operational care when handling data. However, no website, email, form, platform, AI tool, CRM, dashboard, hosting account, or internet transmission can be guaranteed as completely secure.
No absolute security claim
MAVLINX does not claim zero-risk data handling, guaranteed compliance, bank-level protection, military-grade encryption, or absolute platform security.
Shared responsibility
Clients are responsible for their own account access, passwords, user permissions, staff behavior, third-party platform settings, and compliance obligations.
Legal review required
This policy should be reviewed by qualified legal counsel for jurisdiction-specific privacy, data protection, contractual, and regulatory requirements.
Policy updates
MAVLINX may update this Privacy Policy as services, tools, workflows, legal requirements, or operational practices change. The updated version should be posted on this page with the latest revision date.
Use the route that matches your state before sharing project or system details.
I am unsure what data or system I need to share.
Start with the diagnosis route so your business gap is classified before unnecessary project detail is exchanged.
I have questions before submitting a form.
Review common questions about system scope, pricing, AI-assisted workflows, SEO, paid lead systems, and process boundaries.
I am ready to request installation.
Use the structured install request route when you understand the system type and want MAVLINX to review your project requirements.
Questions before sharing project data?
Start with clarification. Use the FAQs if you need general answers, or use Get My Recommendation if you need the correct MAVLINX system route before submitting detailed project information.