Privacy Policy

Version: 2026-10-28.1. Effective date: 28 October 2026.

1. Controller and contact

Finooi is a product name, not a claim that it is a registered company. Data controller: [LEGAL OPERATOR NAME AND CORRESPONDENCE ADDRESS TO BE CONFIRMED; COMPANY DETAILS IF APPLICABLE]. The controller decides why and how your personal information is processed. Its identity, and any required representative or data protection officer details, remain outstanding and must be completed before treating this as the final public legal notice.

Contact support@finooi.com for privacy requests, support, security concerns and complaints. noreply@finooi.com is used for transactional email and is not the support inbox.

2. Information we process

• Account information: email address, user identifier, password authentication information, confirmation and recovery information, and session credentials. Passwords are handled by Supabase Auth; Finooi does not maintain a separate password database.
• Profile and workspace information: first name, surname, identifiers, workspace ownership/name, GBP currency preference, registration status and creation/update timestamps. Names collected at signup populate the profile and can be updated through My Account.
• Financial information you enter: financial entities and contexts, account names/types and institutions, balances and observation dates, income and expenses, categories, transaction descriptions, transfers and monthly budget targets. Supporting ledger records, request receipts and timestamps maintain consistency and retry behaviour. Summaries and forecasts are calculated from these saved records.
• Acceptance information: your user identifier, the policy version and database timestamp captured when you explicitly agree during signup. These are saved in protected profile fields when the new account is created, then recorded in the acceptance history after your email is verified. Later changes to editable Auth metadata are not acceptance evidence. Existing users are not assigned historical acceptance.
• Device and request information: IP addresses, browser/request details and session information processed by hosting, authentication and email infrastructure for delivery, security and troubleshooting.
• Support information: communications you send to the operator. Do not include passwords, active authentication links, full card details or unnecessary financial records.

The separate demonstration uses sample financial data and keeps edits in memory. Those edits are not saved into your private workspace. A browser display preference persists separately as described below.

3. Purposes and lawful bases

We process account/profile information to provide requested registration, confirmation, sign-in, recovery and private workspace access, and financial entries to save records and provide requested calculations. The basis is performance of our service contract or steps you request before entering it.

We process necessary security, request and operational information to protect users, prevent abuse and resolve faults, relying on legitimate interests in a safe and reliable service. Acceptance evidence and necessary dispute records support proportionate administration and establishing or defending claims, also relying on legitimate interests. These uses must be necessary and balanced against your rights. Support uses contract where needed to deliver the service and legitimate interests for other necessary administration. Where a specific legal duty requires processing, we rely on that duty and limit processing accordingly.

Policy acceptance is not blanket data-processing consent. There is no optional marketing subscription or analytics-consent flow, and no advertising tracker or optional analytics SDK is integrated. Any future consent-based purpose requires separate, freely chosen consent that can be withdrawn.

4. Providers and recipients

Supabase provides authentication and the database containing profile, workspace, acceptance and financial records. Vercel hosts the application. Postmark delivers transactional authentication emails through Supabase SMTP, including confirmation and recovery messages; the configured sender is noreply@finooi.com. That sender address is not a verified support or privacy inbox.

Authorised administrators and providers may access information where necessary for service delivery, support or security. Workspace isolation does not mean that administrators and infrastructure providers can never access information. We may disclose information where required by law or otherwise supported by an applicable lawful basis, limited to what is appropriate. No payment processor, live bank feed or credit-bureau integration is connected.

5. Locations and transfers

The production database region, hosting/email processing locations and countries of administrative access have not been confirmed in this repository. UK-only storage or processing is not promised. The operator must confirm actual processing locations and any applicable international-transfer safeguards before public release. Contact support@finooi.com for details. This notice does not claim an unverified adequacy arrangement or contractual safeguard is already in place.

6. Cookies and browser storage

Supabase cookies support authentication, session refresh and recovery. They are accessible to the browser authentication client and sent with relevant requests. The application uses SameSite=Lax and Secure in production. Login can persist between visits; sign out on shared devices. Restricting cookies can prevent authentication from working.

The net-worth display preference uses browser local storage under fcc.profilePreferences. It is not a stored financial balance, is not scoped to a user account and can remain after sign-out or browser restart until overwritten or cleared. Clearing site data can remove that preference and authentication state; it does not delete your backend account. Separate demo edits generally disappear on reload.

No advertising cookies or optional analytics SDK are integrated. Infrastructure logging still occurs. Policy acceptance does not authorise unrelated tracking or replace any separately required storage consent.

7. Security and workspace isolation

The application uses Supabase authentication, cookie sessions, server-side user verification and database ownership policies. Row Level Security isolates user-owned records. Application reads derive workspace ownership from the verified user; financial contexts are organisational filters. Elevated database credentials are not exposed in browser code.

These controls reduce risk and do not guarantee uninterrupted access or prevent every loss or unauthorised disclosure. Keep credentials secure, check your entries and retain original financial records. Report suspected misuse at support@finooi.com.

8. Retention and deletion

The application does not automatically expire accounts or financial records. We retain account and financial information while needed to provide your account and requested history. Retention after a request or account closure depends on the information needed to fulfil that request, resolve disputes, maintain security or meet applicable legal duties. Retention must be limited to those purposes; no indefinite archival right is created here. Provider logs and backups may follow separate schedules. Specific provider schedules have not been verified, and immediate erasure of all copies is not promised.

Signing out, clearing browser storage, hiding or closing a financial account does not delete backend records. Permanent account deletion is separately gated and is unavailable unless enabled by the operator. When enabled, it verifies identity and removes the Auth account and associated application records, including financial history and acceptance records; a failure can leave the account intact and a network timeout can leave the outcome uncertain. Provider logs, backups and preferences on other devices are not synchronously erased by that operation.

There is no active self-service financial-data reset or complete personal-data export. The demonstration PDF control is not a full data export or deletion mechanism. Requests and statutory rights must still be handled through the operator, with appropriate identity checks.

9. Your rights and complaints

Subject to applicable conditions, you may request access, correction, erasure, restriction or portability of personal information. You may object to processing based on legitimate interests. Where processing relies on consent, you may withdraw it without affecting earlier lawful processing. These rights depend on the purpose and basis and are not absolute.

Email support@finooi.com for requests and complaints. You may complain to the Information Commissioner's Office about UK data protection concerns without first complaining to us.

10. Required information and changes

Email, password, first name and surname are required for the registration offered here. Your explicit signup agreement and email confirmation are required to finish setup; the saved agreement is finalised automatically for the verified user. Financial entry is optional; no financial record is required to retain access or view the demonstration. Do not supply online-banking passwords, full card details, health information or unnecessary third-party personal details.

Forecasts are informational calculations, not automated lending, investment or other decisions with legal or similarly significant effects. Open Banking, payment execution, subscription billing and an AI financial adviser are not connected. Material new processing requires an updated explanation before it begins. The version and effective date identify this notice; acknowledging it is not consent to future processing.