FinEye

Privacy Policy

Last updated: November 2, 2026

This Privacy Policy ("Policy") explains how FinEye, operated by PE Vladyslav Kaida ("we", "us", or "our"; also referred to as "Licensor" in our Terms of Use), VAT number 3615506315, registered in Mykolaiv, 54000, Ukraine, collects, uses, stores, shares, and deletes personal data when you use the FinEye mobile applications (iOS and Android), web version, and related online services including the FinEye Model Context Protocol (MCP) server and AI connection features (collectively, the "Application").

This Policy is part of our Terms of Use (End User License Agreement). By downloading, installing, registering for, connecting an AI client to, or using the Application, you acknowledge that you have read and understood this Policy.

Controller and contact

Data controller: PE Vladyslav Kaida (FinEye), Mykolaiv, 54000, Ukraine.
Email: support@fineye.app
We have not appointed a Data Protection Officer. For privacy requests, contact us at the email above.

1. Personal data we process

Depending on how you use the Application, we may process the following categories of personal data:

1.1. Account and profile data — internal user identifier (User ID), account settings, preferences, and related metadata needed to operate your account.

1.2. Financial and app content data — transactions, accounts, categories, tags, workspaces, net worth snapshots, workspace membership, and invitations, as well as data you import or enter manually. If you connect an AI client via MCP, tool responses may include this data for the workspace you authorize (see section 8.1).

1.3. Subscription and purchase data — subscription status, entitlements, product identifiers, and last activity timestamps processed through our subscription provider (we do not receive or store full payment card numbers; payments are handled by the relevant app store or payment provider).

1.4. Integration data (optional) — if you connect third-party services (for example, banking integrations), we store credentials or tokens necessary to provide that integration in encrypted form, as described in the Application.

1.5. AI connection / MCP data (optional) — if you connect a third-party AI application (for example, Claude or ChatGPT) through FinEye MCP: OAuth client identifiers and names, chosen access scopes (read and/or write), the active workspace binding (connections start on your personal workspace), account email associated with the connection, connection creation time, opaque access and refresh tokens, connection metadata needed to authenticate tool calls, and diagnostic logs of MCP requests (for security and reliability). We do not receive your AI provider account password.

1.6. Support contact data (optional) — email address or other contact details you voluntarily provide when contacting support.

1.7. Technical and usage data — device type, operating system, app version, approximate location (country/city where available), IP address, diagnostic logs, and analytics events (for example, via Firebase), in accordance with your device and platform settings.

2. Sources of data

2.1. Data you provide directly in the Application.
2.2. Data generated when you use the Application, including MCP tool calls made by an AI client you connected.
2.3. Data from app stores, subscription platforms, and payment providers (for example, Apple App Store, Google Play, RevenueCat, Paddle) to validate purchases and subscriptions.
2.4. Data from analytics and infrastructure providers listed in section 8.
2.5. Data from AI clients you authorize (client name, redirect URI, and related OAuth registration metadata).

3. Purposes and legal bases (GDPR)

We process personal data for the purposes below. Where GDPR applies, our legal bases include:

3.1. Providing the Application (performance of a contract / Art. 6(1)(b) GDPR) — creating and managing your account, syncing and displaying your financial data, workspaces, subscriptions, optional integrations, and optional AI connections / MCP access you request.

3.2. Security, fraud prevention, and service integrity (legitimate interests / Art. 6(1)(f) GDPR) — protecting accounts, investigating abuse, maintaining logs, enforcing rate limits and entitlements, and ensuring reliable operation, balanced against your rights.

3.3. Customer support (contract / legitimate interests) — responding to your requests and resolving issues.

3.4. Analytics and product improvement (legitimate interests / consent where required by law) — understanding how the Application is used and improving features, subject to your platform privacy settings.

3.5. Legal compliance and retention (legal obligation / legitimate interests) — complying with applicable law, enforcing our Terms, and applying the retention and deletion schedules described in sections 6 and 7.

4. Children

The Application is not directed to children under 16. We do not knowingly collect personal data from children under 16. If you believe we have collected such data, contact support@fineye.app and we will delete it promptly.

5. Your rights

Subject to applicable law (including GDPR where it applies), you may have the right to:

— access your personal data;
— rectify inaccurate data;
— erase your data ("right to be forgotten");
— restrict or object to certain processing;
— withdraw consent where processing is based on consent;
— data portability for data you provided in a structured, commonly used format;
— lodge a complaint with a supervisory authority in your country of residence, place of work, or place of the alleged infringement.

To exercise your rights, contact support@fineye.app or use in-app account deletion (see section 10). We may ask you to verify your identity. We will respond within a reasonable time and, where applicable law requires a specific deadline, within that period.

You may stop further MCP access by disconnecting FinEye in the AI client, by contacting support@fineye.app, or by deleting your FinEye account (section 10). Stopping access does not erase data already received or stored by the AI provider under its own policy.

Automated processing: We may automatically identify inactive accounts for deletion as described in section 7.2. This inactivity process is not intended to constitute automated decision-making that produces legal or similarly significant effects under GDPR Article 22. You may contact support if you believe your account was incorrectly flagged before our scheduled deletion process runs.

6. Retention periods

We keep personal data only as long as necessary for the purposes above, unless a longer period is required by law.

6.1. Active account data — retained while your account is active and you use the Application.

6.2. After manual deletion — deleted from production systems within a reasonable time and in any event as required by applicable law after a completed deletion request, except data we must retain by law (see section 10).

6.3. Inactive accounts — see section 7.2.

6.4. Support correspondence — typically up to 24 months after the ticket is closed, unless a longer period is needed for disputes or legal claims.

