← Back to Home

Privacy Policy

Last updated: May 25, 2026

1. Introduction

Welcome to Builders.to ("we," "our," or "us"), a platform for sharing projects, getting feedback, finding first paying users, sponsoring builders, running peer reviews, posting bounties, and earning or spending in-app tokens (including via the optional $BUILDERS Solana token). We are committed to protecting your privacy and personal information. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our website, our native mobile apps, and any related services.

2. Information We Collect

2.1 Information You Provide

  • Account Information: When you sign in using OAuth providers (Google, GitHub, or X/Twitter) or via a magic-link email, we receive your name, email address, and (for OAuth) your profile picture and provider user ID.
  • Profile Information: Username, display name, bio, headline, location (city, state, country, zip code), website, social media links, YouTube / Twitch URLs, and other profile fields you choose to add.
  • Location Data: When you provide your location, we geocode it to coordinates for map display. We apply a privacy offset of approximately 10 miles to protect your exact location.
  • Project Information: Details about projects you submit including titles, descriptions, images, URLs (including the backlink URL we verify), tags, and milestone data.
  • Company Information: Business details you provide when creating company profiles, including tech stack, traction metrics, and team information.
  • Content: Daily updates, comments, polls, threaded replies, and any other content you post on the platform.
  • Reviews / Testers: Review requests you create (project URL, notes, number of reviews requested) and reviews you submit to other builders (text content, optional 1–5 star rating).
  • Bounties: Bounty listings you post (title, description, summary, skills, reward amount in tokens and/or USD, deadline, external links) and work-request messages you submit to bounty owners.
  • Service Listings: Information about services you offer, including descriptions, pricing, and portfolio projects.
  • Local Listings: Classified listings you create, including contact information you choose to share.
  • Job Postings: Information about roles and positions you post for your company.
  • Events: Event details you create including title, description, date, time, location, and whether events are physical, virtual, or hybrid.
  • Chat & Messages: Messages you send in community channels and direct conversations, including text content, images, GIFs, code snippets, polls, and emoji reactions.
  • Presence Data: Your online/offline status, "last seen" timestamps, and typing indicators when using the real-time chat.
  • Builder Matching Data: Your building category (e.g., SaaS, Mobile App, Developer Tools), tech stack, and interests used for discovering similar builders.
  • Onboarding Progress: Which onboarding steps you have completed in the welcome modal and the settings wizard.
  • Tax-Buff & Token Spend Preferences: Optional buff selections that bias how engagement-based tokens are credited (e.g., projects, social, or wagers).

2.2 Information Collected Automatically

  • Usage Data: Information about how you interact with our services, including pages visited, features used, and content viewed.
  • Device Information: Browser type, operating system, device identifiers, and (for the iOS / Android app) whether the request originates from inside our native shell.
  • Log Data: IP address, access times, referring URLs, and request data.
  • Analytics: View counts, click tracking, and engagement metrics for projects, listings, profiles, and advertisements. Critical conversion events are also reported server-side via Umami.
  • Browser Geolocation: When you use nearby features (events, users), we may request your browser location with your permission to find content within your radius.
  • Profile View Data: When another signed-in builder views your profile, that view is logged so you can see who has visited your profile.

2.3 Information from Third Parties

  • OAuth Providers: Profile information from Google, GitHub, or X/Twitter when you authenticate.
  • Giphy: When you use GIFs in posts, we interact with the Giphy API on your behalf.
  • OpenStreetMap: We use OpenStreetMap Nominatim for geocoding your location data.
  • Solana RPC & Price Providers: When you use crypto payment, sponsorship, or wallet-linking features, we interact with Solana RPC nodes and external SOL/USD price providers (e.g., CoinGecko, Coinbase, Binance) on your behalf, and with on-chain price feeds (e.g., Dexscreener, Jupiter) to resolve the live $BUILDERS USD rate.
  • Backlink Verification: To verify that your published projects link back to Builders.to, we fetch the public HTML and a limited number of script assets from the URLs you submit.
  • External Embeds: When you link YouTube, Twitch, or other supported videos / GIFs, those services may receive standard request data when other users load your content.

2.4 Platform Connection Data

When you connect social media platforms for cross-posting, we collect:

  • OAuth Tokens: Access and refresh tokens for Twitter/X, encrypted at rest using AES-256-GCM.
  • Platform Profiles: Your username, display name, avatar, and follower count from connected platforms.
  • Token Expiration: When your tokens expire so we can refresh them automatically.

