End User License Agreement and Terms of Service.

1. Agreement and service provider

This End User License Agreement and Terms of Service (“Terms”) governs access to and use of TurtleNet, including its websites, hosted services, collectors, architecture views, reports, exports, APIs, automation, and related software (“TurtleNet”). Qvert LLC, a Texas limited liability company, operates qvert.net and provides TurtleNet as a product within the shared Qvert software family (“Qvert” or “Provider”).

By creating or using an account, authorizing an application registration, granting Microsoft permissions, connecting a tenant or subscription, or otherwise using TurtleNet, the customer and each authorized user agree to these Terms. If a separate written agreement applies, that agreement controls to the extent it expressly conflicts with these Terms.

2. Authority to accept and grant access

You represent that you are legally able to accept these Terms and have authority from the customer organization to use TurtleNet, connect the applicable Microsoft tenant, create or authorize an application registration, and grant every permission approved through Microsoft. You must not connect a tenant, subscription, account, or resource that you do not own or have explicit authority to administer.

3. Microsoft consent and permissions

TurtleNet relies on Microsoft identity and Azure interfaces. Microsoft—not TurtleNet—presents the interactive sign-in and consent experience and identifies the permissions requested. Depending on enabled features, approved permissions may allow TurtleNet to:

• identify the signed-in user and customer tenant;
• enumerate authorized tenants, subscriptions, resource groups, resources, relationships, configurations, status, and operational metadata;
• collect and retain authorized configuration evidence for topology, architecture, reporting, monitoring, change tracking, restoration planning, or troubleshooting; and
• perform configuration or deployment operations only where a feature, permission, customer instruction, and applicable workflow authorize that activity.

The Microsoft consent screen is authoritative for the permissions requested in that transaction. Customers should apply least privilege, review permissions before approval, periodically review access in Microsoft Entra, and revoke access when TurtleNet is no longer required.

4. Customer-controlled application registrations and credentials

A customer may be asked to create, own, or approve a Microsoft application registration or service principal. The customer remains responsible for tenant administration, authorized administrators, permission decisions, credential lifecycle, conditional-access policies, and prompt revocation of unnecessary or compromised access. TurtleNet does not make an administrator’s consent decision on the customer’s behalf.

Credentials, tokens, and secrets must not be placed in support messages, diagrams, exports, source repositories, or other unapproved locations. A customer must promptly notify Provider through its established support or account channel if it reasonably suspects unauthorized access.

5. License and permitted use

Subject to these Terms and any applicable commercial agreement, Provider grants the customer a limited, non-exclusive, non-transferable, non-sublicensable, revocable right for its authorized personnel to access and use TurtleNet for the customer’s internal business, architecture, administration, security, reporting, planning, and operational purposes during the applicable service term.

No ownership interest in TurtleNet is transferred. Rights not expressly granted are reserved by Provider and its licensors.

6. Customer Data and instructions

As between the parties, the customer retains its rights in information supplied to or collected through the customer-authorized connection (“Customer Data”). The customer instructs Provider to process Customer Data as necessary to operate, secure, support, and improve TurtleNet; produce customer-requested maps, reports, exports, and actions; comply with documented instructions; and satisfy applicable legal obligations.

The customer is responsible for the legality, accuracy, quality, and authorization of Customer Data and instructions, including whether the customer has provided required notices or obtained required approvals from its users, employees, contractors, clients, or other affected parties.

7. Configuration changes and customer review

Architecture recommendations, generated configurations, scripts, deployment plans, restoration plans, cost estimates, security observations, and automated outputs may be incomplete, delayed, or incorrect. They are decision-support materials, not a substitute for qualified review. The customer is responsible for reviewing scope, dependencies, impact, rollback capability, authorization, and backups before applying a change.

Where TurtleNet offers an action capable of changing a customer environment, the customer remains responsible for the instruction to execute that action and for the resulting business and technical consequences, except to the extent a separate written agreement expressly assigns responsibility otherwise.

8. Pre-release and evolving functionality

TurtleNet is currently pre-release software under active development. Features, interfaces, data models, collectors, outputs, availability, and performance may change. Functions may contain defects or may be suspended, replaced, or removed. Pre-release functionality should not be the customer’s only record, backup, disaster-recovery mechanism, security control, monitoring system, or basis for an irreversible production change.

9. Acceptable use

You must not use TurtleNet to violate law or third-party rights; access systems without authorization; distribute malware; evade security controls; interfere with service operation; conduct abusive scanning against third parties; misrepresent identity or authority; extract credentials; or attempt to obtain Customer Data belonging to another customer. Authorized security testing must remain within the tester’s documented scope and applicable law.

You must not resell, sublicense, copy, reverse engineer, or create derivative works from TurtleNet except where applicable law prohibits that restriction or a written agreement expressly permits the activity.

10. Security

Provider will use reasonable administrative, technical, and organizational safeguards appropriate to the service’s nature and pre-release status. No internet-connected system is completely secure. Provider does not guarantee that TurtleNet will prevent every compromise, detect every condition, remain continuously available, or be free from vulnerabilities. Customers remain responsible for their own identity controls, tenant security, backups, incident response, business continuity, and independent validation of important outputs.

11. Privacy

Provider’s processing of personal information is described in the TurtleNet Privacy Statement. By using TurtleNet, you acknowledge that statement. The customer remains responsible for its own privacy notices and obligations concerning Customer Data.

