BotanicSoft

Peony is a mobile personal ledger service that helps users manage ledgers and transaction records they enter. This policy explains what personal data Peony collects, why it is used, and how it is protected for service operation and Google Play submission.

1. Data We Collect

Account identifiers: email address, display name, and profile image URL provided through Google OAuth
User-generated content: ledgers, accounts, transactions, tags, notes, and other financial records entered by the user
Device and network metadata: app version, OS version, network state, and runtime environment
Diagnostic logs: app startup events, error messages, crash stack traces, and performance diagnostics
Notification access data: when the user explicitly enables Android notification access in system settings, notification content required to support autofill features

2. How We Use Data

Authentication and account management
Ledger data storage, synchronization, and backup
Notification-based transaction autofill assistance
Service quality improvement, error analysis, and performance diagnostics
Legal compliance, abuse prevention, and dispute resolution

3. Retention

Account data and user-generated content are retained while the account remains active.
Upon account deletion or data deletion request, data is deleted within 30 days except for records that must be retained by law.
Diagnostic logs are retained for the period required for service stability analysis, then deleted or anonymized.

4. Third-Party Sharing

Peony does not sell or share personal data with third parties. Exceptions may apply when required by law or when the user provides explicit consent.

5. Subprocessors and External Services

Google LLC: OAuth authentication
BotanicSoft operational infrastructure: application servers, databases, logs, and telemetry storage
Cloud or hosting providers: provider name and processing location will be added after the production infrastructure is finalized.

6. International Transfers

Personal data may be transferred internationally depending on the locations of authentication and infrastructure providers. Destination countries, transfer purposes, retention periods, and safeguards will be added after the deployment infrastructure is finalized.

7. Your Rights

Users may request access, correction, deletion, or restriction of processing.

Request channel: [email protected]
Deletion request target: within 30 days after receipt

8. Data Protection Officer

Name: {DPO or responsible officer}
Contact: [email protected]

9. Security Measures

Encryption in transit using HTTPS and TLS 1.2 or later
Access control and least-privilege operation for stored data
Separate handling of operational access logs and diagnostic logs
Secrets and release keys are kept in a separate secret store and are not committed to source control

10. Changes to This Policy

We will announce changes in the app or on the public web page and update the effective date above.

11. Items to Finalize Before Publication

Effective date
Data protection officer or responsible officer name
Actual infrastructure provider and international transfer details
Public URL: https://www.botanicsoft.com/legal/privacy-policy