BattlePass Privacy Policy

Introduction

Welcome to BattlePass.

BattlePass is a participation and reputation platform that helps communities, organizers, hackathons, workshops, bounty programs, and event teams create campaigns where members can complete activities, earn XP, unlock badges, and build public participation profiles.

This Privacy Policy explains how BattlePass collects, uses, stores, shares, and protects information when you use our website, app, dashboards, public profiles, community pages, campaign pages, and related services.

This policy applies to all users of BattlePass, including visitors, members, community owners, admins, reviewers, event staff, sponsor viewers, and any other person who accesses or uses the platform.

By using BattlePass, you agree to the collection and use of information as described in this Privacy Policy. If you do not agree with this Privacy Policy, you should not use BattlePass.

Key Definitions

For clarity, the following terms are used throughout this Privacy Policy.

"BattlePass," "we," "our," or "us" refers to the BattlePass platform, website, application, and related services.

"User," "you," or "your" refers to anyone who accesses or uses BattlePass.

"Visitor" refers to a person who browses public pages without signing in.

"Member" refers to a user who creates an account and participates in communities, campaigns, activities, or passes.

"Community" refers to an organization, group, ecosystem, event organizer, hackathon team, developer community, or other entity that uses BattlePass to manage participation.

"Campaign" refers to a structured participation program created by a community. Examples include hackathons, workshops, bounty programs, event series, and community seasons.

"Activity" refers to a task, event, workshop, bounty, mission, check-in, submission, or other action that a user can complete inside a campaign.

"Badge" or "Achievement" refers to a credential or recognition issued to a user after completing a verified activity or milestone.

"Public Profile" refers to a user profile that may display public participation history, badges, achievements, communities, and campaign involvement.

"Wallet" refers to a blockchain wallet, including a Solana wallet, that may be linked to a user account for identity, verification, badges, passes, and on-chain records.

Information We Collect

BattlePass collects information in different ways depending on how you use the platform.

We collect information when you browse public pages, create an account, sign in, connect a wallet, join a community, enroll in a campaign, complete activities, submit proof, receive badges, manage communities, or interact with dashboards.

3.1 Information You Provide Directly

You may provide information directly when you create or update your BattlePass account, set up your profile, join campaigns, submit activity proof, or manage communities.

This may include:

• Display name
• Username
• Email address
• Profile photo or avatar
• Short bio
• Social links, such as X/Twitter, GitHub, LinkedIn, Discord, or website
• Community details if you create or manage a community
• Campaign details if you create or manage a campaign
• Activity submissions, such as text, links, files, screenshots, GitHub links, project links, wallet transaction references, or other supporting proof
• Messages, notes, or feedback submitted through forms or dashboards
• Support requests or communications with BattlePass

You should only submit information that you have the right to provide. If you submit information relating to another person, you are responsible for ensuring that you have permission to do so.

3.2 Account and Authentication Information

BattlePass may use an authentication provider such as Privy or another third-party identity provider to support sign-in, wallet login, email login, embedded wallet onboarding, and session management.

Depending on the sign-in method used, we may receive or process:

• Authenticated user ID from the authentication provider
• Email address
• Email verification status
• Linked wallet address
• Login method
• Session/token information needed to keep you signed in
• Linked account information made available by the authentication provider

BattlePass does not need to store your private keys, seed phrase, or wallet recovery phrase. You should never share your private key or seed phrase with BattlePass or any person claiming to represent BattlePass.

3.3 Wallet and Blockchain Information

Because BattlePass is built around Solana-based participation and credential flows, we may collect or display blockchain-related information.

This may include:

• Public wallet address
• Wallet connection status
• Wallet signature confirmation for login or verification
• Campaign pass ownership references
• Badge or achievement on-chain record references
• NFT, compressed NFT, or credential asset identifiers
• Transaction signatures submitted for activity verification
• Public blockchain data related to activities or credentials

Blockchain data may be public by nature. If a badge, pass, transaction, or wallet-linked record is published on-chain, it may be visible to others through blockchain explorers or other tools.

BattlePass does not control public blockchain networks and cannot guarantee that on-chain data can be deleted, hidden, or changed once published.

3.4 Community, Campaign, and Activity Information

When you participate in BattlePass campaigns, we may collect information about your participation.

This may include:

• Communities you join
• Campaigns you enroll in
• Activities you view, start, submit, complete, or fail to complete
• Event check-ins
• QR code check-ins
• Claim code submissions
• Proof submissions
• Reviewer decisions
• Admin approvals
• XP earned
• Levels reached
• Badges earned
• Rewards unlocked or claimed
• Activity status, such as pending, approved, rejected, completed, expired, or revoked

This information is necessary to operate the platform and show your progress, achievements, and public participation history.

3.5 Submission and Verification Information

Some activities require users to submit proof for review. Reviewers, admins, or automated systems may evaluate this proof.

Submission and verification information may include:

