YOYU Privacy Policy

YOYU v1.9.1

1. Scope and developer

YOYU is provided by an individual developer and is intended for adults aged 18 or older. You must register and sign in before using bookkeeping, reports, ledgers or other financial features. Without an account session, only registration, sign-in and related introductory flows are available. Having an account does not mean your financial records are automatically synchronized to the cloud. This policy also covers relevant processing on this website.

2. Financial records and local storage

Transactions, amounts, dates, notes, categories, ledgers, assets, liabilities, financial snapshots, recurring entries and financial exports are stored or calculated on your device. YOYU currently does not offer its own cloud synchronization of financial records. Raw financial content is not uploaded to the account service or included in product-usage analytics. Local financial storage is isolated by internal user account. Legacy records with uncertain ownership are not silently assigned or merged into a new account, and signing in to another account does not grant access to the first account's records.

With analytics consent, actions such as saving a record may generate a feature-use event without financial content. If you share an exported spreadsheet, the receiving app or service handles that copy under its own terms. Copies you export or share are not automatically removed when you delete your YOYU account. Home-screen background images you choose are processed and stored locally rather than uploaded to the YOYU account service. Reminders use local notifications.

3. Exchange-rate requests

When conversion is needed and no suitable cached rate is available, the app may request public reference rates from Frankfurter (api.frankfurter.dev) over HTTPS. Requests may include the date and source and target currency codes, but not transaction amounts, ledger content or a YOYU account identifier. The provider may still receive your IP address and request parameters and process connection logs under its own practices. Returned rates are cached locally.

4. Registration, sign-in and account data

To operate accounts, the service processes an internal user identifier, verified sign-in identity, account creation time and related authentication data. Email verification and password recovery may process your email address, one-time codes, challenge status and expiration. Passwords are not stored in plaintext; the server uses salted scrypt password hashes. The app may keep credentials in protected local storage. Regional and third-party sign-in options work only when configured. If Google, WeChat or SMS verification is enabled, those providers process authorization or verification requests under their own terms. Your public-facing YOYU ID is distinct from the internal user ID.

5. Optional profile and analytics consent

Age range, country or region, and occupation or current status are optional and can be skipped or edited. YOYU does not require an exact date of birth, identity document or real-name verification. Product analytics has a separate setting that users can turn off. Allowlisted usage and categorical error events are sent only with valid consent, an authenticated session and an available service. Events may contain a random event ID, event name, app version, error category, receipt time and a pseudonymous account association, but no raw transaction amounts, notes, ledger names, category names, asset or liability values. Disabling consent stops new consent-gated events; previously collected events may remain until account deletion and are not necessarily erased by switching the setting off.

6. Diagnostics and security

With consent and where supported, the app may report categories such as crashes, unresponsive processes or initialization failures. This description does not include raw stack traces, full exception text, advertising IDs, device fingerprints or financial records. Account services may process normal network information and hashed rate-limiting keys to prevent abuse. Hashing does not guarantee anonymity. Hosting, mail and network providers may keep separate operational logs.

7. Account deletion and local financial data

You can delete your account in the app after authentication and a second confirmation, or visit the account-deletion page on this website for an off-app route. Before deletion, the app should prompt you to export any financial records you wish to keep. After the server deletes the account and associated credentials, identity links, optional profile, sessions and account-linked analytics, the old credentials can no longer sign in.

In the new account-required design, once the server confirms successful deletion, the current device deletes that account's local financial storage, media and session. This replaces the legacy statement that deleting an account leaves local financial records intact. If deletion fails, local data should be preserved for retry. Local records on other devices cannot be guaranteed to be physically erased immediately by an action on this device; access must be blocked after the other device revalidates the deleted account. Previously exported or shared copies are outside automatic deletion. Backups, infrastructure logs and legally required records may have different retention schedules; instant erasure from all backups is not promised.

8. Service providers and regional processing

YOYU uses Brevo Transactional Email for account verification and security messages, which may disclose the recipient email address and message content to Brevo, but not financial ledgers. Frankfurter provides exchange-rate reference data. Google, WeChat and SMS providers are available only where configured.

9. Your choices and rights

You may edit supported optional profile fields, disable product analytics, request account deletion and contact privacy@yoyufinance.com about access, correction, erasure and other rights available under applicable law. YOYU does not currently claim an automated server-data export or a fully automated legal-rights request workflow. Requests may require manual handling and appropriate identity verification, without requesting your password or unrelated financial records.

10. Age requirement

The initial YOYU release is intended for adults aged 18 or older. An exact birth date or identity document is not required. Age-range questions are optional.

11. Retention and security limitations

Actual retention of account records, analytics events, verification challenges and rate-limit data depends on the deployed service. Account-linked records are removed from the active database through the implemented deletion process; immediate erasure from backups, provider logs or legally required retention is not promised. HTTPS, password hashing and protected local credential storage are security measures, not a guarantee of absolute production security.

12. Contact and updates

Privacy and support: privacy@yoyufinance.com. Material changes to account features, processing, providers or supported regions require updates to this policy and relevant app-store disclosures.