Skip to content
LimestoneGovPublic Sector Software

Legal

Master Services Agreement

The Agreement referenced on every LimestoneGov invoice and Service Order — governing the platform, implementation, hosting, support, and AI-enabled functions ordered by public-sector customers.

Provider

Limestone Technology Group

Form

LimestoneGov - public sector

Version

v1.9.17 — October 14, 2026

Governing law

As stated in the applicable Service Order

Agreement
Contents

This Agreement governs the platform, applications, implementation, hosting, support, and AI-enabled functions ordered by public-sector customers. Product scope and pricing are stated in executed Service Orders.

This Master Services Agreement (the "Agreement") is between Limestone Technology Group, 101 W Broadway Ave., Suite 280, Maryville, TN 37801 ("Provider"), and the customer identified on the first executed Service Order that references this Agreement ("Customer"). Each may be a "Party" and together the "Parties." The Effective Date is the date of the first executed Service Order.

LimestoneGov is a division and trade name of Limestone Technology Group. Limestone Technology Group is the contracting party and is responsible for performance.

DocumentVersionWhat it governs
Master Services Agreement - LimestoneGovv1.9.17Legal, operational, service-level, and data terms
Service Order (Invoice and Service Authorization, Quote, or Statement of Work)Initial engagement or added ModuleExecuted Service Order: Products, Modules, users, fees, term, scope, and deployment name
AddendumWhen neededRegulated data, special security, or expressly negotiated terms
Later billing invoicePer billing eventBilling only: invoice number, date, itemized fees, taxes, and due date
Core termsSchedules
1-4 Definitions, orders, responsibilities, and paymentB Availability, support priorities, and service credits
5-8 Term, license, Customer Data, and AI-enabled functionsC Security, incidents, subprocessors, data, and AI safeguards
9-14 Branding, confidentiality, warranties, indemnity, and liabilityService Orders identify the purchased products and commercial terms
15-24 Termination, compliance, disputes, and general termsAddenda apply only when signed and specifically incorporated

If documents conflict, the order is: (1) a signed amendment that identifies the provision changed; (2) an executed Service Order, only for its commercial terms or an express modification; (3) this Agreement; (4) Schedule C; (5) Schedule B; and (6) a later billing invoice. A later billing invoice is for billing purposes only, does not require signature, does not modify the Parties' agreement, and is subordinate to the applicable executed Service Order and this Agreement.

1. Definitions

Platform means the shared Limestone infrastructure used for identity, tenancy, hosting, monitoring, backup, security operations, and support. Module means a discrete Limestone application identified in a Service Order. Products are the Platform and ordered Modules. Products, documentation, implementation, and support are the Service. Authorized Users are Customer personnel and contractors approved to use the Service. Service Order means an ordering document that references this Agreement and states the purchased Products, scope, users, fees, and term, including an Invoice and Service Authorization, Quote, or Statement of Work. A Service Order is executed when Customer either (a) signs it, including by electronic signature, or (b) approves it in writing by email from an authorized representative of Customer that identifies the Service Order by number or date. Provider’s issuance of the Service Order constitutes Provider’s execution.

1.1. Licensed Users and Participants

A Licensed User is a named Authorized User authorized to access a Module under a paid seat in a Service Order. Licensed Users typically perform work within a Module, including resolving, administering, configuring, approving, or reporting. Licensed User seats are counted per Module and are the licensed unit. A Participant is an Authorized User who submits requests, supplies information, takes part in a process, and views the status and records of the Participant's own submissions. Participant access is unlimited and carries no seat charge unless a Service Order states otherwise.

2. Services, orders, and access

Provider will configure, host, support, and make the ordered Products available as stated in each Service Order. Customer will provide timely access to personnel, information, sample records, workflows, and decisions needed for implementation. Material scope changes require a written change order, which Customer may sign or approve by email in the same manner as a Service Order under Section 1. Customer may permit only Authorized Users to access the Service, is responsible for their compliance, and will not allow named accounts to be shared. Provider may improve security, reliability, or functionality so long as it does not materially reduce the core purchased functionality during the current term.

