Where each agreement is shown, and how clients accept it

Rules that apply on every screen

App-wide footer (every screen)

What must stay separate, and why

1. Registration person becomes a verified user

Invitation-only sign-up. One tick accepts the client agreement (with its schedules, fees and privacy policy); the disclosure documents are given, not agreed.

What the user sees

Placement

2. Entity onboarding SMSF, company, trust or fund

The entity becomes the client. The authorised person accepts once, in the entity's capacity, and receives the entity's Service & Disclosure Particulars once approved.

What the user sees

Placement

3. Stocks, ETFs and managed funds self-directed dealing · Idealx Securities Limited, AFSL 531729

One-time "Agree and activate" for the securities schedule, the general advice warning on every ticket, and PDS/TMD before any fund application.

What the user sees

Placement

4. Digital assets Idealx Digital Assets Pty Ltd — not an AFS licensee

One activation button with the risk statement above it. The "not AFCA / not an AFS licensee" statement must be visible on the screen, not hidden in the schedule.

What the user sees

Placement

5. Strategies (model portfolios) Client-Approved Strategy Service, document 14 · Idealx Securities

Not an MDA: the client approves every basket. "Invest and join" accepts the schedule on first use and is the authority for the basket shown; every later change needs "Approve changes". Never call a model "recommended".

What the user sees

Placement

6. Payments, recipients and direct debit cash & payments · Schedule A · payment provider and sponsoring ADI

Pay-outs are push payments under Schedule A, authorised by button. Funding by direct debit is the one place a tick remains: a BECS Direct Debit Request on its own screen naming the debit user.

What the user sees

Placement

7. Planned journeys not yet built

Documents already exist for these; build the acceptance controls when the service is activated.

Auto Pilot & Managed Strategies (MDA) — Trend Investor Services Pty Ltd, AFSL 255475

Cash placement and earnings (26)

Recording acceptances

Every tick or authority button posts one record. The portal keeps the document version and hash immutable, so the record can be reproduced years later.

POST https://legal.idealx.com/api/v1/acceptances
Authorization: Bearer <ACCEPTANCE_API_KEY>

{
  "external_ref": "user_8f2c…/entity_41a0…",
  "document_slug": "client-services",
  "version": "3.0",
  "content_hash": "sha256:…",          // from GET /api/v1/documents
  "action": "agree",                    // agree | given | authority | consent
  "capacity": "trustee",                // self | trustee | director | officer | firm
  "entity_id": "41a0…",
  "context": "entity-onboarding/review",
  "accepted_at": "2026-11-01T02:14:09Z",
  "ip": "203.0.113.7",
  "user_agent": "IdealxApp/2.3 iOS"
}

• Fetch GET /api/v1/documents at build or daily; use its version_url for links and content_hash in the record.
• Listen to /api/v1/changes (or RSS) for new effective versions; queue the "Updated terms" interstitial for affected users.
• For strategies, DDRs and standing orders also store the platform's own artefact id (basket hash, DDR id, authority id).
• Never store card or account numbers in the acceptance record — masked form only.

QA checklist before release

• Sign-up has exactly one tick; entity submission one tick; the Direct Debit Request one tick. Everything else is a labelled button with one sentence above it.
• No checkbox is checked on first render; the primary button is disabled until a required tick is made.
• Each link opens the version named in the wording and offers a download.
• The general advice warning is visible without scrolling on every order, strategy and digital-asset screen.
• The FSG is given before the first financial service is available, and its version is recorded.
• The Direct Debit Request is on its own screen, names the debit user, and a copy is emailed.
• No tick or button sentence names a licensee or provider; the app-wide footer and the "Provided by" line on the securities, digital-asset, MDA and confirmation screens do.
• Digital-asset screens carry the amber risk statement ("not an AFS licensee / not AFCA") and no FSG.
• Strategy screens say "Available", never "Recommended"; a manager change never trades without "Approve changes".
• Entity acceptances record capacity and, for multi-signatory entities, wait for every authoriser.
• Re-acceptance interstitial appears on the effective date of a new version and records the new version.
• Copy uses "being processed", never "approved by our team", for automated steps.