Last updated 29 October 2026
This notice describes how spendklaro handles personal information in the current product. It reflects present behaviour in the software, not a certification, audit or legal opinion. It has not been reviewed by counsel. A complete privacy policy addressing applicable law, including the GDPR and the CCPA where they apply, will be published before a public launch.
spendklaro is a personal finance application. You upload account statements; we parse them, store analysed transactions against your account and show insights, limits, goals and activity so you can understand your spending. We act as the controller of personal information processed in a spendklaro instance that we operate.
We collect the following categories of information:
We do not collect payment card numbers as a payment processor, and we do not connect directly to your bank. You choose which files to upload and whether the phone may send a payment text. We do not collect your mobile number in order to receive bank or wallet texts.
We process personal information only to:
We do not sell personal information. We do not use your financial information for advertising. We do not share it with other spendklaro users. We do not send statement contents or payment texts from the phone to analytics, advertising or AI services. Parsing and categorisation run on the application server that hosts your spendklaro instance. Original statement files, when kept, are stored with a cloud object-storage provider as described below.
If you set a spending limit, we store the label, monthly amount and optional category you choose so we can compare it with your analysed expenses for the month, quarter or year you are viewing, and so we can show progress on Overview and Limits, and related cards on Insights. If a limit is over, or on pace to go over that stretch, we also show a notice on Overview and Limits.
Limits are stored with your account. We do not use them for advertising or share them with other users. You can change or remove a limit at any time on Limits. Removing a limit stops that comparison going forward and does not delete transactions. Account deletion removes limits with the rest of your data.
If you set a goal, we store the kind (save a monthly amount, or spend less in a category than the previous stretch), the amount or percent you choose and the optional category, so we can compare it with your analysed income and expenses for the period you are viewing, and so we can show progress on Overview and Limits, and related cards on Insights.
Goals are stored with your account. We do not use them for advertising or share them with other users. You can change or remove a goal at any time on Limits. Removing a goal stops that comparison going forward and does not delete transactions. Account deletion removes goals with the rest of your data.
When you open Overview, we calculate a score for the month, quarter or year you are viewing. The score uses analysed pay, spending, bank fees and the gap between payday and must-pay bills. If you have set spending limits or goals, those comparisons are included. Parts we cannot measure from the file are left out of the average.
We calculate the score for display. We do not store it as a separate record. We do not use it for advertising or share it with other users. Days of cover in the score are estimated from the uploaded file, with the running balance starting at zero for that period. They are not your bank's official balance.
There is no setting to turn the score off. You can change or remove limits and goals at any time on Limits, which changes those parts of the score. Deleting a statement or your account removes the transactions the score uses. While those statements remain, opening Overview calculates the score again.
When you open Overview or Insights, we compare the charges in the month, quarter or year you are viewing with the other transactions in your uploaded statements. We look for a charge that is much larger than your usual amount at that place, a merchant name that has not appeared in an earlier month and a week where spending is faster than usual.
We calculate these notes for display. We do not store them as a separate record. We do not use them for advertising or share them with other users. They are a comparison inside your own file, not a fraud alert from your bank.
There is no setting to turn these notes off. Deleting a statement or your account removes the transactions the comparison uses. While those statements remain, opening Overview or Insights calculates the notes again.
Account and financial records are stored in a database associated with your user account. Access in the product is scoped to the signed-in account. Original statement files are stored in a private object-storage bucket under object keys scoped to your account, unless you turn that off in Settings. Objects are not published at a public URL; spendklaro reads and deletes them only from the application server. Passwords are stored as one-way hashes, not in plain text. Passkey public keys are stored with your account and cannot be used to reconstruct a biometric.
When you create an account, we keep the original statement file after it has been parsed so we can re-process it later. The same setting keeps a payment text the phone sends. Files and those texts are stored in private cloud object storage (an S3-compatible bucket). This setting is on for every account, including accounts created before this became the default, unless you turn it off. We also tell you this when you register, on Overview before your first upload and on Upload.
You can change this at any time in Settings by checking or unchecking "Keep original statement files after parsing". That change is saved immediately. Unchecking deletes stored original files and payment texts, and we do not keep new ones. We keep the file checksum described above so a later upload of the same file updates the existing statement. Turning this off does not undo parsing that already occurred; analysed transactions remain until you delete the statement, the retention period removes it or you delete your account. You may turn the setting back on at any time; that applies to files and texts you add after you turn it on.
While original files are kept, we may re-read them when we change how statements are parsed, so analysed records stay consistent. We do not send statement files to third-party analytics, advertising, AI or OCR services. The object-storage provider processes the file bytes only to store, retrieve and delete them on our instructions.
If you choose "Set up on this iPhone" for "Track your mobile money spending" in Settings, we turn capture on and prepare a key for that phone. We open a one-time setup page so you can finish the Shortcut steps. We do not install Apple's Message automation for you. The phone can then send a payment text to spendklaro. We collect that text, and the amount, currency, counterparty, receipt, fee and balance when the wording matches a template we have. We save the other person's name and phone number from a payment text, kept apart from each other. The app and your exports show only part of the number. A payment text kept as an original file still holds the full text. We use the sender id, when the phone sends one, only to decide whether to accept the text. We do not keep the sender id, except as part of a text shape described below. We process the text to add the payment to your ledger. A text we do not recognise is not guessed into a transaction. A text with no currency amount, and a one-time code, is dropped and not kept. If the phone does not send a sender id, a text that states a currency amount is accepted. A text that does not match a payment format we know is dropped and not kept. Before we drop it, we may keep its shape, as described under Payment text shapes. The phone also sends the time it received the text. We use it only to date the payment when the text has no date.
Parsing runs on our servers. We do not collect your mobile number in order to receive bank or wallet texts. We do not sell the text. We do not send the text, or the payments read from it, to analytics. The phone uses a key that we store only as a hash. Setup uses a one-time link: we store a hash of that link's code, and we hold the capture key encrypted only until the link is used or expires. The long-lived key is not placed in an ordinary page URL. The raw text is kept only while "Keep original statement files after parsing" is on. Turning that setting off deletes stored texts and we do not keep new ones. We still keep a checksum, and any payments already added to the ledger.
You can turn capture off at any time in Settings. That stops new texts and ends unused setup links. It does not undo payments already added. Setting up again creates a new key, and the old key stops working. The first time the phone checks in (a Play test with no payment text, or a payment text), we store that you set up the phone, when and whether it was Android or iPhone. Turning capture off does not delete that install record. Deleting your account removes the key, setup links and that record. You can delete that batch on Upload, turn off retention or delete your account. Withdrawal does not affect processing that already occurred while capture was on. You can change this setting at any time.
When a statement is parsed, we may store a short structural note: the column headings (such as date, description, debit and credit), the currency code printed on the file or the currency of the country you selected, whether numeric dates are day-first or month-first and whether amounts include a decimal fraction. We store this so a later statement with the same columns and currency can be read the same way, including a statement uploaded by someone else.
That note does not include transaction descriptions, names, amounts, account numbers or the file itself. It is not linked to your account. We do not sell it. We do not send it to analytics, advertising or AI services.
Deleting a statement or your account does not delete the note, because it is not a record of your transactions and cannot be used to identify you. There is no separate setting to turn this off. If you do not upload a statement, we do not add a note from that file.
When a payment text passes our filter but no payment format we know can read it, we may keep its shape: the company sender name, when the phone sends one, and the wording with every amount, date, time, phone number, name, reference, link and code replaced by a blank, such as "You have sent {amount} to {name}". We keep shapes so we can add support for new payment formats. A person checks each new format before spendklaro reads it. We never keep the text itself.
A shape is not linked to your account. To count how many people received the same shape, we keep a one-way code made from your account and the shape with a server secret. It cannot be turned back into your account without that secret, and we delete it when we act on the shape or the shape is deleted. Only the founder sees shapes, and only once the same shape has come from at least three people. We do not sell shapes or send them to analytics, advertising or AI services.
We delete a shape we have not acted on within a week after 90 days pass without a new text of that shape. A shape we marked as not a payment is kept for up to a year after its last text, so the same promotion is not checked again. One-time codes never produce a shape. Deleting your account does not delete a shape, because it does not contain your payments and cannot identify you.
You may set how long we keep analysed statements in Settings (between 30 and 3,650 days; the default is 365). The period is measured from the date we stored the statement (the upload), not from the dates printed on the transactions inside it.
When that period is saved, and when you use the product while signed in, we delete statements older than the period you chose. Deleting a statement removes its analysed transactions, parse history and any stored original file for that statement. This cannot be undone. Shortening the period can remove existing statements as soon as the new period is saved. Lengthening the period does not restore statements that were already deleted.
We apply this period when you use spendklaro, including when you change it in Settings. The new period is saved when you finish editing the number. We do not currently run a separate deletion job while you are signed out. You can change this setting at any time. You can also delete an individual statement or delete your account.
We use cookies that are necessary to keep you signed in and to protect your session. These are required for the service to function. Signing out ends your session. We do not use advertising cookies. We also keep a few settings in your browser, like which setup step you are on and notes you have closed.
We do not collect page views, navigation events, load times or other performance measurements. We do not use website analytics or session replay. The last time you opened the app is stored as described under product notes and visits. That record is not a trail of pages.
If you write an optional sentence on a statement we could not read, we store those words so we can decide what to build next. From the sidebar you can write one note about what is working, what is confusing, or what is missing. We store that note as one reply with the account you are signed in with. Replies sent earlier may still be two answers, what worked and what did not work. We store the name and email on that account with the reply so we can write to you about the product. When you send the reply, we email it to the founder so they can read it. That email contains the note and the name and email stored with the reply. A reply to that notice goes to the email on your account. We send the notice through Resend so it can deliver the message. If you email us about the product, we store that message with the other product notes. Once a week we send a brief to xAI, which provides the Grok model. The brief contains counts for that week (signups, uploads, parse results, unrecognised payment texts, limits, goals and how many people with a statement have not opened the app in fourteen days), plus the sentences written that week, sidebar replies, review notes we wrote, lines we recorded after a release and the previous memo. It does not contain statement files, payment texts from the phone, transactions, amounts, merchants, names or email addresses.
xAI uses that brief only to draft a memo for us. We store the brief and the memo. We email the memo to ourselves. We do not sell it.
Each sentence is optional. You can leave a box blank, and on the sidebar card you can send one line and leave the other empty. You can choose not to send a sidebar reply. After you send one, there is no control to recall the email to the founder. Do not include a statement, a payment text or amounts; if you do, those words are in the brief. There is no way to send a sidebar reply without it being tied to your account when you send it. Deleting your account does not delete a sidebar reply. The words, and the name and email stored with that reply, remain so we can still write to you about the product. There is no control to delete a sidebar reply. Deleting your account deletes other sentences tied to that account, and later briefs will not include those sentences. A sidebar reply can still appear in a later brief. A memo already stored can still contain a sentence from before deletion. A support email from an address that is not an account is not removed when someone deletes an account. There is no separate control to delete one sentence or to turn the weekly counts off.
We do not sell personal information, and we do not share it for cross-context behavioural advertising.
If you choose to sign in with Google, Google processes your sign-in under Google's own privacy policy. We use the account details Google returns only to authenticate you. You can stop using Google sign-in by signing out. To remove the information we hold, delete your account in Settings. Managing connected apps in your Google account is described by Google.
When you register with email, when you ask us to send another verification link or when you ask us to reset your password, we send your email address and that link to Resend so it can deliver the message. When you send a sidebar reply, we send that reply, with the name and email stored with it, to Resend so it can deliver a notice to the founder. We use Resend only to deliver those messages. We do not use Resend for marketing. Until Resend is configured, a local development server shows the verification or reset link in the app instead of sending it, and writes the sidebar notice to the server log instead of emailing it.
The systems that host spendklaro necessarily store the information described in this notice in order to run the product. That includes the application host, the database host and a cloud object-storage provider for original statement files and for payment texts you keep. Those providers process information only to store it and operate the service. We do not use them for advertising or for analytics of your financial information.
Once a week we send the product brief described above to xAI so it can draft a memo. That brief does not include your financial records. You can choose not to write a sentence. You cannot withdraw a sentence from a memo that has already been stored.
Depending on where you live, you may have rights to access, correct, delete or receive a copy of personal information, to restrict or object to certain processing and to withdraw consent where processing is based on consent. You can exercise the access, correction, export, deletion and consent-withdrawal controls described above in the product, principally in Settings and Activity.
Withdrawing consent does not affect processing that was lawful before withdrawal. Account deletion is irreversible.
This section describes rights commonly recognised under data protection law. It does not mean spendklaro has completed a GDPR, CCPA or similar compliance programme, and it is not legal advice.
spendklaro is not directed at children under 16, and we do not knowingly collect personal information from children. If you believe a child has created an account, delete it in Settings or contact us as described below.
We will revise this notice when our practices change. The date at the top of this page is the effective date of the current version.
You can exercise the controls in this notice in Settings after you sign in. A dedicated privacy contact address will be published before public launch. Use of spendklaro is also described in our Terms.