• Links to work submitted
• GitHub repositories or pull requests
• Project URLs
• Screenshots
• Uploaded files
• Transaction signatures
• Written explanations
• Reviewer notes
• Approval or rejection decisions
• Timestamps
• Verification method used
• Internal review history

Not all submitted proof is public. Public profiles should generally display the achievement earned, not necessarily all raw evidence. However, if you submit public links, blockchain transactions, or public repositories, those may already be visible outside BattlePass.

3.6 Information Collected Automatically

When you use BattlePass, we may automatically collect technical and usage information.

This may include:

• Device type
• Browser type
• Operating system
• IP address
• Approximate location derived from IP address
• Pages visited
• Buttons clicked
• Referring URLs
• Session duration
• Error logs
• Feature usage
• Performance data
• Cookies or similar technologies

This information helps us operate, secure, improve, and debug the platform.

3.7 Cookies and Similar Technologies

BattlePass may use cookies, local storage, session storage, and similar technologies to support core product functionality.

These technologies may be used to:

• Keep users signed in
• Remember preferences
• Store intended redirects after sign-in
• Improve performance
• Understand usage patterns
• Protect against abuse
• Support analytics

You may be able to control cookies through your browser settings. However, disabling certain cookies or local storage features may affect the functionality of BattlePass.

How We Use Information

BattlePass uses information to operate the platform, provide user accounts, support community participation, issue badges, manage campaigns, and improve the product.

We may use information for the following purposes:

4.1 To Provide and Operate the Platform

We use information to create accounts, authenticate users, maintain sessions, display dashboards, show campaigns, track participation, process submissions, and provide public and private product features.

4.2 To Create and Manage User Profiles

We use profile information to display your BattlePass identity, username, public profile, badges, communities, campaigns, and achievements.

4.3 To Support Community and Campaign Participation

We use participation data to allow users to join communities, enroll in campaigns, complete activities, earn XP, unlock badges, and claim rewards.

4.4 To Verify Activities and Issue Achievements

We use submitted proof, check-in data, transaction references, reviewer decisions, and admin approvals to verify whether activities were completed and whether badges should be issued.

4.5 To Display Public Reputation

If you participate in public communities or public campaigns, some of your participation information may appear on your public profile, campaign pages, leaderboards, activity feeds, or community pages, depending on visibility settings.

This may include:

• Username
• Display name
• Avatar
• Public wallet address or shortened wallet address
• Public badges
• Public achievements
• Public activities completed
• Campaigns joined
• Communities joined
• XP or level information
• First verified activity
• Recent public achievements

4.6 To Manage Community Dashboards

We use community and role information to allow community owners, admins, reviewers, event staff, and sponsor viewers to access appropriate dashboards and perform permitted actions.

4.7 To Improve and Secure BattlePass

We use technical and usage data to detect bugs, prevent fraud, secure accounts, investigate abuse, monitor platform performance, and improve user experience.

4.8 To Communicate With Users

We may use contact information to send service-related messages, such as verification emails, account notices, activity updates, submission decisions, badge notifications, reward updates, security alerts, and support responses.

4.9 To Comply With Legal Obligations

We may use information where required to comply with applicable laws, legal requests, regulatory obligations, dispute resolution, fraud prevention, or enforcement of our Terms of Service.

Public Information and Visibility

BattlePass is designed around public participation and public reputation. Some information may be visible publicly depending on how you use the platform and the visibility settings of communities, campaigns, badges, and profiles.

5.1 Information That May Be Public

The following information may be public:

• Display name
• Username
• Avatar
• Bio
• Public social links
• Public wallet address or shortened wallet address
• Communities joined
• Public campaigns joined
• Public activities completed
• Public badges and achievements
• XP and levels where enabled
• Verification method for public achievements
• On-chain badge or pass references
• Public leaderboard placement
• Public activity timeline

5.2 Information That Should Not Be Public by Default

The following information should not be public by default:

• Email address
• Private reviewer notes
• Internal admin notes
• Private uploaded files
• Rejected submissions
• Pending submissions
• Fraud flags
• Internal audit logs
• Private campaign data
• IP address
• Sensitive operational data

5.3 Public Profiles

Your public profile may be used to show your verified community journey. If you participate in public campaigns, certain achievements and activities may appear publicly.

You may have controls to update profile details or manage certain visibility settings. Some visibility settings may also depend on the community or campaign that issued a badge or achievement.

5.4 Leaderboards and Public Activity Feeds

Some campaigns may use public leaderboards, recent activity feeds, or top contributor lists. If you join those campaigns, your public participation may appear in those areas unless visibility settings allow you to opt out.

How We Share Information

BattlePass does not sell user personal information. However, we may share or display information in the ways described below.

6.1 With Communities and Organizers

If you join a community or campaign, the community owner, admins, reviewers, or event staff may access information necessary to manage participation.

This may include:

• Your username
• Display name
• Wallet address
• Campaign enrollment status
• Activity submissions
• Submission status
• Activity completion history
• Badges earned
• XP and level progress
• Reward claim status

Community admins and reviewers may need this information to verify activities, approve submissions, issue badges, and manage campaign operations.

