GlobeIce/Privacy

Privacy Policy

This is a GlobeIce-specific privacy overview written for the platform GlobeIce is actually building: a public hockey knowledge layer plus role-based operating systems for organizations and individuals.
Last updated: April 21, 2026
Accounts + workspacesPublic submissionsOfficial pagesCommerce readiness
Account and profile dataName, email, language preference, role, organization membership, account security state, and related workspace permissions.
Public contribution and editorial dataCorrections, source links, reports, moderation context, uploaded files, official page content, and governance notes tied to a submission.
Usage, device, and language signalsBrowser preferences, approximate region, cookies or local storage choices, sign-in state, and operational logs needed for reliability and abuse prevention.
Commerce and operational dataBilling capability state, organization purchase history, jobs or marketplace activity, and payment-related references when commerce is enabled.
Privacy Posture

Where privacy questions should go next

Privacy on GlobeIce is connected to real product behavior. These next routes help separate policy reading from account settings, support, trust, and governance.
Contact and rights routing
Start with Contact when a privacy issue has become a real support, correction, rights, or trust-routing problem rather than a reading question.
Terms and product rules
Open Terms when the privacy question overlaps with account access, organization authority, moderation, or commercial service behavior.
Follow and preferences
Open Follow Settings when the practical privacy concern is language, region, or personal preference rather than a legal interpretation.
Source and public trust
Open Sources when the privacy question touches public publication, official pages, provenance, or how submitted material becomes visible.
Policy Detail

How privacy works on GlobeIce

GlobeIce should align product behavior with governance promises. That means privacy is not only a legal page, but also a product design rule for language selection, permissions, moderation, payments, and public publishing.

1. Scope

This policy describes how GlobeIce handles personal data across the public site, Hockey OS workspaces, official GlobeIce pages, organization-managed official pages, Academy, Marketplace, Jobs, and related admin and governance tooling.

2. How GlobeIce gets data

GlobeIce receives data directly from users and organizations, from public source submissions, from platform usage, from authentication and security flows, and from trusted operational providers that help GlobeIce run hosting, identity, storage, analytics, moderation, and payments.

3. Why GlobeIce uses data

GlobeIce uses data to run accounts and workspaces, present public hockey information, route intake into the right governance lanes, personalize language and region defaults, prevent abuse and fraud, maintain canonical data quality, support payments where enabled, and improve product reliability.

4. Language, country, and locale handling

GlobeIce may look at browser language, previously stored language preference, and region or country signals to choose a default locale. GlobeIce should prefer a user-selected language once set. If no better signal exists, GlobeIce defaults to English.

5. Cookies and similar storage

GlobeIce may use cookies or similar storage for session continuity, login state, security, language preference, workspace context, product performance, and moderation reliability. GlobeIce should not use cookies only because they are convenient; they should map to an actual platform need.

6. Public pages, official pages, and submissions

If a user, club, federation, arena, or other organization publishes information on GlobeIce, that content can become publicly visible. Public contributions and moderation records may also remain in governance systems for audit, trust, quality, and legal reasons even after a page is changed.

7. Payments, Jobs, and Marketplace

When GlobeIce enables commerce, billing, subscriptions, payments, jobs, or marketplace workflows, GlobeIce may process transaction references, billing metadata, reporting context, trust signals, and safety events. Sensitive payment handling may be delegated to a payment provider such as Stripe instead of being stored directly by GlobeIce.

8. Sharing of data

GlobeIce may share data with service providers that help run the platform, with organizations where the user has a legitimate role or relationship, with moderation or legal counterparties where required, and with the public where a page, listing, profile, or official workspace is intentionally published.

9. Retention

GlobeIce retains data for as long as it is needed for platform operation, canonical integrity, moderation, contractual performance, fraud prevention, audits, or legal obligations. Retention can differ between account data, payments, moderation evidence, public history, and editorial records.

10. Security and governance

GlobeIce uses access controls, role-based workspace permissions, moderation queues, and audit-oriented admin tooling to reduce misuse. No internet service can promise perfect security, but GlobeIce should be built so that access, publication, and sensitive actions are visible and governable.

11. Your choices and rights

Depending on jurisdiction, users may have rights to access, correct, export, restrict, or delete personal data, and to object to some processing. GlobeIce should also provide practical account controls where possible, including language preference, follow settings, and organization role governance.

12. Policy changes

GlobeIce may update this policy as the platform grows. When the policy changes materially, GlobeIce should publish the updated language here and align product behavior with the updated policy rather than leaving a mismatch between words and implementation.
Operational note
GlobeIce still has product work ahead in language selection, payments, official pages, and organization tooling. The right answer is not to hide that complexity, but to document the intended privacy model now and continue closing product gaps so behavior matches policy over time.
For policy routing or platform issues, start with Contact.