6.5. Analytics and technical logs — typically up to 14 months, or shorter where configured in our analytics tools. MCP diagnostic logs are kept only as needed for security and operations.

6.6. AI connection / OAuth grants — access tokens are short-lived (about one hour); refresh tokens and grants typically expire after about 30 days, or earlier if you disconnect the connection or we invalidate access for security or policy reasons. After account deletion, MCP access stops; residual OAuth connection records may remain until they expire under this schedule or are purged from our systems.

6.7. Backups — residual copies in encrypted backups may persist until the backup cycle expires (typically up to 90 days), after which they are overwritten.

7. Inactive accounts and automatic deletion

7.1. To limit unnecessary storage and protect user privacy, we apply an inactivity policy.

7.2. If you do not use the Application for six (6) consecutive months, as measured by our subscription/analytics provider based on your last recorded activity, we may delete your account and associated app data listed in section 10 (including data in workspaces you own), unless you have an active paid subscription or we must retain data by law. This Policy is your notice of that practice; we do not send separate reminder emails before scheduled deletion.

7.3. Using the Application again before the scheduled deletion process runs re-establishes activity and cancels deletion for that inactivity cycle.

8. Recipients, processors, and international transfers

We use trusted service providers who process data on our instructions. They may include:

— Supabase (database hosting, including storage used for MCP OAuth connection records) — supabase.com/privacy;
— RevenueCat (subscriptions and activity) — revenuecat.com/privacy;
— Paddle (payments on web, where applicable) — paddle.com/legal/privacy;
— Google Firebase (analytics) — policies.google.com/privacy;
— Apple App Store / Google Play — for distribution and in-app purchases, under their respective policies;
— Hosting / infrastructure for the MCP server and related APIs, under their respective policies.

8.1. AI clients you connect (independent parties)

MCP is optional. We do not send your financial data to an AI provider unless you connect that client and approve access (including the scope you choose). After you allow a connection, the AI client may request FinEye tools and receive responses that include personal and financial data from the authorized workspace. That disclosure is made at your direction to provide the feature you requested.

AI providers and AI applications (for example, Anthropic, OpenAI, or other MCP clients) are independent controllers or services. Their processing, retention, training, and subprocessors are governed by their terms and privacy policies, not ours. We do not control how they use data after it leaves FinEye. Review their policies before connecting. You can stop further FinEye access by revoking the connection (section 5); disconnecting does not delete copies already held by the AI provider.

Some providers are located outside your country (including the United States). Where required for our processors, we rely on appropriate safeguards such as the European Commission’s Standard Contractual Clauses or equivalent mechanisms. Transfers to an AI client you connect are based on your request to use that integration; you may contact us for more information about transfers relevant to your FinEye account data.

We may also disclose data if required by law, court order, or governmental request, or to protect our rights, users, or the public, to the extent permitted by law.

9. Security

We use technical and organizational measures to protect your data, including encrypted connections (HTTPS), secure cloud hosting, access controls, and database rules (including row-level security) that limit access to your information. Banking integration tokens, if you use them, are stored and handled with additional care. For MCP, we use OAuth-based authorization, opaque access tokens scoped to the MCP service, short-lived credentials for data access, and workspace / scope checks on tool calls. You can stop a connection as described in section 5.

Please keep your device and app up to date, do not share access to your account, only approve AI clients you trust, prefer read-only scope when write access is unnecessary, and contact support@fineye.app if you notice suspicious activity. No online service can guarantee absolute security; we address data breaches as required by applicable law.

10. Account and data deletion

You may delete your account at any time:
— in the Application: Settings → Delete Account;
— by email to support@fineye.app with subject Account Deletion Request and your User ID (Settings → Profile → User ID).

Data we delete (subject to technical and legal limits) includes, without limitation: account/profile data, transactions, accounts, categories, tags, settings, net worth records, workspaces you own (and related workspace data), workspace memberships, workspace invitations, and integration credentials (for example, Monobank links). MCP access tied to your account stops; residual OAuth connection records are handled as described in section 6.6.

Data we may retain after deletion: minimal records required by tax, accounting, fraud prevention, or other applicable law; anonymized or aggregated data that no longer identifies you; and backup copies until the backup retention cycle ends (section 6.7).

Deleting your FinEye account or disconnecting an AI client does not require AI providers to delete data they already received. Use each provider’s own controls where available.

Detailed steps are also described in our Terms of Use .

11. Business transfers and successor controller

If we merge, are acquired, reorganize, or transfer the Application to another legal entity or affiliate, your personal data may be transferred to the successor that continues to operate the Application. The successor will assume the obligations in this Policy, and we will provide notice as required by applicable law. You may contact us before the transfer takes effect if you have questions or wish to exercise your rights (including account deletion).

12. Changes to this Policy

We may update this Policy from time to time. For material changes (for example, a new data controller, new purposes, new categories of recipients, or changes to automatic deletion), we will provide notice through the Application or by posting an updated Policy with a new "Last updated" date, with advance notice where required by applicable law. Continued use after the effective date constitutes acceptance where permitted by law.

13. Questions

FinEye (PE Vladyslav Kaida)
Mykolaiv, 54000, Ukraine
Email: support@fineye.app

FinEye

Finanse osobiste w jednej aplikacji

Pobierz aplikację

iOSAndroid

Produkt

Aplikacja FinEyeCennikIntegracje AI

Społeczność

DiscordTelegramWsparcie

© 2026 FinEye. Wszystkie prawa zastrzeżone.Polityka PrywatnościWarunki Świadczenia Usług