Privacy Policy

This Privacy Policy describes how Opti-mized Solutions Inc. and its affiliated entities, where applicable (collectively, “Opti-mized,” “we,” “us,” or “our”) collect, receive, access, use, process, store, disclose, protect, retain, and otherwise handle information in connection with our websites, software platforms, hardware products, services, reports, communications, purchasing processes, customer support activities, and related business operations.

This Privacy Policy is intended to apply broadly to information that we collect or receive through your interaction with Opti-mized, whether that interaction occurs directly through our website or platform, through connected hardware deployed at a facility, through communications with our team, through purchasing or support activities, or through other products and services that expressly reference or link to this Privacy Policy.

Depending on how you interact with Opti-mized, different portions of this Privacy Policy may apply to you. For example, a visitor browsing our public website may provide significantly less information than an authorized user managing a facility through the Opti-mized platform. Similarly, a customer purchasing hardware may provide different information than a facility representative submitting electrical panel photographs or a user reviewing facility performance information through the dashboard.

For purposes of clarity, this Privacy Policy applies to information collected through or in connection with the following.

The Opti-mized Website and Related Webpages

This Privacy Policy applies to information collected through the Opti-mized website and any webpages, landing pages, informational pages, forms, interactive tools, resource pages, demonstration pages, product pages, support pages, contact pages, or other online experiences operated by Opti-mized that link to or reference this Privacy Policy.

This may include information provided when you browse our website, request information, submit a contact form, request a demonstration, communicate with our team, download materials, request access to a product or service, begin a facility setup process, subscribe to communications, or otherwise interact with features made available through the website.

Information collected through our website may also include technical and usage information associated with your interaction with the website, such as browser type, device type, operating system, approximate geographic region, referring pages, pages viewed, time spent on certain pages, navigation activity, interactions with forms or website features, and similar information that may be collected through cookies, analytics technologies, server logs, or comparable technologies.

The fact that this Privacy Policy applies to our website does not necessarily mean that we collect all categories of information described in this Privacy Policy from every website visitor. The information collected depends on how you use and interact with the website.

This Privacy Policy applies to information collected, generated, transmitted, displayed, stored, processed, or otherwise handled through the Opti-mized web platform, including customer dashboards, facility dashboards, administrative interfaces, analytics tools, energy intelligence features, equipment views, reporting functions, notifications, configuration tools, and other platform functionality.

The Opti-mized platform may receive and process information relating to facilities, electrical systems, connected equipment, energy consumption, electrical behaviour, equipment operation, runtime patterns, demand, operating schedules, facility configuration, device connectivity, hardware status, detected conditions, calculated opportunities, estimated savings, historical performance, and other information associated with the services provided by Opti-mized.

The platform may also process information generated from analysis of collected data. This can include calculated values, classifications, operating patterns, comparisons, baselines, trends, detected changes, alerts, estimated opportunities, equipment-level observations, and other information produced through automated or manual analysis.

Information displayed within the platform may originate from several sources, including information entered by authorized users, information collected through Opti-mized hardware, information provided by customers or facility representatives, information generated by the Opti-mized platform, information obtained from authorized integrations, and information created as part of technical or customer support activities.

Opti-mized User Accounts

This Privacy Policy applies to information collected and processed in connection with the creation, administration, authentication, maintenance, and use of Opti-mized user accounts.

This may include information such as a user's name, business or organization name, email address, telephone number, role, facility association, account permissions, access credentials, account status, login activity, authentication information, user preferences, communication preferences, and other information necessary to provide and administer access to Opti-mized services.

Where an account is associated with an employer, municipality, organization, property owner, facility operator, consultant, contractor, or other customer, certain information relating to the user's access or activities may also be available to authorized administrators of that organization, subject to applicable agreements, permissions, and platform functionality.

Users may be granted different levels of access depending on their role. For example, some users may be permitted to view only certain facilities, reports, dashboards, systems, or equipment, while other users may have administrative permissions relating to an organization or multiple facilities.

Account-related information may also be used to maintain security, detect unauthorized access, troubleshoot platform issues, administer user permissions, communicate important service information, and maintain records relating to customer and user activity.

Opti-mized Hardware, Sensors, Gateways, and Connected Equipment

This Privacy Policy applies to information collected, transmitted, received, generated, or processed through Opti-mized hardware and connected systems, including sensors, current transformers, gateways, communications equipment, circuit-level measurement devices, related accessories, firmware, and associated technologies deployed in or around customer facilities.

Depending on the configuration of a particular installation, Opti-mized hardware may collect or transmit information relating to electrical characteristics, energy consumption, current, voltage, load behaviour, operating patterns, equipment activity, circuit activity, equipment runtime, cycling, demand, changes in electrical behaviour, timestamps, equipment or circuit identifiers, connectivity status, signal quality, gateway status, device configuration, diagnostic information, and similar operational or technical information.

The nature and extent of information collected may vary depending on the type of hardware installed, the configuration selected by the customer, the equipment being measured, the capabilities of the applicable device, and the services enabled for the customer.

Opti-mized hardware is generally intended to collect information relating to facility systems, energy use, electrical behaviour, and equipment operation rather than information relating to the private activities of individuals. However, certain operational information may indirectly reflect patterns associated with the use or occupancy of a facility. For example, energy usage patterns may indicate that equipment is operating during certain periods or that facility activity has changed.

Information transmitted from hardware may be processed by the Opti-mized platform in order to provide analytics, dashboards, reports, alerts, calculations, equipment insights, performance comparisons, diagnostics, service functionality, and other features.

Facility Setup and Configuration Forms

This Privacy Policy applies to information submitted through facility setup, configuration, onboarding, assessment, quotation, pre-order, installation, or similar forms provided by Opti-mized.

These forms may request information needed to understand a facility and determine an appropriate system configuration. Depending on the service being requested, this information may include the name or description of a facility, facility type, approximate facility size, electrical distribution information, number and type of electrical panels, motor control centres, switchgear, circuits, equipment, utility information, installation characteristics, contact details, project information, and other information relevant to determining hardware, installation, service, or reporting requirements.

Facility setup information may also be used to create equipment records, prepare account or platform configurations, generate quotations, estimate hardware requirements, assist with installation planning, support commissioning activities, and provide ongoing services.

Where a facility setup process allows a user to save progress and return later, Opti-mized may also process identifiers, reference codes, contact information, or similar information necessary to associate a user with a previously created facility setup.

Information provided through these processes may become part of a customer's ongoing facility configuration or account records.

Facility Intelligence Reports and Similar Reports

This Privacy Policy applies to information contained in, used to prepare, or generated as part of Facility Intelligence Reports, energy reports, equipment reports, opportunity reports, performance reports, analytical reports, summaries, dashboards, assessments, recommendations, and similar materials provided by Opti-mized.

These reports may incorporate information collected through Opti-mized hardware, information provided by customers, historical energy information, facility information, equipment information, operational data, environmental or contextual information, calculations, assumptions, estimated savings, identified opportunities, equipment observations, and analytical outputs generated through the Opti-mized platform.

Reports may be generated automatically, manually, or through a combination of automated analytics and professional review.

Reports may also contain customer-provided information such as facility names, equipment names, equipment descriptions, operating schedules, utility costs, photographs, notes, or other project-specific information.

Where reports are shared with authorized customer representatives, consultants, contractors, service providers, facility operators, decision-makers, funding organizations, or other parties at the direction of a customer, the handling of those reports by the receiving party may also be subject to that party's own privacy, confidentiality, information security, or data-handling practices.

Electrical Panel, MCC, Switchgear, and Equipment Photo Submissions

This Privacy Policy applies to photographs, images, files, documents, diagrams, labels, equipment information, and other materials submitted to Opti-mized in connection with electrical panels, motor control centres (MCCs), switchgear, circuits, equipment, electrical infrastructure, facility systems, installation planning, technical support, or facility configuration.

Customers and users may be asked to provide photographs in order to assist Opti-mized in understanding electrical infrastructure, identifying equipment, determining system configuration, preparing hardware requirements, supporting installation, assisting troubleshooting, or maintaining accurate facility records.

Photographs may include electrical panels, breaker directories, panel schedules, equipment labels, nameplates, wiring arrangements, electrical rooms, switchgear, MCCs, transformers, equipment, mechanical systems, or other facility infrastructure.

Depending on how a photograph is taken, additional information may incidentally appear in an image. For example, photographs may capture portions of a room, facility signage, employee names appearing on labels, asset identifiers, serial numbers, addresses, documents posted near equipment, or individuals located in the background.

Users submitting photographs to Opti-mized should use reasonable care to avoid including personal, confidential, sensitive, or unrelated information that is not necessary for the intended purpose.

Opti-mized may process submitted images manually or using automated technologies in order to identify relevant information, organize facility records, assist with system configuration, improve data accuracy, support technical review, or provide requested services.

Online Store and Purchasing Process

This Privacy Policy applies to information collected in connection with our online store, purchasing process, quotations, orders, invoices, payments, subscriptions, renewals, product shipments, returns, warranties, and related commercial transactions.

Depending on the transaction, information collected may include a purchaser's name, organization, business address, shipping address, billing address, email address, telephone number, products or services ordered, quantities, pricing, transaction information, tax-related information, payment status, delivery information, and other information required to complete or administer a transaction.

Payment information may be processed directly by a third-party payment processor rather than stored by Opti-mized. In such circumstances, the payment processor may collect information such as payment card details, bank information, billing information, or other information required to complete the transaction.

Opti-mized may receive limited information from payment processors relating to the transaction, such as payment confirmation, transaction identifiers, payment status, payment method type, billing information, or information needed for accounting, fraud prevention, customer support, or order administration.

Our collection and use of information relating to purchases may also include records required for accounting, taxation, financial reporting, warranty administration, fraud prevention, customer service, contract administration, and compliance with applicable legal obligations.

Customer Service and Support

This Privacy Policy applies to information provided, collected, generated, or retained when customers, users, prospective customers, contractors, facility representatives, or other individuals communicate with Opti-mized for customer service, technical support, onboarding, troubleshooting, product assistance, training, warranty assistance, or other support purposes.

Support communications may occur through email, telephone, online forms, support portals, video calls, screen sharing, messaging systems, or other communication methods.

The information collected during support activities may include names, contact information, account details, organization information, facility information, device identifiers, equipment information, screenshots, photographs, diagnostic information, error information, platform activity, communications, notes, and other information necessary to investigate or resolve the applicable request.

In some circumstances, authorized Opti-mized personnel or service providers may access a customer's account, facility configuration, device information, or related data where reasonably necessary to investigate a technical issue, provide requested support, maintain the service, or protect the security and integrity of the platform.

Records of support communications may be retained for purposes such as resolving ongoing issues, maintaining service history, improving our products and services, training personnel, identifying recurring problems, documenting customer requests, and maintaining appropriate business records.

Marketing Communications and Notifications

This Privacy Policy applies to information used in connection with marketing communications, product announcements, newsletters, service updates, educational communications, event invitations, demonstrations, sales communications, and similar messages sent by or on behalf of Opti-mized.

Depending on how you interact with us, we may collect information such as your name, email address, telephone number, organization, job title, area of interest, communication preferences, records of consent where required, interactions with communications, and information relating to prior communications with Opti-mized.

We may also collect information regarding whether communications have been delivered, opened, viewed, or interacted with where permitted by applicable law and supported by the communication technologies we use.

Marketing communications are separate from certain operational or service-related communications. If you maintain an Opti-mized account or use our services, we may need to send administrative, transactional, security, billing, support, system, or service-related messages even if you have chosen not to receive promotional communications.

Where required by applicable law, we will provide mechanisms for users to unsubscribe from or modify their preferences regarding promotional communications.

Service, System, and Facility Notifications

This Privacy Policy also applies to information used to provide notifications relating to the operation of Opti-mized services.

These notifications may include equipment alerts, detected operating conditions, performance notifications, energy-related observations, device connectivity notifications, account security notices, system maintenance notices, report availability notifications, facility updates, support messages, and similar operational communications.

Depending on the configuration selected by a customer or user, notifications may be delivered through the Opti-mized platform, email, mobile notification, SMS, or other communication channels that may become available.

Information associated with these notifications may include contact information, user preferences, facility or equipment identifiers, alert information, platform activity, notification delivery status, and records of notification settings.

Demonstrations, Sales, Quotations, and Business Communications

This Privacy Policy may also apply when individuals communicate with Opti-mized outside of the website or platform in connection with potential or existing business relationships.

For example, we may process information when a person requests a product demonstration, asks for a quotation, communicates with our sales team, participates in a meeting, responds to an outreach communication, attends an event, requests information about our services, or discusses a potential facility or project.

Information collected in these circumstances may include business contact information, organization information, facility information, project requirements, meeting notes, communications, purchasing interests, requested services, and other information relevant to the business relationship.

Where appropriate, this information may be associated with an existing or prospective customer record.

Installation, Commissioning, and Technical Services

Where Opti-mized or an authorized contractor provides installation, commissioning, configuration, inspection, troubleshooting, or technical services, this Privacy Policy applies to information collected or created in connection with those activities.

This information may include facility contact information, facility access information, installation photographs, electrical information, equipment information, configuration information, device identifiers, panel or circuit information, technical notes, commissioning records, connectivity information, service records, and other information reasonably required to provide the applicable service.

Where services are performed by a third-party contractor or service provider, that party may also process information in accordance with its contractual obligations and, where applicable, its own privacy policies.

Information Provided Through Business Customers and Organizations

In many cases, Opti-mized provides services to businesses, municipalities, government organizations, facility owners, property operators, institutional customers, contractors, consultants, or other organizations.

Accordingly, information about an individual may sometimes be provided to Opti-mized by the organization with which that individual is associated rather than directly by the individual.

For example, an organization may provide the names and business email addresses of employees who require access to the Opti-mized platform, may identify facility personnel as contacts for an installation, or may provide information about individuals responsible for equipment, purchasing, billing, or project administration.

Where an organization provides information to Opti-mized, that organization is responsible for ensuring that it has appropriate authority to provide the information to us and that its collection and disclosure of the information complies with applicable requirements.

Data Generated Through the Use of Opti-mized Services

This Privacy Policy also applies to certain information that may not be directly submitted by a user but is generated through use of our products and services.

Examples may include platform activity records, account activity, device status information, facility performance data, equipment operating patterns, detected conditions, calculated values, diagnostic records, system logs, configuration history, report generation activity, communication history, and similar information produced as a result of using Opti-mized services.

Some information generated by our systems may be derived from other information. For example, Opti-mized may analyze electrical information over time in order to establish an operating baseline, detect unusual behaviour, identify potential energy loss, estimate savings, compare equipment behaviour, identify peak demand contributions, or generate other facility intelligence.

Derived or calculated information may be treated in accordance with this Privacy Policy where it relates to an identifiable customer, user, facility, account, device, or other identifiable record.

Future Opti-mized Applications, Products, and Services

This Privacy Policy also applies to future Opti-mized websites, software applications, mobile applications, platform features, hardware products, reporting tools, digital services, analytics services, customer portals, integrations, and other products or services that expressly reference, incorporate, or link to this Privacy Policy.

Opti-mized may continue to develop and expand its products and services over time. New functionality may involve new ways of collecting, processing, analyzing, presenting, or using information.

Where appropriate, this Privacy Policy may be updated to reflect material changes to our products, services, information practices, technologies, legal requirements, or business operations.

The inclusion of future services within the scope of this Privacy Policy does not mean that every future Opti-mized product will necessarily be governed by this Privacy Policy. Certain products, jurisdictions, services, or business relationships may be governed by supplemental privacy notices, contractual terms, or separate privacy policies where appropriate.

Interactions Across Multiple Opti-mized Services

A customer or user may interact with Opti-mized through more than one of the channels described above.

For example, a prospective customer may first visit our website, request a demonstration, submit facility information, receive a quotation, purchase hardware, create an account, upload panel photographs, install Opti-mized hardware, use the platform, receive Facility Intelligence Reports, and contact our support team.

Where reasonably necessary to provide, administer, secure, improve, or support our services, information collected through these different interactions may be associated with the same customer, organization, account, facility, project, device, or user record.

This allows Opti-mized to provide a more complete and consistent service experience, maintain accurate records, respond to customer requests, support facility configurations, maintain account security, manage transactions, troubleshoot issues, and provide relevant platform functionality.

Third-Party Websites and Services

Opti-mized services may contain links to, integrate with, communicate with, or otherwise make use of third-party websites, software, applications, payment processors, cloud providers, communications providers, analytics providers, authentication providers, delivery providers, customer support systems, mapping services, utility data services, contractors, or other external services.

This Privacy Policy generally applies to information processed by Opti-mized. It does not automatically apply to the independent information practices of third parties.

Where you provide information directly to a third party, access a third-party website or service, use a third-party account, or authorize a third-party integration, the collection, use, storage, disclosure, and protection of information by that third party may be governed by the third party's own terms, privacy policy, contracts, and information-handling practices.

For example, if a payment transaction is processed through an independent payment processor, the payment processor may collect and process certain payment information according to its own privacy policy and legal obligations.

Similarly, if you access Opti-mized through a third-party link, integration, authentication service, application, browser extension, telecommunications provider, or other external service, information processed independently by that third party may fall outside the scope of this Privacy Policy.

Opti-mized does not control the privacy practices of independent third parties solely because our services link to, integrate with, or rely on their services.

We encourage users to review the privacy policies and terms of third-party services where appropriate before providing information to or through those services.

Third-Party Integrations Authorized by Customers

Certain Opti-mized services may permit customers to connect or integrate external applications, systems, platforms, data sources, utility services, software tools, or other third-party services.

Where a customer elects to enable such an integration, Opti-mized may receive information from or transmit information to the third-party service as necessary to provide the integration.

The types of information exchanged will depend on the nature of the integration, the permissions granted by the customer, and the functionality being used.

Customers are responsible for evaluating third-party integrations they choose to enable and for ensuring they have appropriate authority to direct Opti-mized to exchange information with those services.

The third party's independent handling of information remains subject to its own privacy practices.

Customer-Controlled Information and Authorized Users

Certain information processed through Opti-mized may be provided, configured, controlled, or made available by a customer organization.

For example, a customer may determine which employees or contractors receive access to a facility account, which users receive reports, which equipment names are entered into the platform, what photographs are uploaded, which notification recipients are configured, or which third-party integrations are enabled.

Where Opti-mized processes information at the direction of a customer organization, certain privacy requests or questions relating to that information may need to be addressed initially to the applicable organization.

Nothing in this section is intended to alter the rights, responsibilities, or obligations established under applicable law or under agreements between Opti-mized and its customers.

Information Outside the Scope of This Privacy Policy

This Privacy Policy does not necessarily govern every piece of information that Opti-mized may encounter.

For example, information may fall outside the scope of this Privacy Policy where it has been aggregated, anonymized, de-identified, or otherwise processed so that it can no longer reasonably be associated with an identifiable individual, where permitted by applicable law.

Information relating exclusively to businesses, equipment, facilities, electrical systems, or other non-personal matters may also fall outside the legal definition of personal information in certain jurisdictions, although Opti-mized may nevertheless protect such information in accordance with contractual obligations, security practices, confidentiality requirements, and internal policies.

This Privacy Policy also does not replace any confidentiality obligations, data-processing terms, customer agreements, service agreements, employment policies, contractor agreements, nondisclosure agreements, or other contractual terms that may apply to specific information or relationships.

Where another agreement between Opti-mized and a customer establishes additional or more specific obligations regarding information, that agreement may apply in addition to this Privacy Policy.

Application of This Privacy Policy

The inclusion of a category, technology, service, or type of information in this Privacy Policy does not mean that Opti-mized necessarily collects that information from every individual, customer, user, or facility.

The specific information we collect and the purposes for which it is processed depend on factors such as the services being used, the customer's configuration, the products installed, the nature of the relationship with Opti-mized, the jurisdiction involved, the permissions provided, and the actions taken by the user.

References in this Privacy Policy to particular information practices are intended to describe practices that may occur where relevant and are not intended to imply that every practice applies in every circumstance.

This Privacy Policy should therefore be read together with any additional notices, disclosures, agreements, consent mechanisms, platform notices, or contractual terms that may be presented in connection with a specific Opti-mized product, service, transaction, or relationship.

The information we collect, receive, generate, derive, access, store, or otherwise process depends on the nature of your relationship with Opti-mized, the products and services you use, the features you access, the configuration of your organization or facility, the hardware installed at a facility, the information you choose to provide, and the manner in which you interact with our website, platform, personnel, products, and services.

Different users and customers may therefore provide or generate different categories and amounts of information.

For example, a person who only visits the Opti-mized website may provide relatively limited information, while a customer that purchases and deploys Opti-mized hardware throughout a facility may provide substantially more facility, equipment, electrical, operational, configuration, and account information.

Similarly, an authorized user who accesses a dashboard may generate account and platform-usage information, while a facility representative who submits electrical panel photographs may provide facility configuration information without necessarily becoming a regular platform user.

The categories described below are intended to explain the types of information that Opti-mized may collect or process where relevant. The inclusion of a category in this Privacy Policy does not mean that Opti-mized necessarily collects that category of information from every individual, organization, facility, customer, device, or user.

Information processed by Opti-mized may include information you provide directly to us, information provided to us by your organization or another authorized party, information collected automatically through our websites or services, information transmitted by Opti-mized hardware, information received through authorized third-party integrations, and information generated or derived through analysis of other information.

Some information processed through Opti-mized relates primarily to buildings, electrical systems, circuits, equipment, devices, or facility operations rather than identifiable individuals. Depending on applicable law and the circumstances, such information may not constitute personal information. However, Opti-mized may nevertheless protect facility, operational, equipment, and customer information through the administrative, technical, contractual, and organizational safeguards described in this Privacy Policy and in applicable customer agreements.

Account and Contact Information

We may collect information that identifies, describes, or enables us to communicate with an individual who interacts with Opti-mized.

This information may be provided when you create an account, request a demonstration, request a quotation, submit a facility setup form, purchase products or services, communicate with our team, request support, subscribe to communications, participate in a project, or otherwise interact with Opti-mized.

Account and contact information may include:

• Name
• First and last name
• Business email address
• Other email address provided to us
• Telephone number
• Mobile telephone number
• Company name
• Municipality name
• Government organization name
• Institutional organization name
• Employer
• Department
• Division
• Job title
• Professional role
• Facility role
• Project role
• Business address
• Mailing address
• Facility address
• Billing address
• Shipping address
• Country, province, state, region, or municipality
• Username
• User ID
• Account number
• Customer identifier
• Organization identifier
• Facility identifier
• Project identifier
• Reference code
• Account status
• User permissions
• User role
• Administrative permissions
• Organization affiliation
• Facility access permissions
• Communication preferences
• Notification preferences
• Language preferences, where supported
• Login information
• Authentication information
• Password-related information in protected or hashed form, where applicable
• Single sign-on or authentication identifiers, where supported
• Multi-factor authentication information, where supported
• Account recovery information
• Date an account was created
• Date an account was modified
• Date of last login
• Account activity
• Records relating to account access
• Records relating to account suspension, termination, or reactivation

We may use account and contact information to create and administer accounts, authenticate users, control access to facilities and platform functionality, communicate with users, deliver reports and notifications, provide customer service, maintain security, manage business relationships, and provide requested products and services.

Where Opti-mized services are purchased or administered by an organization, that organization may provide us with information about individuals who are authorized to access its account or facilities.

For example, a municipality may provide the name and business email address of a facilities manager, administrator, finance representative, contractor, consultant, or other employee who should receive access to the Opti-mized platform.

In those circumstances, we may receive account or contact information from the organization rather than directly from the individual.

Customer and Organization Information

In addition to information about individual users, we may collect information concerning the organization that purchases, evaluates, administers, owns, operates, finances, or otherwise uses Opti-mized products or services.

This may include:

• Organization name
• Business name
• Municipality name
• Government entity name
• Institution name
• Organization type
• Industry or sector
• Department or division
• Business address
• Mailing address
• Billing address
• Shipping address
• Website
• Business telephone number
• Tax-related information
• Purchase-order information
• Procurement information
• Vendor registration information
• Customer number
• Account number
• Contract number
• Project number
• Grant or funding reference information
• Billing contacts
• Technical contacts
• Facility contacts
• Administrative contacts
• Procurement contacts
• Authorized signatories
• Customer representatives
• Contract status
• Subscription or service status
• Products or services purchased
• Facilities associated with the organization
• User accounts associated with the organization
• Support history
• Commercial communications
• Project communications
• Project schedules
• Customer preferences
• Service requirements
• Deployment requirements

Much of this information relates to an organization rather than an individual. However, where organization information identifies or is associated with a specific person, it may constitute personal information under applicable law.

Facility Information

We may collect information about a facility in order to evaluate, recommend, design, configure, deploy, operate, maintain, analyze, support, or improve Opti-mized products and services.

Facility information may be provided directly by a customer or authorized representative, obtained through facility setup forms, collected during installation or commissioning, derived from photographs and documents, entered into the Opti-mized platform, received through authorized integrations, or generated through use of Opti-mized products and services.

Facility information may include:

• Facility name
• Facility address
• Site address
• Facility identifier
• Building identifier
• Facility type
• Building type
• Facility use
• Building use
• Approximate square footage
• Gross floor area
• Conditioned floor area
• Number of buildings
• Number of floors
• Number of operational areas
• Number of electrical rooms
• Facility age, where provided
• Facility operating schedule
• Opening and closing hours
• Daily operating hours
• Weekly operating schedule
• Seasonal operating schedule
• Holiday operating schedule
• Occupancy schedules, where provided
• Approximate occupancy information, where relevant
• Facility operating characteristics
• Facility operating constraints
• Facility functions
• Facility processes
• Seasonal operating conditions
• Existing building systems
• Mechanical systems
• Electrical systems
• Lighting systems
• Heating systems
• Cooling systems
• Ventilation systems
• Pumps
• Motors
• Fans
• Compressors
• Refrigeration equipment
• Process equipment
• Plug loads
• Specialized equipment
• Electrical panels
• Distribution panels
• Main distribution panels
• Subpanels
• Motor control centres
• MCCs
• Switchgear
• Transformers
• Electrical distribution equipment
• Breakers
• Feeder information
• Circuits
• Panel and circuit layouts
• Panel schedules
• Breaker schedules
• Circuit schedules
• Circuit identifiers
• Circuit names
• Equipment identifiers
• Equipment names
• Equipment categories
• Equipment types
• Equipment quantities
• Approximate circuit quantities
• Approximate equipment quantities
• Electrical service information
• Voltage information
• Phase information
• Panel ratings
• Breaker ratings
• Current-transformer requirements
• Electrical configuration information
• Existing meter information
• Communications infrastructure
• Network availability
• Wi-Fi availability
• Ethernet availability
• Cellular connectivity requirements
• Gateway placement information
• Installation requirements
• Installation constraints
• Accessibility information relating to equipment locations
• Information regarding electrical rooms or equipment locations
• Utility provider information
• Electricity account information
• Electricity consumption information
• Utility billing information
• Utility bills
• Demand information
• Electricity rates
• Tariffs
• Rate structures
• Historical utility information
• Heating-fuel information where relevant
• Water information where relevant to a project
• Facility energy costs
• Existing energy projects
• Proposed retrofit projects
• Planned capital projects
• Facility objectives
• Energy-reduction objectives
• Operational objectives
• Sustainability objectives
• Performance objectives
• Cost-reduction objectives
• Decarbonization objectives
• Project goals
• Customer priorities
• Operational concerns
• Known equipment issues
• Known energy concerns
• Planned facility changes
• Other information provided to help us understand the facility

Facility information may be used to determine the appropriate number and type of Opti-mized sensors, gateways, CT hubs, or other hardware; determine installation requirements; organize a facility within the platform; associate circuits with equipment; understand operating context; conduct analysis; prepare reports; identify opportunities; provide technical support; or improve the accuracy and usefulness of Opti-mized services.

Some facility information may relate exclusively to a building, piece of equipment, electrical system, utility account, or commercial operation and may not identify an individual.

Where facility information does not relate to an identifiable person, it may not constitute personal information under applicable privacy laws.

We may nevertheless treat customer facility information as confidential or otherwise protected information in accordance with applicable agreements, internal practices, and security controls.

Facility Configuration and Mapping Information

Opti-mized may collect or generate detailed information regarding how a facility is organized within the Opti-mized system.

This may include information used to connect electrical measurements with the corresponding physical equipment, circuits, systems, areas, panels, or facility functions.

Facility configuration information may include:

• Facility hierarchy
• Building hierarchy
• Electrical-panel hierarchy
• MCC hierarchy
• Switchgear hierarchy
• Circuit assignments
• Circuit-to-equipment relationships
• Sensor-to-circuit relationships
• Gateway-to-device relationships
• Equipment-to-location relationships
• Circuit names
• Circuit descriptions
• Equipment names
• Equipment descriptions
• Equipment categories
• Equipment groups
• Panel names
• Panel identifiers
• Breaker numbers
• Circuit positions
• Metering points
• Measurement-point identifiers
• Hardware associations
• Device associations
• Installation notes
• Configuration notes
• Commissioning information
• Equipment classifications
• User-created labels
• Customer-created labels
• Facility zones
• Building areas
• Departments
• Operational areas
• System groups
• Custom fields
• Customer-defined descriptions

This information allows us to organize raw electrical and sensor measurements into meaningful facility and equipment information.

Electrical Equipment Information

We may collect information about equipment installed or operated at a customer facility.

Equipment information may include:

• Equipment name
• Equipment category
• Equipment type
• Manufacturer
• Model
• Serial number
• Nameplate information
• Rated capacity
• Voltage rating
• Current rating
• Power rating
• Horsepower
• Equipment age where provided
• Installation date where provided
• Location
• Serving area
• Operating schedule
• Expected runtime
• Typical operating characteristics
• Equipment status
• Maintenance information where provided
• Replacement information where provided
• Equipment condition observations
• Equipment identifiers
• Asset numbers
• Circuit association
• Panel association
• MCC association
• Switchgear association
• System association
• Equipment photographs
• Equipment notes
• Customer comments
• Installation notes
• Configuration information
• Operating characteristics derived through analysis

Where equipment information is associated with an employee name, technician name, operator name, or other identifiable individual, the associated portion may constitute personal information.

Photos and Images

You, your organization, an authorized representative, installer, contractor, consultant, or other authorized party may provide photographs or images to Opti-mized.

Photographs may be submitted through facility setup forms, the Opti-mized platform, email, customer support channels, installation processes, project communications, or other authorized methods.

When you upload electrical panel photos through a saved link, one consent covers three uses: preparing your quote, setting up your dashboard, and follow-up that may include anonymized marketing. The photos are stored for that facility record. They are not published as public website files. You can ask us to delete them.

Photographs may include:

• Electrical panel photographs
• Panel directory photographs
• Breaker photographs
• MCC photographs
• Motor control centre photographs
• Switchgear photographs
• Transformer photographs
• Gateway photographs
• Sensor installation photographs
• CT installation photographs
• Electrical-room photographs
• Equipment photographs
• Mechanical-equipment photographs
• HVAC equipment photographs
• Pump photographs
• Motor photographs
• Lighting-equipment photographs
• Facility photographs
• Building photographs
• Nameplate photographs
• Equipment-label photographs
• Manufacturer-label photographs
• Serial-number photographs
• Electrical schedule photographs
• Panel schedule photographs
• Wiring-related photographs
• Installation-condition photographs
• Communications-equipment photographs
• Network-equipment photographs
• Troubleshooting photographs
• Commissioning photographs
• Photographs submitted as part of customer support

Photographs are generally requested for purposes such as understanding a facility's electrical configuration, determining hardware requirements, identifying equipment, assisting installation, matching circuits with equipment, preparing deployment recommendations, organizing facility records, assisting commissioning, diagnosing technical issues, or configuring the Opti-mized platform.

Photographs may incidentally capture information that is not specifically requested by Opti-mized.

For example, an electrical-room photograph could contain employee names written on a panel schedule, building signage, asset numbers, facility addresses, documents posted on walls, computer screens, license plates, personal belongings, or individuals in the background.

Users should avoid intentionally submitting unnecessary personal, confidential, privileged, or sensitive information in photographs where that information is not required for the applicable purpose.

Opti-mized may review photographs manually, through software-assisted processes, or through automated technologies for purposes such as identifying equipment, reading labels, organizing records, supporting facility configuration, or providing requested services.

Customers, users, facility representatives, consultants, contractors, or other authorized parties may provide documents and files to Opti-mized.

Documents may include:

• Utility bills
• Electricity bills
• Natural-gas bills
• Heating bills
• Water bills
• Utility consumption records
• Interval data
• Utility account summaries
• Panel schedules
• Electrical schedules
• Equipment schedules
• Asset lists
• Facility lists
• Floor plans
• Electrical drawings
• Single-line diagrams
• Mechanical drawings
• Equipment specifications
• Equipment cut sheets
• Equipment inventories
• Maintenance information
• Operating schedules
• Capital plans
• Retrofit information
• Energy-audit information
• Energy-model information
• Facility reports
• Engineering or technical reports
• Project documents
• Procurement documents
• Purchase orders
• Quotations
• Contracts
• Invoices
• Grant-related documents
• Funding documents
• Customer spreadsheets
• Facility spreadsheets
• Installation documents
• Commissioning records
• Screenshots
• Support documents
• Other supporting facility documentation

Documents and Files

Documents may contain information about facilities, organizations, accounts, equipment, utilities, projects, employees, representatives, or other individuals.

We process information contained in these documents where reasonably necessary to provide the requested products or services.

Utility Information

Where customers provide utility information, or authorize us to receive it, we may collect information relating to facility utility accounts and historical utility consumption.

This may include:

• Utility provider
• Utility account number
• Meter number
• Service address
• Billing period
• Billing date
• Electricity consumption
• Peak demand
• Demand charges
• Energy charges
• Fixed charges
• Taxes
• Fees
• Rate classification
• Rate schedule
• Tariff information
• Historical consumption
• Historical cost
• Seasonal usage
• Interval consumption information where available
• Natural-gas consumption where relevant
• Heating-fuel consumption where relevant
• Water or sewer consumption where relevant to a project
• Credits
• Adjustments
• Billing history
• Account status
• Utility contact information
• Other information contained on a utility bill

Utility bills may incidentally contain the name, mailing address, account number, customer number, or contact information of an account holder.

We use utility information for purposes such as establishing historical baselines, understanding facility performance, comparing measured information with billed consumption, analyzing demand, estimating savings, supporting energy models, calculating financial opportunities, preparing reports, and evaluating facility performance.

Energy and Electrical Data

When Opti-mized hardware, sensors, gateways, meters, or other connected equipment are installed or connected, our products may automatically collect, transmit, receive, store, or process information concerning the electrical operation of a facility, circuit, system, or piece of equipment.

This information may be collected continuously, periodically, or in response to particular system events, depending on system configuration and service functionality.

Energy and electrical information may include:

