These are the Logic Weaver app's Terms and Conditions, reproduced here exactly as they appear in the app. How we handle your information is covered in Security & Privacy.
Last updated: September 19, 2026
1. Acceptance of Terms
By accessing and using Logic Weaver (“the Application”), you accept and agree to be bound by the terms and provisions of this agreement. If you do not agree to these terms, please do not use the Application.
2. Use License
Permission is granted to use Logic Weaver for personal or commercial PLC programming and project management purposes. This license shall automatically terminate if you violate any of these restrictions.
You may not:
- Modify or copy the application’s materials without authorization
- Use the application for any unlawful purpose
- Attempt to reverse engineer or decompile any part of the application
- Remove any copyright or proprietary notations from the application
- Transfer the application to another person or entity without proper authorization
3. Data Storage and Privacy
Logic Weaver stores your data in the cloud using Google Firebase. Data collected includes:
- Project and routine information
- Imported L5X files and their revisions
- User account information (email, display name) if you create an account
- Application settings and preferences
- AI usage metrics for billing and analytics
Your data is used solely for providing the application’s functionality. We do not sell, trade, or share your personal data with third parties except as required to operate the service.
3.1 Inactive Free Accounts
Free accounts that show no sign-in activity for more than twelve (12) consecutive months may be deleted at our discretion, together with any projects, routines, and tag data they contain. Deletion is permanent, and deleted data cannot be recovered.
Where we hold a valid email address for the account, we will make a reasonable effort to give notice before deleting it, so you have an opportunity to keep the account active. Signing in resets the inactivity period — no other action is required.
This applies to Free accounts only. Accounts on an active paid plan are not subject to inactivity deletion. Because routines are brought into a Free account by importing your own files, you retain the original copies of anything you imported; a paid plan additionally lets you export your work from Logic Weaver at any time.
4. User Responsibilities
As a user of Logic Weaver, you are responsible for:
- Maintaining the confidentiality of your account credentials
- All activities that occur under your account
- Ensuring the accuracy of the data you enter into the application
- Regularly backing up your data using the export functionality on a paid plan, or, on the Free plan, retaining the original files you imported
- Complying with all applicable laws and regulations in your use of the application
- Notifying us immediately of any unauthorized use of your account
4.1 Live Testing and Live Control (Connected Controllers)
Logic Weaver’s Live Testing features (Live monitoring and Live Control) connect Logic Weaver — through the Data Weaver companion application (formerly Logic Weaver Connect) — to a physical programmable logic controller on your own network. You use these features entirely at your own risk.
Intended use. The two halves of Live Testing have different intended uses:
- Live monitoring only reads the connected controller. It writes nothing, and it may be used with bench, test, and development equipment and to monitor a controller on an installed machine or process.
- Live Control writes to the connected controller. It is intended for test-bench, factory-test, and development equipment only — a controller that is not connected to installed machinery or a running process. It is not intended for use on an installed machine or process. If you choose to use it there, you do so outside its intended use and at your sole risk and responsibility.
Qualified people only. Live Testing is a tool for people who are trained, competent, and authorized by the equipment’s owner to work on the connected controller and the equipment it operates. You are responsible for making sure that everyone who uses it under your account or on your project is.
By arming Live Control you acknowledge and agree that:
- Writes made through Live Control take effect on the connected controller immediately, exactly as if made from vendor programming software, and may start, stop, or otherwise change the behavior of any machinery, process, or equipment that controller operates.
- A Live Control write changes the value of a tag. It is not an I/O force: the controller’s own logic, including its interlocks, keeps running and may overwrite the value on its next scan. A write can, however, change a value that operators cannot reach from the machine’s own operator interface, and so go around the checks that interface was designed with. Knowing what a tag does before writing it is your responsibility.
- Every time a project goes Live — to monitor or to control — every Live attempt refused because the project did not match the controller, every time Live Control is turned on or off, and every value written through it, is recorded with your identity, the time, the controller, the tag, and the value before and after — in Data Weaver’s audit trail on the computer it runs on, and in the project’s Live PLC record in the Project Journal, which is visible to everyone with access to the project and cannot be edited or deleted.
- The Live PLC record is kept. It is a safety and accountability record, kept so that what was written to a controller, when, and by whom can be established later. It has no expiry date, and it is kept after the project it belongs to is deleted, and after the account that created it is closed: from then on it is no longer visible to you or to other project members and can be read only by Logic Weaver’s administrators. It contains the name and email address of each person who went Live on the project or used Live Control. We use it only to establish what happened on a connected controller — for example in response to a safety incident, a dispute, or a lawful request — and you agree to it being kept for that purpose. If you need a copy of a project’s record, export it from the Project Journal before deleting the project.
- You are solely responsible for knowing what the connected controller operates before arming Live Control, for ensuring that no person or equipment can be put at risk by a tag write, and for complying with all applicable safety procedures, standards, and regulations — including lockout/tagout and machine-guarding requirements.
- Before Live starts, Logic Weaver checks that the project’s controller name and program list match what the connected controller reports, and does not start if they differ. That check cannot confirm that every routine and rung is identical: Logic Weaver cannot verify that the logic shown on screen matches the revision running in the controller. Displayed values are always the controller’s own, but the rung layout drawn is the routine open in Logic Weaver — confirming that the two match is your responsibility.
- Monitoring and control depend on your network, the companion program, and the controller itself, and the connection can be interrupted at any time. A write in flight when the connection drops (for example, the release of a held pushbutton) may not be delivered; the controller retains the last value it received.
- Live Testing is not a safety device. It must never be used as, or in place of, a safety system, an emergency stop, a safety interlock, or an operator interface for production equipment. Emergency stops and safety functions must be provided by hardwired or safety-rated means that do not depend on Logic Weaver, Data Weaver, the network, or the computer they run on.
- To the maximum extent permitted by law, Logic Weaver and its developers are not liable for any damage to equipment, product, data, or persons, nor for any downtime or loss, arising from the use of Live Testing or Live Control. The limitations of liability in Section 7 apply in full.
5. AI-Generated Content
Logic Weaver uses AI models to assist with PLC programming. While we strive for accuracy, AI-generated content may contain errors. You are responsible for reviewing and validating all AI-generated code before deploying it to production systems. Logic Weaver is not liable for any damages resulting from the use of AI-generated content without proper verification.
6. Disclaimer of Warranties
The application is provided “as is” without any warranties, expressed or implied. We do not warrant that:
- The application will meet your specific requirements
- The application will be uninterrupted, timely, secure, or error-free
- The results obtained from using the application will be accurate or reliable
- Any errors in the application will be corrected
7. Limitations of Liability
In no event shall Logic Weaver or its developers be liable for any damages (including, without limitation, damages for loss of data, business interruption, or loss of profits) arising out of the use or inability to use the application, even if we have been notified of the possibility of such damage.
8. Modifications to Terms
We reserve the right to modify these terms at any time. Changes will be effective immediately upon posting to the application. Your continued use of Logic Weaver after any changes constitutes your acceptance of the new terms.
9. Trademarks and Third-Party Rights
Studio 5000, Logix, CompactLogix, ControlLogix, RSLogix, Allen-Bradley, and Rockwell Automation are trademarks of Rockwell Automation, Inc. All other product and company names referenced in Logic Weaver are the property of their respective owners.
Logic Weaver is an independent application and is not affiliated with, endorsed by, sponsored by, or associated with Rockwell Automation, Inc. References to these trademarks are made solely for descriptive and interoperability purposes — to identify the file formats and programming environment that Logic Weaver works with. Logic Weaver operates only on L5X files that you export and own; it does not redistribute Rockwell software, firmware, or documentation.
10. AI Credits, Billing, and Payment Terms
Paid plans include an allowance of AI credits, and additional usage may be handled as described below.
- Included monthly allotment. Each paid plan includes a monthly allowance of AI credits. The monthly period is anchored to your plan’s activation date and resets at the start of each new period.
- Rollover. Credits from your included allotment that you do not use in a period carry forward to the next period, up to a maximum of one additional month’s allotment. Rollover credits are a usage allowance only: they have no cash value, are not redeemable or refundable, and are not transferable.
- Prepaid credit bank. You may arrange additional prepaid AI credits with the administrator. Prepaid bank credits are applied only after your monthly allotment and rollover are used, are non-refundable, have no cash value, and do not expire.
- Overage and back-charging. Where over-usage is enabled on your account, AI usage beyond your included allotment, rollover, and prepaid bank is recorded as an outstanding balance, up to a per-account limit. Overage is priced at the same rate as included credits (there is no additional overage surcharge). Any outstanding balance is first recovered from your subsequent unused credits; any balance not recovered in this way is billed in arrears (back-charged) and is payable within 30 days of the invoice date (net 30). You are responsible for these charges.
- Suspension of AI features. When your included allotment, rollover, prepaid bank, and any permitted overage are all used up, AI-backed features are paused until your next monthly reset (or until additional credits are added to your account). Non-AI features of your plan — such as viewing, editing, simulating, and exporting — remain available.
- Changes. Included allotments, credit rates, rollover limits, overage limits, and these billing terms may change from time to time, with notice as provided in Section 8.
11. Contact Information
If you have any questions about these Terms and Conditions, please contact us through the application’s support channels.