Workspace / Privacy Notice
Tuesday, November 17 LET'S BUILD SOMETHING

Privacy Notice

A place for people, projects, and possibilities.

Privacy Notice

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. Who controls your data

zonify systems operates Moozy and is the intended controller of personal data processed for platform purposes. Contact sales@zonify.co.uk for questions, complaints or rights requests. The operator's address, full legal identity, applicable ICO fee registration and any required data protection officer or representative details are TO BE CONFIRMED.

We must handle personal data under the UK GDPR and Data Protection Act 2018, as amended, and other applicable law. These drafts do not certify compliance. Organisations using Moozy for their own contacts, staff, customers or transactions may be separate controllers.

2. Information the platform processes

  • Account name, email, password hash, account status, role, security/version records and optional verification information. Passwords are hashed, not intentionally stored as readable account passwords.
  • Profile biography, location, authorised website links, profile images and business details you supply.
  • Posts, projects, listings, comments, replies, reviews, ratings and uploaded media.
  • Follows, connection requests and introductions, connection status, blocks, notifications and private messages.
  • Saved items, preferences, interests, votes and qualified content-view history where social discovery is active.
  • Where profile analytics is enabled, signed-in profile visits, qualified post impressions, category-only search appearances, daily pseudonymous deduplication tokens, lifetime aggregate totals, and an optional visitor-identity sharing choice.
  • Admin site-traffic statistics: successful HTML page hits for members, guests and recognised bots; daily estimated visitors; page paths without query strings; referring hostnames; aggregated self-reported member locations; and separately opted-in recent member identities.
  • Security and operational records, including IP-related rate-limit identifiers, timestamps, audit events and hosting logs where collected by the hosting environment.
  • Where enabled, applications, quotes, orders, billing records, transaction references and payment-provider responses. Actual payment fields and supplier access must be checked before payment services are enabled.

Information comes from you, your interactions, other users who refer to or communicate with you, and enabled service providers. Do not upload unnecessary health, identity-document, financial, criminal-offence or other sensitive information. We must establish an appropriate legal basis and additional safeguards before intentionally processing special-category or criminal-offence data. The bundled application does not perform facial recognition on profile photographs; any new biometric use would need separate assessment and safeguards.

3. Purposes and proposed lawful bases

The operator must confirm and document the basis for each actual processing activity before finalising this notice. Agreement to terms is not blanket GDPR consent.

  • Contract: necessary account administration and delivery of the platform features or paid services you request, where genuinely necessary for that contract.
  • Legitimate interests: proportionate security, fraud prevention, moderation, service maintenance and professional-community operation, subject to a documented assessment of necessity and the impact on your rights.
  • Legal obligation: records or disclosures required by applicable tax, accounting, regulatory or other law; relevant obligations must be identified.
  • Consent where required: optional marketing, non-exempt device storage/access and other optional processing that requires it. Consent must be specific, informed, freely given and withdrawable, not bundled with service terms.

Personalised recommendations use signals such as follows, interests and votes; qualified views can affect which content is shown again. The platform provides preference controls for recommendations and view tracking. View tracking currently defaults on for members when social discovery is active; an opt-out is not proof of valid consent or another lawful basis. The operator must assess and, where needed, change that practice before relying on this notice.

Recommendation ranking is not designed to make legally or similarly significant automated decisions about employment, credit or access to essential services. Any new such decision-making needs a separate assessment, disclosures and applicable safeguards.

4. Public and restricted information

Published profiles, business listings, posts, uploaded public images, comments and reviews are publicly accessible and may be indexed by search engines. Public follower totals are visible beside names; the total is distinct from a published list of follower identities. Content-view history, account email, password hashes and private messaging are not public-profile fields by default.

Analytics excludes anonymous traffic and self-views and counts each signed-in viewer once per item per UTC day. Post and search-result impressions require at least half visibility for one second; profile visits require a visible page for one second. Post view totals are public, but profile/search analytics and drill-down reports are available only to the profile owner. Visitor names and profile links are shared only after the visitor explicitly enables the separate, optional identity-sharing setting, which defaults off. Other counted visits are anonymous in owner reports. Withdrawing this choice removes previous named visits from active analytics, preserving aggregate totals. Analytics does not store raw search text or searcher identities; it reports aggregate categories from qualifying displayed results. Existing hosting/request logs need separate review.

Restricted information may be accessed by authorised personnel where necessary for legitimate support, security, moderation, legal obligations or data-rights handling. Do not treat private messaging as end-to-end encrypted. Public copies made by others and search-engine caches may remain outside our direct control after removal.

5. Sharing, processors and international transfers

Site-wide hit counting is separate from profile analytics. Only platform administrators can view traffic reports. Successful HTML page requests count whether the requester is a guest, member or recognised bot; these are not verified people or all hosting requests. Bot classification is an estimate based on self-reported user-agent patterns. APIs, static/media requests, redirects and error pages are not included. No raw IP addresses, complete user agents, query strings, referring URL paths or device geolocation are stored by this counter, and no external geolocation service is contacted. Member profile locations are self-reported and may be inaccurate or outdated; guests and bots have unknown locations. A country or region is not inferred.

Recent named site visits require a separate optional admin traffic identity-sharing choice, off by default, available on Admin traffic privacy and in My analytics. A profile-owner identity-sharing choice does not enable admin traffic identity sharing. Turning admin traffic identity sharing off removes your named site visit from active statistics without altering aggregates. Site-wide aggregate hits are not stopped by the separate qualified-view tracking preference; the operator must assess the lawful basis and any consent or exemption requirements for this distinct processing before deployment.