• Electrical current
• Electrical voltage
• Current measurements
• Voltage measurements
• Power
• Active power
• Reactive power where supported
• Apparent power where supported
• Energy consumption
• Circuit-level energy consumption
• Circuit-level electrical usage
• Equipment-level electrical usage
• Electrical load
• Load magnitude
• Load profile
• Load shape
• Load duration
• Demand
• Peak demand
• Demand contribution
• Power fluctuations
• Electrical patterns
• Equipment runtime
• Equipment start times
• Equipment stop times
• Equipment operating periods
• Equipment cycling
• Cycling frequency
• Equipment activation
• Equipment deactivation
• Equipment operating duration
• Equipment operating frequency
• Continuous load
• Baseload
• Idle load
• Standby load
• After-hours operation
• Off-hours operation
• On-hours operation
• Historical electrical usage
• Historical load information
• Time-series information
• Timestamp information
• Date information
• Time information
• Frequency of measurements
• Changes in electrical behaviour
• Changes in load behaviour
• Changes in equipment operation
• Electrical events
• Sensor measurements
• Calculated electrical measurements
• Derived electrical values
• Measurement quality information
• Circuit identifiers
• Equipment identifiers
• Panel identifiers
• Hardware identifiers
• Gateway identifiers
• Sensor identifiers
• CT identifiers
• Device status
• Gateway status
• Sensor status
• Connectivity status
• Communications status
• Device health information
• Diagnostic information
• Firmware information
• Data-transmission status
• Measurement status
• Installation configuration
• Device configuration
• Measurement-channel information

We refer to this information collectively in this Privacy Policy as “Energy and Operational Data.”

Energy and Operational Data is primarily intended to describe the behaviour and operation of electrical systems, circuits, equipment, and facilities.

Opti-mized does not generally deploy its electrical measurement systems for the purpose of identifying the personal activities of individual people.

However, because patterns of facility operation may sometimes correspond with periods of occupancy, business activity, equipment use, or other operational events, Energy and Operational Data may in some circumstances indirectly reveal information about activities occurring within a facility.

For example, electrical information may indicate that particular equipment generally begins operating at a certain time, that a facility experiences reduced activity on weekends, or that certain electrical loads remain active after scheduled operating hours.

Whether such information constitutes personal information depends on applicable law, the context in which the data is used, and whether it can reasonably be associated with an identifiable individual.

High-Frequency and Time-Series Measurements

Certain Opti-mized products may collect electrical or equipment-related measurements at relatively frequent intervals in order to understand equipment behaviour and facility performance.

High-frequency or time-series measurements may allow Opti-mized to evaluate patterns that would not be visible from monthly utility bills alone.

These measurements may be used to understand matters such as:

• When equipment starts
• When equipment stops
• How long equipment operates
• How frequently equipment cycles
• Whether operating patterns are changing
• Whether equipment operates outside expected schedules
• How much electrical load equipment contributes
• Whether a particular circuit contributes to peak demand
• Whether a facility maintains an unusually high baseload
• Whether equipment usage changes over time
• Whether operating behaviour differs between weekdays and weekends
• Whether operating behaviour varies seasonally
• Whether equipment performance is consistent with established baselines

The frequency and granularity of information collected may vary depending on hardware type, system configuration, firmware, technical requirements, and services enabled for a particular customer.

Operational Context Information

Electrical measurements alone may not always provide sufficient context to understand facility behaviour.

Customers may therefore provide, or Opti-mized may generate or receive, contextual information that allows electrical information to be interpreted more meaningfully.

Operational context information may include:

• Facility hours
• Equipment schedules
• Production schedules
• Occupancy schedules
• Opening and closing times
• Weekend schedules
• Holiday schedules
• Seasonal schedules
• Expected equipment operation
• Facility shutdown periods
• Maintenance periods
• Operational changes
• Special events
• Weather information
• Outdoor temperature information
• Environmental conditions
• Heating or cooling periods
• Customer-defined operating rules
• Equipment-control strategies
• Known operational exceptions
• Facility operating notes

Where applicable, we may combine such contextual information with Energy and Operational Data in order to identify patterns, calculate opportunities, or provide Facility Intelligence Data.

Facility Intelligence Data

Opti-mized may analyze information collected or received from a facility in order to generate additional information, calculations, classifications, estimates, comparisons, predictions, observations, recommendations, alerts, or other analytical outputs.

This may involve analysis of Energy and Operational Data together with facility information, utility information, operating schedules, weather information, equipment information, historical information, customer-provided information, and other relevant contextual information.

Facility Intelligence Data may include:

• Equipment operating patterns
• Circuit operating patterns
• Facility operating patterns
• Equipment baselines
• Circuit baselines
• Facility baselines
• Expected equipment behaviour
• Expected facility behaviour
• Runtime calculations
• Runtime analysis
• Operating-hour analysis
• Cycling analysis
• Cycling frequency
• Start and stop analysis
• Load analysis
• Demand analysis
• Peak-demand analysis
• Peak-demand contribution
• Baseload analysis
• Continuous-load analysis
• Idle-load analysis
• Standby-load analysis
• On-hours usage analysis
• Off-hours usage analysis
• After-hours usage analysis
• Weather correlation
• Environmental correlation
• Environmental mismatch observations
• Schedule mismatch observations
• Anomaly detection
• Behavioural changes
• Deviations from historical patterns
• Deviations from expected baselines
• Unusual operating conditions
• Potential operational issues
• Potential equipment issues
• Potential energy-loss opportunities
• Energy-loss classifications
• Detected areas of potential savings
• Estimated electricity reduction
• Estimated demand reduction
• Estimated energy savings
• Estimated financial savings
• Estimated annual savings
• Estimated monthly savings
• Estimated avoided cost
• Savings ranges
• Cost calculations
• Utility-rate calculations
• Retrofit calculations
• Retrofit simulations
• Scenario calculations
• Return-on-investment calculations
• Simple payback calculations
• Estimated payback periods
• Prioritization scores
• Opportunity rankings
• Equipment rankings
• Facility rankings
• Operational recommendations
• Energy-management recommendations
• Retrofit recommendations
• Data-backed retrofit assessments
• Potential maintenance indicators
• Predictive-maintenance indicators
• Preventative-maintenance indicators
• Equipment deterioration indicators
• Changes in equipment electrical signatures
• Facility performance insights
• Equipment performance insights
• Equipment classifications
• Circuit classifications
• Equipment-to-circuit associations
• Detected events
• Alerts
• Notifications
• Findings
• Observations
• Calculated metrics
• Derived metrics
• Trend information
• Benchmark information
• Comparative information
• Facility summaries
• Equipment summaries
• Savings summaries
• Facility Intelligence Reports
• Energy reports
• Operational reports
• Equipment reports
• Executive summaries
• Dashboard information
• Charts
• Graphs
• Tables
• Visualizations
• Other facility intelligence generated from collected information

We refer to this information collectively as “Facility Intelligence Data.”

Facility Intelligence Data may be generated automatically, manually, or through a combination of automated analysis, software calculations, algorithms, analytics, customer-provided context, and professional or technical review.

Not every observation, estimate, calculation, alert, classification, or recommendation will be available for every facility or customer.

The specific Facility Intelligence Data generated depends on available measurements, hardware configuration, data quality, equipment characteristics, facility information, customer settings, and enabled services.

Derived and Inferred Information

Some information used by Opti-mized is not directly provided by a customer and is not itself a raw sensor measurement.

Instead, we may derive, calculate, estimate, classify, infer, or otherwise generate information from other information available to us.

For example, we may use electrical measurements to estimate equipment runtime, compare operation against a known schedule, identify repeated operating patterns, calculate estimated costs, establish a baseline, or identify a potential energy-loss opportunity.

Derived information may include:

• Calculated runtime
• Estimated runtime
• Operating-state classifications
• Equipment-state estimates
• Expected baselines
• Usage patterns
• Behavioural patterns
• Equipment classifications
• Circuit classifications
• Equipment correlations
• Operational trends
• Comparative performance
• Savings estimates
• Cost estimates
• Demand estimates
• Retrofit estimates
• Efficiency opportunities
• Performance indicators
• Anomaly indicators
• Maintenance indicators
• Risk indicators
• Priority rankings
• Confidence indicators where supported
• Analytical summaries

Derived information should generally be understood as analytical information based on available data, assumptions, calculations, and system functionality and may not represent a direct physical measurement in every instance.

Reports and Analytical Outputs

We may collect, generate, store, or maintain information included in reports created through or in connection with Opti-mized.

These may include:

• Facility Intelligence Reports
• Equipment reports
• Energy reports
• Opportunity reports
• Savings reports
• Facility summaries
• Operational summaries
• Energy-loss summaries
• Performance reports
• Dashboard exports
• PDF reports
• Data exports
• Charts
• Graphs
• Tables
• Screenshots
• Findings
• Recommendations
• Calculations
• Supporting notes
• Customer-provided comments
• Facility photographs
• Equipment photographs
• Equipment descriptions
• Utility information
• Project information

Reports may be retained within the Opti-mized platform, provided electronically to customers, downloaded by authorized users, or otherwise distributed as permitted by the applicable customer relationship.

Hardware and Device Information

Opti-mized may collect information relating to hardware that is manufactured, supplied, configured, installed, connected, or supported as part of our services.

This may include:

• Hardware model
• Hardware type
• Device serial number
• Gateway identifier
• Sensor identifier
• CT identifier
• Hub identifier
• Device ID
• Communications-module identifier
• Firmware version
• Software version
• Hardware version
• Device configuration
• Sensor configuration
• Gateway configuration
• Communication settings
• Measurement settings
• Installation information
• Commissioning information
• Date of activation
• Date of installation
• Last communication time
• Device uptime
• Connectivity status
• Network status
• Signal quality
• Connection type
• Wi-Fi connection information where necessary for configuration
• Ethernet status
• Cellular status
• IP-related network information
• Cloud connectivity status
• Message-delivery information
• Data-transmission status
• Device health
• Hardware errors
• Gateway errors
• Sensor errors
• Diagnostic logs
• Fault information
• Reconnection events
• Restart events
• Firmware-update status
• Over-the-air update information
• Configuration history
• Device replacement history
• Warranty information
• Support history
• Troubleshooting information

This information helps us install, configure, maintain, monitor, secure, troubleshoot, update, and support connected Opti-mized devices.

Device and Technical Information

When you access the Opti-mized website, platform, dashboard, applications, or related online services, we may automatically collect certain technical information about your device, browser, network connection, and interaction with our systems.

This may include:

• Internet Protocol address
• IP address
• Approximate geographic location derived from IP address
• Browser type
• Browser version
• Device type
• Computer type
• Mobile-device type
• Operating system
• Operating-system version
• Device identifiers
• Browser identifiers
• Session identifiers
• Cookie identifiers
• Application identifiers
• Network information
• Internet service provider information where available
• Referral URL
• Referring website
• Landing page
• Pages viewed
• Features accessed
• Dashboard activity
• Buttons selected
• Forms accessed
• Form interactions
• Navigation activity
• Session start time
• Session duration
• Session end time
• Date and time of access
• Time zone
• Login activity
• Login attempts
• Successful logins
• Failed login attempts
• Logout activity
• Authentication activity
• Account-access history
• Platform usage
• Application usage
• Feature usage
• Report access
• Report downloads
• File uploads
• Configuration changes
• User-setting changes
• Notification-setting changes
• Error logs
• Crash information
• Diagnostic information
• Performance information
• System-response information
• Security events
• Suspicious activity indicators
• Access-control events
• Device and browser security information
• Other technical information necessary to operate and secure our services

Technical information may be collected through server logs, application logs, cookies, analytics technologies, authentication systems, security technologies, or similar mechanisms.

Platform Usage Information

We may collect information regarding how authorized users interact with the Opti-mized platform.

Platform usage information may include:

• Account login
• Login date
• Login time
• Session duration
• Facilities viewed
• Dashboards viewed
• Equipment records viewed
• Reports viewed
• Reports downloaded
• Filters used
• Date ranges selected
• Charts viewed
• Features accessed
• Files uploaded
• Configuration changes
• Equipment labels created
• Circuit labels created
• Notes entered
• User preferences
• Notification settings
• Administrative actions
• Account-management activity
• Invitation activity
• User-permission changes
• Data-export activity
• Support-related activity
• Errors encountered
• Feature interactions
• Search activity within the platform
• Other interactions with platform functionality

We may use this information to provide and improve the platform, understand feature usage, maintain security, troubleshoot issues, support customers, improve usability, and develop new functionality.

Cookies and Similar Technologies

When you use our website or certain online services, we or service providers acting on our behalf may use cookies, pixels, local storage, software development kits, log files, analytics technologies, or similar technologies to collect information about your device or interaction with our services.

Depending on the technologies used, information collected may include:

• IP address
• Browser
• Device
• Session identifier
• Cookie identifier
• Pages visited
• Referring page
• Time spent on a page
• Interactions with website features
• Navigation paths
• Approximate location
• Website performance
• Error information
• Marketing attribution information
• Communication interactions
• Other technical or usage information

Some technologies may be necessary for security, authentication, account functionality, preferences, or basic operation of our services.

Other technologies may be used for analytics, performance measurement, website improvement, or marketing, where permitted by applicable law.

Additional information regarding cookies and similar technologies may be provided elsewhere in this Privacy Policy or in a separate cookie notice, if applicable.

Security and Authentication Information

We may collect information for purposes of protecting Opti-mized, our users, customers, systems, hardware, infrastructure, and services from unauthorized access, fraud, abuse, cybersecurity threats, or other harmful activity.

Security-related information may include:

• Login attempts
• Failed login attempts
• Authentication information
• IP addresses
• Device information
• Browser information
• Session identifiers
• Password reset activity
• Multi-factor authentication activity
• Account recovery activity
• Suspicious access attempts
• Unusual login activity
• Access logs
• Security events
• User-permission changes
• Administrative activity
• Device security information
• Network-security information
• Error logs
• System logs
• Security alerts
• Fraud indicators
• Abuse indicators
• Incident information
• Information relating to suspected violations of our terms or security policies

We may also generate security-related inferences or alerts where our systems identify activity that appears unusual, unauthorized, fraudulent, abusive, or potentially harmful.

Transaction and Purchasing Information

When you purchase, order, subscribe to, renew, return, or otherwise acquire Opti-mized products or services, we may collect information relating to that transaction.

Transaction information may include:

• Purchaser name
• Organization
• Billing contact
• Shipping contact
• Billing address
• Shipping address
• Email address
• Telephone number
• Purchase-order number
• Purchase-order documentation
• Quote number
• Invoice number
• Products ordered
• Hardware ordered
• Services ordered
• Quantities
• Product configuration
• Order date
• Order history
• Pricing
• Discounts
• Taxes
• Shipping charges
• Transaction status
• Payment status
• Payment date
• Invoice status
• Delivery status
• Shipping tracking information
• Subscription information
• Renewal information
• Cancellation information
• Refund information
• Return information
• Warranty information
• Tax-exemption information
• Commercial terms
• Contract information
• Related correspondence
• Other commercial information required to process or administer the transaction

Payments may be processed through independent third-party payment providers, banks, financial institutions, payment gateways, or similar service providers.

Opti-mized does not intend to store complete payment-card or credit-card numbers where payment-card information is processed directly by an independent payment processor.

Where a third-party payment processor handles payment information, the processor may collect payment-card numbers, expiration dates, security codes, banking details, billing information, or other information required to complete a payment.

Opti-mized may receive limited transaction information from the processor, such as confirmation that a payment was successful, the transaction amount, transaction identifier, payment status, billing contact, payment method category, or other limited information needed to administer the transaction.

Information provided directly to a payment processor is subject to that provider's own privacy, security, retention, and data-handling practices.

Billing and Financial Administration Information

In addition to transaction information, we may maintain information required to administer customer accounts and our financial relationship with customers.

This may include:

• Billing contact information
• Accounts-payable contact information
• Invoice records
• Invoice history
• Purchase orders
• Payment status
• Payment history
• Outstanding balances
• Credits
• Refunds
• Tax information
• Tax-exemption certificates
• Vendor documentation
• Remittance information
• Customer accounting references
• Contract values
• Subscription information
• Renewal dates
• Service periods
• Commercial correspondence

We may retain certain transaction and financial records for accounting, taxation, audit, compliance, contractual, dispute-resolution, and other legitimate business purposes.

Sales, Demonstration, and Prospective Customer Information

If you contact us regarding potential Opti-mized products or services, request a demonstration, request a quotation, attend a meeting, respond to outreach, participate in a sales discussion, or otherwise express interest in Opti-mized, we may collect information relating to the potential business relationship.

This may include:

• Name
• Business email
• Telephone number
• Organization
• Job title
• Role
• Facility name
• Facility location
• Number of facilities
• Facility type
• Approximate facility size
• Project requirements
• Business needs
• Energy-related concerns
• Deployment goals
• Purchasing timeline
• Budget information if voluntarily provided
• Procurement requirements
• Funding information
• Grant information
• Hardware requirements
• Requested services
• Meeting notes
• Demonstration history
• Proposal history
• Quotation history
• Communications
• Follow-up activity
• Customer relationship information

We may retain this information to respond to inquiries, prepare quotations, understand prospective customer requirements, conduct sales activities, manage potential customer relationships, and maintain business records.

Communications

We may collect information contained in communications between you and Opti-mized.

This may occur when you:

• Contact us
• Email us
• Telephone us
• Request information
• Request a demonstration
• Request a quotation
• Request support
• Submit a support ticket
• Complete a form
• Submit a facility setup
• Request a Facility Intelligence Report
• Submit a photograph
• Submit a document
• Submit feedback
• Participate in a survey
• Respond to a questionnaire
• Communicate with our sales team
• Communicate with our technical team
• Communicate with our customer-support team
• Communicate with an installer
• Communicate with a project representative
• Communicate with us regarding billing
• Communicate with us regarding a contract
• Communicate with us regarding a purchase
• Communicate with us regarding a facility
• Subscribe to updates
• Subscribe to marketing communications
• Respond to a marketing communication
• Participate in another business interaction with us

Communication information may include:

• Name
• Contact information
• Message content
• Email correspondence
• Support requests
• Questions
• Feedback
• Comments
• Complaints
• Technical issues
• Facility information
• Equipment information
• Account information
• Screenshots
• Photographs
• Attachments
• Documents
• Support notes
• Internal notes relating to the request
• Date and time of communications
• Participants in communications
• Resolution information
• Follow-up information

We may retain records of communications where reasonably necessary to respond to requests, provide support, maintain customer histories, resolve disputes, improve services, train personnel, document business transactions, or comply with applicable legal requirements.

Customer Support and Troubleshooting Information

If you contact Opti-mized for technical or customer support, we may collect information needed to diagnose, investigate, reproduce, resolve, or document the issue.

This may include:

• Account information
• User information
• Facility information
• Equipment information
• Hardware identifiers
• Gateway identifiers
• Device information
• Sensor information
• Connectivity information
• Error messages
• Error logs
• Diagnostic information
• Firmware information
• Network information
• Screenshots
• Photographs
• Videos provided for troubleshooting
• Configuration information
• Platform activity
• Recent system events
• Support-ticket information
• Communications
• Troubleshooting steps
• Resolution information
• Support history

Where necessary and authorized, support personnel may access relevant account, facility, device, or platform information to investigate and resolve a support request.

Installation and Commissioning Information

Where Opti-mized products are installed, configured, commissioned, inspected, or serviced, we may collect information relating to the installation and commissioning process.

This may include:

• Facility name
• Facility address
• Site contact
• Installation contact
• Electrical contractor information
• Installer information
• Installation date
• Installation location
• Electrical-panel information
• MCC information
• Switchgear information
• Circuit information
• Equipment information
• Sensor placement
• CT placement
• Gateway placement
• Network configuration
• Connectivity information
• Commissioning results
• Device identifiers
• Hardware serial numbers
• Device configuration
• Installation notes
• Photographs
• Troubleshooting information
• Testing information
• Verification information
• Installer comments
• Customer comments
• Service records

Some installation records may be retained as part of the ongoing facility configuration to support future troubleshooting, device replacement, maintenance, upgrades, or expansion.

Maintenance and Service Information

We may maintain information relating to servicing, maintaining, replacing, troubleshooting, updating, repairing, or modifying Opti-mized hardware and services.

This may include:

• Service requests
• Service dates
• Device replacement records
• Hardware replacement records
• Warranty claims
• Firmware updates
• Configuration updates
• Troubleshooting history
• Equipment status
• Gateway status
• Sensor status
• Communications status
• Support records
• Technician notes
• Customer communications
• Diagnostic information
• Corrective actions
• Resolution history

Feedback, Surveys, and Research Information

We may collect information when customers, users, prospective customers, or other individuals voluntarily provide feedback or participate in surveys, product research, interviews, testing, or similar activities.

This may include:

• Responses to surveys
• Product feedback
• Feature requests
• User-experience feedback
• Customer-satisfaction information
• Comments
• Suggestions
• Interview responses
• Testing feedback
• Research responses
• Voluntarily provided demographic or professional information where appropriate
• Information about how users interact with our products or services

We may use this information to improve products and services, identify customer needs, prioritize development, improve usability, and evaluate customer satisfaction.

Marketing and Communication Information

If you subscribe to marketing communications, request information, attend an event, receive sales communications, or otherwise interact with promotional content, we may collect information relating to those communications.

This may include:

• Name
• Email address
• Telephone number
• Organization
• Job title
• Area of interest
• Marketing preferences
• Subscription status
• Consent records where required
• Unsubscribe status
• Communication history
• Email-delivery information
• Email-open information where supported and permitted
• Link-click information where supported and permitted
• Campaign information
• Event participation
• Demonstration requests
• Content requests
• Other interactions with promotional communications

Marketing information may be combined with other business-contact information where permitted by applicable law.

Notification Information

Where users configure alerts or notifications through Opti-mized, we may collect information required to deliver and administer those notifications.

This may include:

• Notification recipient
• Email address
• Telephone number where applicable
• Notification preference
• Alert preference
• Facility association
• Equipment association
• Notification threshold
• Delivery channel
• Delivery status
• Notification history
• Acknowledgement information where supported
• Notification settings
• Subscription or unsubscribe information

Notifications may relate to account security, platform status, equipment behaviour, detected conditions, reports, customer support, device connectivity, operational information, or other Opti-mized functionality.

Information from Third Parties

In some circumstances, we may receive information from third parties rather than directly from you.

Depending on the applicable relationship, these third parties may include:

• Your employer
• Your organization
• A municipality
• A government organization
• A facility owner
• A facility operator
• A property manager
• A contractor
• An installer
• A consultant
• A project manager
• A customer administrator
• An authorized user
• A utility
• A service provider
• A payment processor
• A shipping provider
• An integration provider
• A business partner
• Another party authorized to provide information to Opti-mized

Information received from third parties may include contact information, facility information, account information, utility information, equipment information, installation information, transaction information, project information, or other information necessary to provide requested services.

Where a customer or other authorized organization provides personal information about another individual, we generally rely on that party to have appropriate authority to provide the information to us.

Information from Authorized Integrations

Customers may choose to connect Opti-mized with external systems, applications, platforms, utility services, software, databases, or other third-party services.

When an integration is authorized, we may receive information from or transmit information to the integrated service as necessary to provide the requested functionality.

Depending on the integration, this may include:

• Account identifiers
• Facility identifiers
• Device identifiers
• Utility data
• Energy data
• Equipment data
• Operational information
• Building information
• Environmental information
• Weather information
• User information
• Authentication tokens or integration credentials in protected form
• Configuration information
• Other information authorized by the customer

The particular information exchanged depends on the integration and permissions selected.

Publicly Available and Business Information

In limited circumstances, we may collect publicly available or commercially available business information relevant to our relationship with a prospective or existing customer.

This may include information such as:

• Organization name
• Organization address
• Public facility information
• Public business telephone number
• Public employee business contact information
• Public procurement information
• Public project information
• Public grant or funding information
• Publicly available facility information
• Other publicly available business information

We may use this information for legitimate business purposes such as identifying potential customers, understanding organizations, responding to procurement opportunities, administering projects, or maintaining accurate business records.

Information About Contractors, Consultants, and Business Partners

Where individuals work with Opti-mized as contractors, consultants, installers, suppliers, vendors, professional advisors, technical partners, or other business partners, we may collect information relating to those business relationships.

This may include:

• Name
• Business contact information
• Company
• Role
• Qualifications
• Project assignment
• Facility assignment
• Communications
• Contract information
• Invoice information
• Payment information
• Work records
• Scheduling information
• Access information
• Project deliverables
• Technical documentation
• Other information necessary to administer the relationship

Information Generated Through Use of Our Services

In addition to information that users directly provide, Opti-mized systems may automatically generate records as users, facilities, hardware, and software interact with our services.

Generated information may include:

• Account activity
• User activity
• System events
• Device events
• Gateway events
• Measurement events
• Facility configuration changes
• Platform configuration changes
• Notification events
• Report-generation events
• Data-processing events
• Data-upload events
• Data-download events
• Device-connection events
• Device-disconnection events
• Firmware-update events
• Error events
• Security events
• System logs
• Audit logs
• Diagnostic records
• Analytics outputs
• Derived information
• Facility Intelligence Data

These records may be necessary for functionality, auditing, security, troubleshooting, quality assurance, customer support, and product improvement.

Information We Combine

Where permitted by applicable law and appropriate for the services being provided, Opti-mized may combine information obtained from different sources.

For example, we may combine:

• Facility information with Energy and Operational Data
• Utility bills with measured electrical information
• Equipment information with circuit-level data
• Operating schedules with equipment runtime
• Weather information with heating or cooling behaviour
• Customer-provided equipment names with sensor measurements
• Facility photographs with facility configuration information
• Historical data with current measurements
• Account information with platform activity
• Hardware identifiers with device diagnostic information
• Transaction information with customer-account information
• Support communications with relevant hardware or platform information

Combining information allows us to provide context and transform individual measurements or records into more meaningful facility intelligence.

For example, a raw electrical measurement may provide limited value on its own. When it is associated with a particular circuit, equipment type, operating schedule, utility rate, and historical baseline, it may allow Opti-mized to provide a more useful assessment of how that equipment is operating and whether an opportunity may exist.

Information That May Incidentally Identify Individuals

Opti-mized is primarily designed around facility, equipment, electrical, energy, and operational information rather than consumer profiling or monitoring individual behaviour.

Nevertheless, some information that is primarily related to a facility or organization may incidentally identify an individual.

Examples may include:

• A person's name appearing on a utility bill
• A person's name appearing on a panel schedule
• A facility contact appearing in project documentation
• An employee visible in a facility photograph
• An email address included in a support document
• A technician's name included in installation notes
• A user's activity associated with an Opti-mized account
• An individual's business contact information included in a customer record

Where information can reasonably be associated with an identifiable individual, we handle that information as personal information where required by applicable law.

Sensitive Information

Opti-mized products and services are generally not designed to collect highly sensitive categories of personal information that are unrelated to providing our products and services.

We ask users not to intentionally provide unnecessary sensitive personal information through facility photographs, support requests, uploads, free-text fields, or other communications.

For example, users should generally avoid submitting information concerning medical conditions, government identification numbers, financial account credentials, personal passwords, biometric information, or other highly sensitive personal information unless specifically requested by Opti-mized for a legitimate and lawful purpose.

If sensitive information is incidentally provided to us, we may process it as reasonably necessary to address the applicable request, comply with law, protect security, or otherwise fulfill an appropriate business purpose.

Personal Information and Non-Personal Facility Data

A significant portion of the information processed by Opti-mized relates to commercial facilities and physical systems rather than individuals.

Examples may include:

• Electrical current measurements
• Circuit loads
• Equipment runtime
• Equipment cycling
• Gateway status
• Panel configuration
• Equipment classifications
• Utility usage associated with a commercial facility
• Equipment photographs
• Electrical drawings
• Facility operating schedules
• Equipment energy consumption
• Demand profiles
• Savings calculations
• Equipment-performance trends

Depending on applicable privacy law and the specific circumstances, this information may not constitute personal information because it does not identify or relate to an identifiable individual.

However, the fact that certain information may not legally constitute personal information does not mean that Opti-mized treats customer facility data as unrestricted public information.

Customer facility information may remain subject to contractual confidentiality obligations, security controls, customer agreements, internal policies, intellectual-property protections, or other safeguards.

Aggregated and De-Identified Information

Where permitted by applicable law, Opti-mized may generate aggregated, statistical, anonymized, or de-identified information from information collected through our products and services.

For example, information may be combined across multiple devices, equipment types, facilities, customers, time periods, or other categories in a manner intended to prevent the information from reasonably identifying a particular individual.

Aggregated or de-identified information may include:

• Statistical information
• Average equipment behaviour
• Product-performance information
• System-performance information
• General usage trends
• Equipment benchmarks
• Facility benchmarks
• Energy-use trends
• Feature-usage statistics
• Hardware-performance statistics
• Diagnostic trends
• Generalized analytical patterns
• Product-development information

Where information has been properly aggregated or de-identified so that it no longer constitutes personal information under applicable law, it may not be subject to all provisions that apply specifically to personal information.

Information We Do Not Necessarily Collect

The fact that this Privacy Policy identifies a particular category of information does not mean that Opti-mized collects that information in every situation.

The information collected depends on the products and services being used, customer configuration, hardware configuration, technical functionality, facility requirements, enabled features, legal requirements, and information voluntarily provided to us.

For example:

• A website visitor may never provide facility information.
• A prospective customer may never create an Opti-mized account.
• A customer may purchase services without enabling every platform feature.
• A facility may not have every type of equipment identified in this Policy.
• Certain hardware may not collect every type of electrical measurement described above.
• Certain analytical features may not be enabled for every customer.
• A customer may not connect third-party integrations.
• A user may never provide marketing consent.
• Certain customers may not purchase through our online store.

Accordingly, the categories listed in this Privacy Policy describe information that may be collected where relevant rather than information that is necessarily collected in every instance.

Information You Choose to Provide

In addition to categories specifically requested by Opti-mized, users may voluntarily provide other information through open-text fields, uploaded files, communications, support requests, forms, surveys, notes, or other interactions.

Because we cannot always predict what users may choose to include in these submissions, voluntarily provided information may occasionally include information that is not specifically identified elsewhere in this Privacy Policy.

We will generally use such information in connection with the purpose for which it was provided and otherwise in accordance with this Privacy Policy.

Users should avoid submitting information that is unnecessary for the applicable purpose.

Accuracy of Information

The quality of Opti-mized services may depend in part on the accuracy of information provided to us.

Customers and authorized users are responsible for providing information that is accurate and appropriate to the best of their knowledge and for updating information where reasonably necessary.

For example, inaccurate equipment names, operating schedules, utility rates, circuit assignments, facility information, or configuration information may affect the accuracy or usefulness of analytics, savings calculations, reports, notifications, or other Facility Intelligence Data.

Opti-mized may take reasonable steps to verify, correct, normalize, supplement, or organize information where appropriate, but we cannot guarantee that all customer-provided information is complete or accurate.

Changes to the Information We Collect

The types of information processed by Opti-mized may evolve as we develop new products, hardware, software features, analytics capabilities, integrations, reports, applications, and services.

We may also modify how information is collected as technology, customer requirements, security practices, and legal requirements change.

Where a new product or feature materially changes our privacy practices, we may update this Privacy Policy, provide additional notices, obtain consent where required, or take other steps appropriate under applicable law.

Summary

In general, information processed by Opti-mized may fall into several broad categories:

• Information about users and customer representatives
• Information about customers and organizations
• Information about facilities
• Information about electrical systems and equipment
• Photographs, documents, and files
• Utility and billing information
• Energy and Operational Data collected through connected hardware
• Facility Intelligence Data generated through analysis
• Hardware, device, and technical information
• Platform and website usage information
• Transaction and purchasing information
• Communications and support information
• Installation and commissioning information
• Information obtained from authorized third parties or integrations
• Derived, inferred, calculated, aggregated, and de-identified information
• Other information voluntarily provided in connection with Opti-mized products and services

The specific categories applicable to any particular customer, individual, user, facility, or interaction will depend on the circumstances and the Opti-mized products and services involved.

Information Generated Through Historical Comparison

Opti-mized may compare current information with historical information in order to understand whether facility or equipment behaviour is changing.

For example, we may compare:

• Current runtime with historical runtime;
• Current demand with historical demand;
• Current cycling with previous cycling;
• Current energy consumption with historical consumption;
• Current weekday behaviour with prior weekdays;
• Current weekend behaviour with previous weekends;
• Current seasonal performance with prior seasonal performance;
• Current equipment behaviour with an established baseline.

The results of these comparisons may become part of Facility Intelligence Data.

Opti-mized may collect, receive, generate, derive, access, obtain, record, transmit, store, or otherwise process information through a number of different sources and methods depending on how an individual, customer, organization, facility, device, or authorized user interacts with our products and services.

The method by which information is collected may vary depending on the product or service being used, the configuration of a facility, the hardware installed, the features enabled, the nature of our relationship with the customer, the information voluntarily provided to us, the technologies used to operate our services, and the instructions or permissions provided by the customer or authorized user.

In some circumstances, information is provided directly to Opti-mized by an individual. In other circumstances, information may be provided by a customer's organization, facility representative, contractor, consultant, installer, utility provider, service provider, payment processor, or other authorized third party.

Certain information may also be collected automatically through Opti-mized hardware, gateways, sensors, websites, software applications, platform functionality, server infrastructure, communications systems, analytics technologies, or other technologies used to provide our products and services.

In addition, Opti-mized may generate new information through analysis of information previously collected or received. For example, raw electrical measurements may be analyzed together with operating schedules, equipment information, utility information, environmental conditions, historical performance, and other contextual information in order to generate Facility Intelligence Data.

The following sections describe the primary ways in which Opti-mized may obtain information.

Directly From You

We may collect information directly from you when you voluntarily provide information to Opti-mized.

This may occur through our website, platform, forms, communications, purchasing processes, facility setup processes, support channels, demonstrations, meetings, surveys, reports, installation activities, or other interactions with us.

For example, we may collect information directly from you when you:

• Visit or interact with the Opti-mized website;
• Create an Opti-mized user account;
• Register for access to the Opti-mized platform;
• Accept an invitation to access an organization or facility;
• Configure an account;
• Update your profile;
• Update your contact information;
• Select account preferences;
• Configure notification preferences;
• Submit a contact form;
• Request information about Opti-mized;
• Request a product demonstration;
• Request a consultation;
• Request a quotation;
• Request pricing information;
• Request a Facility Intelligence Report;
• Begin a facility setup;
• Continue or update an existing facility setup;
• Submit information about a building;
• Submit information about multiple buildings;
• Add an electrical panel;
• Add an MCC;
• Add switchgear;
• Add electrical equipment;
• Add circuits;
• Identify equipment connected to circuits;
• Provide operating schedules;
• Provide equipment schedules;
• Enter facility operating hours;
• Provide utility information;
• Upload utility bills;
• Upload electrical schedules;
• Upload panel schedules;
• Upload equipment schedules;
• Upload facility documentation;
• Upload photographs;
• Upload electrical panel photographs;
• Upload MCC photographs;
• Upload switchgear photographs;
• Upload equipment photographs;
• Upload facility photographs;
• Upload nameplate photographs;
• Provide installation information;
• Provide network or connectivity information;
• Submit a purchase order;
• Purchase products;
• Purchase services;
• Subscribe to services;
• Renew services;
• Request a return;
• Submit a warranty request;
• Provide shipping information;
• Provide billing information;
• Contact customer support;
• Contact technical support;
• Contact our sales team;
• Contact our billing team;
• Communicate with an Opti-mized representative;
• Participate in a meeting;
• Participate in an installation or commissioning process;
• Submit troubleshooting information;
• Submit screenshots;
• Submit videos;
• Submit diagnostic information;
• Respond to a survey;
• Provide product feedback;
• Submit suggestions;
• Submit feature requests;
• Participate in research or testing;
• Subscribe to communications;
• Subscribe to marketing updates;
• Register for notifications;
• Respond to communications;
• Participate in another interaction with Opti-mized.

The information collected in these circumstances depends on what you choose to provide and the reason for the interaction.

For example, a person requesting a product demonstration may provide only a name, organization, email address, telephone number, facility type, and general description of the facility.

By contrast, a customer configuring a large facility may provide significantly more detailed information about the facility's electrical systems, equipment, panels, MCCs, switchgear, circuits, utility accounts, operating schedules, building characteristics, communications infrastructure, and project objectives.

Information You Enter Into the Opti-mized Platform

We may collect information that you or another authorized user enters directly into the Opti-mized platform.

This may include information entered during initial setup as well as information added, edited, corrected, renamed, categorized, configured, or otherwise maintained during continued use of the platform.

Information entered into the platform may include:

• Facility names;
• Facility addresses;
• Building names;
• Building descriptions;
• Facility types;
• Facility operating hours;
• Equipment names;
• Equipment types;
• Equipment categories;
• Equipment descriptions;
• Equipment identifiers;
• Panel names;
• Panel numbers;
• Circuit names;
• Circuit numbers;
• Breaker identifiers;
• MCC information;
• Switchgear information;
• Electrical-system information;
• Equipment-to-circuit relationships;
• Facility zones;
• Departments;
• Building areas;
• Operating schedules;
• Expected runtime information;
• Utility-rate information;
• Cost information;
• Equipment notes;
• Installation notes;
• Customer-defined labels;
• Custom descriptions;
• Configuration information;
• Alert thresholds;
• Notification settings;
• User permissions;
• Facility access permissions;
• Comments;
• Feedback;
• Other information entered through available platform functionality.

Information entered by one authorized user may, depending on account permissions, be visible to other users associated with the same organization or facility.

Information Submitted Through Facility Setup and Configuration Processes

Opti-mized may provide digital or manual facility setup, planning, configuration, quotation, deployment, or onboarding processes.

During these processes, we may collect information directly from a customer or authorized representative in order to understand the facility and determine the appropriate Opti-mized configuration.

Information may be collected through:

• Online facility setup forms;
• Guided configuration tools;
• Product-selection tools;
• Hardware-planning tools;
• Quote-request forms;
• Pre-order forms;
• Installation questionnaires;
• Facility surveys;
• Customer interviews;
• Technical calls;
• Email communications;
• Spreadsheet templates;
• Uploaded documents;
• Photographs;
• Project documentation;
• Other setup methods.

The information provided may be used to determine matters such as:

• The number of electrical panels at a facility;
• The number of MCCs;
• The number of switchgear locations;
• Approximate circuit quantities;
• Required sensor quantities;
• Required CT sizes;
• Appropriate gateway quantities;
• Communication requirements;
• Installation requirements;
• Hardware configuration;
• Facility hierarchy;
• Equipment relationships;
• Estimated project requirements;
• Appropriate services;
• Platform configuration.

In some cases, Opti-mized may create an initial facility configuration based on the information submitted and later modify that configuration as additional information becomes available.

Information Submitted Through Photographs and Images

We may collect information from photographs or images that you, your organization, an installer, contractor, consultant, facility representative, or another authorized party provides to us.

Photographs may be submitted through:

• The Opti-mized website;
• The Opti-mized platform;
• A facility setup process;
• An upload portal;
• Email;
• Customer support;
• Technical support;
• Installation communications;
• Commissioning activities;
• Project communications;
• Other approved channels.

A photograph may itself constitute information, and it may also contain information that can be read, interpreted, extracted, classified, or associated with a facility.

For example, a photograph of an electrical panel may contain:

• A panel identifier;
• Panel rating;
• Breaker configuration;
• Breaker quantities;
• Circuit numbers;
• Circuit labels;
• Equipment labels;
• Voltage information;
• Manufacturer information;
• Model information;
• Nameplate information;
• Electrical schedules;
• Handwritten notes;
• Building or room identifiers.

A photograph of equipment may similarly contain:

• Equipment manufacturer;
• Equipment model;
• Serial number;
• Electrical rating;
• Capacity;
• Equipment type;
• Equipment location;
• Equipment condition;
• Asset identifier;
• Installation information.

We may review photographs manually or use software-assisted or automated processes to identify, organize, categorize, extract, or verify relevant facility information.

Information identified from a photograph may be associated with an existing facility, panel, circuit, equipment record, customer account, installation record, or project.

Photographs may occasionally include information that was not intentionally submitted, such as individuals in the background, signage, documents, employee names, computer displays, room contents, addresses, serial numbers, or other information visible within the photograph.

We encourage users to avoid including unnecessary personal, confidential, sensitive, or unrelated information when submitting photographs.

To Send Alerts and Operational Notifications

Where enabled, we may use contact and facility information to send alerts concerning:

• Equipment behaviour;
• Energy-loss opportunities;
• Facility conditions;
• Equipment changes;
• Device connectivity;
• Gateway status;
• Measurement availability;
• Reports;
• Other configured events.

Opti-mized may use, process, organize, analyze, combine, review, store, transmit, display, generate, derive, aggregate, de-identify, or otherwise handle information for a variety of purposes related to operating our business, providing our products and services, supporting customers, administering accounts, analyzing facility performance, maintaining connected hardware, generating Facility Intelligence Data, developing and improving our technology, protecting our systems, complying with legal obligations, and carrying out other legitimate business activities.

The particular purposes for which information is used depend on the nature of the information, how the information was collected, the products or services involved, the customer's configuration, the relationship between Opti-mized and the applicable customer or user, the functionality being used, applicable contractual requirements, and applicable law.

Not every use described in this section applies to every category of information, every user, every customer, or every facility.

For example, information collected from a website visitor may primarily be used to operate and improve the website, respond to inquiries, measure website activity, and communicate with the visitor. By contrast, Energy and Operational Data collected from installed Opti-mized hardware may be used to analyze equipment behaviour, identify operating patterns, detect possible energy-loss opportunities, calculate savings, generate alerts, and create Facility Intelligence Data.

Where required by applicable law, we use personal information only where we have an appropriate legal basis, authorization, consent, contractual justification, legitimate business purpose, or other lawful basis for doing so.

The following sections describe the principal ways in which Opti-mized may use information.

To Create and Manage User Accounts

We may use account, identity, contact, organizational, technical, authentication, and related information to create, maintain, administer, secure, update, and manage Opti-mized user accounts.

This may include using information to:

• Create a new user account;
• Register a user;
• Verify account information;
• Associate a user with an organization;
• Associate a user with one or more facilities;
• Associate a user with a customer account;
• Assign user roles;
• Assign administrative privileges;
• Establish account permissions;
• Limit access to appropriate facilities;
• Configure user preferences;
• Configure notification preferences;
• Maintain contact information;
• Manage invitations;
• Activate accounts;
• Suspend accounts;
• Disable accounts;
• Reactivate accounts;
• Assist with account recovery;
• Facilitate password resets;
• Support authentication;
• Support multi-factor authentication where available;
• Support single sign-on where available;
• Maintain login records;
• Identify account owners or administrators;
• Maintain account histories;
• Manage organizational access;
• Transfer administrative permissions where appropriate;
• Remove user access when requested or required;
• Maintain records relating to account status.

We may also use account information to ensure that users see only the facilities, data, reports, equipment, dashboards, or platform features that they are authorized to access.

To Authenticate Users and Control Access

We may use information to determine whether a person attempting to access Opti-mized systems is authorized to do so.

This may include using:

• Username information;
• Email addresses;
• Password credentials in protected form;
• Authentication tokens;
• Session identifiers;
• IP addresses;
• Device information;
• Multi-factor authentication information;
• Account permissions;
• Organization identifiers;
• User roles;
• Login history;
• Security information.

Authentication and access-control information may be used to:

• Confirm user identity;
• Establish secure sessions;
• Restrict unauthorized access;
• Detect unusual login activity;
• Prevent credential misuse;
• Protect customer information;
• Maintain account integrity;
• Manage access to facilities;
• Manage access to reports;
• Manage administrative privileges;
• Prevent users from viewing information they are not authorized to access.

To Provide the Opti-mized Platform

We may use information to operate, maintain, and provide access to the Opti-mized web platform and its associated functionality.

This may include using information to:

• Display customer facilities;
• Display facility dashboards;
• Display electrical information;
• Display equipment information;
• Display historical information;
• Display current information;
• Display analytics;
• Display detected opportunities;
• Display calculations;
• Display trends;
• Display alerts;
• Display recommendations;
• Display reports;
• Display equipment status;
• Display gateway status;
• Display sensor status;
• Organize facility information;
• Organize equipment information;
• Allow authorized users to navigate facilities;
• Allow users to access reports;
• Allow users to configure settings;
• Allow users to manage notifications;
• Allow users to add or update information;
• Allow administrators to manage user access;
• Allow data to be filtered;
• Allow information to be compared across time periods;
• Allow users to review equipment behaviour;
• Allow users to review facility-level performance;
• Provide data exports where available;
• Provide report downloads;
• Provide customer-specific functionality;
• Support features made available now or in the future.

Information may be associated with a specific organization, facility, building, panel, MCC, switchgear location, circuit, equipment item, gateway, sensor, measurement point, report, or user in order to provide meaningful organization and navigation within the platform.

To Operate Opti-mized Hardware

We may use information to operate, configure, communicate with, monitor, maintain, update, and support Opti-mized hardware.

This may include hardware such as:

• Sensors;
• Current transformers;
• CTs;
• CT Hubs;
• Gateways;
• Communications equipment;
• Measurement devices;
• Related accessories;
• Other connected Opti-mized hardware.

Information may be used to:

• Identify devices;
• Associate devices with customers;
• Associate devices with facilities;
• Associate devices with panels;
• Associate sensors with circuits;
• Associate measurements with equipment;
• Configure device settings;
• Verify device operation;
• Monitor device connectivity;
• Monitor communications status;
• Check device health;
• Detect hardware errors;
• Detect data-transmission failures;
• Troubleshoot connectivity;
• Diagnose equipment issues;
• Perform remote configuration where supported;
• Perform firmware updates;
• Perform over-the-air updates where supported;
• Maintain device compatibility;
• Maintain system security;
• Confirm successful data transmission;
• Recover or synchronize information following connection interruptions;
• Track hardware deployment;
• Maintain hardware records;
• Support replacement or servicing of devices.

To Provide Connected Services

Opti-mized hardware may communicate with cloud infrastructure, software systems, databases, analytics services, notification services, and the Opti-mized platform.

We may use information to enable these components to function together.

For example, information may be used to:

• Receive measurements from installed hardware;
• Transmit measurements securely;
• Associate measurements with appropriate customer accounts;
• Process measurement data;
• Store historical data;
• Generate analytics;
• Update dashboards;
• Produce reports;
• Trigger notifications;
• Maintain synchronization between devices and cloud services;
• Monitor connectivity;
• Identify missing or delayed data;
• Maintain service availability;
• Support customer access to facility information.

To Understand a Facility

We may use information provided by customers, users, contractors, consultants, installers, service providers, or other authorized parties to understand the structure, systems, operations, and electrical configuration of a facility.

This may include using information concerning:

• Facility type;
• Building size;
• Number of buildings;
• Building use;
• Operating schedules;
• Electrical service;
• Electrical panels;
• MCCs;
• Switchgear;
• Circuits;
• Equipment;
• Utility information;
• Existing metering;
• Communication infrastructure;
• Equipment schedules;
• Panel schedules;
• Facility photographs;
• Electrical drawings;
• Customer objectives.

We may use this information to build an organized representation of the facility within the Opti-mized system.

To Determine Appropriate Hardware for a Facility

We may use facility information, electrical information, photographs, equipment information, panel information, and customer requirements to determine what Opti-mized hardware may be appropriate for a particular facility.

This may include determining:

• The number of measurement points;
• The approximate number of circuits to be measured;
• The number of electrical panels;
• The number of MCCs;
• The number of switchgear locations;
• The number of gateways required;
• The number of CT Hubs required;
• The number of CTs required;
• Appropriate CT sizes;
• Appropriate sensor types;
• Communication requirements;
• Network requirements;
• Installation requirements;
• Expansion requirements;
• Hardware configuration;
• Potential hardware placement;
• Hardware quantities;
• Hardware compatibility;
• Other deployment requirements.

These determinations may be based on information supplied by the customer and may be revised when additional information becomes available during installation, commissioning, or facility setup.

To Prepare Facility Setup Recommendations

We may use information collected through facility setup forms, photographs, documents, technical discussions, or other sources to prepare recommendations regarding how Opti-mized products could be deployed.

Recommendations may include:

• Suggested hardware quantities;
• Suggested sensor quantities;
• Suggested gateway quantities;
• Suggested CT Hub quantities;
• Suggested measurement locations;
• Suggested circuit coverage;
• Suggested panel coverage;
• Suggested equipment coverage;
• Connectivity recommendations;
• Deployment sequencing;
• Configuration recommendations;
• Preliminary installation assumptions;
• Estimated deployment requirements.

Recommendations may be preliminary and may depend on the accuracy and completeness of information provided by customers or their representatives.

To Estimate Setup Costs

We may use information about a facility, hardware requirements, quantities, products, services, installation requirements, and customer configuration to estimate the cost of an Opti-mized deployment.

This may include calculating or estimating:

• Hardware costs;
• Sensor costs;
• Gateway costs;
• CT Hub costs;
• Accessory costs;
• Installation costs where applicable;
• Configuration costs;
• Deployment costs;
• Setup costs;
• Service costs;
• Subscription costs where applicable;
• Shipping costs;
• Taxes;
• Other project-related costs.

Cost estimates may be based on assumptions and available information and may change as facility conditions, hardware requirements, pricing, project scope, or other factors change.

To Review Electrical Panel, MCC, Switchgear, and Equipment Photos

We may use photographs and other images provided by customers or authorized parties to understand facility electrical infrastructure and equipment.

For example, we may review photographs to:

• Identify electrical panels;
• Identify MCCs;
• Identify switchgear;
• Identify breakers;
• Identify panel ratings;
• Identify circuit information;
• Read labels;
• Read panel schedules;
• Identify equipment names;
• Identify equipment categories;
• Identify manufacturer information;
• Identify equipment nameplate information;
• Estimate circuit quantities;
• Estimate equipment quantities;
• Determine hardware requirements;
• Determine potential sensor requirements;
• Determine appropriate CT sizes;
• Identify installation considerations;
• Support configuration;
• Support troubleshooting;
• Validate information provided through forms;
• Maintain facility records.

Photographs may be reviewed manually, through software-assisted tools, or through automated analysis where appropriate.

To Extract and Organize Information From Documents

We may use information from uploaded or submitted documents to support facility configuration, analysis, reporting, installation, purchasing, or customer service.

For example, information from utility bills may be used to determine:

• Historical electricity consumption;
• Historical demand;
• Historical utility cost;
• Utility rates;
• Rate structures;
• Billing periods;
• Seasonal patterns;
• Cost baselines.

Information from electrical drawings or panel schedules may be used to:

• Identify circuits;
• Identify electrical systems;
• Organize equipment;
• Map circuits to equipment;
• Determine hardware requirements;
• Support installation;
• Support configuration.

To Create Panel-by-Panel Configurations

We may use information to create detailed configurations for individual electrical panels, MCCs, switchgear assemblies, or other distribution equipment.

This may include using information to:

• Assign panel names;
• Assign panel identifiers;
• Record panel ratings;
• Record breaker positions;
• Identify circuit names;
• Identify circuit numbers;
• Identify breaker sizes;
• Associate sensors with circuits;
• Associate circuits with equipment;
• Organize circuits by category;
• Record CT requirements;
• Associate panels with facilities;
• Associate panels with gateways;
• Maintain installation records;
• Create digital representations of customer electrical infrastructure.

These configurations may be updated over time as additional information is provided or facility conditions change.

To Map Panels, Circuits, Sensors, and Equipment

A core function of the Opti-mized service may involve associating electrical measurements with meaningful facility assets.

We may use information to create relationships between:

• Facilities;
• Buildings;
• Panels;
• MCCs;
• Switchgear;
• Breakers;
• Circuits;
• Sensors;
• CTs;
• Gateways;
• Equipment;
• Building areas;
• Facility systems;
• Operational functions.

For example, information may be used to determine that a particular sensor measures a particular circuit and that the circuit serves a particular rooftop unit, pump, lighting system, motor, exhaust fan, or other equipment.

This mapping allows raw measurement information to be presented in a more understandable and useful form.

To Organize Facility Information

We may use information to organize facilities, buildings, equipment, electrical systems, measurement points, reports, and users within the Opti-mized platform.

This may involve:

• Creating facility hierarchies;
• Grouping buildings;
• Grouping equipment;
• Creating equipment categories;
• Organizing circuits;
• Organizing electrical panels;
• Linking facility assets;
• Associating documents with facilities;
• Associating photographs with equipment;
• Associating reports with facilities;
• Associating users with facilities;
• Maintaining customer-specific naming conventions;
• Maintaining customer-defined categories;
• Creating portfolio-level views.

To Configure Customer Dashboards

We may use information to configure dashboards and platform views that are relevant to each customer's facilities and services.

Dashboard configuration may involve:

• Selecting available data;
• Organizing facilities;
• Organizing equipment;
• Displaying electrical measurements;
• Displaying runtime information;
• Displaying energy consumption;
• Displaying detected opportunities;
• Displaying savings calculations;
• Displaying alerts;
• Displaying equipment trends;
• Displaying facility trends;
• Displaying historical data;
• Providing portfolio views;
• Applying customer-specific names or labels;
• Configuring permissions;
• Configuring filters;
• Configuring reporting functionality.

To Process Energy and Operational Data

We may use Energy and Operational Data collected through Opti-mized products in order to transform raw measurements into useful information about a facility and its equipment.

Processing may include:

• Receiving data;
• Validating data;
• Organizing data;
• Timestamping data;
• Storing data;
• Normalizing data;
• Cleaning data;
• Aggregating data;
• Comparing data;
• Calculating values;
• Associating measurements with circuits;
• Associating measurements with equipment;
• Establishing historical records;
• Identifying missing measurements;
• Evaluating data quality;
• Preparing data for analytics;
• Preparing data for dashboard presentation;
• Preparing data for reports.

To Generate Facility Intelligence Data

We may use collected information to generate Facility Intelligence Data.

Facility Intelligence Data may be created by analyzing Energy and Operational Data together with other available information such as:

• Facility information;
• Equipment information;
• Circuit information;
• Operating schedules;
• Utility rates;
• Utility bills;
• Historical information;
• Environmental information;
• Weather information;
• Customer-defined thresholds;
• Equipment classifications;
• Customer objectives.

The resulting Facility Intelligence Data may include:

• Operating patterns;
• Equipment baselines;
• Runtime calculations;
• Cycling analysis;
• Load analysis;
• Demand analysis;
• Energy-loss opportunities;
• Savings estimates;
• Cost calculations;
• Performance trends;
• Equipment comparisons;
• Facility comparisons;
• Notifications;
• Recommendations;
• Alerts;
• Reports;
• Other derived intelligence.

To Establish Equipment and Facility Baselines

We may use historical Energy and Operational Data to establish baseline patterns for equipment, circuits, systems, buildings, or facilities.

A baseline may represent an expected or typical operating pattern based on historical information.

Baseline analysis may consider:

• Typical runtime;
• Typical start time;
• Typical stop time;
• Typical load;
• Typical energy consumption;
• Typical demand contribution;
• Typical cycling frequency;
• Typical weekday behaviour;
• Typical weekend behaviour;
• Typical seasonal behaviour;
• Typical performance under comparable conditions.

Baselines may then be used to compare current operation against historical or expected behaviour.

To Analyze Equipment Behaviour

We may use information to understand how equipment actually operates over time.

Analysis may include evaluating:

• When equipment turns on;
• When equipment turns off;
• How long equipment runs;
• How frequently equipment cycles;
• How much electrical power equipment draws;
• Whether electrical demand changes;
• Whether operating behaviour is stable;
• Whether operating behaviour changes over time;
• Whether equipment runs outside scheduled hours;
• Whether equipment operates continuously;
• Whether equipment cycles more or less frequently than expected;
• Whether equipment behaviour correlates with environmental conditions;
• Whether operating patterns differ from historical patterns.

Equipment behaviour analysis may be presented through dashboards, graphs, reports, notifications, or other Opti-mized functionality.

To Analyze Facility Behaviour

We may also use information to understand how energy and electrical usage change across an entire facility.

This may include analyzing:

• Facility baseload;
• Facility operating hours;
• Daily usage;
• Weekly usage;
• Monthly usage;
• Seasonal usage;
• Peak-demand events;
• Equipment contributions to demand;
• After-hours consumption;
• Continuous loads;
• Changes in facility behaviour;
• Portfolio-level comparisons;
• Historical performance.

To Analyze Runtime

We may calculate or estimate runtime using electrical measurements, sensor information, equipment information, or other available data.

Runtime analysis may be used to determine:

• Total operating hours;
• Operating hours per day;
• Operating hours per week;
• Operating hours per month;
• Operating hours per year;
• Runtime during scheduled hours;
• Runtime outside scheduled hours;
• Runtime by season;
• Changes in runtime;
• Differences between expected and actual runtime.

Runtime information may support energy-loss identification, cost estimates, maintenance indicators, and operational decision-making.

To Analyze Equipment Cycling

We may use information to identify or estimate equipment cycling patterns.

This may include:

• Number of starts;
• Number of stops;
• Cycling frequency;
• Runtime per cycle;
• Changes in cycle length;
• Changes in cycling frequency;
• Repeated starts;
• Unusual cycling behaviour;
• Historical comparisons.

Cycling information may be used to provide operational context, identify changes in equipment behaviour, or support potential maintenance analysis.

To Analyze Demand

We may use information to analyze facility electrical demand and identify equipment or circuits that contribute to demand peaks.

This may include:

• Identifying peak-demand periods;
• Measuring demand levels;
• Identifying simultaneous equipment operation;
• Identifying major contributors to peak demand;
• Comparing peak periods;
• Evaluating historical peak demand;
• Estimating potential demand reduction;
• Calculating potential cost savings from demand reduction.

To Analyze Baseload and Continuous Loads

We may use information to identify electrical loads that remain active continuously or for extended periods.

This may include analyzing:

• Overnight loads;
• Weekend loads;
• Base electrical consumption;
• Continuous equipment;
• Constant circuits;
• Minimum facility load;
• Changes in baseload over time;
• Potentially unnecessary continuous consumption.

To Identify Off-Hours Usage

We may compare equipment or circuit operation with facility operating schedules to identify electrical use occurring outside expected operating hours.

This may include identifying equipment that:

• Operates after a facility closes;
• Starts before expected operating hours;
• Runs overnight;
• Runs on weekends;
• Runs during holidays;
• Runs during scheduled shutdowns;
• Remains energized beyond expected periods.

This information may be used to estimate the amount and cost of potential off-hours energy use.

To Identify On-Hours Overusage

We may use information to identify equipment or systems that appear to consume more energy than expected during normal facility operating hours.

Analysis may involve:

• Comparing current load with historical load;
• Comparing equipment with established baselines;
• Reviewing operating duration;
• Evaluating expected equipment use;
• Identifying unnecessarily high load;
• Evaluating repeated or prolonged operation;
• Comparing similar operating periods.

To Identify Environmental Mismatch

Where relevant contextual information is available, we may compare equipment operation against environmental or operating conditions.

For example, analysis may identify potential situations in which:

• Heating equipment operates when conditions do not appear to require heating;
• Cooling equipment operates when conditions do not appear to require cooling;
• Equipment operation does not align with outdoor temperature;
• Equipment operation appears inconsistent with expected environmental conditions;
• Heating and cooling systems appear to operate in conflict;
• Environmental conditions suggest a different expected operating pattern.

Such observations may depend on available data and should be understood as analytical indicators rather than definitive conclusions in every circumstance.

To Identify Idle or Standby Loads

We may use Energy and Operational Data to identify equipment or circuits that remain energized while not appearing to be actively performing their primary function.

This may include:

• Standby loads;
• Idle equipment;
• Equipment energized between uses;
• Equipment drawing power outside active cycles;
• Low-level continuous consumption.

To Identify High Continuous Loads

We may use information to identify equipment, circuits, systems, or facility loads that operate continuously at comparatively high levels.

This may be used to:

• Prioritize investigation;
• Evaluate operating schedules;
• Compare equipment performance;
• Estimate potential savings;
• Identify unusual or unnecessary continuous operation.

To Identify Potential Energy-Loss Opportunities

We may analyze facility and equipment information to identify potential areas where energy consumption could possibly be reduced.

Potential energy-loss opportunities may include:

• Off-hours operation;
• On-hours overusage;
• High continuous loads;
• Idle or standby loads;
• Environmental mismatch;
• Peak-demand contribution;
• Unusual operating schedules;
• Equipment operating longer than expected;
• Equipment operating more frequently than expected;
• Changes in electrical behaviour;
• Other patterns that may indicate avoidable consumption.

The identification of an opportunity does not necessarily mean that energy use is definitively unnecessary or that a particular corrective action is appropriate.

Facility conditions, operational requirements, safety requirements, equipment requirements, customer objectives, and other factors may affect whether an identified opportunity should be acted upon.

To Estimate Energy Savings

We may use measured information, historical information, utility information, operating schedules, calculations, assumptions, and analytical models to estimate potential energy savings.

Savings estimates may be based on factors such as:

• Measured power;
• Estimated runtime reduction;
• Historical runtime;
• Current operating schedule;
• Proposed operating schedule;
• Utility rates;
• Demand charges;
• Equipment behaviour;
• Facility behaviour;
• Seasonal variation;
• Historical consumption.

Estimates may be expressed as:

• Kilowatt-hours;
• Demand reduction;
• Annual energy savings;
• Monthly energy savings;
• Percentage reduction;
• Savings ranges;
• Other energy-related metrics.

To Estimate Financial Savings

We may use utility pricing, rate information, estimated energy reduction, demand reduction, operating schedules, and other relevant data to estimate the financial value of identified opportunities.

Financial estimates may include:

• Estimated annual savings;
• Estimated monthly savings;
• Estimated avoided energy cost;
• Estimated demand-cost savings;
• Estimated cumulative savings;
• Savings ranges;
• Other cost-related estimates.

Financial estimates are dependent on assumptions and inputs and may vary based on actual operating conditions, utility rates, implementation results, equipment performance, facility changes, weather, occupancy, or other factors.

To Calculate Return on Investment and Payback

Where appropriate, we may combine project costs with estimated savings to calculate financial metrics intended to help customers evaluate potential investments.

This may include:

• Simple payback;
• Estimated payback period;
• Return on investment;
• Estimated annual return;
• Estimated cumulative savings;
• Cost-benefit comparisons;
• Scenario comparisons.

These calculations may be based on assumptions and should not necessarily be interpreted as guarantees of future financial performance.

To Support Retrofit Decisions

We may use collected information and Facility Intelligence Data to support evaluation of potential equipment retrofits, replacements, upgrades, control changes, operational improvements, or other facility investments.

This may involve:

• Understanding current equipment performance;
• Establishing existing baselines;
• Estimating current energy use;
• Evaluating runtime;
• Evaluating demand;
• Modeling potential changes;
• Comparing existing and proposed equipment;
• Estimating possible savings;
• Calculating payback;
• Evaluating different scenarios;
• Supporting data-backed decision-making.

To Generate Simulations and Scenarios

Where supported, we may use information to model or simulate possible changes to a facility, equipment, operating schedule, energy use, or project configuration.

Examples may include:

• Equipment replacement scenarios;
• Schedule-change scenarios;
• Load-reduction scenarios;
• Retrofit scenarios;
• Demand-management scenarios;
• Energy-cost scenarios;
• Operating-hour scenarios.

Simulations and scenarios may rely on assumptions and may not predict actual future results with certainty.

To Detect Changes in Equipment Behaviour

We may compare current equipment information with historical information to identify changes in electrical or operating behaviour.

This may include changes in:

• Runtime;
• Cycling;
• Power draw;
• Start behaviour;
• Stop behaviour;
• Load shape;
• Demand contribution;
• Operating schedule;
• Electrical signature;
• Energy consumption;
• Frequency of operation.

Changes may be used to identify potential operational concerns, changes in facility use, maintenance indicators, or opportunities for further investigation.

To Identify Operational Anomalies

We may use analytical processes to identify activity that appears unusual when compared with historical, expected, or customer-defined patterns.

Potential anomalies may include:

• Unexpected runtime;
• Unexpected start times;
• Unexpected shutdowns;
• Changes in cycling;
• Increased load;
• Decreased load;
• Unusual continuous operation;
• Changes in demand;
• Changes in energy consumption;
• Changes in operating patterns;
• Missing data;
• Unusual device behaviour.

An anomaly is an analytical indication that a pattern may differ from expected behaviour and does not necessarily mean that a fault or problem exists.

To Generate Predictive or Preventative Maintenance Indicators

Where supported by available data and functionality, Opti-mized may use changes in equipment electrical behaviour, runtime, cycling, load characteristics, or historical performance to identify indicators that may be relevant to maintenance.

These indicators may include:

• Changes in runtime;
• Changes in cycling;
• Changes in power draw;
• Changes in electrical behaviour;
• Changes in operating consistency;
• Deviation from established baselines;
• Unusual equipment patterns.

Such indicators may be used to identify equipment that may warrant further inspection or attention.

They are not intended to replace appropriate inspection, servicing, maintenance, professional judgment, or equipment safety procedures.

To Prioritize Identified Opportunities

We may use information to help customers prioritize detected energy, operational, maintenance, or retrofit opportunities.

Prioritization may consider factors such as:

• Estimated savings;
• Estimated cost;
• Estimated payback;
• Magnitude of energy consumption;
• Frequency of occurrence;
• Duration;
• Demand contribution;
• Equipment importance;
• Customer priorities;
• Potential operational impact;
• Available information.

Opportunities may be displayed, ranked, grouped, filtered, or categorized to help customers review a larger number of findings.

To Generate Reports

We may use information to prepare Facility Intelligence Reports and other reports, summaries, analyses, or exports.

Reports may contain:

• Facility information;
• Equipment information;
• Utility information;
• Energy information;
• Runtime information;
• Detected opportunities;
• Savings estimates;
• Financial estimates;
• Payback calculations;
• Charts;
• Graphs;
• Tables;
• Photographs;
• Equipment descriptions;
• Recommendations;
• Findings;
• Historical comparisons;
• Facility Intelligence Data.

Reports may be generated automatically, manually, or through a combination of software processes and human review.

To Generate Alerts and Notifications

We may use information to generate alerts or notifications based on account, device, facility, equipment, energy, operational, or security activity.

Notifications may relate to:

• Equipment behaviour;
• Detected opportunities;
• Operational anomalies;
• Changes in equipment behaviour;
• Gateway connectivity;
• Device status;
• Data availability;
• Report availability;
• Account activity;
• Security issues;
• Support updates;
• Platform maintenance;
• System notices;
• Billing matters;
• Other service information.

Notifications may be delivered through available channels such as the Opti-mized platform, email, SMS, or other communication methods where supported.

To Provide Recommendations

We may use information to provide recommendations intended to help customers better understand, evaluate, or manage facility energy performance and equipment operation.

Recommendations may relate to:

• Operating schedules;
• Further investigation;
• Equipment usage;
• Energy-loss opportunities;
• Demand;
• Retrofit evaluation;
• Potential operational changes;
• Maintenance review;
• Data collection;
• Hardware expansion;
• Facility setup.

Recommendations may be based on available information and should be considered together with facility-specific operational, technical, safety, financial, and professional considerations.

To Compare Historical Performance

We may use information to compare performance over different periods.

Comparisons may include:

• Day-over-day;
• Week-over-week;
• Month-over-month;
• Year-over-year;
• Weekday versus weekend;
• Operating hours versus off-hours;
• Seasonal comparisons;
• Before-and-after comparisons;
• Pre-retrofit and post-retrofit comparisons;
• Current performance versus baseline;
• Current performance versus historical averages.

To Verify Results

Where changes, retrofits, operational adjustments, or other actions are implemented, we may use information collected after implementation to evaluate whether facility or equipment performance changed.

This may include:

• Comparing before-and-after energy use;
• Comparing runtime;
• Comparing demand;
• Comparing equipment behaviour;
• Comparing operating schedules;
• Comparing financial estimates;
• Evaluating whether an identified condition continues;
• Evaluating whether an opportunity appears to have been addressed.

To Support Measurement and Verification

Where appropriate, we may use Energy and Operational Data, historical information, utility information, and Facility Intelligence Data to support measurement and verification activities.

This may involve establishing a baseline, documenting pre-implementation performance, measuring post-implementation performance, and comparing results over time.

To Support Portfolio-Level Analysis

Customers with multiple facilities may use Opti-mized across a portfolio.

We may use information to provide:

• Portfolio dashboards;
• Facility comparisons;
• Facility rankings;
• Aggregate savings information;
• Aggregate energy consumption;
• Aggregate demand information;
• Cross-facility trends;
• Equipment comparisons;
• Opportunity comparisons;
• Portfolio-level reports;
• Other multi-facility analytics.

To Process and Fulfill Purchases

We may use information to process customer purchases and commercial transactions.

This may include:

• Preparing quotations;
• Processing orders;
• Confirming orders;
• Creating invoices;
• Processing payments through third-party providers;
• Confirming payment;
• Coordinating shipping;
• Delivering hardware;
• Providing services;
• Managing subscriptions;
• Administering renewals;
• Processing returns;
• Processing refunds;
• Handling warranties;
• Maintaining purchase histories;
• Maintaining financial records;
• Communicating about orders.

To Ship Products

Where physical hardware is purchased, we may use contact, shipping, order, and transaction information to:

• Prepare shipments;
• Create shipping labels;
• Coordinate with carriers;
• Provide tracking information;
• Confirm delivery;
• Resolve delivery issues;
• Manage lost shipments;
• Process returns;
• Handle replacement shipments;
• Comply with customs or shipping requirements where applicable.

To Administer Billing and Accounts Receivable

We may use information to:

• Issue invoices;
• Track payment status;
• Process purchase orders;
• Manage accounts receivable;
• Apply credits;
• Process refunds;
• Maintain tax records;
• Maintain accounting records;
• Reconcile transactions;
• Respond to billing questions;
• Manage commercial relationships.

To Provide Customer Service

We may use information to respond to customer questions, requests, inquiries, complaints, or other communications.

This may include:

