SuperYears - Accessibility & Data‑Use Statement
Version: Draft v2026-1
Effective date: 01 March 2026
Applies to: The public SuperYears website and public calculators/tools (not the logged‑in subscription app; see Subscriber/App Terms for that service). This page works alongside our Website Terms, Privacy Policy, Cookie Policy, Acceptable Use Policy (AUP), and Responsible Disclosure/Security Policy.
Plain‑English explainer (read this first)
Everyone should be able to use SuperYears. This page sets out our accessibility commitments (how we design for people of all abilities) and our data-use practices for public tools like calculators. It explains the standards we aim to meet, known limitations, how to get support, and how we handle the data you enter.
WHAT’S INSIDE
• A-1 Standard & scope
• A-2 Core accessibility features (what you can expect)
• A-3 Compatibility & supported environments
• A-4 Feedback, support & alternative formats
• A-5 Exceptions & known limitations
• A-6 Testing, governance & release process
• D-1 What data our public tools handle
• D-2 Personalisation, analytics & opt-outs
• D-3 Calculator input handling (transient, storage & de-identification)
• D-4 Retention & deletion windows for tool data
• D-5 Security controls (VPDSS-aligned)
• D-6 Privacy & cookie linkage
• D-7 Changes to this Statement
• D-8 Contact channels
A-1. Standard & scope
• We aim to conform to WCAG 2.2 success criteria appropriate to each page or component, targeting Level AA by default.
• Where full conformance is not yet feasible, we provide equivalent access or a workaround while we remediate.
• This Statement covers content, navigation, forms, error handling, media, and interactive tools on the public site.
• Equal access commitment: We support equal access consistent with the Disability Discrimination Act 1992 (Cth) and will make reasonable adjustments on request.
A-2. Core accessibility features (what you can expect)
• Readable design: base text ≥16px; generous line height; predictable headings and landmarks; clear labels; link text that describes destination.
• Contrast: minimum 4.5:1 for body text; 3:1 for large text and UI components where allowed.
• Keyboard access: all interactive elements operable by keyboard; visible focus states; logical tab order and skip links.
• Forms & errors: clear instructions near inputs, inline validation, descriptive error messages, and ways to fix errors.
• Media: captions for videos where provided; transcripts for audio where provided; avoid autoplay with audio.
• Motion & flashing: reduced motion options; avoid content that flashes more than three times per second.
• Touch targets: at least ~44×44px where feasible; sufficient spacing to prevent accidental taps.
• Language: plain English; acronyms explained on first use (e.g., ABP, TTR/TRIS, TBC).
A-3. Compatibility & supported environments
• We test common modern browsers and assistive technologies.
• Performance considerations: pages are optimised for quick loading; heavy assets are deferred or compressed where possible.
A-4. Feedback, support & alternative formats
• If you encounter an accessibility barrier, contact us and we’ll work to fix it: accessibility@superyears.com.au.
• Response time target: INFORMATION NEEDED HERE: E.G., WE AIM TO REPLY WITHIN 5 BUSINESS DAYS***
• Alternative formats: on request, we will provide key documents in an accessible format (e.g., tagged PDF, large print) where reasonable.
• Reasonable adjustments: tell us what you need and we will work with you to provide an accessible alternative wherever feasible.
A-5. Exceptions & known limitations
• If you encounter an accessibility barrier, contact us and we’ll work with you to address it: accessibility@superyears.com.au.
• Response time target: We aim to acknowledge and respond within 5 business days. More complex issues may take longer to resolve; we will keep you informed.
A-6. Testing, governance & release process
• Pre-release checks: automated and manual tests against WCAG 2.2 AA; keyboard-only passes; screen-reader spot checks; colour-contrast checks.
• Governance: an internal owner reviews accessibility defects and approves go-live when blocking issues are resolved to an agreed risk level.
• Training: designers and engineers receive periodic accessibility refreshers.
• Usability testing: where feasible, we conduct sessions with assistive-technology users and incorporate findings into our backlog.
D-1. What data our public tools handle
• Calculator inputs are values you type to see estimates (e.g., balances, ages, retirement targets).
• Our goal is to process inputs transiently (in memory) and return results to your browser.
• If temporary storage is necessary (e.g., troubleshooting, quality checks), we minimise fields captured and de-identify where feasible.
D-2. Personalisation, analytics & opt-outs
• We may tailor tips or page ordering based on your on-site activity (where enabled).
• Opt-out: you can manage cookie preferences in your browser and unsubscribe from marketing emails using the links provided.
• No sale of data: we do not sell personal information.
• If we add a consent banner, our Cookie Policy will list cookie categories, examples, and retention windows.
D-3. Calculator input handling (transient, storage & de-identification)
• Default mode: compute locally or server-side without persisting personally identifying inputs.
• If storage occurs: we set short retention periods, restrict access, and hash or remove identifiers where possible.
• Outputs: estimates are illustrative; see our Website Disclaimer for limits and assumptions.
• No eligibility decisions: tool outputs are not used to determine eligibility for products or services.
D-4. Retention & deletion windows for tool data
• Transient computation: Where calculations are processed in memory only, no retention occurs beyond the session.
• Stored tool data (account-linked): Where calculator inputs or outputs are saved to your account, they are retained while your account remains active. If your account is deleted or terminated, stored tool data is deleted or de-identified within 30 days, subject to backup rotation and legal retention requirements.
• Logs and diagnostics: Security and application logs are typically retained for up to 90–365 days for monitoring, fraud detection and incident response purposes, after which they are deleted or anonymised.
• Analytics data: Aggregated analytics events are retained in line with tool defaults, typically 14–26 months, and are de-identified where reasonably practicable.
• Personalisation profiles: If you disable personalisation, stored profile signals are cleared or de-identified within 30 days, subject to backup rotation processes.
D-5. Security controls (VPDSS-aligned)
• We apply proportionate administrative, technical, and organisational controls, including:
• Access control/least-privilege; MFA for privileged roles.
• Encryption in transit; hardened hosting; regular patching.
• Monitoring and alerting; vulnerability management.
• Incident response and continuity planning.
• We align our approach with the Victorian Protective Data Security Standards (VPDSS) principles for governance, risk management, identity & access, incident handling, and third-party oversight.
• More detail on our personal information handling is in our Privacy Policy.
D-6. Privacy & cookie linkage
This Statement sits alongside our Privacy Policy (how we handle personal information) and any Cookie Policy (cookie categories and controls).
Where there is a conflict, the Privacy Policy prevails for personal information handling.
D-7. Changes to this Statement
We may update this page as our services evolve. The Effective date at the top will change. If changes are material, we’ll take reasonable steps to notify users (e.g., a site banner).
D-8. Contact channels
• Accessibility feedback: accessibility@superyears.com.au
• Privacy questions: privacy@superyears.com.au
• General legal: legal@superyears.com.au
Information provided is general in nature and does not constitute personal financial advice.