Privacy Policy

Who is responsible

Perfin is operated by Priyanshu Kumar, based in Sweden, who is the controller of your personal data. For privacy questions or requests, contact hello@finafa.eu.

Data we process and where it lives

The table lists every kind of data we hold, why, and where. Your ledger is kept on your device first and synced to our cloud database, so it survives a lost phone and works across devices.

Bank balances and transactions are financial data. We use them only to provide Perfin to you and never sell them or use them for advertising. We run no advertising or third-party analytics trackers.

Google account data

Perfin uses Google Sign-In only to let you log in. We ask Google for the basic profile scopes (openid, email and profile) and receive your name, email address, profile picture and a Google account identifier. We do not request access to your Gmail, Google Drive, Calendar or any other Google service.

• Use: to create and recognise your Perfin account, show your name and picture in the app, and contact you about your account. Nothing else.
• Optional Google Contacts: only if you choose "match phone numbers to my contacts" on the Payees page, Google asks you to allow read-only access to your contacts (scope contacts.readonly). We read your contacts once, only to find the name that belongs to a phone-number payee in your ledger. The contacts themselves are not stored and the access is not kept; only a name you confirm becomes a payee name. If you do not choose it, we never see your contacts.
• Sharing: we do not sell, rent or share this data with anyone, except the service providers listed below that run Perfin for us (for example our database host).
• Advertising and AI: we do not use it for advertising, profiling or to train AI models, and no person at Perfin reads it except to support you at your request.
• Storage and deletion: it is stored in our cloud database for as long as your account exists. Delete your data in Settings, or write to hello@finafa.eu, and it is removed. You can also remove Perfin's access in your Google Account settings (Security, Third-party access).

Perfin's use and transfer of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

Why we use it and our legal basis

• Providing Perfin (your ledger, sync, reports, imports): performance of our contract with you.
• Bank connection: your explicit consent, given at your bank when you authorise access. You can withdraw it at any time by disconnecting the bank in Bank connections; history already imported stays until you delete it.
• AI-assisted features (receipt and PDF statement reading, categorisation, payee cleanup, transfer and recurring detection, insights): your explicit, optional consent, asked separately when you set up Perfin and off until you agree. You can withdraw it at any time in Settings, Privacy and consent; Perfin then stops sending data to AI models and keeps working without those features.
• Security, reliability and troubleshooting: our legitimate interest in running a safe service.
• Legal obligations: where the law requires us to keep or disclose data.

How AI is used

Some features send data to AI models through the Vercel AI Gateway. Today this is Google Gemini, run in an EU data centre, for reading a scanned receipt or a PDF statement you import and for the assistant in About you (your own words and monthly totals by category, never payee names) (each request tells the gateway to run in the EU and to fail rather than run anywhere else), and OpenAI models, processed in the United States, for categorisation, payee cleanup, transfer and recurring-payment detection and insights. Depending on the feature, this can include receipt images and text, PDF statements; bank or ledger transaction text, amounts, dates and your own category names, so a category can be suggested; and summarised spending facts for insights. Bank credentials are never sent. AI output is a suggestion you can correct, and Perfin makes no decisions about you with legal or similarly significant effects. If you do not consent, none of this data is sent to any AI model.

Outside assistants (Claude, ChatGPT, Gemini)

You can let an AI assistant you use yourself, such as Claude (Anthropic), ChatGPT (OpenAI) or Gemini (Google), read your Perfin figures through Perfin's connector. This only happens after you approve that assistant in the Perfin app, and you can switch the feature off in Settings > Connections.

• What it can see: when you ask, the assistant receives answers about your own data, such as totals by category, transactions, recurring payments, budgets and goals. It cannot move money, pay bills, or change or delete transactions. It can create or change goals only if you also allow goal editing when you approve.
• How long: an approval stays for up to 30 days. The assistant renews its 30-minute access token in the background during that time. You can end a connection at any time in Settings > Connections, and switching the feature off ends them all.
• The log: Perfin keeps a log of each connection and each question the assistant asked (the tool, when, and whether it worked), so you can see what was shared. It is kept with your account and deleted with it.
• The assistant's side: what the assistant does with the answers it receives is covered by that provider's own terms and privacy policy, not by this policy.

