Your Data is Safe With Us

We NEVER sell, share, or monetize your data. Your business information is used solely for FBR e-invoicing compliance. Period.

🔒

No Data Selling

Your data is never sold, rented, or shared with advertisers or third parties.

🔐

End-to-End Encryption

TLS 1.2+ in transit, encrypted at rest. Your data is protected at every layer.

🏳

FBR Compliance Only

Invoice data goes to FBR as legally required. Nothing else leaves our servers.

Privacy Policy

Last Updated: March 25, 2026 | Developer: Muhammad Mazhar Aleem

1. Our Promise — We Never Sell Your Data

Riyazee will NEVER sell, rent, trade, or monetize your business data, personal information, or any data collected through this platform to any third party — for any purpose, at any time. This is an unconditional commitment.

2. Data We Collect

  • Business Information: Business name, NTN, STRN, address, phone, email — required for FBR compliance
  • Invoice & Financial Data: Sales/purchase invoices, buyer/supplier details, tax calculations, HS codes, FBR responses
  • Location Data (Optional): GPS coordinates when creating invoices, receipts, refunds, and POS transactions — used to enable fraud prevention, misuse detection, stolen-device geofencing, cashier accountability, refund integrity, AML signals, field-sales verification, provincial tax jurisdiction verification, and audit defense. You can disable this anytime in Settings → Privacy.
  • Camera Data (Barcode Only): Used only to scan product barcodes for inventory/POS. No photos or videos captured or stored.
  • Device Data: Device type, OS version, app version, connectivity status. No advertising IDs or tracking.

3. How We Use Your Data

  • FBR Compliance: Submitting digital invoices to FBR as required by Pakistani tax law
  • Business Operations: Invoice management, buyer records, catalog, POS, tax calculations
  • Security: Location tagging for fraud detection, audit trails, device fingerprinting for unauthorized access

4. Who We Share Data With

  • FBR Only: Invoice data submitted to Federal Board of Revenue as legally required
  • No Advertisers: We do not share data with any advertising network
  • No Analytics Firms: We do not share data with third-party analytics services
  • No Data Brokers: We do not sell data to data brokers or aggregators
  • No Partner Sharing: We do not share data with business partners
  • Location Data: Used internally for fraud prevention and audit defense; FBR DI API V1.12 payload (business address and province ARE submitted as required by law). Riyazee will comply with applicable laws.

5. Data Storage & Security

  • Hosted on Amazon Web Services (AWS), encrypted in transit (TLS 1.2+) and at rest
  • JWT authentication with HS256 signing, Super Admin PIN verification
  • Local data encrypted with device-specific keys (iOS Keychain / Android EncryptedSharedPreferences)
  • Role-based access control with 8 permission levels
  • 11 security headers (Helmet): HSTS, X-Frame-Options, CSP, CORS, etc.
  • Input sanitization, SQL injection prevention (Prisma ORM), rate limiting
  • All local data wiped on logout or account deletion

6. Data Retention

  • Active Accounts: Data retained while your account is active
  • Deleted Accounts: Personal data deleted after 30-day grace period
  • FBR Records: Retained for 7 years as required by Sales Tax Act, 1990 (Section 24) and Income Tax Ordinance 2001 (Section 174)
  • Account Deletion: You can cancel within 30 days to reactivate

7. Your Rights

  • Access: View all your data through the app at any time
  • Correction: Update your business profile in Settings
  • Deletion: Request account deletion (30-day grace period, FBR data retained per law)
  • Portability: Export invoices as PDF
  • Opt-out: Disable location collection, deny camera access — core invoicing still works

8. Permissions Explained

Camera Permission

Used exclusively to scan product barcodes (EAN-13, UPC-A, Code128, QR) for inventory management and POS receipts. No photos, videos, or images are captured or stored. You can deny camera access and manually enter barcodes instead.

Location Permission

