1. Scope and responsibilities

This Privacy Notice explains how PLEXBLD handles personal information on public pages and in individual accounts, approved project workspaces, project sources, project agents, mobile collection, reality capture, review activities, and support. It applies to account holders, project contributors, people appearing in project material, public-page visitors, and people who contact PLEXBLD.

The organization or other project party responsible for a project often determines why project information is collected and used. In that situation, that party is responsible for participant notices, lawful instructions, access decisions, and rights requests, while PLEXBLD handles information to provide the agreed service. For account administration, security, public-page operation, service improvement, and legal compliance, PLEXBLD may determine its own purposes and responsibilities under applicable law.

2. Account and optional affiliation information

PLEXBLD collects the name, email address, password-protection record, account status, notice versions, and acceptance times needed to create and protect an individual account. A person may also provide a position or project role, telephone number, preferred language, time zone, country, or later project-affiliation information. Organization affiliation is not required to create an account, and signup does not record a claim that the person represents an organization or already has project authority.

Email verification confirms control of an address. It does not independently confirm identity, employment, company registration, title, project membership, or authority.

3. Public-page and enquiry information

When a person visits a public page, PLEXBLD may record a randomly generated visit and session reference, page viewed, date and time, time engaged, general device category, country or region supplied by the network service, referring-site host, and campaign labels contained in the page address. Public-page measurement is used to understand interest, improve communication, prevent abuse, and assess page performance.

PLEXBLD does not need the visitor’s name or message contents for this measurement. Individual public-visit records are scheduled for removal after 90 days; aggregated daily measurements may be retained longer because they no longer describe a named account. A person who contacts PLEXBLD may also provide identity, contact details, organization information, enquiry content, and correspondence history.

4. Account activity and security information

PLEXBLD may process sign-in and verification events, session and device information, account changes, project-access actions, failed or suspicious activity, rate-limit events, audit records, support actions, and incident information. This information is used to authenticate users, protect accounts and projects, investigate misuse, recover service, and demonstrate accountable operation.

5. Project information

Project information can include project identity, location, dates, scope, stakeholder roles, contracts, obligations, schedules, quantities, commercial records, drawings, models, reports, approvals, quality and safety records, photographs, video, audio, site observations, correspondence, authorship, signatures, actions, review decisions, and evidence supplied by project participants.

Personal information within project material can include names, work contact details, job roles, appearance, voice, messages, activity, location within a site, document authorship, and decisions. Organizations should avoid submitting unrelated personal information and should apply additional approval and safeguards before submitting sensitive information.

6. Approved project sources and agents

Only after PLEXBLD activates an account, assigns the relevant project responsibility, and an actually authorized participant intentionally configures or uses a project source may PLEXBLD receive, retrieve, copy, store, organize, and analyze project-relevant content and attachments from the approved scope. Sources may include a dedicated project email address or mailbox, a workplace collaboration service, a messaging or social-media channel, a mobile collection connection, or another supported project system.

A PLEXBLD project agent may operate within the approved source boundary where it is deliberately deployed. The connection does not authorize access to unrelated personal messages, unrelated folders, unrelated groups, unrelated accounts, or other content outside that project boundary. Creating an account, accepting this notice, receiving platform activation, or receiving project access does not by itself create or authorize a source connection. Before connection, the participant must have actual authority, provide required participant notices or permissions, and remove or pause access when it is no longer appropriate.

7. Information created from project material

PLEXBLD may create structured records, extracted values, summaries, classifications, links, duplicate indicators, confidence information, geometry, visual masks, possible issues, progress or constraint indicators, review status, and action suggestions from submitted project information. These derived records remain connected to the relevant project and should be treated as working evidence until appropriately reviewed.

8. Purposes of handling

Personal and project information may be used to:

• create, verify, activate, administer, and support accounts and subscriptions;
• register projects and apply project-access boundaries;
• receive, organize, preserve, retrieve, and present project information;
• connect records to activities, locations, responsibilities, and review status;
• support planning, coordination, progress, quality, safety, commercial, and reality-capture workflows;
• provide automated analysis selected for the project and support required human review;
• send account, project, security, and service communications;
• measure public-page performance and improve user guidance;
• prevent abuse, protect confidentiality, maintain records, investigate incidents, and recover service;
• meet contractual, accounting, regulatory, and legal obligations; and
• establish, exercise, or defend legal claims.

9. Lawful grounds

Depending on the person, project, location, and purpose, handling may be necessary to perform a contract or take requested steps before a contract; comply with law; protect a person’s vital interests; carry out legitimate interests in secure and effective construction-project administration; follow the responsible project party’s lawful instructions; or act on consent where applicable law requires it.

Signup separately records agreement to the Account Terms, acknowledgement of this notice, acceptance of the promise not to connect or submit a project source without approved project responsibility and actual authority, and acknowledgement of automated processing. Signup does not record a claim of organization representation or authorize a source connection. A privacy-notice acknowledgement confirms receipt; it is not treated as consent for every purpose where another lawful ground applies. A person may withdraw a consent-based permission without affecting earlier lawful handling, but some service functions may then be unavailable.

10. Automated analysis, VGGT, and SAM 3

When a relevant project function is selected and available, PLEXBLD may use automated methods to extract, classify, summarize, compare, connect, or prioritize project information. Reality-capture work may use VGGT, the Visual Geometry Grounded Transformer, to estimate camera and scene geometry from selected images or video frames. Visual review may use Meta’s Segment Anything Model 3 (SAM 3) to detect, segment, or track prompted visual concepts in selected images or video.

