Last updated: October 27, 2026.
Who operates this website
GURLY (gurly.blog) is operated by Optimum Solution Group, Bulgaria, which is responsible for the personal data processed through this website. For privacy questions or requests, email admin@gurly.blog.
Operator address: Pirotska street 11, ent. B fl.2, Burgas, 8000, Bulgaria.
Tax number: 207236182.
Information you provide
Email: if you contact us, we receive your email address, the content of your message, and any information you choose to include. We use this information to respond, resolve corrections or requests, and manage relevant correspondence. Please do not send sensitive health details, passwords, or payment information.
Comments: if you submit a comment, WordPress collects the information shown in the comment form, such as your name, email address, optional website, and comment. It also records an IP address and browser information to help identify spam and misuse. Your approved comment and display name can be visible publicly; your email address is not displayed as part of the comment.
Technical and security information
Our hosting and security services process technical information needed to deliver and protect the website, including IP addresses, requested pages, timestamps, and browser or connection information. Loginizer records failed sign-in attempts to help prevent unauthorised access. Administrative account information is used to run the website.
Cookies and optional services
WordPress uses cookies for sign-in and administration. If you select the comment form’s remember-me option, it stores your comment details in your browser. Our Cookie Policy explains these choices. We use a local, cookie-free counter to select the most-read story over the last seven days. After eight seconds of visible reading, it records only the article ID and the UTC time of the view. It does not store IP addresses, visitor identifiers, cookies, or browser storage, and does not send these statistics to a third-party analytics service. Repeat visits can count again; logged-in visitors and common automated crawlers are excluded. Records older than eight days are removed by a daily scheduled cleanup, which runs when WordPress receives traffic. We have not configured an external analytics platform or advertising pixel. Optional tracking must be reviewed and, where required, enabled only after consent.
Why we process information
We rely on legitimate interests to operate and secure the website, respond to correspondence, moderate discussions, and address corrections, while considering users’ rights. Where a feature requires consent, you can refuse or withdraw that consent. We may also retain information when necessary to meet a legal obligation or handle legal claims.
Service providers and external websites
Hosting, email, and security providers may process information necessary to provide their services. We may disclose information when required by law. If you follow a retailer or affiliate link, you leave GURLY and that provider’s own privacy practices apply. Those providers may process data in countries outside your own. Contact us if you need information about a particular provider or international transfer.
How long information is kept
Correspondence is kept for as long as needed to address the request and any related obligations or disputes. Approved comments and their metadata may remain while the relevant discussion is published, unless removed. Security records are retained according to their operational purpose and provider settings. Backups may retain earlier copies until they are replaced through the backup cycle.
Your choices and rights
Depending on the law applicable to you, you may request access, correction, deletion, restriction, portability, or object to certain processing. You may withdraw consent where processing is based on consent. Contact admin@gurly.blog; we may need proportionate information to verify your request. These rights can be subject to legal exceptions. You may also complain to an applicable data protection authority.
Updates
We will revise this notice when the website’s data practices change. The date at the top identifies the latest revision.