Customer Agreement
Commercial plan, billing cycle, renewal, expiry grace, support scope, implementation scope, termination, and final signed terms.
AbhiPOSS Legal & Trust
Clear agreements for software, data, security, support, and risk.
AbhiPOSS is designed around customer-controlled data, offline-first operation, and practical business continuity. This page summarizes the responsibilities that should be documented before a production rollout.
Customer data stays in customer control.
Offline deployments keep billing data on the merchant's device or local network. Cloud hosting, remote access, backup, and sync are separate operating choices that must be enabled and governed by the selected plan.
This overview does not replace a signed customer agreement. The final order form, license terms, implementation scope, and applicable law control each deployment.
Software License
AbhiPOSS is licensed for authorized business use. Tampering, bypassing activation, reverse engineering, and unauthorized resale are prohibited.
Data Responsibility
Merchant-controlled POS data remains the merchant's responsibility unless Abhikalan is explicitly providing hosting, sync, backup, or support access.
Backup Policy
Standalone offline deployments require local backup discipline. Managed backup or sync services must define retention, restore process, and recovery timelines.
Security Policy
Covers roles, device access, password responsibility, license protection, audit expectations, remote support approval, and breach handling.
SLA & Support
Defines support channels, response windows, paid customization, printer/network limits, and hardware dependency responsibilities.
Refunds & Cancellation
Monthly, annual, trial, renewal, cancellation, and refund expectations are documented before purchase.
Compliance Records
GST-ready receipts, reports, and exports support business operations, while final statutory filing remains the merchant or accountant's responsibility.
Responsibility Matrix
Who is responsible for what?
Area
Customer responsibility
Abhikalan responsibility
Website enquiries, demo requests, trial forms
CustomerProvide correct contact and business details.
AbhikalanUse the details for communication, demos, onboarding, and support records.
Offline/local AbhiPOSS data
CustomerProtect the device, users, passwords, database files, and local backups.
AbhikalanProvide product features and support guidance. Abhikalan cannot recover data that was never backed up or shared.
Remote support session
CustomerApprove access, supervise sensitive work, and avoid sharing unnecessary personal data.
AbhikalanAccess only what is needed for the support case and keep support handling limited to the stated purpose.
Managed sync, hosting, or backup
CustomerUse the service as configured and verify business-critical exports.
AbhikalanOperate the agreed service, retention, restore, access, and security process described in the signed plan.
GST, tax reports, invoices
CustomerVerify tax settings, classifications, rates, and returns with their CA or tax advisor.
AbhikalanProvide billing, receipt, tax summary, and export tools based on configured business data.
Printers, network, Android devices, Windows counters
CustomerMaintain working hardware, OS permissions, network availability, and consumables.
AbhikalanSupport compatible configuration and troubleshooting within the agreed support scope.
Offline-first deployments
Suitable when the outlet wants local continuity and direct control of counter data. The merchant must maintain device security, user discipline, power protection, and regular local backups.
Remote and intranet rollouts
Suitable when multiple counters, Android devices, or supervisors need shared access through a server. Network, backup, and access rules should be documented during setup.
Managed backup or hosted services
Suitable when the merchant wants Abhikalan to operate backup, restore, or cloud/sync services. Retention, recovery, and support boundaries should be written into the plan.