3. Customer responsibilities

Customer will use the Service lawfully and for its internal operations; maintain accurate user and contact information; promptly disable departed users; safeguard credentials; not reverse engineer, resell, sublicense, interfere with, or attempt unauthorized access; ensure Customer Data is accurate, lawfully collected, and appropriate for processing; maintain its own internet access, endpoint security, identity controls, and business-continuity procedures; and not enable access to an unlicensed Module. Customer will also identify its contracting authority, procurement contact, and any legally required purchase-order or appropriation reference on the applicable Service Order.

4. Fees, taxes, and payment

Customer will pay the fees in each Service Order and later billing invoice. Unless an invoice states another due date, payment is due thirty (30) calendar days after Customer receives the invoice. Customer must provide written notice of any good-faith dispute within ten (10) business days after receipt, identifying the disputed amount and the basis for the dispute. Undisputed amounts remain due as stated. Undisputed overdue amounts may accrue interest at the lesser of 1.0% per month or the maximum rate permitted by applicable law. Provider will give at least ten (10) days' written notice before suspension for nonpayment. Customer will reimburse Provider's reasonable costs of collection, including attorneys' fees, for undisputed amounts more than thirty (30) days overdue. Fees exclude sales, use, and similar transaction taxes. Customer is responsible for taxes properly imposed on the transaction, excluding taxes on Provider's net income, and will provide any valid exemption or direct-pay certificate before payment is due. Invoices issued after the applicable executed Service Order are for billing purposes only. They do not require signature, do not modify the terms stated in the Service Order, and are subordinate to that Service Order and this Agreement. If a later invoice conflicts with the Service Order, the Service Order controls.

4.1. Seat additions

Each Service Order states an included Licensed User count and a per-seat rate for each Module. Customer may add Licensed User seats at any time on written request from a contact identified in the applicable Service Order; no new Service Order is required for seat additions alone. Added seats are billed at the per-seat rate stated in that Service Order, prorated from the first day of the calendar month in which the seat is activated through the end of the then-current service term, and co-terminate with that term. Provider will invoice seat additions on the next regular invoice for the affected Module, except that Provider may invoice separately where the prorated amount exceeds two hundred fifty dollars ($250). At renewal, the active Licensed User count for each Module becomes the baseline for the renewal term. Participant counts are not metered.

4.2. Seat reductions

Licensed User seats may not be reduced during a service term, and no credit or refund is issued for a seat deactivated mid-term. Customer may reduce its Licensed User count effective at renewal by written notice given at least sixty (60) days before the end of the then-current service term.

4.3. Additional Modules

Additional Modules purchased during a service term require a new executed Service Order. Fees for an added Module are prorated from the first day of the calendar month in which the Module is activated through the end of the then-current service term, and the added Module co-terminates with that term. Implementation fees for an added Module are not prorated and are invoiced in full.

Commercial control. A no-charge line is included only for the stated term and condition. It is not a waiver of Provider's standard rates for another term, Product, Module, or customer.

5. Term, renewal, and add-on orders

This Agreement continues until all Service Orders expire or are terminated. Each Service Order states its initial term. A Service Order renews only through a written renewal or extension that Customer signs or approves by email from an authorized representative, in the same manner as a Service Order under Section 1, unless that Service Order expressly permits another legally valid method. If Customer's governing body does not appropriate funds for a future fiscal period, Customer may terminate the affected future period on prompt written notice with reasonable evidence of non-appropriation. Fees earned or incurred through the termination date remain due, and completed or committed implementation fees are not refundable. Seat additions are governed by Section 4 and do not require a new Service Order. Additional Modules are governed by Section 4.3.

6. Provider technology and license

Provider and its licensors retain all rights in the Platform and Modules, source and object code, architecture, models, prompts, templates, workflows, documentation, know-how, generic configurations, and improvements (collectively, Provider Technology). During an active paid term, Provider grants Customer a limited, nonexclusive, nontransferable right for Authorized Users to access the ordered Modules for Customer's internal operations. No source-code rights or ownership transfer. Provider may use voluntary feedback without restriction if it does not identify Customer or disclose Customer Confidential Information.

