RetailOSBy Grovix Ventures
Get Started
person
Legal Document

Terms of Service

Last updated: September 5, 2026 • Grovix Ventures Pvt Ltd

These Terms of Service govern your use of Retail OS, the software platform operated by Grovix Ventures Pvt Ltd (referred to as “Company”, “we”, “us”, or “our” — subject to final legal verification of the operating entity). If the legal entity differs, replace Grovix Ventures Pvt Ltd and related references before publishing. By creating an account or using the service, you agree to these Terms.

Configuration notice: Verify Grovix Ventures Pvt Ltd, [CITY, INDIA] and [email protected] before publishing. Do not publish placeholder [email protected].

1. Parties & Definitions

Retail OS is the software platform. Grovix Ventures Pvt Ltd is the Company operating the platform, subject to final legal verification. “Company”, “we”, “us”, “our” refer to Grovix Ventures Pvt Ltd as operator of Retail OS.

  • Tenant — a business/customer organization using the platform.
  • User — an individual authorized by a Tenant to access the platform.
  • Administrator — a Tenant user with administrative privileges.
  • Staff — a Tenant user with staff-level privileges.
  • Subscription — the paid service plan associated with a Tenant.
  • Customer Data / Tenant Data — business and operational information submitted or generated by a Tenant through the platform, including Customers, Inventory, Enquiries, Quotations, WhatsApp messages, and related operational records.

The Tenant retains its rights in Customer Data subject to rights granted to operate the service; we do not claim ownership of the Tenant’s underlying business data unless separately agreed in writing.

2. Account Creation & Responsibilities

Signup currently creates a Tenant using the supplied company name and creates an ADMIN user. The account requires email verification via a 6-digit OTP valid for approximately 10 minutes with 3 verification attempts. Login is blocked when the user is inactive, the Tenant is inactive, or email verification has not been completed. Tenant context is established for authenticated requests. ADMIN and STAFF roles are supported. Tenant storage quota is 5 GiB and currently acts as a soft warning rather than a hard technical storage block.

You are responsible for:

  • providing accurate registration information;
  • maintaining account credentials securely;
  • controlling which employees/users receive access;
  • ensuring authorized users comply with these Terms;
  • notifying the Company of unauthorized access or suspected compromise.
Not currently implemented as platform-enforced controls: mandatory MFA, passwordless authentication, automatic account/tenant deletion, guaranteed account recovery, or hard enforcement of the 5 GiB limit.

3. Subscription Plans & Service Access

Supported plan intervals are Monthly, Yearly, Lifetime with payment modes AUTOPAY and MANUAL. Subscription states include PENDING_PAYMENT, ACTIVE, EXPIRED, LIFETIME, CANCELLED. Plans contain plan code, plan name, price (INR), billing cycle, active/inactive state, and contact-sales configuration.

Access rule — no grace period

Unless otherwise expressly agreed in writing, subscription access begins only after the applicable payment requirements have been satisfied and may be suspended or blocked when the subscription expires. PENDING_PAYMENT does not receive normal paid-service access. There is no general grace period, free trial, or automatic Lifetime renewal implied by the codebase.

4. Payments

Retail OS uses Razorpay for supported online subscription payments where configured (Razorpay Key ID/Secret in environment). Online checkout is created for eligible active plans; Lifetime, contact-sales, and MANUAL configurations are not processed through the normal Razorpay recurring checkout flow. Razorpay customer/subscription records are created for supported recurring subscriptions and verification uses HMAC; webhook events are deduplicated by event ID.

Online payments are processed through Razorpay and are subject to Razorpay’s applicable terms and policies. Retail OS does not store card numbers and is not itself represented as PCI-DSS certified; payment-card handling is delegated to the payment provider. Do not expose Razorpay secret keys.

5. Auto-Renewal, Manual Billing & Cancellation

AUTOPAY

For supported recurring plans, Razorpay handles recurring billing according to the configured subscription schedule using recurring subscription counts (not unlimited).

MANUAL

Manual/custom plans can be assigned by administrators and have explicitly configured subscription periods. The system can renew manual/custom plans through administrative billing operations.

Cancellation

  • Self-service cancellation cancels the Razorpay subscription at the end of the current billing cycle; access continues until currentPeriodEnd and status becomes CANCELLED.
  • Administrative hard cancellation can terminate access immediately.
  • Lifetime subscriptions cannot be cancelled through the normal cancellation flow.

Refund policy

Subscription fees are generally non-refundable and unused portions of a billing period are not automatically refunded. The codebase contains no automated Razorpay refund implementation; any refund exception is handled manually at the Company’s discretion and, where applicable, through the designated billing/sales contact: [email protected] (verify before publishing; do not use [email protected]).

No automatic, prorated, or guaranteed refunds, and no specific refund SLA is promised by the application.

6. Tenant Data, Ownership, Retention & Storage

The platform stores tenant-specific operational information including Customers, Inventory, Enquiries, Quotations, WhatsApp messages, product/pricing/operational records, and uploaded media. Models such as Customer, Inventory, Enquiry, Quotation, and WhatsappMessage include tenant relationships.

The Tenant remains responsible for the legality, accuracy, and rights associated with information it submits. We do not claim ownership of the Tenant’s underlying business data.

Retention

The implementation does not provide a universal deletedAt/TTL-based retention system. Tenant data may remain stored while the Tenant’s account or service relationship remains active and may continue to be retained after suspension or deactivation where necessary for operational, contractual, security, accounting, dispute-resolution, or legal purposes. Deactivating a Tenant currently operates as a soft suspension (isActive=false) rather than immediate hard deletion; actual deletion occurs through administrative/database deletion mechanisms and cascading relationships. hiddenFromPipeline only affects processing/automation, not deletion. No automatic 30-day cryptoshredding or guaranteed permanent deletion is promised.

