Your salary is private
Updated November 2, 2026.
The annual summary processes income, exemptions and personal deductions only in browser memory. These amounts are never stored or sent. Language changes preserve the entry; reloading clears the annual summary. Its controls do not send events containing financial data.
Calculation data and language switching
Your salary and deductions are processed in your browser. There are no accounts, databases or calculation APIs that receive these amounts. We do not save them in cookies, local storage, links or URL parameters. Switching between English and Spanish preserves your current inputs in memory only. Reloading resets the example. The default homepage is Spanish; English has its own URL.
Optional analytics: your choice
Analytics stays off until you choose “Allow analytics”. Before that choice, we do not load Google Analytics or Vercel Web Analytics, send events to our behavior service or create visit identifiers. Rejecting analytics does not limit calculations, comparisons, cards or downloads.
We store only your analytics choice in localStorage so it survives reloads, language changes and other tabs in the same browser. This preference does not contain an analytics identifier. If browser storage is blocked, your choice lasts only while this page is open. The control at the foot of the page lets you change your choice or withdraw consent without reloading or clearing your calculation. Withdrawal stops new measurements and removes local session and daily visitor identifiers. It does not automatically delete statistics already received. We also honor Do Not Track for all optional analytics.
Only after acceptance, Vercel Web Analytics receives visits to known public routes without URL queries or fragments. We use aggregate page, country and device statistics without analytics cookies. Vercel details.
Only after acceptance, Google Analytics receives page visits and predefined tool actions: calculation mode, period, region, language and rule version. We send no salaries, salary bands, deductions, results or entered text. analytics_storage, ad_storage, ad_user_data and ad_personalization remain denied: we do not enable Analytics cookies or personalized advertising. Enhanced measurement is disabled. We do not use Microsoft Clarity or session recordings.
Cookieless does not mean no data transmission: after acceptance, providers may process event signals, IP addresses and technical device information to deliver their services. See Google’s privacy policy.
Page and tool usage
Only after acceptance, our behavior analytics stores public page, language, source category, broad screen size, scroll depth and predefined actions in Supabase. We measure visible time and active time. Active time pauses when the page is hidden or after 60 seconds without interaction. Updates are sent every 15 seconds and when leaving; abrupt closure can leave incomplete measurements.
Random visit and tab-session identifiers are used without accounts, tracking cookies or browser fingerprints. The session is kept in sessionStorage and renewed after 30 minutes without observations. A separate random browser identifier is kept in localStorage for daily visitor counts. It is replaced on the next visit after the Mexico City calendar day changes and is removed when analytics is turned off. These tables receive no salaries, results, salary bands, phone numbers, photos, entered text, full URLs, IP addresses or user agents. Providers may process IP addresses and technical logs to deliver their services. Withdrawing consent using the footer control also disables this collection.
References for other pay periods are calculated locally. Opening that view sends only a predefined action and language to Google Analytics, without amounts. This action is sent only after accepting analytics.
The annual ordinary salary reference is also calculated in your browser. Its amounts are not stored or sent, and opening it does not add an analytics event. The result image is generated locally and includes this reference only if you have opened it.
Public visitor map
For new measured page visits, the server stores the country code supplied by the hosting platform, inferred from the connection location. No raw IP or precise location is added to these behavior tables. The map preserves the previously recorded figures and adds new measured visits from the subsequent collection period. It polls every 60 seconds with up to one minute of aggregate caching while the page is visible. New visitors are counted once per daily random browser identifier, with page views attributed to their first observed country. Returning on another day or during a different measurement period can count again. These cumulative browser observations are not lifetime unique people or a complete all-time audience. Coverage depends on storage, analytics preferences and successful delivery. Country aggregates remain after individual records expire. Supabase stores the aggregate records and supplies the map through the site server. New accepted visits update these records as they arrive. The map does not read its displayed statistics from repository JSON files. Daily JSON backups are saved in the project GitHub repository, alongside the separate 30-complete-day page-visit archive. No browser, visit or session identifiers, salaries, contacts or individual records are included in these public files. This collection requires explicit analytics acceptance and honors Do Not Track.
Hosting and advertising
The hosting provider may process IP addresses and access logs to serve and protect the site. These do not contain entered salary because it is not sent. This version loads no advertisements. A static Google AdSense ownership meta tag and a public ads.txt file identify the authorized publisher. These elements do not load advertising code or send entered calculation amounts. Future advertising integrations will require a review of providers, consent and this policy.
Professional card
Cards, profile photos and QR images are processed locally; files are not uploaded to the server. Names, contact details and other fields stay in memory, including during language changes. Reloading clears them. These fields are not sent to analytics. Downloaded images and copied text are under your control; review which details you want to share.