7. Customer Data

Customer retains all rights in data, text, records, attachments, instructions, and other content submitted by or for Customer (Customer Data). Customer authorizes Provider and its subprocessors to process Customer Data only as reasonably necessary to provide, secure, support, and improve the Service, comply with law, and enforce this Agreement. Provider may use aggregated and deidentified statistics that do not identify Customer, an individual, or Customer Confidential Information.

8. AI-enabled functions

AI features may classify, summarize, retrieve, draft, recommend, or otherwise assist with operations. AI output can be incomplete or incorrect and does not replace qualified human judgment. Customer is responsible for human review before relying on AI output for material operational, safety, legal, employment, financial, or regulated decisions. Provider will not knowingly use Customer Data to train a generally available model without Customer's prior written consent. An AI Usage Allowance is a commercial allowance, not a fixed number of tokens, calls, or outputs. When technically practicable, Provider will notify Customer near 75% and 90% usage. Provider will not impose overage charges without written authorization. If the allowance is exhausted and more usage is not authorized, Provider may notify Customer and rate-limit or temporarily suspend AI-enabled features without incurring additional third-party AI charges; Provider will use reasonable efforts to keep non-AI core functions available and will restore AI features after usage is authorized or a new allowance begins. Unused allowance expires at term-end and is not refundable or transferable.

9. Deployment branding and marks

Customer may apply an approved deployment name, logo, colors, or domain when stated in a Service Order and grants Provider a limited license to display those materials only to deliver and support the Service. Customer owns its supplied marks; Provider owns Limestone names and marks. Any in-product attribution will be stated in the Service Order. Provider may not use Customer's name or logo for external marketing without Customer's prior written consent.

10. Confidentiality

Each Party will protect nonpublic information that is marked confidential or reasonably understood to be confidential, use it only for this Agreement, and disclose it only to personnel and contractors who need it and have confidentiality duties. Exclusions apply to information independently developed, rightfully received without restriction, publicly available without breach, or previously known without restriction. Customer's duties are subject to applicable public-records and open-meetings laws. When lawful, Customer will give Provider prompt notice of a request for Provider Confidential Information and reasonable opportunity to seek protection. Confidentiality duties last five (5) years after disclosure; trade-secret duties last while the information remains a trade secret.

11. Security and privacy

Provider will maintain the safeguards in Schedule C. Each Party will comply with privacy and security laws applicable to its own activities. Customer will not submit regulated or specially protected data, including protected health information, payment-card data, criminal-justice information, tax information subject to special safeguards, or government-classified information, unless the Parties first complete a written assessment, sign any required addendum, and confirm the Service is configured for that data. Provider may suspend the affected workflow immediately on written notice when needed to prevent material security or legal harm.

12. Service warranty and disclaimers

Provider warrants that implementation and support will be performed in a professional and workmanlike manner and that the Service will materially conform to the functionality stated in the applicable Service Order under normal authorized use. Customer must report a claimed breach with reasonable detail within thirty (30) days after the affected service. Provider's obligation and Customer's exclusive remedy are to reperform or correct the affected service; if Provider cannot do so after reasonable efforts, Customer may terminate the affected Module and receive a prorated refund of prepaid, unused recurring fees for that Module. Except for those express commitments, the Service and AI output are provided "as is" and "as available." To the maximum extent permitted by law, Provider disclaims implied warranties of merchantability, fitness for a particular purpose, title, noninfringement, and warranties arising from course of dealing or usage. Provider does not promise uninterrupted or error-free operation or accurate AI output. This disclaimer does not reduce Schedule B.

13.1. Provider IP indemnity

Provider will defend Customer against a third-party claim that Customer's authorized use of the unmodified Service infringes a United States patent, copyright, or trademark, and will pay damages finally awarded or agreed in settlement. Provider may modify or replace the affected Module, obtain continued-use rights, or terminate the affected Module and refund prepaid unused recurring fees. This does not apply to claims arising from Customer Data, a Customer-supplied mark, unauthorized use, third-party combinations not supplied by Provider, or Customer specifications.