Why GPS is collected:

  • Fraud prevention — detecting ghost invoices, phantom deliveries, and fabricated transactions issued from locations inconsistent with the business's registered branches
  • Misuse detection — identifying credential sharing, unauthorized off-site invoicing, and stolen device activity through location anomalies
  • Cashier and shift accountability — verifying POS staff are physically present at the registered branch during their shifts
  • Stolen device geofencing — if a registered POS device transmits from outside the business's known operating region, it can be auto-locked
  • Anti-money-laundering signals — unusual location patterns inconsistent with normal business operations feed into AML pattern detection
  • Field sales / mobile invoicing verification — for distributors and field agents, GPS proves invoices were actually issued at the customer's premises (prevents phantom delivery fraud)
  • Refund integrity — ensuring refunds are processed at the same location as the original sale to prevent collusion
  • Provincial tax jurisdiction verification — confirming invoices are issued in the correct province for PRA / SRB / KPRA / BRA compliance
  • Audit defense — providing a forensic location + timestamp trail to defend taxpayers against FBR audit challenges

Your control: You can disable GPS capture anytime from Settings → Privacy inside the app, or from your device's system settings (iOS Settings → Riyazee → Location, or Android Settings → Apps → Riyazee → Permissions). The app remains fully functional without location access. Disabling GPS reduces fraud-detection effectiveness, weakens cashier accountability, and may limit Audit Defense coverage. Location data is stored securely, never sold, never used for advertising, and never shared with third parties for marketing purposes.

Note: Pakistan's FBR Digital Invoicing framework requires business address and province on every invoice. GPS coordinates are used internally for fraud prevention, misuse, lost/stolen device safeguard and audit defense.

Push Notifications

FBR submission confirmations, onboarding progress updates, and account alerts. No marketing or promotional notifications. You can disable in device Settings.

Terms of Service

1. Service Description

Riyazee provides FBR Digital Invoice compliance, business management, inventory, and POS features for registered Pakistani businesses.

2. User Responsibilities

  • Provide accurate business registration information (NTN, STRN)
  • Ensure invoice data accuracy before FBR submission
  • Maintain confidentiality of login credentials and SA PIN
  • Comply with all applicable Pakistani tax laws and FBR regulations
  • Not attempt to reverse-engineer, modify, or exploit the application

3. Subscriptions & Payments

Subscriptions are purchased exclusively via Apple App Store or Google Play Store. Billing is managed by the respective store. Web dashboard access matches your mobile plan tier. No payment information is stored by Riyazee.

4. Limitation of Liability

Riyazee is provided on an "as-is" basis. The developer is not liable for FBR penalties from user data errors, service interruptions, or data loss beyond commercially reasonable measures. Total liability shall not exceed subscription fees paid in the preceding 12 months.

5. Governing Law

These terms are governed by the laws of Pakistan. Disputes shall be resolved in the courts of Islamabad.

Security Policy

TLS 1.2+ Encryption

All data encrypted in transit between your device and our servers

Encrypted Storage

Data encrypted at rest on AWS servers and on your device

JWT Authentication

HS256 signed tokens with session timeout (30 minutes)

Super Admin PIN

Additional PIN verification for administrative access

Biometric Auth

Face ID and Fingerprint authentication supported

8-Level Role System

SUPER_ADMIN → OWNER → ADMIN → MANAGER → OPERATOR → VIEWER hierarchy

Rate Limiting

Authentication endpoints limited to prevent brute force attacks

CORS Protection

Only authorized origins can access the API

Input Sanitization

All HTML/script tags stripped from inputs (XSS prevention)

SQL Injection Prevention

Prisma ORM with parameterized queries — no raw SQL

11 Security Headers

HSTS, X-Frame-Options, CSP, X-Content-Type-Options, Referrer-Policy, etc.

Cross-Business Isolation

Each business's data is completely isolated at the API level

Audit Logging

All sensitive operations logged with user, timestamp, and action

No Server Info Leaked

404 errors return JSON, no stack traces or server details exposed

No Cookies

Stateless JWT auth — no CSRF vulnerability

Device Tamper Detection

Root/jailbreak and debugger detection on mobile

For privacy inquiries, data access requests, or account deletion:

support@cosmos-solutions.com

Developer: Muhammad Mazhar Aleem | Platform: riyazee.com