RelioHubBack to home

RelioHub Terms of Service

Version 2026-10-14 · Effective

Version 2026-10-14 · Effective October 14, 2026

Provider: NORTHMARK MANAGEMENT GROUP LLC, a Texas limited liability company doing business as “RelioHub”

Contacts: legal notices to legal@reliohub.com · privacy requests and security reports to privacy@reliohub.com · support through in-app support tickets

PLEASE READ THESE TERMS CAREFULLY. SECTION 20 REQUIRES BINDING INDIVIDUAL ARBITRATION AND WAIVES JURY TRIALS AND CLASS, COLLECTIVE AND REPRESENTATIVE ACTIONS, SUBJECT TO LIMITED EXCEPTIONS. SECTIONS 17 THROUGH 19 DISCLAIM WARRANTIES, LIMIT PROVIDER’S LIABILITY AND REQUIRE CUSTOMER TO INDEMNIFY PROVIDER, AND SECTION 17.4 WAIVES RIGHTS UNDER THE TEXAS DECEPTIVE TRADE PRACTICES-CONSUMER PROTECTION ACT. SUBSCRIPTIONS RENEW AUTOMATICALLY EACH MONTH AND FEES ARE NON-REFUNDABLE. BACKUPS DO NOT GUARANTEE THAT DATA CAN BE RESTORED, THERE IS NO BULK EXPORT, AND CUSTOMER DATA MAY BE DELETED AFTER TERMINATION. BY CHECKING THE ACCEPTANCE BOX OR USING THE SERVICE, CUSTOMER AGREES TO THESE TERMS.

Welcome to RelioHub. We built RelioHub to help construction businesses run their projects, crews, documents and billing in one place, and we are grateful you are considering it for your company.

The Service is offered only to businesses. These Terms of Service are part of the Agreement between Provider and Customer, which also incorporates the RelioHub Privacy and Data Protection Policy (the Privacy Policy), the Acceptable Use Rules in Section 7 and each Order. Each major Section opens with a summary labeled “In plain terms.” The summaries are for convenience only; they are not part of the legal terms and do not affect their interpretation.

1. Acceptance of These Terms; Electronic Signature

In plain terms. When you create an account, you tick a box confirming that you agree to these Terms and our Privacy Policy and that you may agree for your company. That click is a real signature, and we keep a record of it so we both know which version was accepted and when.

1.1 Clickwrap Acceptance and Electronic Signature

(a) At sign-up, the Service presents links to these Terms of Service and the Privacy Policy and an acceptance checkbox that is not pre-checked. No Account is created unless the Account Creator checks it and submits the form, thereby confirming the opportunity to read both documents, binding Customer to the Agreement and adopting that action as Customer’s electronic signature. The Agreement takes effect on that acceptance or on any earlier use of the Service and continues until terminated under Section 16.

(b) That acceptance, and any acceptance under Section 21.2, is an electronic signature and record under the Electronic Signatures in Global and National Commerce Act (15 U.S.C. § 7001 et seq.) and the Texas Uniform Electronic Transactions Act (Tex. Bus. & Com. Code ch. 322), with the effect of a handwritten signature. Customer will not contest the Agreement’s validity or admissibility because it was formed or kept electronically.

1.2 Authority, Age and Business Use

(a) The Account Creator, and each Administrator who accepts a new version, represents that he or she is at least 18, has authority to bind Customer, and has given accurate information, and that Customer is a business in good standing or a sole proprietorship operating a bona fide business. A person who lacks authority, or accepts for a business that does not exist, is personally bound and liable for Customer’s obligations. Customer’s payment of Fees or use of the Service for more than thirty (30) days ratifies the acceptance.

(b) Customer represents that it uses the Service solely for business purposes, not personal, family or household purposes. Provider relies on this and may close any Account used for consumer purposes.

1.3 Acceptance Records

Each acceptance of a version of the Terms of Service or the Privacy Policy creates an Acceptance Record of the version identifier, a hash of the document, the timestamp, the IP address, the browser user agent and the accepting username. Customer agrees that Acceptance Records are admissible business records evidencing its acceptance, the acceptor’s identity, the time and the version, and Provider may keep them after the Agreement ends.

1.4 Users

Each User must comply with the Agreement and accept any user-level terms Provider requires, including individual arbitration. Customer is liable for every act and omission of each User, Worker and other person who uses the Service through the Account, or through credentials, links or MCP Grants issued for it, as its own. Users acquire no rights in their own name.

2. Definitions and Interpretation

In plain terms. This glossary serves both these Terms and our Privacy Policy, so the same words mean the same thing everywhere.

2.1 Definitions

2.2 Interpretation

“Including” means “including without limitation.” “Written” includes email and in-Service records. “Currently” describes present practice and creates no commitment to keep it. “May” confers discretion, not obligation. A Section reference is to the document in which it appears unless the other is named. The Agreement is an arm’s-length contract between businesses and will not be construed against its drafter.

3. Accounts, Administrators and Users

In plain terms. Your account belongs to your company, and your administrators decide who signs in and what each person can do. Please keep sign-in details private, tell us right away if something looks wrong, and think carefully before permanently deleting a person, because that also deletes records you may need.

3.1 Registration and Administrators

(a) Customer will keep its registration and User information accurate. Provider may rely on it, may require proof of existence or authority, and may refuse a misleading or infringing company identifier.

(b) Customer decides who holds administrative privileges. Administrators manage Users and roles, approve or deny Support Access Session requests, manage MCP Grants, links and the Public Profile, and configure settings, including the Processing Fee Pass-Through. Provider may rely on any Administrator’s instruction or acceptance as Customer’s.

(c) Permanent deletion. Permanently deleting a User irreversibly removes the User’s login and associated Customer Data, including timesheets, pay history, photos and reports; deactivation keeps them. Customer must first keep outside the Service every record it needs or must retain by law. PROVIDER HAS NO LIABILITY FOR ANY LOSS FROM A DELETION INITIATED THROUGH THE ACCOUNT.

3.2 Credentials and Security

Users sign in with the company identifier, a fixed username and a password, or another method Provider requires; email is optional and used for notifications. Credentials are personal and may not be shared, and Users must be 18 or older (the Service does not verify age). Customer is responsible for credential confidentiality, device security and promptly removing Users, and will report any suspected compromise without undue delay by support ticket or at privacy@reliohub.com. Provider does not represent that any particular authentication feature is or will be available. PROVIDER IS NOT LIABLE FOR ANY LOSS FROM USE OF CREDENTIALS ISSUED FOR THE ACCOUNT, WHETHER OR NOT AUTHORIZED.

3.3 Account Management and Control Disputes

To protect security, at Customer’s request, to enforce the Agreement or to comply with law, Provider may disable Users, force password resets, end sessions, unlock accounts, change emails at an Administrator’s request and revoke MCP Grants, with or without notice and without liability for good-faith action. The Account belongs to Customer, not any individual; in a dispute over its control, Provider may rely on the Administrators in its records, require documentation such as a resolution or court order, restrict access until resolved and decline to take sides, while Fees continue to accrue.

4. The Service and Changes to the Service

In plain terms. RelioHub is a living product: we add, improve and sometimes retire features and change providers, and we occasionally need downtime. We do not guarantee uptime, so please choose RelioHub for what it does today rather than for future plans.

4.1 Right to Use

Subject to the Agreement and payment, Provider grants Customer, during the Trial and Subscription Term, a limited, non-exclusive, non-transferable right for it and its Users to use the Service for Customer’s internal business operations, including dealing with its own Clients, Payers and Guest Contributors, within the Plans and limits purchased. Access may be read-only after an unpaid Trial or a payment failure and blocked during suspension or after termination (Sections 11 and 16); the Tax Features, including reading their records, are unavailable without a Plan that includes them or an active Trial. In each of these cases, a Worker may still view and download the tax forms furnished to them electronically, as described in Section 8.6(d). All other rights are reserved.

4.2 Description and Changes

(a) Depending on Plan, the Service currently includes project, report and to-do tools; photo, video, document and audio storage; the Workforce Features; quotes, invoices and Pay Pages; on Plans that include them, electronic signature of quotes by Clients and expense tracking with AI reading of receipt images; the AI Features; MCP connections; a Public Profile; and Upload Links. Features vary by Plan and between web and Mobile App. This description is not a specification or warranty.

(b) Provider may at any time add, change or discontinue features, Plans, integrations, hosting, Subprocessors (Section 7 (Subprocessors) of the Privacy Policy) and AI Providers. For a materially adverse reduction of a paid Plan’s core functionality, Provider will use reasonable efforts to give advance notice, except for changes needed for security, legal or third-party reasons. Customer’s sole remedy is to cancel.

4.3 Availability; No Service Level

PROVIDER WILL USE COMMERCIALLY REASONABLE EFFORTS TO MAKE THE SERVICE AVAILABLE BUT OFFERS NO SERVICE-LEVEL AGREEMENT AND DOES NOT GUARANTEE UPTIME, PERFORMANCE OR ERROR-FREE OPERATION. Maintenance, defects, security events, failures of Third-Party Services or of the hosting, email, payment and AI services the Service relies on, and events beyond Provider’s control may interrupt it.

4.4 Beta Features; Mobile App; Future Features

BETA FEATURES ARE OPTIONAL AND PROVIDED “AS IS” WITHOUT WARRANTY OR SUPPORT, MAY BE WITHDRAWN AT ANY TIME, AND PROVIDER HAS NO LIABILITY FOR THEM. The Mobile App is part of the Service; it may lack some web features (such as sign-up and acceptance of new versions), may update itself, including over the air, and may request device permissions such as location and camera. Customer’s purchases do not depend on, and Customer has not relied on, any future feature, roadmap or marketing description, which may show features that are not part of the Service.

4.5 Emails and Notifications

EMAIL DELIVERY IS NOT GUARANTEED. MESSAGES MAY BE DELAYED, FILTERED OR SILENTLY SUPPRESSED, AND A MESSAGE SHOWN AS SENT, RELAYED OR ARCHIVED MAY NEVER HAVE BEEN DELIVERED. Customer must confirm receipt of any communication that matters, including invoices and legally required notices, and Provider has no liability for non-delivery. Emails sent for Customer are governed by Section 22.3.

5. Customer Content, Data Ownership and Licenses

In plain terms. Your invoices, quotes, photos and records belong to your company; we never own them and we treat them as confidential. We use them only to run, protect, support and improve RelioHub, and we never sell them. We back up the Service so we can recover from failures, but those backups are not an archive for you, so please keep your own copies of anything important.

5.1 Ownership and License

(a) As between the parties, Customer owns Customer Content and Customer Data. Provider acquires no ownership by hosting or processing them.

(b) Customer grants Provider a worldwide, non-exclusive, royalty-free license, for the Subscription Term (including any Trial) and while Provider retains Customer Data under Section 16, to host, store, copy, back up, process, index, transcribe, embed, display and create derivative works of Customer Content and Customer Data as reasonably necessary to provide, secure, support and improve the Service, prevent fraud, comply with law and enforce the Agreement, with the right to sublicense to Subprocessors and AI Providers for those purposes.

(c) Customer also licenses Provider to publish the Public Profile fields Customer chooses and let search engines index them (a published profile is indexable unless Customer opts out, and third parties may keep cached copies), and to display each invoice’s content to any holder of its Payment Link until it expires or is revoked, including after suspension or termination. Customer is responsible for all public-facing content.

5.2 Customer’s Representations

