Privacy Notice
1. Controller and contact
Artur Minvaleev operates this website under the business name MINVALEEV and is responsible for the processing of personal data described here. For privacy questions or to exercise your rights, contact artur@minvaleev.com.
Artur Minvaleev
Am Römerhof 51
60486 Frankfurt am Main
Deutschland
2. Contact enquiries
When you send us an enquiry, we process your name and email address and, if supplied, your telephone number and message to handle your request and reply to you. Name and email are required fields. Telephone number and message are optional. The form does not provide a file attachment function.
Where your enquiry concerns a contract with you or steps you request before entering into a contract, we process the necessary data under Article 6(1)(b) GDPR. For other business enquiries, including where you act on behalf of a company, we rely on Article 6(1)(f) GDPR. Our legitimate interest is handling business enquiries and communicating with prospective clients and business partners.
Acknowledging this notice is optional. It is not consent to marketing and is not a condition for handling your enquiry. Analytics consent is separate from submitting an enquiry.
3. Email processing and recipients
The website sends your enquiry by email to artur@minvaleev.com, together with the submission time and the canonical address of the site page. Your email address is used as the reply address, not as the sender address. The form does not attach your IP address, browser user agent or referring URL to the email.
The website runs on Rocket.net hosting. WordPress passes the email through the installed WP Mail SMTP integration to the Google Gmail API; Google then handles delivery to the mailbox. WP Mail SMTP is the integration software on the website, not an additional mail-content relay through its OAuth callback service. The website host, Google as mail service, and the operator handling the mailbox process the correspondence. These services involve processing beyond the form itself; this notice does not promise that data stays only in the EU.
The form plugin does not retain enquiry content in WordPress or create a WordPress lead database. This does not mean that correspondence disappears after submission: email and replies remain subject to mailbox handling and retention. Nor does it mean that the hosting and mail infrastructure processes no technical connection data or logs.
A successful form response means that the mail transport accepted the enquiry, not that the recipient has read it. If the response is interrupted, the email may already have been accepted. The form does not automatically retry an uncertain submission.
4. Website operation and protection against misuse
Delivering this website requires the hosting infrastructure to process connection data, including the IP address used to request a page. We use website delivery and security functions to operate the site and protect it against misuse. The legitimate interests in reliable operation and protection against misuse are the basis for this processing under Article 6(1)(f) GDPR.
The contact endpoint checks the request origin, a form-specific request header and the JSON format. A sitewide rate limit uses an aggregate counter, an expiry time and a short lock. This limiter does not store your name, email, phone, message, IP address or a personal identifier. Expired limiter metadata ceases to be used; physical cleanup follows WordPress housekeeping. These checks are abuse protection, not proof of a visitor’s identity. The email form does not use an anonymous challenge nonce or an external CAPTCHA service.
5. Retention
We retain enquiry correspondence for as long as needed to handle and follow up the request. Where correspondence becomes part of a contractual relationship, the purpose of that relationship also determines what must be kept. Specific legal retention duties or the establishment, exercise or defence of legal claims may require keeping particular records longer. These criteria apply to the correspondence in the mailbox and any necessary copies; there is no single fixed retention period for every enquiry.
6. Privacy settings and analytics
When the operator enables Google Analytics 4, the Google tag is loaded only after you explicitly consent to analytics in the privacy settings. Rejecting analytics prevents this integration from loading the tag. Sending an enquiry does not grant analytics consent. Google processes browser and network data, including the IP address needed for the connection, device/browser information, cookie identifiers, page views and acquisition information. Processing may occur outside the EU.
Enhanced Measurement is enabled for usage interactions such as scrolling, outbound links, downloads, form interactions, history changes and supported embedded videos. These events are not proof of a successful enquiry. A separate generate_lead event is sent only when the website reports acceptance by the mail transport, with current analytics consent; this does not prove inbox delivery. Our integration does not attach form field values, email addresses, telephone numbers or request IDs to analytics events. Contact clicks send only the channel, not the address or number.
We provide a canonical page URL and a stable page title. Campaign labels are normalized and screened for common email, telephone, URL and identifier patterns; referral information is reduced to a public web origin without a path or query. This screening is limited: names or identifiers disguised as ordinary labels cannot reliably be recognized. Campaign labels must not contain personal data. Google’s own Enhanced Measurement may process link and interaction metadata independently; these controls are not a guarantee that all possible personal data is detected. Advertising storage, advertising user data, advertising personalization and Google Signals are not enabled by this integration.
The privacy settings store your choice in this browser’s local storage for up to 30 days. This is the lifetime of your consent choice, not Google’s data retention period. Analytics uses first-party GA cookies after consent. Reopen the privacy settings in the footer to change or withdraw your choice. Withdrawal stops this integration, removes its GA cookies and reloads the page; it cannot recall data already sent. If the operator has not enabled analytics, choosing a preference cannot enable it.
7. Your rights
Subject to the applicable legal conditions, you have rights of access, rectification, erasure, restriction of processing and data portability. Where processing is based on consent, you can withdraw it at any time with effect for the future.
Right to object: Where we process data under Article 6(1)(f) GDPR, you may object on grounds relating to your particular situation.
You also have the right to complain to a data protection supervisory authority, in particular in the Member State of your habitual residence, place of work or the place of the alleged infringement.
For these requests, contact artur@minvaleev.com. Deutsche Fassung.