MIBDOG Beta Privacy Notice

MIBDOG is currently made available as a devnet beta product for testing, evaluation, iteration, and limited early access.

Because the Beta Service is experimental, information processing in this environment may include activities that are broader, more technical, or more operational than those typically found in a final production release, including:

• debugging;
• logging;
• monitoring;
• moderation;
• product testing;
• feature evaluation;
• abuse prevention;
• operational review.

The Beta Service may change at any time, and the categories of information processed may also change as the product evolves.

This Notice applies to information processed through the Beta Service, including without limitation:

• launch surfaces and devnet launch flows;
• social and profile surfaces, including MIB-S;
• utility and premium product surfaces, including Sponsored and Verified;
• documentation pages and related product materials;
• settings, account-related surfaces, invite flows, moderation flows, and related operational surfaces.

This Notice does not govern third-party services that may be linked to, integrated with, or used alongside the Beta Service, including wallets, social platforms, explorers, RPC providers, storage providers, or other external services. Those services are governed by their own privacy notices and terms.

Depending on how you use the Beta Service, MIBDOG may collect or process the following categories of information.

3.1 Wallet and blockchain-related information

• wallet address;
• wallet connection status;
• signed messages used for authentication or product actions;
• transaction-related information associated with your beta activity;
• public blockchain data related to actions you choose to take through devnet-connected flows;
• token, launch, sponsorship, or utility-related onchain references visible through beta product operation.

3.2 Profile and account-related information

• username, handle, display name, profile bio, avatar, banner, and profile settings;
• linked social identifiers or linked profile metadata, including possible X-linked profile state if such features are active;
• invite state, verification state, beta access state, moderation state, and related account/product flags;
• preferences, settings, or basic profile configuration.

3.3 Content and activity information

• posts, comments, messages, profile content, launch descriptions, media, links, and other content you submit;
• launch-related content, such as token name, symbol, description, image, links, and creator-facing metadata;
• interactions with product surfaces, such as likes, replies, trending interactions, profile visits, or other beta engagement signals;
• submissions for Sponsored, Verified, or other utility/product flows.

3.4 Payment and utility-related information

• records of beta utility purchases or paid beta actions;
• utility/payment state connected to Sponsored, Verified, or other beta product surfaces;
• current devnet payment mode information, including flows involving Wrapped SOL (devnet) where applicable;
• status information relating to whether a utility flow was attempted, completed, displayed, rejected, or moderated.

3.5 Technical and device information

• IP address or approximate network information;
• browser type and version;
• device type, operating system, language preferences, and similar technical metadata;
• pages viewed, timestamps, referring pages, navigation paths, session-level usage information, and other activity logs;
• performance data, crash data, request logs, rate-limit signals, and debugging information.

3.6 Upload and media information

• images, media, and files you upload;
• metadata associated with uploads;
• moderation or safety review signals related to uploaded content;
• storage or reference links associated with your beta content.

3.7 Communications and support information

• information you provide when contacting MIBDOG for beta feedback, support, bug reports, or moderation-related communications;
• correspondence content, contact details you voluntarily provide, and support context.

We may collect information:

• directly from you when you connect a wallet, create a profile, upload content, submit a launch, use beta utilities, or interact with product surfaces;
• automatically when you use the Beta Service, through logs, technical monitoring, session data, security systems, and product analytics;
• from blockchain infrastructure or other sources that reflect public onchain activity associated with your wallet-connected beta actions;
• from third-party services you choose to connect or use with the Beta Service, where applicable;
• from moderation, integrity, or operational review processes.

MIBDOG may use information collected through the Beta Service for the following purposes:

5.1 To operate the Beta Service

• authenticate users through wallet-based or product-based flows;
• provide profiles, launches, social surfaces, utilities, documentation, and related features;
• show beta state, access state, utility state, or product configuration.

5.2 To test and improve the product

• evaluate product behavior and beta feature performance;
• debug technical issues;
• analyze product usage and discoverability;
• review friction points and improve UX, reliability, and consistency.

5.3 To secure the Beta Service

• detect abuse, spam, fraud, bot activity, or misuse;
• investigate technical incidents, moderation issues, or policy concerns;
• enforce beta access restrictions, product rules, moderation rules, and safety measures.

5.4 To support public and social product surfaces

• display profile information, launch information, social content, and public beta activity where those surfaces are designed to be public;
• support public accountability features connected to launches, profiles, and MIB-S activity.

5.5 To manage utilities and beta payment flows

• process or reflect beta utility state;
• support sponsored visibility, verification-related flows, or other beta utility products;
• review payment-linked or access-linked beta behavior.

5.6 To communicate with you

• respond to support, moderation, or beta feedback messages;
• provide product notices, policy notices, or beta-related communications;
• send administrative or operational communications related to the Beta Service.

5.7 To comply with law and protect the Beta Service

• comply with applicable law, requests, or legal obligations where required;
• protect the rights, property, security, and integrity of MIBDOG, users, service providers, and the Beta Service itself.

Some information processed through the Beta Service may be visible to other users or to the public, depending on how the product surface is designed.

This may include, for example:

• wallet-linked profile surfaces;
• public profile information;
• launch pages and launch-related information;
• posts, comments, and public social activity;
• badges, visibility states, sponsorship states, or verification-related states;
• public blockchain data associated with devnet wallet activity.