13.2. Customer indemnity

To the extent permitted by applicable law and without waiving any immunity, Customer will defend Provider against a third-party claim arising from Customer Data, a Customer-supplied mark, Customer's violation of law, or Customer's material breach of this Agreement, and will pay damages finally awarded or agreed in settlement.

13.3. Indemnity process

The indemnified Party must promptly notify the indemnifying Party, provide reasonable cooperation at the indemnifying Party's expense, and allow control of the defense and settlement. No settlement may admit fault by or impose a nonmonetary obligation on the indemnified Party without written consent.

13.4. AI-output claims

Customer will defend and indemnify Provider against any third-party claim arising from Customer's reliance on, publication of, or action taken on AI-assisted output without the human review required by Section 8 and Schedule C5, and will pay damages finally awarded or agreed in settlement. This obligation is not subject to the caps in Section 14. All provisions apply only to the extent enforceable against a governmental entity, and nothing waives a statutory or common-law immunity.

14.1. General cap and damages waiver

To the maximum extent permitted by law, neither Party is liable for indirect, incidental, special, exemplary, punitive, or consequential damages, or for lost profits, revenues, goodwill, or data, even if advised of the possibility. Except as stated in Section 14.2, each Party's aggregate liability arising from this Agreement will not exceed the recurring fees actually paid by Customer for the twelve (12)-month service term in which the event giving rise to the claim occurred. The implementation fee and any AI Usage Allowance are excluded from this cap. All provisions apply only to the extent enforceable against a governmental entity, and nothing waives a statutory or common-law immunity.

14.2. Special caps and exclusions

Provider's aggregate liability under Section 13.1 will not exceed three (3) times the recurring fees paid for the service term in which the event occurred. Customer's obligations under Sections 13.2 and 13.4, and liability arising from unauthorized user access, security or privacy violations, prohibited data, AI-safeguard violations, or unauthorized use or misappropriation of Provider Technology, are not subject to a cap. The caps do not limit Customer's payment obligations or either Party's liability for gross negligence, willful misconduct, fraud, or liability that cannot legally be limited. All provisions apply only to the extent enforceable against a governmental entity, and nothing waives a statutory or common-law immunity.

14.3. Limitation of actions

No claim under this Agreement may be brought more than twelve (12) months after the claiming Party knew or reasonably should have known of the facts giving rise to it, except a claim for nonpayment or where applicable law prohibits that limitation.

15. Suspension, termination, and data return

Either Party may terminate for a material breach not cured within thirty (30) days after written notice. Provider may suspend sooner when reasonably necessary to prevent material security harm, unlawful use, prohibited data processing, or after the nonpayment notice in Section 4. Provider will limit and promptly lift a suspension when the cause is resolved. At expiration or termination, access ends. At Customer's written request at any time before deletion, Provider will make one commercially reasonable export of Customer Data available in a commonly used format. Provider will not delete Customer Data earlier than sixty (60) days after expiration or termination unless Customer requests earlier deletion or law requires otherwise. Backup copies may remain until overwritten in ordinary retention cycles. Accrued payment obligations remain due. Sections 3, 4, 5, 6, 8, 11, 12, 13, 14, 21, 22, and 23 survive, together with provisions that by nature should survive.

16. Publicity and marks

Neither Party may use the other Party's name, logo, testimonial, or engagement details in external marketing, a case study, or a press release without prior written consent. Factual disclosures required by law or procurement rules are permitted.

17. Compliance with law

Each Party will comply with laws applicable to its own performance. Customer is responsible for the legality of its instructions, Customer Data, access approvals, and use of outputs. Provider is not Customer's legal, tax, regulatory, employment, or safety advisor.

18. Notices

Legal notices must be in writing and delivered by personal delivery, nationally recognized overnight courier, certified mail, or email followed by one of those physical methods. Notices go to the addresses in the applicable Service Order unless updated by written notice. Operational support may use the designated support channel.

