This policy explains how the Receptify Android app, the app.receptify.dev web app, and the receptify.dev product website process information. Android and web use the user's own Google Drive; anonymous product-research data is handled separately.
1. Receptify Android and web app overview
Receptify is an expense and receipt tracking tool. Synchronized financial records are encrypted in the Android device or the user's browser before being stored in the user's own Google Drive. Receptify does not operate a centralized backend database that stores readable financial records.
2. Information processed by the Android and web apps
Expense records and receipts
These may include amount, date, description, category, timestamps, labels, and receipt images or PDFs. They are processed primarily on the device and may be synchronized to the user's Google Drive in encrypted form.
Wallet notification data
If the user explicitly enables Wallet notification capture, the app may read supported payment-notification text and parse it locally. A notification remains a pending import until the user confirms it. It may be synchronized only after it becomes part of an encrypted expense record.
Google account information
Google Sign-In may provide name, email address, and account identifiers for authentication, session management, and associating synchronized data with the correct Google Drive account.
Settings
Categories, budgets, display preferences, and other settings may be stored on the device or in the browser. Some settings may be included in encrypted synchronization data.
3. Google APIs and third-party services
The Android and web apps use Google Identity Services and Google Drive API. The Android app also uses Google ML Kit. The Drive drive.file scope allows Receptify to manage files created by Receptify or selected by the user for use with Receptify. Receipt text recognition runs on the Android device.
Users may sign out, revoke access through Google Account permissions, or delete Receptify-created files from Google Drive at any time.
4. Local and Google Drive information used by the web app
After the user explicitly authorizes access, app.receptify.dev reads and writes the Google Drive files used by Receptify. Expense contents are decrypted only in the browser. If the user chooses to remember the device, the decryption password is encrypted with a non-exportable browser key before local storage. Google access tokens remain short-lived and are not stored as long-term credentials on Receptify servers.
5. Anonymous information processed by the product website
The receptify.dev product website does not access expense records, receipts, Google account information, or Google Drive data used by the Android or web apps. To understand product demand and download sources, the product website may record:
- A randomly generated anonymous identifier stored in the browser.
- Language version, page path, and broad device type (mobile, tablet, or desktop).
- Explicit product events such as visiting the website, selecting Web or Google Play, connecting Drive successfully, creating or unlocking the encrypted vault, saving the first Web expense, and returning on another day.
- A randomly shown hypothetical Premium price and voluntary response.
- Button placement and UTM source, medium, and campaign values.
- The time of an event, response, or click.
These anonymous measurements never include a Google account, email, encryption password, expense amount, description, category, receipt content, or Google Drive file content. The website does not enable automatic behavioral recording or advertising tracking.
These records do not contain a name, email address, payment information, or in-app financial records. Pricing research is not a subscription or purchase and does not result in a charge.
6. Product website storage and traffic analytics
Anonymous research data is stored in structured storage provided by ChatGPT Sites. Local Storage keeps the anonymous browser identifier and assigned price group so one browser is not repeatedly counted. ChatGPT Sites may also produce aggregate page-view and unique-visitor metrics and standard technical records needed to operate the service. The Receptify product website does not add advertising SDKs or third-party behavioral analytics SDKs.
7. Sharing, retention, and deletion
Android and web app information is sent only to relevant Google services for sign-in, synchronization, and features the user selects. Product website research data is not sold and is not used for targeted advertising. Information is retained only as needed to provide the service, evaluate product demand, and meet legal obligations, after which it is deleted or aggregated.
Users can delete financial information through the Android app, web app, or Google Drive. For other privacy or deletion questions, contact receptify.dev@gmail.com.
8. Security
Synchronized expense records and receipts are encrypted in the Android device or browser before upload to Google Drive. Sensitive local information may be protected using Android secure-storage mechanisms or browser Web Crypto with a non-exportable key. No system can guarantee absolute security, but reasonable safeguards are used to reduce risk.
9. Children's privacy
Receptify is not directed to children under 13, and we do not knowingly collect personal information from children under 13.
10. Changes and contact
This policy may be updated as the product or applicable requirements change. The date above will be revised when changes are made. Questions may be sent to receptify.dev@gmail.com.