FISCL

Privacy Policy

Effective 2026-11-14 · Version 2026-11-14

1. Who we are

FISCL is a financial planning application operated by AH Solutions Pty Ltd (ABN 74 644 535 302; ACN 644 535 302). Contact: support@fiscl.com.au. Business location: New South Wales, Australia.

2. Information we collect

When you create an account, we collect your name, email address and authentication information. Passwords are stored as hashes. We maintain session and security records, which can include IP addresses, browser or device information and rate-limit records. At registration we also record your adult confirmation, the terms and privacy policy versions you acknowledge, and the time of acceptance.

When you use FISCL, we collect the information you enter or import: workspace details and membership roles; personal or business financial profiles; income, budgets and allocations; bills, records of payments made externally and debts; account details and balances; transactions and their descriptions; categorisation rules; and financial plans and forecasts. CSV imports may contain information about other people, and imported transaction records can include source data and import metadata. We also retain records needed to track calculations and changes to financial records.

If you contact support, we receive the information you choose to include. Please do not send passwords or unnecessary identity documents. Only enter or import information you are entitled to use and share.

The current release supports manual information, CSV imports and demonstration data. It does not provide a live bank connection, execute bill payments or ask you to supply your internet-banking password. Wage-calculator inputs stay in the current page and do not change your saved plan.

If you subscribe, Stripe collects payment and billing details through its hosted checkout. FISCL sends Stripe your account email and an internal account identifier, and stores Stripe customer and subscription identifiers, plan, payment status and renewal information. FISCL does not receive or store your full card number or card security code. We use billing records to provide paid access and handle billing support.

3. How and why we use information

We use information to create and secure accounts, verify email ownership, recover access, operate workspaces, produce calculations and forecasts, support transaction imports and categorisation, respond to support requests and investigate errors or misuse. Essential account messages include verification and password-recovery emails.

FISCL's financial calculations depend on the information you supply. They help with planning; they do not make lending, insurance, employment or other eligibility decisions about you. You can review and correct the underlying information.

We do not use separate marketing, advertising analytics or AI integrations to process your financial records. Our infrastructure and email providers use their own service providers to operate their services, as described below. If our uses change, we will update this policy and provide any required notices or choices.

4. Sharing and service providers

Information in a shared workspace is available to authorised members according to their access. Consider who has access before adding personal or third-party information.

We use service providers to operate FISCL. The current application uses Netlify for hosting and database infrastructure and Google Workspace for account email and support communications. These providers process relevant data to supply their services. Information may also need to be disclosed where required or authorised by law.

Our providers may use authorised personnel and subprocessors for infrastructure, security, maintenance and support. Access may be needed to investigate a service issue. We limit the customer information we include in support requests to what is needed to resolve the issue.

We use Stripe to process subscription payments, prevent payment fraud and maintain billing records. Your payment information is also handled under Stripe’s privacy policy at https://stripe.com/au/privacy. Your financial workspace transactions are not sent to Stripe for subscription billing.

If you submit a lending enquiry, FISCL stores and reviews the contact details, lending purpose, requested amount and message you provide. Before a broker or lender can view that enquiry, we show you the named partner and ask for your separate approval. Approval shares only those enquiry details, not your financial workspaces, budgets or transactions. Reassignment requires new approval. You can withdraw the enquiry in My lending enquiries to stop further partner portal access; this cannot recall information already received by a partner. We retain the enquiry and consent history to explain what was shared. Contact support@fiscl.com.au for correction or deletion requests.

5. Overseas processing

Your information may be stored or processed outside Australia. Our production database is configured in the United States (us-east-2). Netlify uses United States infrastructure providers and a distributed network; this database region is not a promise that every copy or network request stays in one country.

Google Workspace uses international infrastructure and support operations. Its published locations for core services include the United States, Belgium, Canada, Chile, Denmark, Finland, Ireland, Japan, Mexico, the Netherlands, Singapore and Taiwan for data-centre operations. Maintenance and support may also involve Argentina, Australia, Brazil, Bulgaria, Colombia, El Salvador, France, Germany, Hong Kong, India, Israel, Italy, Malaysia, New Zealand, the Philippines, Poland, Romania, South Korea, Spain, Sri Lanka, Sweden, Switzerland and the United Kingdom. These are provider locations, not a claim that each receives every FISCL customer’s information.

The providers publish their current processing and subprocessor information at https://www.netlify.com/trust-center/ and https://workspace.google.com/terms/subprocessors/. Locations can change. Contact us for help understanding how these services relate to your information.

Stripe may process payment and billing information outside Australia, including in the United States and other locations where Stripe and its service providers operate. See https://stripe.com/au/privacy for Stripe’s international transfers and safeguards information.

6. Cookies and browser storage

FISCL uses authentication cookies to keep you signed in and browser storage to support workspace navigation. Blocking essential cookies can prevent sign-in. We do not use advertising cookies or separate website analytics tags in the current app.

7. Security and retention

We use account authentication, email verification, access controls and security limits to help protect information. No online service can guarantee absolute security.

We keep account and workspace information while it is needed to provide the service. This can include imported transaction source information and financial audit history needed to explain your records. Account closure and deletion are handled manually. We assess the information involved, shared-workspace rights and any legal or dispute-related reason for retaining particular records, and explain the outcome to you.

Support correspondence and security records are retained as needed to handle requests, investigate misuse and meet applicable obligations. We review retention when handling closure or deletion requests and remove or de-identify information that is no longer needed, subject to lawful retention requirements.

We review resolved support correspondence 12 months after the request is closed and minimal privacy-request completion records after 24 months. We delete information that is no longer needed, unless an ongoing dispute, legal requirement or another documented necessary purpose requires retention. These are manual reviews, not automatic deletion deadlines. Account-deletion requests are assessed individually, and we explain the scope, expected timing and any retention limits to the requester.

Deletion from active systems does not immediately remove copies in provider backups. Our database uses scheduled and deployment backups; deployment backups can remain until replaced by later deployments. We cannot currently give a fixed maximum period for removal from every provider backup. We will explain known limitations when handling your request. If we restore a backup, completed deletion requests must be reapplied before the restored data returns to ordinary use.

8. Access, correction, export and deletion

You can correct supported financial information within the app. Workspace owners can export the supported workspace records. The export is not a complete personal-information access report: it excludes authentication data and some source-import and audit records.

For other access, correction or deletion requests, contact support@fiscl.com.au. We may need to verify your identity and your authority over a shared workspace before acting. Deleting a personal account may require separate decisions about business records or information other members are entitled to retain. We will explain any applicable limits or lawful retention requirements.

Our business operator monitors support@fiscl.com.au and handles access, correction and deletion requests manually. We aim to respond within 30 days. This response target is not a promise that all deletion, including removal from backups, will be completed within that period. We will explain the steps, expected timing and any retention limits applicable to your request.

9. Privacy complaints

Contact support@fiscl.com.au with your concern and the outcome you seek. Our business operator reviews complaints received at this address and aims to respond within 30 days. We may contact you for information needed to investigate and will explain our response and any proposed steps to resolve the concern. If Australian privacy law applies and you remain dissatisfied, you may be able to raise the matter with the Office of the Australian Information Commissioner at https://www.oaic.gov.au/privacy/privacy-complaints.

10. Changes

We will publish the current policy with its effective date and email your registered address about material changes, explaining when they take effect. Where a change requires your consent, we will seek that consent before proceeding.