Financeia does not sell private financial records or use them for targeted advertising.
PRIVACY POLICY
How Financeia handles
your information.
This Policy explains what Financeia handles across the public website and customer applications, why it is needed, when it may be disclosed, how long it is retained, and the choices available to you. It is written for a product that may contain highly sensitive financial context even when the data is not legally classified as a special category.
Effective Website, web app, Android, and iOSVersion 1.2
Workspace data is processed to provide the features you request, keep them secure, and satisfy applicable law.
Product analytics, billing records, administrator history, and operational telemetry use distinct purposes, access rules, and retention controls.
Important current-product boundary
Financeia currently receives financial information that you enter or import. It does not connect to your bank, request online-banking credentials, initiate transactions, or store full payment-card details. Financeia does not share your financial data with external AI services unless you explicitly connect one and grant access to selected data. The public Contact and Journal forms prepare an email on your device; the page itself does not upload the form values. Administrative, first-party analytics, billing, and expanded operational modules may be released in stages. A described module handles information only after it is enabled in the relevant production service.
Who we are and what this Policy covers
The responsible service
Financeia is the financial-organization service responsible for the processing described in this Policy. Where data-protection law uses the term “controller,” the legal operator identified in the applicable app-store listing or purchase record is the controller for Financeia account and service information. Contact details are provided at the end of this Policy.
This Policy covers the Financeia public website, web application, Android and iOS applications, authentication and device approval, account settings, financial workspaces, imports, reports, exports, support communications received by Financeia, first-party product measurement when enabled, subscription and entitlement administration when enabled, restricted internal administration, and related service operations. It does not govern a third-party website, app store, email provider, operating system, or service that acts independently under its own policy.
Your role when adding another person’s data
If you add information about an employee, client, tenant, partner, family member, beneficial owner, or another individual, you decide why that information is entered and whether you have authority to do so. Depending on the circumstances, you or your organization may be a separate controller and responsible for required notices, permissions, legal bases, and responses to that person’s requests.
Our privacy commitments
We seek to collect only information reasonably needed for the feature, security control, support request, or legal duty.
Private balances, salaries, transaction amounts, merchants, descriptions, notes, and account details are excluded from behavioral analytics and are not used for targeted advertising.
Requests are evaluated against an authenticated user and explicitly selected workspace.
Manual, estimated, converted, reference, demonstration, and dated values should remain distinguishable.
You can review sessions, export the workspace, correct profile details, and start authenticated deletion.
Public support forms do not transmit a message until you choose to send the prepared email.
The current public website and applications do not deploy third-party advertising cookies or cross-site behavioral tracking. Financeia may operate purpose-limited first-party product analytics to understand whether features work and where users encounter difficulty. That system is separated from the financial ledger and is not a copy of it. If Financeia proposes a materially different use of personal information, this Policy will be updated before that use begins and consent or another valid legal basis will be obtained where required.
Information we collect and handle
| Category | Examples | When it is handled |
|---|---|---|
| Account and profile | Email address, display name, avatar selection, account status, locale, time zone, and reporting currency. | Registration, profile management, localization, and account administration. |
| Authentication and security | Password verifier, optional two-factor policy, one-time challenge records, opaque session and approval tokens, trusted-device identifier and name, platform, push token where enabled, sign-in times, session status, and security events. | Account creation, sign-in, recovery, mobile approval or verified-email fallback, password or email change, session review, and deletion verification. |
| Financial workspace | Accounts, balances, currencies, events, categories, budgets, goals, recurring items, transfers, ledger entries, business or household scope, ownership interests, holdings, property, manual valuations, conversion choices, dates, and notes. | When you enter, import, classify, calculate, synchronize, review, or export records. |
| Files and generated materials | Import workbooks, validation results, reconciliation information, export archives, and requested PDF reports. | When you use import, export, reconciliation, or reporting features. |
| AI assistant connections | Your consent and withdrawal records (date and time, consent version and language, a fingerprint of the accepted text, the statements you confirmed, web or phone, a keyed one-way hash of the device and network address, and the browser or app description); each connection’s assistant name and web address, permissions, selected profiles, and dates; one-way hashes of connection credentials; an activity log of which Financeia tools an assistant used and when; and proposals an assistant sent, stored encrypted until they are decided and removed. | Only if you turn on AI assistant connections and connect an assistant. |
| Device and service operations | IP address used for security and rate limiting, browser or platform type, app version where provided, request time, route, response status, correlation identifier, and limited diagnostic events. | When a device communicates with the service or an error is investigated. |
| Support and legal communications | Name, reply email, subject, message, attachments you choose to send, correspondence history, and safe diagnostic context. | Only after you send an email or otherwise communicate with Financeia. |
| First-party product analytics | Pseudonymous event and session identifiers, event name, feature or onboarding stage, time, platform, application version, selected language, coarse country or region where available, and success or error state. Behavioral events exclude financial values and record contents. | Only when product analytics is enabled and you use a measured website or application feature. |
| Purchase and entitlement | Store, product and plan identifiers, subscription status and period, transaction reference, renewal, grace, cancellation, or refund state, region, verified provider event, and a time-limited support entitlement where authorized. Financeia does not need your full card number. | When store subscription processing is enabled and you make, restore, or request support for a purchase. |
| Administrator and support history | Authorized administrator identity, role, authentication strength, action, time, pseudonymous target, stated operational reason, outcome, approval, and support note. Biometric templates and device unlock credentials are not received by Financeia. | When authorized personnel secure or support an account, administer a verified entitlement, manage the internal team, or review a controlled operation. |
| Operational telemetry | Service, release and environment identifiers, route or component, time, response status, error code, correlation identifier, performance and availability measurements, and minimized security context. | When the service operates, detects an error, prevents abuse, or is investigated. |
Information we deliberately do not request
The current service does not request your online-banking password, brokerage password, card security code, full payment-card number, government identity number, precise location, contact list, photos, microphone, or camera. Behavioral analytics must not contain balances, salaries, transaction amounts, merchant names, transaction descriptions, account names or numbers, financial notes, import contents, or report contents. Do not place prohibited or unnecessary information in names, notes, uploads, analytics feedback, or support messages. Device permissions and data practices must be updated in this Policy before a future feature uses them.
Derived information
Financeia calculates totals, balances, cash flow, budget status, net worth, conversions, trends, ownership values, and other reports from workspace records. These derived figures remain part of the financial workspace and receive the same treatment as the underlying data.
Where information comes from
- Directly from you: registration, profile choices, financial entries, settings, imports, exports, report requests, and communications you send.
- From authorized workspace members: records, invitations, role changes, and edits made in a shared scope, where that feature is available.
- Automatically from the service and device: session state, device identifier, platform, application version, first-party product events where enabled, request metadata, correlation identifiers, security events, and minimized error context needed to operate, understand, and protect the service.
- From an AI assistant you connect: proposals it sends for your review, the request text it attaches to them, and technical details it provides when it identifies itself to Financeia.
- From app stores: verified purchase, renewal, cancellation, grace-period, refund, and entitlement events when store subscription processing is enabled.
- From authorized Financeia personnel: role assignments, security and support actions, operational reasons, approvals, and support notes entered through the restricted administration service.
- From public reference-data providers: centrally refreshed currency and limited market snapshots. Mobile and web clients read Financeia’s stored snapshot rather than sending each user’s portfolio or identity to those providers.
Financeia does not currently obtain bank-transaction history from financial institutions or data aggregators. If that changes, the connection flow will identify the provider, requested accounts and fields, purpose, duration, revocation method, and applicable terms before access is authorized.
Why we process information and the legal bases
The legal basis depends on the jurisdiction and purpose. Where the EU GDPR, UK GDPR, UAE Personal Data Protection Law, or a comparable law requires a basis, Financeia relies on the following as applicable:
| Purpose | Information involved | Typical legal basis |
|---|---|---|
| Create and provide the account | Account, profile, authentication, workspace records, files, and derived reports. | Performing the Terms and taking requested steps before entering them. |
| Synchronize and preserve record integrity | Workspace versions, edits, device context where needed, ledger history, and audit records. | Performing the Terms and legitimate interests in reliable, traceable records. |
| Protect users and the service | Sessions, devices, IP-based rate-limit key, authentication events, request metadata, and limited logs. | Performing the Terms, legitimate interests in security and abuse prevention, and legal obligations. |
| Respond to support and rights requests | Account details, correspondence, requested records, identity-verification material, and relevant diagnostics. | Performing the Terms, legitimate interests in support, consent where required, and legal obligations. |
| Measure and improve the product | Purpose-limited first-party product events and aggregated activation, reliability, retention, and feature-use measures that exclude financial record contents. | Legitimate interests in understanding and improving the service, or consent where required. |
| Administer access and accountable support | Administrator identity and role, linked-app approval records, support notes, action history, and minimized customer and diagnostic context. | Legitimate interests in secure, accountable operations; performing the Terms; and legal obligations. |
| Administer a store purchase | Verified provider transaction and entitlement information, plan, region, status, support history, and a separately recorded temporary support grant where authorized. | Performing the purchase contract and tax, accounting, consumer, fraud-prevention, and recordkeeping obligations. |
| Connect an AI assistant you choose | The profiles and permissions you select, the financial records an assistant reads within them, proposals it sends, consent records, connection details, and the activity log. | Your consent, which you can withdraw at any time in Settings; performing the Terms for the feature you requested; and legitimate interests in keeping evidence of consent and in security. |
| Comply with and defend legal rights | Information reasonably relevant to lawful requests, disputes, enforcement, safety, and records we must preserve. | Legal obligations and legitimate interests in establishing, exercising, or defending legal claims. |
Where we rely on legitimate interests, we consider the necessity of the processing, its benefit, its likely effect on you, and reasonable safeguards. You may object as described below. Where consent is the basis, you may withdraw it at any time without affecting processing already lawfully completed. Information required to create and operate an account is contractual; without it, Financeia cannot provide that account or feature.
Financeia does not use private financial records for targeted advertising, sell them to data brokers, or use them to determine eligibility for credit, employment, insurance, housing, or government benefits.
AI assistant connections
Off by default.
Financeia does not share your financial data with external AI services unless you explicitly connect one and grant access to selected data.
AI assistant connections let you use an external assistant, such as one that supports the Model Context Protocol (MCP), with your Financeia records. The setting is off for every account until its user turns it on in Settings under Security preferences. Each person decides only for themselves: a plan owner cannot turn it on for a member, and a member cannot turn it on for an owner or for other members.
How access is granted
Turning the setting on requires you to read the consent, confirm each statement, and enter your password. Financeia keeps a record of that consent as described in the table above, and you can view it in Settings. Each assistant is then connected separately: you approve it on a Financeia page, choose the profiles it may use, and choose whether it may send proposals in addition to reading. In a Joint profile, an assistant can read only what your own role allows, and other members of that profile can see that you connected an assistant to it.
What the assistant receives
A connected assistant receives the information it requests from the profiles you selected, such as balances, transactions, categories, holdings, properties, and summaries. Financeia does not give an assistant your password, other members’ private records, or profiles you did not select. An assistant cannot change your records; proposals it sends are checked and wait for your approval.
Once an assistant receives information, it leaves Financeia. The assistant’s provider handles it under that provider’s own terms and privacy policy, may process it in other countries, and decides how it is stored, retained, or used, including for model training. That provider is not Financeia’s service provider, and Financeia cannot recall information it has already received.
Safeguards
Connections use OAuth 2.1 with PKCE verification of each authorization code, require your password to approve, are limited to the address Financeia issued them for, and end automatically after 90 days. Financeia stores only one-way hashes of connection credentials, keeps proposals encrypted, checks the connection and your setting again on every request, detects reused credentials and disconnects the connection, and limits how often an assistant may make requests. Turning the setting off or disconnecting an assistant stops further access immediately.
Hosting location and international processing
Financeia may be accessed globally, and information may be processed in countries where its operator and configured providers maintain infrastructure or personnel. Laws in those countries may differ from the law where you live. The precise hosting and backup locations are deployment-specific; Financeia does not claim a fixed data-residency location in this Policy.
Where transfer-restriction law applies, a transfer must rely on a recognized mechanism or exception appropriate to the circumstances. Depending on the route, that may include an adequacy decision, approved contractual safeguards such as standard contractual clauses, or a legally permitted necessity or derogation. Supplementary technical and organizational safeguards should be applied where required by the transfer assessment.
You may contact us to ask about the processing locations and transfer safeguard that apply to your account. A country-specific data-residency commitment applies only if expressly stated in a signed service agreement or deployment notice.
How long information is retained
Financeia retains personal information only for as long as reasonably needed for the purpose described, to keep the service and records reliable, and to meet legal requirements. Retention is determined by the nature and sensitivity of the information, account status, feature requirements, security risk, applicable limitation periods, and tax, accounting, consumer, dispute, and legal-preservation duties. Product analytics, provider billing records, administrator history, and operational telemetry are separate record classes; they do not share one default period or access policy.
Account and workspaceWhile the account is active and until you remove information or complete permanent account deletion, subject to the exceptions below.
Sessions and verificationSessions have a maximum validity period and can be revoked earlier. Verification and approval codes expire within short stated windows, but limited security records may remain as needed to prevent abuse.
Imports, exports, and reportsAccording to the requested workflow, account controls, and storage needed to deliver or validate the file; included in active-data deletion.
AI assistant connectionsConsent and withdrawal records are kept unchanged while the account exists, as evidence of what you agreed to. Assistant activity records are kept for 365 days. A proposal you do not decide expires after 30 days, and decided proposals are removed 30 days after the decision. Connection credentials expire automatically: access credentials after one hour, renewal credentials after 30 days, and every connection after 90 days. All of these are deleted with the account.
First-party product analyticsWhen enabled, the planned default is up to 90 days for raw events and up to 13 months for linkable user-level aggregates. Irreversibly de-identified statistics may be kept longer where reasonably needed to compare product performance.
Provider billing and entitlementWhen enabled, for the subscription lifecycle and any longer period required for tax, accounting, fraud prevention, refunds, disputes, provider reconciliation, or legal preservation.
Administrator and support historyWhen enabled, support notes remain for the case and an appropriate follow-up period. The planned default for append-only administrative history is 24 months, with longer retention for billing, security, legal-preservation, or dispute records where required.
Operational telemetryWhen enabled, the planned default is up to 30 days for ordinary service logs and up to 90 days for security-relevant events, unless an incident, legal duty, or verified operational need requires another period.
These periods are operational defaults for modules that are enabled, not promises to retain every item for the maximum period. A shorter period may be used when information is no longer necessary, and a longer period may apply where law, a provider obligation, fraud prevention, security investigation, legal hold, or the establishment, exercise, or defence of claims requires it. Production configuration must be reviewed against the applicable jurisdiction and documented before a module is released.
Account deletion
Authenticated deletion immediately purges active account identity and financial workspace data and invalidates sessions. Deletion is irreversible. When product analytics is enabled, linkable analytics identifiers are deleted or de-linked according to the active deletion specification; statistics that were already irreversibly de-identified cannot be associated with the account. Operational backups, when configured, are outside normal application access and follow the verified retention and security controls of that deployment. Because those controls are deployment-specific, this Policy does not state an unverified fixed backup expiry.
Short-lived pseudonymous rate-limit records may remain until the configured window expires. Financeia retains an unlinkable receipt that records only a random receipt identifier, completion time, and purge-scope version; it contains no user ID, workspace ID, email address, or financial-data hash. Read the Account deletion page or the linked machine-readable policy for the current pathway.
Deletion from Financeia does not cancel or erase records independently controlled by an app store, email provider, another authorized user, or an authority. Financeia may preserve minimized provider-billing, support, security, and append-only administrator records when legally or operationally required; retained administrator history should use a pseudonymous target where direct identification is no longer necessary and must not contain the customer’s financial record contents. Cancel a store subscription separately before deleting the Financeia account if one exists.
Security, confidentiality, and incidents
Financeia uses administrative, technical, and organizational measures designed for the sensitivity of financial-workspace information. The implemented foundation includes password verifiers rather than readable passwords, encrypted verified-email storage, opaque and revocable sessions, device-bound mobile session storage, secure web cookies, authenticated workspace boundaries, version-aware writes, immutable ledger corrections, rate limits, restricted browser capabilities, and security-focused logging.
Hosted requests are scoped to a verified user and selected workspace, with database row-level controls designed to reinforce that boundary. Production traffic is intended to use encrypted transport, and mobile applications use platform-protected storage for session credentials. Access by personnel and providers should be limited to a legitimate operational purpose and appropriate authorization.
The restricted administration service uses a separate password and session audience, mandatory approval through the administrator's linked Financeia app, server-enforced role permissions, recent verified-session authorization for sensitive actions, and append-only action history. The mobile app requires operating-system biometrics or the device PIN, password, or pattern before it sends an approval; a verified email code is available only as a fallback. Financeia does not receive the biometric template or device unlock credential. The administration browser does not connect directly to the database, reuse a customer session, silently impersonate a customer, or give a role unrestricted access to private financial records.
No security system is impenetrable, and Financeia cannot guarantee absolute security. You can reduce risk by using a unique password, protecting the verified email account and device lock, reviewing active sessions, installing trusted updates, and refusing unexpected requests for a password or one-time code.
Report a suspected incident promptly.
Revoke unfamiliar sessions and contact contact@financeia.app. Do not send a password, one-time code, recovery secret, or full financial export. If an incident affecting your information requires notice under applicable law, Financeia will provide that notice through an appropriate channel.
Your privacy rights and choices
Depending on where you live and the reason for processing, you may have rights to:
- know whether and how personal information is processed and receive a copy;
- correct inaccurate information and complete information that is materially incomplete;
- delete information in circumstances provided by law;
- receive qualifying information in a portable, machine-readable format;
- restrict or object to particular processing, including direct marketing;
- withdraw consent where processing relies on consent;
- opt out of a sale, targeted advertising, or qualifying profiling where applicable;
- ask for human review of a qualifying solely automated decision;
- appeal a refusal where local law provides an appeal; and
- complain to the data-protection, privacy, or consumer authority where you live or work, or where an alleged violation occurred.
Controls available now
Authenticated Settings lets you edit profile information, change the password, review and revoke sessions, turn AI assistant connections on or off, disconnect an assistant, view your consent history and assistant activity, request a portable workspace export, and start permanent deletion. The public Account deletion page links to the authenticated process. Browser or device settings control local preferences and notifications.
When first-party product analytics is enabled, you may also object to processing based on legitimate interests or withdraw consent where consent is the applicable basis. A valid request may cover linkable analytics, provider entitlement records, support notes, operational records, and administrator history, subject to identity verification and lawful limits such as security, fraud prevention, another person’s rights, legal preservation, and append-only accountability obligations.
How to make a request
Email contact@financeia.app with “Privacy Request” in the subject and describe the right you wish to exercise. Use the verified account email where possible and do not attach unnecessary financial records. We may request proportionate verification and clarification to protect the account. An authorized agent may submit a request where local law allows, but we may require proof of authority and direct verification with you.
We will respond within the period required by applicable law. A request may be limited or refused where an exception applies, such as inability to verify identity, another person’s rights, legal privilege, security, fraud prevention, a legal obligation, or the establishment or defence of claims. We will explain a refusal and available appeal or complaint route where required. Financeia will not unlawfully discriminate against you for exercising a privacy right.
Additional regional disclosures
European Economic Area and United Kingdom
The purposes and legal bases above are intended to provide the information required by Articles 13 and 14 of the GDPR and UK GDPR. Rights may include access, rectification, erasure, restriction, portability, objection, withdrawal of consent, and complaint to a supervisory authority. If you object to direct marketing, processing for that purpose will stop. Financeia does not currently conduct direct marketing through the service.
United Arab Emirates
Where the UAE Personal Data Protection Law applies, processing is subject to its requirements and exceptions. Depending on the circumstances, rights may include obtaining information, access, portability, correction, erasure, restriction or cessation, objection to certain automated processing, and complaint to the competent authority. A request remains subject to identity verification and lawful exceptions.
California and other United States states
In the preceding 12 months, Financeia may have collected the categories described above: identifiers; customer-record information; internet or electronic-network activity; account credentials and financial information; and inferences consisting of calculated financial reports. First-party product analytics, provider purchase and entitlement records, administrator history, and expanded operational telemetry are included only to the extent the relevant module was enabled during that period. These categories are collected from the sources and for the purposes described in this Policy and disclosed only to the categories of recipients described above.
Financeia has not sold personal information or shared it for cross-context behavioral advertising, does not use sensitive personal information to infer characteristics or for purposes requiring a right to limit, and does not offer a financial incentive for personal information. We do not knowingly sell or share the personal information of anyone under 18. Applicable state rights may include access, correction, deletion, portability, opt-out, limitation, appeal, and non-discrimination. Because there is no current sale, targeted-advertising share, or qualifying profiling, an opt-out signal does not change those practices.
These regional descriptions do not claim that every law applies to Financeia in every circumstance. They explain the controls Financeia will provide when a relevant law covers the account or processing. You may contact the competent local authority even if it is not named here.
Children and family information
Financeia is designed for adults managing authorized personal, household, property, investment, or business records. It is not directed to children under 18, and they may not create accounts. We do not knowingly collect personal information directly from a child through account registration.
An adult may record a limited family-related financial item only where authorized and lawful, but should avoid unnecessary identifiers and sensitive details. A shared subscription does not change the minimum age for independent registration unless a separate child-appropriate experience, verified permission process, and required safeguards are introduced.
If you believe a child created an account or provided personal information directly, contact contact@financeia.app. We will investigate and take appropriate action, including deletion where required.
Calculations, profiling, and automated decisions
Financeia automatically calculates and displays financial totals, classifications, trends, budget progress, conversion results, and other reports from the records and settings in a workspace. These calculations help the user organize information; they do not approve or deny credit, insurance, employment, housing, benefits, or another legal right. Product engagement metrics, when enabled, are used to understand service use and reliability, not to make those decisions.
Financeia does not currently make a decision based solely on automated processing that produces legal or similarly significant effects about you. If such a feature is proposed, it will not be activated without the disclosure, lawful basis, explanation, safeguards, and human-review rights required by applicable law.
Policy changes and how to contact us
Changes to this Policy
We may update this Policy when the product, providers, security controls, laws, or commercial model change. The effective date identifies the current version. Financeia will review and, where necessary, update this Policy before activating a materially new analytics, billing, administration, or telemetry use. If a change materially affects how personal information is used, Financeia will provide notice appropriate to the change before it takes effect where required, and will seek consent where a new use requires it.
Contact and complaints
For a privacy question, rights request, complaint, or security concern, email contact@financeia.app. Include “Privacy” in the subject line and enough information to understand the request, but never include a password, one-time code, recovery secret, bank credential, or unnecessary financial record.
If you are dissatisfied with our response, you may request any internal appeal available under applicable law and complain to the privacy or data-protection authority with jurisdiction where you live, work, or believe a violation occurred.
Financeia Privacycontact@financeia.appFor account deletion, use the protected in-app flow whenever you can sign in.Open account deletion guidance