by SubTrack (LX AI)
SubTrack — See where your subscriptions go Use it as decision-support: demo mode works without a live key; live runs require configuration. No fabricated metrics, and no claims for SSO/CSV/Slack unless that surface is actually shipped.
Decision-support only — confirm before you publish or act.
I built SubTrack so you can see a quick picture of your recurring spend without any setup friction. When you open the product in demo mode you are presented with a blank form that asks for three fields per line: subscription name, amount, and billing interval. You can type as many lines as you need; each line is stored only in the browser’s local storage and disappears when you close the tab or clear the data.
Click the “Demo” toggle at the top of the page. No API key is requested. The interface switches to a read‑only notice that explains all calculations are performed locally and that no data leaves your device.
For each service you type the exact name as it appears on your statement, the numeric amount you are charged, and choose either “monthly” or “yearly” from the dropdown. If you pay quarterly you can enter the yearly amount and select yearly; the tool will still compute a monthly equivalent.
As soon as you leave the last input field the script adds up all monthly amounts and shows a running total. It also multiplies each yearly entry by twelve to contribute to the yearly total. The totals appear in a bold bar beneath the form.
Press the “Copy list” button to place a plain‑text version of your entries on the clipboard. You can paste it into a note‑taking app or a spreadsheet for further review. The copy operation does not transmit any data to a server.
If you want the product to call an external language model for additional checks you must provide a valid API key. The key is stored only in the browser’s encrypted storage area and is never logged. When the key is present the product switches to “live” mode and sends a minimal payload that contains only the subscription names and amounts.
Open the settings panel, paste the key into the field, and press “Save”. The key is encrypted with a nonce derived from your session and saved under .data/key.bin. You can remove it at any time by pressing “Delete”.
I followed the guidance from the OWASP LLM Top 10 (https://owasp.org/www-project-top-10-for-large-language-model-applications) and the NIST AI Risk Management Framework (https://www.nist.gov/itl/ai-risk-management-framework) to keep the key isolated from the UI thread and to prevent accidental leakage through console logs or network traces.
When you press “Analyze” the product builds a JSON object that lists each subscription with its name, amount, and interval. No personal identifiers, email addresses, or usage metadata are included. The request is sent over HTTPS to the endpoint you configured in the settings.
The model returns a short text that highlights any subscriptions that appear unusually high compared to typical market prices. SubTrack then adds those suggestions to the “Top cuts” list and shows them alongside the totals. You must still review the suggestions before acting on them.
SubTrack keeps the input model deliberately simple so that anyone can start tracking without learning a new schema. Each row represents one recurring charge and consists of three mandatory fields.
Enter the exact label as it appears on your bank or credit‑card statement. If the name includes a promotional code you can keep it; the tool treats the string as an opaque identifier.
Type the numeric value you are charged each billing cycle. Use the decimal separator that matches your locale (a period for US dollars, a comma for euros). Do not include currency symbols; the script assumes the amount is in the currency you have set in your profile.
Choose “monthly” if you are charged every 30 days, or “yearly” if you are charged once per 12 months. For quarterly or biannual plans you can enter the yearly total and select yearly; the internal math will still produce a correct monthly average.
You may add a short comment after the amount, separated by a pipe character (|). This note is stored locally but is not used in any calculation. It is handy for remembering why you signed up or for noting a trial end date.
Once the form is filled the script runs a series of deterministic steps to produce the numbers you see in the summary bar. No guessing, no external averages, and no fabricated metrics.
All amounts marked as monthly are added directly. For yearly entries the script divides the amount by twelve and adds the result to the monthly sum.
All amounts marked as yearly are added directly. For monthly entries the script multiplies the amount by twelve and adds the product to the yearly sum.
The script sorts the entries by their monthly equivalent (amount divided by one for monthly, amount divided by twelve for yearly) in descending order. It then picks the three highest‑value items and labels them as potential cuts. If you have fewer than three entries the list shows however many are available.
Below the top‑cuts list SubTrack shows the sum of the monthly equivalents of those three items. This figure represents the maximum amount you could save if you cancelled all three subscriptions immediately. It is presented as a decision‑aid, not a promise.
Seeing a subscription at the top of the list does not automatically mean you should cancel it. The list is a mechanical ranking based solely on the numbers you entered. You still need to consider usage, contract terms, and personal value.
The ranking uses the monthly equivalent of each charge. This normalizes different billing frequencies so that a $120 yearly plan and a $10 monthly plan are treated as equal cost. The script does not weigh features, usage frequency, or satisfaction scores.
Imagine you entered the following:
The monthly equivalents are: video $15, music $10, cloud $10, gym $45, magazine $8. The sorted list becomes gym ($45), video ($15), music ($10), cloud ($10), magazine ($8). The top three are gym, video, and music, with a combined monthly equivalent of $70.
I want to be explicit about the limits of SubTrack so you do not mistake it for something it is not.
The tool only shows where money is going. It does not promise that cutting any listed subscription will save you a specific amount, nor does it guarantee that you will save money at all.
SubTrack never contacts your bank, your credit‑card provider, or the merchant’s API. You must perform any cancellation yourself through the vendor’s usual channels.
If the current build does not include a sign‑in with Google, a Slack notification button, or a CSV export feature, those capabilities are not present. Do not assume they exist because they appear in marketing screenshots elsewhere.
The output is a simple arithmetic summary. It does not consider tax implications, interest rates, or opportunity cost. For major financial decisions consult a qualified adviser.
All inputs stay in your browser unless you explicitly provide a live API key. Even then only the subscription names and amounts are transmitted, and no personally identifiable information is harvested.
See where your subscriptions go
Operators and builders who need a fast first draft or checklist from SubTrack.
Yes in explicit Demo mode. Live AI requires a configured key.
No. Outputs are decision-support; you still review before publishing or acting.
Only if those features are implemented in this product build — do not assume them from marketing copy.
Runs may be stored locally under the product's .data/ boundary; treat demos as ephemeral.