Current status: This policy describes the data behavior verified in BuildQuantities’ public static source on 30 July 2026. The site is hosted through Hostinger. The public operator identity, launch markets, exact hosting-log practices, and jurisdiction-specific legal review remain pending.
Current browser behavior
Calculator inputs are processed by JavaScript in the active browser page. The current calculator code uses those values to display results and does not send them to a BuildQuantities server.
The active source contains no code that sets cookies or saves calculator inputs in localStorage or sessionStorage. Refreshing or leaving the page clears the active calculator state, apart from values a browser may preserve through its own form or navigation behavior.
Services present in this build
| Feature | Current status | Required before activation |
|---|---|---|
| Calculator processing | Runs in the active browser page | Keep network and storage behavior documented when calculator code changes |
| Accounts and sign-in | Absent | Identity, access, security, retention, deletion, and support policy |
| Contact submissions | Absent | Fields, purpose, delivery provider, access, retention, deletion, abuse controls, and confirmation |
| Analytics and session measurement | Absent | Provider, events, identifiers, purpose, retention, sharing, regional controls, and visitor choices |
| Advertising and affiliate tracking | Absent | Partners, identifiers, cookies or storage, disclosures, consent controls, and opt-out routes where applicable |
| Third-party embeds and external fonts | Absent | Provider requests, transferred fields, purpose, retention, and fallback behavior |
Hosting and request logs
The public site is delivered through Hostinger. Web hosting and content-delivery systems may process request information such as an IP address, request time, requested URL, browser or user-agent data, response status, and security signals to deliver and protect the site.
The repository does not establish the exact fields Hostinger retains for this account, who can access them, how long they remain, or every processing location. Those account-level details must be verified before this policy is treated as a complete legal notice.
How future data collection will be reviewed
- Identify the exact visitor or operational purpose.
- List every collected or derived field and its source.
- Limit collection to the fields needed for that purpose.
- Record processors, recipients, storage locations, access roles, and security controls.
- Set retention and deletion rules before collection starts.
- Provide required notice, choice, consent, and request routes for the applicable markets.
- Test the rendered controls and update this page before enabling the service.
Privacy requests and contact status
A public privacy-request channel remains pending with the general contact route. The final process will identify the operator, available request types, verification steps, response handling, and applicable jurisdictional scope. The contact page records the readiness gate.
Policy updates
The page date and service table will change before a new collection feature goes live. Material changes include a hosting or logging change, analytics, advertising, affiliate tracking, embeds, accounts, saved calculations, forms, payments, or a new public market.
Guidance used for this policy
Review boundary: These sources support data inventory, minimization, protection, and risk-management practices. The launch policy still needs review for the final operator, vendors, features, and applicable jurisdictions.