CFO AI · Română

Privacy Policy

Last updated: 17 November 2026

1. Who we are

This policy describes how personal data is processed in connection with the CFO AI platform at cfo-ai.io.

PARACHAIN CAPITAL S.R.L.
Registered office: Intrarea Bitolia nr. 32, Sector 1, Bucharest, Romania
Company registration number (CUI): 45298544
Trade Register number: J2021021081405
Email: privacy@cfo-ai.io

We refer to ourselves in this document as "CFO AI", "we" or "the Company".

2. The two roles in which we process data

The distinction below is essential to understanding this policy.

We are the CONTROLLER of your account data: your name, email address, billing details, platform usage logs and your correspondence with us. We process this data in order to provide the service to you.

We are a PROCESSOR for the financial documents you upload. If you are an accountant or adviser uploading trial balances, financial statements or other documents belonging to your clients, you (or your client) remain the controller of that data. We process it solely on your instructions, for the purpose of producing the financial analysis you requested.

Using the platform for your clients' documents constitutes a data processing agreement between us, on the terms described in this policy and in the Terms of Service.

3. What data we process

Account data: first and last name, email address, preferred language and currency, account settings.

Authentication data: if you sign in with Google, we receive the email address and name associated with your Google account. We never receive or store your Google password.

Uploaded documents: for the three features — My subscriptions (a person's or a company's bank or card statements), My financing (a bank score, from a company's trial balance or a person's statements) and Financial analysis (a company's trial balance) — trial balances, financial statements, sales files and other accounting documents, and bank or card statements (their dates, amounts and transaction descriptions), together with the values read from them and the analyses generated. The file itself is deleted as soon as its analysis ends (section 7).

Billing data: if you purchase a subscription, payment data is processed directly by Stripe. The one-time payment for Clean Wallet is processed the same way, by card on Stripe's page, and its receipt and invoice are sent to you by email. We do not store your card details on our servers.

Technical data: IP address, browser and device type, time of access, pages visited and errors encountered. We use this for security, diagnostics and improving the service.

Visit records (our own, never a third party): for every visit we record, on our own server, where the visitor came from (the ad campaign and keyword or the UTM tags of the link, whether the link carried a Google or Facebook click identifier — never its value — or the site that linked to us), the country and city derived from the IP address at the moment of the visit (the IP address itself is not stored), a keyed one-way fingerprint of a random identifier stored in the browser, the device type (phone, tablet or computer), the language, the pages opened and the actions taken (the steps on the way to an upload — scrolling the page, touching the upload box, choosing a file, opening the sample or the bank guide, asking for the link by e-mail —, an upload and its result, a cancel link opened, a result shared, a video of the home page opened). If you are signed in, the record is linked to your account. We use it to understand which channels bring visitors and where the product fails. It stays on our server, is never sold and is never sent to a third party, so it is recorded whether or not you accept cookies; it is kept for 13 months (section 7). The country and city come from a database stored on our server: IP Geolocation by DB-IP (https://db-ip.com), licensed CC BY 4.0.

Usage and ad-measurement data (only with your consent): if you accept the statistics or advertising cookies, Google receives the pages visited, the browser and device type, the Google ad that brought you to the platform and the steps taken afterwards — an upload, a result shown, an account created, a payment, with its plan and price. It does not receive your files, your figures, your name, your email address or your tax identification number. With your consent to advertising, Meta and TikTok receive the conversion data described in section 6.

Correspondence you send us by email or through in-app forms.

The link sent by email ("E-mail me the link"): if you ask us, on our first page or on an upload page, to email you the link, we use the address you type once, to send you that single email, through Resend (section 6). We send it only after you tick the consent box. We do not store the address, add it to any list or subscribe you to anything. So that the same link is not sent repeatedly, our server keeps, in memory only and at most until the end of the day (UTC), a keyed one-way fingerprint of the address.

Free without an account: a visitor can upload a trial balance (any file: Excel, PDF, CSV, a scan or a photo) or bank / card statements (PDF, Excel, CSV, another export from the bank's, card's or wallet's app, or a photo or screenshot of the transactions) from our first page and have them analysed without creating an account — in 30 days, up to 10 bank statements per visitor and up to 5 trial balances per visitor and per company. Your file is not stored: we read it, calculate, then delete it. Without an account, the results are kept for 30 days. A bank or card statement is also read by an Anthropic model, as a second check; a trial balance in a layout we know is read only by our code, and one in a new layout is read by an Anthropic model and checked figure by figure by our code (section 5); the providers that process data for us are listed in section 6. We process the file only while it is analysed, the company identification read from it (name and fiscal code), the values computed and the analysis generated, under a temporary anonymous session stored in the visitor's browser. No name or email address is asked for. The analysis is produced automatically by our software, as section 5 describes; it can be opened only from the browser that uploaded the file and is not published or listed anywhere. To apply these limits (per company, per file and per visitor), and to limit abuse, we compute keyed one-way fingerprints of the fiscal code, of the file, of a random identifier stored in the browser, and of the network (IP) address. A fingerprint cannot be read back into the value it was computed from.

4. Why we process it, and on what legal basis

PurposeLegal basis (Art. 6 GDPR)
Providing the platform and generating analysesPerformance of a contract
Creating and administering your accountPerformance of a contract
Billing and collectionPerformance of a contract; legal obligation
Retaining our own accounting and tax recordsLegal obligation
Platform security, abuse prevention, access logsLegitimate interest
Improving the product using aggregated, anonymised dataLegitimate interest
Visit records: where visitors come from and where the product fails (section 3)Legitimate interest
Marketing communicationsConsent (withdrawable at any time)
Sending, at your request, a single email with the upload linkConsent
Usage statistics (Google Analytics 4) and measuring Google ads (Google Ads), Meta ads (the Meta pixel and Meta's Conversions API) and TikTok ads (the TikTok pixel and TikTok's Events API), through cookies and from our serverConsent (withdrawable at any time)

Processing of your clients' financial documents is carried out on your instructions, in our capacity as processor (Art. 28 GDPR).

5. Artificial intelligence and model training

We consider this section essential and state it without ambiguity.

Your financial data is not used to train artificial intelligence models — neither by us nor by our providers.

The platform uses language models provided by Anthropic to write plain sentences about results our deterministic engine has already computed: the briefing, the bank-score sentences and the answers of Ask CFO AI. The model receives the computed figures. No uploaded file, and no text, row or account name read from a file, is sent to a language model, with the five exceptions below. Numerical computation is performed by our deterministic engine, never by the language model. Transmission goes through the commercial API, which does not use submitted data for model training. Anthropic is the only artificial-intelligence provider that receives data from the platform.

Ask CFO AI: when you ask a question, your question is sent to the model together with the computed figures of the company you have open, its name and the period.

My subscriptions (bank and card statements): for each recurring charge whose merchant our list of services does not recognise, only the merchant's text from the statement line is sent to the model, so that it can give the merchant a clean name and a category. Before it is sent, every digit, account number (IBAN), card number, e-mail address and reference is removed, and a line that could name a person (for example a transfer to someone) is not sent at all. All such merchants of one analysis go in one request. In this naming request, amounts, dates, account details and the bank's name are never sent.

The shared merchant dictionary: the clean name and the category the model gives a merchant are kept in a dictionary shared by all users, so that the same merchant is never sent twice. It holds only the cleaned merchant text, its name, its category and whether it is a subscription — nothing that links to any user, account or statement.

Bank and card statements are read twice (My subscriptions and the personal bank score): every statement is read independently by our parser and by an Anthropic model, which receives the statement file itself — its dates, amounts, descriptions and printed balances — through the commercial API, which does not use it for training. The two readings are compared transaction by transaction and checked against the balances the statement prints; every figure is still computed by our engine, only from the transactions both readings confirm. If neither reading checks against the balances, no figure is shown and the statement is checked again. We do not store the statement file: it is deleted after the analysis.

A bank or card statement is read as described above in whatever form you upload it — a file, a scan, a photo or a screenshot. Trial balances (Financial analysis, Company financing): a trial balance in a layout we know is read only by our code. A new layout is read by AI (Anthropic), and our code checks every figure: debits equal credits and, for every account, the opening balance plus the movements equals the closing balance. The file is deleted after the analysis. The model receives the trial balance file — in any form, a scan or a photo included — through the commercial API, which does not use it for training; every figure is still computed by our engine, only from the rows our code has proven, and the analysis is marked “AI-read”. A file uploaded as a trial balance that our code does not recognise is read this way also to learn whether it is a trial balance; if it is not, it is not analysed. If the figures cannot be proven, no figure is shown, and the file is kept encrypted until a person on our team has finished checking it, then deleted. The last exception is a trial balance from another country (Multi-Country): it can only be read by a language model, so that file is sent to Anthropic to be read, through the commercial API, which does not use it for training; the result is marked “AI-read” and every figure is still computed by our engine. We do not store the file afterwards.

6. Who we share data with (sub-processors)

ProviderRoleLocation
SupabaseDatabase, authentication, file storageEuropean Union
AnthropicLanguage model processingUnited States
StripePayment processingEuropean Union / United States
Infrastructure hosting providerApplication serversEuropean Union
Resend (transactional email provider)Authentication and notification emails, product news to those who subscribed, and the single email with the link, sent on requestEuropean Union / United States

What Stripe receives: when you start a checkout, your email address and an internal account identifier; on Stripe's own page, the payment details you enter there and, where the checkout asks for them, your billing name, address and tax identification number. We receive from Stripe the status of the payment and of the subscription, never your card number. Invoices are transmitted to the Romanian tax authority (ANAF) through RO e-Factura where Romanian law requires it.

Transfers to providers outside the European Economic Area are made under the Standard Contractual Clauses approved by the European Commission.

Google, only with your consent: Google Ireland Limited (Gordon House, Barrow Street, Dublin 4, Ireland) receives the usage and ad-measurement data described in section 3, through Google Tag Manager, Google Analytics 4 and Google Ads, only if you accept the statistics or advertising cookies. The data may also be transferred to the United States. We do not use personalised advertising or remarketing. You can withdraw your consent at any time (section 10).

Meta, only with your consent to advertising: Meta Platforms Ireland Limited (Merrion Road, Dublin 4, D04 X2K5, Ireland) receives, through the Meta pixel in your browser and from our server through Meta's Conversions API, which page you visited and that an upload, a result shown, an account creation or the Clean Wallet payment (with its price) happened, so we can measure our Facebook and Instagram ads. With each event our server also sends your IP address and your browser's identification (its user agent), which Meta uses to match the event and which we do not store — for a payment they are held in our server's memory for up to 24 hours, only to send the purchase once the payment is confirmed, then dropped —, Meta's own cookies (_fbp, _fbc) when your browser holds them, and — only if you are signed in to an account, or for a payment the e-mail address you gave at checkout — your e-mail address in a one-way hashed form (SHA-256), never in clear. Meta never receives the file, its figures, your name or your tax identification number. Without your consent to advertising nothing is sent to Meta, neither from your browser nor from our server. Meta keeps this data for the periods its own policy states. The data may also be transferred to the United States. You can withdraw your consent at any time (section 10); from then on nothing more is sent to Meta.

TikTok, only with your consent to advertising: TikTok Technology Limited (10 Earlsfort Terrace, Dublin, D02 T380, Ireland) receives, through the TikTok pixel in your browser and from our server through TikTok's Events API, exactly what Meta receives above, for the same purpose — to measure our TikTok ads: which page you visited and that an upload, a result shown, an account creation or the Clean Wallet payment (with its price) happened; with each event our server sends your IP address and browser identification, which we do not store (for a payment held in our server's memory for up to 24 hours, then dropped, as for Meta), TikTok's own cookie (_ttp) when your browser holds it, and — only where Meta receives one — your e-mail address in a one-way hashed form (SHA-256), never in clear. TikTok never receives the file, its figures, your name or your tax identification number. Without your consent to advertising nothing is sent to TikTok, neither from your browser nor from our server. TikTok keeps this data for the periods its own policy states; it may be transferred outside the European Economic Area under TikTok's own safeguards. You can withdraw your consent at any time (section 10); from then on nothing more is sent to TikTok.

We do not sell your data. We do not make it available to data brokers; the advertising networks Google, Meta and TikTok receive only the measurement data above, with your consent.

We may disclose data where required by law, in response to lawful requests from competent authorities.

7. How long we keep data

Account data: for the life of the account and 30 days after its deletion.

Uploaded files: a file you upload is deleted as soon as its analysis ends; we do not keep it. While a bank or card statement is being read it is held encrypted, so that a restart of our servers does not lose it. If a statement cannot be read automatically, the file is kept encrypted only until a person on our team has checked it, and is deleted when that check ends; that person may open the file for the check, and nobody else can; a visitor without an account may leave an e-mail address for that check, which is kept only for that case and deleted when it closes. Likewise, a trial balance whose figures could not be proven is kept encrypted only until a person on our team has finished checking it, and is deleted then.

Trial-balance analyses in an account (the values read and the analyses generated): until you delete them or delete your account. We delete them permanently within 30 days of the request.

Bank-statement analyses (My subscriptions, the personal bank score): deleted automatically 30 days after the analysis.

Subscriptions you mark as cancelled (My subscriptions): when you mark a subscription “I cancelled”, “Ends on…” or “I moved to a cheaper plan”, we keep in your account only the service, the amount and the date — and beside them what you chose: cancelled, the date it is paid until or the new plan's price, and whether it is yours or which company's — to show you what you saved and to check on your next statement that the charge stopped. We use them for at most 13 months from that date; an older one is deleted at your next change of these decisions. They are deleted with your account (without an account, with the anonymous session).

The link sent by email: we do not store the address; its fingerprint is held only in our server's memory, at most until the end of the day (UTC). Resend, which delivers the email, keeps its own record of the send under its own policy.

Billing data: 10 years, as required by Romanian tax and accounting law.

Technical and security logs: up to 12 months.

Visit records (where a visit came from, its country and city, the device's fingerprint, the pages and actions): 13 months.

Advertising events sent to Meta and TikTok: we keep only a random identifier of each event, its name, its time and whether it was sent, for 35 days, so that the same event is never sent twice, and — for a send that failed — the network's own error code and message; no IP address, no browser, no e-mail address.

Backups: up to 35 days, after which they are overwritten in the normal rotation cycle.

Free without an account: the uploaded file is deleted right after its analysis. Access to the results ends 30 days after the free period started, and the results and the anonymous session are then deleted automatically — normally within hours — unless an account was created from that browser in the meantime. If an account is created, the results are kept in that account and the periods above apply. After the deletion we keep only the fingerprints: those of the company's fiscal code and of the file without a time limit, so that the free limits apply per company and per file; that of the browser identifier for up to 180 days after it was last used; that of the network address for up to 30 days. Copies in backups and entries in technical logs follow the periods stated above.

8. Your rights

As a data subject you have the right of access, rectification, erasure, restriction of processing, data portability, objection to processing based on legitimate interest, and the right to withdraw consent where processing relies on it.

You can exercise these rights by writing to privacy@cfo-ai.io. We respond within 30 days at the latest.

You can delete your account directly in the application, under Settings. Deleting your account deletes the analyses of the documents you uploaded (the files themselves are not kept after their analysis).

If you believe your data is being processed unlawfully, you have the right to lodge a complaint with the Romanian National Supervisory Authority for Personal Data Processing (ANSPDCP), B-dul G-ral. Gheorghe Magheru 28-30, Sector 1, Bucharest, www.dataprotection.ro.

9. Security

We apply appropriate technical and organisational measures: encryption in transit (TLS), encryption at rest, role-based access control, database-level isolation between accounts, access logging and automated security checks in our development process.

No system is absolutely secure. In the event of a personal data breach posing a risk to the rights and freedoms of data subjects, we notify ANSPDCP within 72 hours and, where the law requires it, inform the affected individuals.

10. Cookies

Our use of cookies is described in the Cookie Policy. Statistics cookies (Google Analytics 4) and advertising cookies (Google Ads, the Meta pixel, the TikTok pixel) are set only with your consent, asked for on your first visit; the legal basis is consent. You can change or withdraw your consent at any time, from the "Cookie settings" link in the footer of every page or under Settings; withdrawal does not affect processing carried out before it.

11. Minors

The platform is intended for professionals and legal entities, and for individuals who use My subscriptions or My financing for their own bank statements. We do not knowingly collect data from anyone under 16.

12. Changes

We may update this policy. We will communicate substantial changes by email or through a visible in-app notice at least 15 days before they take effect. The version in force is always the one published at this address, with the update date shown at the top.

13. Contact

For any question about data processing: privacy@cfo-ai.io

PARACHAIN CAPITAL S.R.L., Intrarea Bitolia nr. 32, Sector 1, Bucharest, Romania

Terms · Cookies · Home

Version of 17 November 2026 · reference 908032a0d24b
PARACHAIN CAPITAL S.R.L. · CUI 45298544 · J2021021081405
Intrarea Bitolia nr. 32, Sector 1, București, România
Privacy · Terms · Cookies · contact@cfo-ai.io