Customer represents and warrants, continuously, that (a) it has all rights needed to submit Customer Content and grant these licenses; (b) it has given every notice and obtained every consent Applicable Law requires from its Users, Workers, Clients, Payers, Guest Contributors and others for Provider, its Subprocessors and AI Providers to process their Personal Information as the Agreement describes, including under Sections 6, 8 and 10; (c) neither Customer Content nor its processing infringes any right or violates any law; and (d) it contains no Prohibited Data.

5.3 Output, Feedback, Usage Data

(a) Customer owns Output to the extent rights subsist; Output may not be unique, and Provider does not warrant that it is original or non-infringing.

(b) Customer grants Provider a perpetual, irrevocable, royalty-free license to use Feedback for any purpose; Provider will not publicly name Customer as its source without consent.

(c) Provider owns Usage Data and Aggregated Data and may use them for any lawful purpose, including operating, metering, securing and improving the Service. Provider will disclose Aggregated Data only in non-identifying form and will not re-identify it. Personal Information in Usage Data collected in serving Customer is processed only as Section 1 (Scope of This Policy and Our Roles) of the Privacy Policy permits.

5.4 No Sale; Deletion by Customer

(a) Provider does not sell Customer Data or use it for targeted or cross-context behavioral advertising, and discloses it only as stated in Section 6.10 and Sections 6 (How We Disclose Information) and 7 (Subprocessors) of the Privacy Policy.

(b) Customer may delete certain content as the Service permits; sent invoices, audit and change records, Payment Acceptance Records, Quote Signature Records, support-access records, AI usage records and sent-email copies and metadata cannot be deleted. Deletion is not immediate or complete: items may be held before purge, files are removed asynchronously, and residual copies may remain in backups, logs, caches and storage versions until they age out. Provider has no obligation to delete within any period except as law requires; see Section 10 (Retention and Deletion) of the Privacy Policy.

5.5 Backups; Customer’s Own Copies; No Export

(a) Backups. Provider performs backups of the Service designed to support recovery of the Service after a failure, on a schedule, scope and retention it determines and may change. Backups are for Provider’s operational use; they are not an archive, a records-retention system or an export for Customer, and Provider does not restore individual records, files or Accounts on request. PROVIDER DOES NOT GUARANTEE THAT ANY BACKUP WILL EXIST, BE COMPLETE OR BE USABLE, OR THAT ANY LOST, CORRUPTED OR DELETED DATA CAN OR WILL BE RESTORED, AND MAKES NO RECOVERY-TIME, RECOVERY-POINT OR DISASTER-RECOVERY COMMITMENT.

(b) No export. The Service has no bulk or self-service export, and Provider does not commit to any export or portability, during or after the Subscription Term, except as Data Protection Laws require (Section 13 (Your Rights and Choices) of the Privacy Policy). While the Account is active and not suspended, Customer may download individual items the Service makes downloadable, such as documents, photos and invoice PDFs.

(c) CUSTOMER IS SOLELY RESPONSIBLE FOR KEEPING ITS OWN COPIES OF ALL DATA IT NEEDS OR MUST RETAIN BY LAW. TO THE MAXIMUM EXTENT PERMITTED BY LAW, PROVIDER HAS NO LIABILITY FOR ANY LOSS, CORRUPTION OR UNAVAILABILITY OF CUSTOMER CONTENT OR CUSTOMER DATA, WHETHER OR NOT A BACKUP EXISTS.

6. Platform Access to Customer Data

In plain terms. Running RelioHub means some of our people can see some of your information, and we want to be candid about when, how and why.

  • We never sell your data or use it for advertising.
  • Access has a purpose: support, fixing problems, keeping RelioHub running and secure, preventing fraud, billing, legal obligations and enforcing our agreement, and our policy is to look only at what the task requires. Everyone with access is bound by confidentiality.
  • You approve “view as” visits. We normally ask your administrators first; visits are read-only and time-limited, and every request, even one made without prior approval, appears on your Support & access page.
  • Limited exceptions. For security incidents, legal obligations, fraud or harm prevention, keeping the Service running, or urgent problems when we cannot reach you, authorized senior staff may access data without asking first, and the reason for any such visit must be recorded.
  • What our tools show: company and user details, support tickets and email records. Specifically authorized staff can open copies of emails sent through RelioHub, including invoices and quotes, and each opening is logged.
  • Servers and test systems. People who run our servers and private test systems can technically reach stored data, and we may copy data to test systems to check changes. That access is limited by policy and confidentiality, not by technology.
  • Logging. We log administrative actions, support-access requests, the start of each support session and every opening of email content, but not every individual view.

Customer acknowledges, and consents for itself and its Users, that Platform Personnel can and may access, view, copy and process Customer Data, Account Data and Usage Data as described in this Section 6 and in Section 5 (Platform Staff Access to Your Data) of the Privacy Policy, for as long as the Service is used and Provider retains Customer Data. This Section 6 controls if the two conflict.

6.2 Purposes

Platform Personnel may access that data for: (a) customer support; (b) troubleshooting and correcting errors and failed processing; (c) operating, maintaining, upgrading and restoring the Service; (d) protecting the security and integrity of the Service and all customers’ data, including investigating Security Incidents; (e) preventing and investigating fraud, abuse, unlawful activity and breaches of the Agreement; (f) billing, refunds, credits and administration of Subscriptions, AI Credits and the Account; (g) complying with law, legal process and binding governmental requests; (h) enforcing the Agreement, pursuing or defending claims and protecting the rights, property and safety of Provider and others; and purposes reasonably related to these. Provider’s policies direct Platform Personnel to access Customer Data only as reasonably necessary for these purposes; their technical ability to view information (Sections 6.3 and 6.6) may be broader, and this Section does not require Provider to restrict it.

6.3 Administrative Tools

Platform Personnel hold roles (currently ownership, administration, support, billing, operations and read-only); only specifically authorized personnel may add staff or change roles.

(a) Every role, including read-only, may currently view across all Accounts: company details (names, license data, addresses, phones, website, owner and billing contacts, invoice settings, Plan and Subscription status, billing summaries and Stripe identifiers, AI Credit balance, counts of Workers, projects, documents, signed quotes and expenses, open disputes, last activity); User details, including emails, status, last sign-in and active sessions with IP addresses; support tickets with messages, attachments (such as screenshots), diagnostics and Provider’s internal notes; internal Account notes; per-User AI usage; document processing status and, for failed documents, title, project and error; email metadata (sender, recipients, subject, type, related company, project and Worker, delivery status); MCP Grants; Acceptance Records; and the audit log.

(b) Email content. Personnel in roles specifically authorized for it may view the body and attachments of, and download, any email the Service sent that remains in Provider’s archive, including invoices and quotes sent to Clients with their PDFs and messages to Users and Workers. Authorized Platform Personnel may therefore view the full content of documents Customer sends through the Service and their recipients’ names and addresses. Each viewing or download is designed to be recorded in the audit log. Section 10 (Retention and Deletion) of the Privacy Policy describes how long email content is kept.

(c) The Administrative Tools do not currently provide a screen for browsing projects, invoices, quotes, photos, timesheets or documents directly, but Platform Personnel may view them through Support Access Sessions, infrastructure access and the email archive. These tools and roles may change, without limiting Section 6.2.

6.4 Support Access Sessions with Administrator Approval

(a) When Platform Personnel need to see the Service as a User sees it, authorized personnel will normally submit a request naming the User and the reason. Provider currently emails it to Customer’s Administrators and lists it on the support-access page (currently “Support & access”). Any Administrator may approve or deny it, and any approval binds Customer.

(b) An approval currently opens a 24-hour window in which one or more sessions may be started, each currently limited to 30 minutes and not extendable. Provider may change these periods.

(c) In a session, Platform Personnel see what the named User can see, which for an Administrator may include invoices, quotes, Client details, payment, time and attendance records, Location Data, pay rates and Estimated Pay.

(d) Sessions are designed to be read-only: the Service is designed to refuse requests that would create, change or delete data, send invoices or emails, create Payment Links, change billing or Plans, buy AI Credits or change the Connected Account. Provider does not warrant that these controls are error-free.

(e) The support-access page currently lists each request, including those under Section 6.5, with the requesting staff member, reason, status and decision. It does not currently show session times or what was viewed, sessions are not recorded in the Account’s change history, and an approval cannot be withdrawn once given. Customer may raise concerns by support ticket or at privacy@reliohub.com, and Provider will consider them in good faith.

(f) A denial or non-response does not limit access under Sections 6.3, 6.5, 6.6 or 6.7 and may limit support, without liability. Provider will not use Section 6.5 solely because a routine request was denied or unanswered.

6.5 Access Without Prior Approval

(a) Authorized senior Platform Personnel may start a Support Access Session, or otherwise access Customer Data, without an Administrator’s prior approval and without prior or contemporaneous notice, when they reasonably consider it necessary to: (1) respond to an actual or suspected Security Incident or other threat to the Service or any data; (2) comply with a legal obligation, legal process or binding governmental request; (3) prevent or address harm to any person, fraud, abuse or unlawful activity; (4) keep the Service running or restore it; or (5) address an urgent issue affecting Customer or its Users when Customer cannot be reached promptly.

(b) The reason for each such session must be recorded in the Administrative Tools. It is read-only and time-limited as in Section 6.4 but not subject to the approval window, and further sessions may be started under the same authorization until it is ended. Requests for these sessions are currently listed on the support-access page; other access under this Section is not. Provider does not undertake to give separate notice of this access and may withhold notice where law requires or to protect an investigation, the Service or any person.

6.6 Infrastructure-Level Access

Platform Personnel who administer Provider’s servers, databases, storage, identity systems, queues, logs, backups and copies have technical access to Customer Data in them, outside the Administrative Tools and Support Access Sessions, and may use it only for the purposes in Section 6.2, such as maintenance, migrations, debugging, data repair, backup and recovery and security response. Their tools include live logs with identifiers and request metadata and job-queue dashboards. This access is controlled by credentials, network restrictions, policy and need, not by technical impossibility, and may not be individually logged.

6.7 Non-Production Environments

Provider may copy Customer Data, in whole or in part, into Non-Production Environments to reproduce problems, test changes and migrations before release and verify the Service with realistic data, and may, but does not undertake to, minimize, pseudonymize or replace it with placeholders. Access is limited to Platform Personnel, and the data remains subject to Section 14, Section 6.9 and the Privacy Policy and is used only for these purposes and those in Section 6.2. Section 12 (Where Data Is Processed) of the Privacy Policy describes where these environments operate.

6.8 Logging

(a) Provider maintains an audit log designed to record administrative actions taken through the Administrative Tools (such as suspensions, Plan changes, refunds, AI Credit adjustments, login management and MCP Grant revocations) with the staff account and roles, time, target, outcome, IP address and user agent and, for sensitive actions, the reason; each Support Access Session request, each session authorized under Section 6.5 with its reason, the start of each session and any early end; and each viewing or download of archived email content.

(b) The log is designed to be append-only, so entries cannot be changed or deleted through ordinary database operations, but Provider does not represent that it is tamper-proof, and records may outlive the Account. Not every access is logged: routine viewing of the information in Section 6.3(a), the records viewed within a session and infrastructure access may not be. The log is Provider’s record and is not provided to Customer except as law requires, though Provider may share relevant information, for example after a Security Incident.

6.9 Confidentiality and Safeguards

Provider applies these safeguards, which it may change without materially reducing overall protection: (a) every member of Platform Personnel is bound by written confidentiality obligations no less protective of Customer Data than Section 14; (b) role-based permissions, with sensitive capabilities restricted to specified roles; (c) a separate administrative console with separate sign-in and session cookies and sessions limited by inactivity and duration; (d) staff accounts designed not to be usable as Users of the customer-facing Service; and (e) a policy of accessing only the data the task requires. Provider is responsible for its Platform Personnel’s compliance with this Section 6.

