Privacy Policy

Privacy Policy for Receptify

Last updated: March 5, 2026

Overview

Receptify is an expense tracking application that allows users to record expenses and synchronize encrypted data with their Google Drive.

Receptify does not operate its own backend servers. Most data processing occurs locally on the user's device.

When you sign in with your Google account, the application synchronizes encrypted expense data and receipt files with your Google Drive in order to provide backup and multi-device access.

Information We Process

Receptify may process the following types of information when you use the application.

Expense records

Examples include expense amount, date, description, category, timestamps, and receipt references.

Processing location: Primarily on the user's device.
Storage location: Stored locally on the device and synchronized in encrypted form to the user's Google Drive.
Sharing: Data is transmitted only to Google Drive for synchronization purposes.

Receipt files

Users may attach receipt images or PDF files to expense records.

Processing location: Receipt images may be processed locally on the device for viewing or text recognition.
Storage location: Stored locally on the device and synchronized in encrypted form to the user's Google Drive.
Sharing: Receipt files are uploaded to Google Drive to support synchronization and backup.

Wallet notification data (optional feature)

If the user enables wallet notification capture, the app may read notification text to help detect expense information.

Processing location: All parsing occurs locally on the device.
Storage location: Stored temporarily on the device until the user confirms or saves the entry.
Sharing: Notification data is not shared with external services unless it becomes part of an expense record that is later synchronized to Google Drive.

Google account information

When you sign in using Google Sign-In, the application may access basic profile information such as your name and email address.

Purpose: Used to authenticate the user and associate synchronized data with the correct Google account.
Storage location: Account identifiers may be stored locally on the device for session management.

Sharing: Obtained directly from Google authentication services.

App settings and configuration

Examples include application preferences, categories, and display settings.

Processing location: On-device.
Storage location: Stored locally on the device and synchronized in encrypted form to Google Drive.
Sharing: Shared only with Google Drive as part of the synchronization process.

Google Sign-In and Google APIs

Receptify uses Google authentication and APIs to enable account login and synchronization.

The app requests the following Google OAuth scopes:

https://www.googleapis.com/auth/drive.file
https://www.googleapis.com/auth/userinfo.profile
https://www.googleapis.com/auth/userinfo.email

Purpose:

drive.file: Allows the application to create, read, update, and delete files created by Receptify in the user's Google Drive.
userinfo.profile and userinfo.email: Used to identify the signed-in user and manage account access.

Google Drive Usage

Receptify stores synchronized data in the user's Google Drive account.

The application creates a folder within the user's Google Drive where encrypted application data and optional receipt files are stored.

Important notes:

All synchronized expense data and receipt files are encrypted before being uploaded.

Users can delete synchronized data either from within the application or directly through their Google Drive account.

Users may disconnect Google Drive access at any time by signing out of the application or revoking access in their Google Account permissions.

Third-Party Services

Receptify uses the following third-party services provided by Google.

Google Identity Services (Google Sign-In)

Used for account authentication and authorization.

Google Drive API

Used for synchronization and storage of encrypted application data.

Google ML Kit / On-device text recognition

Used to detect and extract text from receipts directly on the device.

Receipt text recognition is performed locally on the device and is not transmitted to any Receptify-operated servers.

The current codebase does not include advertising SDKs or analytics services.

Permissions Used

The application may request the following permissions:

INTERNET
Required to communicate with Google authentication and Google Drive APIs.

ACCESS_NETWORK_STATE
Used to detect network availability.

POST_NOTIFICATIONS
Used for application notifications.

USE_BIOMETRIC / USE_FINGERPRINT
Used for biometric confirmation for sensitive operations.

Notification listener service
Used only if the user explicitly enables wallet notification capture within Android system settings.

Data Retention and Deletion

On-device data
Data remains stored on the device until the user deletes it in the app, clears application data, or uninstalls the application.

Google Drive data
Files stored in Google Drive remain there until deleted by the user or removed through the application.

Account access
Users may disconnect their Google account at any time or revoke application access from their Google Account permissions settings.

Security

Receptify encrypts expense data and receipt files before uploading them to Google Drive.

Sensitive locally stored information may be protected using Android secure storage mechanisms.

While no system can guarantee absolute security, we use reasonable safeguards to protect user data.

Children's Privacy

Receptify is not intended for children under the age of 13.
We do not knowingly collect personal information from children under 13.

Changes to This Policy

We may update this Privacy Policy as the application evolves.
The "Last updated" date will reflect the latest version.

Contact

If you have questions about this Privacy Policy, please contact: receptify.dev@gmail.com

Page updated

Google Sites

Report abuse