Privacy Policy

This policy explains what FinSage (finsageguide.com) stores, what third parties are involved, and what choices you have. It describes how the site's code actually behaves today. If the site's behaviour changes — most importantly, if advertising is switched on — this page is updated before the change goes live, with a new date at the top.

Who runs this site

FinSage is an independent personal project operated by pasindu.nbuss. There is no company and no postal address; email is the contact channel for everything, including privacy questions: pasindu.nbuss@gmail.com.

What FinSage does not collect

The site is static and has no accounts, no login, no sign-up, no newsletter and no contact form. It does not ask for or collect your name, email address, phone number, postal address or payment details anywhere, and it operates no visitor database of its own.

Everything you type into a calculator — income, loan amounts, savings, ages, insurance figures — is processed entirely inside your own browser and is never transmitted anywhere. It is not stored, not logged and not seen by anyone, including the site owner.

What is stored on your device

FinSage uses your browser's local storage (not cookies) for three things. Local storage stays on your device; it is not sent to any server.

You can delete all of it at any time through your browser's “clear browsing data / site data” settings for this site. Nothing breaks — the site simply forgets your theme and re-fetches prices.

Live market data and our proxy

Prices for cryptocurrencies, the tokenised gold proxy (PAX Gold) and currency exchange rates are not fetched by your browser from the data providers directly. Your browser requests them from this site's own endpoints (/api/crypto and /api/rates), which run as serverless functions on our hosting provider and call the upstream providers server-side:

• CoinGecko — crypto and PAX Gold prices (privacy policy)
• open.er-api.com — daily currency exchange rates (terms)

Because the call is made by our server, those providers do not receive your IP address, your browser details or any information about you — they see one request from our infrastructure that serves all visitors. The requests contain no personal data and are identical for everyone. Responses are cached (about 90 seconds for crypto, up to 6 hours for exchange rates).

Hosting and server logs

The site is hosted on Netlify. Like every web host, Netlify processes the technical information your browser necessarily sends to deliver a page — IP address, requested URL, user agent, timestamp — and may retain it in server and CDN logs for operations, security and abuse prevention. This is standard infrastructure processing, not analytics run by FinSage. See Netlify's privacy policy and its GDPR/CCPA information.

Analytics

FinSage runs no analytics product — no Google Analytics, no tag manager, no pixels, no heatmaps, no fingerprinting and no cross-site tracking of any kind. If that ever changes, this page will say so before it is introduced.

Advertising

Current status: no advertising is running on this site. No advertising account has been approved, no publisher ID is configured, no advertising script is loaded, and no ad units or empty ad placeholders appear anywhere on the site. Nothing in this section is active today.

The intention is to fund hosting through Google AdSense in future. This section describes what will happen when it is switched on, so the position is clear in advance; it will be updated to describe the live behaviour at that time.

• Consent gate. No advertising script will load until you accept advertising cookies in the banner. If you decline, or ignore the banner, no advertising script is requested and no advertising cookies are set.
• What Google would do. Google and its partners use cookies and similar technologies to serve ads, limit how often you see the same ad, measure performance, and — where permitted and consented to — personalise ads based on your prior visits to this and other websites. Google's use of advertising cookies is described in How Google uses cookies in advertising and its Privacy Policy. That processing is governed by Google's policies, not this one.
• Third-party vendors. AdSense may involve additional advertising networks, exchanges and measurement vendors, each of which may set its own cookies and operate under its own privacy policy. Google publishes the list of its advertising partners here.
• Personalised vs non-personalised ads. Personalised ads use data about your browsing to choose what to show. Non-personalised ads are based only on rough context such as the page content and approximate location, though they still use cookies for frequency capping, fraud prevention and aggregated reporting. Declining consent means non-personalised ads at most — and in the current configuration, no ads at all.

How to control or opt out of personalised advertising

• On this site: click “Cookie choices” in the footer of any page to change or withdraw your consent at any time, or decline the banner in the first place.
• Across Google services: manage or turn off ad personalisation at Google My Ad Center (formerly Google Ads Settings) — this applies to your Google account across sites and devices.
• Across many networks at once: YourAdChoices (DAA), the NAI opt-out, and in Europe Your Online Choices.
• In your browser or device: block third-party cookies, use private browsing, or use your operating system's ad-tracking limits (for example iOS App Tracking Transparency, Android's advertising ID reset).

Cookie consent — what our banner does, and its limits

The banner you see on your first visit is a simple, self-hosted accept/decline gate. It records your choice in local storage on your own device and controls whether any advertising script may load. Being open about its limitations:

• It is not a Google-certified Consent Management Platform, and it does not implement the IAB Transparency & Consent Framework. It generates no TCF consent string — deliberately, because a fabricated one would be worse than none.
• It does not detect your location, so everyone sees the same banner, and it does not offer granular per-purpose or per-vendor choices.
• It is not claimed to satisfy any particular law in any particular country.

Google requires a certified CMP for ads served to users in the EEA, the UK and Switzerland. Before advertising is enabled here, a Google-certified CMP (such as Google's own Privacy & messaging tool in AdSense) will be configured for those regions, and this section will be rewritten to describe what is actually running.

Children's privacy

FinSage is a general-audience educational site, is not directed at children, and does not knowingly collect personal information from anyone — including children. If advertising is introduced it will be configured as a general-audience, non-child-directed site.

Your rights

Depending on where you live, data-protection law may give you rights to access, correct, delete or restrict processing of personal data about you, or to object to it. In practice FinSage holds essentially nothing about you: there are no accounts, no forms and no visitor database, and the material stored by the site sits in your own browser where you can delete it yourself. Requests relating to host-level logs may need to be directed to Netlify, and requests relating to advertising data to Google, since each acts as controller of its own processing.

To ask a question or make a request, email pasindu.nbuss@gmail.com with “Privacy” in the subject line.

Changes to this policy

If the site's data handling changes, this page is updated and the “last updated” date at the top is changed. Material changes — in particular switching advertising on — will be reflected here before they take effect.

Contact

Questions about this policy: pasindu.nbuss@gmail.com. See also the contact page, the terms of service and the disclaimer.