6.10 Limits on Use and Disclosure

(a) Provider never sells Customer Data, does not use it for advertising, and does not permit Platform Personnel to use access to it except for the purposes in Section 6.2 and other uses the Agreement permits; misuse violates Provider’s policies and may lead to revocation of access and other action.

(b) Provider does not disclose Customer Data to third parties except: (1) to Subprocessors that help provide, support, secure or operate the Service (Section 7 (Subprocessors) of the Privacy Policy); (2) when it believes in good faith that law, legal process or a binding governmental request requires it; (3) when it believes in good faith that disclosure is necessary to protect the rights, property or safety of Provider, its customers, Users or others, including to prevent fraud; (4) in an actual or proposed merger, acquisition, financing, reorganization or asset sale, subject to customary confidentiality; or (5) with Customer’s instruction or consent.

(c) Customer instructs Provider to transmit Customer Data as needed for the functions Customer uses, including to Stripe for payments and dispute evidence, to email recipients, on Pay Pages and Public Profiles, and to MCP Clients and other Third-Party Services Customer connects; these recipients are not Subprocessors. Provider may comply with a binding demand for Customer Data without notifying Customer, although it may redirect the requester to Customer or notify Customer where lawful and reasonable.

6.11 Account Actions by Provider

Customer authorizes Platform Personnel to act on the Account through the Administrative Tools, including to suspend or reactivate it, change, cancel or extend Subscriptions, Plans and Trials, apply credits and issue refunds, adjust AI Credits and auto-recharge, manage Users and MCP Grants, manage document processing, and take other actions reasonably necessary for the purposes in Section 6.2, without liability for good-faith action.

6.12 Customer’s Disclosures

Customer will inform its Users and, where law requires, its Workers and other individuals in Customer Data, that Platform Personnel may access their information as described in this Section 6 and the Privacy Policy, and will make no inconsistent statement.

6.13 No Additional Commitments

EXCEPT AS EXPRESSLY STATED IN THIS SECTION 6, PROVIDER DOES NOT COMMIT THAT ACCESS TO CUSTOMER DATA WILL REQUIRE CUSTOMER’S PRIOR APPROVAL, THAT CUSTOMER WILL BE NOTIFIED OF ANY ACCESS, THAT ANY PARTICULAR ACCESS WILL BE LOGGED OR DISCLOSED TO CUSTOMER, OR THAT ANY PARTICULAR AUTHENTICATION METHOD WILL BE USED FOR PLATFORM PERSONNEL. Provider’s security practices are described in Section 15 and Section 11 (Security) of the Privacy Policy.

7. Customer Responsibilities and Acceptable Use

In plain terms. Please tell your people and your clients how their information is used, keep highly sensitive information such as Social Security numbers and medical details out of RelioHub, and use the tools lawfully.

7.1 Notices and Consents

These Acceptable Use Rules bind everyone who uses the Service through the Account. Customer will use the Service only for its internal business purposes and in compliance with Applicable Law, and is solely responsible for giving every notice and obtaining every consent the law requires from its Users, Workers, Clients, Payers and Guest Contributors, including notice of the processing in Sections 6, 8, 9 and 10 and that their information is shared with Subprocessors and Stripe. Customer handles Privacy Requests about Customer Data as described in Sections 13 (Your Rights and Choices) and 16 (Customer Obligations to Its Workers and Clients) of the Privacy Policy.

7.2 Prohibited Data

Tax Identification Data entered through the Tax Features as designed is not Prohibited Data and is governed by Section 8.6; anywhere else in the Service it is. Customer will not enter or store Prohibited Data anywhere in the Service, including notes, documents, photos (such as images of IDs or cards), receipt images, recordings, Company Rules or support tickets. A receipt image may show a masked or truncated card number (such as the last four digits) but must not show a full card number, and Customer is responsible for every receipt its Users upload. The Service is not designed to protect Prohibited Data, and Provider has no duty to detect it. PROVIDER HAS NO LIABILITY ARISING FROM PROHIBITED DATA, AND CUSTOMER WILL INDEMNIFY THE PROVIDER INDEMNITEES AGAINST ANY RESULTING CLAIM OR OBLIGATION, INCLUDING BREACH-NOTIFICATION OBLIGATIONS.

7.3 Prohibited Conduct

Customer will not, and will not permit anyone to: (a) use the Service for illegal, fraudulent, deceptive or infringing purposes; (b) transmit malicious code; (c) access any account, data or system without authorization, or test the Service’s security without Provider’s written consent; (d) scrape or extract data except through documented APIs and the MCP Server; (e) circumvent quotas, rate limits, Seat counts or metering, including by misreporting Worker status; (f) overload or disrupt the Service; (g) use the Payment Services for fraud, money laundering, sanctions evasion, prohibited businesses or unlawful surcharges; (h) send unsolicited commercial messages or false invoices; (i) harass, defame or unlawfully discriminate, or unlawfully surveil anyone, including tracking Workers outside working time; (j) impersonate anyone or misstate Customer’s licensing; (k) share credentials; (l) resell or provide the Service to third parties; (m) build a competing product or copy the Service; or (n) help anyone do these things.

Customer is responsible for distributing and revoking Upload Links and Payment Links, for all content submitted through its Upload Links by anyone, and for its Public Profile. The Service is not a records-retention system; Customer must keep, outside the Service, every record that law or contract requires, including time, payroll, tax, employment, contract and invoice records.

7.5 Enforcement

Provider may, but need not, monitor the Service, including through Section 6. If Provider reasonably believes these Rules or the law have been or may be violated, or that anyone is exposed to harm or liability, it may without notice investigate, remove content or links, suspend Users, features or the Account, and report to and cooperate with authorities, Stripe and card networks, including by disclosing Customer Data. PROVIDER HAS NO LIABILITY FOR ACTING OR NOT ACTING IN GOOD FAITH UNDER THIS SECTION. Violations may be reported to legal@reliohub.com.

8. Workforce Features: Time Clock, Geolocation, Device Identity and Pay Estimates

In plain terms. Our time clock shows who worked where and for how long and estimates pay, but you are the employer: payroll, overtime, breaks and the notices your crew is owed are yours, and our numbers are a starting point. Location is recorded at clock-in and clock-out (and accessed while the clock screen is open) and with reports, photos and videos; the Mobile App is not designed to track location in the background. A long-lived device cookie and browser fingerprint help spot one person clocking in for another. We collect no biometrics, and these signals are hints for a person to review, never a verdict.

8.1 Customer Is the Employer

The Workforce Features let Customer record time against projects with Location Data and Device Identity Data, set geofences, review and correct timesheets (with prior values recorded), record pay rates, calculate Estimated Pay and receive open-shift alerts. As between the parties, Customer alone is responsible for all employment and wage-and-hour law, including the Fair Labor Standards Act and state law on minimum wage, overtime, breaks, rounding, prevailing wage, worker classification, payroll, withholding, wage statements, recordkeeping, pay transparency and child labor.

8.2 Estimated Pay and Shift Records

(a) ESTIMATED PAY IS INFORMATIONAL ONLY. IT IS NOT PAYROLL, A WAGE STATEMENT OR TAX, LEGAL OR EMPLOYMENT ADVICE, and may omit overtime, premiums, deductions and other amounts. Customer must verify all hours and amounts before paying anyone.

(b) When a shift stays open for an extended period (currently 12 hours), the Service may alert the Worker and managers and close the shift provisionally, excluding it from pay totals until a manager confirms it. Alerts may fail and open shifts may go undetected; Customer must review all shifts and corrections.

(c) PROVIDER DOES NOT WARRANT THE ACCURACY OR LEGAL SUFFICIENCY OF ANY TIME RECORD, SHIFT CLOSURE OR ESTIMATED PAY, AND HAS NO LIABILITY FOR ANY UNDERPAYMENT, OVERPAYMENT, WAGE CLAIM OR PENALTY. CUSTOMER ASSUMES ALL RISK OF RELYING ON THE WORKFORCE FEATURES, EVEN IF THE LOSS ARISES IN WHOLE OR IN PART FROM THE NEGLIGENCE OF PROVIDER OR ANY PROVIDER INDEMNITEE.

8.3 Geolocation and Device Identity

(a) The Service collects Location Data at clock-in and clock-out (the device’s fix and accuracy, distance to the jobsite and geofence status); continuously while the clock screen is open, to prepare that fix; with daily reports and photos, from the device or photo metadata, including Upload Link submissions; in metadata embedded in videos; and by geocoding project addresses through a third party. A Worker may be allowed to clock in without a fix or outside a geofence by giving a reason. The Mobile App is not designed to collect location in the background. Location may be wrong or unavailable, and Customer will not use it as the sole basis for any decision about a Worker.

(b) To protect attendance integrity and detect buddy punching, the Service uses a persistent device-identity cookie (currently about two years, renewed on use and not cleared at sign-out), a browser fingerprint hash, device labels, session keys, and records of which devices clocked in which Workers, including shared-device indicators naming other Workers seen on a device. These are indicators, not findings of misconduct; Customer will apply meaningful human review before any adverse action.

(c) The Service collects no biometric identifiers: no photo at clock-in, facial recognition, fingerprints or voiceprints. Voice recordings may be transcribed but are not used to identify speakers. See Section 9 (Location Data, Device Identity, Cookies and Similar Technologies) of the Privacy Policy.

8.4 Notice to Workers

Before any Worker uses the Workforce Features, Customer will give every notice and obtain every consent the law requires for Location Data, Device Identity Data and electronic monitoring, including state monitoring-notice laws (such as N.Y. Civil Rights Law § 52-c, Conn. Gen. Stat. § 31-48d and Del. Code tit. 19, § 705), notices at collection under Data Protection Laws and any duty to bargain with a union, and will describe these features accurately.

8.5 Limitation

THE WORKFORCE FEATURES AND THE TAX FEATURES ARE NOT A PAYROLL SERVICE OR CERTIFIED TIMEKEEPING SYSTEM. PROVIDER HAS NO LIABILITY FOR ANY EMPLOYMENT DECISION OR WAGE PAYMENT BASED ON THEM, AND CUSTOMER WILL INDEMNIFY THE PROVIDER INDEMNITEES AGAINST ANY CLAIM BY A WORKER, UNION OR AUTHORITY ARISING FROM ITS USE OF THEM.

8.6 Payment Records and Tax Features

In plain terms. If you turn the tax features on, RelioHub keeps a record of what you paid each person, collects their W-9 or W-4 with an electronic signature, suggests withholding for employees, and prepares the 1099-NEC, W-2 and W-3 forms and upload files for you. You stay the payer and the employer: you check every number, decide who is a contractor or an employee, withhold and deposit taxes, and file and deliver the forms yourself. We protect taxpayer numbers with encryption and strict access, and we will tell you promptly if something goes wrong.

(a) Turning them on. The Tax Features are off until an Administrator turns them on after accepting this version of the Agreement. Payment records (without Tax Identification Data) may be available without turning on the rest of the Tax Features.

