Workspace / Cookies & Tracking
Tuesday, November 17 LET'S BUILD SOMETHING

Cookies & Tracking

A place for people, projects, and possibilities.

Cookies & Tracking

Operator: zonify systems. Version: 2026-11-15-draft.

Draft - not a completed compliance statement

These documents require the operator's address, hosting and supplier details, retention schedule and legal review before being relied on as final policies. Items marked TO BE CONFIRMED are unresolved, not assurances that a practice or safeguard is already in place.

1. Essential session storage

Moozy uses a first-party cookie named apus_session for session handling, sign-in and security functions such as protecting forms against forged requests. The cookie carries a session identifier rather than your public profile or password. It is a browser-session cookie under the application's default settings; server-side session expiry and any hosting overrides are TO BE CONFIRMED.

The application sets HttpOnly and SameSite=Lax attributes; the Secure attribute depends on HTTPS being correctly detected. The operator must use and verify HTTPS on the deployed site. Blocking essential session cookies may prevent sign-in and other requested interactive functions.

2. Tracking is not limited to cookies

When social discovery is active, the application records qualified content views against signed-in accounts and uses preferences, follows, interests and votes for feed filtering or recommendations. This is server-side personal-data processing, even if it does not create a separate analytics cookie. Current member view tracking defaults on, with controls on the recommendations page and history controls.

Enabled profile analytics also records signed-in profile visits, qualified post impressions and category-only displayed search appearances, using the same view-tracking opt-out. It adds no third-party analytics service or analytics cookie. Named profile visits require an explicit optional identity-sharing choice, off by default, available in My analytics. Reports expire named visits after 90 days; daily deduplication is short-lived and lifetime totals are aggregate. Search text and searcher identities are not stored by this analytics feature. See the Privacy Notice for retention, maintenance and backup responsibilities.

An opt-out is not a substitute for valid consent where consent is required. The operator must assess this processing under data-protection law and assess any device storage/access under PECR. The Privacy Notice describes the draft purposes and unresolved lawful-basis assessment.

3. External embeds and services

Admin site-traffic statistics also count successful rendered HTML page requests, including guests and recognised bots. Daily non-bot visitor estimates use the existing session identifier or signed-in account ID to derive short-lived keyed tokens; no additional cookie or browser storage is introduced. This is a separate analytics use of session information, not automatically covered by its essential sign-in purpose. Raw IP addresses, full user agents and complete referrer URLs are not stored by the counter. Names require the separate, off-by-default Admin traffic privacy choice. Site aggregate hit counting is separate from the qualified-view opt-out. The operator must assess its lawful basis and applicable PECR consent or exemption conditions before deployment.

Displayed YouTube/Vimeo players and other enabled external integrations may contact third-party servers and may store or access information on your device. This can disclose your IP address, browser/device information and the page or video being used. A privacy-enhanced player URL does not by itself establish that no personal data or cookies are involved.

TO BE CONFIRMED: a deployment inventory of cookies, local storage, pixels, embeds, analytics, advertising, payment and other technologies, including providers, purposes and duration. The operator must verify the deployed site, not just the bundled application code.

4. Consent and exemptions

Optional local advert rotation uses uploaded images/GIFs, without adding advertising cookies or behavioural targeting. Visit-frequency selection is a random page-render decision and is not a record of a visitor's browsing history. Following an advert link contacts the destination site. Google AdSense settings are preparation only in this release: no Google advertising scripts or requests are loaded, including when Google mode is selected. They must remain paused until appropriate consent support and deployment review are complete.

Where a technology requires consent, it must be held back until valid consent is obtained, with a genuine refusal choice and an accessible way to withdraw. Essential storage/access and any other applicable statutory exemption must be assessed against its actual conditions; optional tools cannot simply be labelled essential.

This release adds information pages, not a cookie-consent manager or an automatic block on embeds. It does not claim consent has already been collected. Any consent-dependent integration must be disabled or correctly gated before use. Browser settings alone and continued browsing do not provide blanket consent.

5. Controls and questions

You can manage cookies through your browser and available account preferences. Clearing cookies signs you out but does not erase server-side account records, view history, messages or backups. Contact the operator using the details below for questions or data-rights requests.


Questions, complaints or data-rights requests: sales@zonify.co.uk.

YOUR COMMUNITY STARTS HERE

Welcome back.

Resend verification email

SHARE WITH YOUR COMMUNITY

Create a contribution

Share an update, introduce your work or tell your business story.

Contribution details

Choose a category of contribution and give it a clear title.

Additional details (optional)

Help people find your contribution and get in touch. These details are public.

Edit profile image

Choose a JPEG, PNG or WebP original (up to 25 MiB). Drag to position; zoom and rotate to fill the frame. Profile pictures fit 320 by 320 pixels; headers fit 1200 by 400 pixels. Only the cropped WebP is uploaded and stored.