We may need hosting, backup, email, payment and technical support providers to deliver enabled features. Public information is also shared with visitors, and information you send in messages or transactions is shared with its intended recipients. Necessary disclosures may be made to professional advisers, courts, regulators or law enforcement where justified by law.

TO BE CONFIRMED: hosting provider and country, backup locations, email/payment providers, other subprocessors, any analytics/advertising services, their roles and the actual categories of information they receive. Processor contracts and access controls must be verified. This draft does not claim that data is never shared, sold, used for advertising or accessed overseas when those facts have not been confirmed.

External YouTube/Vimeo videos and links may connect your browser to another provider, exposing information such as your IP address and device/browser information. Their own notices apply to their processing; this does not remove our duties when integrating them.

Local sponsored images and animated GIFs are hosted by Moozy and rotated without advertising profiles or new advertising cookies. They may link to an advertiser's external site, which receives requests when you follow the link. Publisher and slot IDs can be configured for future Google AdSense use, but this release does not load Google advertising; consent support and provider/deployment checks are still required before any such integration.

Transfers outside the UK require an applicable lawful mechanism and assessment where necessary. Actual destinations, adequacy decisions or safeguards, including relevant agreements, and how to request a copy are TO BE CONFIRMED. Hosting geography must not be assumed from the operator's location or domain.

6. Retention and deletion

We must retain data only for as long as justified by its purpose, legal requirements, disputes, security needs and other people's rights. The operator must complete a category-by-category retention schedule, deletion procedure and backup expiry/recovery safeguards before final publication.

  • TO BE CONFIRMED: active and closed account records; public content and media; connection/private-message data; moderation and audit records; hosting logs; billing/transaction records; rights-request records; backups and third-party copies.
  • Qualified view entries older than 90 days are pruned when new views are processed. This is event-driven cleanup, not a guarantee that every dormant account's records are automatically erased on day 90.
  • Named profile visits are retained for up to 90 days and never displayed after that period. Analytics deduplication tokens are retained only for their current UTC day. Pruning runs on analytics operations; operators must also schedule the provided daily analytics-maintenance command so physical deletion does not depend on continued activity.
  • Lifetime analytics totals contain no viewer identities and remain until the related target or owning account is removed, subject to the operator's retention review. Hiding content or deactivating an account is not removal. Analytics maintenance removes aggregates for removed targets. Restoring an analytics backup clears named visits and resets identity sharing off so old consent choices are not silently revived; visitors must opt in again. Historical backup copies still need a separate retention/erasure procedure.
  • Pending email-verification records are pruned after 24 hours when relevant registration/verification operations run; this is not a scheduled deletion guarantee.
  • Site traffic keeps up to 90 UTC days of daily totals and up to 100 opted-in recent members for no more than 90 days. Daily estimated visitors use rotating keyed tokens derived from signed-in account IDs or the existing session identifier; source IDs and session identifiers are not stored in these tokens. Tokens and their random key reset each UTC day. Estimates exclude recognised bots, cap at 2,000 tracked visitors per day and are marked as a lower bound when capped. Lifetime page/referrer/self-reported-location groups are bounded to 100 each, with additional labels counted under Other, and contain no individual visitor history. The daily analytics-maintenance command prunes expired traffic details even on an idle site. Restoring a backup clears traffic identities, identity-sharing choices and daily tokens, preserving aggregate counts; restoring can change the accuracy of same-day estimates. Backups and operator retention review remain separate responsibilities.
  • Account closure, suspension, hiding content and erasure are different actions. Deactivating an account does not itself erase its JSON records or backups.

Erasure may be subject to lawful exceptions. Where appropriate, deletion must also be communicated to processors or recipients, and retained backups must not silently reintroduce erased data into active use. Contact us to request closure or erasure; no automatic self-service account export/erasure tool is promised by this notice.

7. Security

The platform uses password hashing, session controls, permissions, CSRF protections, input validation, private storage and controlled media access. HTTPS, hosting permissions, backups, access review, incident response and any encryption at rest depend on the actual deployment and must be verified. No system is guaranteed completely secure.

Report suspected misuse promptly. The operator must assess breaches and notify the ICO within the applicable 72-hour period where notification is required, and affected people without undue delay where the applicable high-risk threshold is met.

8. Your rights and complaints

Depending on the processing and applicable conditions, you may request access, correction, erasure, restriction, portability or object to processing, including relevant legitimate-interest processing. You may withdraw consent without affecting the lawfulness of processing before withdrawal. Direct-marketing objections must be respected. These rights are not cancelled by accepting terms.

Send requests to the contact below, identifying the account and request. We may seek proportionate identity confirmation, not unnecessary sensitive documents. Rights requests are normally addressed within one calendar month, subject to lawful extensions or pauses; we must explain any applicable delay, refusal or permitted fee.

You may complain to us about data handling. The operator must facilitate complaints, acknowledge them within 30 days where required and investigate and respond without undue delay. You also have the right to complain to the Information Commissioner's Office and pursue available legal remedies.

9. Required information, age and changes

Account name, email and password are needed to create and secure an account; without them the account cannot be provided. Profile photographs and optional biography/website information are not compulsory. Additional information may be necessary for particular transactions and should be explained at collection.

Moozy accounts are intended for people aged 18 and over. Tell us if an under-age account or content raises a concern so we can investigate and take appropriate action. This policy statement does not itself implement age assurance or replace any applicable child-safety duties.

We must explain material changes to data purposes, bases, sharing, retention or transfers before the changed processing where required. The version above identifies this draft; the final notice requires a confirmed effective date and a record of previous versions.


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.