Jamango Privacy Policy#

Last updated: 10 November 2026

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, playjamango.com, Jamango games, creator tools, accounts, multiplayer services, community features, and partner-distributed Jamango experiences.
Contact: support@jamango.io for support, privacy requests, and legal notices.

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 support@jamango.io or by writing to our registered office. 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 first-party analytics and PostHog, with cookies and local storage, to understand and improve the service. Jamango does not use advertising trackers and does not record play sessions.
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 is played by people of all ages and is designed with that in mind: guests can play without giving any personal details, chat is moderated by AI agents and human moderators, there is no private messaging, and every player can report another player. See section 10.
You can request access, deletion, correction, objection, restriction, portability, withdrawal of consent, or other applicable privacy rights by contacting support@jamango.io.

4. Information We Collect#

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.
Discord account connection data if you choose to sign in with or connect Discord, such as Discord account ID, account-linking status, OAuth tokens or scopes handled by our authentication system, server membership signals, role membership for rewards, and other integration metadata.
If you play through a distribution platform account, such as a CrazyGames account, the platform user ID and username that the platform shares with us.

Public profile data such as username, avatar or profile image, cover image, about-me text, social links that you choose to add, badges, level, XP, followers, following, joined date, world plays, tokens or balances shown in the product, and public creator activity.
World pages, creator pages, thumbnails, descriptions, tags, likes, play counts, published status, remix links, collaborators, package listings, and other public or semi-public Jamango surfaces.
Community or social activity, including Discord-linked community activity where Jamango uses Discord identifiers, usernames, avatars, role or membership signals, and account-linking data in Jamango community features.

Creator Content and Gameplay Information#

Worlds, world versions, game logic, code, scripts, resource bundles, uploaded files, images, audio, textures, models, thumbnails, templates, packages, assets, avatars, game settings, experiments, world metadata, remix relationships, collaboration permissions, and creator workflow data.
Gameplay data such as matchmaking requests, multiplayer sessions, server identifiers, player state, persistent world or account data created through Jamango APIs, leaderboard scores, ranks, challenge progress, rewards, badges, inventory, and other game or platform state.
Publishing, review, moderation, archive, removal, reporting, admin, and appeal data related to worlds, packages, accounts, chat, profiles, and other user-generated content.

Chat, Reports, Support, and Communications#

Chat messages sent in Jamango games where chat is enabled, including timestamps and usernames. Jamango may process chat for delivery, display, filtering, reports, moderation, safety, and abuse prevention.
Report data such as reporter account, reported user, category, description, reported message, surrounding chat-message snapshots, moderation notes, decisions, warnings, mutes, bans, unbans, and related timestamps.
Support requests, survey responses, feedback, emails, attachments, security reports, legal notices, and other communications you send us.

IP address, approximate country inferred from IP address, browser, operating system, device type, language, referring and exit pages, page views, click and navigation events, timestamps, session IDs, and security or fraud-prevention signals.
Gameplay, editor, and platform analytics, such as world creation, world views, card impressions, clicks, play and edit sessions, loading events, gameplay heartbeats, editor heartbeats, performance data, errors, and server activity.
Cookies, local storage, and similar technologies for login sessions, preferences, security, analytics, and service functionality.
Product analytics and diagnostic tools to understand crashes, performance issues, reliability issues, product flows, and usability problems. Jamango does not record play sessions (session replay). Users should not enter sensitive personal information into usernames, profiles, chat, worlds, or uploads.

Purchases#

If you buy tokens or other digital items, our payment provider processes your payment details. Jamango receives a record of the purchase, such as the item, amount, currency, time, and account, but not your full card details.

Information From Partners and Third Parties#

Authentication, account, and community data from Discord or other connected services you choose to use.
Referral, attribution, campaign, platform, language, loading, gameplay, fraud-prevention, advertising, or analytics signals from distributor websites, embedded-player partners, or similar services.
Operational data from service providers, such as email delivery status, hosting logs, content delivery logs, analytics reports, security alerts, and support tooling.

Jamango is a creator and gameplay platform with public and interactive features. Do not include your real full name, home address, school, phone number, private email, government ID, payment details, passwords, health information, biometric information, precise location, or other sensitive personal information in usernames, profiles, chat, worlds, thumbnails, images, scripts, packages, social links, reports, or support attachments unless we specifically ask for it for a lawful support or compliance purpose.

