FYMIND / LEGAL

Privacy Policy

This policy explains how Veliquon Solutions Pty Ltd handles personal information when you use FyMind, contact support, or request account deletion.

1. Scope

This policy explains how VELIQUON SOLUTIONS PTY LTD handles personal information in connection with FyMind, its mobile application, backend services, support channels and associated websites.

2. Information we collect and hold

Depending on the features used, FyMind may collect or hold account and authentication information; the country selected during registration; an approximate country inferred from network headers where available; country and currency selections used for financial calculations; user-entered financial planning information such as income, expenses, savings, assets, liabilities, property details, goals, assumptions and scenarios; calculated outputs and saved simulations; subscription identifiers and verified entitlement records; support communications; and app activity, diagnostics, crash and analytics information when relevant services are enabled.

For account security, FyMind may also hold a randomly generated app-installation identifier, device category, platform, operating-system and browser family/version where available, app version/build, language/locale, timezone, IP address, approximate IP country, login and last-activity times, token expiry, revocation history and user-agent information. FyMind does not require IMEI, hardware serial numbers or advertising identifiers for session management.

Do not enter passwords, bank login credentials, complete card numbers, government identifiers or unrelated sensitive information into free-text fields.

3. Collection and storage

Information is collected when a user creates an account, enters information, uses features, contacts support, makes a purchase or changes settings. Technical information may be collected automatically by the app, backend and configured providers. Information may be held in protected local device storage, FyMind production systems, encrypted user backup snapshots, operational disaster-recovery backups, logs and service-provider systems.

Versioned cloud backup and restore is a paid feature. Eligible users can view and select retained restore points. FyMind encrypts the snapshot payload before database storage, applies integrity checking, keeps no more than the configured snapshot limit and removes snapshots under the configured retention policy. A pre-restore safety snapshot is created before restoration. Account deletion removes active user backup records; infrastructure backups may remain temporarily until normal secure rotation.

4. Purposes

Information is used to authenticate and secure accounts; operate and synchronise FyMind; calculate planning estimates; provide verified monthly or yearly subscription access; send verification, reset, MFA and support messages; prevent misuse; diagnose faults; provide export and deletion; and meet legal, security and app-store obligations. FyMind does not sell user-entered financial planning information.

5. Automated outputs

FyMind uses deterministic rules and software to calculate estimates, scores, scenarios, alerts and planning outputs from user information and assumptions. Planning Guide specialist reviews do not use generative AI, interpret chatbot prompts or send financial records to an external large-language-model provider. These are educational planning estimates and do not make lending, credit, insurance, employment or other legally determinative decisions for third parties. If the processing model changes, the product disclosures, consent flow and privacy information must be updated before release.

6. Providers and overseas processing

Configured providers may support hosting, databases, email, app-store billing, purchase validation, advertising, consent management, analytics, crash reporting, notifications, security monitoring and support. Some providers may process information outside Australia. Provider locations can change; current information may be requested from support.

7. Subscription model

FyMind is funded through monthly and yearly subscriptions rather than the sale of user-entered financial planning information.

8. Payments

Android subscriptions are processed by Google Play and iOS subscriptions by Apple. FyMind receives purchase tokens, product identifiers, states and expiry information required to verify access, not complete card details.

9. Security

Controls include authenticated APIs, short-lived access tokens, rotating refresh tokens, one active login per app installation, session revocation, role-based access, admin separation, MFA support, rate limiting, audit logging, request correlation, account-scoped local storage, encrypted backup snapshots, backup integrity checks, restricted production CORS, server-side purchase validation and safer logging. Multiple tabs or concurrently open private-browsing windows may share one browser session; closing the entire private-browsing context normally clears its local session storage. No system can guarantee absolute security.

10. Access, correction and export

Users may update available information and use the in-app Export Data function. Requests for access or correction of other eligible information may be sent to support. Identity verification may be required.

11. Deletion

Deletion is available in the app and at the FyMind account deletion page. Active account data is deleted subject to limited retention required for security, fraud prevention, disputes, backups, accounting or law.

12. Retention

Information is retained only as reasonably needed for the purposes in this policy and applicable legal, accounting, security and dispute requirements, then deleted or de-identified where reasonably practicable and permitted.

13. Complaints

Send privacy questions or complaints to support@veliquonsolutions.com. The company will assess and respond within a reasonable period. Where applicable, individuals may also contact the Office of the Australian Information Commissioner.

14. Changes

This policy may be updated as features, providers, legal obligations or information practices change. The current version is identified by its effective date.