19. Governing law and disputes

The governing law and venue stated in the applicable Service Order control. If the Service Order is silent and legally permissible, Tennessee law governs and state and federal courts in Blount County, Tennessee have jurisdiction. Before filing suit, executives will meet in good faith within ten (10) business days after written escalation, except for reasonably necessary immediate injunctive relief. Nothing waives Customer's immunity, statutory defenses, notice requirements, or limits imposed by law.

20. Force majeure

A Force Majeure Event is beyond a Party's reasonable control, including natural disaster, fire, flood, epidemic, war, terrorism, civil disorder, labor disruption not limited to the affected Party's workforce, widespread internet or utility failure, government action, or critical third-party platform failure despite reasonable contingency measures. The affected Party will promptly notify the other, mitigate, and resume performance. Payment obligations are not excused. If the event materially prevents an affected Service for more than thirty (30) consecutive days, either Party may terminate that Service on written notice. Fees invoiced or accrued before termination remain due, and implementation fees are not refundable.

21. Insurance

During the term, Provider will maintain workers' compensation coverage as required by law and commercial general liability insurance. Provider will furnish a certificate of that coverage on reasonable written request. Insurance does not expand Provider's liability under Section 14.

22.1. Public-sector records, authority, and accessibility

Customer will identify in the applicable Service Order or signed addendum the Customer's adopted records-retention schedule and any mandatory audit, accessibility, security, procurement, or public-records requirements applicable to the Service. Provider will retain and dispose of Customer Data and responsive Service records in accordance with that identified schedule and applicable law, subject to the data-return framework in Section 15 and any technical limitation disclosed before the Service Order is executed. Provider will reasonably cooperate with lawful audit and records requests relating to the Service, subject to confidentiality, security, privilege, and reasonable cost protections. Each person who signs or approves a Service Order on behalf of a Party represents that the person has authority to bind that Party. Customer's obligations are limited by applicable law; no term creates a pledge of future appropriations or waives governmental immunity.

22.2. Conditional statutory certifications

To the extent applicable to Provider and the Service under a Service Order, Provider certifies that it will comply with the Tennessee Lawful Employment Act, including E-Verify requirements when required; is not identified on the applicable Tennessee list of persons engaged in investment activities in Iran; and will not, for the duration of the applicable Service Order, engage in a boycott of Israel as defined by and subject to the exceptions in applicable Tennessee law. Customer may require separate signed statutory certification forms as part of its procurement process. Those forms do not modify this Agreement unless signed by both Parties as an amendment.

23. General terms

Neither Party may assign this Agreement without the other's consent, except to an affiliate or with a merger, reorganization, or sale of substantially all relevant assets, with notice and assumption of obligations. The Parties are independent contractors. There are no third-party beneficiaries. If a provision is unenforceable, it will be narrowed to the minimum extent necessary and the remainder continues. No failure or delay in exercising a right is a waiver.

24. Entire agreement

This Agreement, its Schedules, signed addenda, and executed Service Orders are the entire agreement about the Service and supersede prior proposals and discussions on the same subject. Amendments and waivers must be signed by authorized representatives. A later master form does not change an executed Service Order unless the Parties sign an amendment adopting it. Counterparts and electronic signatures are permitted. Customer purchase orders, portals, vendor-onboarding forms, and unsigned billing documents do not modify this Agreement unless an authorized Provider representative expressly signs a document stating the modification. A Customer purchase order may be issued for Customer’s internal processing and may be referenced on a Service Order, but a purchase order does not by itself execute a Service Order, and any preprinted or additional terms in the purchase order do not apply.

The Master Agreement is executed once. Products, Modules, implementation scope, users, fees, terms, deployment names, and customer-specific compliance commitments are added through executed Service Orders and signed addenda.

Schedule B

Service Level Agreement

B1. Monthly availability objective

