Service and contact
This policy covers the free MLMProfitCalc calculator at mlmprofitcalc.com and its owner's separate MLMProfitCalc Research tool. The support contact is listed below. Last updated: 18 October 2026.
Financial calculations stay in your browser
The calculator does not send transaction amounts or product names to a server or add them to page URLs. Calculations run in your browser. The app has no advertising trackers, external fonts or AI requests. Visitors do not need a Google account or Google Ads permission to use the calculator.
Technical hosting requests
Your browser requests pages and files from Sites hosting infrastructure using OpenAI and Cloudflare. Hosting providers receive ordinary request information such as IP address, requested URL and browser headers, not your financial ledger. Provider policies also govern their technical logs and retention; we do not claim an unconfirmed log-retention period.
Device storage is optional
Without saving enabled, calculations remain in tab memory. Save on this device stores scenarios in this site's localStorage. Other people with access to the same browser profile may read them; this is not encrypted storage. Data does not move automatically between domains or devices.
Backups and deletion
JSON backups and downloaded reports contain your records. Treat them as personal documents. Disabling saving removes the localStorage copy but not the open calculation or downloaded files. Delete saved data affects this site only. Information you choose to email to support enters the email provider's system; do not send your financial ledger, passwords or tokens for an ordinary bug report.
What MLMProfitCalc Research is
This is a separate local tool used by the site owner to research search phrases and improve site content. It is not connected to visitor calculations. Google Ads API is not connected yet: OAuth authorization and a real metrics request have not been completed. The following sections describe the prepared workflow after explicit permission from the Google account owner.
Google access and requested data
The planned scope is https://www.googleapis.com/auth/adwords. This is broad Google Ads permission, not a server-enforced read-only scope. The prepared local code implements only GenerateKeywordHistoricalMetrics: it sends selected search phrases, country, language and an authorized Ads customer ID to Google, and receives aggregate historical metrics and phrase variants. It does not request Gmail, Drive, contacts, browsing history or private campaign performance, and it does not create or change ad campaigns.
Research use and storage
The purpose is search-demand research and improving MLMProfitCalc content. After authorization, OAuth tokens are stored locally in a Windows DPAPI-encrypted file under the owner's Windows account and sent to Google for authorized requests. The OAuth client JSON remains where the owner downloaded it. Local research reports contain phrases, parameters and aggregate metrics, not tokens or Ads customer IDs. Aggregate reports may be analyzed with an AI development assistant; visitor financial records are not part of those reports. Secrets are not published on this website or sent to chat.
Sharing, retention and revocation
Google API information is used only for the stated research, not sold or used for advertising targeting or training general-purpose models. Access is limited to the owner and explicitly authorized research participants. Reports and tokens remain until deleted by the owner. Data received from a person contacting support is deleted on request unless further retention is required. Google permission can be revoked through Google account connections. Deleting a local token file does not revoke permission, and revoking permission does not delete existing reports. Google API information use is limited to the disclosed purpose and Google API Services User Data Policy, including Limited Use.
Security and changes
User content is rendered as text, not HTML. JSON imports are validated before replacing scenarios, and CSV text cells are protected against formula injection. These measures are not a guarantee against all vulnerabilities. DPAPI does not protect against a process already running as the same Windows user. Material processing changes will be reflected here before taking effect; broader Google access requires separate consent.