Foliq Logo FOLIQ
  • Features
  • Precision Engine
  • Pricing
  • FAQ
  • Privacy Policy
← Back to Home
Google Play Compliant • 100% Offline Pledge

Foliq Privacy Policy

Effective Date: October 10, 2026  •  Last Updated: October 10, 2026

🛡️ Our Privacy Pledge to You

Foliq is engineered from the ground up as an offline-first, privacy-by-design financial application. Your cashbooks, transaction amounts, customer notes, and vendor debts stay exclusively on your physical device. We do not operate cloud tracking servers, we do not sell data, and we do not profile your finances.

1. Information We Do NOT Collect

Unlike traditional bookkeeping and cloud ledger software, Foliq rejects invasive surveillance:

  • No Cloud Ledger Ingestion: Your transactions, books, account balances, and customer credit entries are never uploaded to any remote server.
  • No Contact List Harvesting: Foliq does not scrape or upload your address book to company databases.
  • No Third-Party Advertising Trackers: Foliq contains zero advertising SDKs, zero analytics trackers, and zero behavioral marketing libraries.
  • No Data Monetization: We do not sell, rent, license, or share your financial records with financial institutions, data brokers, or marketing platforms.

2. Information Stored Locally on Your Device

All data generated while using Foliq is saved strictly in your device's private SQLite/Room database (`foliq.db`):

  • Ledger & Cashbook Data: Names of cashbooks, bank/cash/UPI accounts, transaction amounts (stored deterministically in 64-bit integer minor currency units), timestamps, category tags, and optional transaction remarks.
  • Khata Parties: Customer and supplier contact names, optional phone numbers provided by you, opening balances, and debit/credit history.
  • Receipt Images: Locally captured or selected invoice/receipt image files, stored within your application's isolated sandboxed storage directory.
  • User Preferences: Selected theme mode (Obsidian, Cashmere, Paper, System), preferred language (English, Hindi, Hinglish), digit grouping format (Indian Lakh/Crore vs Western Million), and biometric lock preferences.

3. Device Permissions & How They Are Used

Foliq requests only the minimum required Android permissions, strictly utilized for on-device features:

  • Biometric Hardware (`android.permission.USE_BIOMETRIC`): Used to prompt for fingerprint or face authentication on app launch. Biometric verification is executed entirely on-device by the secure Android Keystore hardware environment; Foliq never accesses or stores your raw biometric vectors.
  • Google Play In-App Billing (`com.android.vending.BILLING`): Used exclusively to communicate with Google Play services for purchasing or restoring Foliq Pro subscriptions or lifetime licenses. All payments are processed directly by Google; Foliq never receives or stores your credit card, debit card, or UPI banking credentials.
  • Storage Access Framework (SAF): When you export PDF reports, CSV spreadsheets, or local `.foliq` backup files, Android’s Storage Access Framework opens the system file picker to let you select your destination folder. Foliq never requests broad access to your entire device storage.
  • Internet Permission (`android.permission.INTERNET`): Utilized solely by the official Google Play Billing library to authenticate digital purchase signatures with Google servers. Foliq executes zero background network calls for data transmission.

4. Cryptographic Local Backups (.foliq Container)

To prevent sensitive financial records from being exposed as readable plain text when backed up or shared:

  • Foliq produces a custom encrypted binary backup container with the .foliq file extension.
  • The payload is compressed with GZIP to eliminate repetitive text headers and encrypted with AES-256-GCM (Galois/Counter Mode authenticated encryption) using 256-bit keys derived via PBKDF2 with 10,000 stretching rounds.
  • Opening a .foliq file in text editors or cloud previews yields only unreadable binary ciphertext.
  • Data integrity is validated via SHA-256 cryptographic checksums and GCM authentication tags.

5. WhatsApp & SMS Payment Reminders

When you choose to remind a customer or supplier about an overdue Khata balance over WhatsApp or SMS:

  • Foliq constructs a standard intent URI containing a courteous payment reminder message and amount.
  • The message is passed directly to the messaging application installed on your device (e.g., WhatsApp).
  • Foliq never transmits background messages autonomously or discloses your contact details to third parties.

6. Data Retention, Control & Deletion

Because all records reside locally on your phone, you maintain complete ownership over your ledger:

  • Recycle Bin / Soft Deletions: Deleted transactions are held in a local Recycle Bin where you can restore them or purge them permanently at any time.
  • Cashbook Reset: You can purge all transaction entries for an active book with one tap from Settings.
  • Complete Erasure: Clearing app storage in Android Settings or uninstalling Foliq permanently and immediately erases all database records from your device.

7. Children's Privacy

Foliq is designed as a commercial productivity ledger for business owners, freelance merchants, and independent professionals. We do not knowingly collect or solicit personal data from children under the age of 13.

8. Policy Updates

We may update this Privacy Policy from time to time to reflect product enhancements, architectural updates, or regulatory compliance. Any revisions will be reflected on this page with an updated "Last Updated" timestamp.

9. Contact & Support

If you have questions, feedback, or inquiries regarding Foliq’s privacy architecture and data safety measures, please reach out directly:

  • Developer & Support Email: yogirana5557@gmail.com
© 2026 Foliq Technologies. All rights reserved. 100% Offline & Deterministic Precision.
Home