Creators must not design Jamango games, scripts, forms, leaderboards, chat flows, external links, or other user-generated content to collect personal information from players unless Jamango has expressly approved the collection in writing and the collection complies with applicable law.

6. How We Use Information and Our Legal Bases#

Provide Jamango: Accounts, guest sessions, login, purchases, email verification, saved progress, profiles, worlds, creator tools, multiplayer, matchmaking, leaderboards, persistent data, asset storage, and content delivery. Legal basis: Contract; legitimate interests in operating the service.
Publish and distribute creator content: World hosting, world review, thumbnails, feeds, search, recommendations, distribution channels, embedded players, creator pages, remix and collaboration features. Legal basis: Contract; legitimate interests in operating, promoting, and improving the platform.
Security and abuse prevention: Authentication, session protection, ban and mute enforcement, fraud checks, rate limits, exploit prevention, anti-spam, account integrity, and infrastructure monitoring. Legal basis: Legitimate interests; legal obligations where applicable.
Moderation and safety: Moderation by AI agents and human moderators, reports, surrounding chat snapshots, admin review, warnings, mutes, bans, unpublishing, removal, and legal or safety escalations. Legal basis: Legitimate interests in protecting users and Jamango; legal obligations; vital interests in urgent safety situations where applicable.
Analytics and product improvement: First-party analytics, PostHog analytics, limited product diagnostics, performance reports, country/device reports, creator funnel analysis, and feature testing. Legal basis: Legitimate interests; consent where required by law for cookies, analytics, or similar technologies.
Communications: Transactional emails, verification, password reset, support responses, security notices, product updates, community messages, and optional marketing. Legal basis: Contract; legitimate interests; legal obligations; consent or opt-out where required for marketing.
Compliance and legal claims: Responding to law enforcement, regulators, legal requests, rights requests, IP complaints, corporate records, tax/accounting obligations, and dispute handling. Legal basis: Legal obligations; legitimate interests in establishing, exercising, or defending legal claims.

7. Cookies, Analytics, Advertising, and Diagnostics#

Jamango uses cookies, local storage, SDKs, and similar technologies to keep you logged in, remember settings, secure the service, measure usage, debug product issues, and understand how Jamango is used.

Jamango first-party analytics record platform, gameplay, editor, performance, and content events so we can understand product usage and reliability.
PostHog is used for production analytics and diagnostics. Analytics events may be associated with an internal account identifier and basic account details. Jamango does not use session replay.
Jamango does not use advertising cookies, advertising pixels, or third-party advertising trackers on its own pages.
Distribution platforms and embedded partners may use their own SDKs, cookies, analytics, advertising systems, fraud-prevention tools, and consent flows when you access Jamango through them.

You can control cookies through browser settings. Distribution platforms may provide their own consent controls. Disabling cookies may prevent login, saved preferences, or other Jamango features from working correctly.

We share personal data only where we have a reason to do so. Current categories include:

