1.Authorization

The Client (as defined in the Order Form or, if no Order Form is in effect, as identified by signature below) authorizes SlabOS LLC, an Illinois limited liability company (“Provider”), to access the Client's existing fabrication software account — including without limitation Moraware, CounterGo, and comparable third-party platforms (the “Source System”) — solely for the purpose of migrating the Client's business data to a dedicated SlabOS tenant.

2.Credential Handover & Password Rotation

2.1 · Temporary admin credential

The Client will supply Provider with credentials to a single administrator-level account on the Source System. The Client retains all other credentials.

2.2 · Pre-handover password rotation

Before delivering credentials to Provider, the Client will rotate the password on the administrator account to a value used only for the migration window. This isolates the migration credential from any password the Client uses elsewhere.

2.3 · Secure transmission

Credentials are transmitted through a Provider-supplied secure channel (encrypted secret-link, password manager share, or other mutually-agreed method). Credentials sent by plain email are accepted only with the Client's written acknowledgment of the risk.

2.4 · Post-migration rotation

Within 24 hours of the migration window closing, the Client will rotate the administrator password again to a value Provider has never seen, terminating any further access. Provider will, in parallel, purge the temporary credential from its credential store and confirm in writing.

3.Scope of Access

3.1 · What Provider does

• Authenticates to the Source System using the supplied administrator credential.
• Extracts copies of accounts, jobs, quotes, drawings, price lists, slab inventory, calendar/activities, contacts, attachments, and associated addresses — the full record set required for an accurate migration.
• Loads the extracted data into a dedicated SlabOS tenant assigned to the Client.
• Runs the migration multiple times as required — successive verification passes that re-extract the source data, compare it against the SlabOS tenant, identify any deltas or mismatches, and back-fill missing records until the two systems reconcile.
• May write minimal technical metadata to the Source System (such as export markers, sync timestamps, or progress flags) where the Source System requires it to track migration state across passes. Business records (accounts, jobs, quotes, financial data) are not altered.
• Issues a written verification report at the end of the migration window confirming record counts and the final pass's deltas.

3.2 · What Provider does not do

• Provider will not destroy, archive, or maliciously alter any business record on the Source System.
• Provider will not modify financial data, customer-account details, pricing rules, or invoicing records on the Source System.
• Provider will not change account, user, or permission settings on the Source System beyond the credential rotation described in Section 2.
• Provider will not use the administrator account to log into linked third-party services, even if the credentials would technically permit it.
• Provider will not use Source System data outside the explicit migration purpose, and will not share it with any third party.

3.3 · Existing subscription remains active

The Client's existing subscription to the Source System remains in force, billed by the Source System vendor, throughout the migration. Provider does not contact, modify, or cancel the Source System subscription on the Client's behalf.

4.Security & Handling

4.1 · Tenant isolation

Migrated data lands in a dedicated SlabOS tenant. Tenant data is logically isolated at every layer (database row scoping, application authorization, audit logging) so that no other SlabOS customer can ever query the Client's records.

4.2 · Encryption

All data is transmitted over TLS 1.2 or later and stored encrypted at rest. Passwords belonging to migrated users are not extracted — users will set new credentials directly within SlabOS.

4.3 · Access log

Every API call and database read performed under the migration credential is logged with timestamp, source IP, and operation type. The log is preserved for 12 months and is available to the Client on written request.

4.4 · Pricing & commercial data — absolute confidentiality

The Client's price lists, customer pricing rules, margin data, vendor agreements, and any other commercially-sensitive information are treated as the Client's confidential information. Provider will never:

• Share, expose, or disclose the Client's pricing to any other SlabOS customer, prospect, or third party.
• Use the Client's pricing data to train any model, algorithm, or product feature visible to other customers.
• Reference the Client's specific rates, margins, or supplier discounts in any external communication.

Aggregate, anonymized industry benchmarks derived from many customers may be used internally for product development — never in a form that identifies the Client or reconstructs specific rates.

5.Trial & Deletion Terms

5.1 · 3-business-day side-by-side trial

Following migration, the Client receives login credentials for the new SlabOS tenant and operates both platforms in parallel for three (3) business days. The Source System is unaffected throughout.

5.2 · If the Client proceeds

The Client signs the SlabOS Master Subscription Agreement and Order Form, and transitions off the Source System at its own pace. Migrated data is retained per the MSA.

5.3 · If the Client does not proceed

Provider permanently deletes all migrated data — including backups, snapshots, and any working copies — within 24 hours of the Client's written notice of non-proceeding. Provider supplies written certification of deletion within 48 hours.

6.Client Representations

By signing below, the Client represents that:

1. They are an authorized representative of the Client entity with authority to grant the access described in this document.
2. They own or are licensed to access all data being migrated, and the Source System vendor's terms of service permit the Client to grant a third party temporary access for migration purposes.
3. They have rotated the Source System administrator password as described in Section 2.2 before transmitting credentials to Provider.
4. The credentials supplied are functional and valid for the duration of the migration window.

7.Term & Termination

This authorization is effective on the signature date and terminates on the earlier of: (a) completion of the migration as confirmed in writing by Provider, (b) twenty (20) business days after the signature date, or (c) written revocation by the Client. Sections 4.4 (Pricing Confidentiality), 5.3 (Deletion), and 9 (Liability) survive termination.

8.Indemnification

Provider indemnifies the Client against any third-party claim arising from Provider's misuse of the migration credentials or breach of Section 3.2 (Scope of Access). The Client indemnifies Provider against any claim by the Source System vendor that the Client lacked authority to grant the access described herein.

9.Limitation of Liability

Provider's aggregate liability under this document is limited to $25,000. Neither party is liable for indirect, consequential, special, or punitive damages. The limitation does not apply to indemnification obligations, gross negligence, or willful misconduct.

10.Governing Law

This authorization is governed by the laws of the State of Illinois, USA. Any dispute arising from or related to this document will be resolved by binding arbitration in Chicago, Illinois under the AAA Commercial Rules, except that either party may seek injunctive relief in any court of competent jurisdiction.

11.General

This document constitutes the entire understanding regarding the Source System migration. It may be executed in counterparts and via electronic signature. If any provision is held unenforceable, the remainder remains in effect.