1. Scope
This Cookie Policy applies to HoneyNotify-controlled public website pages, the hosted account dashboard, and the restricted blog administration area. It should be read with our Privacy Notice. A customer website or application that uses a HoneyNotify SDK is controlled by that customer and should provide its own information about cookies, Web Push, local storage, and consent.
2. Cookies and similar technologies
A cookie is a small text value stored by a browser and returned to a website. Similar technologies include local storage, service-worker storage, cache entries, and browser push subscriptions. Some are strictly necessary to provide a requested feature, while others may support preferences, measurement, or advertising.
Server access logs are not cookies. Like most internet services, HoneyNotify infrastructure may record ordinary request information such as an IP address, timestamp, requested path, user agent, response status, and security events. Our Privacy Notice explains how we handle personal information.
3. Public website
HoneyNotify uses an audience-measurement script served from track.ispspeedtest.net across its public website, blog, documentation, application, status, and support pages. When a page loads, the script sends the page URL without its fragment, referring URL, and screen resolution to that host. The current script does not read or set cookies or browser local storage, and it is not used for third-party advertising or cross-site advertising profiles.
The measurement script is currently configured with data-dnt="false", so a browser's Do Not Track setting does not prevent that page-view request. If we introduce optional cookies or other storage that requires consent, it will remain disabled until the required choice has been made and this policy and the available controls will be updated.
4. Strictly necessary account and administration cookies
The authenticated HoneyNotify dashboard uses a session cookie to keep a user signed in, associate requests with the correct session, and support protections against unauthorised account actions. The restricted blog administration area also uses a session cookie for authorised staff. These cookies are necessary for the user-requested login and administration functions.
Session cookie names may vary by environment. They are configured with protections appropriate to their context, including HttpOnly, SameSite restrictions, and Secure transport in production. Browser session cookies normally expire when the browser session ends, but the corresponding server session may expire earlier or be invalidated at logout for security reasons.
Blocking these cookies will prevent login or cause authenticated features to stop working. HoneyNotify does not use these essential session cookies to advertise to users or track them across unrelated websites.
5. Web Push, service workers, and customer properties
Web Push requires the browser to maintain a push subscription and service-worker state. A customer implementation may also store a HoneyNotify device identifier so it can update the correct registration. These technologies provide the notification feature requested through that customer's website; they are not used by HoneyNotify to follow a recipient across unrelated customers.
The HoneyNotify customer determines why Web Push is offered, when permission is requested, and what notices or consent controls appear on its property. Recipients can manage notification permission and site data through their browser settings. Removing browser storage or permission may disable notifications and may require the device to register again.
6. External resources and linked services
Public pages request font files from Google Fonts, and measured HoneyNotify pages request the analytics script from track.ispspeedtest.net. These connections provide ordinary network information such as IP address and user-agent details to the relevant server, but HoneyNotify does not use them to place a HoneyNotify advertising cookie. The payment journey and other linked services may operate on separate domains and apply their own cookie practices.
Following an external link or using a third-party service is subject to that provider's information and controls. HoneyNotify will not describe a third party's cookie as essential to HoneyNotify unless it is genuinely required for the service the user requested.
7. Your choices
Most browsers allow users to inspect, block, or delete cookies and site data, clear service-worker storage, and change notification permissions. Browser help documentation explains the available controls. Blocking all cookies can prevent the dashboard and other authenticated services from functioning.
Where an optional HoneyNotify technology requires consent, consent may be withdrawn as easily as it was given. Withdrawal does not make earlier lawful processing unlawful. A privacy or deletion request should be made through the support details in the dashboard; a browser “Do Not Track” signal is not an authenticated account request.
8. Changes and contact
We may update this policy when browser technology, our services, or legal requirements change. The effective date above identifies the current version. Material changes will be highlighted through an appropriate website, dashboard, or account notice where practical.
Questions about this policy or the identity of the relevant HoneyNotify contracting operator can be sent through the support details shown in the dashboard. Do not include passwords, API keys, provider credentials, or unnecessary recipient information.