(b) What Provider does. Provider supplies software that (i) records payments Customer reports having made outside the Service, including an optional image of a check or of a transfer or Zelle receipt; unless the Service reads the image with high confidence as a transfer or Zelle receipt, it blacks out, before storage, the bottom of the image and the line where it locates a check’s bank routing and account numbers (the MICR line), an automated step that may not cover every number; it stores an image it reads as a transfer or Zelle receipt without that blackout, so Customer will not upload any image that shows a full bank account or routing number (long account-like numbers the Service reads from an image are masked to their last four digits in the details it records); (ii) lets Workers submit Forms W-9 and W-4 electronically under penalties of perjury, or lets Customer record paper forms; (iii) suggests federal Social Security, Medicare and income-tax withholding from published IRS tables and the Worker’s Form W-4; and (iv) prepares Forms 1099-NEC, W-2 and W-3, recipient and payer copies, and electronic files formatted for the IRS Information Returns Intake System and the Social Security Administration. Tables, form text and file layouts change every year and may be wrong or out of date.

(c) What Provider does not do. PROVIDER IS NOT CUSTOMER’S PAYROLL PROVIDER, TAX RETURN PREPARER, TRANSMITTER, REPORTING AGENT OR TAX ADVISER. PROVIDER DOES NOT FILE ANY RETURN, FURNISH ANY STATEMENT ON CUSTOMER’S BEHALF EXCEPT AS CUSTOMER DIRECTS THROUGH THE SERVICE, WITHHOLD OR DEPOSIT ANY TAX, MOVE ANY MONEY TO WORKERS, VERIFY ANY TAXPAYER IDENTIFICATION NUMBER WITH THE IRS, OR DETERMINE WHETHER A WORKER IS AN EMPLOYEE OR AN INDEPENDENT CONTRACTOR.

(d) Customer’s responsibilities. Customer alone is responsible for: classifying each Worker; the accuracy and completeness of every payment, wage and withholding amount, including any suggestion it accepts; obtaining Forms W-9 and W-4 and keeping them as the law requires; backup withholding; depositing and reporting employment taxes (including Forms 941 and 940); state and local withholding, filing and reporting; filing every return and furnishing every statement correctly and on time; obtaining any Transmitter Control Code or Social Security Administration credential it needs; and giving Workers every notice and obtaining every consent the law requires, including consent to receive statements electronically. Customer will review every form and file before filing or furnishing it. A Worker who receives a form electronically must sign in to the Service to view it. A form the Service recorded as furnished electronically, whose notice to the Worker did not bounce, stays available to that Worker to view and download through its access period: October 15 of the year after the form’s tax year, or the next business day when that date falls on a Saturday, Sunday or legal holiday, or, for a corrected form, ninety (90) days after it was furnished if that is later. It stays available even if the Worker withdraws consent to electronic delivery, Customer switches off electronic delivery, the Worker is deactivated, Customer’s Account no longer has a Plan that includes the Tax Features or an active Trial, or Customer’s Account is suspended or the Agreement ends. While the Worker is deactivated or the Account lacks such a Plan or Trial, is suspended or has ended, the Tax Features show the Worker only the forms still within their access period (and, if the Worker is deactivated or the Account is suspended or has ended, the Service shows the Worker nothing else), and a deactivated Worker’s sign-in is disabled after the last of those access periods ends. The Worker cannot view the form, even within its access period, if the Worker asked to delete their account or held administrative or supervisory privileges when deactivated; once the form no longer matches the payments recorded for its tax year (for example, after Customer voids a payment) or Customer replaces it with a corrected form; while Provider limits the Tax Features until an Administrator accepts a new version of the Agreement (Section 21.2) or the Tax Features are otherwise unavailable; or if the Worker cannot sign in for any other reason, which may include a Worker deactivated before this version of the Agreement took effect, until an Administrator applies the deactivation again. The Service does not then prompt Customer to mail a form it already furnished electronically, and while the Account lacks a Plan that includes the Tax Features or an active Trial, is suspended or has ended, Customer cannot print the form from the Service either. Customer is responsible for furnishing a paper copy to a Worker who cannot view a form through its access period (including when the notice bounced) and in every other case the law requires one, should keep its own copy of every form it furnishes, and should not deactivate a Worker who holds administrative or supervisory privileges before that date unless it furnishes the paper copy.

(e) Security of Tax Identification Data. Provider encrypts Tax Identification Data with keys kept outside the database, limits who can see a Worker’s taxpayer identification number in full to Customer’s Administrators who re-enter their password and state a reason (Customer’s own employer identification number is printed in full where the law requires it, including on the copies furnished to Workers and in the files for the IRS and the Social Security Administration), records every such access in an audit trail, excludes Tax Identification Data from logs, notifications, AI processing and the MCP Server, and does not let Platform Personnel or support sessions view it. If Provider determines that Tax Identification Data in its custody was acquired without authorization, it will notify Customer without unreasonable delay and give Customer the information reasonably available to help it meet its own notification duties; Customer, as the owner of the data, is responsible for notifying affected individuals and authorities unless the parties agree otherwise in writing.

(f) Retention. Provider keeps Tax Identification Data and signed forms for at least four years after the later of the Worker’s last recorded payment and the due date of the last return that relies on them, and then deletes the Worker’s full taxpayer identification number and any scan of a paper form, keeping the rest of the signed form (including the name, address, last four digits of the number and the signature record) as the record of what the Worker certified, as described in the Privacy Policy. Within a reasonable time after the Agreement ends and every retention period for Customer’s tax records described in the Privacy Policy has passed, Provider will destroy Customer’s encryption keys for Tax Identification Data, after which any remaining encrypted copies can no longer be read. Copies may persist in encrypted backups for a limited period.

(g) Limitation. PROVIDER DOES NOT WARRANT THAT ANY WITHHOLDING SUGGESTION, FORM, COPY OR FILE IS ACCURATE, COMPLETE, TIMELY OR ACCEPTED BY ANY AUTHORITY, AND HAS NO LIABILITY FOR ANY TAX, PENALTY, INTEREST OR CLAIM ARISING FROM CUSTOMER’S USE OF THE TAX FEATURES, INCLUDING LATE OR INCORRECT FILING, MISCLASSIFICATION OR FAILURE TO WITHHOLD OR DEPOSIT, EVEN IF THE LOSS ARISES IN WHOLE OR IN PART FROM THE NEGLIGENCE OF PROVIDER, EXCEPT TO THE EXTENT CAUSED BY PROVIDER’S BREACH OF SECTION 8.6(e). CUSTOMER WILL INDEMNIFY THE PROVIDER INDEMNITEES AGAINST ANY SUCH CLAIM.

9. Invoicing, Quotes and Online Payments

In plain terms. RelioHub helps you prepare quotes and invoices and get paid online, but your business issues those documents and gets paid. Payments run through your own Stripe account and go straight to you; we never hold the money. The setting that adds an estimated processing fee to your client’s payment is on by default, so decide before accepting online payments whether it is lawful for you to keep it.

9.1 Customer Is the Issuer

Every quote and invoice is issued by Customer to its Clients. Provider is not a party to any transaction, contract or payment arrangement between Customer and its Clients or Payers (a “Customer Transaction”), does not warrant any work, is not a collection agent and does not guarantee payment. All document content, including prices, payment terms, the “Agreements” text Customer writes (which the Service may carry from a quote into its invoice), the Payer acceptance statement (including default wording Customer keeps) and Client data, is Customer’s responsibility, as is compliance with contractor-licensing, home-improvement contract, lien-notice, consumer-protection, rescission, prompt-payment and Tax laws. Templates and defaults are not legal advice. Customer must review each document before sending it; a sent invoice cannot be changed, and only drafts may be deleted.

9.2 Quotes and Quote Signatures

(a) Customer’s Users may mark a quote “accepted” or “declined” themselves; that status is Customer’s own record and is not an electronic signature or evidence of a contract. Quotes cannot currently be paid online.

(b) On Plans that include it, a quote sent with online signing enabled lets the Client, through its Payment Link, accept and sign the quote electronically by typing a full name, entering an email address, reviewing an electronic-records disclosure and checking a consent box, or decline it with an optional reason. The Service records the typed name, the email entered, the email the link was sent to, the time, the IP address, the user agent and device, the approximate country, the disclosure and consent text shown, and a copy of the quote content as signed with its SHA-256 fingerprint (a “Quote Signature Record”); marks the quote accepted or declined; and emails a signed copy to the signer and to Customer. A signed quote cannot be reopened or edited; a change requires a new quote. A link sent while signing was available remains signable until it expires or is revoked, even if Customer’s Plan changes.

(c) A signature is between Customer and its Client. Provider is not a party to any quote or any contract resulting from it, does not verify the signer’s identity or authority, and only records the evidence described above. Customer remains solely responsible for deciding whether an electronic signature is sufficient for its contract and for every formality the law requires, including consumer consent and disclosures under 15 U.S.C. § 7001(c) where other law requires information to be given in writing, home-improvement and home-solicitation contract requirements, notices of cancellation or rescission rights (such as the Federal Trade Commission’s three-day cooling-off rule and state equivalents), lien notices, and any document the law requires to be signed in ink, witnessed or notarized. Customer must obtain and keep its Clients’ agreement in the form the law requires.

(d) PROVIDER DOES NOT WARRANT THAT ANY QUOTE SIGNATURE RECORD IS A VALID OR ENFORCEABLE ELECTRONIC SIGNATURE, PROVES IDENTITY OR AUTHORITY, CREATES A CONTRACT, SATISFIES ANY WRITING, DISCLOSURE OR CANCELLATION REQUIREMENT, OR WILL PERSUADE ANY COURT OR ARBITRATOR.

9.3 Payment Services; Merchant of Record

(a) The Payment Services are provided by Stripe under the Stripe Terms, to which Provider is not a party. Stripe verifies Customer and decides whether to approve, restrict or close the Connected Account; Provider stores only its identifier and status.

(b) PAYMENTS THROUGH PAY PAGES ARE DIRECT CHARGES ON CUSTOMER’S CONNECTED ACCOUNT, AND CUSTOMER IS THE MERCHANT OF RECORD. PROVIDER NEVER RECEIVES, HOLDS OR TRANSMITS CLIENT FUNDS AND IS NOT A BANK, MONEY TRANSMITTER, PAYMENT PROCESSOR OR FIDUCIARY. Stripe’s fees are charged directly to Customer. Provider currently charges no fee on Pay Page payments.

(c) Provider has no liability for any act of Stripe, including holds, reserves, reversals or account closures. Customer bears all losses, fees and fines on its Connected Account, including fraud, refunds, disputes and chargebacks.

(d) Customer authorizes and directs Provider to create or link the Connected Account; share with Stripe the information needed to operate it (including Customer’s business details, invoice data and the Client’s bill-to email for receipts); manage payment intents; act on Stripe notifications; and compile and submit dispute evidence under Section 9.6.

(a) Payment methods depend on Stripe and Customer’s settings. Cards may require 3D Secure. Bank payments may use Stripe Financial Connections, which may check the Payer’s balance and lead the Service to refuse an apparently unfunded payment. Payers enter card and bank details only in Stripe-hosted fields, and Customer must never record them elsewhere.

(b) ANY PERSON WHO HOLDS A PAYMENT LINK CAN, WITHOUT SIGNING IN, VIEW, DOWNLOAD, PAY OR SIGN THE INVOICE OR QUOTE IT OPENS until the link expires or is revoked. Links currently last at least 60 days (or 30 days past the due date, if later) and 90 days after payment or signature, and keep working while the Account is suspended and after termination. Customer is solely responsible for recipients, forwarding, revocation and every payment made through its links.

9.5 Payment Acceptance Records

Before paying, a Payer may be asked to type a name and confirm Customer’s acceptance statement, which expresses terms between the Payer and Customer, not Provider. The Service records the typed name, the statement, amounts, payment method, user agent, approximate country and time (a Payment Acceptance Record). PROVIDER DOES NOT WARRANT THAT ANY PAYMENT ACCEPTANCE RECORD IS A VALID ELECTRONIC SIGNATURE, PROVES IDENTITY OR ACCEPTANCE OF WORK, CREATES A CONTRACT, OR WILL PERSUADE STRIPE, A CARD NETWORK, COURT OR ARBITRATOR.

