Skip to content

Privacy Policy

Effective date: November 6, 2026

This policy explains how BuildCostKit handles information when you use the website or contact us.

Who operates BuildCostKit

BuildCostKit, at https://buildcostkit.com/, is owned and operated by Anton Hladyshev, an individual based in Ukraine. In this policy, “we” means Anton Hladyshev as the operator of BuildCostKit.

For questions about this policy, your information, or a calculator, email contact@buildcostkit.com. You can also use our Contact form.

Calculator entries and site searches

Our calculators process your measurements, quantities, material choices and entered prices in your browser. The calculator code does not send those entries or results to our server, save them in a visitor account, or store them in cookies, local storage or session storage. Your browser may independently remember or restore values. Keep a separate copy of any result you need.

All calculators let you download a PDF summary of your last successful calculation. Our code creates the PDF in your browser without sending your entries, results or the file to our server or an outside service.

The downloaded file is saved on your device. Your browser can record the download, and your chosen folder, sync or backup settings may retain copies. You control those copies. Our export code keeps the calculation in page memory and does not add cookies, browser-storage records or a download history of its own. Loading the local PDF software still involves ordinary requests to our hosting server.

A site search works differently: its search term is sent to our server as part of the requested URL and can appear in request logs. Do not put passwords, contact details or other private information into a site search.

Messages you send us

The Contact form asks for your email address and message. Your name is optional. It does not accept attachments, sign you up for a newsletter, or send an automatic reply.

The form sends your name, if provided, and message to contact@buildcostkit.com through HOSTiQ’s authenticated SMTP service over TLS. Your email address is used as Reply-To so that we can answer you. The sender address and recipient are fixed to our contact mailbox.

The form code does not keep a copy of your message in the WordPress database, an application log or a retry queue. The delivered message and any reply remain in the email mailbox. If submission fails, the form returns your entries in the response page so you can correct them. On a successful submission, the fields are cleared.

If you email us directly, we receive the information you include and ordinary email headers. Please send only what we need to understand your inquiry. Do not send passwords, payment details, identity documents or sensitive personal information with an initial message.

Form abuse prevention

We use a hidden honeypot field, form-verification tokens and server-side rate limits to reduce spam and repeat submissions. No third-party CAPTCHA is connected.

The rate limiter uses a keyed HMAC of the network address supplied to the application by the server. Its private counter file stores that pseudonymous identifier, timestamps and hashes of submission tokens, not your name, email, message or the original network address. This is not a guarantee of anonymity: the identifier still lets the system recognise attempts from the same address.

Limits use a rolling one-hour window. Old timestamps and tokens are removed, and inactive address records older than one hour are cleared, when the next submission passes the form-verification checks. Records for an active address can remain while new attempts continue. There is no background job that guarantees physical deletion exactly one hour after an event.

Hosting, security and WordPress

HOSTiQ provides the hosting and email infrastructure. HOSTiQ has confirmed that the supplier for our service is Скуріхін Сергій Миколайович, a sole proprietor in Ukraine. Delivering and protecting a page involves processing a network address, requested URL, date and time, browser information, response information and, where supplied, a referring page. Requested URLs can include search terms and other query parameters.

HOSTiQ operates WebShield, part of Imunify360, to detect and limit suspicious automated requests. It can analyse IP addresses, HTTP headers, request patterns and frequency, and the results of security checks. It may run a JavaScript browser check or display a verification page. This is separate from the Contact form’s rate limiter.

HOSTiQ says its server sends technical data to CloudLinux cloud services. CloudLinux OS can send server identifiers and licensing information. Imunify360 can send other information to analyse security events.

The possible Imunify360 information includes:

  • events from ModSecurity and OSSEC logs;
  • hosted domains checked for reputation;
  • Anti-Bot verification information;
  • malware-scan results;
  • suspicious files sent for further analysis.