Provider targets 99.5% Monthly Availability for the production Service. Monthly Availability equals (total minutes in the month minus Unavailable minutes) divided by total minutes in the month, multiplied by 100. Unavailable means the production Service cannot accept authenticated user requests because of a failure within Provider's reasonable control. Intermittent slowness or failure of one feature is not Unavailable unless it materially prevents substantially all normal activity in an affected Module.

B2. Exclusions

Unavailable minutes exclude Scheduled Maintenance and announced Emergency Maintenance; Customer systems, credentials, configurations, data, networks, devices, or misuse; external internet or telecommunications failures; third-party platforms or AI providers outside Provider's reasonable control when Provider uses reasonable restoration or workaround efforts; periods when AI features are rate-limited or suspended under Section 8; a permitted suspension under this Agreement; beta, preview, trial, or no-charge features; Customer-requested suspension or maintenance; Force Majeure Events; malicious attacks not caused by Provider's failure to maintain reasonable safeguards; and legal or governmental action.

B3. Maintenance

TypeNotice targetOperating approach
Scheduled MaintenanceAt least 48 hoursPlanned outside normal Customer business hours when reasonably practicable
Emergency MaintenanceAs much as practicableUsed for urgent security, stability, or third-party infrastructure risks
Routine deploymentsNo advance notice requiredDesigned not to create material downtime

B4. Monitoring and reports

Provider will use reasonable monitoring appropriate to the Service. On reasonable request, Provider will provide a summary of a material incident or availability calculation. Provider's monitoring records control unless Customer provides credible contrary evidence.

B5. Continuity targets

Backup frequencyRecovery point targetRecovery time target
Continuous, with point-in-time recovery for fourteen (14) days24 hours1 business day
Continuity targets are operational objectives, not guaranteed restoration times. Customer remains responsible for exports or records needed for its own legal and business-continuity requirements.

B6. Support coverage

Standard support hours are Monday through Friday, 8:00 a.m. to 5:00 p.m. Eastern Time, excluding United States federal holidays (Business Hours). Incidents may be emailed at any time to support@limestonetg.com. Response targets are measured during Business Hours except Priority 1 incidents. For a P1 incident outside Business Hours, Customer must also call 865-680-9841; Provider will then use reasonable efforts to respond outside Business Hours. Separately from support, Provider monitors security and availability alerts twenty-four (24) hours a day, seven (7) days a week, and an on-call engineer is paged when an alert fires. This monitoring does not change the Business Hours support response targets.

B7. Priority levels

PriorityDefinitionInitial responseUpdate target
P1 CriticalProduction broadly unavailable, or confirmed active security event materially affects Customer Data; no reasonable workaround2 hoursEvery 4 hours while actively worked
P2 HighMaterial degradation of a core function affecting multiple users; limited workaround may exist4 Business HoursEach Business Day
P3 NormalNoncritical defect affecting a user or feature with a reasonable workaround1 Business DayAs material progress occurs
P4 RequestQuestion, documentation request, cosmetic issue, or enhancement request2 Business DaysAs appropriate

Response time means acknowledgment, priority confirmation, and the start of reasonable investigation; it is not a guaranteed resolution time. Provider may change priority based on documented impact and will communicate a material change.

B8. Customer cooperation

Customer will provide affected user names, timestamps, screenshots, reproduction steps, business impact, and reasonable access needed to investigate. Time waiting for Customer information, access, or confirmation is excluded from response and update measurements.

B9. Service credits

Monthly availabilityCreditCredit basis
99.5% or greater0%No credit
99.0% to 99.49%5%One month's prorated Platform and affected Module fees
98.0% to 98.99%10%One month's prorated Platform and affected Module fees
Below 98.0%20%One month's prorated Platform and affected Module fees

Customer must request a credit in writing within thirty (30) days after the affected month and include reasonable incident details. Approved credits apply to a future invoice, have no cash value, and are capped at 20% of one month's prorated Platform and affected Module fees. Credits are the sole monetary remedy for an availability-objective miss.

B10. Chronic failure

If Monthly Availability is below 99.0% for three consecutive months, Customer may terminate the affected Module by written notice within thirty (30) days after the third month and receive a prorated refund of prepaid, unused recurring fees for that Module. Implementation fees are not refundable.