9.6 Disputes and Refunds

Customer is solely responsible for all disputes, chargebacks and refunds on its Connected Account; refunds to Clients are issued by Customer through Stripe. When Stripe reports a dispute, Customer authorizes Provider to compile evidence automatically (which may include invoices, receipts, the Payment Acceptance Record, delivery and payment history, project photo and report counts and the Client’s name and email), disclose it to Stripe, card networks and issuers, stage it for Customer’s review and, unless Customer submits first, submit it automatically before Stripe’s deadline (currently about 48 hours before). Customer remains responsible for reviewing and supplementing evidence. PROVIDER DOES NOT GUARANTEE THAT EVIDENCE WILL BE SUBMITTED OR SUFFICIENT, OR ANY DISPUTE OUTCOME.

9.7 Processing Fee Pass-Through

(a) THE PROCESSING FEE PASS-THROUGH IS ENABLED BY DEFAULT AND ADDS AN ESTIMATED PROCESSING FEE TO WHAT PAYERS PAY FOR CERTAIN METHODS. CUSTOMER MUST DECIDE, BEFORE ACCEPTING ONLINE PAYMENTS, WHETHER TO KEEP IT. KEEPING IT IS CUSTOMER’S OWN ELECTION ON ITS OWN LEGAL ADVICE, AND THE DEFAULT IS NOT A REPRESENTATION THAT SURCHARGING IS LAWFUL.

(b) Customer is solely responsible for state surcharge and convenience-fee laws (some of which prohibit card surcharges), card network and Stripe rules (including notice, caps and the ban on surcharging debit and prepaid cards) and disclosure requirements, and must disable the setting wherever a fee is unlawful. The feature is currently designed to apply only to credit card and bank payments, cap the card fee (currently at 3 percent) and show the fee before payment; amounts are estimates of Stripe’s standard US pricing, and Provider does not warrant card classification or legal compliance.

(c) CUSTOMER WILL INDEMNIFY THE PROVIDER INDEMNITEES AGAINST ANY CLAIM, FINE OR LOSS ARISING FROM ANY FEE CHARGED THROUGH THE PROCESSING FEE PASS-THROUGH, INCLUDING BECAUSE IT WAS LEFT ENABLED, EVEN IF CAUSED IN WHOLE OR IN PART BY THE NEGLIGENCE OF ANY PROVIDER INDEMNITEE, INCLUDING IN SELECTING THE DEFAULT.

9.8 Taxes on Customer’s Documents

Customer enters one tax rate per document manually; the Service does not determine taxability or calculate taxes. Customer is solely responsible for all taxes on its Customer Transactions.

10. AI Features

In plain terms. RelioHub uses AI to make your documents searchable, answer questions about them, transcribe voice notes, read receipts and help you write. Some of your content is sent automatically to outside AI services we choose, which may be outside the United States. AI can be wrong, so please check what it produces before relying on it or sending it to a client.

10.1 Automatic Processing

Every supported document uploaded is automatically indexed: its text is extracted, segmented and sent to an AI Provider to create embeddings. The Service may also send AI Providers queries, questions with document excerpts, full documents for enrichment, transcripts, quote and invoice content for summaries, receipt images submitted for expense extraction, and Company Rules. THE AI FEATURES ARE NOT OPT-IN AND HAVE NO PER-ACCOUNT OPT-OUT; BY UPLOADING CONTENT OR USING THEM, CUSTOMER INSTRUCTS PROVIDER TO PROCESS IT AS DESCRIBED HERE AND IN SECTION 8 (AI PROCESSING) OF THE PRIVACY POLICY. Customer must not upload content it does not want so processed.

10.2 AI Providers, Location and Retention

Provider selects AI Providers and models in its sole discretion and may change them without notice; current ones are listed in Sections 7 (Subprocessors) and 8 (AI Processing) of the Privacy Policy. Audio is currently transcribed on systems operated by or for Provider by default, but a third-party provider may be used. AI Providers may process Input outside the United States, including in the People’s Republic of China, and Customer consents to that transfer (Section 12 (Where Data Is Processed) of the Privacy Policy). PROVIDER MAKES NO REPRESENTATION THAT AI PROVIDERS WILL NOT RETAIN, REVIEW OR TRAIN ON INPUT OR OUTPUT, WHICH THEIR OWN TERMS GOVERN.

10.3 Output; No Reliance

OUTPUT MAY BE INACCURATE, INCOMPLETE, MISLEADING OR NOT UNIQUE, AND MAY MISSTATE CUSTOMER’S DOCUMENTS OR CITE EXCERPTS THAT DO NOT SUPPORT IT. CUSTOMER MUST REVIEW AND CORRECT ALL OUTPUT BEFORE RELYING ON, SAVING OR SENDING IT. OUTPUT IS NOT ENGINEERING, SAFETY, LEGAL, TAX, PAYROLL OR ESTIMATING ADVICE, MUST NOT BE THE SOLE BASIS FOR ANY SIGNIFICANT DECISION ABOUT AN INDIVIDUAL, AND IS USED AT CUSTOMER’S SOLE RISK, EVEN IF A LOSS ARISES IN WHOLE OR IN PART FROM THE NEGLIGENCE OF PROVIDER OR ANY PROVIDER INDEMNITEE. Invoice and quote summaries are designed so that prices, quantities and Client names are not sent to the AI Provider, but Customer must still check each one. Expense details read from receipts, such as amounts, taxes, dates, merchants and categories, may be wrong or missing, and Customer must review them before confirming or relying on them. EXPENSE RECORDS ARE NOT BOOKKEEPING, ACCOUNTING OR TAX RECORDS OR ADVICE, AND PROVIDER HAS NO LIABILITY FOR ANY REIMBURSEMENT, ACCOUNTING, TAX OR OTHER DECISION BASED ON THEM.

10.4 AI Credits; Prohibited Uses

AI Features are paid from prepaid AI Credits at rates Provider may change for future use; there is no free allowance, and AI Features stop at a zero balance. Provider’s metering is conclusive absent manifest error. Customer will not circumvent AI safeguards or metering (including by prompt injection), generate unlawful or infringing content, submit Prohibited Data, extract models or prompts, or use Output to train competing models, and will obtain every consent the law requires before recording audio.

11. Fees, Trials, Billing, Renewals and Taxes

In plain terms. Try RelioHub free for 30 days without a card. If a card is on file when the trial ends, your subscription starts automatically; otherwise the account becomes read-only until you subscribe. You then pay monthly per Active Worker, plus any storage or invoicing Plan, and AI usage from prepaid credits, in US dollars, until you cancel. Amounts paid are generally not refunded.

11.1 Trial

A Trial currently lasts 30 days and needs no payment method; Provider may limit, extend or end it. If a payment method is on file when it ends, a paid Subscription starts automatically for the Plans and Seats then in effect; otherwise the Account becomes read-only until Customer subscribes and may be closed under Section 16. Reminders are optional.

11.2 Prices, Seats and Plans

Fees are as shown in the Service or at checkout, in US dollars. Billing is currently monthly only; any interval chosen at sign-up is a preference. Seats are billed per Active Worker, minimum one, whether or not the Worker used the Service. Storage and invoicing Plans are billed monthly, and Plan features may change under Sections 4 and 21. Storage quotas use binary units (1 GB = 1,073,741,824 bytes); exceeding one may block uploads but does not delete content.

11.3 Automatic Renewal and Payment Authorization

EACH SUBSCRIPTION RENEWS AUTOMATICALLY FOR SUCCESSIVE BILLING PERIODS (CURRENTLY ONE MONTH), WITHOUT FURTHER NOTICE, UNTIL CANCELLED OR TERMINATED. BY PROVIDING A PAYMENT METHOD, PLACING AN ORDER OR ALLOWING A SUBSCRIPTION TO START AFTER A TRIAL, CUSTOMER AUTHORIZES PROVIDER, AND STRIPE AS ITS PROCESSOR, TO CHARGE THE PAYMENT METHOD ON FILE (OR ANY REPLACEMENT) FOR ALL RECURRING, PRORATED AND OTHER FEES AND TAXES WHEN DUE, INCLUDING AUTO-RECHARGES CUSTOMER ENABLES, BY OFF-SESSION CHARGES AND WITHOUT FURTHER CONSENT, UNTIL ALL AMOUNTS ARE PAID. Customer will keep a valid payment method on file. Plan changes take effect immediately with the prorated difference charged at once; Seats sync automatically with Active Workers and added Seats are prorated at the next renewal; credits apply only to future Fees and are never paid in cash.

11.4 AI Credits

AI Credits are sold in the amounts offered (currently $10, $25 or $50). IF CUSTOMER ENABLES AUTO-RECHARGE, IT AUTHORIZES OFF-SESSION CHARGES OF THE SELECTED AMOUNT EACH TIME THE BALANCE FALLS BELOW THE THRESHOLD (CURRENTLY $5), POSSIBLY SEVERAL TIMES PER PERIOD, UNTIL IT DISABLES AUTO-RECHARGE. A declined recharge disables it. AI Credits have no cash value, are not transferable, are non-refundable except under Section 16.3(b) or as law requires, and are forfeited when the Agreement ends.

11.5 Complimentary Entitlements; Price Changes

Complimentary Plans, coupons, credits and Trial extensions are discretionary and revocable. Provider may change prices on at least 30 days’ notice before an increase in recurring Fees, effective from the next Billing Period after the notice period; continued use is acceptance.

11.6 Late Payments and Billing Disputes

(a) If a payment fails, Provider may allow a grace period (currently 7 days). Afterward, the Account may become read-only, and continued non-payment may lead to cancellation, suspension of all access and termination. Fees continue to accrue during read-only status and suspension. Overdue amounts bear interest at the lesser of 1.5 percent per month and the maximum lawful rate; any interest above the rate permitted by law, including Chapter 303 of the Texas Finance Code, is unintended and will be credited or refunded. Customer will reimburse reasonable collection costs, and Provider may set off amounts owed.

(b) Customer must dispute a charge in good faith, at legal@reliohub.com or by support ticket titled “Billing Dispute”, within ninety (90) days, or it is final to the extent the law permits. Customer will not initiate a chargeback of Fees without first raising the dispute with Provider.

11.7 Cancellation

Customer may cancel through the Stripe billing portal, where it offers cancellation, or by an Administrator’s support ticket expressly requesting it. Cancellation normally takes effect at the end of the current Billing Period, whose Fees remain due. Choosing free Plans does not cancel the Seat subscription. AFTER CANCELLATION TAKES EFFECT, ALL ACCESS, INCLUDING READ ACCESS, MAY END; CUSTOMER MUST DOWNLOAD BEFOREHAND ANYTHING IT WANTS TO KEEP.

11.8 No Refunds

ALL FEES ARE NON-REFUNDABLE AND ALL PAYMENTS ARE FINAL, EXCEPT WHERE THE LAW REQUIRES OTHERWISE. NO REFUND OR CREDIT IS GIVEN FOR PARTIAL PERIODS, UNUSED SEATS, PLANS OR AI CREDITS, OR ON CANCELLATION, DOWNGRADE, SUSPENSION OR TERMINATION, OTHER THAN AUTOMATIC CREDITS UNDER SECTION 11.3 AND ANY REFUND UNDER SECTION 16.3(b). A DISCRETIONARY REFUND CREATES NO OBLIGATION TO GIVE ANOTHER.

