Terms of Service

1. Architecture and Tenant Isolation

Rowan operates on a logically segregated, multi-tenant database architecture.

• Tenant Segregation: All customer data is stored in isolated partitions within our PostgreSQL database layer. Isolation is enforced at the database query layer.
• Client Workspaces: Tenant administrators may provision discrete workspaces for separate clients and assign specific team members or external contractors to those workspaces.
• Access Containment: The Platform utilizes strict Row-Level Security (RLS) policies. Contractors or staff members assigned to specific workspaces are restricted from querying, viewing, or exporting data associated with other workspaces in the same tenant.

2. User Accounts, Credentials, and 2FA

To maintain the integrity of client workspaces, Customers must secure their authentication credentials:

• Mandatory 2FA: Two-Factor Authentication (2FA) is mandatory for all Owner and Admin roles on Rowan. Access to these roles is restricted until 2FA setup is complete.
• Credential Protection: You are solely responsible for keeping your password, API keys, and 2FA recovery codes secure. We are not liable for any unauthorized access resulting from compromised credentials.
• Session Revocation: Rowan supports instant, server-side session revocation. Revoking a session will immediately terminate the associated active authentication cookie on the user’s next API request.

3. Customer Support and Impersonation Policy

To diagnose system faults, assist with data recovery, or resolve billing issues, authorized Rowan support engineers and platform staff (“Superadmins”) may occasionally need to view or impersonate a customer session.

• Consent: By submitting a support ticket or requesting assistance, you authorize Rowan platform staff to impersonate your user account.
• Auditing: All support impersonation sessions are logged and write an immutable audit trail entry directly to our centralized logging system. Impersonating sessions operate in a restricted mode to prevent unauthorized database updates wherever possible.

4. Document Management and File Delivery

Rowan implements a decentralized document processing system:

• Client-Side Hashing: Files uploaded to Rowan are hashed via SHA-256 in the browser before the upload begins. Rowan uses these hashes to deduplicate files and optimize storage.
• Pre-signed URLs: Access to uploaded documents is served via short-lived, pre-signed URLs. These URLs automatically expire fifteen (15) minutes after generation. You are responsible for ensuring that pre-signed URLs are not shared outside authorized communication channels.
• IP Allowlisting: Organization administrators can configure IP allowlist policies. Users attempting to access files or workspace contents from an IP address outside the allowlist will be blocked at the network gate.

5. Third-Party Integrations and Services

The Platform provides native integrations with third-party software tools:

• Jira Sprint & Task Import: Rowan connects to the Jira REST API to sync sprint structures and issues. Rowan does not store your Jira password and connects solely via OAuth or personal access tokens.
• LinkedIn Publishing: The Platform includes AI-assisted social media publishing tools that connect to the LinkedIn API. You are responsible for all content drafted and published through our tools.
• Compliance: By linking these third-party accounts, you agree to comply with their respective developer agreements, API terms of use, and community guidelines.

6. Billing, Payments, and Subscriptions

Billing and payment transactions on Rowan are processed through Razorpay:

• Subscriptions: By subscribing to a paid tier (Essential, Advanced, or Pro), you authorize recurring billing to your selected payment method via Razorpay.
• Taxes and Fees: All plans are billed in your regional currency (USD, EUR, or INR) based on detected timezone indicators. You are responsible for all applicable local taxes.
• Cancellations: You can cancel your subscription at any time through the billing dashboard. Access to paid features will continue until the end of the current billing cycle.

7. Limitations of Liability and Indemnification

TO THE MAXIMUM EXTENT PERMITTED BY APPLICABLE LAW, ROWAN AND ITS SUPPLIERS SHALL NOT BE LIABLE FOR ANY INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES (INCLUDING LOSS OF PROFITS, DATA LOSS, OR BUSINESS INTERRUPTION) ARISING OUT OF THE USE OR INABILITY TO USE THE PLATFORM.

You agree to indemnify and hold harmless Rowan, its directors, and employees from any claims, damages, or losses arising from your breach of these Terms, unauthorized data uploads, or misuse of third-party API keys.

8. Changes and Governing Law

We reserve the right to modify these Terms at any time. Significant updates will be communicated via email or an in-app banner. Continued use of Rowan after modifications constitutes acceptance of the updated Terms.

These Terms shall be governed by and construed in accordance with the laws of the jurisdiction in which Rowan operates, without giving effect to any principles of conflicts of law.