Schedule C

Security, Data, and AI Safeguards

C1. Security program

  • role-based access and least-privilege practices;
  • unique administrative credentials and multifactor authentication where supported;
  • encryption in transit using TLS 1.2 or higher;
  • encryption at rest of Customer Data, including backups, using AES-256;
  • reasonable logging and monitoring, with security alerts monitored twenty-four (24) hours a day, seven (7) days a week;
  • remediation of vulnerabilities in the Service within the following periods after a fix becomes available, based on Provider's reasonable severity rating using the CVSS score or the vendor's rating: Critical, seven (7) days, and sooner when actively exploited; High, fourteen (14) days; Medium, thirty (30) days; and Low, ninety (90) days;
  • personnel confidentiality obligations;
  • backup and recovery practices described in Schedule B; and
  • documented incident-response procedures.

C2. Security incidents

A Security Incident is confirmed unauthorized access to or acquisition, alteration, disclosure, or destruction of Customer Data in Provider's control. It excludes unsuccessful attempts that do not compromise Customer Data or the Service. Provider will give Customer preliminary notice within twenty-four (24) hours after Provider discovers a suspected Security Incident that Provider reasonably believes affects Customer Data, and full written notice within seventy-two (72) hours after confirmation. Notice will include known material facts, containment actions, and reasonable next steps, with updates as material information becomes available. Provider may delay information when required by law enforcement or necessary to preserve security. These duties do not apply to an incident caused by Customer credentials, configurations, devices, or breach of this Agreement.

C3. Subprocessors

Provider may use subprocessors for cloud hosting and storage, AI and model services, monitoring and logging, and communications and support. Provider will require subprocessors that process Customer Data to maintain appropriate confidentiality and security obligations and remains responsible for its contractual obligations. Provider maintains a current list of subprocessors and will provide it on reasonable written request. Where commercially practicable, Provider will notify Customer before adding a material new subprocessor that will process Customer Data.

C4. Data use and retention

Provider will process Customer Data only for this Agreement, Customer's documented instructions, security and support, or applicable law. Customer controls what it submits and should minimize sensitive information. Production Customer Data is retained during the service term and handled after termination under Section 15. Backup copies may persist until overwritten through ordinary retention cycles. For AI Gateway prompt and response logs, Customer may set the retention period to match its records retention schedule, and Provider will permanently delete logs older than that period, subject to the backup copies described above.

C5. AI safeguards

  • Provider will configure supported enterprise privacy controls where commercially available and appropriate.
  • Provider will not knowingly use Customer Data to train a generally available AI model without Customer's prior written consent.
  • Customer will not submit secrets or regulated data to an AI-enabled field unless the Parties approved that workflow.
  • Customer will maintain human review for material decisions and will not present AI output as verified fact without appropriate validation.
  • Provider may change an underlying model or provider for security, availability, quality, or cost if purchased functionality is not materially reduced.

C6. Customer controls

Customer is responsible for access approvals, endpoint protection, retention requirements, user training, and prompt reporting of suspected credential compromise. Customer will notify Provider before materially changing expected data types or use cases.

C7. Regulated environments

This Agreement does not by itself establish compliance with HIPAA, PCI DSS, CJIS, FedRAMP, IRS Publication 1075, state criminal-justice requirements, government-classified-data rules, or a Customer-specific security standard. The Parties must complete a written assessment and sign any required addendum before regulated data is introduced. For a public Customer, the applicable Service Order should also identify records-retention, public-records, data-location, and breach-notification requirements.

Operational rule. AI-assisted output supports a process; it does not replace the Customer's accountable human decision-maker.

This Agreement is accepted when a Service Order referencing it is executed as described in Section 1, not by browsing this page. No Product is ordered until a Service Order is executed.

Operational contactDetail
Provider support channelsupport@limestonetg.com
Provider P1 support line865-680-9841
Customer operational contactAs stated in the applicable Service Order

Questions about these terms? Email us at info@limestonetg.com.