Plain-language summary
FinanceBase currently has no user accounts, contact form, newsletter, payment system, advertising network, or audience-analytics service. Calculator and screener inputs are evaluated in your browser and are not saved by FinanceBase. One first-party localStorage record remembers your privacy choices; optional analytics and advertising are off until you allow them.
The website is delivered through Cloudflare, which necessarily processes technical request and security information when you visit. Cloudflare’s role is explained below.
Information processed when you use the site
Calculator and screener inputs
Values entered into FinanceBase calculators and the stock signal screener are processed locally by JavaScript in the current page. The application does not transmit those inputs to a FinanceBase server or save them in cookies, localStorage, sessionStorage, or IndexedDB. Reloading or leaving the page resets the interactive state to the published defaults.
Privacy choices
The privacy control stores a record named financebase_consent_v1 in first-party localStorage. It contains a schema version, your analytics and advertising choices, the time of your decision, and an expiry time. It does not contain your name, email address, calculator values, or a cross-site identifier.
The record expires after 180 days, after which the site asks again. You can change or withdraw your choice at any time with the Privacy settings button in the footer. You can also remove the record through your browser’s site-data controls. Strictly necessary site delivery and security processing cannot be switched off in this interface.
Website and API requests
FinanceBase is hosted and protected by Cloudflare Pages and Cloudflare Pages Functions. When your browser requests a page, asset, or same-origin API endpoint, Cloudflare may process information such as your IP address, traffic-routing data, requested URL, request time, browser or system information, referring page, response status, and security signals. Cloudflare calls information made available through its services “Customer Logs” and may also derive network-level security and reliability data.
FinanceBase does not currently maintain its own visitor-profile database or add custom application logging statements to its data endpoints. Infrastructure processing and any provider-side retention are governed by the applicable Cloudflare configuration and Cloudflare Privacy Policy.
Data refreshes
Market, macroeconomic, and official-news cards include a complete, dated build snapshot. After the page loads and a card approaches the viewport, the browser may request a FinanceBase endpoint under /api/. That Cloudflare function retrieves public data from the U.S. Department of the Treasury, Federal Reserve Bank of New York, U.S. Bureau of Labor Statistics, or Federal Reserve Board. The browser does not send your calculator inputs or stored privacy choices with those requests.
Cookies, local storage, analytics, and advertising
The FinanceBase application currently sets no cookies and loads no advertising or audience-analytics scripts. Reserved ad spaces are inert placeholders: they contain no ad request, tracking pixel, iframe, or vendor code. Choosing “Accept all” records a preference but does not activate a service that is not present.
No future non-essential analytics or advertising service may load through the FinanceBase preference scaffold unless the relevant choice is active. Before any provider is activated, FinanceBase must publish the provider, purposes, storage technologies, retention, recipients, and any international transfers here. If an advertising platform requires a certified consent-management platform or an industry consent framework, this custom scaffold must be replaced or integrated with a compliant provider before ads go live.
Cloudflare may set strictly necessary cookies when particular security or traffic-management features are active—for example, to remember that a browser passed a security challenge or to distinguish automated traffic. Availability depends on the live Cloudflare configuration. Cloudflare documents the names, purposes, and durations of these cookies in its Cloudflare Cookies reference.
Why technical information is processed
Technical request information is processed as needed to deliver and cache pages, run the public-data endpoints, prevent abuse and malicious traffic, diagnose failures, and maintain the security and reliability of the service. FinanceBase does not use calculator inputs for these purposes because those inputs remain in the page.
External sources and links
FinanceBase links to primary sources and other reference sites. If you follow an external link, your browser contacts that third party directly, and its own privacy policy applies. A source link does not mean that the source sponsors or endorses FinanceBase.
Retention and security
Because FinanceBase currently accepts no accounts, form submissions, payments, or saved calculator scenarios, it retains none of those categories. The local privacy-choice record remains for up to 180 days unless you replace or delete it sooner. Technical request metadata may be retained by Cloudflare according to the enabled service, plan, account configuration, and Cloudflare’s policies. No Internet service can promise absolute security.
Privacy rights and questions
Depending on where you live, you may have rights concerning personal information, including rights to request access, correction, deletion, restriction, portability, or objection, to withdraw consent, and to complain to a data-protection authority. These rights can be subject to legal exceptions and may not apply when FinanceBase does not hold information that identifies you.
Use the Contact page or email etfnordic@gmail.com for privacy questions. Do not send sensitive financial records.
Children and policy changes
FinanceBase is a general-audience financial education site and is not directed to children. It does not knowingly collect personal information from children through an account or submission feature.
This policy will be revised before any material change such as adding accounts, saved scenarios, contact forms, newsletters, payments, advertising, or analytics. The date at the top will change when the policy changes materially, and consent will be requested again when a new schema version or materially different purpose requires it.