• Responding to account questions;
• Explaining platform functionality;
• Assisting with reports;
• Assisting with facility setup;
• Assisting with hardware;
• Resolving billing questions;
• Responding to order questions;
• Helping customers manage user access;
• Providing product information;
• Addressing service concerns;
• Recording customer requests;
• Following up on unresolved matters.

To Provide Technical Support

We may use technical, hardware, account, facility, device, diagnostic, and communications information to investigate and resolve technical issues.

Support activities may include:

• Reviewing gateway status;
• Reviewing sensor status;
• Reviewing connectivity;
• Reviewing system logs;
• Reviewing error messages;
• Reviewing recent data;
• Reviewing configuration;
• Reviewing firmware version;
• Diagnosing communication failures;
• Diagnosing data issues;
• Recommending corrective steps;
• Updating configuration;
• Supporting reconnection;
• Replacing hardware;
• Documenting resolution.

To Troubleshoot Connectivity

We may use network and device information to identify and resolve issues relating to:

• Wi-Fi;
• Ethernet;
• Cellular connections;
• Internet connectivity;
• Cloud connectivity;
• Gateway communication;
• Device communication;
• Data transmission;
• Authentication;
• Configuration.

To Maintain Our Products and Services

We may use information to maintain the ongoing performance, reliability, compatibility, stability, availability, and functionality of our products and services.

This may include:

• Maintaining databases;
• Maintaining cloud infrastructure;
• Maintaining software;
• Maintaining hardware;
• Updating firmware;
• Updating platform features;
• Correcting errors;
• Repairing defects;
• Maintaining integrations;
• Monitoring service availability;
• Maintaining backups;
• Testing system performance;
• Updating configurations;
• Maintaining technical documentation.

To Improve Our Products

We may use information to understand how Opti-mized products perform and identify opportunities to improve them.

This may include evaluating:

• Product reliability;
• Hardware reliability;
• Gateway reliability;
• Sensor performance;
• Data quality;
• Platform performance;
• Analytics accuracy;
• User experience;
• Feature adoption;
• Report usefulness;
• Customer feedback;
• Support issues;
• Common configuration challenges;
• Technical failures.

Information may be used to identify design improvements, prioritize product development, improve reliability, simplify workflows, and improve customer experience.

To Develop New Products, Features, Analytics, and Services

We may use information, including aggregated or de-identified information where appropriate, to research, design, develop, test, evaluate, and improve new Opti-mized products and services.

Development activities may include:

• New platform functionality;
• New dashboards;
• New reports;
• New hardware;
• New sensors;
• New gateway functionality;
• New integrations;
• New analytics;
• New energy-loss detection methods;
• New maintenance indicators;
• New benchmarking tools;
• New calculations;
• New facility intelligence features;
• New automation;
• New customer workflows;
• New mobile or web applications.

To Test Products and Features

We may use information to test software, hardware, analytics, reports, calculations, and features before or after deployment.

Testing may include:

• Quality assurance;
• Performance testing;
• Regression testing;
• Security testing;
• Reliability testing;
• Hardware testing;
• Firmware testing;
• Data-validation testing;
• Analytics testing;
• User-interface testing;
• Integration testing.

Where practical, testing may use synthetic, aggregated, de-identified, or limited information rather than directly identifiable information.

To Improve Analytics

We may use historical information, customer feedback, measurement results, comparisons, and analytical outcomes to improve how Opti-mized generates Facility Intelligence Data.

This may include improving:

• Equipment classification;
• Runtime calculations;
• Baseline creation;
• Anomaly detection;
• Energy-loss detection;
• Savings calculations;
• Demand analysis;
• Equipment behaviour analysis;
• Ranking methods;
• Reporting;
• Recommendations.

To Conduct Internal Analytics

We may analyze information internally to better understand our business, products, customers, services, and operations.

Internal analytics may include:

• Number of users;
• Number of customers;
• Number of facilities;
• Platform usage;
• Feature usage;
• Report usage;
• Hardware deployment;
• Device health;
• Support trends;
• Customer retention;
• Website activity;
• Product adoption;
• Order trends;
• Service performance;
• System reliability;
• Data quality;
• Business performance.

Internal analytics may be conducted using aggregated or de-identified information where appropriate.

To Create Aggregated Information

We may aggregate information from multiple users, facilities, devices, customers, or time periods so that the resulting information provides broader statistical or analytical insights.

Aggregated information may be used for:

• Product development;
• Benchmarking;
• Internal analytics;
• Capacity planning;
• Research;
• Reporting;
• Improving analytics;
• Understanding equipment performance;
• Understanding facility trends;
• Improving customer experience.

To Create De-Identified Information

Where permitted by law, we may remove, generalize, mask, or otherwise process identifiers so that information is no longer reasonably associated with an identifiable individual.

De-identified information may be used for legitimate business purposes including:

• Research;
• Product development;
• Analytics development;
• Benchmarking;
• Quality assurance;
• System improvement;
• Statistical analysis;
• Business planning.

To Create Benchmarks

Where appropriate, we may use historical, aggregated, de-identified, or facility-specific information to develop benchmarks.

Benchmarks may allow a customer to compare:

• Current facility performance with historical performance;
• Equipment performance with its own historical baseline;
• Similar equipment;
• Comparable time periods;
• Comparable facility characteristics;
• Other appropriate reference points.

To Monitor Product Performance

We may use technical and operational information to evaluate whether Opti-mized products and systems are functioning as intended.

This may include monitoring:

• Device connectivity;
• Data transmission;
• Measurement quality;
• Gateway health;
• Sensor health;
• Software performance;
• Platform response time;
• API availability;
• Error rates;
• Service availability;
• Report-generation success;
• Notification delivery.

To Maintain Data Quality

We may use information to identify and address possible errors, inconsistencies, missing values, duplicate records, incorrect mappings, or other data-quality concerns.

This may include:

• Validating measurements;
• Checking device assignments;
• Checking circuit mappings;
• Reviewing unusual readings;
• Correcting customer-provided labels;
• Normalizing equipment names;
• Identifying duplicate equipment;
• Resolving missing data;
• Comparing configuration information against uploaded documents.

To Maintain Accurate Customer Records

We may use information to maintain accurate records relating to:

• Customers;
• Organizations;
• Facilities;
• Users;
• Hardware;
• Equipment;
• Orders;
• Contracts;
• Support history;
• Installation history;
• Billing;
• Communications.

To Communicate With You

We may use contact information to communicate with customers, prospective customers, authorized users, contractors, consultants, and other business contacts.

Communications may relate to:

• Account setup;
• Account administration;
• Orders;
• Payments;
• Shipping;
• Product updates;
• Platform updates;
• Facility setup;
• Installation;
• Commissioning;
• Technical support;
• Customer support;
• Reports;
• Alerts;
• Detected conditions;
• Service availability;
• Maintenance;
• Security;
• Contracts;
• Billing;
• Renewals;
• Customer requests;
• Product demonstrations;
• Quotations;
• Other business matters.

To Send Service-Related Communications

Certain communications are necessary to operate or administer Opti-mized services and may not be considered marketing communications.

These may include:

• Account verification;
• Password reset information;
• Security notices;
• Login alerts;
• Account status notices;
• System-maintenance notices;
• Service interruption notices;
• Billing notices;
• Invoice communications;
• Order confirmations;
• Shipping notices;
• Support responses;
• Report notifications;
• Device connectivity alerts;
• Changes to terms or policies where required;
• Other administrative communications.

To Send Marketing Communications

Where permitted by applicable law, we may use business contact information to provide communications concerning:

• Opti-mized products;
• New features;
• New services;
• Product updates;
• Industry information;
• Educational materials;
• Demonstrations;
• Events;
• Case studies;
• Newsletters;
• Promotional offers;
• Other marketing content.

Where consent is required, we will seek appropriate consent before sending applicable marketing communications.

Recipients may be able to unsubscribe from promotional communications using the methods provided in those communications or otherwise made available by Opti-mized.

Choosing not to receive marketing communications does not necessarily prevent Opti-mized from sending transactional, administrative, security, support, or service-related communications.

To Respond to Inquiries and Sales Requests

We may use information provided by prospective customers to:

• Respond to questions;
• Schedule demonstrations;
• Understand customer needs;
• Prepare quotations;
• Recommend hardware;
• Discuss services;
• Evaluate facility requirements;
• Provide product information;
• Follow up on inquiries;
• Maintain prospective customer records;
• Manage sales opportunities.

To Prepare Quotations and Proposals

We may use facility, customer, project, hardware, and commercial information to prepare:

• Quotes;
• Proposals;
• Statements of work;
• Pricing estimates;
• Hardware lists;
• Scope descriptions;
• Deployment recommendations;
• Project schedules;
• Other commercial documents.

To Manage Customer Relationships

We may use information to administer our ongoing relationship with customers.

This may include:

• Maintaining customer records;
• Tracking projects;
• Tracking orders;
• Tracking support matters;
• Maintaining contact information;
• Understanding service history;
• Managing renewals;
• Managing facility expansion;
• Managing additional hardware orders;
• Documenting customer preferences;
• Managing contracts;
• Maintaining project communications.

To Manage Contractors and Service Providers

We may use information to coordinate work performed by contractors, installers, consultants, shipping providers, technical providers, and other service providers.

This may include:

• Assigning work;
• Providing facility information;
• Coordinating schedules;
• Managing installation;
• Managing support;
• Tracking deliverables;
• Processing invoices;
• Maintaining records;
• Evaluating provider performance.

Information shared for these purposes will generally be limited to information reasonably necessary for the applicable provider to perform its services.

To Improve Customer Experience

We may use information about customer interactions, feedback, platform use, support history, and product use to identify ways to make Opti-mized products easier to use and more effective.

This may include:

• Simplifying onboarding;
• Improving facility setup;
• Improving dashboards;
• Improving reports;
• Improving navigation;
• Improving configuration tools;
• Improving alerts;
• Improving support materials;
• Improving installation processes;
• Reducing technical issues.

To Personalize the Service

Where appropriate, we may use information to tailor the Opti-mized experience to the customer, organization, facility, or user.

This may include:

• Displaying relevant facilities;
• Applying customer-specific names;
• Remembering preferences;
• Configuring dashboards;
• Showing relevant equipment;
• Applying selected filters;
• Providing relevant reports;
• Delivering configured alerts;
• Maintaining user-specific access rights.

To Protect the Security of Our Systems

We may use information to protect Opti-mized infrastructure, hardware, software, customer accounts, and information.

Security purposes may include:

• Detecting unauthorized access;
• Detecting suspicious activity;
• Detecting unusual login patterns;
• Preventing credential misuse;
• Monitoring network activity;
• Identifying malicious requests;
• Identifying attempted attacks;
• Investigating security events;
• Responding to incidents;
• Protecting customer accounts;
• Protecting cloud infrastructure;
• Protecting connected devices;
• Maintaining access controls;
• Maintaining audit trails;
• Improving security systems.

To Prevent Fraud and Abuse

We may use account, transaction, technical, security, and other information to prevent, identify, investigate, or respond to:

• Fraudulent transactions;
• Unauthorized purchases;
• Account misuse;
• Credential theft;
• Unauthorized access;
• Automated abuse;
• Malicious activity;
• Misuse of Opti-mized products;
• Violations of applicable terms;
• Other harmful activity.

To Detect and Respond to Security Incidents

We may use information to investigate actual or suspected security incidents.

This may include:

• Reviewing logs;
• Reviewing access history;
• Reviewing user permissions;
• Reviewing device activity;
• Reviewing IP addresses;
• Reviewing authentication activity;
• Determining affected accounts;
• Determining affected systems;
• Containing incidents;
• Restoring systems;
• Notifying affected parties where required;
• Complying with legal reporting obligations;
• Documenting incident response.

To Maintain Business Continuity

We may use and retain information as necessary to support:

• Backups;
• Disaster recovery;
• Service restoration;
• Data recovery;
• Hardware replacement;
• System redundancy;
• Operational continuity;
• Incident response.

To Enforce Our Terms and Agreements

We may use information to administer and enforce:

• Customer agreements;
• Terms of service;
• Purchase terms;
• Subscription terms;
• Acceptable-use requirements;
• Confidentiality agreements;
• Licensing terms;
• Other contractual obligations.

This may include investigating suspected violations, resolving contractual disputes, or restricting access where appropriate.

To Comply With Legal Obligations

We may use, retain, or disclose information where reasonably necessary to comply with applicable laws, regulations, regulatory requirements, court orders, legal proceedings, subpoenas, lawful government requests, taxation requirements, accounting requirements, recordkeeping requirements, or other legal obligations.

This may include:

• Maintaining financial records;
• Maintaining transaction records;
• Responding to lawful requests;
• Complying with privacy laws;
• Complying with security obligations;
• Complying with tax laws;
• Complying with corporate recordkeeping requirements;
• Cooperating with lawful investigations;
• Meeting reporting obligations;
• Preserving records when legally required.

To Respond to Government and Regulatory Requests

Where legally required or appropriately authorized, we may use or disclose information in response to requests from:

• Courts;
• Regulatory authorities;
• Law-enforcement authorities;
• Government agencies;
• Tax authorities;
• Other public authorities.

We may evaluate requests to determine whether they appear valid and whether disclosure is legally required or otherwise appropriate.

To Establish, Exercise, or Defend Legal Claims

We may use information where reasonably necessary to establish, exercise, investigate, pursue, resolve, or defend legal rights or claims.

This may include matters involving:

• Contract disputes;
• Payment disputes;
• Intellectual-property matters;
• Customer disputes;
• Vendor disputes;
• Fraud;
• Security incidents;
• Regulatory proceedings;
• Insurance matters;
• Litigation;
• Arbitration;
• Other legal proceedings.

To Protect Rights, Property, and Safety

Where appropriate and permitted by law, we may use or disclose information where reasonably necessary to protect:

• Opti-mized;
• Our customers;
• Our users;
• Our personnel;
• Our service providers;
• Our systems;
• Our property;
• Our intellectual property;
• Our legal rights;
• The rights or safety of other persons.

For Accounting and Financial Administration

We may use transaction, customer, contract, and payment-related information for:

• Bookkeeping;
• Accounting;
• Financial reporting;
• Accounts payable;
• Accounts receivable;
• Audits;
• Tax preparation;
• Tax compliance;
• Financial planning;
• Revenue recognition;
• Expense administration;
• Transaction reconciliation;
• Other financial administration.

For Insurance Purposes

Where appropriate, we may use information in connection with insurance matters such as:

• Claims;
• Coverage;
• Risk assessment;
• Incident reporting;
• Loss investigation;
• Legal disputes.

For Corporate Transactions

If Opti-mized is involved in or considers a merger, acquisition, financing, investment, reorganization, asset sale, business sale, insolvency, bankruptcy, or similar corporate transaction, information may be used as reasonably necessary to evaluate, negotiate, complete, or administer the transaction.

Appropriate confidentiality and data-protection measures may be used where required.

For Auditing and Compliance

We may use information to conduct internal or external audits and compliance reviews relating to:

• Information security;
• Privacy;
• Financial records;
• Customer agreements;
• System access;
• Product quality;
• Operational procedures;
• Legal requirements;
• Vendor performance;
• Other business controls.

To Maintain Audit Logs

We may maintain records of important actions taken within Opti-mized systems.

Audit logs may record:

• User logins;
• Permission changes;
• Configuration changes;
• Data exports;
• Facility changes;
• Account changes;
• Device changes;
• Administrative actions;
• Security events;
• Report generation;
• Other significant activity.

Audit information may be used for security, troubleshooting, customer support, compliance, and accountability.

To Manage Data Retention and Deletion

We may use information about data type, account status, customer relationships, contractual obligations, and legal requirements to determine how long particular information should be retained.

Information may also be used to:

• Process deletion requests;
• Process account closures;
• Apply retention schedules;
• Maintain legal holds;
• Remove expired data;
• De-identify records;
• Archive records;
• Maintain backup retention;
• Document deletion activity.

To Respond to Privacy Requests

We may use identity, account, contact, and other information to verify and respond to requests relating to privacy rights.

Depending on applicable law, requests may concern:

• Access;
• Correction;
• Deletion;
• Portability;
• Objection;
• Restriction;
• Consent withdrawal;
• Marketing preferences;
• Other privacy rights.

We may request additional information where reasonably necessary to verify the identity or authority of the person making a request.

To Obtain and Maintain Consent

Where consent is required, we may use information to:

• Request consent;
• Record consent;
• Maintain consent records;
• Record withdrawal of consent;
• Manage communication preferences;
• Manage cookie preferences;
• Document authorization for particular processing activities.

To Comply With Customer Instructions

Where Opti-mized processes information on behalf of a customer, we may use information as instructed or authorized by that customer, subject to applicable law and agreements.

For example, a customer may direct Opti-mized to:

• Create user accounts;
• Configure facilities;
• Analyze data;
• Generate reports;
• Send notifications;
• Add integrations;
• Provide information to authorized consultants;
• Support particular users;
• Process facility information for a specific project.

To Support Integrations

Where customers enable third-party integrations, we may use information to:

• Authenticate connections;
• Exchange data;
• Synchronize information;
• Match facility records;
• Match device records;
• Import information;
• Export information;
• Maintain integration status;
• Detect integration errors;
• Troubleshoot integrations;
• Provide requested integrated functionality.

To Support APIs

Where APIs are used, we may process information to:

• Authenticate requests;
• Authorize access;
• Provide requested data;
• Receive data;
• Maintain API security;
• Monitor usage;
• Apply rate limits;
• Diagnose errors;
• Maintain integrations;
• Maintain audit records.

To Ensure Compatibility

We may use device, browser, software, hardware, and configuration information to ensure compatibility between:

• Browsers and the Opti-mized platform;
• Hardware and firmware;
• Gateways and sensors;
• Devices and communications networks;
• APIs and integrations;
• Different versions of software;
• Customer systems and supported integrations.

To Perform Quality Assurance

We may use information to evaluate whether products, reports, analytics, and services meet expected standards.

Quality assurance may include:

• Checking data accuracy;
• Reviewing report outputs;
• Reviewing calculations;
• Checking configuration accuracy;
• Checking device operation;
• Reviewing customer feedback;
• Investigating defects;
• Testing corrective changes.

To Conduct Research and Development

Where permitted and appropriate, we may use information, including aggregated or de-identified information, to conduct research relating to:

• Energy analytics;
• Facility behaviour;
• Equipment behaviour;
• Electrical patterns;
• Hardware performance;
• Sensor performance;
• Product reliability;
• Facility intelligence;
• Energy-loss detection;
• Demand analysis;
• Maintenance indicators;
• Benchmarking;
• Other areas relevant to Opti-mized products and services.

To Improve Automation and Analytical Systems

We may use appropriate data to evaluate and improve automated systems used to classify, calculate, detect, organize, or analyze facility information.

This may include improving systems used for:

• Equipment classification;
• Photo interpretation;
• Document information extraction;
• Runtime analysis;
• Energy-loss detection;
• Anomaly detection;
• Savings calculations;
• Report generation;
• Equipment mapping;
• Data-quality checks;
• Facility configuration support.

Where personal information is involved, such uses will be subject to applicable law, contractual commitments, and appropriate safeguards.

To Develop Statistical Insights

We may use aggregated, de-identified, or otherwise appropriately processed information to understand broader trends.

For example, we may analyze:

• Typical hardware performance;
• Typical data-transmission reliability;
• Common equipment usage patterns;
• Typical platform usage;
• Common customer-support issues;
• General facility energy patterns;
• General product adoption;
• General equipment behaviour.

To Improve Capacity Planning

We may use information about system activity, data volume, connected hardware, customer growth, and usage to plan:

• Cloud capacity;
• Storage capacity;
• Network capacity;
• Database capacity;
• Hardware support capacity;
• Customer-support resources;
• Technical infrastructure;
• Product development.

To Diagnose and Correct Errors

We may use technical, account, platform, hardware, and facility information to diagnose software or hardware problems.

This may include identifying:

• Software bugs;
• Data-processing errors;
• Missing measurements;
• Incorrect mappings;
• Device failures;
• Failed API requests;
• Authentication errors;
• Report errors;
• Notification errors;
• User-interface errors;
• Configuration problems.

To Prevent Data Loss

We may use information to support backup, redundancy, synchronization, recovery, and restoration processes designed to reduce the risk of information loss.

To Maintain Historical Records

Certain historical information may be maintained to support:

• Trend analysis;
• Baseline analysis;
• Historical comparisons;
• Reports;
• Customer support;
• Measurement and verification;
• Equipment behaviour analysis;
• Legal compliance;
• Contract administration.

To Understand Customer Needs

We may use feedback, communications, usage information, support requests, purchasing history, and facility information to understand what customers need from Opti-mized products.

This may help us determine:

• Which features to develop;
• Which reports are most useful;
• Which hardware configurations are common;
• Which facility types require particular workflows;
• Which support resources are needed;
• Which improvements should be prioritized.

To Evaluate Business Performance

We may use aggregated business information to assess:

• Revenue;
• Sales;
• Customer acquisition;
• Customer retention;
• Product adoption;
• Hardware deployments;
• Platform usage;
• Support demand;
• Operating costs;
• Service performance;
• Other business metrics.

To Administer Projects

Where Opti-mized provides products or services as part of a customer project, we may use information to:

• Define project scope;
• Manage milestones;
• Coordinate customer contacts;
• Coordinate contractors;
• Track deliverables;
• Manage facility access;
• Track hardware;
• Track installation;
• Manage documentation;
• Track reports;
• Maintain communications;
• Manage project completion.

To Maintain Confidentiality and Access Restrictions

We may use customer, organization, user, and permission information to enforce confidentiality and access limitations.

For example, information may be used to ensure that:

• One customer cannot access another customer's data;
• Users see only authorized facilities;
• Administrative functions are restricted;
• Reports are delivered to authorized recipients;
• Facility data is accessible only to appropriate parties.

To Meet Contractual Obligations

We may process information where necessary to perform obligations under agreements with customers, suppliers, contractors, partners, or other parties.

This may include obligations relating to:

• Service delivery;
• Support;
• Hardware supply;
• Installation;
• Reporting;
• Security;
• Data processing;
• Billing;
• Retention;
• Confidentiality;
• Compliance.

To Exercise Contractual Rights

Information may also be used where reasonably necessary to exercise rights available to Opti-mized under applicable agreements, including rights relating to:

• Payment;
• Account suspension;
• Service restrictions;
• Contract enforcement;
• Intellectual-property protection;
• Dispute resolution;
• Termination.

To Comply With Procurement and Funding Requirements

Where customer projects involve public procurement, grants, utility programs, government funding, incentives, or other third-party programs, we may use information to satisfy applicable administrative or reporting requirements.

This may include:

• Project information;
• Facility information;
• Customer information;
• Pricing information;
• Milestone information;
• Reports;
• Savings information;
• Project documentation.

To Respond to Emergencies or Urgent Security Issues

Where reasonably necessary, we may use information to respond to urgent situations involving the security, integrity, or availability of our systems or customer services.

To Support Business Operations Generally

We may use information for other ordinary and legitimate internal business purposes reasonably related to operating Opti-mized.

These may include:

• Strategic planning;
• Operational planning;
• Workforce planning;
• Vendor management;
• Procurement;
• Budgeting;
• Business forecasting;
• Internal reporting;
• Corporate administration;
• Policy development;
• Risk management;
• Training;
• Quality management.

Use of Aggregated, De-Identified, and Non-Personal Information

Where information has been aggregated or de-identified so that it no longer identifies or can reasonably be linked to an identifiable individual, we may use that information for purposes such as:

• Analytics;
• Benchmarking;
• Research;
• Product improvement;
• Product development;
• Business planning;
• Statistical analysis;
• System optimization;
• Quality assurance;
• Reporting;
• Trend analysis.

Information relating solely to equipment, commercial facilities, electrical systems, or other non-personal matters may also be used for legitimate business purposes, subject to applicable contractual, confidentiality, and security obligations.

No Guarantee of Analytical Outcomes

Certain Opti-mized outputs, including savings estimates, return-on-investment calculations, payback calculations, anomaly detections, maintenance indicators, equipment classifications, opportunity classifications, simulations, forecasts, benchmarks, and recommendations, may be based on available data, customer-provided information, measurements, assumptions, calculations, algorithms, models, or historical patterns.

These outputs may assist customers in understanding facility performance and making decisions, but they should not necessarily be interpreted as guarantees of future energy savings, financial performance, equipment condition, operational results, or other outcomes.

Actual results may vary depending on factors including:

• Facility conditions;
• Equipment condition;
• Weather;
• Occupancy;
• Operating schedules;
• Utility rates;
• Customer actions;
• Maintenance practices;
• Equipment controls;
• Building changes;
• Data availability;
• Data quality;
• Changes in facility use;
• Implementation quality;
• Other factors outside Opti-mized's control.

Relationship Between Raw Data and Facility Intelligence Data

Many Opti-mized services involve transforming raw or relatively simple information into more useful facility intelligence.

For example, Opti-mized may begin with a sequence of electrical measurements associated with a circuit.

Those measurements may then be:

1. Associated with a specific facility;
2. Associated with a specific panel;
3. Associated with a specific circuit;
4. Associated with a specific piece of equipment;
5. Compared against historical operation;
6. Compared with facility operating schedules;
7. Compared with environmental conditions where applicable;
8. Combined with utility-rate information;
9. Analyzed for patterns or changes;
10. Used to estimate energy consumption;
11. Used to identify a potential energy-loss opportunity;
12. Used to calculate potential savings;
13. Used to rank the opportunity;
14. Presented through the Opti-mized dashboard or a Facility Intelligence Report.

Accordingly, information may be used through multiple stages of processing in order to provide the functionality and intelligence customers expect from Opti-mized.

Use of Information Across Multiple Opti-mized Services

A customer's information may be used across different Opti-mized products and services where appropriate to provide a consistent customer experience.

For example, information submitted during facility setup may later be used to:

• Prepare a quotation;
• Configure hardware;
• Configure the platform;
• Support installation;
• Label circuits;
• Create equipment records;
• Interpret sensor measurements;
• Generate reports;
• Provide customer support.

Similarly, information collected from hardware may later be used to:

• Populate dashboards;
• Establish baselines;
• Generate Facility Intelligence Data;
• Create reports;
• Generate alerts;
• Support troubleshooting;
• Verify improvements.

We Do Not Necessarily Use Every Category of Information for Every Purpose

The descriptions above identify purposes for which Opti-mized may use information where relevant.

They do not mean that every category of information is used for every purpose.

For example:

• Payment information would not ordinarily be used to analyze equipment behaviour;
• Energy and Operational Data would not ordinarily be used to process a credit-card payment;
• Marketing information would not ordinarily be necessary to configure a sensor;
• Website analytics would not necessarily be used to calculate facility energy savings;
• Facility photographs would not necessarily be used for marketing;
• User login records would not ordinarily be used to calculate retrofit savings.

The actual use of information depends on its nature and the context in which it was collected.

Use Consistent With the Purpose of Collection

Where appropriate, we generally use information for the purposes described at the time of collection, purposes reasonably related to those purposes, purposes described in this Privacy Policy, purposes authorized by the customer or individual, purposes required to provide requested products or services, and other purposes permitted or required by applicable law.

If we intend to use personal information for a materially different purpose that is incompatible with the purpose for which it was originally collected, we may provide additional notice, obtain consent where required, or take other measures required by applicable law.

Summary of How We Use Information

In general, Opti-mized may use information to:

• Create, maintain, secure, and administer user accounts;
• Authenticate users and manage access permissions;
• Provide and operate the Opti-mized platform;
• Operate Opti-mized hardware and connected services;
• Receive and process Energy and Operational Data;
• Understand customer facilities;
• Determine appropriate hardware configurations;
• Determine sensor, gateway, CT, and CT Hub requirements;
• Prepare facility setup recommendations;
• Estimate deployment and setup costs;
• Review electrical panel, MCC, switchgear, and equipment photographs;
• Extract relevant information from documents;
• Create panel-by-panel configurations;
• Map panels, circuits, sensors, and equipment;
• Organize facility information;
• Configure dashboards;
• Establish equipment and facility baselines;
• Analyze equipment behaviour;
• Analyze facility behaviour;
• Analyze runtime and cycling;
• Analyze peak demand;
• Analyze baseload and continuous loads;
• Identify on-hours overusage;
• Identify off-hours usage;
• Identify environmental mismatches;
• Identify idle and standby loads;
• Identify high continuous loads;
• Detect unusual or changing equipment behaviour;
• Generate Facility Intelligence Data;
• Identify potential energy-loss opportunities;
• Estimate energy savings;
• Estimate financial savings;
• Calculate return on investment;
• Calculate payback periods;
• Evaluate retrofit opportunities;
• Generate simulations and scenarios;
• Generate reports;
• Generate alerts;
• Generate recommendations;
• Prioritize opportunities;
• Compare historical performance;
• Support measurement and verification;
• Provide portfolio analytics;
• Process purchases;
• Fulfill orders;
• Administer billing;
• Ship products;
• Provide customer service;
• Provide technical support;
• Troubleshoot connectivity and hardware;
• Maintain and improve our products;
• Improve analytical systems;
• Develop new products, features, analytics, and services;
• Conduct research and development;
• Conduct internal analytics;
• Generate aggregated or de-identified information;
• Develop benchmarks;
• Monitor product performance;
• Maintain data quality;
• Maintain accurate customer records;
• Communicate with customers and users;
• Send operational and service-related communications;
• Send marketing communications where permitted by applicable law;
• Respond to sales inquiries;
• Prepare quotations and proposals;
• Manage customer relationships;
• Coordinate contractors and service providers;
• Protect our systems and customers;
• Prevent fraud, misuse, and unauthorized access;
• Detect and respond to security incidents;
• Maintain business continuity;
• Enforce our terms and agreements;
• Maintain audit records;
• Respond to privacy requests;
• Comply with customer instructions;
• Support authorized integrations;
• Meet legal, accounting, tax, regulatory, and contractual obligations;
• Establish, exercise, or defend legal claims;
• Protect our rights, property, systems, users, customers, and personnel;
• Support corporate, administrative, financial, and operational activities; and
• Carry out other legitimate and lawful business purposes consistent with the circumstances in which the information was collected.

The specific purpose for which any particular information is used will depend on the nature of that information, the services being provided, the customer's instructions, the applicable relationship, and applicable legal requirements.

Opti-mized may use information generated, collected, received, derived, or created through the use of our products and services to operate, maintain, evaluate, improve, refine, test, validate, secure, expand, and develop the Opti-mized technology ecosystem.

Improving Opti-mized may involve improving existing products and services as well as researching, designing, testing, and developing new products, services, features, analytical capabilities, hardware, software, reports, workflows, detection methods, calculation methods, algorithms, models, classifications, recommendations, and other facility-intelligence capabilities.

Because Opti-mized is designed to transform facility, electrical, equipment, operational, and contextual information into useful intelligence, the performance of our technology may improve as we gain a better understanding of how facilities, electrical systems, equipment, hardware, software, and analytical methods behave under different conditions.

Accordingly, information collected through Opti-mized may, where appropriate and permitted, be used to improve the accuracy, reliability, usefulness, efficiency, security, scalability, and performance of our products and services.

Depending on the circumstances, information used for these purposes may include:

• Energy and Operational Data;
• Facility Intelligence Data;
• Facility information;
• Equipment information;
• Circuit information;
• Electrical-panel information;
• MCC information;
• Switchgear information;
• Hardware information;
• Gateway information;
• Sensor information;
• Device diagnostics;
• Technical logs;
• Historical measurements;
• Equipment runtime information;
• Equipment cycling information;
• Demand information;
• Baseload information;
• Operating schedules;
• Utility information;
• Weather or environmental information where available;
• Customer-provided classifications;
• Customer corrections;
• Facility configurations;
• Equipment mappings;
• User feedback;
• Support information;
• Platform usage information;
• Product performance information;
• Error information;
• Diagnostic information;
• Reports;
• Customer-requested analyses;
• Analytical outputs;
• Aggregated statistics;
• De-identified information;
• Other information reasonably relevant to product development and improvement.

The particular information used depends on the product, feature, customer relationship, technical need, applicable contractual terms, and applicable law.

Not every category of customer information is used for every improvement purpose.

Improving the Accuracy of Facility Intelligence

A significant purpose of product improvement is to make Opti-mized's Facility Intelligence capabilities more accurate, useful, consistent, and actionable.

We may evaluate information to improve how our systems recognize and interpret facility and equipment behaviour.

For example, information may be used to improve how Opti-mized identifies or analyzes:

• Equipment operating patterns;
• Equipment runtime;
• Equipment start and stop events;
• Cycling behaviour;
• Continuous loads;
• Baseload;
• Idle loads;
• Standby loads;
• On-hours energy usage;
• Off-hours energy usage;
• After-hours operation;
• Demand peaks;
• Peak-demand contribution;
• Load patterns;
• Equipment behaviour changes;
• Deviations from historical baselines;
• Environmental relationships;
• Schedule mismatches;
• Potential operational anomalies;
• Potential energy-loss opportunities;
• Potential retrofit opportunities;
• Maintenance-related indicators;
• Equipment classifications;
• Circuit classifications;
• Facility operating patterns;
• Savings opportunities;
• Cost estimates;
• Return-on-investment calculations;
• Payback calculations;
• Other analytical outputs.

Improvement may involve examining whether the systems correctly identify patterns, whether analytical thresholds are appropriate, whether classifications are useful, whether calculations are consistent, and whether the resulting information is meaningful in actual facility environments.

Improving Runtime Detection

Opti-mized may use historical measurements and other appropriate information to improve the accuracy of runtime detection.

This may involve evaluating whether our analytical systems correctly identify:

• Equipment startup;
• Equipment shutdown;
• Operating periods;
• Idle periods;
• Equipment cycles;
• Partial-load operation;
• Continuous operation;
• Intermittent operation;
• Short-duration operation;
• Extended operation;
• Operation outside scheduled hours.

Where a customer's configuration or equipment mapping indicates that an analytical result is incorrect or incomplete, that information may help us improve the customer-specific configuration and, where appropriate, broader analytical methods using aggregated or de-identified information.

Improving Cycling Analysis

We may use information to improve how Opti-mized detects and interprets equipment cycling.

Cycling analysis may involve understanding:

• Typical cycle duration;
• Typical number of cycles;
• Start frequency;
• Stop frequency;
• Changes in cycle length;
• Changes in cycling frequency;
• Differences between scheduled and actual operation;
• Differences across seasons;
• Differences under different environmental conditions.

Improving cycling analysis may help Opti-mized provide more accurate operational insights and identify changes that may warrant investigation.

Improving Baseline Development

Opti-mized may use historical information to establish expected or representative operating baselines.

We may evaluate and improve methods used to create baselines based on:

• Time of day;
• Day of week;
• Operating schedule;
• Season;
• Weather;
• Outdoor temperature;
• Facility operating status;
• Historical runtime;
• Historical demand;
• Historical energy consumption;
• Equipment-specific behaviour;
• Facility-specific behaviour;
• Other relevant contextual information.

Improved baseline methods can help reduce inaccurate comparisons and provide better context when determining whether current equipment or facility behaviour differs from what would ordinarily be expected.

