Privacy Policy
How ERPX collects, uses, shares and retains data.
Last updated: 3 November 2026
ERPX ("we", "us", "our") operates the ERPX mobile application and web platform at app.erpx.co.in (collectively, the "Service"). This Privacy Policy explains what data we collect, why we collect it, how it is used and shared, how it is retained, and the rights and choices available to users under applicable Indian law, including the Digital Personal Data Protection Act, 2023 ("DPDP Act") to the extent applicable.
This Policy is intended to work together with the ERPX Terms and Conditions.
1Who We Are
ERPX is a sole proprietorship operated by:
Anirudh Maruti Killekar
Sy. No. 92/A, Shri Narayan Building, Bhagyanagar 9th Cross, Belagavi, Karnataka 590006, India
Email: support@erpx.co.in
WhatsApp: +91 84314 02908
2Our Role and Business Customer Responsibility
ERPX is primarily a software platform for businesses. Depending on the type of data and processing, ERPX may process personal data on behalf of a business customer as a service provider/data processor, while the business customer may remain responsible for deciding why and how its customer, supplier, employee or other personal data is collected and used. Where ERPX determines purposes of processing for its own services, ERPX will act in the role required by applicable law.
Business customers are responsible for ensuring that they have the rights, notices, permissions and lawful basis required to provide personal data to ERPX for processing.
3Data We Collect
3.1 Account Information
- Name, email address, password or authentication credentials in protected form, and Firebase Authentication UID or equivalent account identifier.
3.2 Business Data
- Business/company name, GSTIN, address, state, pincode and related business information.
- Customer and supplier records, including names, contact details, GSTINs and addresses.
- Invoices, purchase records, expenses, payments, credit notes, delivery challans and purchase orders.
- Inventory, production, stock, warehouse and related operational records.
- Journal entries and chart of accounts.
- Bank transaction information contained in bank-statement files uploaded by the user.
- Employee, reimbursement or other records added by the business through features enabled in the Service.
3.3 Documents and Images
- Bill/receipt images for AI scanning.
- Business cards and other business documents uploaded by users.
- Bank statement PDFs.
- Company logos.
- Documents or PDFs generated through the Service.
3.4 Usage and Technical Data
- Audit logs of actions performed within the Service.
- Device or push-notification identifiers where required for notification delivery.
- Technical information reasonably necessary to secure, operate and troubleshoot the Service, such as logs, timestamps, IP/network information or device/browser information, where collected.
3.5 Data We Do Not Intentionally Collect
- Precise location unless a future feature expressly requires it and provides an appropriate notice.
- Contacts, calendar, SMS or call logs unless a future feature expressly requires it and provides an appropriate notice.
- Health, fitness or biometric data unless a future feature expressly requires it and provides an appropriate notice.
- Payment instrument details such as full card numbers, bank-account credentials or UPI credentials where those are collected directly by the payment provider rather than ERPX.
4Why We Use Data
| Purpose | Typical basis / context |
|---|---|
| Provide and secure the Service โ invoicing, accounting, GST-related reports, inventory, production, CA portal and other requested functions | Performance of the service, user request, consent where required, and other lawful grounds under applicable law |
| Process subscription payments | Payment processing and performance of the subscription contract |
| AI document scanning and AI-assisted functions | User-requested processing; consent where required by law |
| Push notifications and service communications | User settings, service necessity, consent where required, or other applicable lawful basis |
| Audit logs, fraud prevention and security | Legitimate security/operational needs, legal requirements or other lawful grounds |
| Customer support and service improvement | Service provision, user request, legitimate operational purposes or consent where required |
5AI Processing and Extraction Records
ERPX may use third-party AI services, currently including Google Gemini API and Anthropic Claude API, for document extraction or other user-requested AI functions.
- AI processing is initiated by a user action such as selecting Scan or another AI function.
- Uploaded documents may be transmitted to the selected AI provider for processing and returned to ERPX.
- ERPX will use the provider configuration and contractual terms applicable to the API service used at the time.
- AI providers and processing arrangements may change as ERPX evolves; material changes will be reflected in this Policy where required.
- Where technically supported, ERPX will not use customer content to train its own models unless separately disclosed and permitted by applicable law and customer terms.
5.1 Original Source and Original Extraction
To support auditability, ERPX may preserve the original uploaded document and the initial AI-extracted result as read-only records. If a user later edits, corrects, confirms or rejects an extracted value, the later user action may be stored separately from the original extraction. This is intended to help distinguish what the user originally submitted, what ERPX initially extracted, and what the user subsequently approved or changed.
Retention of source documents and extraction records is subject to the retention rules described in this Policy and applicable law.
6Payment Processing
Subscription payments may be processed by Razorpay Software Private Limited or other payment providers. The payment provider may collect payment instrument details directly. ERPX generally receives transaction identifiers, status, amount and related subscription information needed to activate and manage the subscription. The payment provider's own privacy policy also applies to data it collects.
7Data Sharing and Service Providers
ERPX does not sell customer personal data. ERPX may share or disclose data to service providers and other recipients where reasonably necessary to operate the Service, fulfil user requests, protect the Service, comply with law, or perform other functions described in this Policy.
| Provider / Category | Purpose | Typical data |
|---|---|---|
| Firebase / Google Cloud | Authentication, database, storage, cloud functions | Account information and business records |
| Razorpay or payment provider | Subscription payment processing | Payment and subscription transaction information |
| Google Gemini API | AI document processing | Uploaded documents submitted for AI processing |
| Anthropic Claude API | AI document processing fallback or other AI functions | Uploaded documents submitted for AI processing |
| Vercel or web-hosting providers | Web application delivery | Technical/web traffic information |
| Cloudflare R2 or backup storage providers | Encrypted backup/disaster recovery | Encrypted backup archives |
| Email, notification and messaging providers | Transactional communications and notifications | Email address, notification identifiers and relevant message metadata |
ERPX may replace or add providers as the Service evolves. Where required, ERPX will maintain appropriate contractual, security and privacy safeguards.
8CA Portal and Authorised Access
If a business owner or authorised administrator invites a Chartered Accountant to access the business account, the CA may receive access to financial records, reports, GST-related data, exports, correcting entries or other functions configured for that CA role.
- The business customer controls the CA invitation and may revoke access through the available controls.
- CA access and significant CA actions may be logged for audit and security purposes.
- CA access does not transfer ownership of the business account or its data to the CA.
- ERPX is not responsible for professional advice, filing decisions or other professional services performed by the CA.
9Account Ownership, Recovery and Identity Verification
Because ERPX may hold business records for many years, ERPX must protect against unauthorised requests for historical data or account control.
- A person asking ERPX to release old data, change the primary administrator, replace a registered email address, restore access or transfer account control may be required to complete enhanced verification.
- Verification may include prior account information, verified email or phone, billing information, business documents, identity documents, proof of authority, or other reasonable evidence appropriate to the request.
- Login access or possession of an old email account may not by itself establish legal ownership of the business.
- Where an account owner is deceased, incapacitated or unavailable, ERPX may require appropriate legal or business documentation before changing account control or releasing sensitive records.
- Where ownership is disputed, ERPX may pause sensitive account changes until entitlement is established.
- ERPX will use identity documents or other verification information only for the verification purpose and will retain them only as long as reasonably necessary, subject to applicable law.
10Data Storage and Security
- Data is stored using cloud infrastructure and security controls appropriate to the Service.
- Data is encrypted in transit and, where supported by the infrastructure, at rest.
- Authentication credentials are handled through authentication infrastructure rather than stored by ERPX in plain text.
- Sensitive server-side credentials and API keys are protected using secure server-side mechanisms.
- Access controls, rate limiting, subscription controls, logging and security reviews are used as appropriate.
No storage or transmission system can be guaranteed completely secure. ERPX will take reasonable steps to investigate and respond to suspected security incidents and provide notices required by applicable law.
11Data Retention
| Data | Indicative retention | Reason |
|---|---|---|
| Financial and statutory business records | For the period required or permitted by applicable law; ERPX may retain such records for up to 7 years or longer where legally required | Legal, tax, GST, accounting, audit or dispute requirements |
| Account information | Until account deletion, subject to lawful retention exceptions | Service provision and account management |
| Audit/security logs | For as long as reasonably necessary, and up to periods required for security, legal or financial audit purposes | Security, accountability and dispute handling |
| AI scan documents and extraction records | As described in this Policy and based on the requested workflow; some source records may be retained for auditability | Service, audit trail and lawful retention |
| Backups | Rolling retention, currently targeted at up to 12 months unless a longer period is needed for security, legal or disaster-recovery reasons | Disaster recovery |
Retention periods may be extended where necessary to comply with law, resolve disputes, investigate fraud or security incidents, or establish/exercise/defend legal claims.
12Access, Correction, Export and Deletion
Subject to applicable law, users may request access to, correction of, export of, or deletion of personal data through the mechanisms made available by ERPX. Where the request concerns business data controlled by a business customer, ERPX may direct the requester to the business customer or administrator.
12.1 Identity Verification
ERPX may verify the identity and authority of a requester before providing access, changing account control, or deleting data.
12.2 Account Deletion
Users may initiate account deletion from Settings → Delete account in the app, through the account deletion page, or by contacting support@erpx.co.in. ERPX will process valid deletion requests subject to verification and applicable retention obligations.
12.3 What May Be Deleted
Subject to applicable law and retention requirements, deletion may include account credentials, business profile information, uploaded documents, personal data, stored PDFs and other information associated with the account.
12.4 What May Be Retained
ERPX may retain records that it is required or permitted to retain for tax, GST, accounting, audit, security, fraud prevention, legal claims or other lawful purposes. Where reasonably appropriate and technically feasible, retained records may be separated from active user access or de-identified/anonymised as permitted by law.
12.5 Historical Data Requests After Discontinuation
A former user requesting data years after discontinuing ERPX may be required to provide enhanced evidence that they are entitled to that data. ERPX may refuse or delay disclosure where identity or legal authority cannot be reasonably established.
13Nomination and Death / Incapacity
Where applicable under Indian law, ERPX may support nomination or similar mechanisms for exercise of certain data rights after death or incapacity. A nominee or successor may still be required to establish identity and authority. The final process and evidence requirements may depend on the legal status of the account, business structure and applicable law.
14Children's Privacy
ERPX is intended for business users and is not directed to children. ERPX does not knowingly seek to collect personal data from persons under 18 for independent use of the Service.
15Cookies, Analytics and Tracking
The ERPX web application may use essential cookies, local storage or similar technologies for authentication, session management, security and necessary operation. If ERPX introduces analytics, advertising or non-essential tracking technologies, the Privacy Policy and applicable disclosures will be updated as required.
16Legal and Regulatory Disclosures
ERPX may disclose information where required by applicable law, court order, government or regulatory request, or where reasonably necessary to detect, prevent or investigate fraud, security threats, unlawful activity or harm.
17Business Transfer, Merger or Acquisition
If ERPX is involved in a merger, acquisition, restructuring, sale of assets, financing or similar transaction, customer data may be transferred as part of the transaction, subject to applicable law, confidentiality obligations and appropriate safeguards. Users will be notified where required.
18International Processing and Infrastructure
ERPX may use infrastructure or service providers located in India or other jurisdictions. Where personal data is processed outside India, ERPX will apply the safeguards required by applicable law and the contractual or technical arrangements governing the relevant service providers.
19Changes to this Privacy Policy
ERPX may update this Privacy Policy as the Service, providers, features or legal requirements change. Significant changes will be communicated through the Service, email or another reasonable method where required. The 'Last Updated' date will be revised when the Policy changes.
20Grievance Officer
Subject to applicable law and the final legal review of ERPX's designation obligations, the current grievance contact is:
Name: Anirudh Maruti Killekar
Email: support@erpx.co.in
Address: Sy. No. 92/A, Shri Narayan Building, Bhagyanagar 9th Cross, Belagavi, Karnataka 590006, India
Complaints will be handled within the timelines required by applicable law.
21Governing Law and Contact
This Privacy Policy is governed by the laws of India, subject to applicable data-protection and consumer-protection requirements.
For privacy questions, access, correction, deletion or grievance requests:
Email: support@erpx.co.in
WhatsApp: +91 84314 02908
Address: Sy. No. 92/A, Shri Narayan Building, Bhagyanagar 9th Cross, Belagavi, Karnataka 590006, India