Amazon Web Services and cloud infrastructure providers: Data: Account IDs, content files, worlds, avatars, assets, game data, logs, IP-derived technical data, database records, queues, compute and storage metadata. Purpose: Hosting, storage, databases, content delivery, matchmaking, game servers, logging, monitoring, security, and service operations.
PostHog and analytics infrastructure: Data: Internal user or account identifiers and basic account details (such as username and, for registered accounts, email address), device and browser data, country, session events, gameplay/editor events, page events, and performance data. Purpose: Analytics, debugging, reliability, fraud prevention, usability analysis, and product improvement.
Payment providers (Stripe): Data: Payment details you enter at checkout, purchase amount, currency, and transaction identifiers. Purpose: Processing purchases, refunds, fraud prevention, and payment records.
Moderation service providers: Data: Chat messages and the surrounding conversation, usernames or account identifiers, and report content. Purpose: Moderation of chat and other user content.
Internal team tools (such as Slack): Data: Operational notifications, which can include username, email address, country, device type, and purchase or report details. Purpose: Running the service, support, moderation, and team operations.
SendGrid and email delivery providers: Data: Email address, message content, delivery metadata, verification links, reset links, email-change notices. Purpose: Transactional emails, account verification, password resets, security notices, and service communications.
Discord: Data: Discord account IDs, OAuth/account-linking information, usernames, avatars, roles, membership signals, and related metadata. Purpose: Login, account linking, community features, role rewards, Discord presence or membership checks, and social/community activity.
Distribution channels, embedded players, and similar platforms: Data: Platform identifiers, language, loading and gameplay events, technical signals, referral or attribution data, SDK events, and data the distributor collects directly under its own policy. Purpose: Make Jamango games available on distribution channels, run distribution SDKs, support loading/gameplay flows, analytics, advertising, fraud prevention, and platform reporting.
Moderation, legal, safety, and professional recipients: Data: Reports, chat snapshots, account information, content, logs, legal notices, safety escalations, and communications. Purpose: Enforce our terms, investigate abuse, protect users, comply with law, respond to regulators or law enforcement, and obtain legal, accounting, or security advice.
Other users and the public: Data: Public profiles, usernames, avatars, badges, social links, worlds, thumbnails, descriptions, tags, leaderboards, followers/following, creator content, and visible gameplay or community activity. Purpose: Operate Jamango as a social, creator, discovery, and multiplayer platform.
Corporate transaction parties: Data: Relevant business, account, content, operational, and legal records. Purpose: Evaluate or complete a merger, acquisition, investment, financing, restructuring, sale of assets, or similar transaction.

We do not sell personal data, and we do not share personal data for targeted advertising.

9. User-Generated Content and Public Information#

Jamango is built around user-generated games and creator content. When you publish or share content, profile information, social links, worlds, packages, assets, thumbnails, descriptions, tags, leaderboard entries, or other activity, it may be visible to other users, visitors, search engines, community members, Jamango distribution channels, or players on distributor websites.

If you remove or unpublish content, copies may continue to exist for a limited time in backups, caches, reports, moderation records, collaborator copies, remixes, distribution channels, legal records, or places where other users have already interacted with it. We will handle deletion requests according to applicable law and the technical realities of multiplayer, creator, and UGC systems.

10. Children and Teens#

Jamango is a browser-based creator and gameplay platform played by people of all ages, so the same protections apply to every player:

Guests can play without giving a name, email address, or other contact details. Guests can read chat but cannot send messages.
Only registered players can send chat messages. Chat is moderated by AI agents and human moderators, and messages may be checked or blocked automatically.
There is no private messaging. Chat is visible to everyone in the room, and friend requests must be accepted.
Every player, including guests, can report another player. Reports are reviewed by people, who can warn, mute, or ban.
Jamango does not use advertising trackers and does not record play sessions.

If you are under 18, ask a parent or guardian before creating an account, and use Jamango only with their permission. Parents and guardians are responsible for the minor's use of Jamango, including account activity, public content, chat, creator activity, community participation, and any purchases. In some countries the law sets an age, between 13 and 16 depending on the country, below which a parent or guardian must agree to certain uses of a child's personal data. Children below that age should create an account only together with a parent or guardian. We are continuing to add protections for younger players.

Parents and guardians can contact support@jamango.io to ask what information we hold about their child, to have it corrected or deleted, or to close an account. We may ask for information to confirm the relationship. If we learn that we hold personal data about a child that we should not hold, we will delete it or take other appropriate steps as required by law.

Do not use real names, addresses, schools, phone numbers, private emails, precise locations, photos of identity documents, or other personal information in Jamango usernames, profiles, chat, worlds, social links, thumbnails, or uploads.
Creators must not use Jamango games or scripts to ask minors for personal information, external contact details, photos, voice/video contact, payments, or off-platform accounts.
Jamango may restrict features, remove content, disable accounts, or contact a parent or guardian where appropriate to protect minors.

11. International Transfers#

Jamango is operated from Ireland and uses service providers that may process personal data in Ireland, the European Economic Area, the United Kingdom, the United States, and other countries. Where personal data is transferred outside the EEA or another protected jurisdiction, we rely on appropriate safeguards such as adequacy decisions, standard contractual clauses, contractual commitments, and technical and organisational measures where required.

12. How Long We Keep Information#

We keep personal data only for as long as reasonably necessary for the purposes described in this policy, unless a longer period is required or permitted by law. Retention may depend on account status, content status, technical backups, safety needs, legal obligations, and product configuration.

