Understand planning-data privacy and security boundaries

Use the policy documents—not Help—as the authority for privacy promises

Financial planning involves sensitive information, and it is reasonable to ask who can access it, how imports work, what exports contain, and what happens after a deletion or access request. Help can explain the controls visible in YARCalc. The current Privacy Policy, Terms of Use, and Financial Disclosures govern the product’s actual commitments.

This distinction prevents Help from inventing reassuring claims about encryption, certification, backups, physical location, retention, sale, sharing, training use, GDPR, or CCPA that the deployed service and policy documents do not establish.

Use the security controls that match your concern

Use Account Settings to change credentials, enable multifactor authentication, and revoke sessions. Use a unique password and do not share authentication codes. If the concern is a privacy request, use the contact named in the current policy and send only the information needed to identify the request.

Holdings import processes the file you deliberately choose. It is not an ongoing brokerage connection and does not require a brokerage password. Review the preview and avoid uploading unrelated documents or unnecessary identifiers.

Before exporting or sharing a report, read what it contains and choose a secure delivery method. A convenient export can contain enough planning detail to be sensitive even when it contains no login secret.

Keep access secrets and planning information separate

Authentication and scenario ownership controls are intended to prevent one signed-in user from opening or changing another user’s plan. Safe error references help support investigate a failure without showing private diagnostic detail on the page.

Help content is public and should contain no scenario data. Help search uses the Help library rather than sending the question to an unrelated public search service. For product-policy questions, follow the footer links to the current governing documents.

Never put a password, recovery code, authenticator secret, full account number, brokerage login, or complete financial document into an ordinary support email. A useful support request can name the page, approximate time, action, and safe error reference.

Help cannot make a policy guarantee that the policy does not make

A description of a visible control is not a certification, audit, retention promise, encryption guarantee, or statement about every employee or service provider. Those claims require current policy and operational evidence.

Use the formal privacy contact for access, correction, export, or deletion questions. Do not assume that changing a subscription, closing a browser, or deleting one scenario has the same effect as deleting an account.