Lazy Wallet Privacy Policy
Effective date: October 17, 2026
Last updated: October 17, 2026
Document version: 0.0.1-beta
Summary
Lazy Wallet stores the account information and financial records needed to provide the features you use. We use service providers for hosting, storage, sign-in, email, notifications, diagnostics, and support. We do not display ads, sell or rent personal information, share it for advertising, or use it for AI processing or model training.
1. Who is responsible for your information
Tilak Thapa, operating as jrTilak, Nepal, is responsible for the personal information handled by Lazy Wallet. Contact contact@jrtilak.dev about privacy or your data.
This policy covers the Lazy Wallet applications, website, API, and related services worldwide. Lazy Wallet is a manual finance record-keeping service. It does not connect to bank accounts, process payments, or retrieve bank transactions.
2. Information we collect and where it comes from
We collect information you provide, information returned by Google if you choose Google sign-in, and technical information generated when you use the Service:
- Account and security information: name, email, username, profile image, account identifiers, verification status, authentication credentials and tokens, sign-in times, IP addresses, device or browser details, and security events.
- Financial information you enter: wallets, balances, currencies, income, expenses, budgets, savings goals, recurring records, categories, contact details, amounts, dates, notes, tags, and relationships between records.
- Uploaded files: receipts, images, documents, filenames, file types, sizes, and upload metadata.
- Notifications: delivery addresses and push tokens, notification preferences, message contents, and delivery results. Security notifications can include sign-in times, IP addresses, and device or browser details.
- Diagnostics: errors, crash reports, app and operating-system versions, device information, request context, performance timings, and actions leading up to an error. These reports can contain personal information.
- Feedback and support: messages, feedback categories, contact details, and images or other information you choose to submit.
- Local data: session credentials, essential cookies, preferences, and cached application data stored on your device or in your browser.
We receive information about other people from records and files you submit. Only provide information you are entitled to share with us.
Account and authentication information is needed to provide an account. Financial records, attachments, and feedback depend on the features you choose to use.
3. How we use information
We use information to:
- create accounts, authenticate users, and protect sessions;
- save, synchronize, calculate, and display financial records;
- store and retrieve files you upload;
- send verification codes, security messages, and requested notifications;
- diagnose failures, measure performance, and maintain reliability;
- answer feedback and support requests;
- investigate specific security incidents or abuse; and
- meet legal obligations and respond to valid legal requests.
Where data-protection law requires a legal basis, we rely on providing the service you request, our legitimate interests in security and reliability where those interests do not override your rights, and applicable legal obligations. Where consent is required, we obtain it before the relevant processing. You can withdraw that consent without affecting earlier lawful processing.
We use Sentry for diagnostics, performance monitoring, and submitted feedback. We use no advertising trackers or additional analytics service. We do not send personal information to AI services for processing or model training.
4. Files, device permissions, and local storage
Financial attachments are stored for your records. We do not analyze their contents or routinely review them. Authorized access is limited to support you request, a specific security or abuse investigation, or a legal requirement. We may review images submitted with feedback to address it.
We request device permissions when needed for features such as selecting images or receiving notifications. You can manage permissions in your device settings. Refusing permission can prevent the related feature from working.
If you enable app lock, your device handles biometric or device-credential verification. Lazy Wallet receives the authentication result, not your fingerprint, face template, or device PIN.
Essential cookies and device storage keep you signed in, remember preferences, and cache data. Copies you download or export remain under your control.
5. Service providers and other disclosures
We give providers the information needed for their role:
- Hosting providers: process API requests and the account, record, and technical information needed to run the Service.
- Neon: stores account and application data in the database and provides database recovery.
- Cloudflare R2: stores uploaded financial attachments and file metadata.
- Google: provides optional Google sign-in and exchanges the account and profile information needed for authentication.
- Resend: delivers account emails, including recipient addresses, message contents, verification codes, and security notices.
- Expo Push Service and the device platform’s delivery service: deliver notification contents using device push tokens.
- Sentry: processes diagnostic and performance data and feedback you submit, including any name, email, and images included with that feedback.
We may also disclose relevant information where a binding legal obligation requires it or where necessary to address a specific security incident or unlawful activity.
6. Where information is processed
We operate from Nepal. Our providers may store or process information outside Nepal and outside your country, including when providing support or running their infrastructure.
7. Retention, recovery, and account deletion
Financial records and attachments
We retain financial records and attachments while you keep them in your account. When you delete an individual record or attachment, we retain it for three days from deletion to allow recovery. After that period, we permanently remove it from active application storage.
Archiving an item is different from deleting it: an archived item remains part of your account until you delete it or delete your account.
Account deletion
In the app, go to Account & security → Delete account and complete the email verification.
The 30-day waiting period starts when you confirm the deletion request. Signing in again during that period cancels the request. If it is not canceled, we delete the account and its associated records and files from active application storage when the period ends. We do not add another three-day item-recovery period after account deletion or reset an earlier item-deletion deadline.
We also delete identifiable associated information held by our providers or request its deletion, subject to the retention exceptions below. Uninstalling the app or revoking Google sign-in does not delete your Lazy Wallet account. Deleting your Lazy Wallet account does not delete your Google account.
Database recovery and provider copies
We use Neon’s database recovery and do not maintain separate database backups. The Neon Free plan provides up to six hours of restore history, subject to its limits. Provider backup copies follow the provider’s retention rules; the restore window does not specify when every internal copy is erased. See Neon’s plan documentation.
Backup copies are used for recovery, not to reactivate deleted accounts. If a recovery restores deleted information, the deletion must be reapplied.
Diagnostics, feedback, and delivery records
Sentry’s Developer plan retains errors, logs, performance traces, and event attachments for 30 days. Sentry deletes its backups 90 days after creation. See Sentry’s retention periods and backup policy.
For feedback, support correspondence, server and security logs, and email delivery records, retention depends on the time needed to resolve the request, investigate an incident or delivery failure, and meet any applicable legal requirement. We delete this information when those purposes no longer require it, subject to provider backup retention.
Specific legal or security holds
If a binding legal requirement or a specific unresolved security incident requires longer retention, we keep only the information relevant to that requirement or investigation and restrict its use to that purpose. We delete it when that reason ends. We explain the reason and applicable duration when responding to a deletion request, unless the law prohibits that disclosure.
Nothing in this policy limits a right to earlier deletion under applicable law.
8. Your choices and privacy rights
Depending on the law that applies to you, you can request access, correction, deletion, a portable copy, or restrictions on processing. You may also object to processing based on legitimate interests and withdraw consent where we rely on it.
Contact contact@jrtilak.dev to exercise a privacy right or report a problem. We may ask for information needed to verify your identity. Never send a password or verification code to support. We respond within the time required by applicable law and explain any lawful refusal or extension.
You can manage device permissions, update information or delete records in Lazy Wallet, and revoke Google sign-in access through Google’s settings.
You may complain to the data-protection authority responsible for your location. You do not have to contact us first.
9. Children and parental permission
Lazy Wallet is for people aged 13 and older. Users under 13 must not create an account or submit personal information.
For users aged 13 or older, parental or guardian permission is required where applicable law requires it. A minimum age of 13 does not replace a higher local age requirement for consent or authorization.
If you believe a child has provided information without meeting these requirements, contact contact@jrtilak.dev. We will investigate and take the action required by law, including deletion where appropriate.
10. Security
We use authentication, access controls, and protected connections to reduce unauthorized access, disclosure, alteration, and loss. Access by us and our providers is limited to the service, support, security, and legal purposes described above.
No system can guarantee complete security. Protect your account credentials, device, and any downloaded files or access links.
11. Changes to this policy
We give at least seven days’ advance notice of material changes through the app or email, with the updated policy available on our website.
If a legal requirement or urgent security need requires an earlier change, we explain the reason and give notice as soon as permitted.
We update the version and last-updated date when this policy changes. Where a change requires consent, we obtain it before the new processing starts; a policy update or continued use alone does not supply that consent.
12. Contact
Tilak Thapa, operating as jrTilak
Nepal
- Privacy contact: contact@jrtilak.dev
- Website: jrtilak.dev