11.9 Taxes on Fees

Fees exclude Taxes, which Customer will pay. Provider may begin collecting Taxes whenever it determines it must (for example, Texas sales and use tax on data processing services), and that is not a price increase. Customer will gross up any required withholding and reimburse any Taxes later assessed on past Fees.

12. Third-Party Services and Integrations

In plain terms. RelioHub works with other companies’ services, such as Stripe, app stores, maps and AI assistants you connect through MCP. We cannot control them, and data an outside tool reads leaves RelioHub and becomes your responsibility.

12.1 Generally

Third-Party Services are governed by their own terms. PROVIDER DOES NOT WARRANT ANY THIRD-PARTY SERVICE, IS NOT LIABLE FOR ITS ACTS OR DATA HANDLING, AND MAY CHANGE OR END ANY INTEGRATION WITHOUT REFUND. Maps must not be used for surveying, boundary, utility or safety purposes, and geocoding may be wrong.

12.2 MCP Clients

Customer is responsible for every MCP Grant, including one that may be created for the Account Creator at sign-up. A connected MCP Client may read, change and delete Customer Data and take actions (including sending documents to Clients) with the connecting User’s permissions; its actions are Customer’s, and data it retrieves leaves the Service as Customer’s own disclosure. Provider is not responsible for any MCP Client, including actions caused by errors or prompt injection. Provider logs MCP calls, including arguments that may contain Customer Data, and may limit or end MCP access at any time.

12.3 Mobile App and App Stores

The Mobile App may be distributed through Apple’s App Store, Google Play or other app stores (each, an “App Store”) under an account held by Provider or another entity on its behalf (Section 24). The Agreement is with Provider only; Provider, not the App Store operator, is responsible for the Mobile App, its support, any non-disclaimed warranty and any claim about it, including product-liability, legal-compliance, consumer-protection and intellectual-property claims. For Apple, the license covers Apple devices the User owns or controls; Apple’s only warranty obligation is to refund any purchase price (the app is currently free). Customer represents that no User is in a US-embargoed country or on a US restricted-party list. Apple and its subsidiaries are third-party beneficiaries entitled to enforce the Agreement as it relates to the Mobile App.

13. Intellectual Property and Restrictions

In plain terms. Your data belongs to you, and the software belongs to us. Please do not copy it, take it apart, resell it or use it to build a competitor.

13.1 Ownership and Restrictions

(a) Provider and its licensors own the Service, the Mobile App, the Documentation, all underlying technology, Usage Data, Aggregated Data, all improvements (including those based on Feedback) and the RelioHub marks. The Service is licensed, not sold. Customer’s Users may install the Mobile App on devices they control to use the Service for Customer while the Agreement is in effect.

(b) Customer will not, and will not permit anyone to, reverse engineer the Service except as the law expressly permits; copy, modify, frame or resell it; use it to build or benchmark a competing product (competitors may not use it without consent); publish benchmark or security tests; remove proprietary notices; or circumvent any security, device-identity, geofencing, rate-limit or metering measure. Any breach is material.

Provider may identify Customer by name and logo as a customer until Customer withdraws permission at legal@reliohub.com. Copyright notices and counter-notices meeting 17 U.S.C. § 512(c)(3) and (g)(3) go to the Copyright Agent, NORTHMARK MANAGEMENT GROUP LLC, at legal@reliohub.com. Provider may remove material without liability, may restore it no sooner than ten (10) business days after a valid counter-notice unless suit is filed, and may terminate repeat infringers.

14. Confidentiality

In plain terms. Each of us will keep the other’s non-public information private and use it only for this relationship. Your data also has the protections in Sections 5 and 6 and our Privacy Policy.

The receiving party will use the other’s Confidential Information only under the Agreement, protect it with at least reasonable care, and share it only with personnel, Affiliates, advisers and (for Provider) Platform Personnel, Subprocessors, AI Providers and prospective acquirers or investors who are bound by confidentiality, remaining responsible for them. Public, previously known, independently developed or rightfully received information is excluded. Disclosure required by law is permitted, with prior notice where lawful (Section 6.10(c) governs Customer Data). These duties last three (3) years after termination, and longer for trade secrets and retained Customer Data. Customer Data is governed by Sections 5, 6 and 16 and the Privacy Policy, which prevail, and residual copies in backups and logs need not be purged early. Either party may seek injunctive relief as Section 20.5 permits.

15. Security

In plain terms. We protect your data with commercially reasonable safeguards that we keep improving, but no online service is perfectly secure, so we do not overpromise. If we learn of a security incident affecting your data, we will tell you without undue delay.

15.1 Safeguards

Provider maintains commercially reasonable administrative, technical and physical safeguards designed to protect Customer Data. By way of illustration only, they currently include TLS in transit (terminated at a Subprocessor’s edge, so not end-to-end), origin servers reachable only through a private tunnel, secure httpOnly session cookies with device-bound refresh, rate limiting, role-based access, logical separation of each Customer’s data in the application, and backups (Section 5.5). See Section 11 (Security) of the Privacy Policy.

15.2 No Guarantee

PROVIDER DOES NOT GUARANTEE THAT CUSTOMER DATA WILL BE FREE FROM UNAUTHORIZED ACCESS. UNLESS A NEGOTIATED ORDER FORM SAYS OTHERWISE, PROVIDER DOES NOT REPRESENT THAT DATA IS ENCRYPTED AT REST; THAT MULTI-FACTOR AUTHENTICATION OR STRONG PASSWORD RULES ARE AVAILABLE (THEY ARE NOT AS OF THE EFFECTIVE DATE); THAT DATA IS ISOLATED AT THE DATABASE OR PHYSICAL LEVEL; THAT BACKUPS WILL RESTORE ANY DATA; THAT LOGS ARE COMPLETE OR TAMPER-PROOF; THAT LINKS WILL NOT APPEAR IN TECHNICAL LOGS; OR THAT DATA WILL STAY IN ANY LOCATION. Customer will manage access on a least-privilege basis, secure its devices and links, report suspected compromise, and not test the Service’s security without written consent; vulnerabilities may be reported to privacy@reliohub.com.

15.3 Security Incidents

Provider will notify Customer without undue delay after becoming aware of a Security Incident affecting Customer Data, and within any shorter period the law requires of Provider (including Tex. Bus. & Com. Code § 521.053 where applicable), describing what is then known, and will take commercially reasonable steps to contain it and reasonably assist Customer. Customer decides on and gives notices to its Workers, Clients and regulators unless the law requires Provider to. Notification is not an admission of fault, each party bears its own costs except as law requires, and access caused by compromised User credentials, Customer’s acts, shared links or Third-Party Services Customer chose is not Provider’s responsibility. This Section and Section 15 (Security Incident Notification) of the Privacy Policy state Provider’s sole notification obligations.

16. Suspension, Termination and Data After Termination

In plain terms. You may cancel whenever you wish. We may end the relationship for any reason with 30 days’ notice, or sooner for serious reasons, and may pause access right away for non-payment or security risk. There is no export tool, so please download what you need before your account ends. We may delete your data starting 30 days afterward; anything we keep stays confidential and is never sold.

16.1 Suspension

Provider may suspend all or part of the Service immediately, with or without notice, if it reasonably believes that Fees are overdue, the Agreement has been breached, the Account poses a security risk or is used for fraud, use may harm Provider or others, the law requires it, a chargeback of Fees has been initiated, or Stripe or another essential provider requires it. A suspended Account may be blocked from all access, including viewing and downloading, except a Worker’s access to tax forms furnished electronically under Section 8.6(d), and Fees continue to accrue. PROVIDER HAS NO LIABILITY FOR ANY SUSPENSION IMPOSED IN GOOD FAITH.

16.2 Cancellation by Customer

Customer may cancel under Section 11.7, and the Agreement ends when the cancellation takes effect.

16.3 Termination by Provider

(a) Provider may terminate for any reason on at least thirty (30) days’ notice, effective at the end of the then-current Billing Period, and on notice if a Trial ended unpaid or a Subscription lapsed. Provider may terminate immediately for breach of Section 7, Section 13 or payment obligations, and on notice for any other material breach not cured within ten (10) days. Either party may terminate if the other becomes insolvent.

(b) If Provider terminates for convenience, it will refund the unused balance of purchased (not complimentary) AI Credits, as Customer’s sole remedy.

16.4 Effect; Customer Data After Termination

(a) On termination, all access ends, including read access and the Mobile App license, except a Worker’s access to tax forms furnished electronically under Section 8.6(d); accrued Fees become due; and AI Credits are forfeited except under Section 16.3(b). Provider has no obligation to provide any export or copy of Customer Data, except as Data Protection Laws require, but may offer paid retrieval assistance at its discretion if asked promptly.

(b) PROVIDER HAS NO OBLIGATION TO RETAIN CUSTOMER CONTENT AFTER TERMINATION (EXCEPT THE TAX RECORDS THAT SECTION 8.6(f) REQUIRES PROVIDER TO KEEP) AND MAY DELETE IT AT ANY TIME AFTER THIRTY (30) DAYS FOLLOWING TERMINATION, OR SOONER IF LAW REQUIRES, WITHOUT FURTHER NOTICE AND WITHOUT LIABILITY. Provider is not obliged to delete within any period and offers no post-termination access other than a Worker’s access under Section 8.6(d).

(c) Provider may retain Customer Data, Account Data and Usage Data as long as reasonably necessary for legal compliance, claims, security, fraud prevention and audit, and as business records (including issued invoices, payment, dispute and acceptance records, Quote Signature Records, audit logs, email records and support tickets). Residual copies in backups, logs, caches and storage versions may persist until they age out. Retained data stays subject to Section 14 and the Privacy Policy, including Sections 10 (Retention and Deletion) and 13 (Your Rights and Choices).

(d) Payment Links may remain usable until they expire unless Customer revokes them first, and Customer remains responsible for payments through them. Termination does not affect the Connected Account.

16.5 Survival

Every provision that by its nature should survive does so, including Sections 1.2 through 1.4, 2, 3.1(c), 3.2, 5 (except Customer’s right to use the Service), 6, 7, 8.2, 8.5, 9, 10.2, 10.3, 11 (for accrued amounts), 12 through 15, and 16 through 24.

17. Disclaimers of Warranties

In plain terms. We work hard to make RelioHub dependable, but software is never perfect, so we provide it as it is. Please keep your own copies of important records, check time, pay, invoice and AI results before relying on them, and look to your own advisers for legal, tax and payroll questions.

17.1 Service Provided “As Is”

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE SERVICE, ALL OUTPUT, THE DOCUMENTATION, BETA FEATURES AND THIRD-PARTY SERVICES ARE PROVIDED “AS IS”, “AS AVAILABLE” AND “WITH ALL FAULTS”. PROVIDER, FOR ITSELF AND EACH PROVIDER INDEMNITEE, SUBPROCESSOR AND LICENSOR, DISCLAIMS ALL WARRANTIES, EXPRESS, IMPLIED OR STATUTORY, INCLUDING MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE, NON-INFRINGEMENT, ACCURACY AND THOSE ARISING FROM COURSE OF DEALING OR USAGE OF TRADE. NO STATEMENT BY PROVIDER, ITS PERSONNEL, THE WEBSITES OR MARKETING CREATES ANY WARRANTY. THESE DISCLAIMERS APPLY EVEN IF A DEFECT OR LOSS ARISES FROM THE SOLE, JOINT OR CONCURRENT NEGLIGENCE OR STRICT LIABILITY OF PROVIDER OR ANY PROVIDER INDEMNITEE.

