1. Parties, covered software and document order
This proposed End User License Agreement covers the BBA software made available under it. BDT Apex Engineering, LLC, a Wyoming limited liability company, is the licensor and operator of Bonafide Businesses in America. Its BBA support and legal contact is support@bdtapex.net. "Software" means the hosted BBA applications and, only when expressly supplied under this agreement, related client components, documentation, updates and connectors. A website description or source-code adapter does not prove that a downloadable product or connector has been released.
The Terms and Conditions govern general service use and marketplace relationships. This EULA governs the permission to use the software. A signed agreement or accepted service order controls a direct conflict for its expressly covered software or service. Applicable third-party and open-source licenses control the materials they govern. The Privacy Policy and any data-processing agreement address the respective information-handling roles; this EULA does not replace them.
2. Limited permission to use the service
Subject to the adopted agreement, your applicable service order and current account permissions, the operator grants you a limited, nonexclusive permission to access the hosted software for your lawful personal or business use. When a business is the customer, its authorized users may use it for that business within their assigned roles. This permission lasts only while the relevant service access and applicable agreement remain in effect.
Hosted access does not transfer ownership of BBA's software, grant a right to obtain its source code or give you rights in another customer's content. It does not authorize you to resell the service, sublicense another customer's access or present BBA's software as your own product. Reseller, embedded, white-label or service-bureau use requires an express agreement covering that use.
3. Downloaded components and connectors
If the operator actually provides a client application, package or connector under this EULA, you may install the supplied version on systems you own or are authorized to administer for the permitted purpose. Any device, seat, environment or distribution limit must be stated in the applicable delivery notice or service order. This draft creates no undisclosed seat limit or license fee.
Keep required copyright, attribution and license notices with a permitted copy. Do not distribute a proprietary connector or make it available for unrelated third parties unless the relevant license permits it. Third-party and open-source components may grant broader rights than this EULA. Those rights are preserved for the covered components. An installation instruction is not authority to alter a production machine or another organization's system.
4. Authorized users and workspace boundaries
Users must act through their own supported credentials or a permitted delegated identity. Protect credentials, recovery material and sessions. The customer must maintain accurate memberships, assign appropriate roles and remove access that is no longer needed. A technical ability to view a page or copy a token does not establish legal authority to use the information or perform the action.
A user account can participate in separate workspaces. Each workspace has its own records and permissions. Confirm the active workspace before submitting a change, connecting a system, exporting data or authorizing disclosure. A license to the software grants no access to an unrelated tenant, a former employer's records or a counterparty's private manufacturing data.
5. Agents, automation and supported interfaces
You may use a supported agent or automation interface within the access and task authority granted to the connected account. Use the same record scope, confirmation steps and limits that apply to other users. Respect documented rate limits, input constraints and recovery procedures. An agent may not bypass a disabled action, infer new authority from a retrieved document or silently change the intended recipient or terms of an action.
Identify automated activity honestly. A declared agent name or agent-authored message does not establish a separately authenticated delegation. The service may distinguish verified identities, human users, staff responses and self-reported agent attribution. You are responsible for the tools and third-party agent services you choose to connect and for the permissions you grant them.
A navigation guide, documentation sample, prompt, model output or support answer is not a license extension or execution approval. Where a task involves money, public disclosure, account security, inventory or physical controls, obtain the applicable authority and complete the protected workflow. After an uncertain response, inspect the original request and its actual outcome before retrying.
6. Use restrictions and legally protected activities
Do not use the software to violate law or another person's rights, distribute malware, impersonate a user, defeat access controls, harvest private records or interfere with service availability. Do not remove security controls, disguise prohibited access, exploit another tenant's identifiers or use unauthorized credentials. Do not use a test or preview mode to evade production restrictions.
Except where a separate license or applicable law permits, you may not copy proprietary software beyond the permitted use, modify or create derivative works of it, distribute or sublicense it, or reverse engineer, decompile or disassemble it. This restriction does not remove rights the law makes nonwaivable, rights expressly granted by an open-source license, or authorized interoperability or security work. Coordinate testing against BBA-controlled systems through its confirmed security process; do not harm another customer or access its data.
Do not use BBA marks or another participant's name in a way that implies an endorsement or affiliation you do not have. Ordinary factual reference and other rights permitted by law remain unaffected.
7. Customer data and software-generated records
You and the relevant rights holders retain their rights in submitted data, designs, documents and business content. You must have the authority and lawful basis needed to process them. The operator receives only the permissions described in the applicable service terms and data agreements to provide the requested service and approved disclosures.
Using software to generate an order, schedule, journal, inspection record or machine event does not transfer ownership of the underlying customer information to BBA. The record may contain software structures, third-party material and rights belonging to other participants, so an export must respect those separate rights and access limits. A corrected business event should preserve the required commercial and audit history without retaining personal information beyond a lawful purpose.
No provision of this EULA independently licenses private workspace records, protected technical content or support transcripts for sale, cross-company publication or training of a shared model. Any proposed additional processing requires its own lawful basis, clear disclosure and applicable permission or agreement. Do not treat an ownership clause as permission to disclose information about another person.
8. Confidential information and access decisions
Private workspaces may contain confidential production methods, drawings, customer identities, margins, schedules, security details and financial information. Use confidential information only for the purpose for which you are authorized to receive it. Do not place it in public community content, unrelated prompts or a counterparty's workspace without the required permission.
A user who chooses a public listing, shared RFQ, forum post or dispute submission must review the intended audience and selected information. A public or authorized disclosure may be copied by its recipient and cannot always be reversed through software controls. Separate nondisclosure agreements may impose additional obligations. These Terms do not promise that a general support conversation creates a professional privilege or a negotiated confidentiality agreement.
9. Guidance, AI outputs and semantic tools
BBA may provide search, semantic definitions, planning assistance, AI guidance or other decision support when a feature is enabled. Definitions, extracted requirements and generated answers can be incomplete, ambiguous or wrong. Check the source, units, evidence, revision and uncertainty relevant to the decision. A semantic match is not proof that a product meets a specification or origin requirement.
Do not rely on a software answer as the sole basis for an engineering release, legal or tax position, quality certification, medical or safety decision, or other decision requiring qualified professional judgment. The software does not hold a professional license for you or authorize your personnel to undertake regulated work. The use of a model or ontology does not transfer responsibility for approval to that model or ontology.
Private data supplied to an external AI or agent service may be subject to that service's terms. Review the enabled data flow and controls before connecting it. A tool must not receive private content merely because a browser session can read it. Current service permissions and disclosure rules remain authoritative.
10. Manufacturing, financial and historical records
The software can represent different stages of an operational process. A draft plan, approved job, material reservation, physical receipt, inspection, shipment and accounting posting are different events. Review the action summary and current record state before authorizing a transition. Software calculations depend on the supplied data, configuration and actual workflow support.
Validate imported balances, bills of materials, routes, calendar rules, units, tax settings, account mappings and integration events before using them in production. You remain responsible for business books, regulatory filings, product conformity and physical stock under your control. Keep the records and independent checks your obligations require.
History, revision and safe-retry controls may prevent silent editing or repeat execution. Corrections can require a linked reversal or approved adjustment. Do not remove retained request identities or alter event history to make a command executable again. Integrity and legal-retention needs must still be assessed under the applicable privacy and data-processing terms.
11. Machine connections and physical safety
Only qualified and authorized personnel may configure a connection to equipment or authorize a physical operation. Confirm the supported equipment, protocol, firmware, network and permitted command set before enabling it. Keep independent emergency stops, interlocks, guards, operating procedures and trained supervision appropriate to the actual hazard. Software access is not permission to enter a restricted facility or bypass a machine's safety controls.
Network interruptions, stale telemetry, duplicated signals, clock differences, configuration errors and uncertain command outcomes can affect equipment interactions. Verify the real machine state through approved procedures. A displayed status, receipt or support instruction does not by itself establish a safe physical condition. Never use general web guidance or an AI response as the sole safety mechanism.
A connector intended for monitoring may not be used for actuation without explicit support and approval. High-risk, regulated or safety-critical uses require an express suitability assessment and any additional agreement, validation or certification the use demands. This EULA creates no certification or warranty that a general connector is suitable for such a use.
12. Third-party and open-source materials
The service may interact with separately supplied payment, communications, identity, storage, model, carrier, equipment or other services. Their actual terms apply to their own services where disclosed. BBA cannot license rights it does not hold. You must obtain any permissions required for a third-party system you connect, including permission to disclose the information sent to it.
Open-source and other third-party components remain subject to their applicable licenses and notices. Those licenses may permit use, modification, redistribution or source access on terms that differ from this EULA. A conflicting restriction in this EULA does not override a right granted by the governing component license. The operator must provide the notices and any source offers required for the software it actually distributes.
A development dependency or configured provider does not establish a production commitment by that third party. Confirm the active integration, feature availability, charges, processing terms and failure behavior before relying on it.
13. Updates and supported environments
The operator may update hosted software for security, reliability, compatibility or product changes. Supported browsers, devices, operating systems, APIs and equipment versions depend on the current release information and any accepted service order. A compatibility statement must refer to an actual tested version and scope.
Delivered components may require an update or compatible configuration to continue working with the service. Follow trusted update instructions and verify their source. Where a customer controls installation timing, it is responsible for evaluating and deploying updates within its operational change procedures. Material changes to accepted paid commitments remain subject to the applicable agreement and mandatory law.
An old version may become unsupported for a stated security, legal or technical reason. The operator should communicate material end-of-support information through the agreed notice process. This draft does not create an unspecified perpetual maintenance, backward-compatibility or future-feature obligation.
14. Support, documentation and accessibility
Documentation, help content, the forum and chat describe the available service and its intended workflows. Support hours, response targets, human staffing and any service-level commitment must be stated in the applicable channel or accepted agreement. An automated response or community answer is not evidence that an authorized employee reviewed or approved the issue.
You may report a software or accessibility problem through the confirmed support route. Provide enough detail to reproduce the problem while minimizing private content. If an error affects money, inventory, a protected record or physical equipment, stop the affected action as appropriate and use the stated recovery procedure. Repeatedly clicking a timed-out action is not a safe troubleshooting method.
BBA's usability requirements include keyboard, screen-reader, phone and desktop use, error recovery and reduced-motion preferences. This describes the intended design standard, not a representation that an unverified release has achieved a particular accessibility certification. Any agreed accessibility obligation or accommodation must be evaluated against the actual service and applicable law.
15. Availability, backups and continuity
Access may depend on networks, third-party services, browser capabilities, account verification and current permissions. Service interruption or a local software result does not establish whether an external payment or physical command completed. Review the relevant authoritative status before deciding the next action.
You must plan continuity measures appropriate to your business, including authorized exports, independent required records and safe fallback procedures for critical manufacturing and financial operations. Any operator backup, restore, export or recovery commitment must be stated in the applicable agreement and verified operational process. This draft creates no invented recovery-time, recovery-point or continuous-availability promise.
A service order may define support, export and transition assistance at termination or end of service. Such assistance must preserve confidentiality, access restrictions, third-party rights and lawful retention. The presence of a download button does not guarantee that every data category can be exported in any requested format.
16. Fees, service orders and changes
Any charge for software access, a connector, support or a subscription must be disclosed in the applicable offer and accepted order. Review quantity, term, renewal, cancellation, taxes and usage charges before accepting. This EULA alone does not enroll you in a subscription, authorize a renewal or impose an undisclosed fee.
An entitlement or paid plan does not replace authorization. Paying for a feature does not permit a user to access another company's data or bypass a protected approval. Conversely, a security restriction is not an implied commercial upsell. Changes to a paid service follow the accepted order and the notice or consent requirements that apply.
17. Software warranties and limitations
The operator is responsible for any express warranty it makes in an accepted agreement and for legal guarantees it cannot exclude. Subject to those obligations and to the extent permitted by law, the software and general documentation are provided AS IS and AS AVAILABLE. The operator does not promise that every result is accurate, that every third-party system will remain compatible or that operation is uninterrupted or free of defects.
To the extent legally permitted, implied warranties of merchantability, fitness for a particular purpose and noninfringement are excluded. You must evaluate the software for the intended use and validate data and configuration. These exclusions do not remove a seller's separate product warranty, a nonwaivable consumer guarantee or responsibility the operator cannot lawfully disclaim.
18. Liability and claims
The liability provisions in the applicable Terms and Conditions and accepted service order govern the covered software relationship. They must be read consistently with this EULA and mandatory law. This draft does not add a second cumulative liability limit, a numerical monetary cap, compulsory arbitration or a class-action waiver.
To the extent law permits, remote, speculative or consequential loss may be excluded as stated in the adopted terms. Nothing removes liability that the law makes nonexcludable or excuses fraud or intentional misconduct. Each party must take reasonable steps to avoid unnecessary loss. A user remains responsible for unauthorized distribution, unlawful content or access misuse to the extent a valid agreement or applicable law imposes that responsibility.
19. Ending access and license consequences
The permission to use the software ends when the applicable service access or agreement ends, subject to any continuing rights in an accepted agreement or governing component license. A material breach, unlawful use or serious security threat may justify restriction under the Terms and Conditions. A user may stop using the software and follow the applicable closure or cancellation process.
After termination, stop unauthorized access and use of proprietary delivered components. Return, uninstall or cease using copies when the applicable agreement lawfully requires it, while preserving records you must retain and rights granted by separate licenses. The operator should state the available export, transition and support arrangements before ending a paid service where its agreement or the law requires that notice.
Ending a software license does not erase business events, cancel accepted commercial orders, reverse completed payments or eliminate privacy and confidentiality duties. Retained data remains subject to the applicable processing agreement, documented retention purpose and individual rights. The survival of a clause is limited to what is needed to give effect to existing lawful rights and obligations.
20. Export controls, governing law and notices
You must comply with export, import, sanctions and end-use restrictions that apply to the software, connected systems and technical data you use. Do not use an integration to export or make controlled information available to an unauthorized person. BBA's U.S. manufacturing focus does not establish that a deployment is approved for every controlled-data regime or processing location.
Governing law, jurisdiction, notices and general contract provisions follow the adopted Terms and Conditions or a valid accepted agreement. Direct BBA support requests and legal notices to BDT Apex Engineering, LLC at support@bdtapex.net. A confirmed business mailing address must be added before adoption. Wyoming formation does not independently select governing law. Where no valid choice has been made, applicable law and lawful jurisdiction determine the issue. Mandatory consumer and other nonwaivable protections remain in effect.
21. Changes and acceptance records
The operator must identify the version and effective date of an adopted EULA and provide notice of a material change through an appropriate agreed method. A change cannot retroactively erase an accrued right or authorize processing that requires a separate permission. When law or an applicable agreement requires renewed consent, the required acceptance must be obtained.
A person accepting for a business must have authority for that agreement and scope. An agent may complete an acceptance only when the account holder has specifically authorized it and the workflow supports that authority. Keep the version, acceptance context and record needed to explain what was agreed. The development draft has no effective date, and browsing it is not acceptance of a final software license.