1. Purpose of This Policy
This Cookie Policy explains how Activity Habits, available at activityhabits.info, uses cookies and similar browser storage. It describes essential functions, preference choices, optional analytics, retention and the controls available to visitors. The policy should be read with the Privacy Policy, which explains broader handling of personal information.
A cookie is a small text record stored by a browser. Similar technologies include local storage, session storage and server-side session identifiers. These tools can remember a choice, maintain form security, support navigation or provide aggregated information about website performance.
2. Consent Model
The website presents a fixed cookie banner with three choices: Accept All, Partial and Functional. Accept All permits essential, preference and analytics categories. Partial opens a preference panel so that optional categories can be selected. Functional limits storage to items needed for core operation and the record of that choice.
Optional storage must not be activated before the visitor makes an affirmative choice. Closing the preference panel without saving does not count as consent. A visitor can change the decision by clearing site data in the browser and returning to the website. Where a dedicated preference control is later added, it may provide the same function without requiring browser clearing.
3. Essential Cookies and Storage
Essential items support functions requested by the visitor or required to deliver the website securely. They may remember the cookie choice, maintain a server session, create a contact-form security token, distribute traffic, detect abuse and preserve basic accessibility behaviour. The website cannot offer the same secure form and consent experience without these items.
Essential storage is not used to build advertising profiles. A session identifier normally expires when the browser session ends or after a short period of inactivity. A consent record may remain longer so that the banner does not return on each page. Security logs may contain a limited identifier under the retention periods explained in the Privacy Policy.
4. Preference Cookies
Preference storage remembers optional interface choices. Examples could include a saved reading preference, an accessibility setting, a selected content view or a language choice if the website later offers those features. At present, the main preference is the visitor’s cookie selection itself.
Preference items are not intended to identify a visitor by name. They may still be personal information when combined with technical identifiers, so they are handled according to the Privacy Policy. A visitor may refuse these items and continue to read the public content.
5. Analytics Cookies
Analytics tools may be introduced to understand aggregated page use, device categories, broad location, navigation paths and technical performance. Such tools would be configured to reduce data, avoid unnecessary identifiers and respect the consent choice. Activity Habits does not currently require analytics storage for the contact form or ordinary page reading.
If analytics are enabled, the provider, purpose, duration and relevant transfer information should be added to the cookie register below before deployment. Analytics data should not be used to make medical inferences, to deliver personalised advertising or to evaluate an individual reader’s health.
6. Cookie Register
| Category | Purpose | Typical duration | Choice required |
|---|---|---|---|
| Essential session | Contact-form security and basic session continuity | Session or short inactivity period | No, strictly necessary |
| Consent record | Remember Accept All, Partial or Functional | Up to 12 months | No, needed to store the choice |
| Preferences | Remember optional interface settings | Up to 12 months | Yes |
| Analytics | Aggregated audience and performance measurement | Provider-specific, no longer than necessary | Yes |
The register describes categories rather than naming a third-party analytics provider because no provider should be activated until its configuration, contract, retention and transfer safeguards have been reviewed. The deployed register must be updated if the implementation changes.
7. Third-Party Content
The website uses locally stored photographs, logos, styles and scripts. Fonts may be requested from a font service when the browser loads the stylesheet. A font request can reveal technical information such as the internet protocol address and browser headers to the provider even when it does not place an advertising cookie. Deployment teams should review whether fonts will be served locally or through an external service and update this Policy when necessary.
External links do not automatically set cookies through activityhabits.info; however, the destination may use its own technologies after a visitor follows the link. Activity Habits does not control the destination’s choices. Visitors should read the external service’s notice before interacting with it.
8. Browser Controls
Most browsers allow users to view, delete or block cookies and local storage. Controls are usually found under privacy, security or site-data settings. Blocking all storage may prevent the cookie choice from being remembered and may interfere with the secure contact form. Private browsing modes commonly delete storage when the session closes.
Browser “Do Not Track” signals do not have a single legally standardised meaning. Where a consent signal is recognised by applicable law or the deployed consent platform, Activity Habits should respond as required. The website will not interpret the absence of a signal as permission for optional analytics.
9. Retention and Security
Cookie durations should be limited to the shortest period suitable for the stated purpose. Session items should expire promptly. Consent and preference records may remain for up to twelve months unless a shorter period is configured. Analytics retention, if introduced, should be documented and reviewed regularly.
Cookie values should avoid plain-text contact details or message content. Security controls may include secure and HttpOnly attributes for server cookies where appropriate, SameSite restrictions, encrypted transport, limited script access and periodic review. Local storage used by the consent interface should contain only the selected category and a date or version value.
10. Changes and Contact
This Policy may change when the website adds, removes or reconfigures a technology. The update date at the top of the page indicates the current version. Material changes that require a fresh choice should cause the banner to appear again.
Questions about cookies can be sent to [email protected], telephoned to +48 22 000 00 00, or posted to ul. Przykładowa 10, 00-001 Warsaw, Poland. The address and telephone number displayed on this project are placeholders and must be replaced with verified business details before public launch.