LEGAL
Privacy Policy
How DAYNARO handles information in its local-first Android app, optional backups and external services.
Effective date: 14 August 2026
App: DAYNARO
Contact: daynarolabs@gmail.com
Official website: https://daynarolabs.pages.dev/
1. Scope
This Privacy Policy explains how DAYNARO and DAYNARO Labs handle information when a user uses the DAYNARO application, the DAYNARO Labs website, product support and voluntary Support Development links.
DAYNARO’s first public release is being prepared for Android. If DAYNARO becomes available on additional platforms in the future, this Policy may be updated to describe platform-specific services and privacy practices.
2. Information a user may keep in DAYNARO
DAYNARO is a personal organization and financial record-keeping tool. Depending on the features a user chooses, app content may include:
- income, expenses, balances, accounts, cards and transaction details;
- debts, savings, budgets, delivery earnings, financial reports and related records;
- diary entries, notes, tasks, reminders, special days and Work Calendar information;
- vehicle information and other workspace-specific records;
- documents, images, audio or voice notes and other Vault or media content;
- settings, workspace details and backup configuration.
Users decide what information to enter, import, attach, record, export or back up. Users should avoid storing information they do not need and should obtain any permission required before recording information about another person.
3. Local-first storage and processing
DAYNARO is designed primarily to store and process ordinary user records on the user’s Android device. The current release design does not use a DAYNARO Labs-operated server database to store ordinary finance, diary, task, document or other app records.
This does not mean information can never leave the device. Data may be sent to a destination chosen or authorized by the user when they back up, export, share, contact support, use billing, open an external service or otherwise initiate an online flow.
4. Backup and restore
During onboarding, DAYNARO requires configuration of at least one supported automatic-backup destination. A user can choose a supported local folder or, where available and authorized, Google Drive. Android or a selected provider may delay, stop or reschedule background backup work.
DAYNARO backup packages use authenticated encryption. Users are responsible for protecting backup passwords, destination accounts, exported packages and restored devices. DAYNARO Labs does not hold a recovery key that can guarantee access to an encrypted backup if a password or file is lost.
A backup stored in Google Drive, a local folder, removable storage or another user-authorized destination is controlled by that destination and its provider. Provider-side copies, synchronization, retention, deletion and recovery are governed by the user’s account settings and the provider’s terms and privacy practices.
5. App security
DAYNARO uses security measures designed for local app data, including an encrypted database, Android Keystore-protected key material, app PIN or supported system authentication, authenticated encryption for protected content, and lock-state protections.
PIN and biometric checks help control access on the device but cannot remove every risk. Device compromise, malware, rooted or modified systems, shared credentials, insecure exports, screenshots, unlocked backups or vulnerabilities in external services can expose information.
6. Android permissions and system features
DAYNARO uses Android permissions or system interfaces only when needed for a feature the user chooses. Depending on the app version, device and selected workflow, these may include:
- Notifications and alarms for reminders and scheduled information;
- Camera for a user-initiated capture or document workflow;
- Files, photos and media through Android pickers for attachments, import, export, backup or restore;
- Microphone or audio for a user-initiated voice-note workflow;
- Biometric or device authentication for supported app-lock and security checks;
- Network access for user-authorized online features such as Google Play Billing, Google Drive, external links or support.
Android may allow users to deny or revoke some permissions. Doing so may prevent the related feature from working. DAYNARO should not request access merely to support advertising or behavioral analytics.
7. OCR, voice and media
Receipt OCR uses on-device Google ML Kit processing. Google Play services may download or update the recognition model. Selected receipt images are not uploaded to a DAYNARO Labs OCR server. Voice-note, image, document and other media handling can depend on the Android version, device capability and system component used.
OCR and automated extraction can be inaccurate. Users should review extracted text, amounts, dates and other important information before relying on or saving it. Sharing, exporting or backing up media can provide a copy to the destination selected by the user.
8. Reminders and notifications
DAYNARO may process dates, task details and related local records to schedule reminders or notifications. Android power management, permission settings, device state and system scheduling can delay or prevent delivery. Notifications may display information on the lock screen according to the user’s Android settings.
9. DAYNARO Access and Google Play Billing
DAYNARO Access may be purchased through Google Play Billing as Monthly Access, Annual Access or Lifetime Access. Google processes payment credentials and provides DAYNARO with purchase and entitlement information needed to determine Access status. DAYNARO Labs does not receive or store the user’s full payment-card number or Google Play payment credentials.
Google Play’s processing is governed by Google’s own terms and privacy practices. The initial 30-day full-access period is managed by DAYNARO and does not itself enroll the user in a paid Google Play subscription.
10. Voluntary Support Development
The Support page may link users in India to Razorpay and international users to PayPal. Opening or using those links provides information directly to the selected payment provider under that provider’s terms and privacy practices.
Support Development is voluntary and separate from DAYNARO Access. A support payment does not unlock features, extend Access, alter a subscription or grant a digital benefit. Returning from an external provider page is not treated as proof of successful payment.
11. Website and support communications
The current DAYNARO Labs website does not add advertising or analytics SDKs and does not use app records. Cloudflare may process connection and security information needed to deliver and protect the public website under Cloudflare’s own practices.
If a user emails DAYNARO Labs, the email service and DAYNARO Labs receive the address, message and attachments the user chooses to send. Support messages may be retained as reasonably needed to answer the request, maintain support history, prevent abuse or meet legal obligations. Users should not send passwords, backup keys, payment credentials or unnecessary sensitive records.
12. Third-party services
Third-party services can include Google Play, optional Google Drive, Android system services and pickers, a user’s selected sharing or storage destination, Razorpay, PayPal, email providers and Cloudflare website hosting. These providers may process account, device, connection, payment or content information under their own terms and privacy policies.
Institution names and logos displayed in DAYNARO are identification aids. They do not mean that DAYNARO is affiliated with, endorsed by, connected to or able to access an institution.
13. Advertising, analytics and sale of personal data
The current DAYNARO release scope does not include advertising, developer analytics or developer crash-reporting SDKs. DAYNARO Labs does not sell a user’s personal app records. If this changes in a future release, this Policy and any required in-app disclosures will be updated before the changed processing is introduced.
14. Retention and deletion
Local records remain on the device until the user deletes them, clears app data, restores over them where supported, or uninstalls the app. The effect of uninstalling can depend on Android backup and device settings.
Backup, export, shared and media copies stored outside DAYNARO must be deleted separately from every local folder, Google Drive account, removable device, recipient or other destination. Deleting app data does not automatically delete those external copies. Provider retention, trash and recovery periods may continue to apply.
Google Play purchase history, payment-provider records, support emails and website-hosting records are controlled by the relevant provider or retained as required for the stated service, dispute handling, security or legal obligations.
15. Security and data-loss limitations
DAYNARO Labs takes reasonable steps to design DAYNARO for protected local storage, but no device, software, encryption, backup, network or third-party service can be guaranteed completely secure or always available. Users should keep the device updated, protect credentials, maintain tested backups and independently preserve important records.
16. Policy changes
This Policy may be updated as DAYNARO, Android requirements, third-party services or applicable obligations change. The effective date at the top of this page identifies the current published version. Material changes will be communicated through an appropriate public or in-app notice where required.
17. Contact
Privacy or support questions may be sent to daynarolabs@gmail.com.
Related pages: Terms of Use, Disclaimer and Support.