DCA FINANCE
Privacy and data storage
What DCA Finance uses and how to manage your data.
Without an account
The guest budget, ledger and DCA portfolio use browser localStorage. JSON export is available for moving data. Clearing site data removes local copies. Inputs in ordinary calculators are not retained after reloading the page.
Account and sync
Accounts store a name, email, protected password hash, session records, your budget and DCA portfolio: its plan, recorded orders, asset units, fees and notes. Budget and portfolio sync separately. Importing guest copies requires confirmation; conflicting versions are not automatically merged. The site and databases run on Cloudflare. Session cookies support sign-in and do not contain the transaction ledger.
Shared links
Anyone receiving a scenario link can read its parameters. The contents are shown before copying. Transaction descriptions and the full ledger are excluded.
Language preference
Homepage entry uses your browser language, without looking up your country by IP. Selecting EN/RU saves your choice in the dca_locale cookie for one year. Direct links to language versions remain accessible. Deleting the cookie resets the preference.
Public DCA results
Creating a DCA backtest link asks the server to verify the price series and store a snapshot in Cloudflare R2: asset, amount, frequency, dates, the full price series and method version. Anyone with the link can access it without signing in. The snapshot excludes your ledger, notes and account data. Clearing local data does not delete the public snapshot; contact the owner for deletion. A hash of the IP address is used to limit requests when creating links.
Assistant discussions and MCP
Discussion buttons provide the chosen service with the displayed prompt and links. Gemini, Claude, Grok and long prompts use copied text for manual pasting. Budget and portfolio summaries and fee-model context are reviewed and copied separately; their provider buttons open blank chats. Your screen, account and ledger are not automatically shared. The public MCP calculates supplied parameters and reads results by a provided ID without signing into an account; budget parameters are not saved. MCP request limits use the native Cloudflare rate limiter, keyed by a hash of the connecting IP; limits are approximate per Cloudflare location.
Visit analytics
Public pages use Yandex Metrica counter 114104485 with visit statistics, click maps, link tracking and Session Replay enabled. Metrica processes page, browser and interaction information and may use cookies and local identifiers. Personal dashboard content is marked as hidden from Session Replay. The counter initializes regardless of cookie availability; blocking cookies can affect visitor counts. Details: https://yandex.com/support/metrica/en/general/cookie-usage.
Tool action counts
A separate first-party counter stores only the UTC day, a fixed action name and a total count, such as CSV download or citation copy. It stores no amounts, assets, trade dates, notes, accounts, cookies, URLs or visitor identifiers, and works without cookies. IP addresses are used only in a short-lived in-memory request limiter, not in the count table. These are action counts, not unique people or verified investments. Custom Yandex goals receive only the static goal name, without parameters; they are disabled on URLs with query strings or unknown fragments. The existing Metrica visit tracking described above is separate.
Technical data and contact
Cloudflare and the sign-in system process request information, including IP and browser information, to operate and protect the service. For account data or deletion requests, contact the owner at vei96rus@gmail.com.