AelyxFinancial planning
← Back to app

Privacy Policy

Last updated 18 September 2026

The short version. Your plan is saved only on your own device. We never keep a copy. There's no account to use the planner, and we never sell your data. To generate your projection, the figures you enter are sent to our server to be calculated, but they are never stored there: each calculation is worked out, returned, and discarded. The optional AI chat works the same way: what you type is sent to answer your question and isn't kept. We do use limited, anonymous, first-party product analytics now (never a third-party tracker or advertising cookie) to understand how the app is used — section 5 explains exactly what that is and isn't.

1. Who we are

Aelyx is currently operated as a sole trader. It is not yet incorporated as a company, so a company number will be added here once it is. The operator is the data controller for the limited personal data described below. Contact: hello@aelyx.app.

2. Your plan is saved only on your device

Everything you enter about your finances (incomes, savings, ages, goals, and every scenario) is saved locally in your own web browser (using IndexedDB, with a localStorage fallback). We keep no copy of your plan on our servers. If you clear your browser's data for this site, or use a different device or browser, that plan won't be there. You can export a backup file yourself from within the app. (Working out the projection itself does send your figures to our server to be calculated, as section 3 explains, but they are never stored there.)

3. What is sent to our servers to work out your plan, and never stored

Your projection. To turn the figures you enter into a retirement projection, Aelyx sends them to our server to be calculated, and updates them as you change your plan. We process your inputs to generate your plan but never store them: each request stands on its own, is worked out and returned, and nothing is kept afterward. We hold no database of your plans or your financial details.

The optional AI chat. Aelyx also includes an optional "ask the model" chat. If, and only if, you use it, your typed messages and the key editable figures of the plan you're viewing (such as ages, salaries, spending, housing and children details) are sent to our server and passed to a third-party AI service (currently Cloudflare Workers AI) to generate a reply. This too is processed to answer your question in the moment and is not stored on our servers.

4. Abuse-prevention for the chat

The AI chat needs no sign-in. Nothing about who you are is collected to use it. To stop the service being abused, we keep a daily counter of how many chat messages have come from your network connection, identified by IP address rather than any account or email. That counter automatically deletes at the end of each day and is never linked to the content of your plan or your messages. We do not build a profile from it.

5. Cookies, analytics and tracking

We do not use advertising or any third-party tracking, and we don't set tracking cookies. Fonts are served from our own site, not a third party. We do run our own first-party product analytics — never sold, never shared, and never combined with your plan data — described in full below.

How you use the app (anonymous, per visit). To understand which parts of Aelyx are actually useful, we record a small number of anonymous, one-off events as you use the site: which page of the guided setup you reached, whether a projection was produced, whether you tried the AI chat, which Strategy/Projection features you opened, which goal you said you're focused on, and — for our public calculator pages — that the page was viewed and whether you continued into the full app. Each of these is tied only to a random id generated in your browser for that one visit, stored in sessionStorage so it's gone the moment you close the tab. Nothing about who you are is collected, and this id is never combined with your name, email, IP address, or plan contents.

Return visits (a longer-lived, still anonymous id). Separately, we keep a random id in your browser's localStorage (so it survives between visits, unlike the id above) purely to tell whether people come back to Aelyx over time. Each day you open the app, at most one record is written: today's date against your id. We deliberately do not log every time you open the app, only the first time on a given day, so this is a short list of DATES, never a log of your activity.

Which savings wrappers your plan uses (anonymous and disconnected). This is the one place our product analytics touches anything derived from your actual finances, so we've built it as narrowly as we could: once a session, if your plan holds a balance in an ISA, Junior ISA, Lifetime ISA, cash savings, a General Investment Account, or a pension, we record that fact as a bare yes/no per wrapper type — for example, "a plan somewhere has an ISA". We never record the amount, never record which wrapper types appear together on the same plan, and never attach a session id, a return-visit id, or anything else that could connect it back to you, to a single plan, or to any other event on this page. Each record stands completely alone.

How well the AI chat could answer (anonymous, tied to your visit id like the events above). Each time you ask the chat something, we record which of its built-in tools handled it (for example, "a what-if change" or "a procedural how-to guide") and whether it could actually answer — a real answer, an honest decline because a figure wasn't available, a change we couldn't tie to anything you'd said, or the fallback wording it shows if its own phrasing check fails. For four of those tools we also record a single word or short field name from a fixed list built into the app (for example, which topic a how-to question was about, or which one field a what-if changed) — never the value you changed it to, and never your question itself. This never leaves the app with your actual words in it.

Sharing a declined question with us (only if you choose to). If chat has to decline a question, you'll see an optional link to send us that question, to help us see what people ask that the app can't yet cover. This is never automatic — nothing is sent unless you click it. If you do, we strip every digit from the text first (so a figure you typed elsewhere, like an age or an amount, can't ride along) and store what's left with no session id, no return-visit id, and nothing else that could connect it back to you or to any other record on this page.

6. No account, no selling of data

You don't need an account to use the planner. We don't sell, rent, or share your data with anyone for marketing, and there's no advertising in the app.

7. Your rights (UK GDPR)

Because your plan data lives on your device, you already control it directly: you can view, change, export, or delete it at any time. Under UK data-protection law you also have rights of access, correction, erasure, restriction, and objection over the limited data we process (the daily chat counter, and the anonymous product-analytics events described in section 5). None of it is linked to an identity we hold, so we generally cannot look up "your" analytics records to action a request against them individually — deleting the random id from your own device, as section 8 explains, is the practical equivalent of erasure for this kind of anonymous data. To exercise any of these rights, or to complain, contact us at hello@aelyx.app. You can also complain to the UK Information Commissioner's Office (ICO) at ico.org.uk.

8. How to delete your data

9. Children

Aelyx is intended for adults planning their own finances and is not directed at children under 18.

10. Legal basis

Where we process the limited data above, our lawful bases under UK GDPR are our legitimate interests in providing and protecting the service (running the chat and preventing abuse), understanding and improving the product (the anonymous analytics in section 5), and, where relevant, performance of our terms with you.

11. Changes to this policy

We may update this policy as the service evolves; the "last updated" date above will change when we do.