You should assume that content or information you choose to make public through the Beta Service may be visible to others and may remain accessible in ways outside MIBDOG’s direct control.

If you use wallet-connected features, some related information may be recorded on public or semi-public blockchain infrastructure.

Blockchain records are not controlled solely by MIBDOG and may be visible through third-party infrastructure such as explorers, indexers, RPC providers, analytics tools, or other blockchain-facing services.

MIBDOG cannot remove or fully control public blockchain records once created.

The Beta Service may include testing of paid or gated utility flows.

At the current beta stage, some utility-related payments may be reflected through Wrapped SOL (devnet) or similar devnet-denominated flows. MIBDOG may process associated utility records, payment state, verification state, sponsorship state, or related operational data for beta functionality, testing, and support.

Beta payment and utility data may be changed, reset, removed, or replaced as part of beta iteration.

MIBDOG may use cookies, local storage, session storage, and similar technologies to:

• keep sessions working;
• remember preferences or settings;
• support authentication or wallet-connected state;
• measure product usage and beta performance;
• improve reliability and security.

MIBDOG may also maintain logs and technical event records relating to requests, sessions, system events, uploads, moderation actions, and other operational activity.

Because this is a beta environment, logging and technical monitoring may be more extensive than in a final public release.

MIBDOG may share information in the following circumstances.

10.1 With service providers and infrastructure providers

We may share information with hosting providers, storage providers, analytics providers, wallet or blockchain infrastructure partners, moderation tools, communication tools, and other vendors or technical providers that help us operate the Beta Service.

10.2 With public users or the public

Where the Beta Service is designed around public profiles, launch pages, social surfaces, or public devnet activity, information may be made available to other users or publicly visible as part of the product.

10.3 With third-party integrations chosen by you

If you choose to use external links, connect accounts, or interact with third-party services through the Beta Service, relevant information may be shared with or made visible through those services.

10.4 For legal, security, and integrity reasons

We may disclose information if we believe doing so is necessary to:

• comply with law or valid legal process;
• protect MIBDOG, users, service providers, or the public;
• investigate fraud, abuse, security incidents, or Beta Terms violations;
• enforce our policies, terms, or product rules.

10.5 In connection with product restructuring

If MIBDOG’s beta project, assets, operations, or related product infrastructure are reorganized, transferred, financed, or otherwise restructured, relevant information may be disclosed as reasonably necessary in connection with that process, subject to applicable safeguards where required.

Because this is a beta environment, retention periods may be flexible and may change over time.

MIBDOG may retain information for as long as reasonably necessary to:

• operate and improve the Beta Service;
• debug or investigate incidents;
• support moderation, safety, and product integrity;
• comply with legal obligations;
• preserve records relevant to disputes, abuse, or security reviews.

At the same time, MIBDOG may also reset, delete, wipe, anonymize, or remove beta data, devnet-linked data, utility states, launch states, profile states, uploaded references, or related records as part of testing, migration, moderation, technical maintenance, or beta iteration.

You should not rely on the Beta Service for permanent storage or permanent recordkeeping.

MIBDOG takes reasonable steps intended to protect information processed through the Beta Service. However, no system is completely secure, and the Beta Service is experimental.

You understand and accept that:

security measures may evolve during beta;
testing environments may involve changing infrastructure;
blockchain-related, wallet-related, and third-party service risks remain outside MIBDOG’s full control.

You are responsible for protecting your own wallet, credentials, devices, and account environment.

The Beta Service may be accessed from multiple jurisdictions, and technical infrastructure may operate across multiple countries.

By using the Beta Service, you understand that your information may be processed in jurisdictions other than your own, subject to the nature of the Beta Service and the third-party infrastructure used to support it.

The Beta Service is not intended for children.

You must be at least 18 years old, or the age of legal majority in your jurisdiction, whichever is higher, to use the Beta Service.

If MIBDOG becomes aware that information has been collected from a person who is not eligible to use the Beta Service under the Beta Terms, MIBDOG may remove relevant information and restrict access as appropriate.

Depending on the nature of the Beta Service and applicable law, you may be able to request access to, correction of, or deletion of certain information associated with your beta use.

You may also be able to:

• disconnect your wallet;
• change profile information;
• remove or edit certain public content through available product controls;
• stop using the Beta Service at any time.

Because this is a beta environment:

• not all data can be edited or deleted instantly;
• public blockchain data cannot be erased by MIBDOG;
• technical logs, security records, moderation records, and backup states may persist for a period of time;
• certain public or shared beta states may remain visible where required by the product or already reflected in external systems.

Requests may be sent to the contact address listed below.

This Notice should be read together with the MIBDOG Devnet Beta Terms.

If there is a conflict between this Notice and the Beta Terms on a privacy-specific issue, this Notice governs that privacy-specific issue. On issues of beta access, product use, wallet use, disclaimers, or liability, the Beta Terms govern.

MIBDOG may update this Notice from time to time to reflect product, legal, operational, or technical changes.

When this Notice is updated, the “Last Updated” date above will change. Your continued use of the Beta Service after the updated Notice becomes effective means you acknowledge the updated Notice.

For beta privacy questions or requests, please contact:

MIBDOG
Email: contact@mibdog.com
Website: https://mibdog.com