Account and profile data: Kept while the account is active and for a reasonable period after deletion, suspension, or inactivity as needed for security, legal, fraud-prevention, moderation, and backup purposes. Deletion may involve disabling, anonymising, or replacing account identifiers where technically appropriate.
Guest accounts and platform guest sessions: Kept while needed to provide gameplay and account conversion. Guest activity may be deleted, anonymised, or linked to a registered account if the user converts or links the account.
Worlds, assets, packages, uploads, thumbnails, game data, and creator content: Kept while published, saved, used by the account, used by collaborators, distributed through Jamango, or needed for distribution channels, moderation, safety, backups, legal claims, or technical integrity. Unpublished or deleted content may remain temporarily in backups, caches, logs, reports, or moderation records.
Chat, reports, moderation snapshots, bans, mutes, and admin notes: Chat messages are not kept after they are delivered, except where they form part of a report or moderation record. Reports and moderation records are kept as long as needed for user safety, repeat-abuse detection, appeals, legal compliance, enforcement, and platform integrity. Reports may include surrounding chat-message snapshots.
Analytics, logs, and limited diagnostics: Kept for product analytics, debugging, security, and reliability for periods configured in our analytics and logging systems. Aggregated or de-identified analytics may be kept longer.
Email, support, legal, and rights requests: Kept as long as needed to respond, maintain records, comply with law, resolve disputes, and protect Jamango and users.
Backups: Kept for limited backup and disaster-recovery periods and then overwritten or deleted according to our backup practices.

13. Your Privacy Rights and Controls#

Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a portable copy of your personal data; withdraw consent; opt out of certain advertising, sale, sharing, or profiling activities; and complain to a supervisory authority.

EU/EEA and UK users may have GDPR-style rights, including access, rectification, erasure, restriction, objection, portability, withdrawal of consent, and the right to lodge a complaint with a supervisory authority. In Ireland, the supervisory authority is the Data Protection Commission.
California and other US state residents may have rights to know, access, delete, correct, obtain a copy, opt out of sale or sharing, opt out of targeted advertising, limit certain sensitive-data uses, and avoid discrimination for exercising rights, subject to applicable exceptions.
Parents or guardians may contact us to request deletion or restriction of a child's information where applicable.
You can update some profile information in the product, unlink optional connected accounts where supported, control cookies through browser settings, and unsubscribe from marketing emails through the link in those emails where offered.

To exercise rights, contact support@jamango.io. We aim to respond within one month where GDPR applies, or within the timeframe required by applicable law. We may extend the response period where the law allows, for example where a request is complex or there are multiple requests.

Some rights are not absolute. We may retain or withhold information where needed for security, fraud prevention, moderation, public expression, the rights of other users, legal obligations, backups, or legal claims. If we cannot fully comply with a request, we will explain why where required.

14. Automated Safety Tools#

Jamango uses a combination of AI agents and human moderators to help keep chat and content safe. Messages may be checked or blocked automatically. Our team reviews reports and decides bans. Automated checks may also trigger rate limits or short temporary restrictions such as a mute. You can ask us to review a moderation decision by contacting support@jamango.io.

15. Security#

We use technical and organisational measures designed to protect personal data, such as secure cookies where appropriate, access controls, hosted infrastructure controls, authentication safeguards, logging, moderation tools, and operational monitoring. No internet service is completely secure. You are responsible for keeping your login details safe and for reporting suspected account compromise to support@jamango.io.

16. Third-Party Services#

Jamango may link to or integrate with third-party services such as Discord, hosting providers, analytics providers, distribution channels, and other platforms. Those services may process personal data under their own terms and privacy policies. Jamango is not responsible for third-party privacy practices unless we are legally responsible for the processing in question.

17. Changes to This Policy#

We may update this Privacy Policy as Jamango evolves. If changes are material, we will take reasonable steps to notify users, such as updating the effective date, posting an in-product notice, or sending an email where appropriate. Your continued use of Jamango after the updated policy takes effect means the updated policy applies to your use of the service.

18. Contact#

Support, privacy requests, and legal notices: support@jamango.io
Postal address: Brownbricks Limited, trading as Jamango, The View Office Space, The View, Malahide Marina, Malahide, Dublin K36 CX99, Ireland