Back to Home

Privacy Policy

POPOS - Restaurant POS & Billing

Effective Date: April 19, 2026Last Updated: April 19, 2026

1. Introduction

Welcome to POPOS, developed by Devikon Inc. (“we,” “our,” or “us”). POPOS is a comprehensive Android point-of-sale application designed for restaurants of all sizes. This Privacy Policy explains how we collect, use, disclose, and safeguard your information when you use POPOS.

Summary: POPOS is offline-first. ALL your business data — orders, customers, employees, payments, inventory — is stored locally on your device. We do not have accounts, do not upload your business data to any server, and do not sell your personal information. The only external data collection is anonymous Firebase Analytics, Crashlytics, Performance Monitoring, and Sentry telemetry to help us improve the app.

2. Information We Collect

2.1 Locally Stored Business Data

POPOS stores the following data locally on your device using an encrypted Room database. This data never leaves your device:

  • Customer Information: Names, phone numbers, addresses (for delivery), and order history
  • Employee Data: Names, contact details, attendance records, payroll amounts, and role assignments
  • Order & Transaction Records: Cart items, KOT (Kitchen Order Ticket) data, order status, and timestamps
  • Payment Records: Payment method (cash, card, UPI), amount, and reference number — POPOS records payments but does not process them
  • Menu & Inventory: Categories, products, prices, stock levels, and recipes
  • Vendor & Supplier Data: Contact details and purchase history
  • Daily Market Data: Vendor lists, commission calculations, marketplace records
  • Expense Records: Categories, amounts, dates, and notes
  • Restaurant Settings: Tax configuration, printer setup, receipt templates

2.2 Anonymous Telemetry

We use the following services to collect anonymous usage and diagnostic data so we can improve POPOS. None of this data identifies you or your customers.

  • Firebase Analytics: Screen views, session counts, feature usage patterns, device type, OS version
  • Firebase Crashlytics: Anonymous crash reports including stack traces and device state at the time of crash
  • Firebase Performance Monitoring: App start time, screen render time, network request latency for POPOS's own update checks
  • Sentry: Non-fatal error events and performance traces
  • Firebase Cloud Messaging (FCM): POPOS may receive optional push notifications for app updates and announcements; you can disable them in Android system settings (App info → Notifications)

2.3 Information We Do NOT Collect

  • We do NOT require or collect account credentials (no login/signup)
  • We do NOT upload your customer, employee, order, or payment data to any server
  • We do NOT access your device contacts, photos, or other personal files
  • We do NOT collect location data
  • We do NOT process payments — payment records in POPOS are entered by you for bookkeeping
  • We do NOT share your business data with third parties

3. Restaurant Operator Responsibility

POPOS is supplied as an offline tool. When you record customer details, employee information, or payment data in POPOS, you (the restaurant operator) are the data controller for that information under your local data protection law (for example, the EU GDPR, the UK Data Protection Act, India's Digital Personal Data Protection Act, or your jurisdiction's equivalent).

This means:

  • You are responsible for obtaining any required consent from your customers and employees before recording their personal information.
  • You are responsible for honouring data-subject requests (access, correction, deletion) made by your customers or employees, since the data lives on your device, not ours.
  • You are responsible for safeguarding the device that runs POPOS — physical security, screen lock, and device encryption all matter.
  • You are responsible for backing up your data using POPOS's built-in export tools (Settings → Backup) so you can recover from device loss or damage.

Devikon Inc. does not act as a processor of your customer or employee data because we never see it.

4. How We Use Anonymous Telemetry

We use the anonymous telemetry data described in section 2.2 to:

  • Identify and fix crashes and bugs
  • Understand which POPOS features are most used so we can prioritise improvements
  • Detect performance regressions across device types and Android versions
  • Plan future features that match real-world usage patterns

5. Data Retention

Local business data: retained on your device until you delete it (per record), clear app data, or uninstall POPOS. We have no remote backup of this data.

Anonymous telemetry: retained by Firebase and Sentry under their respective standard retention windows. We do not export or merge this telemetry with any personally identifying data.

6. Children's Privacy

POPOS is a business application intended for restaurant operators and their staff. It is not directed at children under 13, and we do not knowingly collect personal information from children.

7. Changes to This Policy

We may update this Privacy Policy from time to time. The “Last Updated” date at the top reflects the most recent revision. Material changes will be highlighted in the app or on this page.

8. Contact Us

If you have any questions about this Privacy Policy or how POPOS handles data, reach out: