Privacy
Privacy Policy
A lightweight privacy notice for MardesOS soft launch, Request Access submissions, and pilot-stage lead handling.
Last updated: August 11, 2026.
Early-stage policy scope
This Privacy Policy is an early/pilot-stage policy for the MardesOS public website and soft-launch request flow. It explains current handling practices and may be updated before full public launch.
This page is not formal legal advice and does not claim regulatory certification, enterprise audit completion, or a completed production legal program.
Information we collect
When you use the Request Access or contact flow, we may collect the information you submit, such as name, email address, phone number, messaging preference, country, company, selected plan, source page, consent status, and your message.
The website may also receive basic technical request information through normal hosting and security logs.
How we use submitted information
Submitted information is used for lead follow-up, onboarding review, support or contact handling, and soft-launch planning.
Submitted lead data is not displayed publicly on the MardesOS website, and we do not sell submitted lead data.
Website analytics and your choice
On the canonical production website, MardesOS uses Google Analytics 4 to understand website usage only after you select Accept analytics. Depending on your browser and settings, this measurement may process technical usage data such as page URLs and titles, referrer information, browser or device details, and interactions with the website, and may use first-party analytics cookies or similar storage.
You can reject analytics when the preference notice appears or change your decision later through Analytics preferences in the website footer. When analytics is undecided or rejected, MardesOS does not load the Google tag. Advertising storage, advertising user data, and advertising personalization remain denied in this implementation.
MardesOS does not intentionally send submitted lead-form fields or personally identifiable information to Google Analytics. Campaign parameters and website URLs should not contain names, email addresses, phone numbers, or other personally identifiable information.
Server-side handling and pilot storage
Request Access submissions are handled by a server-side API and stored through server-side database access. The public website does not provide a public lead listing endpoint.
During the pilot, the temporary lead-storage target may be a non-production Supabase environment. This arrangement should be reviewed before production customer onboarding expands.
Payments and checkout
Payment checkout is not active yet. PayPal references on the website are visual/manual-payment readiness wording only and do not create an automated checkout, subscription, or payment collection flow.
Deletion and contact requests
You can request deletion or follow-up about submitted information through the Contact or Request Access channel. During the pilot stage, requests are handled manually.
Because this is an early-stage website, final privacy operations and response timelines may be updated before full public launch.