personal-ops

Privacy notice

How personal-ops handles bank account data

personal-ops is a private tool one person uses to read their own bank accounts. It has no users beyond its operator, sends account data nowhere, and can move no money.

01 Who is responsible

Yann Lauwers, acting as a natural person in Belgium, is the data controller. There is no company, no team and no third party behind this application. Reach the controller at yann@gpt.nexus for anything in this notice, including every right listed under clause 08.

02 What the application does

personal-ops reads the statements of bank accounts the controller holds or co-holds, and turns them into a personal ledger: categorising own spending, reconciling insurance premiums against what actually left the account, and keeping a household's books.

It is registered for account information services only. It holds no payment-initiation authority, so no call it can make transfers money, creates a standing order, or changes anything at the bank.

03 Which accounts it reaches

Only the accounts explicitly whitelisted by IBAN in the Enable Banking Control Panel, and only after the account holder has authorised access at their own bank. An account that is not whitelisted is stripped from the session even if it was authorised.

Where an account is co-held, access is authorised by one holder — the controller — under the mandate co-holders already carry over that account.

04 What is read

FieldWhat it holds
IBAN, account uidWhich account a statement belongs to
balanceBooked and available balance at the moment of the read
booking_date, value_dateWhen a movement was recorded and when it counted
transaction_amountAmount and currency
creditor, debtorCounterparty name and account, as the bank supplies it
remittance_informationThe communication or structured reference on the movement
bank_transaction_codeThe bank's own classification of the movement
entry_referenceThe bank's identifier, used so one movement is never counted twice

Nothing else is requested. No identity document, no national register number, no credential ever reaches the application — authorisation happens at the bank, under the bank's own strong customer authentication.

05 On what legal basis

The explicit consent of the account holder, given at their own bank, under Article 6(1)(a) GDPR and Article 67 of Directive (EU) 2015/2366 (PSD2). Consent is what creates the access, and withdrawing it ends the access.

A PSD2 access session lasts at most 180 days and then expires on its own. It can be revoked earlier at any moment, either in the bank's own app or by deleting the session; neither requires a request to the controller.

06 Who else sees it

Nobody. Statements are read by the account holder, for the account holder. They are not shared, not sold, not published, not used for advertising, and not used to build a profile. There is no automated decision-making within the meaning of Article 22 GDPR, because there is no decision the application takes.

One processor sits in the path: Enable Banking Oy (Helsinki, Finland), the licensed account information service provider that carries the technical connection to the bank. Its own privacy terms govern that leg, and the bank's terms govern the leg between the bank and it.

07 Where it is kept, and for how long

Fetched statements are written to the controller's own machine and stay there. There is no server, no hosted database and no cloud storage behind this application; the export directory is deliberately excluded from version control so that nothing is published by accident.

They are kept for as long as the personal ledger they feed is kept — a ledger of one's own spending is useful across years — and are deleted on request, or when the account link ends and is not renewed.

A statement read through the provider's sandbox application is still real financial data. The environment names which registration authorised the read, not whether what came back is invented, and sandbox statements are handled under this notice exactly as production ones are.

08 Rights of the account holder

  • Access (Art. 15) — ask what is held about an account and receive a copy.
  • Rectification (Art. 16) — correct anything inaccurate.
  • Erasure (Art. 17) — have the stored statements deleted.
  • Restriction (Art. 18) and objection (Art. 21) — limit or object to the processing.
  • Portability (Art. 20) — receive the data in a machine-readable form; it is already held as JSON and CSV.
  • Withdrawal of consent (Art. 7(3)) — at the bank, at any time, without giving a reason.

A request to yann@gpt.nexus is answered within one month. A complaint can be brought to the Belgian supervisory authority: Autorité de protection des données / Gegevensbeschermingsautoriteit, Rue de la Presse 35, 1000 Brussels — autoriteprotectiondonnees.be.

09 This page

This page is static. It sets no cookie, runs no analytics, loads no tracker, and records nothing about who reads it.