MalixCode
Back to site

Privacy

Privacy policy

How MalixCode handles data from website visits, inquiries, referrals, and payment-details requests, and the privacy choices available to you.

Last updated: September 6, 2026

Privacy

Privacy policy

1) Overview

MalixCode presents web design and development services and accepts project inquiries. This policy explains how data is handled when you browse the website, use its project, quick-question, referral, or payment-details forms, or contact MalixCode directly.

2) Information collected

  • Basic technical data that may appear in hosting and security logs, including IP address, browser and device type, date, time, and requested URL.
  • Project inquiries: your name, whether you have an existing website, its URL if provided, preferred contact method, email address, phone number or Telegram contact, project description, and consent confirmation.
  • Quick questions: the topic, message, first name, preferred reply method, email address or international WhatsApp number, consent confirmation, language, and page path with query parameters and fragments removed.
  • Payment-details request data: name, email address, phone number, agreed package, and consent confirmation.
  • Supported campaign information: UTM parameters, ad click identifiers (GCLID, FBCLID, and MSCLKID), the page path, and the referring URL with query parameters and fragments removed.
  • Referral registration: your own name and contact details, your generated referral code, and the connection between that code and an inquiry submitted directly by the potential client.

Submitted requests are saved in protected server storage and accessed through a private administration area.

The payment-details request form does not collect bank-account, card, digital-wallet, or payment-account credentials.

3) How information is used

  • To review a request and reply through the selected contact method.
  • To review a quick question and reply through the selected email address or WhatsApp contact.
  • To contact a person who requested payment details and allow the MalixCode owner to personally confirm the intended recipient and exact payment instructions.
  • To create a personal referral link, contact the referrer about the program, and match the code to a project request submitted directly by the potential client.
  • To operate the site, prevent spam, and troubleshoot technical problems.
  • To measure website interactions and traffic sources, without personal form details, after you separately agree to analytics.

4) Browser storage and attribution

  • Your privacy preferences are saved in your browser’s local storage under a key specific to this website. They remain until you change them or clear your browser data.
  • The first and most recent recorded traffic sources are saved in browser session storage and sent with a form submission. Unsupported query parameters, query parameters and fragments in the referring URL, and recognizable email addresses or tokens are discarded.
  • The browser remembers whether the quick-question prompt has appeared for the current session only. Draft questions stay in the open panel’s memory and are not saved to browser storage.
  • Language is determined by the URL (/ or /ru) and is not stored separately in browser storage.
  • When Google Analytics 4 is configured and you have agreed to analytics, it may set _ga cookies. If you decline analytics or your browser sends a Global Privacy Control signal, the script does not load and any Google Analytics cookies accessible to this site are removed.

5) Service providers

  • Vercel provides hosting, site delivery, and technical logs.
  • Neon provides the protected lead database when the production database is connected.
  • Resend sends new-lead notifications to the configured service inbox.
  • Google Analytics 4 is used only when a valid measurement ID is configured, analytics is not disabled by configuration, and the visitor has consented.

Google Ads and Meta Pixel are not currently connected. Fonts are included with the website and served directly, so loading a page does not send a browser request to Google Fonts. MalixCode does not sell form data for money.

6) Referral submissions

The referrer enters only their own contact details and receives a personal link with a code. The potential client opens that link and submits the project form directly; the code is stored with their request so the referral can be verified. The referral form does not ask the referrer to provide another person's contact details.

7) How long information is kept

No fixed automatic deletion period is currently configured for leads. Requests are kept while needed to review the inquiry, continue the conversation, manage a project, or maintain the administrative record, and can be archived or deleted from the private admin area. Technical-log retention follows each provider's settings. Session attribution ends with the browser session; the privacy choice remains until changed or cleared.

8) Privacy choices and GPC

Optional analytics is off by default. You can accept, reject, or manage it through the privacy controls and reopen those controls from the footer. A Global Privacy Control signal always counts as a request to reject optional analytics.

Quick-question form consent permits processing the submitted question and contact details to reply. It is separate from optional analytics consent: rejecting analytics does not prevent form submission, and form consent does not enable analytics.

9) Security

The site uses HTTPS, private administrator sessions, server-side validation, a hidden spam-detection field, form submission limits, protected storage, and security headers. No system can guarantee absolute security. Collection is limited to the information needed for the purposes described here.

10) Data requests and updates

To request access, correction, or deletion, email team@malixcode.com. This policy is updated when forms, providers, analytics, or actual data handling changes.

The recipient and payment-instruction verification process is described in the Payment verification rules.