This service is a calculator and guide site, not an account-based personal finance product.
Basic use does not require an account, banking credentials, or uploaded financial documents. Amounts entered are used for the calculation experience rather than for building a personal-finance profile.
Technical request data such as IP, browser type, request path, and error logs may still exist at the hosting or security layer.
The site may use Firebase Analytics-style events, Google AdSense for advertising, and Cloudflare Insights or similar performance tools.
Those providers may rely on cookies, local storage, browser identifiers, and advertising-request metadata depending on region and consent choices.
Advertising and analytics providers may use cookies or similar storage, and consent messages may appear where required by law. Some choices can be adjusted again through browser controls or provider messaging.
Where GDPR, CCPA, or similar rules apply, users may have rights related to access, deletion, withdrawal of consent, or ad-personalization limits. Contact: hdchae89@gmail.com.
When a user follows an external link or interacts with an embedded advertising area, the destination provider may apply its own privacy and cookie rules.
In practice, users need more than a statement that cookies exist. They need to know which tools are active, what browser controls are available, and where personalization choices can be changed again.
That gives the privacy page a practical role in addition to its legal role.
A small site does not automatically deserve a short privacy page. In fact, once advertising, analytics, cookies, browser storage, and regional regulation are all involved, the practical explanation often needs to be more explicit, not less.
That makes the privacy page both a legal document and a user guide. It should help readers understand what can be controlled directly, what belongs to third-party providers, and where they may need to revisit consent or browser settings.
The clearest way to understand a site with advertising and analytics is to separate what the site itself handles from what external providers handle.
Without that split, it becomes hard for users to identify the real control points for privacy and consent.
Can privacy questions be sent to the contact email
Yes. Privacy and cookie questions can be sent to hdchae89@gmail.com, although some answers may also require third-party provider policies.
Why does the privacy page talk about ads and analytics together
Because both can touch browser identifiers, cookies, and request metadata from the user point of view. Their purposes differ, but their practical control points often overlap.
Why does the privacy page talk about browser settings too
Because some meaningful privacy controls live in the browser and third-party provider layer rather than inside the site itself. Users need both the policy explanation and the practical control path.
Tax and customs outputs are estimates for comparison, not final filing or settlement values.