Data Retention and Disposal Policy

This policy sets out how long Algorythyme Ltd keeps personal information, and how we delete it when it is no longer needed. It applies to every product the company runs, including SteerSpend.

It works alongside our privacy notice and our information security policy, and uses the same retention periods as both.

1. Responsibility

Algorythyme Ltd is responsible for this policy. We decide how long each kind of information is kept, and we approve suppliers before they get access to customer information. We check the company inbox, team@steerspend.com, on working days, and questions about retention and requests to delete information should be sent there.

We will review this policy by 10 February 2027, and before any product change that collects a new kind of information.

2. How long we keep each kind of information

We keep only what an account needs to work, and only for as long as set out below. We do not keep customer data for advertising, for lending decisions or to sell.

Account details and settings

This covers the person’s email address, display name, how they sign in, when they agreed to the terms, and their country, currency and date format. It also covers everything they set or correct in the app: pay details, bills and income, category corrections and rules, cushion, savings targets, the savings they keep track of and the moves counted towards them, loan planner entries, budget adjustments, monthly reviews, notification and display choices, and receipt details. All of this is kept while the account exists, and everything about money in it is encrypted on the person’s device, so we can’t read it. When the person deletes the account, it is removed from the live database straight away. Supabase’s backups are overwritten after a limited period, and the encrypted parts stay encrypted in them.

Encryption keys

The key that opens a person’s encrypted data is kept only in locked form: with their recovery code, with a secret from their passkey where the passkey can give one, and in their browser. The locked copies on our side are kept while the account exists and are deleted with it, and the browser’s copy is deleted when the person signs out. If the person starts again (having lost their recovery code), their encrypted data and every copy of the old key are deleted straight away, and a new key is made.

Sign-in: passwords and passkeys

Supabase handles passwords and we never see them, so we hold no passwords to delete. Every account uses a passkey or, where a device cannot use one, an authenticator app. Supabase holds the passkey’s public key, never the fingerprint or face itself, which stays on the person’s device. These details are deleted with the account.

Statement files and payments

Statement files are read on the person’s own device, in the browser. They are never sent to us or stored by us, so there is no file for us to delete. From them, the app keeps only the payments the number needs. For each purchase from about 12 weeks before the current pay period onwards, it keeps the date, the amount, the description as the bank wrote it, a cleaned-up shop name and a category. Payments the app treats as money moved between the person’s own accounts or into savings are kept too, on the same terms, marked as moved. Older purchases are used once, on the device, to find pay and bills, and are not kept. Purchases from more than about 12 weeks before the current pay period are removed each time the person opens the app, and when a new statement is read. Money that came in is kept from the start of the last pay period. Payments that came back, and the payments that paid bills, are kept for 120 days. A summary of how pay and bills were found from older payments is replaced at each upload. For the pay, each bill, each payer of money that came in and each possible bill, the summary holds the name, the number of payments, the total and the last six. From each statement, the app also keeps the account’s balances, with only the last four digits of the account’s number. The latest balance is kept until the person removes it in the app or deletes the account, as is the balance at the end of each day for the last 140 days, with older days removed at each upload. The rest are kept while the account exists and are deleted with it. All of it is stored encrypted.

Money borrowed

Loans the person records (who lent it, the amount, any interest, how and when they will pay it back), and their repayments, are kept, encrypted, while the account exists and are deleted with it. Figures typed into the loan calculator are worked out on the device and are not kept.

How payments were sorted

For each payment, we keep the category or type, whether the AI or the app’s own rules chose it, how sure the AI was and its short reason, and the person’s correction, or the fact that they left it unchanged until the next categorisation (in which case the first category is kept as correct). Entries are only ever added, never changed, because they are what the AI learns from. The most recent 3,000 are kept, encrypted, while the account exists, including those for payments that have since been removed, and older ones are deleted. The AI’s suggestion for each of the most recent 1,500 payees is kept in the encrypted account record, so that the same payee is not sent again. All of it is deleted with the account.

AI categorisation (Anthropic)

While the AI is switched on (which it is unless the person switches it off), anonymised payment descriptions, amounts and past categories are sent through our server to Anthropic, which acts as our processor. Our server keeps nothing it receives or sends, except the number of payees each person had sorted each day, which is kept for a week to limit use. The person’s own account keeps an encrypted record of exactly what was sent and what the AI answered for the last 5 times, up to 90 days, so that they can see it. Anthropic deletes what it receives within 30 days, unless it needs to keep it longer to enforce its usage policy or the law requires it.