Improving Anomaly Detection

Opti-mized may use information to evaluate and improve methods for identifying unusual or changing equipment and facility behaviour.

Potential anomaly-detection methods may consider:

• Unusual runtime;
• Unusual startup time;
• Unusual shutdown time;
• Increased power draw;
• Reduced power draw;
• Changes in cycling frequency;
• Changes in load shape;
• Changes in demand;
• Changes in equipment operating schedule;
• Changes in continuous-load characteristics;
• Changes relative to historical operation;
• Unexpected equipment activity;
• Missing measurements;
• Device communication issues;
• Other departures from expected patterns.

Historical examples, customer feedback, technical review, and aggregated or de-identified information may help us improve the sensitivity and usefulness of these detection methods.

Our goal in improving anomaly detection is generally to identify meaningful deviations while reducing unnecessary or unhelpful alerts.

Improving Energy-Loss Detection

We may use information to improve the methods Opti-mized uses to identify potential energy-loss opportunities.

This may include improving our ability to identify patterns associated with:

• On-hours overusage;
• Off-hours usage;
• Environmental mismatch;
• Peak-demand contribution;
• Idle or standby waste;
• High continuous loads;
• Potential retrofit opportunities;
• Other avoidable or potentially avoidable energy use.

Product-improvement activities may involve evaluating how accurately these categories reflect actual facility conditions and how they should be presented, ranked, or prioritized.

Improving Savings Calculations

We may use information to evaluate and improve calculations relating to potential energy and financial savings.

This may involve evaluating:

• Runtime assumptions;
• Measured electrical loads;
• Utility rates;
• Demand charges;
• Operating schedules;
• Annualization methods;
• Seasonal adjustments;
• Baseline periods;
• Avoided energy assumptions;
• Savings ranges;
• Estimated implementation effects;
• Customer-provided cost information;
• Other variables used in calculations.

Where appropriate, actual observed results after a customer takes action may be compared with prior estimates to help evaluate and improve calculation methodologies.

Such comparisons do not necessarily mean that information from one identifiable customer is used directly to make recommendations for another identifiable customer.

Broader learning and benchmarking may instead use aggregated, anonymized, de-identified, statistical, or otherwise appropriately protected information where reasonably practicable.

Improving Return-on-Investment and Payback Calculations

We may use information to improve the methods used to calculate or estimate:

• Project costs;
• Energy savings;
• Financial savings;
• Annual savings;
• Simple payback;
• Return on investment;
• Cost-benefit comparisons;
• Scenario comparisons;
• Retrofit economics.

These calculations may depend on customer-specific inputs, assumptions, facility conditions, utility rates, project costs, and operating behaviour.

Improvement efforts may focus on making calculations easier to understand, more transparent, more consistent, and more representative of available data.

Improving Retrofit Analysis

Opti-mized may use facility and equipment information to improve tools designed to support retrofit evaluations.

This may include improving methods used to:

• Establish current equipment performance;
• Establish existing energy consumption;
• Compare existing and proposed equipment;
• Model operational changes;
• Estimate potential reductions in consumption;
• Estimate potential reductions in demand;
• Compare alternative retrofit scenarios;
• Evaluate potential financial performance;
• Verify results after implementation.

Where appropriate, aggregated or de-identified historical information may also be used to improve general analytical methods used in retrofit evaluation.

Improving Predictive and Preventative Maintenance Indicators

Where supported by our services, we may use historical equipment behaviour and other relevant information to improve methods used to identify potential maintenance-related indicators.

This may include evaluating patterns such as:

• Increasing runtime;
• Increasing cycling;
• Changes in electrical load;
• Changes in power characteristics;
• Changes in startup behaviour;
• Changes in operating consistency;
• Deviation from established baseline patterns;
• Progressive changes over time.

These analytical methods are intended to support facility operators by identifying changes that may warrant additional review.

They are not intended to replace appropriate inspection, servicing, professional judgment, preventive maintenance programs, manufacturer guidance, or safety procedures.

Improving Equipment Classification

Opti-mized may use customer-provided equipment information, electrical patterns, photographs, circuit descriptions, technical information, and other data to improve how equipment is categorized or classified.

For example, systems may be improved to distinguish between different types of:

• HVAC equipment;
• Motors;
• Pumps;
• Fans;
• Lighting;
• Refrigeration equipment;
• Heating equipment;
• Process equipment;
• Other electrical loads.

Customer corrections may also help improve the accuracy of equipment classifications.

Where such corrections contribute to broader product development, we may use aggregated, anonymized, de-identified, or otherwise appropriately protected information where reasonably practicable.

Improving Circuit and Equipment Mapping

Opti-mized may use configuration information to improve tools that help associate:

• Sensors with circuits;
• Circuits with equipment;
• Equipment with panels;
• Equipment with MCCs;
• Equipment with switchgear;
• Gateways with measurement points;
• Equipment with facility areas;
• Equipment with operating schedules.

Improving these relationships can make dashboards, reports, calculations, and Facility Intelligence Data more accurate and easier to understand.

Improving Photo and Document Processing

Where Opti-mized uses software-assisted or automated technologies to review facility photographs, equipment photographs, panel photographs, documents, utility bills, or other submitted materials, we may use appropriate information to improve those capabilities.

For example, improvements may relate to:

• Reading electrical panel labels;
• Identifying circuit information;
• Identifying breaker numbers;
• Identifying equipment names;
• Identifying equipment categories;
• Reading equipment nameplates;
• Recognizing panel schedules;
• Extracting information from utility bills;
• Organizing facility documentation;
• Associating photographs with facility records;
• Identifying missing information;
• Improving data-entry accuracy.

Where customer-specific files are used to perform or improve analysis for that customer, such use may involve identifiable facility information.

Where information is used for broader research or product improvement, we seek to use aggregated, anonymized, de-identified, limited, or otherwise appropriately protected information where reasonably practicable.

Improving Utility-Bill Analysis

We may use utility information to improve methods for interpreting and processing utility bills.

This may include improving our ability to identify:

• Billing periods;
• Electricity consumption;
• Demand;
• Rate classes;
• Energy charges;
• Demand charges;
• Fixed charges;
• Taxes;
• Utility rates;
• Historical usage;
• Billing anomalies;
• Other billing components.

Improvements may help reduce manual data entry and improve the accuracy of savings calculations and historical facility analysis.

Improving Facility Configuration

We may use facility setup information, installation records, customer feedback, support issues, and system activity to improve how customers configure facilities within Opti-mized.

This may include improving:

• Facility setup forms;
• Panel setup;
• MCC setup;
• Switchgear setup;
• Circuit mapping;
• Equipment mapping;
• Hardware selection;
• User permissions;
• Facility hierarchies;
• Configuration workflows;
• Installation workflows;
• Customer onboarding.

For example, if users frequently encounter difficulty completing a particular configuration step, we may use aggregated usage information or support feedback to simplify that step.

Improving Hardware Recommendations

We may evaluate facility configurations, installation records, hardware performance, and customer feedback to improve recommendations regarding:

• Sensor quantities;
• CT quantities;
• CT sizes;
• Gateway quantities;
• CT Hub quantities;
• Hardware placement;
• Communications options;
• Installation configuration;
• Expansion requirements.

This can help make future facility setup processes more efficient and reduce unnecessary hardware or configuration complexity.

Improving Opti-mized Hardware

Information collected through installed hardware may be used to improve hardware reliability, functionality, performance, connectivity, and usability.

This may include analyzing:

• Device health;
• Gateway performance;
• Sensor performance;
• Data-transmission performance;
• Connectivity;
• Signal quality;
• Firmware performance;
• Device uptime;
• Restart events;
• Error rates;
• Communication failures;
• Installation configurations;
• Power or measurement stability;
• Other technical information.

This information may help us identify:

• Hardware defects;
• Firmware issues;
• Connectivity problems;
• Performance limitations;
• Reliability improvements;
• Installation improvements;
• Configuration improvements;
• Compatibility issues.

Improving Gateway Performance

We may use information generated by gateways to improve:

• Wi-Fi reliability;
• Ethernet reliability;
• Cellular connectivity;
• Cloud communication;
• Reconnection behaviour;
• Buffering;
• Data transmission;
• Firmware updates;
• Device configuration;
• Troubleshooting;
• Network resilience.

For example, aggregated diagnostic information may help identify a firmware issue that affects a particular hardware version or communication method.

Improving Sensor and Measurement Quality

We may evaluate measurement information to improve the reliability and consistency of Opti-mized sensing technology.

This may include reviewing:

• Signal quality;
• Measurement stability;
• Data gaps;
• Unexpected readings;
• Sensor errors;
• Calibration behaviour;
• Hardware configuration;
• CT configuration;
• Communication issues;
• Measurement-channel behaviour.

These activities may help us improve hardware design, firmware, installation guidance, diagnostics, and analytical quality controls.

Improving Firmware

Information from installed hardware may be used to identify opportunities to improve firmware.

This may include:

• Correcting bugs;
• Improving communication stability;
• Improving data transmission;
• Improving device security;
• Improving update processes;
• Improving configuration handling;
• Improving diagnostics;
• Improving device compatibility;
• Improving error recovery.

Firmware-improvement activities may use diagnostic and technical information associated with individual devices where necessary to diagnose a particular issue.

Where broader analysis is possible using aggregated or de-identified information, we may use those forms of information where reasonably practicable.

Improving the Opti-mized Platform

We may use information about platform performance and user interaction to improve the functionality, usability, reliability, and design of the Opti-mized platform.

This may include understanding:

• Which features are used;
• Which dashboards are viewed;
• Which reports are accessed;
• Which workflows are completed;
• Which workflows are abandoned;
• Which pages experience errors;
• Which actions take longer than expected;
• Which features generate support requests;
• How users navigate the platform;
• Which features customers find valuable.

We may use these insights to:

• Simplify navigation;
• Improve dashboards;
• Improve visualizations;
• Improve report access;
• Improve search;
• Improve filters;
• Improve configuration tools;
• Improve user permissions;
• Improve alerts;
• Improve onboarding;
• Reduce errors;
• Improve performance;
• Develop new features.

Improving Reports

Opti-mized may use customer feedback, report usage, analytical results, and other appropriate information to improve Facility Intelligence Reports and other reporting functionality.

This may involve improving:

• Report structure;
• Report readability;
• Report accuracy;
• Visualizations;
• Charts;
• Graphs;
• Tables;
• Executive summaries;
• Opportunity descriptions;
• Savings calculations;
• Recommendations;
• Prioritization;
• Equipment summaries;
• Facility summaries;
• Report-generation performance.

Improving Alerts and Notifications

We may use information about alert generation, customer responses, false positives, missed conditions, user preferences, and operational outcomes to improve alerts and notifications.

This may include improving:

• Alert thresholds;
• Alert relevance;
• Alert timing;
• Alert prioritization;
• Notification frequency;
• Notification wording;
• Equipment-specific alerts;
• Device-status alerts;
• Energy-loss alerts;
• Security alerts.

Our objective may include reducing unnecessary notifications while improving the likelihood that meaningful conditions are brought to the customer's attention.

Improving Recommendations

Opti-mized may evaluate whether recommendations are relevant, useful, understandable, and appropriately prioritized.

This may involve using:

• Customer feedback;
• Subsequent facility performance;
• Customer actions;
• Historical data;
• Equipment information;
• Utility information;
• Analytical results.

Information may be used to improve how recommendations are:

• Generated;
• Described;
• Ranked;
• Grouped;
• Prioritized;
• Presented;
• Supported by underlying data.

Improving Prioritization

Customers may identify a large number of potential opportunities across a facility or portfolio.

We may use appropriate information to improve methods for prioritizing opportunities based on factors such as:

• Potential energy savings;
• Potential financial savings;
• Payback;
• Frequency;
• Duration;
• Demand contribution;
• Magnitude of consumption;
• Customer priorities;
• Equipment importance;
• Historical recurrence;
• Confidence in the underlying analysis.

Improving Customer-Specific Intelligence

Customer-specific information may be used to improve services specifically for that customer.

This is different from using information for general product development.

For example, Opti-mized may use a customer's own historical data to improve:

• That customer's equipment baselines;
• That customer's anomaly thresholds;
• That customer's equipment classifications;
• That customer's circuit mappings;
• That customer's savings estimates;
• That customer's runtime analysis;
• That customer's operating schedules;
• That customer's recommendations;
• That customer's alerts;
• That customer's reports.

As more information becomes available about a particular facility, Opti-mized may be able to provide more contextually appropriate intelligence for that facility.

For example, if the system learns that a particular facility normally operates later on Thursdays than on other weekdays, that information may help distinguish expected Thursday operation from potentially unnecessary after-hours activity.

Likewise, if a customer corrects an equipment label, updates an operating schedule, or identifies a particular circuit, that information may be used to improve future analysis for that customer's facility.

Customer-Specific Models, Baselines, and Configurations

Where applicable, Opti-mized may create customer-specific or facility-specific analytical configurations.

These may include:

• Equipment baselines;
• Operating schedules;
• Alert thresholds;
• Equipment classifications;
• Circuit mappings;
• Facility hierarchies;
• Historical reference periods;
• Customer-specific assumptions;
• Utility-rate configurations;
• Savings calculations;
• Equipment behaviour profiles.

These configurations may evolve over time as additional information becomes available.

Customer-specific information may be used as necessary to operate and improve these customer-specific capabilities.

Learning From Customer Corrections

Customers and authorized users may occasionally correct, update, confirm, or supplement information within Opti-mized.

Examples may include:

• Correcting an equipment name;
• Changing a circuit label;
• Updating an operating schedule;
• Correcting a facility configuration;
• Identifying an equipment type;
• Confirming or rejecting a detected condition;
• Updating utility-rate information;
• Correcting an equipment association.

Such corrections may be used to improve the accuracy of the customer's configuration and future Facility Intelligence Data.

Where appropriate, patterns derived from corrections may also contribute to broader product improvement using aggregated, de-identified, anonymized, statistical, or otherwise appropriately protected information.

Learning From Customer Feedback

We may use customer feedback to improve Opti-mized.

Feedback may include:

• Feature requests;
• Suggestions;
• Survey responses;
• Support communications;
• Product comments;
• Usability feedback;
• Report feedback;
• Analytics feedback;
• Hardware feedback;
• Installation feedback;
• Requests for additional functionality;
• Reports of inaccurate classifications or detections.

Feedback may be evaluated individually and in aggregate to identify common needs and areas for improvement.

Learning From Support Interactions

Customer-support and technical-support records may help identify recurring problems or opportunities to improve our products.

For example, we may identify that customers frequently ask about:

• A particular setup process;
• A particular hardware configuration;
• Connectivity;
• Report interpretation;
• Equipment mapping;
• User permissions;
• Sensor installation;
• Facility configuration.

We may use this information to improve:

• Product design;
• Documentation;
• Installation instructions;
• Platform functionality;
• Customer support;
• Hardware configuration;
• Troubleshooting tools.

Where broader analysis of support information is conducted, we may use aggregated or de-identified information where reasonably practicable.

Using Aggregated Information

Where reasonably practicable, Opti-mized may aggregate information before using it for broader research, analysis, benchmarking, product development, model improvement, or business intelligence.

Aggregation generally involves combining information relating to multiple records, devices, facilities, equipment items, users, customers, or time periods so that the resulting information focuses on broader patterns rather than an individual record.

Aggregated information may be used to understand matters such as:

• General equipment operating patterns;
• Typical facility baseload characteristics;
• General hardware reliability;
• Average gateway connectivity;
• Typical sensor performance;
• Common equipment runtime patterns;
• Common energy-loss conditions;
• Typical platform usage;
• Common customer-support issues;
• General product performance;
• General system performance;
• Broader energy-use trends.

For example, Opti-mized may determine that a certain category of equipment tends to exhibit a particular operating pattern across multiple facilities.

Such information may help us improve classification or analytical methods without requiring an individual customer's identity to be part of the resulting insight.

Using De-Identified Information

Where reasonably practicable, we may de-identify information before using it for broader product improvement, benchmarking, research, or development.

De-identification may involve removing, masking, modifying, generalizing, separating, or replacing information that could directly identify a particular individual or customer.

Depending on the circumstances, this may include removing or modifying:

• Names;
• Email addresses;
• Telephone numbers;
• Account identifiers;
• Facility names;
• Exact facility addresses;
• Customer names;
• User identifiers;
• Other direct identifiers.

De-identification may also involve reducing the precision of certain information or combining information with other records.

The appropriate method depends on the information involved, the purpose for which it will be used, the technical environment, and applicable law.

Where information has been de-identified in a manner intended to prevent it from reasonably identifying an individual, we may use that information for legitimate purposes permitted by law.

Using Anonymized Information

In some circumstances, information may be anonymized so that it is not reasonably capable of being associated with an identifiable individual.

Anonymized information may be used for:

• Statistical analysis;
• Product development;
• Research;
• Benchmarking;
• Model improvement;
• Testing;
• Performance analysis;
• Business planning;
• Other lawful purposes.

The availability and legal meaning of anonymization may vary by jurisdiction.

Accordingly, Opti-mized may apply different techniques depending on applicable requirements.

Using Statistical Information

We may generate statistical information from Opti-mized services.

Statistical information may relate to matters such as:

• Number of connected devices;
• Hardware reliability;
• System uptime;
• Data-transmission success rates;
• Common equipment categories;
• General operating patterns;
• Typical runtime;
• Typical demand patterns;
• General facility energy trends;
• Platform usage;
• Feature adoption;
• Report generation;
• Support activity.

Statistical information may be used to improve products, allocate resources, evaluate performance, and inform product-development decisions.

Using Information for Benchmarking

Opti-mized may use appropriate information to develop or improve benchmarks.

Benchmarks may help users understand how a facility, equipment item, or system compares with:

• Its own prior performance;
• Its historical baseline;
• Similar periods;
• Similar operating conditions;
• Comparable equipment;
• Comparable facility characteristics;
• Appropriate aggregated reference information.

For example, a benchmark may indicate whether a piece of equipment is operating longer than its own historical average.

Where benchmarking uses information across multiple customers, we may use aggregated, anonymized, de-identified, or otherwise appropriately protected information where reasonably practicable.

Internal Benchmarking

Some benchmarks may be used internally rather than presented directly to customers.

Internal benchmarks may help us evaluate:

• Analytics performance;
• Detection accuracy;
• Hardware reliability;
• Data quality;
• System performance;
• Model performance;
• Alert frequency;
• Error rates;
• Customer-support patterns.

Improving Detection Thresholds

Many analytical systems depend on thresholds, parameters, rules, or reference ranges.

Opti-mized may evaluate information to determine whether these thresholds should be adjusted.

Examples may include thresholds used to identify:

• After-hours operation;
• High continuous loads;
• Significant changes in runtime;
• Significant changes in cycling;
• Demand events;
• Possible anomalies;
• Changes in device health;
• Data-quality issues.

Thresholds may be customer-specific, facility-specific, equipment-specific, or more general depending on the applicable feature.

Reducing False Positives

One purpose of analytical improvement may be to reduce cases in which the Opti-mized system identifies an issue, condition, or opportunity that does not ultimately appear meaningful.

We may evaluate detected conditions against:

• Customer feedback;
• Historical behaviour;
• Updated equipment information;
• Updated schedules;
• Facility context;
• Technical review;
• Subsequent measurements.

This may help us refine future detection methods.

Reducing Missed Conditions

Similarly, we may evaluate cases where a meaningful pattern, operational condition, or energy-loss opportunity was not initially identified.

Where appropriate, those examples may help us improve detection logic or analytical methods.

Improving Confidence and Reliability

Where supported, Opti-mized may develop methods for evaluating the confidence, reliability, or quality of analytical outputs.

Relevant factors may include:

• Data completeness;
• Measurement quality;
• Length of historical baseline;
• Consistency of observed patterns;
• Availability of contextual information;
• Accuracy of equipment mapping;
• Accuracy of utility-rate information;
• Customer confirmation;
• Historical recurrence.

We may use this information to improve how insights are prioritized or presented.

Evaluating Model and Algorithm Performance

Opti-mized may evaluate the performance of analytical models, algorithms, rules, calculations, or other automated systems.

Evaluation may consider:

• Accuracy;
• Consistency;
• Reliability;
• Relevance;
• Sensitivity;
• Specificity;
• Error rates;
• False positives;
• False negatives;
• Computational performance;
• Scalability;
• Data requirements;
• Customer feedback.

Testing may be performed using customer-specific information where necessary to provide or troubleshoot a customer's service.

For broader product-development purposes, Opti-mized may use aggregated, de-identified, anonymized, synthetic, statistical, or otherwise appropriately protected information where reasonably practicable.

Testing New Analytical Methods

Before deploying new analytical functionality broadly, Opti-mized may test or validate new approaches.

Testing may involve:

• Historical data analysis;
• Simulation;
• Synthetic data;
• De-identified datasets;
• Aggregated datasets;
• Controlled testing environments;
• Limited customer-specific testing where authorized or reasonably necessary;
• Manual review;
• Comparison with existing methods.

The purpose of testing is generally to determine whether new functionality performs reliably before it is relied upon in production environments.

Validation of Analytical Outputs

We may compare analytical outputs against other available information to evaluate whether they are reasonable.

For example, runtime estimates may be compared with:

• Known operating schedules;
• Customer observations;
• Historical patterns;
• Equipment specifications;
• Manual measurements;
• Other facility information.

Savings calculations may be compared with:

• Utility bills;
• Historical energy consumption;
• Measured consumption;
• Post-implementation results where available.

Human Review and Quality Assurance

Certain product-development, troubleshooting, validation, support, or quality-assurance activities may involve review by authorized Opti-mized personnel or authorized service providers.

Human review may be used to:

• Validate analytical results;
• Investigate unusual results;
• Troubleshoot errors;
• Review customer feedback;
• Confirm equipment mappings;
• Interpret complex facility information;
• Review photographs or documents;
• Evaluate new features;
• Assess report quality;
• Investigate model or algorithm performance.

Access to customer-specific information for these purposes should be limited to persons who require access for legitimate business or service purposes and may be subject to confidentiality, access-control, security, and contractual requirements.

Improving Through Measurement and Verification

Where customers implement operational changes, retrofits, equipment replacements, or other measures, Opti-mized may compare pre-implementation and post-implementation information.

Such comparisons may help:

• Verify whether energy consumption changed;
• Verify whether runtime changed;
• Verify whether demand changed;
• Evaluate the performance of an implemented measure;
• Evaluate the accuracy of prior savings estimates;
• Improve future calculation methods;
• Improve analytical assumptions.

Where information from such projects contributes to broader product improvement, we may use aggregated or de-identified information where reasonably practicable.

Improving Energy Models

Opti-mized may use appropriate facility, operational, energy, utility, and environmental information to improve analytical models used to understand or estimate facility performance.

Model-improvement activities may involve:

• Evaluating historical predictions;
• Comparing predicted and measured performance;
• Adjusting assumptions;
• Improving seasonal adjustments;
• Improving weather-related analysis;
• Improving runtime estimates;
• Improving demand estimates;
• Improving savings calculations;
• Improving scenario analysis.

Improving Weather and Environmental Analysis

Where weather or other environmental information is used in Opti-mized services, we may evaluate how environmental conditions relate to equipment and facility operation.

This may help improve methods used to identify:

• Heating behaviour;
• Cooling behaviour;
• Weather-dependent loads;
• Seasonal equipment usage;
• Environmental mismatches;
• Unusual HVAC operation;
• Changes in energy consumption associated with temperature.

Improving Demand Analysis

We may use historical and aggregated demand information to improve how Opti-mized identifies:

• Peak-demand periods;
• Major demand contributors;
• Simultaneous equipment operation;
• Recurring demand patterns;
• Demand-related opportunities;
• Potential demand-reduction scenarios.

Improving Portfolio Intelligence

For customers with multiple facilities, we may use information to improve portfolio-level functionality.

This may include improving:

• Facility comparisons;
• Facility rankings;
• Portfolio summaries;
• Cross-facility benchmarking;
• Opportunity prioritization;
• Portfolio savings calculations;
• Portfolio reporting;
• Multi-facility dashboards.

Improving Data Quality Processes

We may use information to improve systems designed to detect and correct data-quality issues.

This may include improving detection of:

• Missing measurements;
• Duplicate data;
• Incorrect timestamps;
• Inconsistent equipment labels;
• Incorrect circuit mappings;
• Device misconfiguration;
• Measurement gaps;
• Unrealistic values;
• Communication interruptions;
• Incorrect facility associations.

Improving Automated Data Validation

Opti-mized may use historical information and known valid configurations to improve automated checks intended to identify inaccurate or incomplete information.

For example, automated validation may identify:

• Missing panel information;
• Incomplete facility setup;
• Unmapped circuits;
• Missing sensor assignments;
• Invalid measurement ranges;
• Inconsistent device identifiers;
• Missing utility-rate information.

Improving Customer Setup and Onboarding

We may analyze customer setup activity to understand where users encounter difficulty.

This may include evaluating:

• Completion rates;
• Common missing information;
• Frequently misunderstood questions;
• Repeated corrections;
• Support requests;
• Upload errors;
• Abandoned setup steps.

This information may help us simplify and improve onboarding.

Improving Deployment Efficiency

Installation and commissioning information may help us improve deployment processes.

For example, we may use information to improve:

• Hardware packaging;
• Sensor selection;
• CT selection;
• Gateway placement;
• Installation instructions;
• Commissioning procedures;
• Connectivity setup;
• Hardware labeling;
• Facility configuration.

Improving Technical Support

Support records may be used to identify common technical issues and improve diagnostic tools.

This may help us develop:

• Better troubleshooting guidance;
• Automated diagnostics;
• More useful error messages;
• More reliable connectivity;
• Improved self-service support;
• Better training materials;
• Faster issue resolution.

Improving Security

Information may also be used to improve the security of Opti-mized products and services.

This may include analyzing:

• Login activity;
• Unauthorized access attempts;
• System logs;
• Security incidents;
• Device behaviour;
• Network activity;
• Authentication failures;
• Application errors;
• Security vulnerabilities;
• Suspicious requests.

Security information may help us improve:

• Authentication;
• Access controls;
• Security monitoring;
• Incident detection;
• Device security;
• Firmware security;
• Cloud security;
• Account protection;
• Abuse prevention.

Improving Reliability and Availability

We may analyze information relating to system reliability to improve the availability of Opti-mized services.

This may include:

• Server performance;
• Application response time;
• API performance;
• Database performance;
• Gateway connectivity;
• Device uptime;
• Data-transmission reliability;
• Report-generation reliability;
• Notification-delivery reliability;
• Error rates;
• Service interruptions.

Improving Scalability

As the number of customers, facilities, users, devices, circuits, and measurements grows, we may use aggregated system-performance information to improve the ability of Opti-mized systems to operate efficiently at larger scale.

This may involve improving:

• Data storage;
• Data processing;
• Database performance;
• Cloud infrastructure;
• Device communication;
• Data aggregation;
• Reporting;
• Analytics processing;
• Dashboard performance.

Capacity Planning

We may use aggregated technical and usage information to plan future infrastructure requirements.

This may include planning for:

• Data storage;
• Data-processing capacity;
• Network capacity;
• Device connectivity;
• Server capacity;
• Database capacity;
• Backup capacity;
• Customer-support capacity.

Developing New Products and Services

Information may be used to identify opportunities for new Opti-mized products, services, features, and capabilities.

For example, customer feedback and aggregated usage information may indicate demand for:

• New reports;
• New dashboards;
• New equipment analytics;
• New alerts;
• New hardware configurations;
• New sensor options;
• New integrations;
• New benchmarking;
• New portfolio features;
• New reporting formats;
• New facility setup workflows.

Research and Development

Opti-mized may conduct internal research and development related to its products, services, technology, hardware, analytics, and facility-intelligence capabilities.

Research may focus on areas such as:

• Electrical analytics;
• Equipment behaviour;
• Energy management;
• Facility performance;
• Sensor technology;
• Gateway technology;
• Data processing;
• Detection methods;
• Classification methods;
• Anomaly detection;
• Predictive indicators;
• Energy-loss detection;
• Retrofit analysis;
• Savings calculation;
• Demand management;
• Benchmarking;
• Reporting;
• User experience.

Where reasonably practicable for broader research, we may use aggregated, anonymized, de-identified, synthetic, or otherwise appropriately protected information.

Synthetic Data

In some circumstances, Opti-mized may generate synthetic information designed to resemble relevant patterns without representing the actual data of a particular customer or individual.

Synthetic data may be used for:

• Software testing;
• Analytics testing;
• Model development;
• Demonstrations;
• Quality assurance;
• Development environments;
• Security testing.

Use of synthetic information may reduce the need to use identifiable customer information for certain development activities.

Test and Development Environments

Where customer-derived information must be used for troubleshooting, testing, or development, Opti-mized may take reasonable measures appropriate to the circumstances to limit access and protect the information.

Where reasonably practicable, development and testing may instead use:

• Synthetic data;
• De-identified data;
• Anonymized data;
• Aggregated data;
• Limited datasets;
• Sample data.

Improving Through Aggregated Cross-Customer Insights

Opti-mized may gain valuable technical and analytical insights by evaluating patterns across multiple customers or facilities.

Where we perform broader cross-customer analysis, we seek to use aggregated, anonymized, de-identified, or otherwise appropriately protected information where reasonably practicable.

Examples of broader insights may include:

• Typical equipment runtime ranges;
• Common after-hours operating patterns;
• General equipment load characteristics;
• Hardware reliability trends;
• Gateway connectivity trends;
• Common facility setup configurations;
• Common analytical errors;
• General facility energy patterns;
• Common detection categories;
• Typical data-quality issues.

The purpose of such analysis is generally to improve the Opti-mized product rather than to expose one customer's information to another customer.

Protection of Customer Identity in Benchmarking

Where benchmarking is based on information from multiple customers, Opti-mized may take steps to reduce the likelihood that a benchmark identifies a particular customer.

Depending on the use case, such measures may include:

• Aggregating multiple records;
• Removing customer names;
• Removing facility names;
• Removing direct identifiers;
• Generalizing facility characteristics;
• Presenting ranges rather than individual values;
• Applying minimum-group-size requirements where appropriate;
• Limiting the precision of certain information;
• Using statistical summaries.

The specific techniques used may depend on the type of information and the purpose of the benchmark.

Customer-Specific Data and Broader Product Improvement

There is an important distinction between using information to provide and improve services for a particular customer and using information for broader Opti-mized product development.

Opti-mized may use identifiable or customer-specific information where reasonably necessary to provide, maintain, troubleshoot, configure, secure, or improve services for that customer.

For example, customer-specific information may be needed to:

• Investigate why a customer's sensor is reporting an unexpected reading;
• Correct a customer's circuit mapping;
• Improve a customer's equipment classification;
• Adjust a customer's operating baseline;
• Correct a savings calculation;
• Diagnose a gateway issue;
• Resolve a report error;
• Improve a recommendation for that facility.

For broader research, benchmarking, product development, or generalized model improvement, we seek to use aggregated, anonymized, de-identified, statistical, synthetic, or otherwise appropriately protected information where reasonably practicable.

Limited Use of Identifiable Customer Information

There may be circumstances where identifiable customer information is reasonably necessary to diagnose, test, validate, or improve a product feature.

For example, a particular customer may report that a specific analytical output appears incorrect.

Investigating the issue may require authorized Opti-mized personnel to review:

• The customer's facility configuration;
• Relevant Energy and Operational Data;
• Equipment mappings;
• Operating schedules;
• Historical information;
• Analytical outputs;
• Technical logs.

In such circumstances, customer-specific information may be used as reasonably necessary to investigate and correct the issue.

The use of such information should remain connected to legitimate operational, support, security, quality, or improvement purposes.

Access Controls for Product Improvement

Access to identifiable or customer-specific information used for product-improvement activities may be limited based on job responsibilities and business need.

Depending on our systems and internal processes, protections may include:

• User authentication;
• Role-based access;
• Restricted permissions;
• Logging;
• Confidentiality obligations;
• Security controls;
• Segregation of systems;
• Technical safeguards;
• Administrative safeguards.

Service Providers Supporting Product Improvement

Opti-mized may use service providers to assist with software development, cloud infrastructure, analytics, security, technical support, data processing, testing, or other activities related to improving our products and services.

Where a service provider processes customer information on our behalf, its access should be limited to information reasonably necessary to provide the applicable service and governed by appropriate contractual, confidentiality, security, or data-processing obligations where required.

Service providers that process information on Opti-mized's behalf are different from unrelated third parties using customer information for their own independent purposes.

Artificial Intelligence, Machine Learning, and Automated Analytical Technologies

Opti-mized may use algorithms, statistical techniques, machine learning, artificial intelligence, automated analysis, rules-based systems, or other computational methods to operate or improve certain products and services.

These technologies may be used for purposes such as:

• Identifying electrical patterns;
• Detecting changes in equipment behaviour;
• Identifying potential anomalies;
• Classifying equipment;
• Classifying circuits;
• Identifying operating periods;
• Estimating runtime;
• Identifying energy-loss opportunities;
• Supporting savings calculations;
• Extracting information from photographs;
• Extracting information from documents;
• Organizing facility information;
• Generating analytical summaries;
• Prioritizing opportunities;
• Improving reports;
• Improving customer workflows.

The particular technologies used by Opti-mized may evolve over time.

Use of Customer Data in Opti-mized Analytical Systems

Customer-specific Facility Data, Energy and Operational Data, and related information may be processed by Opti-mized analytical systems where necessary to provide services to that customer.

For example, the system may analyze a customer's own electrical measurements in order to:

• Establish that customer's equipment baseline;
• Identify that customer's equipment runtime;
• Detect changes within that customer's facility;
• Calculate that customer's potential savings;
• Generate that customer's Facility Intelligence Report;
• Provide that customer's alerts or recommendations.

This customer-specific processing is a core part of providing the Opti-mized service and is distinct from training an unrelated general-purpose artificial intelligence model.

Generalized Model Improvement

Where Opti-mized develops or improves generalized analytical methods that may be used across multiple customers, we may use aggregated, anonymized, de-identified, synthetic, or otherwise appropriately protected information where reasonably practicable.

For example, generalized improvement may involve understanding whether a particular analytical method reliably detects equipment operation across a broad range of facility types.

In such cases, the relevant value may come from the pattern or statistical relationship rather than the identity of the customer that generated the underlying information.

Third-Party General-Purpose Artificial Intelligence Models

Opti-mized does not provide identifiable customer Facility Data or identifiable customer Energy and Operational Data to unrelated third parties for the purpose of training those third parties' general-purpose artificial intelligence models unless:

• The customer has specifically authorized such use;
• Such use has otherwise been clearly disclosed to the customer and is permitted by applicable law; or
• Another lawful basis or circumstance expressly applicable to the relationship permits such processing.

For purposes of this provision, a general-purpose artificial intelligence model generally refers to a model designed for broad use across many unrelated applications or customers rather than a system used specifically to provide, host, process, secure, support, or improve Opti-mized services.

No Automatic Right for Unrelated Third Parties to Use Customer Data for Their Own AI Training

