MARKMA is a static site. Calculations run in your browser; there is no account or server-side storage of calculations.
Data processed by the site
The project does not request registration details or collect calculation input on a server: entered values are processed in your browser. The site does not ask for your name, phone number, email address or other identifying fields, so the amounts you enter are not linked to you. If you create a calculation link, its fragment contains the numbers you entered. Those numbers may be sensitive, so share the link only with people you trust.
Storage of calculation state
MARKMA calculators deliberately do not save the last calculation in localStorage or sessionStorage. State stays in page memory while the page is open and disappears when you reload it or close the tab. Copying a link is the only supported way to keep a calculation. Browser settings and consent are stored separately from calculations, and only when the site has a feature that needs them.
Analytics and error monitoring
Analytics is disabled unless explicitly configured. Without keys, no external requests are made and no SDK is loaded. If analytics is not configured, no analytics data is sent. When configured, analytics does not receive monetary values, calculation inputs or outputs, or full URLs containing calculation state. Events contain only the tool type, step, completion status and approved safe aggregate indicators. Error monitoring follows the same rule.
External counters and advertising scripts
The owner can connect third-party counters and automated advertising scripts through the site's local settings. The list is empty in the default installation, so no external requests are made unless an integration is enabled. An enabled integration runs as soon as a matching page opens; there is no separate consent window.
Third-party code is trusted owner code, not an isolated sandbox: technically it can read page content and its URL. MARKMA's own events still use the internal adapter and do not send entered or calculated values, personal information or full calculation URLs. For known counters, form recording and session replay must be disabled in the service's own settings. The owner checks each service before enabling it.
Sharing a calculation by link
Calculation state is encoded in the URL fragment after #, which is not sent to the server during an ordinary navigation. Calculation code runs in the browser. Links containing state are excluded from search indexing.
Anyone who receives a calculation link can see its values and open it. The fragment is not sent to the server by itself, but the values are no longer private once you share or publish the link.
Policy changes
The policy is updated, along with its review date, if the data processed or connected services change.