Privacy and data retention

Last updated 29 September 2026

This notice explains the current TrakBuk private-beta service in plain language.

What we collect

We store your name, email address, password hash when you use a password, customer account and workspace membership, account labels and last four account-number digits, parsed transaction rows, import reconciliation details, daily-spending entries, notification choices, and security activity records. Older accounts may also contain budget or savings-goal records created while those beta features were available.

Statement files

A statement file is used to extract transactions and reconciliation totals, then the uploaded file is discarded. The parsed rows stay in your account until you remove the import, account, workspace, or customer account. We do not request online-banking passwords, BVNs, or full account numbers.

Data kept on this device

Daily-spending entries and pending changes may be kept in this browser so the feature can work without a connection. TrakBuk clears that offline store and its browser cache when you log out or confirm account deletion. Clearing this browser's site data also removes it.

How we use it

We use the data to provide imports, categories, spending summaries, reminders, exports, and workspace access. Automated categories and insights are estimates that you can review. We do not sell your financial data or use it for advertising.

Email, push notifications and service providers

Essential verification, security, invitation, and deletion messages are sent when needed. Financial summaries and warnings are optional. Email, hosting, database-backup, and web-push providers process only the information needed to deliver those services on our behalf.

Retention and deletion

Active records are kept while your customer account is active. Confirmed customer-account deletion has a seven-day recovery period, after which the profile and financial records are permanently removed from the active service. Operational security records are retained for up to 12 months unless a longer period is required to investigate abuse or comply with law. Backup copies follow the hosting provider's protected retention cycle and expire separately.

Security

Access is restricted by customer account and workspace. Passwords are hashed, sensitive connections use encryption in transit, and access-changing actions are audited without request bodies, passwords, transaction narrations, or account numbers. Production backups depend on the configured hosting provider and are checked through operational restore procedures.

Your choices

You can correct account details, review automated categories, download an Excel copy, disable optional notifications, remove imported records, leave a shared workspace, or request customer-account deletion from Profile. Contact noreply@tcmlogic.com with a privacy or access request during the private beta.