17.2 Specific Disclaimers

WITHOUT LIMITING SECTION 17.1, PROVIDER DOES NOT WARRANT THAT THE SERVICE WILL BE UNINTERRUPTED, SECURE OR ERROR-FREE; THAT DATA WILL NOT BE LOST OR THAT ANY BACKUP WILL RESTORE IT; THAT ANY TIME RECORD, LOCATION, DEVICE SIGNAL, ESTIMATED PAY, OUTPUT, TAX OR TOTAL IS ACCURATE; THAT ANY EMAIL OR NOTICE WILL BE DELIVERED; THAT ANY PAYMENT ACCEPTANCE RECORD, QUOTE SIGNATURE RECORD OR SURCHARGE IS LAWFUL OR EFFECTIVE OR ANY DISPUTE WILL BE WON; THAT LINKS WILL BE USED ONLY BY INTENDED RECIPIENTS; OR THAT THE SERVICE WILL ENABLE CUSTOMER TO COMPLY WITH ANY LAW, CODE, LICENSING REQUIREMENT, CARD NETWORK RULE OR RECORD-RETENTION OBLIGATION. The disclaimers in Sections 4, 5.5, 8, 9, 10, 12 and 15 form part of this Section 17.

17.3 No Professional Advice; Exclusive Remedy

The Service is a software tool. Nothing in it, in any Output, template or default (such as acceptance statements, Agreements templates, tax rates, processing-fee settings or shift-closure thresholds), or from Platform Personnel is legal, tax, accounting, payroll, employment, engineering or safety advice, and Customer is solely responsible for its own decisions and advice. Nothing in the Agreement waives a right that cannot lawfully be waived; any warranty that cannot be disclaimed is limited to the minimum scope and duration allowed. Statements that a feature is designed to work in a certain way describe intended practice, not warranties. CUSTOMER’S SOLE AND EXCLUSIVE REMEDY FOR DISSATISFACTION WITH THE SERVICE IS TO STOP USING IT AND CANCEL.

17.4 Waiver of Consumer Rights

I WAIVE MY RIGHTS UNDER THE DECEPTIVE TRADE PRACTICES-CONSUMER PROTECTION ACT, SECTION 17.41 ET SEQ., BUSINESS & COMMERCE CODE, A LAW THAT GIVES CONSUMERS SPECIAL RIGHTS AND PROTECTIONS. AFTER CONSULTATION WITH AN ATTORNEY OF MY OWN SELECTION, I VOLUNTARILY CONSENT TO THIS WAIVER. Here, “I” and “my” mean Customer, which represents that it is not in a significantly disparate bargaining position and has had the opportunity to be represented by counsel not selected by Provider. If this waiver is unenforceable, Sections 17, 18 and 23.1 still apply to the fullest extent permitted.

18. Limitation of Liability

In plain terms. This Section significantly limits what you can recover from us, even if we are at fault. We are not responsible for indirect losses such as lost profits or lost data, our total responsibility is capped at what you paid us in the twelve months before the problem (or $100, if more), and claims must be brought promptly. These limits allow us to offer RelioHub at its price, and they do not reduce rights the law says cannot be limited.

18.1 Exclusion of Damages

TO THE MAXIMUM EXTENT PERMITTED BY LAW, NEITHER PROVIDER NOR ANY PROVIDER INDEMNITEE WILL BE LIABLE, UNDER ANY THEORY (CONTRACT, WARRANTY, TORT INCLUDING NEGLIGENCE, STRICT LIABILITY, STATUTE OR OTHERWISE), FOR ANY (a) INDIRECT, INCIDENTAL, SPECIAL, CONSEQUENTIAL, EXEMPLARY OR PUNITIVE DAMAGES; (b) LOST PROFITS, REVENUE, BUSINESS, CONTRACTS OR GOODWILL; (c) LOSS, CORRUPTION OR UNAVAILABILITY OF DATA, OR COST OF RECOVERING IT; (d) BUSINESS INTERRUPTION OR PROJECT DELAY; (e) COST OF SUBSTITUTE SERVICES; (f) WORKER WAGES OR PENALTIES, UNCOLLECTED INVOICES, CHARGEBACKS, STRIPE FEES OR CUSTOMER’S TAXES; OR (g) DAMAGES CAUSED BY UNAUTHORIZED ACCESS OR BY ANY THIRD PARTY, INCLUDING SUBPROCESSORS, AI PROVIDERS, MCP CLIENTS AND STRIPE; WITH (b) AND (c) EXCLUDED WHETHER DIRECT OR INDIRECT, AND ALL EXCLUDED EVEN IF FORESEEABLE.

18.2 Cap

TO THE MAXIMUM EXTENT PERMITTED BY LAW, THE TOTAL AGGREGATE LIABILITY OF PROVIDER AND ALL PROVIDER INDEMNITEES TOGETHER, ARISING OUT OF OR RELATING TO THE AGREEMENT OR THE SERVICE, WILL NOT EXCEED THE GREATER OF (a) THE FEES CUSTOMER ACTUALLY PAID TO PROVIDER FOR THE SERVICE IN THE TWELVE (12) MONTHS BEFORE THE EVENT GIVING RISE TO THE CLAIM, OR (b) US $100. THIS IS ONE AGGREGATE CAP FOR ALL CLAIMS AND CLAIMANTS, AND ANY AMOUNT PAID REDUCES IT. Fees actually paid are net of refunds and chargebacks and exclude Taxes and Client payments.

18.3 Scope

THESE LIMITATIONS PROTECT, AND MAY BE ENFORCED BY, EACH PROVIDER INDEMNITEE AND SUBPROCESSOR. THEY ARE AN ESSENTIAL BASIS OF THE BARGAIN, ARE REFLECTED IN THE FEES, APPLY EVEN IF A LIMITED REMEDY FAILS OF ITS ESSENTIAL PURPOSE, AND, TO THE MAXIMUM EXTENT PERMITTED BY LAW, APPLY EVEN IF THE LOSS ARISES IN WHOLE OR IN PART FROM THE SOLE, JOINT, CONCURRENT OR COMPARATIVE NEGLIGENCE OR STRICT LIABILITY OF PROVIDER OR ANY PROVIDER INDEMNITEE. They do not limit Customer’s payment obligations, its obligations under Section 19, or its liability for breach of Sections 7 or 13. Nothing excludes liability that cannot lawfully be excluded; if any part of this Section is unenforceable, liability is limited to the maximum extent permitted, and each limitation is severable.

18.4 Time Limit for Claims

TO THE MAXIMUM EXTENT PERMITTED BY LAW, ANY CLAIM AGAINST PROVIDER OR ANY PROVIDER INDEMNITEE ARISING OUT OF OR RELATING TO THE AGREEMENT OR THE SERVICE MUST BE COMMENCED WITHIN ONE (1) YEAR AFTER IT ACCRUES OR IT IS PERMANENTLY BARRED, EXCEPT THAT FOR ANY CLAIM ON THE AGREEMENT FOR WHICH TEX. CIV. PRAC. & REM. CODE § 16.070 OR OTHER LAW FORBIDS A PERIOD SHORTER THAN TWO (2) YEARS, THE PERIOD IS TWO (2) YEARS. The period is tolled during the process in Section 20.1.

19. Indemnification by Customer

In plain terms. You control what goes into your account and how you use it with your workers and clients, so you agree to stand behind those choices. If someone brings a claim against us because of your data, your use of RelioHub, your dealings with workers or clients, or a breach of these terms, you will defend us and cover the costs, unless we were grossly negligent, acted willfully or caused a security incident by breaching our security commitment.

19.1 Indemnity

TO THE MAXIMUM EXTENT PERMITTED BY LAW, CUSTOMER WILL DEFEND, INDEMNIFY AND HOLD HARMLESS THE PROVIDER INDEMNITEES AGAINST ALL THIRD-PARTY CLAIMS AND GOVERNMENTAL INQUIRIES (INCLUDING BY WORKERS, CLIENTS, PAYERS, USERS, STRIPE AND CARD NETWORKS) AND ALL RESULTING LOSSES, FINES, SETTLEMENTS AND REASONABLE ATTORNEYS’ FEES, ARISING OUT OF OR RELATING TO: (a) Customer Content or Customer Data, including lack of a required notice or consent and any Prohibited Data; (b) any use of the Service through the Account, any breach of the Agreement, and any setting Customer chose or left at its default; (c) any violation of law by Customer, its Users or Workers, including employment, wage-and-hour, monitoring, privacy, anti-spam, consumer-protection, lien, licensing, surcharge and tax laws; (d) any claim by a Worker, Client or Payer about wages, time records, Estimated Pay, employment decisions, location or device data, or communications; (e) Customer Transactions, payments, disputes, chargebacks, processing fees and dispute evidence; (f) MCP Clients and other Third-Party Services Customer connects; (g) its Public Profile and Upload Link content; and (h) its Input and use of Output. Every other indemnity of Customer in the Agreement is an obligation under this Section.

19.2 Express Negligence

CUSTOMER EXPRESSLY AGREES THAT, TO THE MAXIMUM EXTENT PERMITTED BY LAW, ITS OBLIGATIONS UNDER THIS SECTION 19 APPLY EVEN IF THE CLAIM OR LOSS ARISES IN WHOLE OR IN PART FROM THE SOLE, JOINT, CONCURRENT OR COMPARATIVE NEGLIGENCE OR STRICT LIABILITY OF ANY PROVIDER INDEMNITEE, EXCEPT FOR THE PORTION OF A LOSS FINALLY ADJUDICATED TO RESULT FROM A PROVIDER INDEMNITEE’S GROSS NEGLIGENCE OR WILLFUL MISCONDUCT, OR FROM A SECURITY INCIDENT CAUSED BY PROVIDER’S BREACH OF SECTION 15.1. CUSTOMER ACKNOWLEDGES THAT THIS PROVISION IS CONSPICUOUS AND SATISFIES THE EXPRESS NEGLIGENCE AND FAIR NOTICE REQUIREMENTS OF TEXAS LAW.

19.3 Procedure; No Cap; No Provider Indemnity

Customer will assume the defense promptly at its expense with counsel reasonably acceptable to Provider; Provider may take control of the defense at any time at Customer’s expense or participate at its own. Customer may not settle without Provider’s written consent if the settlement imposes any obligation or admission on a Provider Indemnitee or lacks a full release. Customer’s obligations under this Section are not subject to the exclusions or cap in Section 18. PROVIDER GIVES NO INDEMNITY TO CUSTOMER OR ANYONE ELSE, INCLUDING FOR INTELLECTUAL PROPERTY CLAIMS, UNLESS A NEGOTIATED ORDER FORM EXPRESSLY PROVIDES ONE.

20. Dispute Resolution, Binding Arbitration and Governing Law

In plain terms. If we disagree, we would much rather talk it through, so we both commit to thirty days of good-faith discussion first. If that does not work, disputes go to private, binding arbitration in Austin, Texas, one business at a time. Neither of us can go to a jury or bring a class action, though either of us can use small-claims court or ask a court to protect intellectual property or confidential information. Texas law governs.

20.1 Informal Resolution First

A party with any dispute, claim or controversy arising out of or relating to the Agreement, the Service, any Fees or the parties’ relationship, including its formation, validity or enforceability and claims by or against the Account Creator or an Administrator individually (a “Dispute”), must first send written notice (to Provider at legal@reliohub.com; to Customer at an Administrator’s or billing email). Customer’s notice must concern only Customer, give its legal name and company identifier, describe the Dispute and relief sought, and be signed by an owner or officer. The parties will negotiate in good faith for thirty (30) days, during which either may require a settlement conference by video; no arbitration may begin before then, and a demand must certify compliance.

