Australian investor resource
Complaints handling
A fair, confidential process for raising and escalating concerns.
Purpose and commitment
We record complaints, assess them objectively and explain the result in plain language. Raising a concern does not affect your right to request support or access information.
For Purpose and commitment, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Purpose and commitment depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 34 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Step 1: Tell us what happened
Email [email protected] with the account email, relevant dates and a clear description. Do not send passwords, one-time codes or full card details.
For Step 1: Tell us what happened, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Step 1: Tell us what happened depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 35 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Step 2: Acknowledgement
We acknowledge a complete complaint and provide a reference. If essential information is missing, we explain what is required and why.
For Step 2: Acknowledgement, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Step 2: Acknowledgement depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 36 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Step 3: Investigation
A person with appropriate authority reviews account records, correspondence and applicable terms. Complex cases may require information from a payment or technology provider.
For Step 3: Investigation, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Step 3: Investigation depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 37 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Step 4: Outcome
We provide the outcome, the reasons and any corrective action. Where a final response cannot yet be given, we explain the status and next expected update.
For Step 4: Outcome, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Step 4: Outcome depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 38 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Information requirements
Include the requested resolution and copies of relevant non-sensitive records. Never include credentials or unrelated identity information.
For Information requirements, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Information requirements depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 39 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Timing and escalation
Australian complaint timeframes depend on the issue and service relationship. If internal review does not resolve an eligible matter, external dispute resolution through AFCA may be available.
For Timing and escalation, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Timing and escalation depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 40 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.
Our commitments and contact
We protect confidentiality, keep useful records, avoid retaliation, communicate honestly and correct confirmed errors. Send complaints to [email protected].
For Our commitments and contact, Complaints handling uses a documented sequence rather than an unexplained outcome. The relevant account record, setting, provider response or market input should be reviewed in context, because an isolated alert can be incomplete or misleading. Australian users should compare what is shown with the published fees, risk controls and support process before acting.
On the complaints page, the practical consequence of Our commitments and contact depends on the user’s verified account, enabled services and current market conditions. LithVestor explains the available controls and keeps material steps visible, while the user retains responsibility for checking details, protecting access and deciding whether the potential loss is acceptable. No analytical output removes volatility, liquidity or third-party risk.
Checkpoint 41 on complaints: review this topic against your own objectives, available capital and tolerance for loss. Keep a dated record of decisions and contact [email protected] if an account control or published condition is unclear.