Cookie Policy.
Version 1.6 · Effective from 11 October 2026
English version
Version 1.6 · Effective from 11 October 2026
Document issued by VISUAL‑FIX DESIGNS S.R.L., tax ID (CUI) RO36987744, J30/53/2021, Str. Lucian Blaga, room no. 1, block CU4, apt. 6, Satu Mare municipality, Satu Mare County, Romania. Contact: support@boostetic.com
This policy describes:
- the cookies and other information stored on the user’s terminal equipment when visiting the boostetic.com site and when using the Boostetic applications (section 1);
- the way in which the Pulse Analytics tool, installed by our customers on their own sites, accesses the terminal equipment of their visitors (section 2).
1. The boostetic.com site and the Boostetic applications
1.1. Strictly necessary cookies
The following cookies and browser storage entries are strictly necessary for providing the service expressly requested by the user. Under art. 4(5) of Law No. 506/2004 (which transposes Article 5(3) of Directive 2002/58/EC, the ePrivacy Directive), they do not require consent and cannot be disabled without the service becoming non‑functional.
| Name | Purpose | Duration |
|---|---|---|
boostetic-consent and boostetic-consent-v (browser storage) | store the choice made in the cookie banner, its date and the version of the list of providers | 12 months; the choice is requested again on expiry or when a new marketing provider is added |
boostetic_consent (cookie) | the same choice, passed to the server, so that at payment no data is sent to Meta without consent | 6 months |
session cookie (*_sess, including boostetic_shell) | keeps you signed in to the app | until the browser is closed |
boostetic_sso and bx_sid | keep you signed in across the platform’s applications and associate the session with the user’s device (visible in the list of devices in the account) | 30 days, if the “Remember me” option is ticked; otherwise, until the browser is closed |
pulse_su | when the account is created, allows the email address to be confirmed directly through the confirmation link opened in the same browser (the account is active from creation); in another browser the password is requested, as protection against accounts created with another person’s address | 14 days |
1.2. Preferences
The following information is stored at the user’s choice, to keep the settings in the app. It is not used for tracking and is not passed to third parties.
| Name | Purpose | Duration |
|---|---|---|
boostetic_theme (cookie and browser storage) | the chosen theme (light or dark) | 1 year |
boostetic_last | opening the last application used from boostetic.com/app/ | 1 year |
browser storage, in the Pulse Analytics application: the background mode of the click maps (pulse_bgmode), the calibration of the maps (pulseCalib1), the menu state, announcements already shown, drafts of messages to support | keeping the settings and the text entered between pages | until the site data is changed or deleted; the calibration, one hour |
session storage, in the app (pulse_trail, pulse_errs, pulse_shell_seen) | the last pages opened and technical errors, attached to a message only if the user sends it from “Help” | until the tab is closed |
1.3. Statistics without cookies
Visits to the pages boostetic.com/pulse-analytics/ are measured with Pulse Analytics, under the same conditions as on our customers’ sites (section 2): without cookies and without identifiers stored on the user’s equipment. For this reason, the measurement does not depend on the choice made in the cookie banner.
1.4. Marketing cookies
Marketing cookies are placed only with the user’s consent, expressed through the “Accept all” button in the cookie banner or by enabling the “Marketing” category in the “Settings” window. If the user chooses “Reject all” or saves the settings without the “Marketing” category, the Meta pixel, the Google Ads tag and the TikTok pixel are not loaded and do not store any information.
| Name | Purpose | Duration |
|---|---|---|
Meta Pixel (_fbp, _fbc) | measuring the effectiveness of our advertising campaigns on Facebook and Instagram | up to 90 days |
Google Ads tag (_gcl_au, _gcl_aw) | measuring the accounts created and the subscriptions paid as a result of our ads on Google, on the Pulse Analytics pages and, after a subscription is paid, on the payment confirmation page in the app; _gcl_aw stores the ad click identifier, only if the user reached the page from a Google ad | up to 90 days |
TikTok pixel (_ttp, _tt_enable_cookie, ttcsid, ttcsid_*) | measuring the visits and the accounts created as a result of our ads on TikTok, on the Pulse Analytics pages; ttclid (the ad click identifier) is read from the address of the page only if the user reached the page from a TikTok ad | _ttp and _tt_enable_cookie: up to 13 months; ttcsid: up to 30 minutes of inactivity |
The Google Ads tag is configured without personalised ads: the data is not used for remarketing lists or for displaying personalised ads, and the user’s email address is not sent to Google. Google Ireland Limited may also read or place its own cookies on its domains (for example google.com), according to Google’s policy on advertising technologies (policies.google.com/technologies/ads).
The TikTok pixel sends to TikTok only the visit to the pages and the creation of the account, without the email address, the phone number or other data entered in the sign‑up form (the automatic matching of this data is disabled). TikTok Technology Limited (Ireland) processes it according to TikTok’s privacy policy (tiktok.com/legal/privacy-policy-eea).
Consent can be withdrawn at any time, as easily as it was given, from the “Cookie settings” button in the footer of the pages. When consent is withdrawn, the _fbp, _fbc cookies, those with the _gcl_ prefix and those of the TikTok pixel (_ttp, _tt_enable_cookie, ttcsid) are deleted, and the Meta pixel, the Google Ads tag and the TikTok pixel are no longer loaded.
2. Pulse Analytics on our customers’ sites
2.1. No cookies
Pulse Analytics does not place cookies and does not store on the visitor’s equipment any identifier of the visitor. The script does not use the document.cookie function.
Visitors are counted through a temporary identifier, calculated on our servers from the IP address, the browser data and a random value that changes and is deleted daily. After 24 hours, the identifier can no longer be recalculated, not even by us. The identifier does not allow the visitor to be tracked across sites or from one day to the next.
2.2. Information stored and read on the visitor’s equipment
The opt‑out marker. Only at the visitor’s express request, by accessing a page with the parameter ?pulse_optout=1, the marker _pulse_optout is stored in the browser’s storage, which stops the measurement on that device. The marker is deleted by accessing a page with the parameter ?pulse_optin=1. At every visit, the script checks whether this marker exists, so that the visitor’s choice can be respected. The script does not read and does not store any other information on the visitor’s equipment.
Browser signals. The script checks the “Do Not Track” and “Global Privacy Control” signals. If either of them is active, as well as in the presence of the opt‑out marker, Pulse Analytics sends no information: no visit, no click, no session recording and no order, and the A/B tests show the original variant without sending data.
Technical data. For statistics, the script sends the data that the browser makes available to any web page: the size of the screen and of the window and the browser language.
2.3. Visitors’ consent
The only operations of access to the visitor’s terminal equipment are the storage, at the visitor’s request, and the reading of the opt‑out marker, as well as the reading of the “Do Not Track” and “Global Privacy Control” signals. These operations are strictly necessary to respect the choice expressed by the visitor and fall under the exemption provided in art. 4(5) of Law No. 506/2004 on the processing of personal data and the protection of privacy in the electronic communications sector, which transposes Article 5(3) of Directive 2002/58/EC. For Pulse Analytics to work, the visitor’s consent is not required under these provisions.
The Customer, as the controller of the site, has the obligation to inform visitors about the use of Pulse Analytics in its own privacy policy. A model text is available in the Compliance Guide for Customers. The assessment of the obligations incumbent on it as controller belongs to the Customer.
The above concerns Pulse Analytics only. Other tools installed on the Customer’s site (for example Google Analytics or the Meta pixel), which store or access information on the visitor’s equipment, may require the visitor’s consent, according to the rules applicable to those tools.
3. Changes
Changes to this policy are published on this page, indicating the version and the date of entry into force. Significant changes are also communicated by email to the account holders.
Let's talk about your project.
Whether you have a question, a brief or just an idea, we're happy to listen. The first meeting is free: together we'll work out the real problem and the right way to reach your goal.
Email us at support@boostetic.com or use the form. We reply within 24 hours.
Message us on WhatsAppThanks! Your message is on its way. We'll get back to you as soon as we can.
Something went wrong while sending. Please write to us directly at support@boostetic.com.