7. Acceptable Use

Retail OS is intended for retail/wholesale business workflows including customer/enquiry management, inventory management, quotations, pricing, WhatsApp-based business communication, and operational retail workflows. You must not use the service to:

  • violate applicable law;
  • impersonate another person or business;
  • upload malicious code;
  • abuse messaging infrastructure;
  • send unlawful or unsolicited communications;
  • infringe intellectual-property rights;
  • attempt unauthorized access to another Tenant;
  • interfere with platform infrastructure;
  • bypass authentication, authorization, billing, or access controls;
  • use the service for fraudulent activity.

Customer controls such as doNotDisturb and hiddenFromPipeline may prevent certain automations but are not universal compliance controls.

8. AI Features & Third-Party Services

Certain features rely on third-party service providers. Information submitted to those services may be processed according to the applicable provider’s terms, privacy policies, and technical configuration.

MSG91 — WhatsApp/messaging and OTP infrastructure.
Google Gemini — 2.5 Flash for OCR, catalog parsing, image understanding, product/data extraction.
Wasabi / S3-compatible — object/file storage with tenant-prefixed paths tenants/${tenantId}/ and short-lived presigned URLs.
Razorpay — subscription/payment processing.
Puppeteer — application-generated document/browser rendering.

We do not claim zero-retention, zero training, exclusive India processing, that every third party has a signed DPA, or that we control third-party availability.

9. AI-Specific Terms

AI-assisted functionality may produce automated or extracted results, can contain errors, should be reviewed by the Tenant/user before being relied upon, is not a substitute for human review, and should not be treated as guaranteed accurate. For OCR/catalog extraction: AI-generated or extracted product information, pricing classifications, or other outputs should be reviewed before being used in quotations, customer communications, inventory decisions, or other business-critical workflows. AI processing is not represented as ephemeral or zero-retention.

10. Service Limits & Availability

The codebase includes authentication rate limiting, signup rate limiting, BullMQ background queues, grouped/background processing, and storage quota warnings. Authentication limiter is approximately 10 requests/minute for relevant authentication routes; signup approximately 20/hour. These are not represented as a complete platform-wide rate-limit policy, and there is no verified production SLA in the codebase.

Retail OS is provided on a commercially reasonable efforts basis. Service availability may be affected by maintenance, infrastructure failures, third-party service outages, network conditions, or other events outside the Company’s reasonable control. No 99.9%/99.99% uptime or guaranteed response/queue-processing/recovery time is promised.

11. Suspension & Termination

The platform currently uses soft deactivation: a Tenant may be suspended by setting tenant.isActive = false (authenticated access rejected) and individual users via user.isActive = false. Suspension may occur for unpaid/expired subscriptions, violation of these Terms, security concerns, suspected misuse, or operational/legal requirements. Suspension does not permanently delete data — suspension and deletion are separate concepts.

Upon termination, access to the service may cease, while certain Tenant information may continue to be retained for legitimate operational, contractual, security, accounting, dispute-resolution, or legal purposes.

12. Intellectual Property

Retail OS software, branding, interfaces, documentation, and underlying platform technology remain the property of the Company or its licensors. The Tenant retains its rights in information/data it submits, subject to rights granted to operate the service. Users receive a limited, non-exclusive, non-transferable right to use Retail OS during an active subscription or authorized service period. We do not claim ownership over customer business data.

13. Disclaimers

Retail OS is provided on an “AS IS” and “AS AVAILABLE” basis to the extent permitted by applicable law. We do not promise uninterrupted service, error-free operation, complete accuracy, uninterrupted third-party integrations, guaranteed business outcomes, guaranteed quotation accuracy, or guaranteed AI accuracy.

14. Limitation of Liability

To the maximum extent permitted by applicable law, the Company will not be liable for indirect, incidental, special, consequential, exemplary, or loss-of-profit damages arising from use of the service.

For direct liability, subject to mandatory legal exceptions, liability is capped at the amounts paid by the Tenant for the applicable service period giving rise to the claim. Nothing in these Terms excludes or limits liability that cannot lawfully be excluded or limited under applicable law.

15. Governing Law & Jurisdiction

These Terms are governed by the laws of India, subject to applicable mandatory laws.

Editable jurisdiction: Subject to applicable law, courts having jurisdiction at [CITY, INDIA] shall have jurisdiction over disputes arising from these Terms. Before publishing, replace [CITY, INDIA] with the legally correct jurisdiction.

16. Age Requirement

Retail OS is intended for business users and may only be used by individuals who are at least 18 years old or otherwise legally capable of entering into a binding agreement under applicable law. The application does not technically verify age.

17. Privacy

Your use of Retail OS also involves the processing of personal information as described in our Privacy Policy.

18. Changes to Terms

We may update these Terms from time to time to reflect changes to the service, legal requirements, or business practices. The updated version will be posted on this page with a revised “Last updated” date. No specific notice period is promised unless implemented or legally required.

19. Contact

For questions about these Terms, contact:

Do not address communications to a “DPO” or “Data Protection Officer” unless such appointment has been formally made.

This Terms of Service describes the platform’s current implementation and is intended for transparency. It should be reviewed and approved by qualified legal counsel before being relied upon as a final legal agreement. No marketing certifications (DPDP compliant, SOC 2, ISO, PCI-DSS) are claimed unless independently verified.