Skip to main content

Privacy Policy

Last Updated: October 4, 2026

Effective: October 4, 2026

1. Introduction

Brick Party ("we," "our," or "us") is operated by Brick Apps LLC, an Oregon limited liability company in the United States.

We are committed to protecting your privacy. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use our LEGO set inventory management application (the "Service"). By using the Service, you agree to the collection and use of information in accordance with this policy.

2. Information We Collect

Account Information

When you create an account, we collect your email address, display name, and authentication provider identifier. If you sign up with Google, we receive your email address and display name via Google OAuth (using the openid, profile, and email scopes). If you sign in with Apple in our iOS app, we receive your email address, which may be an Apple private relay address; we do not store your name.

Payment Information

For paid subscriptions, our payment processor Stripe collects payment information. We do not store full credit card details on our servers. We keep your subscription tier and status, and a history of your invoices and refunds: amounts, dates, and Stripe reference ids.

Referral Information

Once, when you sign up, we record how you found us: the page you landed on, the site that referred you, any campaign tags in the link, an ad click identifier if you arrived from an ad, a promo code if you redeem one, and whether you signed up on the web or in an app. If you sign up by email, this is held for up to 24 hours against a hashed copy of your email address; if you check out before your account exists, it is held for up to 24 hours under a random reference. Either way it is then attached to your account.

Inventory Data

We store LEGO set numbers, part quantities, and collection preferences.

Connected Accounts (Rebrickable and Brickset)

If you connect your Rebrickable or Brickset account, you enter that account's username and password once. We send them to Rebrickable or Brickset to obtain a user token (for Brickset, a user hash) and do not store your password. We store the token, encrypted with AES-256-GCM, and your username for that service on our servers. We use the token only when you ask us to, to read and add sets in your account there and, for Rebrickable, to create part lists and add parts to them. Disconnecting the account in account settings deletes the token and username.

Identify Feature (Images)

When you use the "Identify" feature, we transmit the image you provide to Brickognize for processing. We do not permanently store these images on our servers.

Usage Information

We collect information about search queries and feature usage counts to enforce tier quotas and improve the application.

When you are signed in, we keep a record of your account activity: when you created your account and last signed in, when you last changed your collection, the sets you recently viewed, the parts you recently identified, the Search Parties you hosted, and your progress on the sets you track. Our staff can view this record alongside your email address, username, and subscription to provide support, prevent abuse, manage complimentary access, and understand how the Service is used. We also combine these records into overall statistics, such as how many people are active each day.

We use PostHog for anonymous, cookieless product analytics. This collects page views, feature usage events, and basic device information (browser type, screen size). No persistent identifiers or cookies are used for analytics purposes.

Feedback

When you send feedback through the Service, we store your name, email address, message, and the category you chose so we can review and respond to it.

Request Information

Our hosting provider, Vercel, processes technical details of each request to the Service, such as your IP address and browser user agent. We review this only as combined traffic totals, such as request counts by page or by user agent, to detect automated traffic and manage costs. It is not linked to your account.

3. How We Use Your Information

  • Provide and maintain the inventory tracking service
  • Sync your data across devices when signed in
  • Manage your subscription and process payments via Stripe
  • Send occasional service communications about new features and important updates to the Service
  • Analyze usage patterns, both anonymous analytics and your account activity, to improve the application
  • Measure which referral sources lead to signups, activity, and subscriptions
  • Grant complimentary or promotional access to paid tiers
  • Enforce fair use quotas and subscription tier limits
  • Respond to support requests
  • Prevent fraud and abuse

Service Communications

From time to time, we may send you emails about new features, product updates, and important changes to the Service. These are service communications, not marketing — we do not send promotional offers, discounts, or upsell emails.

You can opt out of service communications at any time by clicking the unsubscribe link included in any such email. Opting out will not affect transactional emails required for your account (such as password resets, billing notices, or security alerts).

4. Data Storage and Security

Your data is stored securely using industry-standard encryption. We use Supabase (PostgreSQL) for server-side storage and IndexedDB for local browser storage. Anonymous users' data is stored only locally and is never transmitted to our servers.

5. Third-Party Services

