Privacy Policy

Fynora is operated by Fynora Technovation LLP, registered at 463, Sita Ram Compound, Chaman Ganj, Sipri Bazaar, Jhansi, Uttar Pradesh, 284003, India. Under the DPDP Act, Fynora Technovation LLP is the "Data Fiduciary" for the personal data described in this policy, and you are the "Data Principal." We process your personal data on the basis of the consent you give when you create an account and when you take actions in the app that involve sharing further data (such as importing a statement) — described in plain terms in the sections below, as the Act requires. You may withdraw consent at any time; since Fynora's core features depend on ongoing access to the data you've provided, withdrawing consent in practice means deleting your account (see Data Deletion below). Withdrawal does not affect the lawfulness of processing carried out before you withdrew it.

Fynora collects the information you provide directly (registration details, account and transaction data you add or import, and your answers to the short questions when you first set up Fynora: how you keep track of your spending today, which everyone is asked once, and what you hope to achieve with Fynora) and a small amount of technical information needed to operate the Service securely (login timestamps, IP address at login, device/browser information for session security).

This includes your full name, email address, and mobile number, collected at registration and used for authentication (including email-or-phone login), account recovery, and OTP-based phone verification.

Fynora stores the accounts, transactions, budgets, goals, and categorization data you create or import. This data is used exclusively to power the features you use — dashboards, reports, budgets, and insights — and is never sold to third parties or used for advertising.

When you import a bank or credit card statement, the original file is stored securely and linked to your account so you can re-download it or re-process it later from Statement History.

When we improve how statements are read, Fynora can refresh the transactions from your statements using these stored files, so you do not have to upload them again. We tell you in the app, by push notification and by email when an improvement would change your statements. A refresh runs only when you choose to start it, and afterwards shows you what changed: transactions added, corrected or removed. A transaction you edited keeps your changes.

In most cases statements are processed entirely automatically by Fynora's own rule-based extraction logic — Fynora does not send your statement or its contents to third-party AI services such as OpenAI, Anthropic, or Google Gemini as part of importing it. (Ask Fyn, a separate optional feature described below, does send data to Anthropic — but only your own already-processed transaction data, never a raw statement file.) When an import cannot be processed automatically, it is queued for review, and authorized staff may access the statement to diagnose and fix the problem. Every such access is logged and auditable; see Administrative Access below.

Some statements are password-protected PDFs. Fynora does not keep the password you type to open one unless you agree to it. When you enter a statement's password, we ask whether you want to save it so that statement can be refreshed without asking you again. Saving is optional and applies to that one statement only. If you choose not to save it, nothing is stored, and we will ask for the password, and offer to save it, the next time that statement is refreshed.

A saved password is stored encrypted and is used only to open that statement's file — to import it, to refresh it, and, if we could not read it automatically, to let authorized staff review it (see below). The password itself is never shown to you or to Fynora staff, and it is never written to logs. You can remove any saved password at any time from Settings → Data → Saved statement passwords, which deletes it immediately. A saved password is also deleted when you delete its statement or its account, or delete your Fynora account. We keep a record of when you gave and withdrew this consent.

If a statement whose password you saved is queued for review because we could not read it automatically, authorized staff reviewing it can open an unlocked copy so they can read its contents and fix the problem. The unlocked copy is created only for that review and is never stored, and every such access is logged.

When you use Ask Fyn, Fynora's AI assistant, your question and the specific account data needed to answer it — such as your balance, budget status, recent transactions, or spending by category — are sent to Anthropic's Claude API to generate a response. Fyn only reads data already stored in your account through a fixed set of lookups; it cannot take any action on your account, and it is instructed to state only figures it actually retrieved, never to guess or estimate one. It is not a financial advisor — if asked for investment advice or a recommendation about a future financial decision, it declines and suggests speaking with a licensed advisor. Your conversations are saved so you can scroll back through them, governed by the same administrative-access rules as your other account data (see Administrative Access below). Separately, each call to the AI is logged for cost and safety monitoring; that monitoring log does not contain your raw conversation text, only which lookup was used and how it performed.

If you attach a screenshot to a question, Fynora reads its text on its own servers and sends that text, not the image. Account numbers, card numbers, UPI IDs, IFSC codes and phone numbers in it are replaced with placeholders before it is sent.

Anthropic's service is also used in two other places. On the Insights page, Fyn writes a short summary of your month from category-level totals and your category names; it is never sent your transactions, merchant names or account details. And if you add a transaction by hand without choosing a category, and Fynora cannot work out a category from your own rules and corrections, its built-in rules, or a shared suggestion (see "Learning From Corrections Across Users" below), the description you typed and the names of your categories may be sent so it can suggest a category. A description that is a payment to a person is never sent, and in any description that is sent, UPI IDs, account and reference numbers and IFSC codes are removed first. Your amount, account details and user ID are never sent. The description is free text and may contain personal information if you type it; anything in it Fynora does not recognise as a name or an identifier is sent as written, so avoid typing anything sensitive into it. Importing a statement does not do this. The short description returned by the service is stored against the payee ID so it can be reused for later transactions with the same payee.