Plan and payment records

Stripe handles all card payments, and we never see or store card numbers. We keep the plan status Stripe sends us: whether the plan is in its free month, active, has a failed payment or has ended, its dates, and Stripe’s customer and subscription reference numbers. This is kept while the account exists and is deleted with it. Records of payments and refunds that we keep for tax are kept for six years. A record of each payment for the plan (amount, currency, plan, monthly or yearly, country, date, and whether it was the first) is kept as figures, so that we can understand how the business is doing. Its link to the account and to the Stripe customer record is removed when the account is deleted. Visits to the site are counted only as totals by day, country and source, which identify no one. Stripe keeps its own payment records, as the law requires.

Accounts without a plan

If a plan ends, the account stays, with everything in it, until the person deletes it. We may delete an account that has had no plan and no sign-in for 2 years, but we email the person first.

Help requests and support emails

Help form requests are kept in the database and copied to the team mailbox. Both are deleted once the matter is resolved, and always within 90 days. The admin page has a button that deletes closed requests older than 90 days, and we use it at least once a month.

A copy shared with support

We hold this only if the person chooses to share it. It is a readable copy of their account, the same as the copy they can make themselves, with any note they add. It is deleted when the time they chose ends (at most 7 days) or as soon as they stop sharing. Deletion is carried out by their app, whenever an admin lists the shares, and by an hourly clean-up. The record of each time someone on our team opened it is kept for a year, so that the person can see it, and is deleted with the account.

Card fingerprints

To give one free month per card, we keep the fingerprint Stripe gives us for the card used for a free month (a code that cannot be turned back into the card number), with the date. It is kept for 2 years, even if the account is deleted, and is then deleted.

Invites and terms accepted or declined

We keep a record of who invited whom, whether they paid and any credit given, and of which version of the terms each person accepted or declined, and when. These records are kept while the account exists and are deleted with it. Every published version of the terms and policies is kept for the record.

Bank connections (US)

In the US, people can link a bank account through Stripe Financial Connections. For each linked account, we keep Stripe’s reference for it, the bank’s name, the account’s name, the last four digits of its number, its kind and whether it can still be read, and when it was last read. These are kept until the person unlinks the account, until Stripe tells us it was unlinked, or until the person deletes their account; the app unlinks every account at Stripe before an account is deleted, and the database refuses to delete an account while any are linked. The account’s payments and balance pass through our server to the person’s device and are not kept by our server; on the device they are kept, encrypted, like a statement’s, under “Statement files and payments” above. When a plan ends, Stripe stops reading the person’s banks each day. Stripe keeps its own records under its privacy policy.

On the person’s device

Statement files are read only on the person’s own device, so they are not information held by Algorythyme Ltd and fall outside this policy. The browser also keeps the sign-in session, the passkeys used on that device and any invite code in local storage until it is cleared, and a locked copy of the person’s data key until they sign out. The cookie policy explains this.

3. How we delete information

When we delete information, we remove it from the live database rather than just hiding it or moving it to an archive. Supabase’s backups are overwritten after a limited period, and the encrypted parts of an account stay encrypted in them.

Deleting an account (in the app, under You, then “Privacy and your data”, then “Delete my account”) removes the login and everything stored with it. If a plan is still running, the app asks the person to cancel it first, so that Stripe stops charging them. Before deleting their account, people can get a copy of their information using “Get a copy of your data” in the app (under You, then “Privacy and your data”), or by emailing team@steerspend.com. Any bank linked through Stripe is unlinked first.

Customer records are never kept on the computer we use to run the service. If a customer sends a file during a support request, it is deleted once the request is closed, and always within 90 days.

4. Changes and document control

If a new product, or a new feature in an existing product, needs to keep a kind of information not listed here, we will update this policy before it is released, and update the privacy notice at the same time. Each change is recorded below.

Entity nameAlgorythyme Ltd
Company number16230652
Registered officeUnit A, 82 James Carter Road, Mildenhall, IP28 7DE
ResponsibleAlgorythyme Ltd
Contactteam@steerspend.com
Version and effective dateVersion 9, 17 October 2026
Next review10 February 2027