BOAT Terms of Service
Pre-release beta status. BOAT, Business Operations and Automation Technology, is currently provided during a pre-incorporation soft launch and beta evaluation phase. Access is provided only for evaluation, workflow testing, performance validation, and bug reporting.
As-is service. BOAT is provided on an "as-is" and "as-available" basis. During this MVP and fine-tuning phase, BOAT does not warrant uninterrupted availability, zero-latency processing, error-free automation, continuous uptime, or uninterrupted work distribution.
Client responsibility. Clients remain responsible for validating outputs, supervising operational decisions, maintaining source backups, and confirming that platform-generated allocations, dashboards, reports, and automation results match their business requirements.
Introductory evaluation access. Initial onboarding includes a 30-day free trial for evaluation, workflow testing, volume/distribution validation, and operational fit review. No credit card or payment credential is required for the free trial. BOAT may issue trial-end or subscription conversion notices exactly 2 weeks before the free trial window ends.
Paid subscription cadence. Post-beta production subscriptions may be billed upfront through an integrated payment gateway on either a six-month or one-year recurring term, based on the plan selected by the client.
Failed payments. If a renewal transaction fails or is rejected, the client must resolve the issue with its financial institution. BOAT may assist in coordinating with the integrated payment gateway provider, but does not control bank authorization decisions.
Cancellation and refunds. Clients may request cancellation during an active paid term. The active calendar quarter in which cancellation is requested is non-refundable because cloud infrastructure and support capacity are already allocated. Any unused subscription balance for later calendar quarters may be calculated pro-rata and refunded to the original payment source.
Limitation of liability. To the maximum extent permitted by law, BOAT, its founder, owners, contributors, and operators will not be liable for indirect, incidental, special, consequential, punitive, or business interruption damages, including loss of revenue, loss of profits, downtime, operational delays, workflow disruption, data entry errors, or missed service metrics arising from beta use or platform evaluation.
Intellectual property. BOAT and its platform logic, interface design, software workflows, automation methods, reports, templates, analytics structures, and system documentation remain proprietary to BOAT. Clients retain 100% ownership and intellectual property rights over their own operational files, configurations, records, and business data.
Governing law. These terms are governed by the laws of India. The exclusive venue for formal dispute resolution, mediation, arbitration, or court proceedings will be Haryana, India, unless BOAT later enters into a written corporate agreement that specifies another jurisdiction after incorporation.
BOAT Privacy & Data Protection Policy
Client data ownership. The client owns and controls its operational data. BOAT provides a secure processing shell for automation, dashboarding, reporting, routing, and evaluation. BOAT does not claim ownership over client data.
Zero cross-exposure policy. BOAT is designed around tenant isolation. Client operational records, file rows, comments, filenames, transactional text, configurations, and business payloads must not be exposed to other clients, entities, editors, or unauthorized roles.
No data monetization. BOAT does not sell, lease, trade, distribute, or disclose client operational data, configurations, or records to third-party marketing entities, data brokers, or unrelated commercial data services.
No routine client data access. BOAT internal operators do not access raw client operational files, rows, comments, or transaction payloads for routine use. Internal BOAT views are intended for metadata, system health, logs, configuration support, and troubleshooting. Any support workflow requiring deeper review should be handled under client authorization and tenant-bound controls.
Restricted internal access. BOAT administrative views are intended for high-level metadata, system health, processing logs, and operational support. They are not intended to expose raw client files, proprietary transaction rows, or sensitive operational payloads.
Security controls. BOAT may process client files and records through secured cloud infrastructure, including cloud storage networks such as Amazon Web Services. Security controls may include encryption in transit, encryption at rest, access controls, role-based authorization, activity logging, and operational redundancy.
Data retention and uploaded files. Clients may configure the operational data retention period in the Admin Panel. The suggested default is three years, and clients may choose retention in months or years. Master upload files are parsed for headers, mappings, and structured rows, then the raw uploaded file blob is discarded after extraction. Place Volume uploads are handled separately: BOAT extracts the rows, places the uploaded file into the mapped procedure folder path, and may keep a temporary safety copy for up to two days for troubleshooting before automatic cleanup.
Infrastructure resilience. BOAT may use storage redundancy and fault-tolerant infrastructure practices, including RAID-backed storage arrays or equivalent cloud resiliency controls, to support continuity and hardware fault tolerance.
Beta limitations. During beta evaluation, security, performance, reporting, and automation logic may be modified to correct defects, improve reliability, and validate production readiness. Clients should avoid uploading unnecessary sensitive data during testing unless required for evaluation.
Operational logs. BOAT may record audit events such as login activity, volume fetching, work distribution, attendance updates, report generation, and system errors. These logs are used for security, troubleshooting, compliance, and platform support.
Future corporate transition. BOAT may later transition from a pre-incorporation/sole-proprietor soft launch structure into an incorporated entity in India or the United States. These terms are designed to remain assignable to that successor entity while preserving client data ownership and tenant isolation commitments.