The fact that Opti-mized may use a third-party cloud provider, software provider, analytics provider, development tool, artificial intelligence service, or other technology provider does not, by itself, mean that such provider is authorized to use identifiable Opti-mized customer Facility Data or Energy and Operational Data to train its own general-purpose models for unrelated purposes.

Where third-party technology providers process information on behalf of Opti-mized, we seek to structure such processing in accordance with the applicable service arrangement, contractual requirements, available privacy controls, and applicable law.

The specific terms applicable to a particular provider may vary depending on the technology and service involved.

Customer Authorization for Additional Uses

A customer may choose to authorize additional uses of its information.

For example, a customer may choose to participate in:

• Product pilots;
• Beta programs;
• Research programs;
• Case studies;
• Benchmarking initiatives;
• Joint development;
• Testing programs;
• Customer advisory programs;
• Additional analytical services.

Where participation involves uses materially beyond the ordinary operation of Opti-mized services, additional terms, disclosures, permissions, or consent may be provided where appropriate.

Product Pilots and Beta Features

Opti-mized may offer customers access to experimental, pilot, preview, beta, or early-access functionality.

Where customers participate, information generated through those features may be used to:

• Evaluate performance;
• Identify errors;
• Improve functionality;
• Measure usefulness;
• Understand user experience;
• Validate analytical results;
• Determine whether to release the feature more broadly.

Additional disclosures may be provided where appropriate for a particular beta or pilot program.

Case Studies and Public Use

Using information internally to improve Opti-mized is different from publicly identifying a customer or publishing a customer case study.

Opti-mized will not treat the internal availability of customer information as automatic authorization to publicly identify a customer, publish identifiable facility information, or disclose customer-specific results for promotional purposes.

Where customer-identifying information or customer-specific results are to be used publicly in a testimonial, case study, marketing publication, or similar material, appropriate authorization may be obtained where required.

Aggregated Success Metrics

Opti-mized may use aggregated or de-identified information to describe general product performance, usage, or impact.

Examples could include aggregated statistics relating to:

• Number of facilities using the platform;
• Number of connected circuits;
• Types of equipment analyzed;
• General categories of opportunities identified;
• Aggregate estimated savings;
• General equipment patterns;
• Product reliability;
• Platform usage.

Where such statistics are publicly communicated, we may take reasonable steps appropriate to the circumstances to avoid unnecessarily identifying individual customers.

Internal Research Versus Public Disclosure

Information used internally for product improvement, testing, research, benchmarking, or quality assurance is not necessarily intended for public disclosure.

Opti-mized may maintain internal datasets, analytical results, benchmarks, performance statistics, or research findings without publicly identifying the customers or facilities that contributed to those findings.

Protecting Confidential Facility Information

Some facility information may be commercially, operationally, or technically sensitive even where it does not qualify as personal information under privacy law.

For example, information about:

• Electrical infrastructure;
• Equipment;
• Facility schedules;
• Energy consumption;
• Utility costs;
• Equipment performance;
• Building systems;
• Electrical distribution;
• Operational patterns;
• Facility layouts.

may be sensitive to a customer even though it does not identify a natural person.

Opti-mized may therefore apply contractual, technical, organizational, or security protections to customer Facility Data independently of whether the data constitutes personal information.

De-Identification Does Not Necessarily Mean Deletion of All Technical Characteristics

In order for de-identified or aggregated information to remain useful for product development, it may be necessary to retain certain technical characteristics.

For example, a de-identified dataset may retain information about:

• Equipment category;
• Facility category;
• Approximate load;
• Runtime;
• Cycling;
• Time period;
• General environmental conditions;
• General building characteristics.

The objective may be to remove or reduce identifying information while preserving the technical relationships necessary for legitimate analysis.

Re-Identification

Where Opti-mized treats information as de-identified for broader research or product-improvement purposes, we do not intend to use de-identification as a method for publicly exposing customer-specific information.

Where required by applicable law, we may maintain measures designed to prevent or limit inappropriate re-identification.

Data Minimization for Improvement Activities

Where reasonably practicable, Opti-mized may limit the amount of identifiable information used for broader product-improvement activities to what is reasonably necessary for the applicable purpose.

For example, a technical analysis of gateway communication reliability may not require customer names, user contact information, or billing information.

Similarly, evaluating a general equipment-load pattern may not require information identifying the facility's individual users.

The categories of information used should therefore depend on what is reasonably relevant to the improvement being performed.

Separation of Unrelated Information

Information collected for one purpose is not necessarily relevant to every product-improvement activity.

For example:

• Payment-card information is not needed to improve equipment detection;
• User telephone numbers are not needed to analyze sensor reliability;
• Shipping addresses are not generally needed to improve runtime calculations;
• Marketing preferences are not needed to improve electrical analytics.

We seek to use information in a manner reasonably related to the applicable purpose.

Data Retention and Product Improvement

The amount of historical information available may affect the performance of certain analytical features.

For example, longer historical periods may allow Opti-mized to:

• Establish more representative baselines;
• Compare seasonal performance;
• Identify gradual behavioural changes;
• Evaluate equipment trends;
• Compare year-over-year performance;
• Improve savings analysis;
• Support measurement and verification.

Information used for product-improvement purposes remains subject to applicable retention practices, contractual obligations, and legal requirements described elsewhere in this Privacy Policy.

Product Improvement Following Account Closure

The termination or closure of a customer account does not necessarily require deletion of information that has already been validly aggregated, anonymized, or de-identified so that it is no longer reasonably associated with an identifiable individual, where retention and continued use are permitted by applicable law and applicable agreements.

Customer-specific information that remains identifiable will be handled in accordance with applicable retention, contractual, and legal requirements.

Product Improvement and Backups

Information may exist temporarily in system backups, disaster-recovery systems, logs, or archived records while ordinary retention and deletion processes are completed.

Such information may continue to be subject to security controls and applicable retention practices.

Accuracy and Limitations of Product Improvement

Although Opti-mized may use information to continuously improve analytical systems, no analytical method is perfect.

Equipment behaviour can vary because of:

• Facility operations;
• Weather;
• Occupancy;
• Maintenance;
• Equipment replacement;
• Equipment controls;
• Changes in schedules;
• Changes in utility rates;
• Changes in production;
• Changes in building use;
• Data quality;
• Sensor placement;
• Customer configuration;
• Other factors.

Accordingly, improvements to analytics do not guarantee that every detection, classification, estimate, recommendation, or prediction will be correct in every circumstance.

Estimates and Predictions

Information generated through improved models or analytical systems may include estimates or predictions rather than direct measurements.

Examples may include:

• Estimated annual savings;
• Estimated future energy use;
• Estimated runtime;
• Estimated payback;
• Estimated retrofit performance;
• Predicted maintenance indicators;
• Expected equipment behaviour.

Such information should be interpreted in light of the available data, assumptions, and facility-specific conditions.

Continuous Improvement

Opti-mized may periodically revise or replace analytical methods as better information, technologies, techniques, or customer feedback become available.

As a result:

• A calculation may change;
• A baseline may be recalculated;
• An equipment classification may be updated;
• An alert threshold may change;
• A recommendation may evolve;
• A detection method may become more accurate;
• A report format may change;
• Historical information may be reprocessed using improved methods.

Such changes may occur as part of ordinary product development.

Reprocessing Historical Data

Where appropriate, Opti-mized may reprocess previously collected information using updated analytical methods.

For example, if a new method improves equipment classification or energy-loss detection, historical data may be analyzed again in order to provide improved results.

Reprocessing may help:

• Improve historical comparisons;
• Update baselines;
• Identify previously undetected opportunities;
• Improve equipment classifications;
• Improve reports;
• Improve customer-specific intelligence.

Versioning of Analytics

Different versions of Opti-mized analytics, calculations, models, firmware, or software may produce somewhat different outputs.

Opti-mized may maintain information regarding:

• Model versions;
• Algorithm versions;
• Firmware versions;
• Calculation versions;
• Report versions;
• Configuration versions.

This information can assist with troubleshooting, quality assurance, reproducibility, and improvement.

Monitoring the Impact of Changes

After making changes to software, hardware, algorithms, models, or analytics, we may evaluate performance to determine whether the change had the intended effect.

This may involve comparing:

• Error rates;
• Detection rates;
• System performance;
• Data quality;
• Customer feedback;
• Support volume;
• Hardware performance;
• Analytical accuracy.

Rollback and Correction

Where a software, firmware, analytical, or product change causes unexpected results, information may be used to investigate the issue and determine whether a correction, rollback, or further update is appropriate.

Internal Documentation

Information learned through product improvement may be incorporated into internal documentation, technical guidance, development standards, troubleshooting documentation, quality-assurance procedures, and product requirements.

Internal documentation may describe general patterns without necessarily retaining customer-identifying information.

Employee and Contractor Training

Authorized personnel may receive training based on generalized, aggregated, synthetic, de-identified, or appropriately limited examples derived from product experience.

Training may cover:

• Facility setup;
• Hardware installation;
• Troubleshooting;
• Customer support;
• Equipment classification;
• Analytical review;
• Data quality;
• Security;
• Product functionality.

Where identifiable customer information is unnecessary, it should not be included merely for training convenience.

Evaluating Third-Party Technologies

Opti-mized may evaluate third-party technologies that could improve our services.

Evaluation may consider technologies for:

• Cloud infrastructure;
• Analytics;
• Artificial intelligence;
• Machine learning;
• Document processing;
• Image processing;
• Security;
• Communications;
• Data storage;
• Monitoring;
• Customer support;
• Software development.

Where customer information is involved in evaluating or using such technologies, we may consider factors such as:

• The information required;
• The provider's role;
• Contractual protections;
• Security;
• Data retention;
• Available privacy controls;
• Whether the provider uses information for its own purposes;
• Applicable law;
• Customer commitments.

Avoiding Unnecessary Third-Party AI Training

Where Opti-mized uses third-party artificial intelligence or machine-learning technologies to support its services, we may seek available configurations, contractual terms, enterprise controls, or service arrangements that limit the provider's independent use of identifiable customer information for unrelated general-purpose model training.

The availability and nature of such controls may vary among providers and over time.

Opti-mized may evaluate those considerations as part of selecting and managing service providers.

No Sale of Customer Intelligence Merely Because It Has Analytical Value

The fact that customer Facility Data, Energy and Operational Data, or Facility Intelligence Data may be valuable for improving Opti-mized's technology does not, by itself, make such information publicly available or eliminate applicable confidentiality, security, contractual, or privacy protections.

Any disclosure to third parties remains subject to the provisions of this Privacy Policy, applicable agreements, and applicable law.

Improvement of Services Does Not Change Customer Ownership or Contractual Rights

The use of information to operate, maintain, develop, or improve Opti-mized does not by itself alter any ownership, licensing, confidentiality, or other rights established under applicable customer agreements.

Where customer agreements contain specific provisions regarding customer data, derived information, confidentiality, intellectual property, or product improvement, those provisions may apply in addition to this Privacy Policy.

Requests and Contractual Restrictions

Certain customers may have contractual requirements concerning how their data may be used.

Where applicable, Opti-mized may implement customer-specific restrictions required by an applicable agreement.

Such restrictions may affect whether and how information can be used for:

• Benchmarking;
• Research;
• Product development;
• Model improvement;
• Case studies;
• Public reporting;
• Cross-customer analytics.

Legal Requirements

Our ability to use information for product improvement may also depend on applicable privacy, data-protection, confidentiality, cybersecurity, contract, and other laws.

Where consent or another specific legal basis is required, we may take appropriate measures to satisfy that requirement.

Changes to Improvement Practices

Opti-mized's technology, analytical methods, and use of artificial intelligence may evolve over time.

New technologies may create new ways to:

• Analyze facility information;
• Process documents;
• Analyze photographs;
• Classify equipment;
• Detect energy loss;
• Generate recommendations;
• Develop benchmarks;
• Improve user experience.

If our practices materially change in a way that affects how personal information is used, we may update this Privacy Policy, provide additional notice, obtain consent where required, or take other measures required by applicable law.

Summary of Our Approach to Product Improvement

At a high level, Opti-mized may use information generated through our products and services to:

• Improve our technology;
• Improve our hardware;
• Improve our sensors;
• Improve our gateways;
• Improve firmware;
• Improve connectivity;
• Improve data quality;
• Improve facility setup;
• Improve equipment mapping;
• Improve circuit mapping;
• Improve equipment classification;
• Improve document processing;
• Improve photograph processing;
• Improve utility-bill analysis;
• Improve runtime detection;
• Improve cycling analysis;
• Improve baseline development;
• Improve anomaly detection;
• Improve energy-loss detection;
• Improve demand analysis;
• Improve savings calculations;
• Improve ROI and payback calculations;
• Improve retrofit simulations;
• Improve maintenance indicators;
• Improve reports;
• Improve alerts;
• Improve recommendations;
• Improve opportunity prioritization;
• Improve customer-specific Facility Intelligence;
• Improve portfolio-level intelligence;
• Improve benchmarking;
• Improve security;
• Improve reliability;
• Improve scalability;
• Improve customer support;
• Improve user experience;
• Develop new products, analytics, models, features, hardware, and services;
• Conduct testing, research, quality assurance, and product development;
• Create aggregated, statistical, anonymized, or de-identified insights where appropriate; and
• Continually improve the usefulness and performance of Opti-mized.

Where reasonably practicable, broader research, benchmarking, product development, generalized analytical improvement, and model-development activities may use aggregated, anonymized, de-identified, synthetic, statistical, or otherwise appropriately protected information rather than information that directly identifies a customer or individual.

Customer-specific information may continue to be used where reasonably necessary to provide, maintain, troubleshoot, secure, configure, analyze, personalize, or improve Opti-mized services for that customer.

Opti-mized does not provide identifiable customer Facility Data or identifiable customer Energy and Operational Data to unrelated third parties for the purpose of training those third parties' general-purpose artificial intelligence models unless specifically authorized by the customer, otherwise clearly disclosed, or otherwise permitted in accordance with applicable law and the applicable customer relationship.

Our objective is to improve Opti-mized using the information necessary to make our products more accurate, useful, reliable, secure, and effective while maintaining appropriate protections for customer, facility, operational, and personal information.

Opti-mized may create, derive, generate, compile, combine, transform, summarize, anonymize, de-identify, pseudonymize, generalize, statistically process, or otherwise modify information collected through our products and services so that the resulting information is less directly associated with, or is no longer reasonably capable of identifying, a particular individual, customer representative, user, account, facility, or other identifiable record, depending on the purpose and the technical method used.

Aggregated and de-identified information can allow Opti-mized to understand broader patterns, improve products and services, evaluate technology performance, develop analytical methods, create benchmarks, conduct research, plan infrastructure, understand customer needs, and develop new functionality without unnecessarily relying on information that directly identifies a particular individual or customer.

The form of information used for these purposes may vary.

In some circumstances, information may be aggregated, meaning that multiple records, measurements, facilities, equipment items, devices, users, customers, time periods, or other data points are combined and analyzed together.

In other circumstances, information may be de-identified, meaning that information reasonably capable of directly identifying a person, customer, facility, account, or other identifiable record is removed, modified, obscured, generalized, separated, replaced, or otherwise processed in a manner intended to reduce the ability to associate the information with an identifiable subject.

In some circumstances, information may be anonymized, meaning that the information is processed in a manner intended to prevent it from being reasonably associated with an identifiable individual, subject to the legal and technical standards applicable in the relevant jurisdiction.

We may also use statistical, synthetic, pseudonymized, masked, tokenized, generalized, or otherwise protected forms of information where appropriate.

The exact method used may depend on the nature of the information, the purpose of the analysis, the technical environment, the risks associated with the information, the size of the dataset, applicable contractual requirements, and applicable law.

Why We Create Aggregated and De-Identified Information

Opti-mized may create aggregated, anonymized, or de-identified information in order to obtain useful analytical and technical insights while reducing unnecessary use of directly identifiable information.

For example, understanding whether a particular gateway model experiences a certain type of connectivity issue does not ordinarily require us to know the name of the customer that owns the gateway.

Similarly, understanding general runtime patterns for a category of rooftop units may not require the exact identity or street address of the facility in which those units are located.

Aggregated and de-identified information may therefore allow Opti-mized to improve technology and understand broader patterns while limiting the amount of customer-identifying or person-identifying information used for those purposes.

Information That May Be Aggregated or De-Identified

Depending on the circumstances, we may create aggregated or de-identified information from categories of information such as:

• Energy and Operational Data;
• Facility Intelligence Data;
• Facility information;
• Equipment information;
• Electrical panel information;
• MCC information;
• Switchgear information;
• Circuit information;
• Equipment classifications;
• Equipment runtime;
• Equipment cycling;
• Demand information;
• Baseload information;
• Off-hours usage information;
• On-hours usage information;
• Environmental correlation information;
• Historical electrical consumption;
• Utility information;
• Savings estimates;
• Financial estimates;
• Payback calculations;
• Retrofit-related information;
• Hardware information;
• Gateway information;
• Sensor information;
• CT information;
• Device health information;
• Device connectivity information;
• Diagnostic information;
• Firmware information;
• System logs;
• Product usage information;
• Platform usage information;
• Support information;
• Report usage;
• Website usage;
• Analytics information;
• Customer feedback;
• Configuration information;
• Installation information;
• Technical information;
• Other information generated through the use of Opti-mized products and services.

The inclusion of a category in this section does not mean that all information within that category is necessarily aggregated or de-identified, nor does it mean that every category is used for every purpose.

Aggregation Across Measurements

Opti-mized systems may collect large numbers of electrical measurements over time.

Individual measurements may be combined to create broader summaries.

For example, measurements may be aggregated into:

• Minute-level summaries;
• Hourly summaries;
• Daily summaries;
• Weekly summaries;
• Monthly summaries;
• Annual summaries;
• Equipment-level summaries;
• Circuit-level summaries;
• Panel-level summaries;
• Building-level summaries;
• Facility-level summaries;
• Portfolio-level summaries.

Aggregation can make information easier to analyze, display, store, compare, and interpret.

It may also reduce reliance on extremely granular information where that level of detail is not necessary for the applicable purpose.

Aggregation Across Equipment

We may combine information from multiple pieces of equipment in order to understand broader equipment patterns.

For example, aggregated information may be used to evaluate:

• Typical runtime for a category of equipment;
• Typical cycling behaviour;
• Typical load characteristics;
• Typical demand contribution;
• Common operating schedules;
• Common energy-loss opportunities;
• Typical changes in equipment behaviour;
• Common maintenance indicators;
• Typical equipment performance ranges;
• General equipment usage trends.

Equipment-level aggregation may occur within a single facility, across multiple facilities of the same customer, or across multiple appropriately protected datasets where permitted.

Aggregation Across Facilities

Information may be aggregated across multiple facilities in order to understand broader facility-level trends.

Examples may include:

• Average facility energy consumption;
• Typical baseload characteristics;
• Average off-hours energy use;
• Common demand peaks;
• Facility-level operating patterns;
• Common equipment categories;
• Typical facility runtime patterns;
• Common energy-loss opportunities;
• Portfolio performance;
• General facility energy trends.

Where cross-customer information is used, we may apply de-identification, aggregation, minimum group sizes, or other protections where reasonably practicable.

Aggregation Across Time Periods

We may aggregate information across different time periods to understand trends.

For example, we may compare:

• Daily averages;
• Weekly averages;
• Monthly averages;
• Seasonal averages;
• Annual averages;
• Historical periods;
• Pre-implementation and post-implementation periods;
• Weekdays and weekends;
• Operating hours and non-operating hours.

Time-based aggregation may support trend analysis, baseline development, benchmarking, reporting, and product improvement.

Aggregation Across Customers

Where permitted and appropriate, Opti-mized may aggregate information from multiple customers for broader analytical, benchmarking, technical, or research purposes.

Cross-customer aggregation may allow us to understand matters such as:

• Common equipment behaviours;
• Common facility operating patterns;
• Typical hardware performance;
• General connectivity performance;
• Typical runtime ranges;
• Typical demand patterns;
• Common energy-loss categories;
• General savings patterns;
• Common facility configuration approaches;
• Product usage trends;
• Support trends;
• System reliability trends.

Where information is aggregated across multiple customers, our objective is generally to analyze broader patterns rather than expose the identifiable data of a particular customer.

De-Identification of Customer Information

Where reasonably practicable, Opti-mized may remove or modify customer-identifying information before using information for broader research, benchmarking, analytics, or product development.

Depending on the circumstances, de-identification may involve removing, modifying, obscuring, masking, or replacing information such as:

• Customer name;
• Organization name;
• Municipality name;
• Facility name;
• Exact street address;
• Customer account number;
• User name;
• User email address;
• Telephone number;
• Account identifier;
• Facility identifier;
• Project identifier;
• Device identifier;
• Other direct identifiers.

In some circumstances, certain technical identifiers may be replaced with randomized, internal, tokenized, or pseudonymous identifiers to permit analysis without using the original identifier.

Generalization of Information

De-identification may also involve reducing the precision or specificity of information.

For example:

• An exact facility address may be replaced with a broader geographic region;
• An exact equipment installation date may be converted to a general year or age range;
• Exact facility square footage may be converted to a size range;
• Exact energy consumption values may be converted to bands or categories;
• Exact timestamps may be converted to broader time intervals;
• A specific facility may be categorized only by general facility type;
• A precise equipment model may be grouped into a broader equipment category.

Generalization may help preserve useful analytical relationships while reducing identifying detail.

Masking and Tokenization

Where appropriate, we may replace certain identifiers with internal codes, tokens, hashes, or other representations.

This may allow systems to associate related records without displaying or directly using the original identifier.

For example, a customer or facility identifier may be replaced with an internal analytical identifier when conducting certain analyses.

The specific techniques used depend on the technical system and purpose involved.

Pseudonymized Information

Certain information may be pseudonymized rather than fully anonymized.

Pseudonymized information may retain the ability to be associated with the original record through separate information, keys, or internal systems.

Where pseudonymized information remains capable of being linked back to an identifiable individual or customer, it may continue to be treated as personal information or confidential customer information where required.

Pseudonymization is therefore not necessarily equivalent to anonymization.

Anonymized Information

In some circumstances, we may process information in a manner intended to make it no longer reasonably associated with an identifiable individual.

Where information has been effectively anonymized in accordance with applicable legal standards, it may no longer constitute personal information under certain privacy laws.

The legal standard for anonymization may vary by jurisdiction.

Opti-mized may therefore apply different methods depending on applicable requirements.

De-Identified Facility Data

Facility information may also be de-identified even where the information is not personal information.

For example, facility information may be de-identified by removing:

• Facility name;
• Street address;
• Customer name;
• Project name;
• Unique account identifiers;
• Unique facility identifiers;
• Other information that could reasonably reveal the facility's identity.

The resulting information may still contain useful characteristics such as:

• Facility type;
• Approximate size;
• Equipment categories;
• General geographic region;
• General operating schedule;
• Energy-use characteristics;
• Runtime characteristics;
• Demand characteristics;
• Equipment behaviour.

Such information may be useful for benchmarking and product development without identifying the specific facility involved.

De-Identified Energy and Operational Data

Energy and Operational Data may be processed so that it is no longer directly associated with a particular identified customer or facility.

For example, de-identified electrical data may retain:

• Load shape;
• Runtime;
• Cycling;
• Energy consumption;
• Demand characteristics;
• Equipment category;
• Time-of-day pattern;
• General seasonal context.

while removing or replacing:

• Customer identity;
• Facility identity;
• Account information;
• User information;
• Exact facility address;
• Other direct identifiers.

This can allow Opti-mized to study electrical and operational patterns while reducing the amount of identifiable customer context attached to the information.

De-Identified Facility Intelligence Data

Facility Intelligence Data may also be aggregated or de-identified.

This may include information relating to:

• Detected operating patterns;
• Energy-loss opportunities;
• Savings estimates;
• Runtime analysis;
• Cycling analysis;
• Demand analysis;
• Anomaly indicators;
• Equipment classifications;
• Maintenance indicators;
• Retrofit opportunities;
• Benchmarking results.

For example, Opti-mized may evaluate how frequently a certain type of equipment generates an off-hours usage finding across a broad group of facilities without identifying the facilities involved.

Facility Energy Performance Trends

Aggregated or de-identified information may be used to analyze general facility energy performance.

This may include trends relating to:

• Total energy consumption;
• Energy consumption by facility type;
• Energy consumption by equipment category;
• Seasonal energy performance;
• Energy use during operating hours;
• Energy use outside operating hours;
• Baseload;
• Demand;
• Changes in energy performance;
• General savings opportunities.

Such analysis may help Opti-mized improve analytics and provide better context for customer-specific results.

Equipment Operating Behaviour

We may use aggregated or de-identified information to understand equipment operating behaviour.

This may include analyzing:

• Typical runtime;
• Typical cycling;
• Start and stop patterns;
• Load characteristics;
• Operating frequency;
• Continuous load;
• Idle load;
• Standby behaviour;
• Seasonal behaviour;
• Changes in electrical behaviour;
• General equipment performance.

For example, we may analyze the typical runtime range for a category of pumps across multiple de-identified facilities.

Energy-Saving Opportunities

Aggregated or de-identified information may be used to understand the types of energy-saving opportunities that occur across different facilities or equipment categories.

This may include trends relating to:

• Off-hours usage;
• On-hours overusage;
• Environmental mismatch;
• Peak-demand contribution;
• Idle or standby loads;
• High continuous loads;
• Retrofit opportunities;
• Operational schedule changes;
• Other energy-loss categories.

This may help Opti-mized improve detection methods, ranking, savings calculations, and recommendations.

Hardware Performance

We may aggregate information relating to Opti-mized hardware to evaluate:

• Sensor reliability;
• Gateway reliability;
• CT performance;
• CT Hub performance;
• Device uptime;
• Device restart frequency;
• Connectivity;
• Signal quality;
• Firmware performance;
• Data transmission;
• Error rates;
• Hardware lifespan;
• Device replacement trends;
• Common installation issues;
• Environmental operating conditions.

For example, we may analyze aggregated gateway connectivity statistics to determine whether a firmware update improves reliability.

Product Usage

We may aggregate information about how customers or users interact with Opti-mized products and services.

This may include:

• Features accessed;
• Dashboards viewed;
• Reports generated;
• Reports downloaded;
• Facilities configured;
• Equipment added;
• Alerts used;
• Notifications configured;
• Configuration workflows completed;
• Website usage;
• Platform activity;
• Support interactions;
• Feature adoption.

Product usage analysis may help us understand which features are useful and where improvements may be needed.

System Reliability

Aggregated technical information may be used to evaluate system reliability.

This may include:

• Server uptime;
• Application availability;
• API performance;
• Database performance;
• Gateway connectivity;
• Data-transmission success;
• Data-processing success;
• Error rates;
• Notification delivery;
• Report-generation performance;
• Software crashes;
• Service interruptions.

This information may be used for engineering, capacity planning, reliability improvement, quality assurance, and incident prevention.

Operational Patterns

We may analyze aggregated operational patterns such as:

• Typical facility opening hours;
• Typical equipment operating schedules;
• Weekend operation;
• Seasonal operation;
• Overnight loads;
• Equipment runtime distributions;
• Demand patterns;
• Baseload patterns;
• Common schedule mismatches;
• Changes in operations over time.

These insights may help Opti-mized improve models and analytical methods.

Facility-Type Benchmarks

Aggregated or de-identified information may be used to develop benchmarks based on facility characteristics.

Facility categories may include, for example:

• Office buildings;
• Municipal buildings;
• Arenas;
• Recreation facilities;
• Swimming pools;
• Warehouses;
• Grocery stores;
• Retail facilities;
• Industrial facilities;
• Public works facilities;
• Water or wastewater facilities;
• Community buildings;
• Other commercial or institutional facilities.

Benchmarks may consider factors such as:

• Facility size;
• Operating hours;
• Equipment mix;
• Energy use;
• Demand;
• Baseload;
• Runtime;
• Savings opportunities.

Equipment Benchmarks

We may develop benchmarks for equipment categories using aggregated or de-identified information.

For example, benchmarks may relate to:

• Typical runtime;
• Typical energy consumption;
• Typical cycling;
• Typical load;
• Typical demand contribution;
• Typical operating schedule;
• Typical savings opportunities;
• Typical baseline behaviour.

These benchmarks may provide context for customer-specific equipment analysis.

Historical Benchmarks

Some benchmarks may be based on a customer's own historical information rather than cross-customer data.

For example, current equipment behaviour may be compared with:

• Its own historical average;
• Its own prior year;
• Its own seasonal baseline;
• Similar weekdays;
• Similar environmental conditions.

In these circumstances, the benchmark may remain customer-specific rather than de-identified.

Cross-Customer Benchmarks

Where Opti-mized develops benchmarks based on information from multiple customers, we may take steps designed to reduce the likelihood that individual customers or facilities can be identified.

Depending on the circumstances, these steps may include:

• Combining information from multiple customers;
• Requiring a minimum number of records before presenting a benchmark;
• Removing customer names;
• Removing facility names;
• Removing exact addresses;
• Generalizing facility characteristics;
• Using ranges;
• Using averages;
• Using medians;
• Using percentiles;
• Limiting precision;
• Suppressing unusually small categories;
• Applying other statistical protections.

Benchmarking Does Not Necessarily Mean Customer Comparison

The use of information for benchmarking does not necessarily mean that Opti-mized will provide one customer with another customer's identifiable information.

Benchmarks may instead present generalized reference information, ranges, averages, percentiles, classifications, or other statistical summaries.

Research

Aggregated, anonymized, or de-identified information may be used for internal research relating to:

• Facility energy performance;
• Electrical behaviour;
• Equipment behaviour;
• Demand management;
• Energy-loss detection;
• Equipment classification;
• Baseline development;
• Savings analysis;
• Hardware performance;
• Connectivity;
• Data quality;
• System reliability;
• Facility intelligence;
• Retrofit analysis;
• Predictive indicators;
• Other areas related to Opti-mized products and services.

Research may help us identify new methods for improving facility intelligence and the usefulness of our products.

Product Development

We may use aggregated or de-identified information in the research, design, development, testing, validation, and improvement of Opti-mized products.

This may include development of:

• New platform features;
• New dashboards;
• New reports;
• New analytics;
• New detection methods;
• New algorithms;
• New models;
• New hardware;
• New sensors;
• New gateways;
• New firmware;
• New integrations;
• New APIs;
• New customer workflows;
• New facility setup tools;
• New reporting formats;
• New benchmarking functionality;
• New portfolio features.

Improving Algorithms

Aggregated or de-identified information may help us evaluate and improve analytical algorithms.

For example, we may use protected historical information to evaluate whether an algorithm accurately identifies:

• Equipment runtime;
• Equipment cycles;
• Off-hours use;
• Continuous loads;
• Demand contributions;
• Equipment anomalies;
• Savings opportunities.

Improving Models

Where Opti-mized uses statistical, analytical, machine-learning, or other models, aggregated, de-identified, anonymized, or synthetic information may be used where reasonably practicable for generalized model development and improvement.

This may include improving models used for:

• Equipment classification;
• Pattern recognition;
• Anomaly detection;
• Runtime analysis;
• Savings estimation;
• Demand analysis;
• Predictive indicators;
• Facility benchmarking;
• Data validation;
• Other analytical purposes.

Improving Detection Methods

Aggregated or de-identified examples of known operating conditions may help us improve energy-loss and anomaly detection.

For example, we may study general patterns associated with:

• Equipment running after hours;
• Excessive runtime;
• High continuous loads;
• Repeated demand peaks;
• Standby loads;
• Unusual cycling;
• Environmental mismatch.

These patterns may help refine future detection methods.

Improving Savings Calculations

We may use aggregated or de-identified information to evaluate the performance of savings methodologies.

This may include comparing estimated savings with observed results where appropriate and available.

We may use those comparisons to improve:

• Runtime assumptions;
• Cost calculations;
• Annualization methods;
• Seasonal adjustments;
• Demand assumptions;
• Savings ranges;
• Confidence ranges;
• Other calculation methods.

Measurement and Verification Research

Aggregated or de-identified before-and-after information may be used to understand how well certain analytical methods estimate actual outcomes.

For example, we may compare:

• Estimated runtime reduction with measured runtime reduction;
• Estimated energy savings with measured savings;
• Estimated demand reduction with observed demand;
• Estimated changes in equipment operation with post-implementation behaviour.

This may help improve future measurement and verification capabilities.

Testing and Quality Assurance

Aggregated and de-identified information may be used for testing.

This may include:

• Software testing;
• Hardware testing;
• Analytics testing;
• Regression testing;
• Performance testing;
• Data-quality testing;
• Report testing;
• User-interface testing;
• Reliability testing;
• Security testing.

Where practical, we may use de-identified, anonymized, aggregated, limited, or synthetic information instead of directly identifiable customer information in testing environments.

Synthetic Information

Opti-mized may create synthetic information based on general characteristics or patterns observed in real-world data.

Synthetic information is designed to resemble relevant technical characteristics without representing the actual identifiable information of a specific customer, facility, or individual.

Synthetic information may be used for:

• Software development;
• Testing;
• Demonstrations;
• Analytics development;
• Quality assurance;
• Model development;
• Training internal systems;
• Security testing.

Demonstration Environments

We may use synthetic, anonymized, de-identified, aggregated, or sample information in demonstration environments where reasonably practicable.

This can reduce the need to display actual identifiable customer information when demonstrating Opti-mized functionality to prospective customers, partners, employees, contractors, or other audiences.

Internal Analytics

Aggregated information may be used for internal business analytics.

For example, we may evaluate:

• Number of customers;
• Number of facilities;
• Number of connected devices;
• Number of measured circuits;
• Platform usage;
• Report generation;
• Customer support volume;
• Product adoption;
• Hardware deployment;
• Feature usage;
• System reliability;
• Customer retention;
• Business growth.

Internal analytics may be used to allocate resources, plan product development, improve customer service, and operate our business.

Commercial Planning

Aggregated or de-identified information may be used for commercial planning.

This may include understanding:

• Which facility types most frequently use particular features;
• Which hardware configurations are most common;
• Which equipment categories are frequently analyzed;
• Which analytical features are most useful;
• Which services customers commonly request;
• Which products require additional support;
• Which capabilities may warrant future investment.

Commercial planning may inform pricing, product strategy, staffing, infrastructure planning, market development, or service offerings.

Capacity Planning

We may use aggregated system and product information to estimate future infrastructure needs.

This may include planning for:

• Data storage;
• Cloud computing;
• Database capacity;
• Network capacity;
• Connected devices;
• Data processing;
• Reporting;
• Customer support;
• Hardware production;
• Device communications.

Hardware Development

Aggregated device information may help us design future hardware.

For example, we may evaluate:

• Typical installation configurations;
• Common CT sizes;
• Common circuit quantities;
• Gateway usage;
• Connectivity methods;
• Common device errors;
• Hardware expansion requirements;
• Typical facility deployment sizes.

This may influence the design of future sensors, gateways, CT Hubs, enclosures, communications systems, or related hardware.

Firmware Development

Aggregated hardware diagnostics may be used to identify opportunities to improve firmware.

This may include improving:

