Terms of use for OnsitePilot.

These terms apply to the OnsitePilot public website, private beta application flow, provider workspace, customer booking pages, and related API workflows operated under the onsitepilot.gigassbox.com domain.

If a signed written agreement, integration authorization screen, or paid checkout later gives more specific terms for a workflow, that more specific agreement controls for that workflow.

OnsitePilot is currently operated as a private beta product for solo service businesses. Submitting a beta application does not guarantee access, onboarding, launch timing, future pricing, or availability of any specific feature.

Private beta access may be free while the private beta is running. The public pricing page may describe intended paid pricing, but no paid subscription starts unless you separately accept a paid checkout, invoice, or commercial agreement.

You must provide accurate account, business, booking, and contact information when using OnsitePilot. You are responsible for keeping passwords, verification codes, private booking links, provider sessions, customer sessions, and admin access secure.

Do not access a provider workspace, admin page, customer booking record, Square connection, Google Calendar connection, or booking link unless you are authorized to do so. You are responsible for activity that occurs through your account or verified session.

Providers are responsible for the services they offer and the booking rules they configure. OnsitePilot supplies booking workflow software; it does not perform the provider service, guarantee service quality, verify licensing, or settle every customer dispute.

• Keep service names, descriptions, prices, deposits, duration, buffers, travel mode, service area, availability, business address, cancellation rules, reschedule rules, refund rules, and no-show rules accurate.
• Maintain any licenses, insurance, permits, tax handling, customer consent, safety practices, and legal compliance required for your business and location.
• Honor confirmed bookings or handle customer communication, cancellations, reschedules, refunds, chargebacks, and disputes according to your own policies and applicable law.
• Do not configure policies, pricing, or availability that you do not intend or are not able to follow.

Customers who use a provider booking page are booking with that provider, not hiring OnsitePilot to perform the service. The provider is responsible for the service, pricing, policy, arrival window, service quality, and customer relationship.

Customers must provide accurate booking and contact information, use verification codes only for their own booking, and avoid false, abusive, or unauthorized bookings.

OnsitePilot uses Square-connected workflows for deposits and payment confirmation. Providers connect their own Square account, and customers may complete payment through Square-hosted checkout or a Square payment link.

OnsitePilot does not hold customer funds as a wallet, escrow account, or money transmitter, and it does not collect full payment card numbers. Square processes payment details under Square terms. OnsitePilot records payment status so the booking workflow can move forward or release a pending hold.

• Provider Square connection status, payment link creation, payment confirmation, payment timeout, webhook handling, and refund status are used to keep booking records aligned with Square.
• Refund eligibility, cancellation consequences, no-show consequences, and reschedule deadlines are primarily controlled by the provider policies configured in OnsitePilot and by applicable payment-network, Square, and legal requirements.
• A payment link or slot hold may expire, be deleted, or stop protecting a slot if payment is not completed within the workflow deadline or if Square reports that payment did not complete.

OnsitePilot uses address, location, service duration, buffer, travel mode, and TomTom route data to recommend or reject booking times. Route-aware scheduling is an operational aid, not a guarantee that traffic, parking, access, weather, customer readiness, or provider delays will match the estimate.

Providers must review unusual addresses, service constraints, travel assumptions, and same-day schedule risk before relying on a booking decision where those facts matter.

Providers may connect Google Calendar so OnsitePilot can write confirmed bookings, update rescheduled bookings, and delete cancelled bookings in the selected provider calendar. OnsitePilot remains the booking source of truth for the current product.

A Google Calendar sync failure does not automatically cancel or invalidate a booking. Providers are responsible for checking OnsitePilot booking state when calendar state and OnsitePilot state conflict.

OnsitePilot may use provider configuration, service rules, policy text, booking state, and business knowledge to automate parts of the booking flow and answer repeat customer questions.