These security mechanisms may involve visitor IP addresses, usernames, requested URLs, browser information and HTTP request parameters. Such information is not necessarily anonymous. Which data are sent depends on the security and diagnostic mechanisms involved. The provider’s explanation and the product documentation do not establish that every listed category has been sent in connection with buildcostkit.com. Information analysed on the server is not necessarily the same as information transmitted to the cloud.

Visitors do not need a WordPress account to use the calculators. New comments, pingbacks and public registration are disabled. WordPress stores administrator account details and sign-in session records, including session expiry, network address and browser information, to manage access and security. Administration can also involve service requests for software updates and account-related resources, including profile images from Gravatar; that is separate from the ordinary visitor page.

Approved account-security notifications use HOSTiQ SMTP and are delivered to an operator-controlled mailbox at Google. This is administrative correspondence, separate from Contact submissions. The form does not automatically forward visitor messages to that mailbox. Other WordPress mail is restricted; password-reset links, Recovery Mode and update-result emails are currently disabled.

Cookies, browser storage and outside services

WordPress can use the session-storage item wpEmojiSettingsSupports to remember whether your browser supports certain emoji characters. It does not contain your calculator entries. Session storage is normally associated with a tab, although a browser may restore it. WordPress uses separate cookies for sign-in, login testing and administrator preferences when those features are used.

The wssplashchk cookie is used for WebShield’s browser security check. It is not an analytics or advertising cookie. HOSTiQ has not confirmed the exact lifetime or renewal behaviour of this cookie for our configuration.

BuildCostKit does not use Google Analytics or advertising. We do not load Google Fonts or use Elementor’s optional usage tracking.

The owner has verified the domain in Google Search Console using a DNS record. This verification did not install a visitor-tracking tag on the site. Advertising services are not active.

Links to manufacturer documents and other outside websites are ordinary links. If you follow one, that website receives the request and may process information under its own policy.

Why we use information and who receives it

We use inquiry information to understand and answer messages, investigate reported calculator issues, and keep relevant correspondence. We use request and security information to deliver the site, protect access, limit abuse and diagnose faults.

Where permitted by applicable law, we rely on our legitimate interests in running and protecting the site and answering inquiries, provided your rights do not override those interests. A legal obligation may require particular records. Sending a message is not consent to analytics or marketing.

Information is available to the operator and to the hosting, email and security providers needed for these functions, including CloudLinux cloud services used with Imunify360. We may disclose relevant information when required by law or when necessary to establish, exercise or defend a specific legal claim. We do not use inquiries for a mailing list or send them to advertising services.

HOSTiQ’s privacy policy describes how HOSTiQ handles information within its own scope. This policy explains how we handle data on BuildCostKit. For requests about your data on BuildCostKit, contact us using the address in the “Your choices and requests” section below.

HOSTiQ has told us that our hosting service and its hosting backups are located in a data centre in Lviv, Ukraine. This does not cover all cloud security processing. Citing CloudLinux documentation, HOSTiQ identifies Germany, Finland and Poland as possible European processing locations. These are examples, not a complete list or a confirmed route for our domain. CloudLinux’s published documentation also describes locations outside the European Union. We have not verified the exact cloud recipients or processing locations used for this account, and do not promise that all data stay in Ukraine or the European Union.

How long information is kept

Our routine correspondence policy is to delete an inquiry and its related replies within 12 calendar months after the last incoming or outgoing message in that conversation. This covers active inbox, sent mail, archive and trash copies, and any working export we control. It is a manual review policy; automatic mailbox deletion has not been configured. It is not a promise that all technical records and backup copies disappear on the same date.

We may keep only the relevant part longer if a specific dispute or legal claim makes that necessary, or if an applicable law or valid order requires it. The reason, scope and review date must be documented. This is not a blanket extension for every message.