• Connectivity;
• Data transmission;
• Device reliability;
• Security;
• Error recovery;
• Update processes;
• Device configuration;
• Measurement processing.

Software Development

Aggregated or de-identified platform information may help identify opportunities to improve software.

This may include:

• Improving speed;
• Improving usability;
• Improving reliability;
• Simplifying workflows;
• Improving dashboards;
• Improving reporting;
• Improving device management;
• Improving facility setup;
• Improving user permissions;
• Improving search;
• Improving alerts.

Security Research and Improvement

Aggregated, de-identified, or technical information may also be used to improve the security of Opti-mized.

We may analyze patterns involving:

• Failed login attempts;
• Suspicious activity;
• Authentication errors;
• Security events;
• System vulnerabilities;
• Device security;
• Network activity;
• Unauthorized access attempts.

Security analysis may help us improve access controls, authentication systems, monitoring, incident response, and device security.

Reliability Research

We may use aggregated system performance information to identify opportunities to improve reliability.

This may include:

• Uptime;
• Service interruptions;
• Connection failures;
• Gateway communication;
• Sensor communication;
• Report generation;
• API failures;
• Data-processing errors;
• Database performance.

Customer Experience Research

Aggregated product usage and support information may be used to understand how customers interact with Opti-mized.

For example, we may analyze:

• Which setup steps cause confusion;
• Which reports are most frequently viewed;
• Which features are rarely used;
• Which workflows generate support requests;
• Which alerts customers interact with;
• Which dashboards are most useful.

This may help improve usability and customer experience.

Customer Feedback

Feedback may be aggregated with feedback from other users or customers.

For example, we may summarize:

• Common feature requests;
• Common support concerns;
• Common hardware requests;
• Common reporting preferences;
• Common analytics feedback;
• Common installation issues.

This may help us prioritize product improvements.

Aggregated Support Information

Customer support records may be aggregated to identify recurring themes.

For example, we may analyze:

• Common technical problems;
• Common connectivity issues;
• Frequent configuration errors;
• Common installation questions;
• Common report questions;
• Common account issues.

This may help us improve documentation, support processes, product design, and troubleshooting tools.

Aggregated Installation Information

Installation information may be aggregated to improve deployment processes.

For example, we may analyze:

• Typical number of panels per facility;
• Typical number of circuits monitored;
• Common gateway locations;
• Common CT sizes;
• Common network configurations;
• Typical installation challenges;
• Common commissioning issues.

Aggregated Utility Information

Where appropriate and sufficiently protected, utility information may be aggregated or de-identified to understand trends in:

• Energy consumption;
• Demand;
• Rate structures;
• Seasonal changes;
• Utility costs;
• Facility-level energy intensity;
• Potential savings.

Such analysis may support calculation improvements, benchmarks, and facility intelligence.

Industry and Facility Benchmarks

Aggregated information may allow Opti-mized to develop generalized benchmarks that help users understand whether a particular pattern is typical, unusual, high, low, or otherwise noteworthy.

Benchmarks may be based on:

• Facility type;
• Equipment type;
• Facility size;
• Operating schedule;
• Climate region;
• General geographic region;
• Equipment category;
• Electrical load;
• Runtime;
• Demand;
• Other relevant characteristics.

The purpose of benchmarking is generally to provide context, not to disclose identifiable information about another customer.

Portfolio-Level Aggregation

Customers that manage multiple facilities may use aggregated information within their own organization.

For example, Opti-mized may provide an authorized portfolio user with:

• Total portfolio energy use;
• Total detected opportunities;
• Aggregate estimated savings;
• Facility rankings;
• Equipment rankings;
• Cross-facility trends;
• Portfolio demand information.

This form of aggregation may remain identifiable to the customer because it is intended to provide that customer with information about its own portfolio.

Such internal customer aggregation is different from cross-customer de-identified benchmarking.

Customer-Specific Aggregation

Information may also be aggregated within a single customer account.

For example, measurements may be combined across:

• Multiple circuits;
• Multiple panels;
• Multiple equipment items;
• Multiple buildings;
• Multiple facilities.

This may be used to create customer-specific summaries and does not necessarily involve de-identification.

Cross-Customer Aggregation

Where information from multiple customers is combined for broader research, benchmarking, or product development, we may apply additional protections appropriate to the context.

These may include:

• Removing direct identifiers;
• Grouping information;
• Using statistical summaries;
• Limiting precision;
• Suppressing small sample sizes;
• Restricting access;
• Limiting export functionality;
• Using ranges or percentiles.

Minimum Group Sizes

Where appropriate, we may require that a sufficient number of records, devices, facilities, or other units be included before a cross-customer benchmark or statistic is generated or displayed.

Minimum group sizes can reduce the risk that information about a specific customer or facility can be inferred from a benchmark.

The appropriate group size may depend on the type of information and intended use.

Avoiding Unique Combinations

Even where obvious identifiers are removed, unusual combinations of characteristics could sometimes make a record more identifiable.

For example, a highly unusual facility type in a very small geographic area could potentially be easier to recognize.

Where appropriate, Opti-mized may reduce this risk by:

• Generalizing categories;
• Suppressing unusual records;
• Combining categories;
• Reducing geographic precision;
• Reducing temporal precision;
• Limiting detailed attributes;
• Using broader ranges.

Geographic Generalization

Exact facility locations may be unnecessary for many forms of benchmarking or product analysis.

Where appropriate, location information may be generalized to:

• City;
• Region;
• Province or state;
• Climate zone;
• Country;
• Other broader geographic category.

In some cases, geographic information may be removed entirely.

Temporal Generalization

Exact timestamps may also be generalized where precise timing is unnecessary.

For example, data may be summarized by:

• Hour;
• Day;
• Week;
• Month;
• Season;
• Year.

This can help reduce unnecessary granularity while preserving useful trends.

Range-Based Reporting

Rather than presenting exact values, aggregated or de-identified results may be expressed as ranges.

For example:

• Runtime range;
• Energy-use range;
• Savings range;
• Demand range;
• Facility-size range;
• Equipment-count range.

Ranges can reduce identifiability while preserving analytical value.

Percentiles and Statistical Summaries

Benchmarks may be expressed using statistical measures such as:

• Average;
• Median;
• Percentile;
• Standard deviation;
• Minimum;
• Maximum;
• Distribution;
• Range.

These statistics may provide useful context without exposing individual underlying records.

Aggregated Data in Reports

Opti-mized reports may include aggregated information.

Examples may include:

• Total facility energy use;
• Total annual savings;
• Total number of opportunities;
• Total demand contribution;
• Equipment category summaries;
• Building-level summaries;
• Portfolio-level summaries.

The fact that information is aggregated within a customer's report does not necessarily mean that it is de-identified from that customer.

Aggregated Data in Dashboards

Dashboards may display aggregated information such as:

• Total facility load;
• Total portfolio savings;
• Equipment category totals;
• Number of detected opportunities;
• Combined runtime;
• Summary metrics.

Again, customer-specific aggregation is different from de-identification.

External Use of Aggregated Information

Where appropriate, Opti-mized may use aggregated or de-identified information externally for purposes such as:

• Benchmarking;
• Industry analysis;
• Product descriptions;
• Research findings;
• Technical materials;
• Business planning;
• General performance statistics.

We may seek to structure such information so that it does not reasonably identify a particular individual or customer.

Public Statistics

Opti-mized may use aggregated statistics to describe general characteristics of its business, products, technology, or customer base.

Examples might include general statistics concerning:

• Number of facilities served;
• Number of connected circuits;
• General categories of equipment analyzed;
• Aggregate opportunities identified;
• Hardware reliability;
• General product usage;
• General analytical capabilities.

Where public statistics are based on customer information, we may take reasonable steps intended to avoid unnecessary identification of individual customers.

Case Studies Are Different

Using aggregated information is distinct from publishing an identifiable customer case study.

Opti-mized does not treat the ability to create aggregated statistics as automatic permission to publicly identify a customer, facility, or project.

Where a public case study, testimonial, customer logo, named project, or identifiable facility result is used, additional authorization may be sought where required.

Research Publications

If Opti-mized publishes research or analytical findings based on customer-derived information, we may use aggregated, anonymized, or de-identified information where reasonably practicable.

Research publications may describe:

• General trends;
• Statistical relationships;
• Equipment behaviours;
• Facility trends;
• Hardware performance;
• Energy-saving patterns.

The intent of such research would generally be to communicate broader insights rather than disclose identifiable customer information.

Third-Party Research

If Opti-mized works with an external research organization, consultant, academic institution, technology provider, or other third party on research involving customer-derived information, additional safeguards may apply.

Depending on the circumstances, these safeguards may include:

• Aggregation;
• De-identification;
• Anonymization;
• Confidentiality obligations;
• Data-use restrictions;
• Security requirements;
• Limited access;
• Customer authorization where appropriate;
• Contractual protections.

Service Providers

Service providers assisting with analytics, infrastructure, development, testing, or research may process aggregated or de-identified information on behalf of Opti-mized.

Where identifiable information is unnecessary for the provider's task, Opti-mized may seek to provide only aggregated, de-identified, anonymized, limited, or otherwise appropriately protected information where reasonably practicable.

Artificial Intelligence and Machine Learning

Aggregated, anonymized, de-identified, synthetic, or otherwise appropriately protected information may be used to improve Opti-mized analytical systems, including statistical, algorithmic, machine-learning, or artificial-intelligence systems where applicable.

Such information may help improve:

• Pattern detection;
• Equipment classification;
• Runtime analysis;
• Anomaly detection;
• Energy-loss detection;
• Savings estimation;
• Equipment mapping;
• Document processing;
• Photo interpretation;
• Data validation;
• Recommendations;
• Report generation.

General-Purpose Artificial Intelligence Models

As described elsewhere in this Privacy Policy, Opti-mized does not provide identifiable customer Facility Data or identifiable Energy and Operational Data to unrelated third parties for the purpose of training those third parties' general-purpose artificial intelligence models unless specifically authorized by the customer or otherwise disclosed and permitted.

Aggregated, anonymized, or appropriately de-identified information may be treated differently where it no longer reasonably identifies the customer or individual and where use is permitted by applicable law and applicable agreements.

Aggregated Data and Customer Confidentiality

Some information may not constitute personal information but may nevertheless be commercially sensitive.

Accordingly, Opti-mized may consider customer confidentiality obligations when creating or using aggregated facility information.

The fact that data has commercial or analytical value does not automatically mean that Opti-mized will disclose identifiable customer information.

Aggregated Information and Intellectual Property

The use or creation of aggregated or de-identified information does not by itself determine ownership of data, analytical outputs, reports, software, models, algorithms, or intellectual property.

Ownership and licensing rights may also be governed by applicable customer agreements, terms of service, contracts, intellectual-property law, and other legal arrangements.

Retention of Aggregated Information

Where information has been validly aggregated, anonymized, or de-identified so that it no longer constitutes personal information under applicable law, Opti-mized may retain the resulting information for research, analytics, product development, benchmarking, statistical analysis, or other legitimate purposes for longer periods than the identifiable information from which it was derived, where permitted.

For example, an identifiable customer record may eventually be deleted or anonymized while aggregated statistical information derived from that record remains part of a historical benchmark.

Retention of De-Identified Information

De-identified information may be retained for as long as reasonably useful for purposes such as:

• Research;
• Product improvement;
• Benchmarking;
• Analytics;
• Quality assurance;
• Model development;
• Historical analysis;
• Business planning;
• Security;
• Statistical analysis.

Applicable laws or agreements may impose additional limitations.

Backups

Aggregated or de-identified information may also appear in backups, archives, disaster-recovery systems, logs, or other technical systems.

Such information may remain subject to applicable security and retention practices.

Re-Identification Risks

Opti-mized recognizes that de-identification is not merely the removal of obvious identifiers.

Depending on the dataset, combinations of information may sometimes create a risk that a record could be associated with a particular individual, customer, or facility.

Accordingly, where appropriate, we may consider factors such as:

• Dataset size;
• Uniqueness of records;
• Availability of external information;
• Geographic precision;
• Temporal precision;
• Facility characteristics;
• Equipment characteristics;
• Sample size;
• Access controls;
• Intended use.

Reasonable Measures Against Re-Identification

We will take reasonable measures intended to prevent information treated as de-identified from being associated with an identifiable individual where required or appropriate.

Depending on the circumstances, such measures may include:

• Removing direct identifiers;
• Replacing identifiers;
• Limiting precision;
• Generalizing information;
• Aggregating records;
• Restricting access;
• Limiting disclosure;
• Applying confidentiality requirements;
• Applying contractual restrictions;
• Using statistical controls;
• Suppressing small groups;
• Monitoring access;
• Using technical safeguards.

No Intentional Re-Identification for Unrelated Purposes

Where Opti-mized has created or received information that is treated as de-identified, we do not intend to attempt to re-identify an individual for unrelated purposes merely because technical re-identification could potentially be possible.

Where re-association is necessary for a legitimate purpose, such as troubleshooting a customer-specific issue involving pseudonymized information, the information may not be considered fully anonymized and may continue to be handled as protected information.

Contractual Restrictions on Re-Identification

Where appropriate, third parties that receive de-identified information may be subject to contractual restrictions intended to prevent:

• Re-identification;
• Unauthorized use;
• Unauthorized disclosure;
• Attempts to combine information with other datasets in a manner that defeats de-identification;
• Use beyond permitted purposes.

Access Controls

Access to aggregated or de-identified datasets may be restricted based on business need.

For example, access may be limited to authorized personnel involved in:

• Product development;
• Analytics;
• Research;
• Quality assurance;
• Security;
• Engineering;
• Business intelligence;
• Benchmarking.

Internal Data Separation

Where technically appropriate, identifiable customer information may be maintained separately from broader analytical datasets.

This may help reduce unnecessary use of direct identifiers in product development or research environments.

Data Minimization

When aggregated or de-identified information is sufficient for a particular purpose, Opti-mized may prefer to use that form of information rather than directly identifiable personal information where reasonably practicable.

For example:

• Hardware reliability analysis may not require customer contact information;
• Equipment runtime benchmarking may not require exact facility addresses;
• Platform feature analysis may not require utility account numbers;
• Energy-loss research may not require billing contact information.

De-Identification Is Context-Dependent

Whether information is sufficiently de-identified depends on the context.

Information that appears anonymous on its own may become more identifiable when combined with other information.

Accordingly, Opti-mized may evaluate de-identification in light of:

• The information retained;
• The information removed;
• Who has access;
• What other information may be available;
• The intended use;
• The technical environment;
• Applicable law.

Not Every Aggregated Dataset Is Anonymous

Aggregation alone does not necessarily mean that information is anonymous.

For example, a report aggregating all electrical consumption within a single identifiable customer's facility may remain customer-specific.

Similarly, a portfolio total for a customer with three facilities may still clearly relate to that customer.

Accordingly, Opti-mized distinguishes between:

• Information aggregated for a customer;
• Information de-identified from a customer;
• Information anonymized under applicable standards;
• Broader cross-customer statistical information.

Not Every De-Identified Dataset Is Public

The fact that information has been de-identified does not necessarily mean that Opti-mized will make it publicly available.

De-identified information may remain subject to:

• Internal access controls;
• Confidentiality obligations;
• Contracts;
• Security controls;
• Business restrictions;
• Research protocols;
• Applicable laws.

Not Every Benchmark Is Shared

Opti-mized may create internal benchmarks that are used only for quality assurance, analytical development, engineering, or product improvement.

The existence of a benchmark does not necessarily mean that the benchmark will be made available to customers or the public.

No Guarantee That Every Analysis Uses Aggregated Data

Certain customer-specific services necessarily require identifiable customer information.

For example, Opti-mized may need to use customer-specific data to:

• Generate a customer's dashboard;
• Troubleshoot a customer's device;
• Correct a customer's facility configuration;
• Calculate a customer's savings;
• Generate a customer's Facility Intelligence Report;
• Respond to a customer's support request.

The preference for aggregated or de-identified information applies primarily where broader analysis can reasonably be conducted without customer-specific identifiers.

Use of Customer-Specific Data Where Necessary

Where customer-specific information is necessary to provide or improve services for that customer, Opti-mized may use the information in identifiable form as permitted by this Privacy Policy, applicable agreements, and applicable law.

For example, customer-specific analysis may require the system to know:

• Which facility generated a measurement;
• Which circuit corresponds to a piece of equipment;
• Which utility rate applies;
• Which operating schedule applies;
• Which equipment classification applies.

This is different from broader cross-customer benchmarking or research.

Aggregation Does Not Replace Security

Aggregation and de-identification are additional privacy and confidentiality techniques.

They do not replace other safeguards.

Opti-mized may also use:

• Encryption;
• Access controls;
• Authentication;
• Logging;
• Confidentiality requirements;
• Data-retention controls;
• Security monitoring;
• Vendor controls;
• Organizational policies.

Aggregation Does Not Eliminate Contractual Obligations

Customer information may be subject to contractual restrictions even if certain privacy laws do not apply to that information.

For example, commercial facility information may remain subject to:

• Confidentiality provisions;
• Data-use restrictions;
• Customer agreements;
• Nondisclosure agreements;
• Procurement requirements;
• Security obligations.

Opti-mized may consider such obligations when using aggregated or de-identified customer information.

Applicable Law

The legal treatment of aggregated, anonymized, pseudonymized, and de-identified information varies by jurisdiction.

Certain privacy laws may continue to apply to information that can reasonably be linked back to an identifiable individual.

Other laws may exclude sufficiently anonymized or de-identified information from the definition of personal information.

Opti-mized may adapt its practices to the legal requirements applicable to the relevant information and jurisdiction.

Changes in Legal Standards

Standards relating to anonymization, de-identification, statistical disclosure, artificial intelligence, and data use may evolve over time.

Opti-mized may therefore update its methods, policies, contractual practices, and technical safeguards as legal requirements, industry standards, or technical capabilities change.

Changes in Technology

Techniques for both de-identification and re-identification may evolve.

Accordingly, a method considered appropriate at one time may later require additional safeguards.

Opti-mized may periodically review its approaches to aggregation and de-identification where appropriate.

Development of New De-Identification Methods

We may adopt new privacy-enhancing techniques as they become practical.

These could include methods such as:

• Improved masking;
• Tokenization;
• Statistical disclosure controls;
• Data minimization;
• Differential privacy techniques where appropriate;
• Synthetic data generation;
• Secure analytical environments;
• Other privacy-enhancing technologies.

The use of a particular method will depend on the applicable use case and technical requirements.

Business Planning

Aggregated or de-identified information may be used to understand broad business trends.

For example, we may analyze:

• Growth in connected facilities;
• Growth in circuits monitored;
• Types of facilities adopting Opti-mized;
• Common hardware configurations;
• Common customer needs;
• Product feature adoption;
• Service utilization;
• Support requirements.

This information may support strategic planning without requiring direct identification of individual users.

Commercial Analytics

Aggregated information may also be used for commercial analytics such as:

• Market analysis;
• Product planning;
• Resource allocation;
• Pricing analysis;
• Infrastructure planning;
• Hardware planning;
• Staffing;
• Customer-success planning.

Product Performance Statistics

Opti-mized may calculate aggregated product performance statistics relating to:

• Hardware reliability;
• Gateway uptime;
• Sensor connectivity;
• Measurement availability;
• Report-generation speed;
• Platform performance;
• System uptime;
• Data-processing reliability.

These statistics may be used internally or, where appropriate, externally.

Aggregated Environmental Analysis

Where environmental or weather information is used, we may analyze aggregated relationships between environmental conditions and facility or equipment behaviour.

For example, we may examine:

• HVAC runtime versus outdoor temperature;
• Heating load versus seasonal conditions;
• Cooling load versus temperature;
• Demand during extreme weather;
• Environmental mismatch patterns.

Aggregated Demand Analysis

We may use aggregated demand information to understand:

• Typical demand peaks;
• Common demand contributors;
• Time-of-day demand patterns;
• Facility-type demand characteristics;
• Opportunities for demand management.

Aggregated Retrofit Analysis

Where customers evaluate or implement retrofits, aggregated or de-identified information may be used to understand:

• Common retrofit opportunities;
• Typical pre-retrofit performance;
• Typical post-retrofit performance;
• Common savings ranges;
• Typical payback periods;
• Measurement and verification patterns.

Aggregated Maintenance Analysis

Where appropriate, aggregated or de-identified information may be used to understand patterns that could support maintenance-related analytics.

For example:

• Changes in runtime before maintenance;
• Changes in cycling;
• Changes in load;
• Changes in electrical behaviour;
• Recurring equipment anomalies.

Aggregated Report Analytics

We may analyze which report sections or outputs customers use most frequently.

This may include:

• Report downloads;
• Report types;
• Common opportunity categories;
• Common savings ranges;
• Common equipment categories.

Such information may help improve reporting functionality.

De-Identified Development Examples

Developers or analysts may use de-identified examples to understand how a feature behaves.

For example, a development dataset may contain:

• Equipment category;
• General runtime pattern;
• General load;
• Detected condition;
• General facility type.

without containing:

• Customer name;
• Facility name;
• User name;
• Exact facility address.

This can allow useful development while limiting direct identifiers.

Use in Training Internal Personnel

Aggregated, de-identified, anonymized, or synthetic examples may be used to train Opti-mized employees or contractors on:

• Product operation;
• Facility setup;
• Analytics;
• Customer support;
• Troubleshooting;
• Hardware installation;
• Report interpretation;
• Equipment classification.

Where identifiable information is unnecessary for training, it should not be used merely for convenience.

Public Demonstrations

Where Opti-mized demonstrates analytical functionality publicly, we may use:

• Synthetic information;
• Sample information;
• De-identified information;
• Aggregated information;
• Customer information where specifically authorized.

The goal is generally to avoid publicly exposing identifiable customer information merely to demonstrate functionality.

Business Transfers

Aggregated or de-identified information may be included in business assets transferred or reviewed in connection with a merger, financing, acquisition, reorganization, or similar transaction.

Identifiable information involved in such transactions is addressed separately under other sections of this Privacy Policy.

Legal Uses

Aggregated or de-identified information may also be used for legal, compliance, audit, security, or risk-management purposes where relevant.

Auditing De-Identification Practices

Where appropriate, Opti-mized may review or audit de-identification practices to evaluate whether they remain appropriate for the intended purpose.

This may include reviewing:

• Identifier removal;
• Data access;
• Statistical disclosure risk;
• Minimum group sizes;
• Export restrictions;
• Third-party access;
• Retention;
• Re-identification risk.

Documentation

Opti-mized may maintain internal documentation describing:

• De-identification methods;
• Aggregation processes;
• Dataset purposes;
• Access permissions;
• Retention;
• Data sources;
• Analytical uses.

Documentation may support consistency, accountability, security, and compliance.

Summary of Permitted Uses

Opti-mized may use aggregated, anonymized, de-identified, statistical, pseudonymized, or otherwise appropriately protected information for purposes including:

• Research;
• Benchmarking;
• Product development;
• Hardware development;
• Software development;
• Firmware development;
• Analytics improvement;
• Algorithm development;
• Model development;
• Energy-loss detection;
• Equipment classification;
• Runtime analysis;
• Demand analysis;
• Savings calculation improvement;
• Facility Intelligence development;
• Quality assurance;
• Testing;
• Security improvement;
• Reliability improvement;
• Capacity planning;
• Infrastructure planning;
• Product usage analysis;
• Customer-experience improvement;
• Internal analytics;
• Business intelligence;
• Commercial planning;
• Statistical reporting;
• Industry analysis;
• Facility benchmarking;
• Equipment benchmarking;
• Portfolio analysis;
• Technical research;
• Development of new Opti-mized features and services;
• Other legitimate business purposes permitted by applicable law and applicable agreements.

Our Approach to De-Identified Information

Where reasonably practicable, Opti-mized seeks to use aggregated, anonymized, de-identified, statistical, synthetic, or otherwise appropriately protected information for broader research, benchmarking, product development, analytical improvement, and similar purposes when direct identification of a customer or individual is unnecessary.

We will take reasonable measures intended to prevent information treated as de-identified from being associated with an identifiable individual where required or appropriate.

Those measures may include removing direct identifiers, generalizing information, combining records, reducing precision, limiting access, applying contractual restrictions, using statistical controls, or implementing other technical and organizational safeguards appropriate to the circumstances.

The specific safeguards used may vary depending on the nature of the information, the purpose for which it is used, the likelihood of re-identification, the technical environment, contractual requirements, and applicable law.

Aggregated or de-identified information may continue to provide substantial value for understanding facility energy performance, equipment operating behaviour, energy-saving opportunities, hardware performance, product usage, system reliability, operational patterns, and industry or facility benchmarks without requiring Opti-mized to disclose or rely on directly identifiable customer information for every analytical purpose.

Our objective is to preserve the technical and analytical value necessary to improve Opti-mized while reducing unnecessary identification of individuals, customers, facilities, accounts, and other sensitive records.

Opti-mized recognizes that customers may provide, upload, transmit, generate, connect, or otherwise make available significant amounts of information relating to their facilities, equipment, electrical systems, operations, projects, utility usage, configurations, and other business activities.

This information may include facility information, Energy and Operational Data, photographs, documents, utility information, panel schedules, equipment records, circuit information, operating schedules, project information, uploaded files, customer-defined labels, configuration information, and other information supplied by or on behalf of a customer.

Customers retain their rights and interests in the underlying customer information they provide or make available to Opti-mized, subject to applicable agreements, third-party rights, intellectual-property laws, and other legal requirements.

For purposes of this Privacy Policy, we may refer collectively to this category of information as “Customer Facility and Operational Data.”

Customer Facility and Operational Data may include information that constitutes personal information under applicable law as well as information that relates primarily to buildings, equipment, electrical systems, organizations, or business operations and does not identify an individual.

The fact that certain Customer Facility and Operational Data may not constitute personal information does not mean that Opti-mized treats such information as public or unrestricted.

We may continue to protect customer-specific facility, equipment, operational, electrical, technical, and project information through contractual obligations, confidentiality requirements, access controls, security measures, internal policies, and other safeguards appropriate to the circumstances.

Categories of Customer Facility and Operational Data

Customer Facility and Operational Data may include information such as:

• Facility names;
• Facility addresses;
• Building information;
• Facility types;
• Facility size;
• Facility operating schedules;
• Facility operating characteristics;
• Building systems;
• Mechanical systems;
• Electrical systems;
• Electrical panels;
• MCCs;
• Switchgear;
• Transformers;
• Breakers;
• Circuits;
• Circuit identifiers;
• Circuit names;
• Panel schedules;
• Breaker schedules;
• Equipment names;
• Equipment descriptions;
• Equipment categories;
• Equipment identifiers;
• Equipment quantities;
• Equipment locations;
• Equipment specifications;
• Equipment operating schedules;
• Equipment photographs;
• Electrical-room photographs;
• Panel photographs;
• MCC photographs;
• Switchgear photographs;
• Facility photographs;
• Utility bills;
• Utility consumption information;
• Utility demand information;
• Utility-rate information;
• Historical energy information;
• Energy and Operational Data;
• Electrical current measurements;
• Voltage measurements;
• Power measurements;
• Energy consumption;
• Equipment runtime;
• Equipment cycling;
• Demand;
• Peak demand;
• Baseload;
• Off-hours usage;
• On-hours usage;
• Continuous load information;
• Sensor measurements;
• Gateway information;
• Hardware identifiers;
• Device configuration;
• Installation information;
• Commissioning information;
• Facility setup information;
• Customer-provided notes;
• Customer-provided labels;
• Customer-provided classifications;
• Uploaded documents;
• Technical records;
• Project documentation;
• Operational objectives;
• Facility objectives;
• Other information provided by or on behalf of the customer.

The specific categories applicable to any particular customer depend on the products and services being used.

Customer Rights in Underlying Data

Opti-mized does not claim ownership of a customer's underlying facility, equipment, operational, utility, electrical, document, photograph, or other customer-provided information merely because that information is uploaded to, transmitted through, stored in, analyzed by, or otherwise processed through Opti-mized products or services.

For example, if a customer uploads a panel schedule, the fact that Opti-mized stores or processes that panel schedule does not by itself transfer ownership of the underlying document to Opti-mized.

Similarly, if Opti-mized hardware collects electrical measurements at a customer's facility, the use of Opti-mized hardware and software does not, by itself, mean that Opti-mized claims ownership of the customer's underlying facility operations or electrical usage.

Customers retain whatever ownership, contractual, intellectual-property, confidentiality, access, or other rights they may lawfully hold in the underlying information.

Nothing in this Privacy Policy is intended to transfer ownership of a customer's underlying facility or operational information to Opti-mized merely because the information is processed through our systems.

Authorization to Process Customer Data

In order to provide Opti-mized products and services, customers authorize Opti-mized to access, receive, collect, host, store, transmit, organize, structure, display, analyze, combine, calculate, derive, generate, reproduce, transform, configure, back up, maintain, secure, and otherwise process Customer Facility and Operational Data as reasonably necessary to provide the applicable products and services.

This authorization may include processing necessary to:

• Create customer accounts;
• Create facility records;
• Configure facilities;
• Configure buildings;
• Configure electrical panels;
• Configure MCCs;
• Configure switchgear;
• Configure circuits;
• Configure equipment;
• Configure sensors;
• Configure gateways;
• Configure CT Hubs;
• Configure dashboards;
• Associate equipment with circuits;
• Associate circuits with panels;
• Associate sensors with measurement points;
• Associate gateways with facilities;
• Store historical information;
• Process Energy and Operational Data;
• Analyze equipment behaviour;
• Establish baselines;
• Detect operating patterns;
• Identify potential anomalies;
• Identify potential energy-loss opportunities;
• Calculate runtime;
• Analyze cycling;
• Analyze demand;
• Estimate savings;
• Estimate financial impact;
• Calculate return on investment;
• Calculate payback;
• Generate reports;
• Generate alerts;
• Generate notifications;
• Generate Facility Intelligence Data;
• Provide technical support;
• Troubleshoot hardware;
• Troubleshoot connectivity;
• Maintain systems;
• Improve customer-specific analytics;
• Maintain data quality;
• Protect customer information;
• Provide backups;
• Support integrations;
• Fulfill customer requests;
• Perform other functions reasonably necessary to provide Opti-mized services.

Processing Necessary to Provide the Services

Customers understand that certain processing of Customer Facility and Operational Data is inherent in the operation of Opti-mized.

For example, if a customer installs Opti-mized sensors to analyze a rooftop unit, Opti-mized may need to:

• Receive electrical measurements from the applicable sensor;
• Associate those measurements with a particular measurement channel;
• Associate the measurement channel with a particular circuit;
• Associate the circuit with a particular piece of equipment;
• Store measurements over time;
• Establish historical operating patterns;
• Compare current behaviour with historical behaviour;
• Compare operation with facility schedules;
• Calculate runtime;
• Evaluate load characteristics;
• Generate analytical outputs;
• Present those outputs within the customer's dashboard;
• Include relevant findings in a report or notification.

These processing activities are part of providing the service and do not constitute a transfer of ownership of the customer's underlying data to Opti-mized.

Facility Configuration

Customers authorize Opti-mized to use Customer Facility and Operational Data to configure their facilities within our systems.

Facility configuration may include:

• Creating facility records;
• Creating building records;
• Creating panel records;
• Creating MCC records;
• Creating switchgear records;
• Creating circuit records;
• Creating equipment records;
• Creating device records;
• Mapping circuits;
• Mapping equipment;
• Assigning sensor channels;
• Assigning gateway connections;
• Associating photographs;
• Associating documents;
• Recording customer-provided labels;
• Recording operating schedules;
• Recording utility rates;
• Recording project information;
• Organizing facility hierarchies.

Facility configuration may be performed by Opti-mized, by customers, by authorized users, by installers, by contractors, by consultants, or through a combination of those parties.

Customer-Provided Labels and Descriptions

Customers may create or provide labels, names, descriptions, categories, notes, classifications, and other information used to organize a facility.

Examples may include:

• “Panel A”;
• “Main Distribution Panel”;
• “RTU-3”;
• “Pool Pump”;
• “Lighting Circuit”;
• “Administration Building”;
• “Wastewater Pump #2”;
• Other customer-defined names.

Customers retain their rights in customer-created content, subject to the limited processing rights necessary for Opti-mized to provide the service.

Opti-mized may store, display, organize, transform, or use those labels as necessary to present information within the platform.

Energy and Operational Data

Customer Facility and Operational Data may include Energy and Operational Data collected through Opti-mized hardware.

Energy and Operational Data may include:

• Electrical current;
• Voltage;
• Power;
• Energy consumption;
• Load;
• Demand;
• Circuit-level usage;
• Equipment-level usage;
• Equipment runtime;
• Equipment cycling;
• Start and stop events;
• Baseload;
• Continuous load;
• Idle load;
• Standby load;
• Off-hours operation;
• On-hours operation;
• Peak-demand contribution;
• Historical electrical usage;
• Time-series measurements;
• Device measurements;
• Sensor readings;
• Equipment operating patterns;
• Other electrical or operational measurements.

Customers authorize Opti-mized to process this information as reasonably necessary to provide facility intelligence and related services.

Facility Intelligence Data

Opti-mized may generate Facility Intelligence Data from Customer Facility and Operational Data.

Facility Intelligence Data may include:

• Equipment baselines;
• Runtime calculations;
• Operating patterns;
• Cycling analysis;
• Demand analysis;
• Anomaly indicators;
• Energy-loss opportunities;
• Savings estimates;
• Financial estimates;
• Payback calculations;
• ROI calculations;
• Equipment classifications;
• Facility performance insights;
• Reports;
• Recommendations;
• Alerts;
• Rankings;
• Analytical outputs;
• Other derived information.

Facility Intelligence Data may be generated through software, algorithms, statistical processes, calculations, machine-learning tools where applicable, manual review, professional judgment, customer-provided context, or combinations of these methods.

Distinction Between Underlying Customer Data and Derived Information

Underlying Customer Facility and Operational Data and information generated by Opti-mized may be related but are not necessarily the same thing.

For example:

• A sensor measurement may be underlying Customer Facility and Operational Data;
• A calculated runtime value may be derived information;
• A customer-provided equipment name may be underlying customer information;
• An equipment classification generated by Opti-mized may be derived information;
• A utility bill may be customer-provided data;
• An estimated savings calculation may be derived information;
• Historical power measurements may be customer facility data;
• A baseline created from those measurements may be Facility Intelligence Data.

Rights relating to derived information, analytics, reports, algorithms, software, calculations, intellectual property, and other Opti-mized-generated outputs may be addressed in applicable customer agreements, terms of service, licensing terms, or other contractual arrangements.

Nothing in this Privacy Policy is intended to override those agreements.

No Ownership Claim Merely Through Processing

Opti-mized does not claim ownership of a customer's underlying data merely because:

• The data is uploaded to Opti-mized;
• The data is stored on Opti-mized infrastructure;
• The data is transmitted through an Opti-mized gateway;
• The data is measured using Opti-mized hardware;
• The data appears on an Opti-mized dashboard;
• The data is included in an Opti-mized report;
• The data is analyzed by Opti-mized software;
• The data is used to calculate Facility Intelligence Data;
• The data is backed up by Opti-mized;
• The data is processed by a service provider acting on behalf of Opti-mized.