PLEXBLD uses the commercial-use VGGT-1B-Commercial checkpoint under the VGGT License and uses SAM 3 under the SAM License. Naming a model does not mean its publisher receives or processes project information. Any organization that actually receives information is addressed under this notice and the applicable project agreement. The reference to SAM 3 does not promise SAM 3.1 or a later public release.

Inputs can include project images, video frames, prompts, project references, and information needed to perform and validate the selected task. Outputs can include estimated camera relationships, scene points, visual regions, masks, tracks, confidence information, and later records derived from those results. These outputs are supporting reality-data inputs rather than project decisions. The authorized project management team and relevant qualified professionals consider them with the wider project record and retain responsibility and final decision authority.

Automated results can be incomplete, inaccurate, biased, or misaligned. PLEXBLD does not intend these tools to make an unreviewed decision that produces legal or similarly significant effects for a person. Qualified human review is required before a result materially affects safety, payment, quality, employment, design, compliance, or programme decisions. A person can ask the relevant project organization for review of a result concerning them.

The signup acknowledgement does not by itself authorize private project information to train a general-purpose model for unrelated customers. A materially different training purpose requires an applicable written agreement or separate notice and lawful ground.

11. Who receives information

Information may be available to permitted project participants, people assigned to review or support the project, and the organization or project party that controls the relevant project source. Visibility depends on centrally assigned project access, project role, and configuration.

PLEXBLD may use service providers for hosting, storage, communication delivery, account protection, security, support, and approved processing. Providers should receive only information reasonably needed for their task and must act under appropriate confidentiality, security, and use restrictions. A connected email, workplace, messaging, or social-media provider also handles information under its own notice and account terms.

Information may be disclosed to professional advisers, auditors, insurers, a purchaser or successor in a properly controlled business transaction, public authorities where legally required, or others where necessary to protect rights, safety, users, projects, or service integrity.

12. International handling

Account, project, communication, storage, support, or processing services may operate in more than one country. This can result in personal information being handled outside the person’s country or project location. Where applicable law requires it, PLEXBLD and the responsible organization should use an approved transfer mechanism and appropriate contractual, technical, and organizational safeguards.

Before rollout on a project with location or residency restrictions, the organization should confirm the approved service region, project requirements, and any required transfer assessment.

13. Retention

Account and organization information is retained while the account is active and for a reasonable period afterward to manage closure, security, billing, disputes, and legal obligations. Project information is retained according to the applicable agreement, project instructions, contractual record duties, review and audit needs, and legal requirements.

Information may remain longer where it is subject to legal hold, investigation, unresolved project action, audit-integrity safeguard, backup cycle, or another lawful preservation requirement. When retention is no longer justified, information is deleted, de-identified, or placed beyond ordinary use. Disconnecting a project source stops new collection where supported but does not automatically erase information already admitted to the project or retained for an approved reason.

14. Security

PLEXBLD uses proportionate safeguards such as email verification, account and project access controls, protected sign-in, secure sessions, audit records, project separation, input controls, size and rate limits, integrity checks, restricted service access, and incident procedures. Providers and project organizations also have responsibilities for their own systems and users.

No service can guarantee absolute security. Use a unique password, protect signed-in devices, restrict shared accounts and project sources, review active connections, remove access promptly, and report suspected loss, disclosure, or compromise to [email protected]. Do not include confidential project material in an initial email report unless PLEXBLD provides an approved secure method.

15. Account and participant controls

An individual can correct available account-profile information and request account closure. Only a participant with the assigned project responsibility and actual authority may manage a project source, pause or remove a supported connection, or request a project-level export, correction, retention change, or closure. PLEXBLD controls account activation and project assignment separately. Some actions may require identity verification, project authority, coordination with another responsible project party, or preservation of required records.

Project contributors should first contact the organization or project party responsible for the project because that party determines the project purpose and can identify the relevant source and record. PLEXBLD will assist that party where required.

16. Individual rights

Depending on applicable law, a person may have rights to information, access, correction, deletion, restriction, objection, portability, withdrawal of consent, complaint to a regulator, or human review of certain automated outcomes. Rights can be limited where another person’s rights, project confidentiality, legal claims, professional records, contract requirements, or law requires preservation.

Send a request to [email protected] and identify the relevant organization and project without including unnecessary confidential material. PLEXBLD may verify identity and authority and may direct the request to the organization responsible for the project.

17. Children and vulnerable people

PLEXBLD accounts are not intended for children. Project parties must not intentionally connect a child’s personal account or collect information about a child through a project source unless the project has a lawful, necessary purpose and appropriate authorization and safeguards. Extra care is also required for vulnerable people and for images or recordings captured in occupied or public areas.

18. Updates and acceptance records

This notice is identified by version and effective date. PLEXBLD may update it when services, project sources, providers, law, or processing purposes materially change. Material changes will be communicated through the account, verified contact address, or another appropriate method, and renewed acknowledgement or authorization will be requested where required.

The signup record may preserve the individual account, notice versions, acknowledgement and acceptance times, and relevant security or audit information so PLEXBLD can demonstrate what was presented and accepted. It does not record organization representation or project-source authority merely because a person registered.

19. Contact

Questions, requests, complaints, and security concerns can be sent to [email protected]. The applicable order or account notice should identify the operating legal entity, registered contact details, and any required privacy representative or data-protection contact for the relevant service and jurisdiction.