HOSTiQ has confirmed these separate rules for our account:

  • SMTP/Exim logs: one month. They include sender and recipient addresses, message identifiers, delivery status and the subject. Addresses and subjects can contain personal information. Full message bodies and attachments are not kept in these logs.
  • IMAP/Dovecot logs: one month. They record technical connection, authentication and mail-session events rather than the contents of correspondence.
  • Standard web access logs: monthly records, generally covering the current and previous months. Automatic removal of the previous month’s archives at the end of each month is enabled for this account. These logs include IP addresses, URLs, HTTP methods, response codes and other request details. They do not contain POST bodies. This does not establish what every application, PHP or security diagnostic may record.
  • Apache error logs: archived without rotation; a maximum retention period has not been specified. cPanel’s recent-error view is not the complete archive.
  • PHP and WordPress error logs: no time-based rotation is currently configured for our site.
  • Local WebShield logs: HOSTiQ reports that these are stored on the server and rotated daily, retaining 52 archives, or approximately 52 days. This is an approximate local-log retention period, not a guarantee that all related data are deleted exactly after 52 days.

CloudLinux’s published Imunify Data Processing Addendum says that processing under the addendum ends when the main agreement expires or is terminated, or earlier if the processing is no longer needed to perform that agreement. The addendum gives a separate rule for Imunify360: files identified as containing personal data are deleted immediately upon identification. CloudLinux’s Clients Privacy Policy says that it securely deletes or anonymizes personal data when it no longer has a legitimate business need to process it.

These documents do not specify a fixed retention period for cloud security events, Anti-Bot checks, IP addresses or HTTP parameters. HOSTiQ could not confirm those periods for our account. The rule for identified files does not establish how long cloud telemetry is kept, and the approximate 52-day period for local WebShield logs applies only to those local logs.

Form counters follow the mechanism described above. Separate maintenance records contain task times and results, not Contact message bodies. Some have a size limit rather than an age limit. Private operator-created recovery and rollback copies also exist; their final retention limits are still being set, and no automatic cleanup of those copies is enabled.

HOSTiQ has confirmed that it keeps each backup for our server for 30 days and holds up to 10 recovery points. The limit does not cause backups to be deleted early. This is the retention period of each backup; deleting a file or message does not start a new 30-day period. Deleted data may remain in a backup that already contains them until that backup expires. HOSTiQ previously described the backups as covering account files, databases, mailboxes and private directories, with standard web access logs excluded. Our own recovery copies, active correspondence, logs and CloudLinux cloud data follow separate rules.

In response to our question about other technical or emergency copies of our web, mail and log data, HOSTiQ said there are no other copies outside its described backup process. This is the provider’s confirmation within that question, not an independent audit and not a statement that CloudLinux holds no copies.

Permanently deleting a message removes it from the active mailbox, but it can remain in earlier backups until every recovery point containing it is replaced. Technical mail-log records follow their separate retention rules. When recovering data, mail should be restored only if needed, and previously required deletions must be reapplied before a recovered mailbox returns to normal use. Deleting a private recovery copy from our account also does not immediately remove copies already captured in provider backups.

Your choices and requests

Contact us at contact@buildcostkit.com to ask what information we hold about your interaction, correct it, or request deletion. Depending on the law that applies, you may also have rights to restrict processing, object to certain uses, receive portable data, withdraw consent, or complain to a competent authority. In Ukraine, the data-protection authority is the Ukrainian Parliament Commissioner for Human Rights.

We may need proportionate information to verify a request and find the relevant records. Please do not send identity documents with your initial request. We will handle requests within applicable legal deadlines and explain any permitted refusal or limitation. We cannot promise that every record can be linked back to an individual.

BuildCostKit does not use analytics or advertising trackers. Browser privacy signals do not stop the technical processing needed to deliver and protect the site.

Children, security and changes

BuildCostKit is intended primarily for adults planning construction and home-improvement projects. It is not designed to attract children. If you believe a child has provided personal information, contact us so we can review it and take the action required by applicable law.

BuildCostKit uses HTTPS, restricted administrative access and private storage for configuration and backups. No method of transmission or storage is completely secure.

We will explain material changes here and provide additional notice or request consent where required.