Effective date: [CONFIRM: publication date]
This Privacy Policy explains how Neplex Technologies Pvt. Ltd. ("Neplex", "Restroplex", "we", "us", or "our") handles information through the Restroplex websites, restaurant-management applications, APIs, support channels, and related services (the "Service"). Our registered office is [CONFIRM: full registered office address].
Restroplex is built primarily for restaurants in Nepal. This policy distinguishes between information we use to operate our own customer relationship and information a restaurant enters into Restroplex about its customers, personnel, suppliers, and operations.
1. Scope and roles
This policy applies to restaurant owners and administrators, authorized restaurant personnel, Restroplex staff and system administrators, prospective customers, website visitors, support contacts, and people whose information a restaurant records in Restroplex.
For account administration, subscriptions, support, security, and our own business operations, Neplex determines why and how information is used. For restaurant records—such as customer, employee, supplier, reservation, order, invoice, inventory, and accounting data—the restaurant generally decides what to enter and how to use it, and Restroplex handles that information to provide the Service. The precise legal characterization may depend on the circumstances and applicable law.
If you are a restaurant customer, employee, or supplier and want to exercise a right concerning information entered by a restaurant, contact that restaurant first. We will reasonably assist the restaurant where appropriate.
2. Information we collect
Account and restaurant information
We collect account identifiers and profile information such as names, email addresses or phone numbers, authentication status, role, position, restaurant memberships, and account status. We also store restaurant and subscription information, which may include restaurant and legal names, addresses, contact details, PAN/VAT information, billing details, operating preferences, plan, subscription status, and payment-receipt files.
Passwords are transformed using a one-way password-hashing function before storage. We also process email-verification, password-reset, and staff-invitation tokens and their expiry times.
Restaurant-controlled operational information
Restaurants may enter and generate:
- employee names, positions, roles, permissions, activity, and transaction attribution;
- customer names, legal names, phone numbers, addresses, PAN details, credit limits, payment terms, dietary preferences, allergies, and restrictions;
- reservations, guest counts, table assignments, orders, delivery details, notes, invoices, returns, payments, balances, and purchase history;
- supplier, purchasing, stock, menu, recipe, tax, accounting, reporting, and audit information;
- uploaded images and documents, including invoice or return attachments and support attachments; and
- printing, kitchen-order, printer-agent, and print-job information.
Invoices may preserve a snapshot of customer information used when the invoice was issued even if the customer profile later changes.
Restaurant-customer payments
Where a restaurant enables eSewa, Khalti, or FonePay, Restroplex facilitates an interaction between the restaurant and its configured payment provider. We may process the provider name, restaurant order reference, amount, payment status, expiry, provider reference, verification results, failure information, and sanitized provider response data. The reviewed implementation does not store card numbers, CVVs, bank passwords, or wallet passwords, and it does not show Restroplex receiving or holding restaurant-customer funds.
The payment provider and restaurant may collect additional information under their own terms and privacy notices.
Communications and support
We store information submitted through contact, demo-request, and support channels. This can include name, email address, phone number, message, ticket description, attachments, restaurant association, and ticket status. If you communicate with us by email, copies may also remain with our email service provider and in the recipient's mailbox.
Usage, device, log, and diagnostic information
Our systems create operational records such as request identifiers, request method and URL, network address, response status, timestamps, authentication and authorization events, error information, export status, audit events, and actions performed in the Service. Audit records may contain actor details and before-and-after values for business records.
We did not identify an active third-party advertising or product-analytics SDK in the reviewed repository. We may still receive ordinary infrastructure logs from hosting, network, database, storage, or email providers used in production. Those providers require confirmation in Section 13.
Public QR menus
A restaurant's public QR menu can display restaurant profile information, menu categories, dishes, add-ons, offers, and related images. The reviewed QR-menu flow does not itself create a customer account or collect an identified visitor's order or payment details. A restaurant may collect information through other Restroplex features.
3. Cookies and browser storage
The reviewed applications use bearer access tokens stored in browser localStorage, not authentication cookies. The applications also use browser storage for product state such as order-taking drafts, recently used command-palette items, and interface-dismissal preferences. Clearing browser storage may sign you out or remove local state.
The reviewed application code does not set a first-party authentication cookie. Hosting, security, or network providers may use cookies outside the reviewed application code; [CONFIRM: production proxy/CDN cookie use].
4. Why we use information
We use information to:
- create and administer accounts, restaurants, roles, and subscriptions;
- provide POS, ordering, reservation, inventory, purchasing, invoicing, accounting, reporting, export, payment-connectivity, printing, and support functions;
- authenticate users, enforce permissions, investigate misuse, and protect the Service;
- send verification, password-reset, invitation, subscription, payment, support, and export communications;
- maintain audit trails and operational records;
- connect enabled restaurants with payment providers and Nepal's Central Billing Monitoring System (CBMS);
- diagnose errors and maintain the reliability and operation of the Service;
- comply with law, lawful requests, and tax or recordkeeping duties; and
- establish, exercise, or defend legal claims.
Depending on the context, we carry out these activities to provide the contracted Service, follow the user's or restaurant's instructions, comply with legal obligations, protect operational and security interests, or act with permission where required. These are practical processing reasons, not an assertion that foreign-law concepts such as GDPR legal bases apply. This policy does not claim that the GDPR, CCPA, or another foreign law necessarily applies.
5. How restaurants must handle information
Restaurants control which customer, employee, supplier, and operational information they enter. Each restaurant is responsible for having a lawful basis or permission to collect and use it, giving any required notices, limiting access, maintaining accuracy, responding to affected people, and meeting its tax, employment, consumer, and recordkeeping duties. Restaurants must not enter information they are not entitled to use.
6. Sharing and disclosures
We may disclose information:
- to personnel and contractors who need it to operate, secure, or support Restroplex;
- to infrastructure, database, cache/queue, storage, email, deployment, and support providers used to operate the Service;
- to a restaurant's users and administrators through the product's configured access controls;
- to eSewa, Khalti, or FonePay when a restaurant enables the relevant gateway;
- to Google Maps Platform when an address-autocomplete feature is configured and used, in which case typed address queries and selected place details may be sent to Google;
- to Nepal's Inland Revenue Department through CBMS when a restaurant enables CBMS, supplies the required seller credentials and configuration, and an eligible tax invoice or return is queued;
- to recipients selected for emailed exports;
- to authorities or other parties where reasonably necessary to comply with law, protect rights or safety, investigate misuse, or respond to valid legal process; and
- in connection with a merger, financing, acquisition, reorganization, or sale of all or part of the business, subject to appropriate confidentiality and applicable law.
We do not claim that every listed integration is enabled for every restaurant. We do not sell restaurant data for monetary consideration.
7. Payments and subscription receipts
Restroplex subscription payments currently use bank or QR instructions followed by receipt upload and manual review. We store the subscription record and submitted receipt. The current implementation stores receipts on server file storage; production access restrictions, migration and backup treatment require confirmation. This is separate from payment-gateway transactions between a restaurant and its diners.
For restaurant-customer payments, the reviewed integration provides technical connectivity using a restaurant's merchant configuration and does not show Restroplex receiving or holding restaurant-customer settlement funds. The provider processes the financial transaction under its own arrangements with the restaurant and payer. Restroplex's final regulatory characterization must be confirmed by Nepal-qualified counsel.
8. Email and exports
We use an environment-configured SMTP service to send transactional messages. The production SMTP provider is [CONFIRM: provider and processing location]. Data exports may be generated as spreadsheet attachments and emailed to addresses chosen by an authorized user. Once delivered, copies may remain in mailboxes or systems controlled by the recipient or email provider.
9. File storage
The Service supports local, MinIO, or S3-compatible object storage, depending on deployment. Uploaded images may be converted to WebP and may have preview copies. Some deployments and file categories use publicly addressable object URLs. Do not upload secrets or documents that the restaurant is not authorized to store.
Production storage provider, access configuration, and region are [CONFIRM: provider, bucket access model, and region].
10. Data location and international processing
The repository does not establish a fixed production hosting country or guaranteed data residency. Our production hosting, database, Redis, storage, deployment, and email providers and their processing locations are [CONFIRM]. Information may be processed outside the user's location where those services operate. Before publication, Neplex must identify any cross-border processing and confirm the safeguards and notices required by Nepal law and applicable contracts.
11. Retention, deletion, and exports
We retain information while an account or restaurant uses the Service and afterward as reasonably needed to provide the Service, maintain business and audit records, meet legal or tax obligations, resolve disputes, enforce agreements, preserve security records, and complete deletion or backup cycles.
The current product commonly uses soft deletion: records are hidden or deactivated but remain stored. The current repository does not implement a general automatic purge schedule, and plan settings described as retention limits operate as display cutoffs rather than verified deletion. We therefore do not promise a fixed deletion period.
Restaurant deletion in the reviewed implementation deactivates or marks central records as deleted but does not automatically drop the restaurant database. Self-service account erasure is not currently implemented. To request access, correction, export, or deletion, contact us and, for restaurant-controlled information, the relevant restaurant. We may retain information where required or permitted by law, where needed for legitimate records, or while a valid dispute is pending.
Authorized users can export certain restaurant records. The availability and format of exports depend on the feature and account state. A post-termination export window is [CONFIRM: business policy].
Backup practices, backup retention, and restore procedures are [CONFIRM: operational practice]; the repository does not establish them.
12. Security
Verified application measures include one-way password hashing, expiring signed access tokens, role and permission checks, restaurant-specific database routing, input validation, and application encryption of configured payment-gateway and CBMS credentials before database storage.
No system is completely secure. Access tokens are stored in browser local storage, some uploaded objects may be publicly addressable depending on deployment, and security also depends on restaurant administrators, users, devices, networks, and third-party providers. Users must protect credentials, restrict authorized-user access, keep devices secure, and promptly report suspected compromise. We do not make a warranty of absolute security or claim any certification not expressly identified in a separate written agreement.
13. Service providers requiring production confirmation
The code supports PostgreSQL, Redis and Bull queues, configurable local/MinIO/S3-compatible storage, SMTP email, Google Maps address autocomplete, Coolify-based deployment triggers, OpenPrinter/OPPA printing agents, eSewa, Khalti, FonePay, and IRD CBMS. Deployment-dependent OpenTelemetry instrumentation may also create operational telemetry. The actual production hosting, database, storage, Redis, SMTP, maps, CDN/WAF, telemetry/monitoring, and backup vendors and regions must be inserted here before publication: [CONFIRM: production subprocessor list, purpose, and location].
14. Privacy rights and choices
Subject to applicable law, product capability, and the restaurant's legal obligations, you may ask us or the relevant restaurant to access or correct personal information about you, address an inappropriate use, request deletion, or provide an available export. A particular remedy is not guaranteed where the law does not require it or an exception applies. We may need to verify identity and authority and may direct a request to the restaurant that controls the relevant operational record.
Nepal's Privacy Act, 2075 (2018) and Privacy Rules, 2077 (2020) protect personal privacy and regulate the handling of personal information. Rights and remedies depend on the facts and governing law. This policy does not limit non-waivable legal rights.
Transactional messages needed for accounts, security, subscriptions, and service delivery are not marketing messages. The reviewed repository does not establish a promotional-email program. If marketing email is introduced, [CONFIRM: consent and unsubscribe process] must be documented.
15. Children
Restroplex is a business service and is not designed for children to create accounts. The minimum age for authorized users is [CONFIRM: minimum age and employment-related exception]. Restaurants must not use the Service to collect children's information unless legally permitted and necessary for their operations.
16. Changes to this policy
We may update this policy as the Service, providers, or law changes. We will post the revised policy with a new effective date and provide any additional notice required by law or contract. Material changes will not apply retroactively where prohibited.
17. External links and public payment links
Restroplex pages may link to payment providers, Google services, social networks, Messenger, review sites, or other external services. Those services may receive ordinary browser request information and are governed by their own notices. A public payment link also displays limited payment-intent status to anyone who possesses its hard-to-guess identifier; restaurants and users must not publish or forward such links unnecessarily.
18. Contact
Privacy requests and questions may be sent to [CONFIRM: privacy/legal email; current product contact is [email protected]] or to [CONFIRM: postal address]. Restaurant customers and personnel should also contact the relevant restaurant.
This policy should be reviewed by Nepal-qualified counsel before publication.