1. Scope
This Privacy Policy explains how LGSF Market collects, uses, stores, protects and shares information when users access the website, create accounts, upload IFC files, generate previews, use viewer tools, share links, publish listings, request support or otherwise use the Service.
2. Information collected
The Service may collect account information, email address, display name, company information, country, profile details, authentication records, upload activity, model processing records, asset IDs, file hashes, share-link activity, export activity, device information, browser information, IP address, timestamps, support communications and payment or marketplace records where applicable.
3. Information from signup providers
If users sign up or sign in with providers such as Google or Apple, the Service may receive account identifiers, email address, name, profile image, authentication status and related security information according to the provider settings and the user consent flow.
4. Public profile, Lobby and Market information
Some profile and publishing information may become public when users choose to publish it, including display name, company name, avatar, biography, links, software skills, model titles, descriptions, tags, preview images, Lobby cards, Market listings, pricing or license statements. Users should not publish confidential or sensitive information in public fields.
5. Uploaded files and model data
Uploaded IFC files, derived model previews, 2D drawings, object properties, frame groups, thumbnails, PDF, CSV, CNC-oriented outputs and related processing metadata are handled to provide upload, viewing, review, collaboration, export, storage, sharing, marketplace and support features. Source files and detailed model data are not intended to be public by default unless the user chooses a sharing, Lobby or Market publishing path.
6. How information is used
Information is used to operate the Service, create browser-ready previews, maintain member workspaces, process files, provide support, verify account activity, secure uploads, prevent abuse, investigate complaints, enforce platform terms, improve reliability, deliver notifications, process payments where applicable and comply with legal obligations.
7. Legal bases and user consent
Depending on the user location and the feature used, processing may be based on contract performance, user consent, legal obligations, legitimate interests in operating and securing the Service, protection against abuse or the need to carry out user instructions for upload, processing, sharing, export, marketplace or support workflows.
8. Cookies and similar technologies
Cookies, local storage and similar browser technologies may be used for login sessions, security, upload state, interface preferences, diagnostics, analytics and consent controls. Non-essential cookies should be controlled through a consent mechanism where required by law.
9. Marketplace, payment and transaction information
If marketplace or paid features are enabled, the platform or its payment providers may process billing details, payment status, purchase history, seller information, buyer information, tax-related information, invoices, refunds, dispute records, download events and transaction-support communications.
10. Automated processing and recommendations
The Service may use automated processing to generate previews, extract model data, detect abuse, prevent spam, recommend content, improve search, classify assets, enforce plan limits and secure accounts. Private IFC files and source-file data should not be used for third-party generative AI training by default without separate permission or a clearly stated lawful basis.
11. Service providers and sharing
Information may be shared with service providers that support hosting, cloud storage, authentication, email delivery, security monitoring, analytics, payment processing, customer support, file processing, marketplace operations, legal compliance or abuse investigation. Service providers should process information only as needed to provide services to LGSF Market.
12. International processing
The Service may be accessed internationally and may rely on cloud infrastructure or service providers located in different countries. Where required, appropriate transfer safeguards, contractual controls or other legal mechanisms should be used for international personal-data transfers.
13. Retention
Account records, upload records, acceptance logs, file hashes, asset IDs, transaction records, support records, security logs and complaint records may be retained for as long as needed to operate the Service, provide user workspaces, maintain backups, enforce terms, resolve disputes, prevent abuse, comply with law and defend legal claims.
14. Security
LGSF Market should maintain administrative, technical and organizational safeguards designed to protect account data, uploads, processing records and platform systems against unauthorized access, loss, misuse, alteration and disclosure. No online service can guarantee absolute security.
15. User rights and choices
Depending on applicable law, users may have rights to access, correct, delete, restrict, export or object to certain processing of personal data. Users may also manage account information, communication preferences, cookie settings and published or shared model access through account controls when available.
16. Communications and notifications
Users may receive service emails related to account verification, password reset, upload processing, security alerts, share-link activity, marketplace transactions, plan changes and important policy updates. Marketing or product emails should be controlled through preference or unsubscribe options where required by law.
17. Children and professional use
The Service is designed for professional, business and project workflows, not for children. The production policy should specify the minimum permitted age and the process for handling personal data if the platform learns that a child account or child data was submitted without proper authority.
18. De-identified and aggregated data
The platform may use aggregated or de-identified operational data to measure product performance, improve upload reliability, understand feature usage, detect abuse, plan infrastructure and develop safer workflows, provided the data is not used to identify a specific user or reveal private source files.
19. Updates and contact
This policy may be updated when the Service, legal requirements, data practices, plans, marketplace features or service providers change. The production version should publish a support contact, legal notice address and company information for privacy requests.