Back to home
Privacy Policy
Legal Document

Privacy Policy

Last updated: February 13, 2026

This Privacy Policy describes how SettleBook handles information when you use our personal finance management app. We are committed to protecting your privacy and being transparent about our data practices.

Your financial data never leaves your device - ever.
01

01Overview

SettleBook is a personal finance management app designed to help you track debts, daily expenses, and subscription payments. The App is available on iOS and Android platforms.

🔒

Key principle: Your financial data stays on your device. We do not store your personal financial information on any server.

02

02Data Stored Locally on Your Device

All of your financial data is stored exclusively on your device in a local SQLite database. This data never leaves your device and includes:

Debt Information

  • Lender name and type (bank or friend)
  • Total amount, paid amount, and remaining balance
  • Payment schedules and due dates
  • Notes and payment history

Expense Records

  • Amount, category, and date
  • Optional notes or descriptions

Bank Statement Data (PDF Import)

  • Parsing data from imported PDF statements (e.g., Kotak, ICICI, HDFC)
  • Transaction history, dates, and category summaries extracted from statements
  • Local Processing: All PDF parsing happens entirely on your device - we never upload your PDFs.

Subscription Details

  • Platform name, cost, and billing cycle
  • Renewal dates and status
  • Payment reminder settings

User Preferences & Security

  • Currency selection and theme preference
  • Notification preferences
  • Security PIN (premium, stored encrypted)
  • Biometric authentication setting (premium)
  • Premium purchase status
03

03Data Collected & Transmitted

While your financial data stays local, we use Firebase services for crash reporting and usage analytics to improve the App.

Firebase Crashlytics (Crash Reporting)

Purpose: Improve app stability and fix bugs.

  • Crash logs and stack traces
  • Device information (model, OS version, screen size)
  • App version and build number
  • Crash timestamps and anonymous crash identifiers
  • Memory and battery state at crash time

Firebase Analytics (Usage Analytics)

Purpose: Understand app usage and improve user experience.

  • Screen views and navigation patterns
  • Feature usage frequency
  • App session duration and frequency
  • Device information (model, OS, language, region)
  • Anonymous user ID (generated by Firebase)
  • In-app purchase events (premium upgrade tracking)
  • Button clicks and user interactions
04

04Data We Never Collect

We want to be clear about what we never collect:

  • Financial transaction amounts or values
  • Your uploaded Bank Statement PDFs or their raw text content
  • Password/PINs used for your bank PDFs
  • Lender names, expense descriptions, or subscription platform names
  • Payment dates, schedules, or history details
  • User email, phone number, or name
  • Location data (GPS coordinates)
  • Contacts, photos, or browsing history
  • Other apps installed on your device
  • PIN codes or biometric templates
  • Any authentication credentials
05

05Internet & Network Usage

The App requires internet connectivity for the following purposes:

  • In-App Purchases: Purchase verification through Google Play or Apple App Store. Managed by the platform, not stored by the App.
  • Firebase Crashlytics: Automatic crash log transmission on crashes.
  • Firebase Analytics: Background transmission of anonymized usage events.
  • Notifications: All notifications are delivered locally - no external push notification service is used.
06

06Data Security

Local Storage Protection

  • All financial data stored in a local SQLite database
  • Data encrypted at device level (OS-managed)
  • Optional PIN lock protection (premium feature)
  • Optional biometric authentication (premium feature)
  • PIN codes stored encrypted on device
  • Biometric templates managed by device OS

Network Security

  • All Firebase connections use HTTPS encryption
  • No custom API endpoints
  • No user authentication tokens

Data Anonymization

  • Firebase Analytics uses anonymous user IDs
  • No personal identifiers linked to analytics events
  • Crash reports contain no financial data
07

07Third-Party Services

Firebase (Google)

Services: Firebase Crashlytics and Firebase Analytics. Data shared includes device technical specs, anonymized app usage patterns, and crash diagnostic information. Processed in the USA on Google Cloud servers.

Firebase Privacy Policy

Google Play / Apple App Store

Used for in-app purchase processing. Payment information is managed entirely by the app stores. Payment data is never accessible to SettleBook.

No Other Third Parties

  • No advertising networks
  • No social media integrations
  • No cloud storage providers
  • No data brokers or affiliates
  • No marketing analytics beyond Firebase
08

08Your Rights & Control

Data Access

  • Financial data is 100% on your device - you have full control
  • Crash reports contain no personal data

Data Deletion

  • Local data: Delete via the App or by uninstalling
  • Analytics data: Automatically deleted after 14 months
  • Crash data: Automatically deleted after 90 days
  • Anonymized analytics cannot be individually deleted (no user account exists)

Data Portability

  • Financial data export is not currently supported
  • Analytics data is anonymized and not tied to your identity
09

09Age Requirements

SettleBook has no age restriction and can be used by anyone. No account registration is required, and all data is stored locally on your device. Parents and guardians should supervise minors using the App. The App is suitable for teaching financial literacy to all ages.

Parental guidance recommended: Parents should review financial data entered by children. In-app purchases require adult authorization via the app store. Premium features (PIN lock) can help parents control access.

10

10Premium Security Features

App Lock (Premium Only):

  • PIN Protection: Create a 4 digit PIN
  • Biometric Authentication: Fingerprint or Face ID (device-dependent)
  • PIN stored encrypted on device only, never sent to servers
  • Biometric templates managed by device OS (Apple/Google)
  • SettleBook never accesses biometric data directly

Important: Forgotten PINs require app reinstall (data loss)

11

11Changes to This Policy

We may update this Privacy Policy from time to time. Firebase-related changes are subject to Google/Firebase policy updates. We recommend reviewing this page periodically to stay informed.

12

12Contact Us

If you have questions about this Privacy Policy or our data practices, please contact us:

Also read our Terms & Conditions

Understand the rules for using Settle Book

Terms & Conditions