We use the following third-party services:

  • Vercel — Hosting; processes request details such as IP address and user agent
  • Supabase — Authentication and data storage
  • Sign in with Apple — Sign-in in our iOS app; Apple gives us your email address (possibly an Apple private relay address); we do not store your name
  • Stripe — Subscription management and payment processing
  • Google Ads (and Microsoft Advertising when we advertise there) — Conversion reporting, performed server-side with no scripts or cookies from either. If you arrived from one of their ads, we send the ad click identifier, the event (signup, trial start, or first payment), its time, and its value.
  • PostHog — Anonymous product analytics
  • Sentry — Error monitoring and reporting
  • Vercel Analytics — Page view and performance metrics
  • Vercel Speed Insights — Core Web Vitals monitoring
  • Rebrickable — LEGO catalog data; if you connect your Rebrickable account, receives your username and password once to issue a token, then the sets and parts you choose to sync or add to a list
  • Brickset — If you connect your Brickset account, receives your username and password once to issue a user hash, then the sets you choose to sync
  • Brick Owl — Pricing and catalog ID lookups; receives only part, set, and minifigure identifiers, never your personal information
  • BrickLink — Pricing and minifigure data
  • Brickognize — Part identification processing

Each service has its own privacy policy governing the use of your information.

6. Your Data Rights

GDPR Rights (EU Users)

You have the right to:

  • Access your personal data
  • Rectify inaccurate data
  • Erase your data (right to be forgotten)
  • Restrict processing of your data
  • Data portability
  • Object to processing
  • Withdraw consent at any time
  • Lodge a complaint with your local supervisory authority

CCPA Rights (California Residents)

You have the right to:

  • Know what personal information is collected
  • Delete personal information
  • Opt-out of sale of personal information (note: we do not sell personal information)
  • Non-discrimination for exercising privacy rights

All Users

You can:

  • Delete your account and all associated data via account settings. Referral and invoice records are anonymized rather than deleted, keeping only the channel and campaign tags, dates, and amounts, with nothing that identifies you, so our revenue totals stay correct. If we granted you complimentary access, the record of that grant (your email address, the tier, its expiry, and our note on why) is kept until you ask us to remove it.
  • Download a Backup file through account settings. It holds your tracked sets (with their status and whether you have the instructions and box), owned piece counts, loose parts, lists and the items in them, minifigures, and your theme and pricing preferences. It does not include your account details, profile, MOCs, or billing history.
  • Contact us for any other data rights request

7. Cookies and Tracking

  • We use essential cookies for authentication and session management.
  • We use local storage (IndexedDB) to cache catalog data and store your inventory preferences locally.
  • PostHog operates in cookieless mode (memory-only persistence, no persistent identifiers).
  • We do not use third-party advertising cookies or tracking pixels.
  • If the link you arrive on carries an ad click identifier, it is saved with your account when you sign up, to count whether the ad led to a signup.

8. Data Retention

  • Account data is retained until you delete your account. We do not automatically purge inactive accounts.
  • Group session data (Search Party): ended sessions and participant records are deleted 30 days after the session ends.
  • Pricing observations: deleted after 180 days.
  • Usage counters: deleted when the tracking window expires.
  • Webhook events: deleted 30 days after processing.
  • Ad click identifiers: deleted 90 days after signup.
  • Referral information held before an account exists: deleted after 24 hours.
  • Referral and invoice records: anonymized when you delete your account, keeping only the channel and campaign tags, dates, and amounts.
  • Complimentary access grants: kept after you delete your account until you ask us to remove them.
  • Anonymous users: all data is stored locally in your browser (IndexedDB) and is never transmitted to our servers.

9. Data Breach Notification

In the event of a data breach affecting your personal information, we will notify affected users via email within 72 hours of discovering the breach.

10. International Data Transfers

Our services (Supabase, PostHog) are hosted in the United States. If you access the Service from outside the United States, your data may be transferred to and stored in the United States.

11. Do Not Track

We do not currently respond to Do Not Track browser signals. However, our analytics operate in cookieless mode and do not persistently track users across sessions.

12. Artificial Intelligence

We do not use your personal data or inventory data to train machine learning or artificial intelligence models.

13. Children's Privacy

Our service is not intended for children under 13. We do not knowingly collect personal information from children under 13. If you are a parent or guardian and believe we have collected information from your child, please contact us at stud@brick-party.com.

14. 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" and "Effective" dates.

15. Contact Us

If you have questions about this Privacy Policy, please contact us at stud@brick-party.com or through the feedback form in your account settings.

LEGO® is a trademark of the LEGO Group. Rebrickable® is a trademark of Rebrickable Pty Ltd. BrickLink® is a trademark of BrickLink Corporation (LEGO Group). This application is not affiliated with, sponsored by, or endorsed by any of these companies.

© 2026 Brick Apps LLC

Privacy Policy | Brick Party - Find, Sort, Build