| Field |
Details |
| Company |
Brownbricks Limited, trading as Jamango |
| Company number |
706319 |
| Registered office |
The View Office Space, The View, Malahide Marina, Malahide, Dublin K36 CX99, Ireland |
| Websites and services |
jamango.io, game.jamango.io, Jamango games, creator tools, accounts, multiplayer services, community features, and partner-distributed Jamango experiences |
| Contact |
[email protected] for privacy requests; [email protected] for legal notices; [email protected] for account or product support |
1. Who We Are and What This Policy Covers
Brownbricks Limited, trading as Jamango ("Jamango", "we", "us", or "our") is the controller of personal data processed through Jamango unless another notice says otherwise. This Privacy Policy explains how we collect, use, share, retain, and protect personal data when people use Jamango websites, games, accounts, creator tools, multiplayer infrastructure, public profiles, community features, support channels, and related services.
This policy also covers Jamango games or experiences made available through distributor websites, embedded players, or similar distribution channels. Those third-party channels may separately collect information under their own terms and privacy policies when you use their sites, apps, SDKs, advertising tools, or account systems.
Jamango is currently an alpha-stage product. That means our features, integrations, publishing flows, moderation systems, analytics, and creator tools may change. If a change materially affects how we process personal data, we will update this policy and, where required, give additional notice or ask for consent.
2. Privacy Contact and Data Protection Requests
Jamango has a privacy lead / data protection contact for privacy questions and data rights requests. You can contact us at [email protected] or by writing to the registered office above. We will publish details of a formal Data Protection Officer if Jamango is required to appoint one or chooses to appoint one.
When you make a request, we may need enough information to confirm your identity, understand the account or content involved, and protect other users. For example, we may ask for your Jamango username, the email linked to your account, relevant world or report IDs, or evidence that you are the parent or guardian of a child user.
3. Quick Summary
- We collect account, profile, device, gameplay, creator, support, moderation, and analytics information needed to run Jamango.
- Public profiles, worlds, assets, leaderboards, social links, creator pages, and other user-generated content may be visible to other users and to visitors.
- Jamango uses analytics and diagnostics, including first-party analytics, PostHog, Google Ads conversion measurement, cookies, local storage, and limited session diagnostics where enabled, to understand and improve the service.
- Jamango supports Discord connections and community features. If you connect Discord, use Discord rewards, or appear in Jamango community surfaces, Discord-related identifiers, roles, membership signals, avatars, usernames, or account-linking data may be processed.
- Jamango games may be distributed through distributor websites, embedded players, or similar channels. Those channels may collect their own device, advertising, analytics, fraud-prevention, and gameplay data.
- Jamango does not currently ask users to provide their age, so we may not know a user's age unless they tell us or we otherwise become aware of it. At this stage, Jamango does not provide a child-specific account or parental consent flow. Users under 13 must not create a Jamango account, publish content, use chat, add social links, connect Discord, or use other interactive/community features without parental consent.
- You can request access, deletion, correction, objection, restriction, portability, withdrawal of consent, or other applicable privacy rights by contacting [email protected].
4. Information We Collect
Account and Login Information
- Username, email address, email verification status, account ID, hashed authentication credentials, session cookies or tokens, password reset and email-change metadata, role, permissions, feature flags, account status, ban or mute status, and account creation or login timestamps.
- Guest account identifiers, generated usernames, temporary account details, platform-specific guest tokens, and gameplay or editor activity linked to a guest session. If you convert or link a guest account, previous guest activity may become associated with the registered account.