PRIVACY AT 2ND BRICK
Your ideas stay yours.
This policy explains what information 2nd Brick uses to create, save, review, and fulfill a custom brick set.
What we collect
When you submit a custom set request, we store your contact and company details, design brief, reference images, requested size, quantity, budget, and timing. Your brief and reference images are only available to authorized reviewers. We use your email to confirm the request and follow up with your design. When you create an account, we receive basic account details such as your name, email address, and profile image. We also store the prompts, reference images, design preferences, generated models, build history, and feedback you choose to provide.
Orders and payments
If you order a set, we use the contact, shipping, and order information needed to quote, fulfill, and support it. Payments are processed by Stripe; 2nd Brick does not store your full payment-card number.
How we use information
We use your information to authenticate your account, generate and refine designs, save your projects, prepare instructions and quotes, fulfill orders, prevent abuse, and keep the service reliable.
Services we rely on
We share only the information needed with service providers that operate 2nd Brick, including authentication, hosting, database, payment, email, and AI model providers. Design prompts and reference images may be sent to model providers so they can generate and review your requested design.
Connected assistants and sharing
When you connect ChatGPT or another assistant using OAuth, we store the client identifier, account connection, creation and last-use times, request counts and revocation status. We do not store OAuth access tokens in the connection record. Tool results sent to your chosen assistant can include your credit balance, design prompts and titles, generated previews, kit prices, share links and order status. Tools act only on the connected account. Reference images and prompts needed to generate a design may be processed by our AI providers. Anyone with an enabled view-only share link can view that model; turn sharing off to disable the link. In Account → Agents you can revoke an assistant connection. Revocation stops further access but does not delete copies already returned to your assistant.
Your choices
You can update your account details from the account page. You can also ask us to correct or delete your account and associated projects by emailing noahsolomon2003@gmail.com.
Retention and security
Saved account records, design requests, prompts, reference images, generated models, build history, order records and assistant-connection records have no automatic expiry in our application database. We retain them until we manually delete them in response to a verified request, except records we need to fulfill an order, resolve a dispute or meet legal obligations. Revoking an assistant connection marks it revoked; it does not delete its stored history. Per-minute agent rate-limit records older than seven days are cleaned up when that connection is next used; inactive connections may retain them longer. Our production database currently has a one-day recovery-history window and no scheduled database snapshots. Our hosting plan provides one day of runtime logs; deployment build logs have no automatic expiry. Manually saved diagnostic and migration copies also have no automatic expiry and must be removed separately when we handle a deletion request. These settings do not establish a deletion deadline for every copy held by our other service providers. We do not promise immediate removal from backups or a fixed deadline for completing deletion requests. Contact support to request deletion and confirm what can be removed. We use access controls and established infrastructure providers to protect it, but no online service can promise absolute security.
Updates
We may update this policy as 2nd Brick changes. The current version is dated October 1, 2026.