6.2 With Reviewers and Event Staff

If an activity requires review or event check-in, assigned reviewers or event staff may access relevant user and submission information to perform their roles.

6.3 With Sponsors or Partner Viewers

Some communities may provide sponsors or partners with limited campaign analytics or impact reports. These reports may include aggregated participation data such as number of members, activities completed, achievements issued, or rewards claimed.

We should avoid sharing private user submissions or sensitive personal information with sponsors unless clearly disclosed and permitted.

6.4 With Service Providers

We may use third-party providers to help operate BattlePass. These may include providers for:

• Authentication
• Wallet onboarding
• Cloud hosting
• Database hosting
• File storage
• Analytics
• Email delivery
• Error monitoring
• Security
• Blockchain RPC or indexing

These providers may process information only as needed to provide services to BattlePass.

6.5 With Blockchain Networks

If a badge, pass, transaction, or credential is created or referenced on-chain, related information may be published to a public blockchain network. Public blockchain data may be accessible to anyone and may not be removable.

6.6 For Legal, Safety, and Security Reasons

We may disclose information if we believe it is necessary to:

• Comply with law or legal process
• Protect the rights, safety, or property of BattlePass, users, communities, or others
• Investigate fraud, abuse, or security issues
• Enforce our Terms of Service
• Respond to government or regulatory requests

6.7 Business Transfers

If BattlePass is involved in a merger, acquisition, financing, restructuring, sale of assets, or similar transaction, user information may be transferred as part of that transaction, subject to appropriate protections.

Third-Party Services

BattlePass may integrate with third-party services. These services may have their own privacy policies and terms.

Examples may include:

• Privy or similar authentication and wallet providers
• Solana wallets
• Blockchain RPC providers
• Cloud hosting providers
• File storage providers
• Email providers
• Analytics tools
• Error monitoring tools
• Social platforms linked by users

BattlePass is not responsible for the privacy practices of third-party websites, wallets, blockchains, or services that we do not control.

You should review the privacy policies of any third-party services you use with BattlePass.

Blockchain and On-Chain Data

BattlePass may use blockchain technology for wallet identity, passes, badges, achievements, and verification records.

You should understand that public blockchains are generally transparent. Information published on-chain may be visible to anyone and may be permanent or difficult to remove.

BattlePass may store certain information off-chain and may only reference on-chain records where appropriate. However, if you choose to receive or interact with on-chain credentials, certain public information may be associated with your wallet address.

You are responsible for understanding the public nature of blockchain transactions and wallet activity.

Data Retention

We retain information for as long as necessary to provide BattlePass, maintain user profiles, operate communities and campaigns, comply with legal obligations, resolve disputes, prevent abuse, and enforce our Terms of Service.

Some information may be retained for longer where necessary for security, audit logs, fraud prevention, legal compliance, or legitimate business purposes.

If information has been published to a public blockchain, BattlePass may not be able to delete or alter that on-chain information.

Data Security

We use reasonable technical, organizational, and administrative measures to protect user information.

These measures may include:

• Authentication controls
• Role-based access controls
• Secure token handling
• Encryption where appropriate
• Access logging
• File storage controls
• Permission checks
• Review of sensitive admin actions

However, no system is completely secure. We cannot guarantee absolute security of information.

You are responsible for keeping your account, wallet, device, email, and credentials secure.

You should never share your wallet private key, seed phrase, or recovery phrase with anyone.

Your Choices and Rights

Depending on your location and applicable law, you may have rights relating to your personal information.

These may include the right to:

• Access your information
• Correct inaccurate information
• Delete certain information
• Object to certain processing
• Request restriction of certain processing
• Request a copy of your information
• Manage public profile visibility settings
• Disconnect or update certain linked accounts where supported

Some information may be required to operate your account or maintain participation records. Some blockchain data may not be removable by BattlePass.

To make a privacy request, contact us using the contact details in this Privacy Policy.

Children and Minors

BattlePass is not intended for children below the minimum age required to use online services in their jurisdiction.

If we learn that we have collected personal information from a child without appropriate consent where required, we may take steps to delete the information or restrict access.

Communities that use BattlePass for schools, youth programs, or minors should ensure they comply with applicable consent, privacy, and safeguarding requirements.

International Users

BattlePass may be accessed from different countries. Your information may be processed in countries other than where you live.

By using BattlePass, you understand that your information may be transferred, stored, and processed in locations where our service providers or infrastructure are located.

Changes to This Privacy Policy

We may update this Privacy Policy from time to time.

When we update it, we will revise the "Last Updated" date at the top of the page. If changes are material, we may provide additional notice through the app, website, email, or other reasonable means.

Your continued use of BattlePass after changes become effective means you accept the updated Privacy Policy.

Contact Us

If you have questions about this Privacy Policy or how BattlePass handles information, contact us at:

Email: battlepassecosystem@gmail.com
Website: battlepass.xyz
Legal Entity: BattlePass Ecosystem
Address: Lagos, Nigeria