2.5 Solana Wallet & Crypto Payment Data

When you use any of our optional crypto features, we collect:

  • Wallet Public Key: The Solana public key (base58 address) you connect or designate as your $BUILDERS reward wallet, plus the signature you provide to prove ownership during a sign-in-with-Solana style verification challenge.
  • Purchase Intents: For SOL token-pack purchases and $BUILDERS burn purchases, we store an intent record containing the pack id, payer address, treasury address, mint address, quoted lamports / base units, and a server-issued quote of the SOL/USD or $BUILDERS/USD price at quote time.
  • On-Chain Confirmation Data: The transaction signature, slot, block time, cluster, and verification metadata after we confirm a payment or burn on chain.
  • x402 Sponsorship Authorizations: For recurring crypto sponsorships, we store the authorization id returned by the x402 facilitator, the sponsor wallet address, the rail (USDC / SOL / $BUILDERS), and per-charge transaction signatures and timestamps.
  • Crypto Tip Records: For one-off crypto tips, we store the asset, amount, sender and recipient public keys, transaction signature, and tip status.
  • Founder Mint / First 1,000 Claim: For users who claim founder rewards, we store a FoundersMint row recording the claim and resulting perk grants. Legacy on-chain mints additionally store the wallet address, asset address, transaction signature, and cluster from the original mint flow.

Wallet public keys, transaction signatures, and on-chain block data are publicly visible on the Solana blockchain by their nature and cannot be deleted from the chain.

2.6 Subscription, Sponsorship & Payout Data

  • Stripe Customer Data: When you subscribe to Pro, Founder's Circle, or Mastermind, or top up tokens with a card, we receive a Stripe customer ID, subscription ID, plan type, billing dates, and (where present) sponsor email. We do not store your card numbers.
  • Stripe Connect (Creator Payouts): If you receive sponsorships or marketplace payouts, we record your Stripe Connect account ID and onboarding status so payouts can be routed to you. Onboarding and payout details are handled by Stripe.
  • Sponsorship Records: Sponsor and creator user identifiers, monthly amount, rail (Stripe USD, x402 USDC, x402 SOL, x402 $BUILDERS), platform fee, status, and per-charge metadata.
  • Burn-Paid Subscription Records: When you pay for Pro / Founder's Circle by burning $BUILDERS, we store an off-chain subscription period plus the burn intent and confirmation metadata described in Section 2.5.

2.7 Native Mobile App Data

If you use our iOS or Android app:

  • Push Tokens: If you allow notifications, we store your APNs (iOS) or FCM (Android) device token so we can deliver push notifications to your device. Tokens are removed when you sign out, uninstall the app, or revoke notification permissions.
  • Native Context Header: Our server detects the native shell from the User-Agent header so it can apply Apple App Store / Google Play in-app-purchase requirements to digital-good purchases (Pro subscriptions, token packs, playbook unlocks, mastermind subscriptions).
  • In-App Purchase Receipts: If you purchase digital goods inside the app, the underlying receipt is processed by Apple or Google. We may receive transaction identifiers needed to grant the corresponding in-app entitlement.

3. How We Use Your Information

We use the information we collect to:

  • Provide, maintain, and improve our services
  • Create and manage your account
  • Display your projects, profile, and content to the community
  • Enable interactions between community members (comments, upvotes, follows, chat channels, direct messages)
  • Process token rewards for engagement, referrals, streak milestones, helpful contributions, and reviews
  • Process Pro, Founder's Circle, and Mastermind subscription payments through Stripe
  • Process payments through Stripe for services, listings, sponsorships, and advertisements
  • Process optional crypto payments (SOL token packs, $BUILDERS burns, x402 sponsorships, crypto tips) and verify them on the Solana blockchain
  • Verify Solana wallet ownership before binding a wallet to your account or paying out $BUILDERS rewards
  • Verify backlinks from your project URLs to Builders.to and run the backlink Autopilot reminder cadence
  • Cross-post your content to connected social media platforms (Twitter/X)
  • Send important service-related communications
  • Send optional daily and weekly digest emails, magic-link sign-in emails, and other transactional emails (most can be opted out of)
  • Deliver web and native (APNs / FCM) push notifications (with your explicit consent)
  • Protect against fraud, abuse, and policy violations, including detection of duplicate accounts, manipulation of the token economy, and abusive Wagers play
  • Comply with legal obligations
  • Generate anonymized analytics and statistics
  • Facilitate event RSVPs and the bounties / reviews / sponsorships marketplaces
  • Find nearby users and events based on your location
  • Provide real-time community chat channels and private messaging between members
  • Display your online/offline presence status and typing indicators to other chat participants
  • Enforce chat moderation rules including auto-moderation filters and slow mode
  • Match you with similar builders based on tech stack, building category, and interests
  • Calculate and display public backer tiers, momentum scores, and the karma leaderboard
  • Apply Apple App Store and Google Play in-app-purchase rules to digital-good purchases initiated from inside the native mobile app

