Last updated: August 3, 2026
Cookies vs. browser storage
A cookie is a small piece of data a site asks your browser to send back on later requests. localStorage is different: it is a browser storage area that site JavaScript can read and write, but which is not automatically attached to website requests. Bank File Flow distinguishes between these technologies because they have different privacy effects.
Cookies currently in use: none
As of the date above, Bank File Flow does not set any cookies of its own. No analytics or advertising identifier is configured, so those services do not load and do not set cookies through this site. If that changes, this page will be updated before the change takes effect.
Browser storage used by the public site
The current public conversion workflow does not need to store statement rows, transaction descriptions, PDF passwords or generated CSV data in localStorage. The site reserves a preference key for the optional-services choice described below, but that choice is not requested or written while no optional service is configured.
Preference storage: the "optional services" choice
If analytics or advertising is configured in the future, a banner will ask whether you allow optional services. The answer would be stored in localStorage under the key bft_optional_services so the site can remember that choice. Optional services are not loaded on file-conversion tool pages regardless of that preference.
Analytics cookies — not currently active
No analytics identifier is configured on this site today, so no analytics cookie or script is loaded. If an analytics service is enabled in the future, it would load only after the consent choice above and only outside file-conversion pages. This policy would be updated first to name the service in use.
Advertising cookies — not currently active
No advertising network is configured on this site today, so no advertising cookie is set. If Google AdSense or a similar network is enabled in the future, third-party advertising cookies, web beacons, or similar identifiers may be used to provide personalized or non-personalized advertising, subject to the consent controls described in the Privacy Policy. You would be able to manage personalized-advertising settings through the advertising network's own controls at that time.
First-party and third-party technologies
Any preference stored by the current site code is first-party browser storage. A future analytics or advertising integration could involve third-party scripts and cookies set by that provider. This page will name a provider only when one is actually configured.
Controlling cookies and storage in your browser
You can view, block or delete cookies and site storage at any time using your browser's own settings, usually under Privacy or Site Settings. Clearing site data also removes any optional-services preference previously saved for this origin.
Revisiting your consent choice
Where the "Privacy choices" control is shown in the site footer, you can reopen it at any time to change your optional-services preference. It is hidden automatically when no optional service is configured, since there is nothing to choose between.
Changes to this policy
We will update this page, and the "Last updated" date above, before enabling any cookie or storage use that isn't already described here.