PILOT · ENGLISH TRANSLATION OF THE 17 SEPTEMBER 2026 NOTICE, WITH SUBSEQUENT FEATURE UPDATES · LANGUAGE PREFERENCE ADDED 21 SEPTEMBER 2026
Files, data and cookies.
Privacy notice still being completed. This page describes how the pilot works technically and does not replace the operator's complete privacy notice. The operator is identified below; the list of providers, the legal arrangements for processing and retention periods for supporting systems are still being completed. At this stage, use the fictional examples or documents that are genuinely anonymous.
Who operates FormaGo
FormaGo is a service of SIA Network Operations Center, a limited liability company registered in Latvia, registration number 40103960010, EU VAT number LV40103960010.
Registered address: Rīga, Elijas iela 21, LV-1050, Latvia. For support and personal data requests: contact@formago.eu. Mention “FormaGo” in your request, without attaching bank statements or banking data.
The company operates the website, accounts and support as a controller for its own purposes. For conversions carried out on behalf of professional customers, it acts as a processor or subprocessor according to the actual roles and the applicable agreement.
What happens to uploaded files
The file is sent to the server over HTTPS to extract or read transactions. Processing takes place on the service's server: the converter does not send the document to external conversion or artificial intelligence services, does not use it to train models and does not create an archive of converted documents. Account technical history is described separately below.
The uploaded PDF, CSV, XLSX, CAMT.053 XML or MT940 TXT file and intermediate output are temporary and are removed when extraction ends, including after a handled error. Extracted tables are available for 10 minutes and removed from memory within the following 30 seconds. Use Delete document to remove them sooner; a successful new upload replaces the previous one in the same session.
An abnormal interruption may leave temporary files until the service next starts or the container is recreated. The architecture does not guarantee physical deletion from any infrastructure copies: the operator must verify server snapshot, backup and administration arrangements.
For CAMT.053 and MT940 exports, you may enter an IBAN, statement number, balance dates and balances. These details are sent over HTTPS with the export request and processed in memory to generate and check the file. Manually entered export details are not saved to your account profile, operation history or document job. When importing CAMT.053 or MT940, account and balance details read from the file are held in the same temporary in-memory job as its transactions, for the same 10-minute lifetime, to prefill the export form. The form is cleared when the document is deleted, replaced or expires; downloaded files remain on your device.
Server location
The pilot server is at Avalon Campus in Milan, Italy. Hosting is managed by the same SIA Network Operations Center that provides the service. Information about any external infrastructure providers, remote access and copies still needs to be completed in the notice.
Data in your browser
The file name, tables and preview appear in your browser. The file name is not sent as upload metadata. Downloaded Excel, CSV, CAMT.053 XML and MT940 TXT files stay on your device; deleting data from the service does not delete those files. Use a personal browser profile: anyone sharing your profile may access the same session.
Technical cookies
The customer area uses __Host-formago_account: a random identifier with Secure, HttpOnly and SameSite=Strict, lasting at most 8 hours, including on the server. Signing out revokes the session; password changes and resets revoke all account sessions. Invitations and password resets are single-use; only the code's hash is stored on the server. The invitation link contains the code in the URL fragment, which is cleared from the address bar when opened.
The pilot uses the first-party cookie formago_pilot to separate sessions and protect document access. It contains a signed random identifier, without any extracted rows; it lasts at most one hour in the browser and is set with Secure, HttpOnly and SameSite=Strict. Password-based access may be remembered separately by your browser.
When you explicitly choose a customer-area language, formago_language remembers the selected language code (en, de, fr, es or it) for up to 30 days. It is a first-party preference cookie with Secure, HttpOnly and SameSite=Lax. It contains no account identifier and does not grant access. It helps keep your language when navigating the customer area or returning from payment.
No advertising cookies, profiling tools or browsing analytics are installed. Necessary technical cookies do not require separate consent here, and there is no acceptance banner.
Likes and sharing
The optional Like button records feedback about the converter. Only after you press it, the first-party formago_like cookie stores a random identifier for up to 30 days (Secure, HttpOnly, SameSite=Strict). The database stores its hash, creation time and expiry, without an account link, email, document or banking contents. Repeated clicks from the same recognised browser do not add votes; removing your like deletes the record and cookie. Expired records are cleaned within the following 30 seconds while the service runs. The converter publicly displays the total likes across all language pages. This aggregate number has no browser identifier and is retained after individual 30-day records expire. Removing a currently recognised like decreases the total. Previously expired and deleted votes cannot be reconstructed. Administrators also see the number of active likes. These are browser-based feedback counts, not verified counts of people. The existing pseudonymised network rate counters also limit repeated new likes.
Sharing buttons contain only a public converter URL and a general description. We do not include your uploaded file, document data, account identifiers or the current page's query parameters. No social-network widgets or tracking scripts are loaded. Clicking a sharing link opens the chosen provider, which then handles the connection under its own terms. Email and device sharing open a draft or chooser; you choose the recipient and confirm sending. We do not record sharing clicks or claim that a message was sent.
Accounts and technical history
Public registration uses email verification, per-network request limits and a hidden anti-spam field. The hidden field is not stored; filled submissions do not create an account or trigger an email. Verification attempts also use the existing pseudonymised network counters, retained for up to 24 hours. No third-party CAPTCHA scripts are loaded.
For an account we store the email address, password hash, selected use category, role, access status, creation date and last sign-in. For invitation-based accounts, the operator enters the email and proposed category; users may change their category. Unused invitation codes expire after 7 days; reset codes expire after one hour. Counters against repeated attempts use an email hash retained for up to 15 minutes. Public registration is described below.
For 90 days, history retains identifiers, timings, page and row counts, export format, layout recognition and warning or error codes. It contains no PDFs, file names, IBANs, transaction descriptions or transaction amounts. Authorised administrators can see customers, history and category summaries to support the pilot and assess its use; they cannot download your tables through the admin area. Access using the original pilot credentials may also generate technical metadata without an associated customer account.
From your profile you can export account data, change your password and delete the account and its history. If payment records exist, closure requires the operator's involvement to check which information may need to be retained. Profiles remain until closure; the operator must also define how inactive accounts are handled. Administrative invitation and access-management actions are recorded for 90 days. Periodic cleanup runs within 30 seconds of expiry while the service is running.
Payments
When the operator enables test mode, the customer area displays a button to open Stripe Checkout in test mode. No real amounts are charged: use test data only. The service sends Stripe a random order identifier, the synthetic amount in EUR, the selected package and test product name, without PDFs, transaction data or the account email address. Stripe also receives the data entered on its page and the technical data needed for the connection.
Test orders retain customer/order identifiers, amount, status, timings, Stripe session and payment references, any synthetic refund and event IDs/types. They do not retain card details, checkout URLs or complete webhook payloads. For Sandbox packages, we also retain a copy of fields from Stripe's test invoice: number, dates, name, email, address, tax identifiers, net amount, VAT, total and links to Stripe documents. Enter fictional billing data only in test checkout. These records are separate from real receipts, can be exported with the account and are removed after 90 days or on account closure; request counters expire after one minute. The test credit ledger (initial bonus, purchases, use and refund adjustments) remains until account closure to preserve the balance, without document contents. Sandbox credits cannot be transferred to a future paid service. Local deletion does not automatically delete data held by Stripe.
Real payments, when enabled, require an explicit purchase through Stripe. There are no automatic renewals. The register may include external payments entered by the operator: service amount, currency, reference, status and change history. Card details and banking credentials are not collected. This register is not an invoice and does not collect or refund money. Before commercial use, the operator must complete the terms, payment-provider arrangements, invoicing and retention periods. Records are not deleted automatically.
Profiles and metadata are saved in a persistent database on the Milan server and survive application updates. Deleting data from the active database does not guarantee removal from infrastructure snapshots or backups: the operator must define access, encryption and retention for these copies.
Service emails and operational notifications
If configured by the operator, service emails are sent to the account address following activation, a password update, or confirmation of a test payment or refund. Messages contain no passwords, recovery codes, PDFs or transaction data, and include no advertising or tracking pixels. Invitation and recovery links are still delivered personally by the operator. The configured SMTP service receives the recipient address and message contents. Administrators can also request a test email to their own account address to check delivery; the request is recorded in the administrative log.
The operator may enable payment alerts in a private operational Telegram group. These include the service name, random order identifier and service or refund amount. Tests are marked TEST. We do not send Telegram the customer's email or name, documents, IBANs or card data. Telegram still receives metadata required for delivery; these alerts are not banking documents.
For 90 days, the local queue retains the account association, type, channel, minimal event data, timings, attempts and delivery outcome. It is included in account exports and deleted with the account. Copies already sent or being delivered are not automatically removed from email, Telegram or recipients' systems. Before using these services with real personal data, the operator must complete the details of the actual SMTP provider and the communication services' terms, countries and retention periods.
Connection, support and rights
IP addresses and connection data are necessarily processed by systems delivering the website. The converter does not enable an HTTP request log; hosting-provider systems or other intermediaries may have their own logs, which must be described in the complete notice.
For pilot questions, use the channel through which you received your invitation. Report the error message without attaching bank statements, IBANs, credentials or other people's data. Do not upload documents revealing health, religious or political beliefs, or other special-category data without the necessary legal conditions.
For processing subject to the GDPR, rights of access, rectification, erasure, restriction, objection and portability apply where their respective conditions are met, as does the right to complain to a supervisory authority, particularly in the country of habitual residence, work or alleged infringement: in Italy, the Garante per la protezione dei dati personali; in Latvia, the Datu valsts inspekcija. You may contact the operator at the email address above.
Professional use
Processing customers' bank statements on behalf of a business or professional requires the privacy roles to be defined and, where applicable, a data processing agreement (DPA). Permission to upload a file and this page alone do not replace that agreement.
Real purchases and accounting retention
If you buy a package in the paid service, we process the data needed for the contract and accounting obligations: the order, acceptance of the terms, billing identity and address, tax identifiers, amounts, invoices, credit notes and adjustments. The bases are performance of the contract and legal obligations. Stripe handles payment; the website does not receive card details.
Closing the profile removes access and deletable operational data, but does not delete tax documents that must be retained. For records subject to OSS, the period is 10 years from the end of the year of the transaction; the controller handles any additional obligations or disputes. Access to accounting and backup copies is restricted. The operator reviews and deletes records when retention expires. We do not retain bank statements for these purposes.
Service messages may confirm real payments and refunds; Telegram alerts to the operator contain only the order identifier and service amounts.
Trial without an account and public registration
In public mode, you can convert without registering. Starting an upload sets the technical cookie formago_guest, with Secure, HttpOnly and SameSite=Strict, valid for 30 days. Merely visiting the page does not set it, and it is not used for advertising. The server stores the identifier's hash, number of trials used and expiry for up to 30 days. The trial includes two documents per browser during that period; used trials are taken into account when you create an account.
To limit abuse and overload, counters associated with an HMAC-pseudonymised network identifier are retained for at most 24 hours. For IPv6, the /64 prefix is used. The service database does not retain the plain IP address in these counters; this does not describe any infrastructure logs. Cookies and network limits do not reliably identify a person. Operations without an account retain the same minimised technical metadata for 90 days, without files or banking contents.
Registration requires an email address, password and use category. The email code expires after 20 minutes and is removed from the queue following successful delivery or expiry; a hash remains for verification. Unconfirmed registrations are removed after 24 hours. The verification email is transactional and does not subscribe you to marketing. Confirmed accounts follow the retention and closure rules above.
This description updates the technical behaviour; the operational parts of the notice and the agreements identified in the privacy documentation still need to be completed. Opening the interface is not GDPR certification.