The processing rights granted to Opti-mized exist so that we can provide, maintain, secure, support, and improve our services as described in this Privacy Policy and applicable agreements.

Limited License or Processing Permission

To the extent legally necessary to provide the services, customers grant Opti-mized the rights and permissions reasonably required to host, store, reproduce, transmit, process, analyze, display, transform, and otherwise use Customer Facility and Operational Data for the purposes described in this Privacy Policy and applicable agreements.

This permission is limited to the purposes reasonably connected with:

• Providing Opti-mized products and services;
• Supporting the customer;
• Securing Opti-mized systems;
• Maintaining the platform;
• Improving customer-specific services;
• Complying with law;
• Exercising contractual rights;
• Other purposes expressly authorized by the customer or described in applicable agreements.

This processing permission does not by itself transfer ownership of the underlying customer data to Opti-mized.

Customer Instructions

Where Opti-mized processes Customer Facility and Operational Data on behalf of a customer, we may process that information in accordance with the customer's instructions, the configuration selected by the customer, the services requested, applicable agreements, and this Privacy Policy.

Customer instructions may be provided through:

• Account configuration;
• Platform settings;
• Facility setup forms;
• Support requests;
• Written communications;
• Contracts;
• Statements of work;
• Integration settings;
• User permissions;
• Other authorized methods.

Authorized Users

Customers may authorize individuals to access Customer Facility and Operational Data through Opti-mized.

Authorized users may include:

• Employees;
• Facility managers;
• Energy managers;
• Administrators;
• Contractors;
• Consultants;
• Electricians;
• Service providers;
• Project managers;
• Municipal employees;
• Property managers;
• Other authorized representatives.

Customers are generally responsible for determining which individuals should have access to their information.

Opti-mized may provide tools that allow customer administrators to:

• Add users;
• Remove users;
• Assign facility access;
• Assign administrative access;
• Limit permissions;
• Configure notification recipients;
• Manage account access.

Customer Responsibility for User Access

Customers should provide access only to individuals who are authorized to view or use Customer Facility and Operational Data.

Where a customer grants access to an authorized user, that user may be able to view, download, export, modify, or otherwise interact with customer information depending on the permissions assigned.

Customers are responsible for managing their authorized users and notifying Opti-mized where access should be removed or modified.

Customer Responsibility for Information Provided

Customers are responsible for ensuring, to the extent required by applicable law, that they have appropriate rights, permissions, authority, or consent to provide information to Opti-mized.

This may apply where customer-provided information includes:

• Personal information about employees;
• Contact information;
• Utility account information;
• Photographs containing individuals;
• Documents containing personal information;
• Information belonging to a facility owner;
• Information provided by a tenant;
• Information belonging to another organization;
• Information subject to contractual confidentiality obligations.

By providing information to Opti-mized, the customer represents that it is authorized to provide or direct the processing of that information to the extent required by applicable law and applicable agreements.

Customer Responsibility for Accuracy

Customers should use reasonable efforts to provide accurate information.

The quality and usefulness of Opti-mized analytics may depend on the accuracy of:

• Facility names;
• Operating schedules;
• Equipment names;
• Equipment classifications;
• Circuit mappings;
• Utility rates;
• Facility configuration;
• Utility bills;
• Equipment associations;
• Other customer-provided information.

Inaccurate or incomplete information may affect:

• Hardware recommendations;
• Facility configurations;
• Savings estimates;
• Runtime calculations;
• Demand analysis;
• Alerts;
• Recommendations;
• Reports;
• Other Facility Intelligence Data.

Opti-mized may attempt to identify obvious inconsistencies, but we cannot guarantee the accuracy of customer-provided information.

Customer Corrections

Customers may update or correct information where platform functionality allows or by contacting Opti-mized.

Corrections may include:

• Equipment names;
• Circuit labels;
• Facility names;
• Operating schedules;
• Utility information;
• Equipment categories;
• User information;
• Facility configurations;
• Other customer-provided information.

Customer corrections may improve future analysis and Facility Intelligence Data.

Customer Facility Photos

Photographs submitted by customers may become part of Customer Facility and Operational Data.

These photographs may include:

• Electrical panels;
• MCCs;
• Switchgear;
• Equipment;
• Electrical rooms;
• Nameplates;
• Panel schedules;
• Facility infrastructure;
• Installation conditions.

Customers authorize Opti-mized to process these photographs as reasonably necessary to:

• Understand facility configuration;
• Determine hardware requirements;
• Configure customer facilities;
• Support installation;
• Support troubleshooting;
• Identify equipment;
• Extract relevant information;
• Maintain facility records;
• Provide Facility Intelligence.

Opti-mized does not claim ownership of a customer's original photograph merely because it is uploaded or processed through our services.

Customer Documents

Customer Facility and Operational Data may also include documents such as:

• Utility bills;
• Panel schedules;
• Electrical drawings;
• Equipment schedules;
• Floor plans;
• Technical reports;
• Energy reports;
• Spreadsheets;
• Equipment lists;
• Project documentation;
• Installation records;
• Other facility documents.

Customers authorize Opti-mized to process these documents as reasonably necessary to provide the applicable service.

Utility Data

Utility information may be provided directly by customers or obtained through authorized integrations or service providers.

Customer utility information may include:

• Account information;
• Meter information;
• Consumption;
• Demand;
• Rates;
• Charges;
• Historical usage;
• Billing periods;
• Utility bills.

Opti-mized may use this information to:

• Establish historical baselines;
• Compare measured and billed consumption;
• Calculate costs;
• Estimate savings;
• Analyze demand;
• Generate Facility Intelligence Data;
• Support reports;
• Support measurement and verification.

Data Collected Through Connected Hardware

Where Opti-mized hardware is installed, the system may automatically generate Customer Facility and Operational Data.

Customers authorize this collection and processing as part of their use of the connected service.

The frequency, granularity, and type of data collected may depend on:

• Hardware configuration;
• Sensor configuration;
• Gateway configuration;
• Number of circuits;
• Device capabilities;
• Customer settings;
• Services enabled;
• Firmware;
• Other technical factors.

Customer Control Over Hardware Deployment

Customers generally determine, directly or through their authorized representatives, where Opti-mized hardware is deployed within their facilities.

This may include decisions concerning:

• Which facilities to monitor;
• Which electrical panels to include;
• Which circuits to measure;
• Which equipment to associate with measurements;
• Which buildings to include;
• Which hardware to install;
• Which users should access the resulting information.

Customer-Specific Analysis

Customer Facility and Operational Data may be used to create customer-specific analysis.

This may include:

• Facility-specific baselines;
• Equipment-specific baselines;
• Customer-specific savings calculations;
• Customer-specific utility-rate calculations;
• Customer-specific alerts;
• Customer-specific recommendations;
• Customer-specific reports;
• Customer-specific equipment classifications;
• Customer-specific facility mappings.

Customer-specific processing may require identifiable facility information because the analysis must correspond with the customer's actual facility and equipment.

Improvement of Services for the Customer

Opti-mized may use a customer's information to improve services for that customer.

For example, we may use historical data to:

• Improve equipment baselines;
• Improve runtime detection;
• Improve alerts;
• Improve anomaly thresholds;
• Improve equipment classification;
• Improve customer-specific savings calculations;
• Improve report accuracy;
• Improve facility configuration.

This use is part of providing and improving the service to the customer.

Broader Product Improvement

As described in Sections 5 and 6 of this Privacy Policy, Opti-mized may also use aggregated, anonymized, de-identified, statistical, synthetic, or otherwise appropriately protected information for broader product development, research, analytics, benchmarking, and model improvement where reasonably practicable.

The use of information for these broader purposes does not mean that Opti-mized claims ownership of the customer's underlying Facility Data or Energy and Operational Data.

Aggregated Data Derived From Customer Data

Opti-mized may create aggregated information from Customer Facility and Operational Data.

For example, we may create statistical information concerning:

• Hardware reliability;
• Equipment runtime;
• Energy-loss categories;
• Platform usage;
• Facility types;
• Typical demand patterns;
• System reliability;
• Equipment categories;
• General product performance.

Where information is sufficiently aggregated or de-identified so that it no longer reasonably identifies the customer or an individual, the resulting information may be used as described elsewhere in this Privacy Policy.

De-Identified Data

Customer Facility and Operational Data may be de-identified for purposes such as:

• Research;
• Benchmarking;
• Product improvement;
• Statistical analysis;
• Quality assurance;
• Model development;
• Hardware improvement;
• Analytics development.

Where reasonably practicable, we may remove or generalize information such as:

• Customer name;
• Facility name;
• Street address;
• User names;
• Contact information;
• Account identifiers;
• Other direct identifiers.

Confidential Customer Data

Some Customer Facility and Operational Data may be commercially sensitive even though it does not constitute personal information.

Examples may include:

• Facility electrical layouts;
• Operating schedules;
• Equipment configurations;
• Utility consumption;
• Utility cost;
• Equipment performance;
• Facility energy use;
• Demand patterns;
• Equipment operating behaviour;
• Retrofit plans;
• Project information.

Opti-mized may protect such information through:

• Contractual confidentiality provisions;
• Access controls;
• Authentication;
• Security controls;
• Internal policies;
• Technical safeguards;
• Service-provider obligations;
• Other measures appropriate to the circumstances.

Access by Opti-mized Personnel

Authorized Opti-mized personnel may access Customer Facility and Operational Data where reasonably necessary for legitimate purposes such as:

• Customer support;
• Technical support;
• Facility configuration;
• Installation support;
• Data-quality review;
• Troubleshooting;
• Report review;
• Product maintenance;
• Security;
• Quality assurance;
• Customer-requested analysis;
• Product improvement;
• Compliance.

Access may be limited based on job role, business need, technical controls, and internal policy.

Service Provider Access

Opti-mized may use service providers to host, store, process, transmit, support, secure, or otherwise handle Customer Facility and Operational Data on our behalf.

Service providers may include providers of:

• Cloud hosting;
• Data storage;
• Infrastructure;
• Communications;
• Cybersecurity;
• Technical support;
• Software development;
• Analytics;
• Payment processing;
• Customer support;
• Other services.

Where service providers process customer information on behalf of Opti-mized, their access may be limited to information reasonably necessary to provide the applicable service and may be subject to contractual, confidentiality, security, and data-processing obligations.

No Independent Rights for Service Providers

The fact that a service provider processes Customer Facility and Operational Data on behalf of Opti-mized does not automatically give that provider the right to use the information for unrelated independent purposes.

Service-provider use may be governed by the applicable agreement, service configuration, privacy controls, and law.

Third-Party Integrations

Customers may authorize Opti-mized to exchange Customer Facility and Operational Data with third-party systems or services.

For example, a customer may enable an integration involving:

• Utility data;
• Building systems;
• Energy platforms;
• Reporting systems;
• Communications tools;
• Customer systems;
• Other external applications.

Where an integration is enabled, information may be transmitted to or received from the third party in accordance with the functionality and permissions selected.

The third party's independent processing may be governed by its own privacy policy and terms.

Customer-Directed Sharing

Customers may instruct Opti-mized to provide information to:

• Consultants;
• Contractors;
• Installers;
• Service providers;
• Funding organizations;
• Government entities;
• Project partners;
• Other authorized recipients.

Where Opti-mized shares information at the customer's direction, the recipient's subsequent use of the information may be governed by the customer's relationship with that recipient.

Reports Shared by Customers

Customers may download, export, print, forward, or otherwise share Facility Intelligence Reports or other information obtained through Opti-mized.

Once a customer or authorized user provides information to another party outside Opti-mized-controlled systems, Opti-mized may not control how that receiving party stores, uses, or rediscloses the information.

Customers should therefore consider confidentiality and privacy requirements before sharing exported information.

Data Exports

Where functionality permits, customers may be able to download or export certain information.

Exported information may include:

• Reports;
• Facility summaries;
• Equipment information;
• Energy data;
• Analytical outputs;
• Facility Intelligence Data;
• Other available records.

Export functionality may vary by product, plan, configuration, agreement, or technical capability.

Data Portability

Where required by applicable law or provided by contract, Opti-mized may assist customers with obtaining certain data in an available format.

The scope of exportable or portable information may depend on:

• Applicable law;
• Customer agreements;
• Technical feasibility;
• Intellectual-property rights;
• Third-party rights;
• Security considerations;
• Product configuration.

Data Retrieval Following Contract Termination

Where a customer relationship ends, the customer's ability to access or retrieve Customer Facility and Operational Data may be governed by:

• The applicable customer agreement;
• Terms of service;
• Retention periods;
• Export functionality;
• Legal obligations;
• Technical limitations.

Customers should retrieve information they require before access to the service ends where applicable.

Retention After Service Termination

Customer Facility and Operational Data may not necessarily be deleted immediately when a customer account is closed or a contract ends.

Certain information may be retained for periods necessary to:

• Complete termination procedures;
• Support customer data export;
• Maintain backups;
• Comply with legal obligations;
• Maintain accounting records;
• Resolve disputes;
• Enforce agreements;
• Maintain security;
• Defend legal claims;
• Comply with retention requirements.

Retention practices are described in greater detail elsewhere in this Privacy Policy.

Deletion of Customer Data

Where applicable and subject to legal, contractual, technical, and legitimate business requirements, customers may request deletion of certain Customer Facility and Operational Data.

Deletion may be subject to exceptions where retention is required or permitted for purposes such as:

• Legal compliance;
• Security;
• Fraud prevention;
• Contract enforcement;
• Dispute resolution;
• Accounting;
• Tax obligations;
• Backup retention;
• Legal claims.

Backup Copies

Customer Facility and Operational Data may be included in backups and disaster-recovery systems.

Information removed from active systems may remain temporarily within backups until those backups are overwritten or deleted through ordinary retention processes.

Backups may be maintained for purposes such as:

• Disaster recovery;
• Business continuity;
• System restoration;
• Security;
• Data integrity.

Data Recovery

We may use backup copies of Customer Facility and Operational Data to recover information following:

• Hardware failure;
• Software failure;
• Database failure;
• Security incident;
• Accidental deletion;
• Service disruption;
• Disaster-recovery event.

Security of Customer Data

Opti-mized may use reasonable administrative, technical, organizational, and physical measures intended to protect Customer Facility and Operational Data.

Security measures may include, depending on the circumstances:

• Authentication;
• Role-based access;
• Encryption;
• Network security;
• Secure cloud infrastructure;
• Security monitoring;
• Logging;
• Access controls;
• Backup systems;
• Device security;
• Firmware security;
• Security testing;
• Incident-response procedures;
• Service-provider controls.

No security system can eliminate all risk, and security protections are discussed in more detail elsewhere in this Privacy Policy.

Segregation of Customer Data

Where appropriate, Opti-mized may use logical or technical controls intended to restrict one customer's access to another customer's identifiable information.

Customer accounts, facilities, permissions, and user roles may be configured to help limit access to authorized information.

Customer Confidentiality

Opti-mized may treat Customer Facility and Operational Data as confidential in accordance with applicable agreements and internal policies.

Confidentiality protections may apply even where the information is not personal information under privacy law.

No Public Disclosure Merely Because Data Is Processed

The fact that Customer Facility and Operational Data is processed through Opti-mized does not mean that the information becomes public.

Opti-mized does not intend to publicly disclose identifiable customer facility information merely because it appears within the Opti-mized platform.

Public Case Studies

Opti-mized may wish to publish case studies, testimonials, project summaries, or examples of customer outcomes.

Identifiable customer information used in public-facing case studies may be subject to additional approval, authorization, contractual terms, or consent where appropriate.

Using customer data internally to provide the service does not automatically authorize public marketing use.

Customer Logos and Names

The right to use customer names, trademarks, logos, photographs, project results, or identifiable facility information for marketing may be governed by separate customer agreements or permissions.

This Privacy Policy does not itself create unrestricted marketing rights in customer trademarks or branding.

Data Used for Legal Compliance

Opti-mized may retain or use Customer Facility and Operational Data where necessary to comply with legal or regulatory obligations.

This may include:

• Court orders;
• Subpoenas;
• Regulatory requests;
• Tax requirements;
• Accounting requirements;
• Recordkeeping obligations;
• Security obligations;
• Other lawful requirements.

Data Used to Protect Rights

Customer information may also be used where reasonably necessary to:

• Investigate fraud;
• Investigate misuse;
• Protect systems;
• Respond to security incidents;
• Enforce customer agreements;
• Resolve payment disputes;
• Defend legal claims;
• Protect Opti-mized's rights;
• Protect customer rights;
• Protect users or third parties.

Customer Data and Government Requests

Where legally required, Opti-mized may disclose information in response to valid requests from courts, regulators, law-enforcement agencies, or other government authorities.

Where permitted and appropriate, Opti-mized may evaluate such requests to determine whether they appear lawful and appropriately scoped.

Customer Data in Corporate Transactions

Customer Facility and Operational Data may be involved in a merger, acquisition, financing, reorganization, asset sale, sale of business, bankruptcy, or similar corporate transaction.

Any transfer or disclosure in connection with such a transaction may be subject to confidentiality, legal, contractual, and privacy requirements.

Data Minimization

Where reasonably practicable, Opti-mized may seek to process only the Customer Facility and Operational Data necessary or relevant to the applicable service or purpose.

For example:

• Technical troubleshooting may not require billing information;
• Hardware reliability analysis may not require customer contact details;
• Equipment runtime analysis may not require payment information;
• Facility setup may not require unrelated personal information.

Unnecessary Sensitive Information

Customers should avoid submitting sensitive personal information that is not required for the requested service.

For example, customers generally should not upload:

• Government identification numbers;
• Personal financial account credentials;
• Personal passwords;
• Medical information;
• Biometric information;
• Unrelated employee records;

Other sensitive personal information

unless specifically requested by Opti-mized for a lawful and necessary purpose.

Personal Information Within Facility Data

Although much Customer Facility and Operational Data concerns buildings and equipment, some facility records may contain personal information.

Examples may include:

• Contact names;
• Business email addresses;
• Phone numbers;
• Names appearing on utility bills;
• Employee names appearing on panel schedules;
• Individuals appearing in photographs;
• Technician names in installation records.

Where Customer Facility and Operational Data includes personal information, Opti-mized processes that information in accordance with applicable privacy requirements.

Non-Personal Facility Data

A significant portion of Customer Facility and Operational Data may not identify an individual.

For example:

• Electrical current;
• Equipment runtime;
• Energy consumption;
• Panel configuration;
• Gateway status;
• Equipment names;
• Equipment operating patterns;
• Demand;
• Circuit loads;
• Facility schedules.

Such information may fall outside the definition of personal information under certain laws.

Opti-mized may nevertheless apply confidentiality and security protections based on the customer relationship.

Customer Ownership Does Not Equal Personal-Information Ownership

Privacy law does not always treat personal information as property capable of being “owned” in the same manner as physical property.

Accordingly, references in this Privacy Policy to customer rights, ownership, or interests in data should be understood subject to applicable privacy, intellectual-property, confidentiality, contract, and data-protection laws.

Nothing in this Privacy Policy is intended to define legal ownership beyond what applicable law and customer agreements provide.

Intellectual Property

Opti-mized's processing of Customer Facility and Operational Data does not transfer ownership of Opti-mized technology to the customer.

Opti-mized may retain rights in its:

• Software;
• Platform;
• Algorithms;
• Analytical methods;
• Models;
• Hardware designs;
• Detection methods;
• User interfaces;
• Reports templates;
• Calculations;
• Documentation;
• Proprietary processes;
• Aggregated insights;
• De-identified analytics;
• Other intellectual property.

Customer agreements may define these rights in greater detail.

Customer Data Versus Opti-mized Technology

A customer may retain rights in its underlying data while Opti-mized retains rights in the technology used to process that data.

For example:

• The customer may retain rights in its electrical measurements;
• Opti-mized may retain rights in the algorithm used to detect an energy-loss condition from those measurements;
• The customer may retain rights in its equipment records;
• Opti-mized may retain rights in the software used to generate the dashboard;
• The customer may retain rights in its facility photographs;
• Opti-mized may retain rights in the analytical methods used to interpret those photographs.

This distinction allows customers to retain their underlying information while allowing Opti-mized to continue developing its technology.

Customer Data Used With Opti-mized Intellectual Property

To provide the service, Customer Facility and Operational Data may be processed using proprietary Opti-mized:

• Algorithms;
• Models;
• Calculations;
• Analytics;
• Detection methods;
• Software;
• Hardware;
• Reports;
• Workflows;
• Classification systems.

The use of these systems does not merge ownership of the underlying customer data with ownership of the Opti-mized technology.

Facility Intelligence Reports

Facility Intelligence Reports may contain a combination of:

• Customer-provided data;
• Measured data;
• Facility information;
• Opti-mized-generated analysis;
• Calculations;
• Graphs;
• Recommendations;
• Proprietary report structure;
• Other content.

Rights to use, reproduce, distribute, or share reports may be addressed in applicable customer agreements.

Customer Access to Facility Intelligence

Customers may access Facility Intelligence Data through available Opti-mized features, subject to:

• User permissions;
• Account status;
• Product configuration;
• Subscription terms;
• Service availability;
• Customer agreements.

Customer Use of Outputs

Customers may use Opti-mized outputs for internal business purposes as permitted under applicable agreements.

These outputs may support:

• Energy management;
• Facility planning;
• Maintenance planning;
• Retrofit decisions;
• Capital planning;
• Budgeting;
• Operational decisions;
• Reporting;
• Funding applications;
• Other facility-related activities.

No Guarantee of Accuracy

Customer Facility and Operational Data may be used to generate estimates, classifications, predictions, savings ranges, payback calculations, alerts, and other analytical outputs.

These outputs may depend on:

• Data quality;
• Sensor accuracy;
• Customer-provided information;
• Equipment mapping;
• Utility rates;
• Operating schedules;
• Historical data;
• Analytical assumptions;
• Facility conditions.

Opti-mized does not necessarily guarantee that every analytical output will perfectly reflect actual future outcomes.

Customer Review

Customers should review significant analytical results in the context of actual facility operations before making decisions that involve:

• Safety;
• Equipment shutdown;
• Maintenance;
• Capital investment;
• Retrofit implementation;
• Operational changes;
• Financial commitments.

Facility Intelligence Data is intended to support informed decision-making and should be considered together with appropriate facility-specific expertise.

Data Used for Verification

Customers may authorize Opti-mized to continue collecting information after operational or retrofit changes in order to verify results.

This may include comparing:

• Pre-change performance;
• Post-change performance;
• Runtime;
• Energy consumption;
• Demand;
• Equipment behaviour;
• Savings.

Verification data remains part of Customer Facility and Operational Data or Facility Intelligence Data as applicable.

Historical Analysis

Customer data may be retained and analyzed historically to:

• Establish baselines;
• Compare performance;
• Identify long-term trends;
• Measure changes;
• Support reports;
• Support verification;
• Detect gradual equipment changes;
• Improve customer-specific intelligence.

Reprocessing Historical Data

Opti-mized may reprocess historical Customer Facility and Operational Data using updated analytical methods where reasonably necessary to improve the customer's service.

For example, historical information may be reanalyzed to:

• Improve equipment classification;
• Improve runtime calculations;
• Improve savings estimates;
• Apply new detection methods;
• Generate improved reports.

Customer Data and New Features

Where customers gain access to new Opti-mized features, Customer Facility and Operational Data may be processed through those features where the use is reasonably related to the services and permitted under applicable agreements.

Materially different uses may be subject to additional notice or authorization where required.

Customer Data and Beta Features

Customers who voluntarily participate in beta, pilot, preview, or experimental features may authorize additional processing necessary to test and evaluate those features.

Additional terms may apply.

Customer Data and Research Participation

Customers may choose to participate in specific research or joint-development initiatives.

Where such participation involves uses beyond ordinary service delivery, Opti-mized may provide additional disclosures or obtain additional authorization where appropriate.

Customer Data and Artificial Intelligence

Opti-mized may use artificial intelligence, machine learning, algorithms, statistical methods, and other automated technologies to process Customer Facility and Operational Data where necessary to provide Opti-mized services.

This may include uses such as:

• Pattern recognition;
• Equipment classification;
• Runtime estimation;
• Document processing;
• Photo analysis;
• Energy-loss detection;
• Anomaly detection;
• Savings estimation;
• Report generation;
• Recommendation generation.

Customer-specific information may be processed by these systems to generate services for that customer.

General-Purpose AI Training

As described elsewhere in this Privacy Policy, Opti-mized does not provide identifiable customer Facility Data or identifiable customer Energy and Operational Data to unrelated third parties for the purpose of training those parties' general-purpose artificial intelligence models unless the customer specifically authorizes such use or the use is otherwise clearly disclosed and permitted by applicable law.

Data Used to Improve Opti-mized

Customer-specific information may be used where reasonably necessary to troubleshoot, maintain, secure, configure, and improve Opti-mized services for that customer.

For broader development and benchmarking, Opti-mized may use aggregated, anonymized, de-identified, statistical, synthetic, or otherwise appropriately protected information where reasonably practicable.

No Sale Merely Because Data Has Value

The fact that Customer Facility and Operational Data may have analytical or commercial value does not by itself mean that Opti-mized sells or transfers ownership of that information to unrelated parties.

Any disclosures are governed by this Privacy Policy, applicable agreements, and applicable law.

Changes in Customer Data Practices

As Opti-mized develops new hardware, software, integrations, reporting tools, analytics, and services, the manner in which Customer Facility and Operational Data is processed may evolve.

Where a material change affects the processing of personal information or customer data, Opti-mized may:

• Update this Privacy Policy;
• Provide additional notice;
• Update customer agreements;
• Obtain consent where required;
• Provide configuration options;
• Take other measures appropriate under applicable law.

Relationship With Customer Agreements

This Privacy Policy should be read together with applicable customer agreements.

Those agreements may contain additional provisions concerning:

• Data ownership;
• Confidentiality;
• Security;
• Data processing;
• Intellectual property;
• Aggregated data;
• De-identified data;
• Data retention;
• Data deletion;
• Service-provider access;
• Reporting;
• Licensing;
• Customer responsibilities;
• Opti-mized responsibilities.

Where a customer agreement provides more specific obligations concerning Customer Facility and Operational Data, those provisions may apply in addition to this Privacy Policy.

Data Processing Addenda

Certain customers may enter into a data processing addendum or similar agreement with Opti-mized.

Such agreements may establish additional requirements concerning:

• Personal information;
• Processing instructions;
• Subprocessors;
• Security;
• International transfers;
• Data-subject requests;
• Breach notification;
• Deletion;
• Audits;
• Other privacy requirements.

Where applicable, those terms supplement this Privacy Policy.

Government and Municipal Customers

Customers may include municipalities, public bodies, governmental organizations, or other public-sector entities.

These customers may be subject to additional obligations concerning:

• Public records;
• Procurement;
• Access to information;
• Records retention;
• Cybersecurity;
• Data residency;
• Confidentiality;
• Government contracting.

The treatment of customer information may therefore also be affected by the laws and contractual requirements applicable to the particular public-sector customer.

Public Records

Information supplied by or to public-sector customers may, in some jurisdictions, be subject to freedom-of-information, access-to-information, public-records, or similar laws.

Opti-mized cannot necessarily guarantee that information held by a public-sector customer will remain exempt from disclosure if that customer is legally required to produce it.

Where applicable, confidentiality designations or contractual protections may be used, but disclosure obligations ultimately depend on applicable law.

Customer Data From Contractors

A contractor, installer, consultant, or other authorized representative may submit Customer Facility and Operational Data on behalf of a customer.

Where that occurs, Opti-mized may treat the information as having been provided on behalf of the applicable customer, subject to the authority of the submitting party.

Multiple Parties With Rights in Data

Some information may involve rights or interests held by multiple parties.

For example:

• A municipality may own a facility;
• A contractor may create an electrical drawing;
• A utility may generate a bill;
• A consultant may prepare a report;
• Opti-mized may generate analytical outputs.

Nothing in this Privacy Policy is intended to determine or override the intellectual-property or contractual rights of those parties beyond what applicable law and agreements provide.

Customers Should Review Third-Party Rights

Customers should ensure that their use of third-party documents, photographs, reports, drawings, datasets, or other materials with Opti-mized is permitted.

Opti-mized's ability to process customer-provided information does not grant the customer rights that the customer does not otherwise possess.

Security Responsibilities

Protecting Customer Facility and Operational Data may involve shared responsibilities.

Opti-mized may be responsible for securing its own systems, while customers may be responsible for matters such as:

• Protecting account credentials;
• Managing authorized users;
• Maintaining secure customer networks;
• Protecting exported reports;
• Protecting downloaded data;
• Removing access for former employees;
• Maintaining secure email accounts;
• Following installation and security guidance.

Customer Passwords and Credentials

Customers and users should not share Opti-mized passwords or authentication credentials with unauthorized parties.

Customer administrators should promptly update or revoke access when a user no longer requires access.

Customer Network Security

Where Opti-mized hardware connects to a customer-provided network, the customer may be responsible for maintaining appropriate security of that network.

Opti-mized may provide technical requirements or recommendations, but customers remain responsible for their own network infrastructure unless otherwise agreed.

Exported Data Security

Once Customer Facility and Operational Data or reports are downloaded from the Opti-mized platform, customers are responsible for protecting the exported copies under their control.

For example, customers should consider:

• Who can access exported files;
• Where files are stored;
• Whether files are forwarded by email;
• Whether shared drives are secure;
• Whether reports contain sensitive facility information.

Customer Notifications

Customers may configure which users receive alerts, reports, or other notifications.

Customers should ensure that recipient information is accurate and that recipients are authorized to receive the applicable facility information.

Data Accuracy and Customer Decisions

Customers should recognize that Facility Intelligence depends in part on the quality and completeness of underlying information.

A savings estimate calculated using an incorrect utility rate may be inaccurate.

A runtime analysis based on an incorrectly mapped circuit may not accurately represent the intended equipment.

A schedule mismatch based on outdated operating hours may not represent actual energy loss.

Customers should therefore update information when relevant conditions change.

Facility Changes

Customers should update Opti-mized where appropriate if:

• Equipment is replaced;
• Circuits are reassigned;
• Panels are modified;
• Equipment schedules change;
• Facility operating hours change;
• Utility rates change;
• Hardware is moved;
• Sensors are reassigned;
• Buildings are added or removed;
• Facility use changes.

Changes in facility configuration may affect analytical results.

Equipment Replacement

Where equipment is replaced, historical information relating to the previous equipment may remain in Opti-mized records for historical comparison, reporting, or verification where appropriate.

New equipment may require updated configuration or baseline information.

Portfolio Changes

Customers managing multiple facilities may add or remove facilities over time.

Access to historical information relating to removed facilities may depend on:

• Customer settings;
• Service terms;
• Data-retention practices;
• Contract requirements.

Account Closure

When an account is closed, Opti-mized may disable customer access to the platform while retaining certain information for lawful and legitimate purposes.

Customers should review applicable terms and export required information before closure where necessary.

Mergers or Facility Transfers

If ownership or management of a facility changes, rights to facility information may need to be addressed between the outgoing and incoming customer.

Opti-mized may require appropriate authorization before transferring access to a new organization.

Customer Identity Verification

Opti-mized may require reasonable verification before:

• Providing sensitive facility information;
• Transferring account administration;
• Exporting data;
• Responding to deletion requests;
• Transferring facilities between organizations.

Verification helps protect Customer Facility and Operational Data from unauthorized disclosure.

Data Requests

Customers may contact Opti-mized with questions or requests concerning their Customer Facility and Operational Data.

Depending on applicable law, contracts, and technical capabilities, requests may include:

• Access;
• Correction;
• Export;
• Deletion;
• Restriction;
• Account changes;
• Permission changes.

Requests From Individual Users

Where a user requests access to or deletion of information that belongs to or is controlled by an organization, Opti-mized may need to coordinate with the applicable customer organization before responding.

For example, an employee may not necessarily have the authority to delete an entire municipality's facility records merely because the employee has a user account.

Customer Administrator Authority

Authorized customer administrators may have greater authority to manage:

• User accounts;
• Facility access;
• Organization settings;
• Notifications;
• Customer information;
• Other administrative functions.

Opti-mized may rely on instructions from properly authenticated customer administrators.

Data Disputes

If multiple parties dispute rights to Customer Facility and Operational Data, Opti-mized may limit access, preserve information, or require additional documentation while the dispute is resolved.

Opti-mized is not necessarily responsible for adjudicating underlying ownership disputes between customers, contractors, property owners, tenants, or other parties.

Preservation During Disputes

Information may be retained where reasonably necessary to preserve evidence or protect legal rights in connection with:

• Contract disputes;
• Ownership disputes;
• Payment disputes;
• Litigation;
• Regulatory investigations;
• Security incidents.

Compliance With Applicable Law

All processing of Customer Facility and Operational Data remains subject to applicable legal requirements.

Nothing in this section requires Opti-mized to process, retain, delete, transfer, disclose, or otherwise handle information in a manner prohibited by law.

Summary of Customer Rights and Opti-mized Processing

In general:

• Customers retain their rights and interests in the underlying facility information they provide to Opti-mized;
• Customers retain their rights and interests in underlying Energy and Operational Data generated through their facilities, subject to applicable law and agreements;
• Customers retain their rights in photographs, documents, schedules, equipment records, and other information they lawfully provide;
• Opti-mized does not claim ownership of a customer's underlying facility or operational data merely because that information is processed through Opti-mized;
• Customers authorize Opti-mized to process that information as reasonably necessary to provide the products and services;
• Opti-mized may configure facilities, panels, circuits, equipment, sensors, gateways, dashboards, and reports using customer information;
• Opti-mized may analyze customer information to generate Facility Intelligence Data;
• Opti-mized may use customer-specific information to improve services for that customer;
• Opti-mized may use aggregated, de-identified, anonymized, statistical, synthetic, or otherwise appropriately protected information for broader research, benchmarking, product development, and improvement where reasonably practicable;
• Opti-mized may use service providers to process customer information on its behalf subject to appropriate safeguards;
• Customers are responsible for ensuring they have appropriate authority to provide information to Opti-mized;
• Customers are responsible for managing access granted to their authorized users;
• Customers should maintain accurate facility and configuration information;
• Customer-specific facility information may remain confidential even where it is not considered personal information under privacy law;
• Customer data may be retained, exported, deleted, or otherwise handled in accordance with applicable agreements, retention practices, and legal requirements;
• Opti-mized retains its rights in its platform, hardware, software, algorithms, analytics, models, proprietary processes, and other intellectual property; and
• Customer agreements may contain additional or more specific provisions concerning ownership, confidentiality, security, retention, processing rights, derived data, and intellectual property.

The purpose of these provisions is to maintain a clear distinction between a customer's underlying facility and operational information and the Opti-mized technology used to collect, organize, analyze, interpret, and transform that information into Facility Intelligence.

Opti-mized's role in receiving, processing, storing, analyzing, and transforming customer information is intended to enable us to provide the products and services customers have requested, not to claim ownership of a customer's underlying facility simply because information from that facility is processed through our technology.