In all of these uses, Fynora hides the names of people it can recognise before anything is sent: the names on your profile and on your accounts, the people you have paid or been paid by (their full names, first names and surnames), names in a screenshot's text, and common first names and surnames from a list built into Fynora, even for someone you have never paid. Each is replaced with a placeholder such as [name-1], and Fynora puts the real name back into the answer before you see it, so Anthropic receives the placeholder, never the name. A name Fynora cannot recognise is sent as written: an uncommon name of someone you have never paid, or a name that is also an everyday word, such as Sunny, typed into a question.

Fynora uses essential, session-related storage (such as your authentication token) to keep you signed in. We do not currently use third-party advertising or tracking cookies. See our Cookie Policy for the full breakdown of exactly what's stored and why.

We may collect aggregated, non-identifying usage data (such as which features are used most) to improve the product. This is never combined with your individual financial data for any purpose outside operating and improving Fynora itself.

We also record the dates on which you use Fynora — the calendar date only, once per day, not the time or what you did — so we can understand how often the product is used. These records are linked to your account and are deleted if you delete your account.

Your data is used to: provide the core features you sign up for; generate categorization suggestions and financial insights (via Fynora's own rule-based logic, except for the three uses of an AI service described under "Ask Fyn (AI Assistant)" above); detect duplicate or transfer transactions; and secure your account (fraud/lockout detection on repeated failed logins).

When you set or confirm a category for a payment to a UPI ID that Fynora classifies as a business or a financial institution, Fynora records the payee's UPI ID, the category, the direction of the payment (money in or out), your account ID, how the payee was classified and the time, in an internal log that other users cannot see. This is used to improve category suggestions. The classification is automatic and can be wrong. Payments classified as an individual, or not classified, are not recorded.

If several separate users (at least three) categorise the same payee the same way, that category becomes a shared suggestion for other users' new transactions with the same payee ID. The shared record holds the payee ID, the direction, the category, how the choices were split, how many users agreed, and internal status and timestamps. It does not include your transaction amounts, transaction dates, account ID or statement files. A shared suggestion is used only when your own rules and corrections, and Fynora's built-in keyword rules, have no answer for a transaction, so it does not override a category you have chosen.

Entries for a payee that has no shared suggestion are deleted 180 days after the most recent entry when only one user has categorised that payee, or 365 days after the most recent entry when two users have. Entries for a payee that has a shared suggestion, or that has three or more users but no shared suggestion, currently have no scheduled deletion date. If you delete your account, the entries in the log that belong to your account are deleted. Shared suggestions are stored separately from individual user log entries, hold no account ID, and are not removed when an account is deleted.

Fynora runs on the following infrastructure and service providers, each processing only what its function requires:

• Firebase Authentication (Google) — sign-in and identity verification.
• Railway PostgreSQL — our primary database.
• Cloudflare R2 — storage for the original statement files you upload.
• Railway — backend application hosting.
• Cloudflare — frontend/website hosting and edge security.
• Resend — transactional email delivery (verification, password reset, notifications).
• TwoFactor — SMS/OTP delivery for phone verification.
• Anthropic — the AI service behind Ask Fyn, the Insights summary and category suggestions for hand-typed transactions, as described above.
• Firebase Cloud Messaging (Google) — delivery of push notifications to the mobile app, using a device token for your phone.
• Sentry — crash and error reporting for our apps and servers. Reports carry technical details of the error; the web and mobile apps remove form contents, your account identity and the identifying parts of page addresses before a report is sent. Session replay and performance tracing are switched off.
• Razorpay — payment processing for subscriptions bought on the web. Your card, UPI or bank details are entered into Razorpay's checkout, not into Fynora. Fynora keeps only what Razorpay reports back to show on your Billing page — for a card, its network and last four digits — never the full number.
• RevenueCat — manages subscriptions bought through the App Store or Google Play, identified by your Fynora account ID. Apple or Google processes the payment itself.
• Setu — Account Aggregator connectivity, used only if you choose to link a bank account through India's Account Aggregator framework, and only with the consent you give in that flow.
• Google Fonts, Google Sign-In and Sign in with Apple — the website loads its typefaces from Google's servers, and the Google and Apple sign-in buttons load those companies' scripts, so they receive your IP address and browser details when those load. See the Cookie Policy for when each one loads.

Some of these providers operate outside India — see Cross-Border Data Transfer below for how that's handled under the DPDP Act.

Passwords are hashed with bcrypt and never stored or logged in plain text. Password reset tokens and session refresh tokens are stored hashed, not in plain text, so a database compromise alone cannot be used to reset an account or hijack a session. Sessions are scoped per device, visible and individually revocable from Settings, and bounded by several limits: the short-lived access token behind each request expires every 15 minutes; a session signs itself out after 24 hours of inactivity, and in any case after 30 days from when you signed in, even with continuous use; and each use of a session automatically rotates it to a new token, so a token used more than once is treated as a sign of compromise and every session on the account is signed out as a precaution. All traffic between your device and Fynora's servers is encrypted in transit (HTTPS/TLS), and our website enforces HTTP Strict Transport Security (HSTS).

Your financial data (transactions, accounts, statements, budgets, goals) is protected by the security of the underlying infrastructure listed above (Railway, Cloudflare R2), rather than by an additional layer of Fynora-managed encryption on top of it. Statement passwords you choose to save (see Saved Statement Passwords above) are the exception: they are additionally encrypted by Fynora before they are stored.

Access to customer data by Fynora staff is governed by role-based permissions — a staff member only has access to the specific data their role requires, not blanket access to all customer data. Every administrative access to your data is logged and auditable, and access is permitted only where necessary to operate and support the Service (for example, reviewing a statement that failed automated processing — see Uploaded Statements above).

If a personal data breach occurs, we will notify the Data Protection Board of India and affected users as required under the DPDP Act, and take steps to contain and remediate the breach.

Your data is retained for as long as your account is active — Fynora does not automatically delete statements, transactions, or other data from an active account. If you delete an individual account (a bank/card/investment account you've added within Fynora), it and its statements continue to appear in Statement History for 7 days before being dropped from that view, purely so recent context isn't lost abruptly; there is no separate "undo delete" action.

We maintain routine backups of our production database for disaster recovery, with point-in-time recovery enabled. Because of this, a small amount of data may persist in encrypted backups for a limited period after you delete it from the live system, until those backups themselves cycle out — this is standard practice and does not mean the data remains accessible or in active use.

Security event logs (audit logs) of account activity are kept indefinitely for security purposes, but the detailed content of each event is cleared after 730 days, leaving only a minimal record (who, what, when) for as long as the log entry itself exists.

As a Data Principal under the DPDP Act, you have the right to:

• Access a summary of the personal data Fynora holds about you and how it is being processed.
• Correct or update inaccurate or incomplete personal data — directly in the app (Settings, Accounts, Transactions) for most fields, or by contacting [email protected].
• Erase personal data that is no longer needed for the purpose it was collected for — see Data Deletion below.
• Withdraw consent at any time, as easily as you gave it — including consent to keep a saved statement password, which you can withdraw from Settings without affecting anything else in your account.
• Nominate another individual to exercise these rights on your behalf in the event of your death or incapacity, by contacting [email protected].
• Grievance redressal — see below — and, if unresolved, the right to file a complaint with the Data Protection Board of India.

If you have a complaint about how Fynora handles your personal data, contact our Grievance Officer, Vishnu Narayan Tiwari, at [email protected] with the details of your concern. We aim to acknowledge and resolve grievances within 30 days. If you're not satisfied with the outcome, you may escalate the complaint to the Data Protection Board of India.

You can export your Fynora data at any time from Settings, on both the web app and the mobile app. Your export downloads as a ZIP archive containing your accounts, transactions, budgets, goals, and other data as JSON files, plus the original statement files you uploaded in their original format, along with a manifest listing exactly what's included (and, for transparency, what's deliberately excluded and why). Exporting requires you to re-confirm your password (or Google/Apple sign-in), the same as account deletion.

You can delete individual transactions, accounts, or statements at any time from within Fynora. You can also delete your entire Fynora account yourself, from Settings on either the web app or the mobile app — this requires you to re-confirm your password (or Google/Apple sign-in) plus a one-time code sent to you, as a safeguard against someone else deleting your account without your knowledge.

Account deletion is immediate and permanent once confirmed — there is no waiting period and no self-service way to undo it. Your transactions, budgets, and goals are permanently removed, and your personal information (name, phone number, email) is erased or replaced with an anonymized placeholder at that point.

Two known exceptions, disclosed here rather than left unstated: (1) a deleted statement's original filename and the account-holder name Fynora automatically detected on it are marked deleted but not currently erased from our database — and, for a statement imported before Fynora moved statement files to dedicated object storage, the original file itself may still be present in the database row the same way. We're aware of this and are working to close it. (2) As described under Data Retention above, a copy of your data may briefly persist in an encrypted backup until that backup cycles out. If you'd rather not go through the in-app flow, you can also request deletion by contacting [email protected].

Fynora does not sell your data to third parties. Each infrastructure and service provider listed above under Infrastructure & Service Providers receives only the minimum information needed to perform its specific function (for example, an email provider receives your email address and message content, not your transaction history).

Fynora's application data is currently hosted and processed on servers located outside India (in the United States). Some third-party services we use for authentication, communications and AI features are also based outside India. The DPDP Act permits this kind of transfer except to countries the Government of India specifically restricts by notification; we do not transfer data to any such restricted country. Wherever your data is processed, it remains subject to the protections described in this policy.

Fynora is intended for users 18 years of age or older and is not directed at children. We do not knowingly collect personal data from anyone under 18. If you believe a child has provided us personal data, contact our Grievance Officer at [email protected] and we will delete it.

We may update this policy from time to time. Material changes will be reflected by an updated "Last updated" date at the top of this page.