We are loading the page and keeping your path focused on Find, Fix, Fortify, Fuel, and Freedom.
5F Money OS
Preparing the next section with the same calm, premium flow.
Version 2026-07-12 · Last updated July 12, 2026
This policy explains what personal data 5F Money OS processes, why it is used, which service providers may receive it, how long it may be retained, and how account holders can access or delete their data.
Account and contact data, such as name, email address, phone number, account role, authentication status, and consent records.
Workspace and financial-organization data entered by the user, including income, expenses, debts, assets, protection, investments, goals, profile details, reports, alerts, tasks, and client-visible advisor notes.
Subscription and billing references, such as plan, billing interval, quote and invoice status, amount, currency, provider customer or charge references, and payment outcome. 5F Money OS does not store full card numbers or card security codes.
Technical and operational records needed for security, reliability, analytics, duplicate-payment prevention, and customer support.
To create and secure accounts, provide the 5F workspace, calculate and display user-requested financial organization outputs, manage subscriptions, provide support, and improve reliability.
Consent records are stored with the document type, version, language, source, and acceptance time. A prior acceptance is not treated as acceptance of a materially updated version.
We may use infrastructure, email, analytics, monitoring, authentication, and payment providers to operate the service. Payment processing is handled by Omise or another configured payment provider.
Providers receive only the data reasonably needed for their function and remain subject to their own terms and privacy practices.
Account and workspace data is generally retained while the account is active. Account deletion removes account-linked data from the application database, including client tasks and advisory notes that do not use database cascade relationships.
Limited billing, fraud-prevention, dispute, tax, legal, security, or operational records may be retained when required or reasonably necessary. Where possible, retained records are minimized or disconnected from the deleted account.
Account holders can review current consent versions, download a machine-readable JSON export, and request permanent account deletion from the Data and Privacy page.
You may also contact us to request access, correction, restriction, objection, or other rights available under applicable law. Some requests may require identity verification and may be limited by legal or security obligations.
We use reasonable technical and organizational safeguards. Password hashes, authentication secrets, session tokens, OAuth tokens, and raw payment-provider webhook payloads are not included in user data exports.
Changing a password, disabling an account, or deleting an account revokes existing sessions through account session-version validation. Deleted users also fail future session validation because the account record no longer exists.
For privacy or data-rights inquiries, contact [email protected].
