Privacy Policy
Expense Management | Last updated: 23 March 2026
This Privacy Policy explains how Expense Management
(“we”, “us”, or “our”) collects, uses, and shares information when you use our mobile application.
Please review this policy before using the app.
Important: This is a template based on the current app functionality
in this project (OTP-based phone login, syncing expenses, and local caching using Hive).
Please have legal counsel review and update placeholders before publishing on Google Play.
1. What information we collect
-
Phone number:
We collect your phone number to send you a one-time password (OTP) for authentication.
-
OTP and authentication results:
We process the OTP you enter and the outcome of OTP verification to sign you in.
-
Account and session data:
After verification, we may receive and use an authentication token and a user identifier.
-
Expense information you enter:
Amount, category, description, date, and optional attachments (as supported by your backend).
-
Local cached data (on your device):
The app stores an auth token and cached expenses locally using Hive.
-
Technical data:
When you use the app, network requests may include technical information such as IP address,
device identifiers, and request logs.
2. How we use your information
-
Authentication: to verify OTP and provide access to your account.
-
Expense management: to create, list, filter, and retrieve your expenses.
-
Sync and offline fallback: the app caches expenses locally so it can display data
even when the network is unavailable.
3. How we share information
We do not sell your personal information. We may share information in the following cases:
-
Service providers:
We may use third parties that help us deliver the app (for example, hosting providers for our backend
and the messaging service used to deliver OTPs).
-
Backend systems:
To authenticate and sync expenses, your information is sent to our backend APIs.
4. Security
We take reasonable administrative, technical, and organizational measures to protect information.
For example, data is typically transmitted over HTTPS.
Note: This app currently stores an auth token and cached expenses locally using Hive (not encrypted by default).
If you want stronger local protection, consider using an encrypted storage solution and update this policy accordingly.
5. Storage and retention
-
Local storage:
Cached expenses and authentication data may remain on your device until you clear the app data
or the app removes them.
-
Server storage:
Expense data and authentication-related data may be retained for as long as needed
to provide the services described in this policy, unless you request deletion earlier.
6. Your choices
Depending on your location, you may have rights to access, correct, or delete certain information.
To make a request, contact us using the details in the “Contact” section below.
For privacy questions, contact:
[email protected]
8. Changes to this policy
We may update this Privacy Policy from time to time. If we make material changes, we will update
the “Last updated” date at the top of this page.