4. Token System & Token Economy

Builders.to operates an in-app token (virtual currency) system:

  • Builder Tokens: Earned through referrals, streak milestones, helpful engagement, peer reviews, the Wagers token game, and other community actions. Tokens can be spent on sidebar advertisements, project trending boosts, peer-review requests, streak freezes, company creation, the Wagers game, and gifts to other builders.
  • Welcome Bonus: New accounts receive a small expiring token grant (currently 10 tokens, 14-day expiry) so you can try a first spend without a top-up.
  • Referral Rewards: When someone signs up with your referral code, both accounts receive non-expiring token credits.
  • Expiring Grants: Some tokens are credited as expiring grants. Token transactions track an outstanding remainingAmount so expiring tokens are consumed FIFO and your balance never drops below earned tokens.
  • Token Top-Ups: Tokens can be purchased with a card (via Stripe), with SOL via a connected Solana wallet, or by burning $BUILDERS from a connected Solana wallet. Each method records purchase metadata (intent, amount, status, on-chain signature, etc.) on your account.

In-app tokens have no real-world monetary value and cannot be redeemed for cash, transferred off the platform, or exchanged for items of monetary value. We reserve the right to modify, reset, or discontinue this system at any time, subject to applicable law.

5. Subscriptions (Pro, Founder's Circle, Mastermind)

Builders.to offers paid subscription plans with enhanced features:

  • Card Subscriptions (Stripe): We store your Stripe customer ID, subscription ID, plan type (Pro / Founder's Circle / Mastermind), billing cycle (monthly/yearly), and billing dates. We do not store your card numbers.
  • Burn-Paid Subscriptions: If you pay for Pro or Founder's Circle by burning $BUILDERS, we store an off-chain subscription record (no Stripe customer, no auto-renew) plus the burn intent and on-chain confirmation metadata described in Section 2.5.
  • Mastermind: The Mastermind subscription is a separate $9/month Stripe subscription with its own customer record.

Card payments are handled by Stripe. Crypto payments are settled directly on the Solana blockchain; the on-chain transaction record is public.

6. $BUILDERS Token, Solana Wallets & Crypto Payments

$BUILDERS is a Solana SPL token publicly listed on Pump.fun. The token is independent of your Builders.to account; we display its public listing details (mint address, locked allocation, transaction links) on the investor page for transparency. Using $BUILDERS or any Solana wallet feature is entirely optional.

When you use crypto features, we process the data described in Sections 2.5 and 2.6. In particular:

  • Wallet Linking: Before associating a wallet with your account or paying out rewards, we issue a short-lived nonce-based challenge that you must sign with your wallet. The signature, public key, and message body are verified server-side; only successful (single-use) verifications are accepted.
  • Token Pack Purchases (SOL): Pack id, lamports, payer address, treasury address, SOL/USD quote, transaction signature, slot, and block time are stored to make the credit idempotent and verifiable.
  • Token Pack Purchases ($BUILDERS Burn): Pack id, mint address, payer associated-token-account, base-unit amount, decimals, $BUILDERS/USD quote, transaction signature, slot, and block time are stored.
  • Recurring x402 Sponsorships: Authorization id, sponsor wallet address, rail (USDC / SOL / $BUILDERS), monthly amount, platform fee, and per-charge transaction signatures are stored.
  • Crypto Tips: One-off tip status (pending / sent / failed), asset, amount, sender and recipient public keys, and transaction signatures are stored.
  • First 1,000 Founder Rewards: A FoundersMint row is created when you claim. The current claim is off-chain (no NFT mint); legacy claims may also store on-chain wallet, asset, and transaction data from the original mint flow.

Solana RPC requests, transaction signatures, and on-chain balances are handled by third-party RPC providers and are publicly visible on the Solana blockchain. We are not the issuer of $BUILDERS, USDC, SOL, or any external token, and we do not custody your wallet keys.

7. Sponsorships, Bounties & Reviews Marketplaces

We operate several marketplaces that involve money or tokens flowing between users:

  • Sponsorships: When you sponsor a builder or project, we store the sponsor and creator user identifiers, monthly amount, rail (Stripe USD or x402 USDC / SOL / $BUILDERS), platform fee (currently 5%), status, billing periods, and per-charge metadata. The sponsor's display name and amount are publicly visible on the recipient's profile and on backer leaderboards unless paid as a guest with no Builders.to account.
  • Crypto Tips: One-off tips include the asset, amount, sender and recipient public keys, status, and transaction signature. Tip activity may be displayed publicly on the recipient's profile.
  • Bounties: Bounty postings are public and include the title, summary, description, skills, reward, deadline, owner, and submitted work-request messages. Bounty owners can see the identity of builders who submit work requests.
  • Reviews / Testers: Reviewers' identities, review text, and ratings are visible to the project owner and (where applicable) on public project pages. Token escrow and payouts are recorded as token transactions.
  • Backer Tiers & Leaderboards: Aggregate sponsorship spend may be summarized into public backer tiers and a backer leaderboard.

8. Information Sharing

We may share your information in the following circumstances:

  • Public Content: Your profile, projects, companies, updates, comments, service listings, local listings, job postings, events, bounty postings, public reviews, and sponsorship-funded badges are publicly visible to other users and visitors.
  • Leaderboards: Karma, streak, and backer-tier data may appear on public leaderboards.
  • Service Providers: We share information with third-party vendors who assist in operating our services:
    • Stripe for payment processing, subscription billing, and Stripe Connect (sponsorship and marketplace payouts)
    • Resend for email delivery (including magic-link sign-in emails)
    • Giphy for GIF integration
    • OpenStreetMap for geocoding services
    • Solana RPC providers for sending and reading on-chain transactions
    • The x402 facilitator and webhook provider for recurring crypto sponsorships
    • SOL/USD price providers (e.g., CoinGecko, Coinbase, Binance) and $BUILDERS/USD price feeds (e.g., Dexscreener, Jupiter)
    • Apple (APNs) and Google (FCM) for native mobile push delivery
    • Apple App Store and Google Play for in-app purchases originating from inside the native shell
    • Infrastructure providers for hosting and database services
  • On-Chain Counterparties: When you transact on Solana, your wallet public key, amounts, and transaction signatures become permanently visible on the public Solana blockchain.
  • Legal Requirements: We may disclose information if required by law or to protect our rights and safety.
  • Business Transfers: In connection with any merger, acquisition, or sale of assets.

We do not sell your personal information to third parties.

9. Data Security

We implement appropriate technical and organizational measures to protect your personal information against unauthorized access, alteration, disclosure, or destruction:

  • Two-Factor Authentication: Optional TOTP-based two-factor authentication with encrypted backup codes.
  • OAuth Security: We use industry-standard OAuth 2.0 for authentication and do not store your social media passwords.
  • Magic-Link Sign-In: Passwordless email sign-in uses single-use, expiring tokens delivered through Resend.
  • Encrypted Connections: All data is transmitted over HTTPS.
  • Secure Payments: Card payment processing is handled by Stripe; we do not store credit card numbers. On-chain crypto payments are signed by you and verified server-side against the Solana blockchain.
  • Encrypted Sensitive Data at Rest: OAuth tokens for connected platforms, 2FA backup codes, and other sensitive blobs are encrypted at rest using AES-256-GCM.
  • Wallet Verification: Wallets must pass a single-use sign-in-with-Solana style challenge before they are bound to your account.
  • Native IAP Enforcement: Digital-good purchases initiated from inside the native iOS / Android shell are gated server-side so they route through StoreKit / Google Play Billing rather than card.
  • Location Privacy: Your geocoded location is offset by approximately 10 miles to protect your exact address.

However, no method of transmission over the Internet or electronic storage is 100% secure, and we cannot guarantee absolute security.

10. Your Rights and Choices

You have the following rights regarding your information:

  • Access and Update: You can access and update your profile information through your account settings.
  • Delete Content: You can delete your projects, companies, updates, comments, listings, events, reviews, bounty postings, and chat messages.
  • Account Deletion: To delete your account entirely, please contact us through our community channels.
  • Email Preferences: You can opt out of daily and weekly digest emails in your settings.
  • Push Notifications: You can disable web push through your browser settings, native push through the iOS / Android system settings, and you can revoke notification permissions on your account.
  • Two-Factor Authentication: You can enable or disable 2FA at any time in your security settings.
  • Platform Connections: You can disconnect your Twitter/X account at any time, which revokes our access to that platform.
  • Wallet Disconnect: You can remove a linked Solana wallet from your account; this prevents new $BUILDERS reward payouts from going to that wallet but does not affect on-chain history.
  • Sponsorships: You can cancel an active sponsorship at any time through the sponsorships dashboard. For x402 sponsorships, cancellation revokes the future-charge authorization with the facilitator.
  • Subscriptions: You can cancel your Pro, Founder's Circle, or Mastermind subscription at any time through your account settings.
  • Data Portability: You may request a copy of your data by contacting us.

Some data cannot be removed: on-chain transactions and signatures are permanently visible on the Solana blockchain, and certain financial / audit records are retained as described in Section 22.

11. Third-Party Services

Our service integrates with third-party services. Your use of these services is governed by their respective privacy policies:

  • Authentication: Google, GitHub, X/Twitter OAuth, and Resend (magic-link emails)
  • Card Payments: Stripe (subscriptions, advertisements, marketplace payouts, sponsorships, Stripe Connect)
  • Crypto Payments: Solana RPC providers, the x402 facilitator (recurring crypto sponsorships), and SOL/USD & $BUILDERS/USD price feeds (CoinGecko, Coinbase, Binance, Dexscreener, Jupiter, or other configured providers)
  • Pump.fun: The official $BUILDERS token listing and creator profile are hosted on Pump.fun; we link to and display public metadata from that listing
  • Cross-Posting: Twitter/X API (when you connect this platform)
  • Community: Discord and Telegram (we share invite links to community channels; if you join, those services receive standard account data on their side)
  • Media: Giphy (for GIF selection)
  • Video Embeds: YouTube, Twitch (when you link videos)
  • Geocoding: OpenStreetMap Nominatim (for location services)
  • Native Push: Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM)
  • App Stores: Apple App Store and Google Play (in-app purchases inside the native shell)
  • Backlink Verification: When you submit a project URL, we fetch the public HTML and limited script assets from that URL to verify the backlink

We encourage you to review those policies before using them.

12. Chat & Messaging

We provide real-time community chat channels and private messaging to facilitate communication between builders:

  • Message Content: Your messages in channels and direct conversations, including text, images, GIFs, code snippets, polls, and emoji reactions, are stored to deliver them to recipients and maintain conversation history.
  • Channel Membership: When you join a chat channel, your membership, role (member, moderator, or owner), and notification preferences are stored.
  • Presence & Status: Your online/offline/away/do-not-disturb status and "last seen" timestamp are visible to other users in the chat. Typing indicators show when you are composing a message.
  • Read Receipts: We track when messages are read to provide unread count indicators and read receipt functionality.
  • Bookmarks & Pins: Messages you bookmark and messages pinned by channel moderators are tracked per user and per channel.
  • Search Indexing: Message content is indexed for full-text search to enable you to find past messages across channels.
  • Message Retention: Free accounts can access up to 90 days of message history. Pro subscribers receive unlimited history. Messages beyond the retention window may become inaccessible.
  • Moderation Data: Auto-moderation rules (word filters, spam detection) may analyze message content in real time. Moderation actions taken on your messages are logged.
  • Privacy: Messages in public channels are visible to all channel members. Direct messages are private between participants. We may access any message content to investigate reported abuse or violations of our Terms.

13. Events

When you create or participate in events:

  • Event Information: Event details including title, description, date, location, and attendee list are publicly visible.
  • RSVP Data: Your RSVP status (Going, Interested, Not Going) is visible to other users viewing the event.
  • Location Data: Physical event locations are displayed to help users find nearby gatherings. The same ~10 mile privacy offset applies.

14. Leaderboard and Karma System

We operate a public leaderboard and karma system to recognize community contributions:

  • Karma Points: We track karma points earned through your contributions (updates, comments, projects, engagement, helpful flags, peer reviews, streak milestones). This data is used to calculate your karma level.
  • Karma Levels: Your karma level (e.g., Newcomer, Contributor, Builder, Mentor, Legend) is publicly visible on your profile and the leaderboard.
  • Public Rankings: The leaderboard displays top builders ranked by karma. Your username, profile image, and karma score may appear publicly.
  • Backer Tier: The aggregate amount you have spent on sponsorships and crypto tips may be summarized into a public backer tier and displayed on the investor / backer leaderboard.

15. Builder Map

We display an interactive map showing the approximate locations of builders:

  • Map Display: If you provide a location, your approximate position is shown on the public builder map. The same ~10 mile privacy offset applies to protect your exact location.
  • Opt-In: Your location only appears on the map if you have added location information to your profile. You can remove your location at any time to be removed from the map.
  • Nearby Matching: Your approximate location may be used to help other builders find you through location-based matching.

16. Similar Builder Matching

We provide matching features to help builders find others with similar interests:

  • Building Category: Your selected building category (e.g., SaaS, Mobile App, eCommerce, Developer Tools, Fintech, Healthtech, Edtech, Marketplace, Agency, Content, Hardware) is used to match you with builders working on similar types of projects.
  • Tech Stack Matching: The technologies you list on your profile are used to find builders with overlapping tech stacks.
  • Interest Matching: Your declared interests help us suggest builders with shared goals and focus areas.
  • Visibility: Your building category, tech stack, and interests may be visible to other builders. You can update or remove this information at any time through your profile settings.

17. Wagers Token Game

If you participate in the Wagers token game, we record:

  • Wager Records: Your wager amount, outcome (win or loss), payout, and timestamp.
  • Wager Profile: Daily streaks, XP, level, mission progress, and aggregate statistics derived from your wagers.
  • Public Feed Events: Notable winning streaks may generate a public feed event linked to your account.
  • Server-Side Randomness: All randomness is generated and resolved on our servers; outcomes are recorded atomically alongside the corresponding token credits and debits.

18. Native Mobile Apps & In-App Purchases

If you use the Builders.to iOS or Android app, additional considerations apply:

  • Push Tokens: APNs / FCM device tokens are stored only after you grant notification permissions and are removed when you sign out, uninstall, or revoke permissions.
  • In-App Purchases: Purchases of digital goods inside the app (Pro / Founder's Circle subscriptions, token packs, mastermind subscriptions, playbook unlocks) are processed by Apple or Google. Apple and Google receive payment data per their terms; we receive only the transaction identifiers needed to grant your in-app entitlement.
  • Native Detection: The User-Agent header is used to detect the native shell so we can apply Apple App Store and Google Play in-app-purchase rules to digital-good purchases (returning a 451 to the web flow when the request originates from inside the app).

19. Cookies and Tracking

We use essential cookies to maintain your session and authentication state. These cookies are necessary for the proper functioning of our service. We may also use analytics tools to understand how users interact with our platform. We track views and clicks on projects, listings, and advertisements to provide analytics to content creators and advertisers.

20. Push Notifications

Our platform supports web push notifications through the Progressive Web App (PWA) functionality, and native push notifications through Apple Push Notification service (APNs) and Firebase Cloud Messaging (FCM) for our iOS and Android apps. Push notifications are entirely opt-in and require your explicit permission. You can manage or revoke push notification permissions at any time through your browser or device settings. We store push subscription data (endpoint URL and encryption keys for web push, device tokens for native push) only for users who opt in, and we automatically remove invalid tokens when delivery providers report them as unregistered.

21. Children's Privacy

Our services are not intended for children under 13 years of age. We do not knowingly collect personal information from children under 13. If you believe we have collected information from a child under 13, please contact us immediately.

22. International Data Transfers

Your information may be transferred to and processed in countries other than your country of residence. These countries may have data protection laws that are different from your country. We take appropriate safeguards to ensure your information remains protected.

23. Data Retention

We retain your information for as long as your account is active or as needed to provide services. We may retain certain information for legitimate business purposes, legal compliance, dispute resolution, or to enforce our agreements. Token transaction history, sponsorship and tip records, crypto purchase intents, and burn-paid subscription records are retained for audit and tax purposes. Pro, Founder's Circle, and Mastermind subscription data is retained for financial records. Platform connection tokens are deleted when you disconnect a platform. Chat message accessibility depends on your subscription tier (90 days for free accounts, unlimited for paid). Chat moderation audit logs are retained for platform integrity. On-chain transaction signatures and wallet addresses are permanently visible on the public Solana blockchain regardless of any deletion request. Anonymized analytics data may be retained indefinitely.

24. Changes to This Policy

We may update this Privacy Policy from time to time. We will notify you of any changes by posting the new Privacy Policy on this page and updating the "Last updated" date. Your continued use of our services after any changes indicates your acceptance of the updated policy.

25. Contact Us

If you have any questions about this Privacy Policy or our privacy practices, please contact us through our community channels: