Privacy Policy

1. Controller and contact

The controller responsible for the processing described in this Policy is:

No data protection officer has been appointed. Privacy requests may be sent to the contact address above in English or Spanish.

2. Personal data we process

• Account data: email address, password hash, verification and account status, Terms version and acceptance time, preferences, and authentication-session records.
• Profile data: username, display name, biography, social links, profile image, and public profile settings you choose to provide.
• Design and User Content data: uploaded source models, processed model data, titles, descriptions, tags, visibility and password-protection settings, branding, and related ownership records.
• Generated asset and usage data: images, videos, render definitions and status, design-processing events, plan limits, credit reservations and consumption, and deletion or archive status.
• Technical and security data: IP address, user agent, request and trace identifiers, timestamps, device/browser information, security events, and diagnostic or operational logs.
• Communication data: support, privacy, illegal-content, copyright, feedback, and other messages, plus any evidence or contact information you include.
• Billing data: Stripe customer, subscription, checkout and price references; plan and subscription state; payment events; and limited billing details returned by Stripe. BrickInView does not store full payment-card numbers.

3. Purposes and legal bases

Certain account information, including your email address, is necessary to create and maintain a BrickInView account. Payment and billing information requested by Stripe is necessary to purchase a paid subscription. If you do not provide the required information, we will not be able to provide the corresponding account or paid service.

4. Public and shared content

Your public username, profile details, and public designs may be visible through BrickInView profiles, discovery, listings, and galleries.

Public content is available broadly; unlisted content is available to people with its link; password-protected content is available through the protected access flow; and private content is intended for the owner. Choose carefully and do not publish personal or confidential information you do not want others to see.

Changing visibility or deleting content cannot necessarily remove copies already downloaded, shared, indexed, or cached by other people or independent services.

5. How files and renders are processed

Source files are uploaded to BrickInView storage, validated and normalised, then processed to create model, image, and video assets. Processing metadata and status are connected to your account and design.

Specialist conversion and rendering workers may temporarily access files and technical instructions to perform the requested job. Browser-based rendering technology may also request part images and metadata needed for the design.

6. Payments

Stripe processes checkout, payment methods, recurring charges, billing-management sessions, refunds, and related fraud prevention. Stripe receives information you submit in checkout and technical information required to process the transaction under its own privacy terms.

BrickInView stores provider identifiers and subscription, checkout, price, plan, invoice-event, cancellation, credit, and entitlement state needed to operate billing. Full card credentials remain with Stripe.

7. Recipients and service providers

• Microsoft Azure services: application hosting, database, blob storage, messaging, and operational email delivery.
• Stripe: checkout, payment, subscription, customer-portal, refund, and billing-event processing.
• Cloudflare Turnstile: automated-abuse protection during relevant account actions.
• PostHog: production product analytics configured for cookieless, anonymous operation without user profiles or persistent identifiers.
• Rebrickable: part metadata and image delivery. Direct image requests can disclose your IP address, browser/device data, requested image, and request time to Rebrickable or its delivery providers.

8. International processing

BrickInView's core production infrastructure is hosted using Microsoft Azure in the East US region in the United States. Personal data relating to users in the European Economic Area may therefore be transferred to and processed in the United States. Microsoft provides safeguards for international transfers under its Data Protection Addendum, including the European Commission's Standard Contractual Clauses. Further information about Microsoft's international-transfer safeguards is available in Microsoft's data-protection and compliance documentation.

9. Retention

• Account, profile, design, and entitlement records are generally kept while your account is active and then deleted or anonymised when no longer needed, subject to the specific periods and legal exceptions below.
• Uploaded source and normalised processing files: ordinarily four days after processing reaches a terminal state.
• Design records and generated images/videos: until you delete them, delete the design or account, or a plan-retention rule applies.
• Designs archived after downgrade: currently at least 180 days before excess designs may be deleted. Design-view records and GLB access records containing IP address/user-agent data: 180 days.
• Internal processing traces: currently 90 days. Expired refresh-token records: currently an additional 60 days. Other production security and application-log retention is 90 days.
• Billing and transaction records: for 365 days, including longer retention where tax, accounting, fraud-prevention, or legal-claims rules require it.
• Support, privacy, content-reporting, and legal communications: for 365 days, or longer where needed to handle a request or establish, exercise, or defend legal claims.
• Deleted data may remain in protected backups for 90 days, isolated from ordinary use until overwritten, unless law requires longer preservation.

