Legal Center

Account and Security

• Access: Registration requires email verification and explicit admin approval. Where enabled, users must utilize Time-based One-Time Password (TOTP) 2FA.
• Responsibility: You are responsible for all activity under your account. Org Admins are responsible for managing user invitations and ensuring only authorized personnel have access to the tenant’s treasury data.
• Identity: Access is tied to your verified identity; attempting to spoof or bypass identity-derivation controls is a material breach.

Use of the Service

• Integrity: You must not disrupt the Service or attempt to bypass tenant isolation or Row-Level Security (RLS) protocols.
• Intellectual Property: Stonerose Treasury Limited owns all rights to the SLOS framework and the software. Users are granted a limited, non-transferable license to use these for internal business purposes only.
• Compliance: You must follow all applicable financial regulations and laws.

Content and Data Handling

• Ownership: You retain ownership of all raw data uploaded to the Service.
• Lifecycle: To maintain system performance and security, raw data uploads (CSV/XLSX) are subject to an automated 90-day lifecycle delete policy.
• Isolation: Your data is stored in a dedicated, isolated PostgreSQL database (Phase 1) or within your own tenant (Phase 2), ensuring no data is shared with other clients.

Mala AI Assistant

• Scope: AI-generated insights are based on curated, aggregated data views and grounded in the SLOS framework.
• Disclaimer: Responses provided by Mala AI are for informational purposes only and do not constitute financial, investment, or legal advice.
• Data Privacy: No raw transactional rows are sent to the LLM; only anonymized, aggregated slices are processed to protect sensitive identifiers.

Subscriptions and Billing

• Payments: Subscriptions are managed via Stripe. Clients are responsible for maintaining valid payment methods in the Customer Portal.
• Tiers: Features and user seats are governed by your selected tier (Essential, Precision, Strategic, or TaaS).
• Dunning: Failed payments will trigger a notice period; continued failure may result in account restriction to "read-only" mode or suspension.

Availability and Liability

• Uptime: We aim for high uptime, supported by Azure’s native infrastructure. Scheduled maintenance will be communicated in advance where possible.
• Limits: The Service is provided “as is”. To the extent allowed by law, liability is limited to fees paid in the 12 months preceding a claim.

Precedence

For clients with bespoke Statements of Work (SOW) or specific enterprise contracts (e.g., Client-Hosted setups), the terms of the executed agreement prevail over this page where they differ.