Cookie Policy
BOTIFY BOT LTD · Last updated 22 September 2026
This policy explains how https://botifybot.vip uses cookies and similar technologies. BOTIFY BOT LTD, of Diamond Court, Water Street, Bakewell, DE45 1EW, United Kingdom, operates the site. Contact it.team@botifybot.vip or +44 7891 837264 if you have a question about this policy. The way personal data is handled more generally is described in the Privacy Policy.
1. What a cookie is
A cookie is a small text file that a site asks your browser to store and to send back on later visits to the same site. Cookies can remember a preference, keep a signed-in session, or, on other sites, recognise a browser for advertising. This site uses a cookie only for the first of those jobs. It does not keep you signed in, because the site has no accounts, and it does not recognise you for advertising.
Similar technologies include local storage, session storage, and pixels. This site does not write a tracking value to local storage or session storage, and it does not embed advertising or analytics pixels. The scripts on the site run in the browser to operate the menu, the form checks, and the layout. They do not send a copy of your browsing to a third-party analytics host.
2. The cookie this site sets
Name: bb_notice. Value: 1. Purpose: to record that you dismissed the short notice at the bottom of the page, so the same browser does not show that notice on every subsequent page. Duration: up to 180 days (the Max-Age attribute is 15552000 seconds). Path: / so that it applies across the pages of this site and not to a single document only. SameSite: Lax, so the browser will not attach it to cross-site requests in the way a SameSite=None cookie would. Secure is set when the page itself was loaded over HTTPS, which is the normal case on the public site. The cookie is not marked HttpOnly, because it is written by the page script rather than by a server response. It contains no name, no email address, and no message text.
The notice is dismissed when you use the Dismiss control. Until you do that, the cookie is not set by us. If you never use the control, nothing is stored for this purpose, and the notice remains available. The pages can still be read, and the contact form can still be used.
3. What we do not set
We do not set analytics cookies, advertising cookies, or social-media cookies. We do not use a consent-management platform that itself stores a string of vendor permissions, because there are no optional vendors to switch on. We do not use a cookie to remember which services you looked at, and we do not use a cookie to count unique visitors. Server logs, described in the Privacy Policy, are a separate matter: they are records on the server, not cookies in your browser.
Embedded content from other companies can set cookies. This site does not embed maps, video players, social feeds, or fonts in a way that sets a cookie from our own pages, except that the typefaces are requested from Google Fonts. A request for a font file is a connection to fonts.googleapis.com and fonts.gstatic.com. That connection is made so the type can be displayed. We do not use it as an analytics tool. If your browser or an extension blocks those hosts, the text still appears in a fallback typeface. If Google sets a cookie during a font request under its own rules, that cookie is Google’s, and Google’s documentation describes it. You can block third-party cookies in your browser and the site remains readable.
4. Why this cookie is used
The notice tells you that a preference can be stored and points to this policy. Showing it on every page after you have read it makes the pages harder to use, especially on a small screen where the notice takes space. The cookie is the minimum record that lets the interface stay out of the way. It is not used to decide what content you see, and it does not change the services described on the site.
Under the Privacy and Electronic Communications Regulations, a cookie that is strictly necessary for a service you have asked for does not always need consent. A preference that only remembers a dismissed notice is a limited case. We still explain it here, and we do not set it until you use the control. We do not bundle it with any other cookie. There is no “accept all” control because there is nothing further to accept.
5. Strictly necessary operation that is not a cookie
The contact form posts to contact.php. That request does not require a session cookie. If the message cannot be sent, the site may return you to the form with an error flag in the address. That flag is part of the URL, not a cookie. It is cleared when you move to a normal address. The script that checks the form in the browser does not write a cookie either.
Load balancing, TLS, and hosting equipment may use technical identifiers that never reach your browser as a first-party cookie of this site. We do not use those identifiers to profile visitors. If a hosting provider uses a cookie of its own to defend the site against abuse, that cookie is there to keep the service available. We do not add marketing tags to it. If we learn that a provider has started setting a non-essential cookie through our pages, we will remove that integration or update this policy before relying on it.
6. How long the cookie lasts
The Max-Age of 15552000 seconds is about one hundred and eighty days. After that, the browser should delete bb_notice and the notice can appear again. You can delete it sooner by the methods below. Closing the browser does not remove it, because it is a persistent cookie rather than a session cookie. Replacing your device, using a private window, or using another browser means the preference is not there, and the notice can show again. That is expected. The cookie is not copied between devices by us.
7. How to refuse or delete it
Do not use the Dismiss control if you prefer not to store the preference. The notice will remain, and you can still use the site. If you have already dismissed it, you can remove the cookie in the browser’s site settings for botifybot.vip. You can also block cookies for this site. Blocking cookies does not block the telephone number or the email address, which are ordinary links.
In most desktop browsers the control sits in the address-bar menu or in Settings, under privacy, under cookies or site data. Choose the site and delete bb_notice, or clear data for the site. On a phone the same control is usually in the browser’s settings rather than in our pages. We do not provide a second button that deletes the cookie from inside the page, because the browser already provides that control and a second mechanism would be easy to confuse with the Dismiss control. After deletion, reload the page if you want to see the notice again.
Private or incognito windows usually discard cookies when the window closes. If you dismiss the notice in a private window, the preference lasts only as long as that window’s cookie store. Extensions that block cookies will prevent the preference from being saved. The site is built to keep working in that case.
8. Third-party sites
Links in our pages, including the link to the Information Commissioner’s Office in the Privacy Policy, take you off this site when you follow them. A linked site can set its own cookies under its own policy. We do not control those cookies. Check the other site’s notice if you want to know what it stores. A link is not a request from us that you accept the other site’s cookies.
9. Legal basis and personal data
The value “1” is not, by itself, a name or an email address. Combined with server logs it could be argued that a cookie identifier relates to a device and therefore to a person. We treat the preference with the same care as other limited technical data. The lawful basis is legitimate interest in presenting a readable site after you have seen the notice, as described in the Privacy Policy. We do not use the cookie as a unique ID for analytics, so we do not match it to the name on a form.
You can object to that limited processing by deleting the cookie and not dismissing the notice again. Because the cookie never leaves your browser except to be sent back to this site with ordinary requests, deletion on your device ends the processing of that value. Requests for access, correction, or erasure of other personal data are handled under the Privacy Policy and should be sent to it.team@botifybot.vip.
10. Changes to this policy
If we add a cookie, change the name, the duration, or the purpose of bb_notice, or start using analytics or advertising, we will update this page and the date at the top before the new cookie is used for the new purpose. A change that introduces a non-essential cookie will be accompanied by a clear choice, not by a silent reuse of the Dismiss control. The Dismiss control will continue to mean only what this policy says it means.
11. Relationship to the other legal pages
The Terms of Service explain how you may use the website. The Terms and Conditions explain how paid or commissioned work is offered. Neither of those documents creates a cookie. If a sentence elsewhere on the site mentions a preference, this policy is the one that defines it. If there is a conflict about cookies, this policy wins on that subject.
12. Contact
Write to BOTIFY BOT LTD, Diamond Court, Water Street, Bakewell, DE45 1EW, United Kingdom, or email it.team@botifybot.vip. Please include “Cookie policy” in the subject if your question is about bb_notice, so that it is not mixed with a project enquiry.
13. A short statement of what you can expect
You can read the site without creating an account. You can dismiss one notice, and the browser will remember that dismissal for up to one hundred and eighty days. You can delete that memory yourself. You will not be followed around the web by an advertising cookie set by this company. You will not be asked to accept a list of analytics vendors. If that description ever stops being true, the date on this page will change and the notice will be rewritten so that it still matches the software.
The notice on the page is deliberately short. It says that the site stores one preference so the notice can stay dismissed, and that advertising and analytics cookies are not used. Those words are meant to match this policy. If you see a notice that claims something else, treat it as out of date and rely on this page, then tell us so we can correct the interface.
14. Browsers and devices we do not control
Some browsers delete unused cookies earlier than the Max-Age we set. Some privacy tools partition cookies so that a preference saved in one context is invisible in another. Some corporate networks strip cookies. In all of those cases the likely result is that the notice appears more often, not that extra data is collected. We do not respond to a missing cookie by setting a different identifier. There is no fallback tracker.
Assistive technology does not need the cookie. The notice is ordinary text and a button. If you use a screen reader, the button is available as a control named Dismiss. Refusing the cookie does not remove that control and does not hide the legal links in the footer.
15. What the page script does besides the cookie
The site script opens and closes the navigation on small screens, checks that the contact form has a name, an email address, and a message before it is posted, and, on a large screen, changes the layout as you scroll. Those behaviours use the document that is already on the page. They do not read bb_notice in order to decide which services to show, and they do not write a second cookie if the first one is missing. A visitor who blocks cookies still receives the same words and the same pictures.
The script also hides the notice when bb_notice is already present. That is the only read of the cookie. The value is compared with the string 1. Any other value is ignored and the notice stays. We do not store a timestamp inside the cookie, because the browser’s own expiry is enough. We do not store a random identifier, because we do not need to tell one browser from another for this purpose.
16. Organisations that manage browsers for their staff
If you visit from a workplace machine, your organisation may set cookie rules that override this site. A blocked cookie means the notice may stay on screen. That is your organisation’s choice, and we cannot see it from the server except as an ordinary page request. We do not ask you to weaken a workplace control in order to read the site. Corporate proxies may also log visits under your employer’s policy. That logging is not a cookie of BOTIFY BOT LTD, and we do not receive your employer’s internal logs.
17. A note on the address bar
Some pages add a query such as a version marker on a stylesheet, or an error flag after a form that did not send. Those are not cookies. They are part of the request for that page. They are not stored for one hundred and eighty days, and they are not sent to advertising networks. Clearing cookies is not required in order to clear a query string: loading the page without the query is enough.
18. Storage on shared computers
If several people use one browser profile, a dismissal by one person hides the notice for the others until the cookie expires or is deleted. That is a limit of a browser preference, not a record we keep of those people. Use a separate profile, or delete the cookie, if a shared machine should show the notice again. We cannot tell from our side whether a profile is shared.
19. Contact details repeated for convenience
Controller: BOTIFY BOT LTD. Address: Diamond Court, Water Street, Bakewell, DE45 1EW, United Kingdom. Email: it.team@botifybot.vip. Telephone: +44 7891 837264. Website: https://botifybot.vip. Cookie name: bb_notice. Related documents: Privacy Policy, Terms of Service, Terms and Conditions.