Service providers (processors)

Each processes data only on our instructions, to run the service. Their own privacy documentation is linked below.

• VercelStockholm, Sweden (app) and Frankfurt, Germany (files)

  Application hosting, private file storage for receipts and backups, and the AI Gateway.

  Privacy policy ↗
• Oracle CloudStockholm, Sweden

  Runs the Postgres database holding your synced ledger, and its nightly backups.

  Privacy policy ↗
• OpenAIUnited States

  The AI models used for categorisation, payee cleanup and insights, reached through Vercel's AI Gateway.

  Privacy policy ↗
• Enable BankingFinland, EU

  A PSD2-licensed account information service provider. It is the source of your bank data, not a destination we send data to: when you connect a bank, it retrieves the accounts, balances and transactions you authorise and passes them to Perfin.

  Privacy policy ↗
• GoogleIreland/United States (sign-in); EU data centre (receipts, PDF statements, the assistant)

  Sign-in through Google Identity Services, and the Gemini AI model (on Google Vertex AI, in an EU data centre) used to read receipts you scan and PDF statements you import, and to answer what you write to the assistant in About you (your own words and monthly totals by category, never payee names), reached through Vercel's AI Gateway.

  Privacy policy ↗

Transfers outside the EU/EEA

Our database, hosting and file storage are all in the EU. AI requests for categorisation, payee cleanup and insights are processed in the United States by OpenAI, through Vercel's AI Gateway; receipt and PDF statement reading and the About-you assistant are processed by Google Gemini in the EU (Vercel's gateway can route that request through any Vercel region first, and Google may review flagged abuse or safety cases under its own policies). For these transfers we rely on the safeguards the GDPR allows: the EU–US Data Privacy Framework where the provider is certified, or the European Commission's Standard Contractual Clauses. You can ask us for details of the safeguards in use.

How long we keep it

• Your ledger and bank data: until you delete it or delete your account. We do not delete transaction history on a timer, because a ledger is only useful when complete.
• Weekly backups: the latest eight are kept and older ones removed automatically; all are deleted with your account.
• Working data the app can regenerate: bank sync logs and applied offline changes after 90 days, unused AI suggestions after 7 days, expired bank-authorisation records after 1 day, archived payees after 30 days.
• The activity log: about 13 months, then it is removed automatically.
• Bank connection consent: ends when the period your bank allows expires; you reconnect if you want more data.
• Technical logs: kept by our hosting provider for a short period.
• After you delete your account: bank consents are revoked with the provider, files and backups are removed, and all your rows are deleted together. Provider logs age out on their normal schedule.

Security

Data is encrypted in transit (HTTPS) and at rest by our database and file-storage providers. Bank keys and API credentials stay on the server and are never sent to your browser, and every request is checked against your signed-in account. The copy on your device sits in your browser's local database, protected by your device lock rather than a separate password, so use a screen lock and sign out on shared devices. If a breach affects you we will tell you and the Swedish supervisory authority as the law requires.

Cookies and local storage

Perfin uses only what it needs to work: a sign-in session cookie, and your device's local database, cache and service worker so the app opens instantly and works offline. There are no advertising or tracking cookies. Clearing site data removes the local copy; your synced data stays in the cloud until you delete it.

Your rights and how to use them

Under the GDPR you may access, correct, delete, restrict and port your data, and object to processing. In the app:

• Access and portability: Settings, Export and backups (JSON or CSV).
• Deletion: Settings, delete your data or delete your account.
• Withdraw bank consent: Bank connections, disconnect.
• Withdraw AI consent: Settings, Privacy and consent.
• Correction: edit any transaction, category or payee directly.

For anything else, including restriction or objection, email us; we reply within one month. You may also complain to the Swedish Authority for Privacy Protection (Integritetsskyddsmyndigheten, IMY), or to your local data-protection authority.

Children

Perfin is not intended for anyone under 16 and we do not knowingly process their data.

Changes

We may update this policy when Perfin or applicable requirements change. The current version is published here with its revision date, and material changes will be highlighted in the app.