Automated output may be incomplete or wrong. Providers are responsible for reviewing their setup and correcting inaccurate service, price, policy, availability, prep, route, refund, or customer-facing information. OnsitePilot output is not legal, tax, medical, safety, emergency, financial, or professional advice.

You may not misuse OnsitePilot or use it in a way that creates operational, security, legal, or customer harm.

• Do not submit fraudulent beta applications, false bookings, fake customer identities, unauthorized payment activity, or misleading provider information.
• Do not interfere with service operation, bypass authentication, scrape private data, probe private APIs, overload the service, inject malicious content, or attempt to access another provider, customer, admin, Square, or Google Calendar record.
• Do not use OnsitePilot for illegal services, emergency dispatch, regulated services that require a different approval workflow, or any workflow where automated booking would violate law or professional obligations.
• Do not put full payment card numbers, government identifiers, protected health information, passwords, or unnecessary sensitive information into notes, support messages, beta forms, or booking fields.
• Do not use customer data collected through OnsitePilot in a way that violates privacy law, spam rules, platform terms, or the provider's own customer promises.

OnsitePilot depends on third-party services for parts of the workflow, including Cloudflare-hosted infrastructure, Resend email delivery, TomTom route and location services, Google Calendar, and Square payment services.

Those third-party services are not controlled by OnsitePilot. Their own terms, policies, outages, limits, account requirements, API behavior, and compliance rules may affect the availability or behavior of OnsitePilot workflows.

OnsitePilot and its software, website, documentation, product copy, interface, workflows, and branding are owned by OnsitePilot or its licensors. You may not copy, resell, reverse engineer, or build competing access to private product workflows except where law expressly permits it.

Providers keep responsibility for their business content and customer relationship. By submitting provider configuration, storefront content, service details, policy text, images, booking notes, or related business data, you give OnsitePilot permission to host, process, display, transmit, and use that content as needed to operate, secure, support, and improve the product.

Use of OnsitePilot is also governed by the Privacy Policy. The Privacy Policy explains what OnsitePilot collects, how data is used, how Google Calendar, Square, TomTom, email, provider, customer, and beta data are handled, and how to make a request during private beta.

The public site, beta flow, provider workspace, customer booking pages, integrations, pricing, and feature set may change, pause, fail, or be removed during private beta. OnsitePilot does not guarantee uninterrupted availability, data export, self-serve signup, public launch timing, or compatibility with every provider workflow.

OnsitePilot may update these terms when the product changes. Continued use after an update means you accept the updated terms for future use.

OnsitePilot is provided during private beta on an as-is and as-available basis. To the maximum extent allowed by law, OnsitePilot disclaims warranties of merchantability, fitness for a particular purpose, non-infringement, accuracy, uninterrupted operation, and error-free behavior.

No booking, route estimate, payment status, calendar sync, automated answer, email, ICS file, or workflow recommendation should be treated as a guarantee that a provider can complete a service, that a customer will appear, that a payment cannot be disputed, or that a third-party service will operate without failure.

To the maximum extent allowed by law, OnsitePilot will not be liable for lost profits, lost revenue, lost business, lost data, missed appointments, route delays, customer disputes, provider disputes, chargebacks, refund disputes, service quality issues, third-party service failures, integration outages, or indirect, incidental, special, consequential, exemplary, or punitive damages.

Some jurisdictions do not allow certain limitations. In those places, the limitation applies only to the extent allowed by law.

OnsitePilot may limit, suspend, or remove access if an account, booking flow, beta submission, integration, or usage pattern appears abusive, fraudulent, unauthorized, legally risky, harmful to customers or providers, or incompatible with beta capacity.

You may stop using the public site or beta product at any time. Some records may remain as described in the Privacy Policy where they are needed for security, payment, audit, dispute, booking-integrity, or legal reasons.

During private beta, use the contact page at /contact/ for terms, beta, provider, or booking-related questions. Include enough context to identify the beta application, provider workspace, booking link, or workflow involved.