20.2 Binding Individual Arbitration

(a) EXCEPT AS SECTION 20.5 PROVIDES, ANY DISPUTE NOT RESOLVED UNDER SECTION 20.1 WILL BE RESOLVED EXCLUSIVELY BY FINAL AND BINDING INDIVIDUAL ARBITRATION, NOT IN COURT. This Section 20 is governed by the Federal Arbitration Act, 9 U.S.C. § 1 et seq., the Agreement evidencing a transaction in interstate commerce, and otherwise by the Texas Arbitration Act.

(b) The American Arbitration Association will administer the arbitration under its Commercial Arbitration Rules (not its Consumer Rules), before one arbitrator who is a licensed attorney experienced in commercial disputes, in English. THE SEAT OF ARBITRATION IS AUSTIN, TRAVIS COUNTY, TEXAS; hearings may be held by video.

(c) DELEGATION. THE ARBITRATOR, NOT A COURT, DECIDES ALL QUESTIONS OF ARBITRABILITY, INCLUDING THE SCOPE, VALIDITY, ENFORCEABILITY AND FORMATION OF THIS AGREEMENT TO ARBITRATE, EXCEPT THAT A COURT DECIDES DISPUTES ABOUT THE CLASS ACTION WAIVER IN SECTION 20.3 AND WHETHER SECTION 20.6 APPLIES.

(d) The arbitrator applies Texas law and the Agreement, including Sections 17 through 19, may award only individual relief, and will issue a reasoned written award, which is final, may be entered as a judgment in any competent court and binds no other claimant. Fees of the administrator and arbitrator follow the AAA rules. EACH PARTY BEARS ITS OWN ATTORNEYS’ FEES, EXCEPT THAT PROVIDER MAY RECOVER FEES TO COLLECT AMOUNTS DUE OR ENFORCE SECTIONS 13 OR 19, AND EXCEPT AS A NON-WAIVABLE STATUTE REQUIRES; EACH PARTY OTHERWISE WAIVES FEES UNDER CHAPTER 38 OF THE TEXAS CIVIL PRACTICE AND REMEDIES CODE. The arbitration is confidential.

20.3 Class and Collective Action Waiver

TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY MAY BRING CLAIMS ONLY IN ITS INDIVIDUAL CAPACITY, AND NOT AS A PLAINTIFF OR CLASS MEMBER IN ANY CLASS, COLLECTIVE, CONSOLIDATED, REPRESENTATIVE OR PRIVATE ATTORNEY GENERAL PROCEEDING, IN ARBITRATION OR COURT. THE ARBITRATOR MAY NOT CONSOLIDATE MORE THAN ONE CUSTOMER’S CLAIMS OR AWARD RELIEF TO NON-PARTIES, EXCEPT FOR THE BATCHING IN SECTION 20.6, TO WHICH BOTH PARTIES CONSENT.

20.4 Jury Trial Waiver

TO THE MAXIMUM EXTENT PERMITTED BY LAW, EACH PARTY KNOWINGLY, VOLUNTARILY AND IRREVOCABLY WAIVES ANY RIGHT TO A JURY TRIAL IN ANY PROCEEDING ARISING OUT OF OR RELATING TO THE AGREEMENT OR THE SERVICE THAT IS LITIGATED IN COURT FOR ANY REASON.

20.5 Exceptions

Either party may (a) bring an individual action in a small-claims or justice court while it remains there; (b) seek injunctive relief in court to prevent infringement or misappropriation of its intellectual property or trade secrets or breach of Section 13, or temporary relief against unauthorized disclosure of its Confidential Information pending arbitration, without bond to the extent the law permits; and (c) seek interim relief in aid of arbitration. All other claims, including those about Customer Data, privacy, platform access or Security Incidents, must be arbitrated.

20.6 Mass Arbitration

If twenty-five (25) or more substantially similar demands are filed or threatened against Provider by or with coordinated counsel within 180 days, then, to the extent the law permits, the AAA’s Mass Arbitration Supplementary Rules apply; each side selects ten (10) bellwether cases while the rest are held without fees; the parties then mediate for at least sixty (60) days; remaining demands proceed in batches of up to fifty (50), each before one arbitrator with one set of fees and individual awards; and limitations periods are tolled for held demands. Batching permits no class or representative relief.

20.7 Severability of Arbitration Provisions

If the class and collective action waiver is finally held unenforceable as to any claim, that claim alone will be severed and decided by a court under Section 20.8, stayed pending the individual arbitration, and will never proceed in class arbitration. Any other unenforceable part of this Section 20 will be severed to the minimum extent necessary. If this Section 20 is wholly unenforceable as to a Dispute, the Dispute goes to court under Section 20.8, and the jury waiver still applies.

20.8 Governing Law and Venue

The Agreement and all Disputes, in contract, tort or otherwise, are governed by the laws of the State of Texas without regard to conflict-of-laws rules, except that the Federal Arbitration Act governs this Section 20. For any matter not arbitrated, the state and federal courts located in Travis County, Texas have exclusive jurisdiction and venue, and each party consents to them; awards and injunctions may be enforced in any competent court. An amendment to this Section 20 applies only prospectively, at least thirty (30) days after notice, and not to Disputes already known or pending.

21. Changes to This Agreement

In plain terms. We will occasionally update these terms. Each version is dated, and when a change matters we will tell your administrators at least 30 days ahead, unless the law or security requires us to move faster. If you do not agree, you can cancel before it takes effect.

21.1 Amendments and Notice

Provider may amend any document in the Agreement. Each version carries a version identifier and effective date; this one is 2026-10-14, effective October 14, 2026. A change Provider reasonably determines is material and adverse takes effect no earlier than thirty (30) days after notice by email to an Administrator or in the Service; a change required by law, a card network or Stripe, or made for security or fraud prevention, may take effect sooner, including immediately; non-material changes take effect on posting.

21.2 Acceptance

Provider may ask Administrators to accept a new version in the Service; acceptance by any one Administrator binds Customer and creates an Acceptance Record. Continued use of the Service after the effective date also constitutes acceptance. Provider may limit features until an Administrator accepts. If Customer does not agree, its sole remedy is to cancel before the effective date. No amendment is effective unless made under this Section or in a Negotiated Order Form; no email, ticket or Customer purchase-order term modifies the Agreement.

22. Electronic Communications and Notices

In plain terms. We handle notices and records electronically, and they count just as much as paper. Please keep your account emails current. Legal notices to us go to legal@reliohub.com, privacy requests to privacy@reliohub.com, and everyday help through in-app tickets.

22.1 Electronic Communications

Customer consents to receive all agreements, notices and records electronically and agrees they satisfy any writing or signature requirement under the ESIGN Act and the Texas Uniform Electronic Transactions Act. Customer represents that this is a business transaction; to the extent consumer-consent rules apply, it consents and confirms it has the internet access, browser, email and PDF reader needed to access and keep these records. Service, security, billing and legal communications cannot be opted out of while the Account exists.

22.2 Notices

Provider may give notice by email to the Account Creator, an Administrator or the billing contact, in the Service, or by posting on the Websites; notice is effective twenty-four (24) hours after sending or posting, whether or not read or filtered. Customer must keep these addresses current. Legal notices to Provider must be emailed to legal@reliohub.com (Provider publishes no street address); privacy requests and security reports go to privacy@reliohub.com; support goes through in-app tickets, which are not legal notices. If an email to Provider bounces, the sender must resend it and the same business day submit a copy by support ticket titled “Legal Notice” or “Privacy Notice”. Notices sent any other way are not effective.

22.3 Communications Sent for Customer

Emails the Service sends to Clients, Payers and Workers at Customer’s direction, such as quotes, invoices, Payment Links and work notices, are Customer’s communications, sent by Provider as its service provider even when they bear the RelioHub name. Customer is responsible for their content, recipients and legal compliance, including the CAN-SPAM Act, and will not send advertising through the Service. Archived copies are kept as described in Section 10 (Retention and Deletion) of the Privacy Policy and may be accessed under Section 6.

23. General Provisions

In plain terms. These standard rules hold the contract together: this Agreement is the whole deal, these Terms prevail if documents conflict, and you are relying only on what is written here.

23.1 Entire Agreement; No Reliance

The Agreement is the entire agreement on its subject and supersedes all prior proposals, statements and earlier draft terms published on the Websites, none of which took effect. CUSTOMER WARRANTS THAT IT HAS NOT RELIED ON ANY STATEMENT, PROMISE, DEMONSTRATION OR ROADMAP NOT EXPRESSLY IN THE AGREEMENT, INCLUDING ON THE WEBSITES, IN APP STORE LISTINGS OR IN MARKETING, AND, TO THE MAXIMUM EXTENT PERMITTED BY LAW, WAIVES ANY CLAIM FOR FRAUDULENT INDUCEMENT OR NEGLIGENT MISREPRESENTATION BASED ON IT.

23.2 Order of Precedence

If documents conflict, the order is: a Negotiated Order Form (only for provisions it expressly overrides); these Terms of Service; the Privacy Policy; other Orders; the Documentation. The Privacy Policy does not expand Provider’s liability or override Sections 6 or 17 through 20.

23.3 Assignment

Customer may not assign the Agreement, including by merger or change of control, without Provider’s written consent. Provider may assign it without consent, including to an Affiliate or a successor, and may subcontract its obligations.

23.4 Force Majeure

Provider is not liable for delay or failure caused by events beyond its reasonable control, including natural disasters, epidemics, war, cyberattacks, and failures of the internet, utilities, hosting providers, Subprocessors, AI Providers, Stripe or email providers. Force majeure never excuses payment.

23.5 Relationship; No Third-Party Beneficiaries

The parties are independent contractors; Provider is not Customer’s agent, fiduciary, employer, joint employer, payroll provider, merchant of record or collection agent. No one else has rights under the Agreement, except that Provider Indemnitees may enforce Sections 17 through 20, Subprocessors may enforce Sections 17 and 18, and Apple may enforce it as stated in Section 12.3.

23.6 Waiver; Severability; Notices of Process

No failure to enforce a right is a waiver, and a waiver must be in a signed writing. An unenforceable provision will be reformed to the minimum extent necessary, and the rest remains in force, subject to Section 20.7. Customer will reimburse Provider’s reasonable costs of responding to subpoenas in Customer’s disputes with third parties.

23.7 Export Controls, Sanctions and Anti-Corruption; Language

Customer will comply with US export-control and sanctions laws and represents that neither it, its owners nor its Users are in a sanctioned country or on a US restricted-party list; Provider may suspend immediately if continuing would risk a violation. Customer will comply with anti-corruption laws, including the Foreign Corrupt Practices Act. The Agreement is in English, which controls over any translation.

24. Contact Information

In plain terms. Here is who we are and how to reach us. We do not publish a street address or phone number, so please use these email addresses and in-app support tickets.

The Service is provided by NORTHMARK MANAGEMENT GROUP LLC, a Texas limited liability company doing business as RelioHub, through reliohub.com, app.reliohub.com and pay.reliohub.com. Legal notices: legal@reliohub.com. Privacy requests and security reports: privacy@reliohub.com (see also Section 18 (How to Contact Us) of the Privacy Policy). Support: in-app support tickets. The Mobile App may be listed in App Stores under a developer or seller name other than “RelioHub” or Provider’s legal name; however it is listed, Provider provides the Service under the Agreement.

Version 2026-10-14, effective October 14, 2026. This version replaces version 2026-10-13.