12. Third-party services

TurtleNet interoperates with Microsoft Entra, Microsoft Azure, and other third-party services. Those services are governed by their providers’ agreements and may change independently. Provider is not responsible for third-party outages, changes, data, security, pricing, permission behavior, or service decisions, but will use reasonable efforts to identify material dependencies affecting TurtleNet.

13. Availability, support, and modifications

Unless a separate written agreement states otherwise, TurtleNet is provided without a guaranteed service level, response time, recovery objective, or uninterrupted availability. Provider may modify or suspend the service to maintain security, integrity, legal compliance, or operability. Provider will use reasonable efforts to avoid unnecessary disruption.

14. Intellectual property and feedback

TurtleNet, its software, visual designs, documentation, models, and service technology are owned by Provider or its licensors. Customer Data remains subject to Section 6. If you voluntarily provide feedback, you grant Provider a worldwide, perpetual, irrevocable, royalty-free right to use that feedback without identifying you or disclosing Customer Confidential Information.

15. Confidentiality

Each party will use reasonable care to protect non-public information disclosed by the other that a reasonable person would understand to be confidential and will use it only for the relationship contemplated by these Terms. This obligation does not apply to information lawfully known without restriction, independently developed, publicly available without breach, or lawfully obtained from another source. Legally compelled disclosure is permitted, subject to notice where lawful and reasonably practicable.

16. Disclaimers

TO THE MAXIMUM EXTENT PERMITTED BY LAW, TURTLENET AND ALL PRE-RELEASE FEATURES, OUTPUTS, RECOMMENDATIONS, AND DOCUMENTATION ARE PROVIDED “AS IS” AND “AS AVAILABLE.” PROVIDER DISCLAIMS IMPLIED WARRANTIES, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY, AND QUIET ENJOYMENT. PROVIDER DOES NOT WARRANT THAT OUTPUTS ARE COMPLETE, CURRENT, ERROR-FREE, OR SUITABLE FOR A PARTICULAR PRODUCTION DECISION.

17. Limitation of liability

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PARTY WILL BE LIABLE UNDER THESE TERMS FOR INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, PUNITIVE, OR CONSEQUENTIAL DAMAGES, OR FOR LOST PROFITS, REVENUE, BUSINESS, GOODWILL, OR DATA, EVEN IF ADVISED OF THE POSSIBILITY. PROVIDER’S AGGREGATE LIABILITY ARISING FROM TURTLENET WILL NOT EXCEED THE AMOUNTS PAID OR PAYABLE FOR TURTLENET DURING THE TWELVE MONTHS BEFORE THE EVENT GIVING RISE TO LIABILITY; IF NO AMOUNT WAS PAID OR PAYABLE, THE CAP IS ONE HUNDRED U.S. DOLLARS.

These exclusions and limits do not apply where prohibited by law and do not limit obligations expressly stated in a separate written agreement. They are an essential allocation of risk for a pre-release service.

18. Indemnification

To the extent permitted by law, the customer will defend and indemnify Provider and its personnel against third-party claims, damages, and reasonable costs arising from the customer’s unlawful or unauthorized use of TurtleNet, Customer Data, instructions, or breach of Sections 2 or 9. Provider will promptly notify the customer of a covered claim and reasonably cooperate in the defense. The customer may not settle a claim in a way that admits fault by or imposes non-monetary obligations on Provider without Provider’s written consent.

19. Suspension and termination

Provider may suspend or terminate access when reasonably necessary to address a security threat, unlawful use, material breach, nonpayment under an applicable agreement, risk to another customer, or material harm to the service. The customer may stop using TurtleNet and revoke Microsoft consent at any time. Termination does not eliminate obligations that by their nature should survive, including payment, confidentiality, ownership, disclaimers, indemnification, and liability limitations.

20. Compliance

Each party is responsible for laws applicable to its own conduct. You must comply with export-control, sanctions, anti-corruption, privacy, computer-access, and industry-specific requirements applicable to your use. TurtleNet is not designed to independently satisfy a customer’s regulatory obligations.

21. Governing terms and disputes

The governing law, venue, and dispute procedure stated in the applicable order form, statement of work, subscription, or master service agreement control. If none is stated, Texas law governs, without regard to conflict-of-law rules, and proceedings must be brought in a state or federal court with jurisdiction where Qvert LLC maintains its principal place of business, to the extent permitted by law.

22. Changes to these Terms

Provider may update these Terms as TurtleNet changes. The effective date will be updated, and material changes will be communicated through the service or the customer’s established business channel when reasonably practicable. Continued use after updated Terms take effect constitutes acceptance, except where law or a separate agreement requires another process.

23. General

Neither party may assign these Terms without the other party’s consent, except in connection with a merger, acquisition, corporate reorganization, or sale of substantially all relevant assets. If any provision is unenforceable, it will be limited to the minimum extent necessary and the remainder will continue in effect. A failure to enforce a provision is not a waiver. These Terms and any incorporated written agreement constitute the entire agreement on their subject matter, and headings are for convenience only.

24. Contact

Questions, legal notices, and security reports should be directed through the TurtleNet support or account contact identified in the customer’s agreement, or by email to jmarshall@qvert.net. Do not send passwords, tokens, private keys, or other credentials by email.