10. Deletion controls

Available controls let you delete designs and individual generated images or videos. Deletion requests trigger removal of associated records and assets, subject to reasonable processing time, backups, security evidence, and legal retention duties.

Account deletion is available in the service and starts deletion of associated account data and subscription cancellation. Download anything you need first. Certain minimal billing, fraud, legal, or audit records may be retained where required or justified.

11. Cookies and browser storage

BrickInView uses strictly necessary authentication and security cookies, including an HttpOnly refresh cookie, a session marker, and a temporary password-access cookie for protected designs. These support requested login and access functions.

Local or session browser storage may keep authentication restoration data, diagnostic log preference, and temporary workspace navigation state. Clearing browser data may sign you out or reset these preferences.

PostHog is configured in production in cookieless mode with persistence disabled and without user profiles. BrickInView does not intend to use analytics cookies or persistent analytics identifiers under that configuration.

Stripe, Cloudflare Turnstile, Rebrickable, or other independently loaded services may process technical data or use storage under their own rules when their functions are requested.

12. Anonymous product analytics

BrickInView uses PostHog to measure anonymous aggregate product interactions and diagnose product-flow problems. The configured integration avoids user identification, profiles, persistence, autocapture, session recording, performance capture, and automatic exception capture.

Only deliberately selected events and sanitised properties are sent; URLs and custom properties are filtered to avoid obvious identifiers. Anonymous technical data can still be personal data in context, so it is protected and subject to the retention and transfer facts that must be confirmed before launch.

13. Emails

We send transactional messages needed for verification, security, account administration, billing, requested renders, support, and legal or moderation communications.

Promotional email is optional. You may withdraw your choice through available settings or by contacting contact@support.brickinview.com. Withdrawal does not affect transactional messages needed to provide or secure the service.

14. Security

We use technical and organisational measures designed to protect personal data, including hashed passwords, restricted access, secure transport, security tokens, and provider access controls. No system is perfectly secure. Keep your password confidential and report suspected compromise to contact@support.brickinview.com.

15. Age requirement

BrickInView accounts are intended only for people aged 18 or older. We do not knowingly offer accounts to children. Contact contact@support.brickinview.com if you believe a minor has created an account or supplied personal data.

16. Your data-protection rights

Depending on where you live and the circumstances, you may have rights to:

• request access to and a copy of your personal data, and information about its processing;
• correct inaccurate data or request erasure where the legal conditions are met;
• restrict processing in specified circumstances;
• object to processing based on legitimate interests or to direct marketing;
• receive certain data in a portable format or ask that it be transferred where technically feasible; and
• withdraw consent at any time for future consent-based processing.

Send a request to contact@support.brickinview.com. We may ask for information reasonably necessary to verify identity and scope. You may also appoint an authorised representative where applicable. We will respond within the period required by law.

You may complain to your local supervisory authority. In Spain, this is the Agencia Española de Protección de Datos (AEPD), at www.aepd.es. We encourage you to contact us first so we can try to resolve the concern.

17. Automated decisions

BrickInView does not currently make decisions based solely on automated processing that produce legal or similarly significant effects. Automated validation, abuse prevention, rendering, and plan-limit checks support service operation and may be reviewed when appropriate.

18. Legal disclosures and business changes

We may disclose data when reasonably necessary to comply with law, respond to competent authorities, protect users and rights, investigate wrongdoing, or establish or defend legal claims. If the service or its assets are reorganised or transferred, data may be disclosed under appropriate confidentiality and data-protection safeguards.

19. Changes to this Policy

We may update this Policy when processing, providers, or law changes. The current effective date will be shown above, and we will provide appropriate notice of material changes.

20. Contact