Privacy Policy
Last updated: September 2026
Information We Collect
When you subscribe to the MyFriendAlex newsletter or join a product launch list, we collect the following information:
- Your first name (optional)
- Your email address
For newsletter signups, MFA also keeps limited consent and delivery records such as the signup source and placement, the page where you joined, the consent-copy version, subscription timestamps, subscription status, welcome-sequence version, and email-provider synchronization status. After subscribing, you may optionally provide a first name and explicitly choose newsletter interests such as saving and debt, housing, retirement and tax, markets and ETFs, family money, credit cards, or deals and bonuses. Those preferences are optional and can be changed later where controls are available. This helps us avoid duplicate subscriber records, honor unsubscribe requests, understand which signup placements are useful, and keep the first-party MFA list consistent with the service used to deliver emails. We do not need an IP address, calculator inputs, or your My MFA financial baseline to subscribe you to the newsletter. For product or template launch interest, MFA may also keep the canonical product or template IDs you selected, your current favorite, the original and most recent signup placement/page, the consent-copy version, first/last interest timestamps, and a count of repeat interest submissions. MFA normalizes the email address to avoid treating repeat submissions as different people and can retain the set of products you expressed interest in so demand rankings are based on unique interested people rather than duplicate rows. Product-interest records are kept private to authorized MFA administration and are not returned with email addresses in the aggregate Growth dashboard. Product-launch updates are a separate consent from the MFA weekly newsletter. If MFA later syncs launch interest to the same email-delivery provider used for the newsletter, launch contacts are segmented as launch interest and by the product(s) they asked about; that does not enroll them in the weekly newsletter without a separate newsletter opt-in. A provider-level unsubscribe or cleaned/suppressed address may be honored conservatively across MFA email delivery, and MFA retains the first-party suppression state needed to avoid resending to an address that should not receive email.
When you submit the contact form, we also collect your name, email address, and the content of your message.
If you choose to submit a community data point in MFA Deals while signed in, MFA may store the deal you are reporting on, the type of event you selected (for example, approved, denied, or bonus posted), an optional two-letter state, an optional bonus-posting time or amount, a short note, your authenticated account identifier, and the moderation status of the report. Community data points remain private to you and authorized MFA administrators until moderation. Public Deals pages receive only sanitized approved aggregates such as report counts or median bonus-posting time; raw notes, account identifiers, email addresses, and other direct identifiers are not returned in the public Deals feed. Please do not put account numbers, card numbers, application or confirmation IDs, passwords, Social Security numbers, street addresses, or other sensitive identifiers in a community note.
MFA Community is a separate public discussion area. If you participate, MFA may store the public handle, optional display name and bio you choose, posts and replies you publish, Helpful votes, reports, moderation status, and any Deal or privacy-safe scenario context you intentionally attach. Your public Community handle is designed to be separate from your private My MFA financial baseline and account email. Community posts and replies are public, may be linked from other MFA pages, and may be discoverable or indexed by search engines, so do not publish information you want to keep private. MFA may also publish clearly labeled “MFA Starter” profiles, posts, and replies written by MyFriendAlex to seed useful example discussions while real member participation grows. MFA Starter content is synthetic, is not a real member experience or endorsement, does not count toward real member totals, and is not given fabricated Helpful votes. MFA applies automated sensitive-data and abuse checks and may moderate, hide, or remove content, but those controls are not a guarantee that every risky detail will be detected before publication.
Deal reactions such as Worth it, Pass, Love and Watching can be used without creating an account. To keep one active reaction per browser for a given Deal, MFA may store a randomly generated browser-level reaction identifier in local browser storage and associate that identifier with the selected Deal reaction. Public pages receive aggregate reaction counts and your browser can receive its own current selection; the reaction system is not designed to publish your email, real name or private My MFA financial baseline.
My MFA Account and Financial Baseline
If you create My MFA and choose to save a financial baseline, we may store the information you intentionally enter so supported tools can reuse it. Depending on what you choose to provide, this can include household income, filing status, state or ZIP, retirement contributions, cash and emergency-fund assumptions, rent or mortgage information, debt balances and rates, vehicle loans, selected credit cards, spending assumptions, family/dependent counts, retirement-income assumptions, health-plan cost assumptions, goals, and saved calculator scenarios. If you organize saved scenarios, MFA may also store labels, pinned status and folder names that you create.
MyFriendAlex does not need or ask you to save bank account numbers, card numbers, passwords, Social Security numbers, brokerage credentials, or other login secrets in My MFA. Please do not enter those items into profile fields, scenario names, contact forms, or notes.
Saved profile data is used to prefill supported calculators, generate rules-based planning comparisons, reopen saved scenarios, and show changes when you update your baseline. Changing a calculator scenario does not silently overwrite your saved My MFA baseline.
If you save a private Deal Watch, MFA may store the Deal identifier and the source-dated offer terms that were current when you started watching, such as the bonus amount, deadline, stated direct-deposit or cash hurdle, holding period, transaction-count hurdle, and a fingerprint of those terms. MFA uses that baseline to tell you when a currently verified Deal differs from the version you chose to watch. Free My MFA can check these saved Deal Watches while you use MFA. If your account has MFA Gold, supported Deal Watch changes can also create a private Gold Center attention item. A private Deal Watch is separate from public Deal reactions such as Worth it, Pass, Love, or Watching and does not publish your My MFA profile or financial inputs.
If you use the private Bonus Tracker, MFA may store the Deal identifier and label, the structured bonus/hurdle snapshot shown when you started tracking (for example the headline bonus, stated cash, direct-deposit, spending, transaction-count or holding-period requirements, and offer deadline), the lifecycle status you select, dates you choose for opening, qualification, expected posting or actual posting, numeric progress you enter toward supported hurdles, and the bonus amount you say was received. Bonus Tracker is a self-reported checklist. It does not connect to a bank or card account, inspect payroll, decide whether a transaction qualifies, or require an account number, card number, bank login, payroll identifier or free-form bank note. The official institution terms remain the source of truth. Bonus Tracker records are separate from Deal Watch records so removing one does not silently remove the other. If you choose the Bonus Tracker control to share a posting data point with the moderated Deals community, MFA can prefill the Deal identifier and the selected event type only; tracker dates, hurdle-progress values and the bonus-received amount are not copied into the community report unless you separately choose to enter them there.
If you save a private APY Watch, MFA may store the savings/CD product identifier, institution/product label, the source-published APY that was current when you saved the watch, source/effective date, optional balance/tier context needed to interpret a tiered published APY, and the most recent source-published APY MFA observed. An APY Watch does not connect to your bank account and does not tell MFA the actual rate on an account or CD you already hold. For CDs, MFA watches the currently advertised APY for the selected product or term; it does not imply that the contractual APY on an existing CD changes when new-offer pricing changes.
If you save a private Economic Release Watch, MFA may store the recurring release type you chose to follow, such as CPI, the jobs report, PCE inflation, GDP or an FOMC decision, along with its category/importance and the most recent matching official calendar event MFA checked. The watch follows the release type rather than hard-coding one calendar date. Release dates and times come from MFA's official-source calendar feeds; MFA does not store or fabricate a market-consensus estimate as part of these watches.
If your account has MFA Gold, MFA may also store membership status and plan, membership-period dates, billing-provider customer or subscription identifiers, store-benefit issuance records, Gold alert preferences, and private Gold Center items or timeline events created from supported rate or market thresholds, Deal changes, published savings/CD APY changes, upcoming watched economic releases, card-perk dates, weekly brief cycles, and quarterly review cycles. Card Wallet can also store the card products you selected, your optional personal point/perk values and used/not-used flags, and an optional account-anniversary or annual-fee review date for a card. That date is used only as a review anchor; MFA does not treat it as a payment due date. When Card Wallet is saved, MFA may prepare private dated Card Perk Reminder rows from explicit issuer cadence or expiry language and from anniversary dates you entered. MFA-managed reminder rows are marked as Gold-required and use a separate internal namespace so automatic synchronization does not overwrite future manual/custom reminders. Active Gold maintenance can advance supported recurring reminders after a period ends and create a generic Gold Center attention item when the reminder enters your selected lead window. Card Wallet reminder records can be exported or deleted with the rest of your user-controlled My MFA data. The in-app weekly brief can store privacy-light counts and status signals such as the number of active saved watches/reminders, watched economic releases scheduled in the next seven days, unread Gold Center items, the calendar-week key, and whether a saved My MFA baseline exists. It is designed not to copy the baseline values, watch thresholds, account balances, card details, or user-entered financial labels into the weekly-brief notification. Supported threshold watches may retain the most recent source value, source timestamp, whether the saved condition is currently met, and the time the condition most recently crossed into the trigger zone so MFA can avoid repeating the same alert until the watch re-arms. Gold Center records are designed to use generic reminder text and product/date context rather than copying private balances or user-entered financial labels into notification records. Gold Scenario + Baseline History can store compact history points for meaningful baseline changes using selected high-level before/after metrics already present in My MFA, plus scenario history metadata such as the MFA tool, a private version sequence, view type, save time, and a pathname with URL query inputs removed. Scenario labels, assumption text, and query-string inputs are not copied into Gold scenario history. User-controlled Gold records—including timeline history, Gold Center inbox items and preferences, and saved quarterly Health Check reports—can be included in the My MFA data export and deleted through My MFA data controls even if the account is no longer actively subscribed to Gold. Gold alert preferences can distinguish categories such as Rates, Markets, Deals, Card perks, Savings APYs and Economic releases. Preference fields for delivery channels can exist before those channels are activated; MFA does not treat email or push delivery as enabled until the corresponding provider/device-delivery infrastructure is actually connected and tested. Gold billing audit records may also retain normalized provider metadata such as the provider name, event ID/type/time, customer/subscription reference, plan/status/period, amount/currency, processing result, and a payload fingerprint so duplicate or out-of-order events can be reconciled without retaining the raw provider webhook body. Payment-card credentials are not stored in these MFA Gold entitlement or billing-audit records; when paid enrollment is enabled, payment processing should remain with the configured payment provider.
MFA Guides can also remember reading progress, such as the guide slug, highest progress milestone, completion status, learning-path context, and first/last reading timestamps. If you are not signed in, this guide progress can be stored locally in your browser so you can continue on the same device without creating an account. If you later create or sign in to My MFA on that browser, anonymous guide progress may be merged into that authenticated account so it can sync across devices. MFA separates locally cached progress by signed-in account so progress from one authenticated account is not intentionally merged into another account on the same device.
Shared Scenarios
When you explicitly create or use a public scenario share, MFA can create a short public scenario record containing only the inputs needed to reproduce that shared view. The sharing system is designed to strip internal profile-source markers and does not publish your private My MFA profile as part of the share. Anyone with a public scenario link may be able to open that scenario, so only share scenarios you are comfortable making accessible through the link.
How We Use Your Information
We use your information to:
- Send the short MFA welcome sequence and subsequent newsletter emails you asked to receive
- Send launch updates when you explicitly join a product or template interest list
- Respond to questions you submit through the contact form
We do not sell or rent your personal information to advertisers or data brokers. We may use service providers acting on MFA's behalf, such as an email-delivery platform, to store subscriber-list data, honor suppression/unsubscribe status, run the welcome sequence, and send the emails you requested. Those providers receive only the information needed to provide that service and are not allowed to use the MFA subscriber list for their own independent marketing. If you manage newsletter settings from a signed-in My MFA account, MFA uses the authenticated account email observed by the server rather than accepting an arbitrary account email from browser analytics.
Commerce and Affiliate Links
MyFriendAlex only presents a purchase control when a real external checkout provider, price, delivery or fulfillment terms, and applicable refund or cancellation terms have been configured for that product. Payment-card processing is handled by the identified checkout provider rather than a normal MFA profile, contact, calculator, or launch-list field. Products that do not pass MFA’s live-commerce checks remain interest-only and do not display a purchase button.
Some outbound links may later be affiliate links. When an affiliate relationship applies, MFA will disclose it and may record a privacy-light aggregate outbound-click event so we can understand whether a monetized link is useful. The click event should identify the placement or partner category, not copy your calculator inputs or private My MFA profile.
Analytics, Financial Inputs and Browser Storage
MyFriendAlex records usage and technical data to understand how the site is being used, improve calculators and planning tools, detect abuse, troubleshoot problems, and measure site performance. This can include visits, pages viewed, calculator interactions, session duration, result-sharing activity, a randomly generated browser identifier, a short-lived session identifier, browser user-agent information, language, time zone, screen dimensions, and the Internet Protocol (IP) address observed by MFA's server when an analytics event is received. MFA may use that server-observed IP, including through a service provider acting on MFA's behalf, to derive and retain an approximate city, state or region, and country for internal visitor-session reporting. IP-based location is approximate and is not GPS or street-address location. When a visitor arrives through a tagged campaign or supported advertising link, MFA may also retain allowlisted attribution values such as UTM source, medium, campaign, content, term, or a supported advertising click identifier. MFA does not intentionally retain arbitrary URL query strings for analytics attribution.
When you enter financial values into supported calculators or the Money Plan, MFA may also store a private snapshot of the financial inputs used in that scenario, such as income, cash savings, spending, debt balances and rates, property values and mortgage assumptions, retirement contributions, or similar values you chose to enter. These analytics records are separate from the My MFA profile you intentionally save to your account. If you arrive from a Mailchimp-delivered MFA email, MFA may also retain the allowlisted Mailchimp campaign identifier (`mc_cid`) and recipient identifier (`mc_eid`) that Mailchimp places on tracked links. These identifiers help MFA connect an email campaign to on-site engagement and conversions without storing arbitrary URL parameters. MFA may compare those on-site outcomes with read-only Mailchimp campaign statistics such as sends, opens, clicks, bounces and unsubscribes. MFA does not need or intentionally collect bank-account numbers, payment-card numbers, passwords, Social Security numbers, brokerage credentials, or other login secrets through calculator analytics, and you should not enter those items into normal calculator, profile, scenario-name, contact, or note fields.
MFA uses these records for internal product analytics, security, abuse prevention, debugging, and to understand which financial scenarios visitors are trying to model. They are not sold or rented to advertisers or data brokers. When you are signed in, MFA may associate usage and financial-scenario analytics with the authenticated account identifier and email address observed by MFA's server. This lets MFA understand the path from an earlier anonymous browser visit to account creation and later signed-in use, measure retention, troubleshoot account-specific issues, and respond accurately to data-access or deletion requests. MFA does not accept an account email or user ID supplied by browser analytics as proof of identity. The private Growth dashboard is designed to show aggregate results and does not return raw IP addresses or raw financial-input snapshots. Separately restricted administrator-only operational tools may allow authorized MFA administrators to inspect raw session, account-linkage, IP, browser, and financial-input records when needed for analytics, security, debugging, product improvement, or responding to data requests.
MyFriendAlex does not use analytics counters to claim that a visitor earned or saved a specific amount of money. Public “dollars modeled” represents modeled scenario volume, not financial gain, and the aggregate applies outlier caps to reduce manipulation. MFA also applies automated redaction to credential-like strings detected in financial analytics snapshots, such as Social Security numbers, payment-card numbers, routing/account-number patterns, passwords, PINs, or similar login secrets. This safeguard is intended to preserve useful financial modeling data while avoiding retention of credentials MFA does not need.
You can disable browser storage or enable a supported Do Not Track setting in your browser at any time. Disabling or clearing browser storage can remove anonymous on-device guide progress and other local convenience state. MFA may retain analytics and financial-scenario records for as long as they remain reasonably useful for product analytics, security, fraud/abuse prevention, debugging, recordkeeping, or other legitimate business purposes, subject to applicable legal requirements and deletion rights. Where applicable, privacy laws may provide additional rights to access, correct, delete, or limit certain uses of personal information.
Your Controls and Rights
You have the right to:
- Unsubscribe from our newsletter at any time using the unsubscribe link in every email
- Review and update the financial baseline you chose to save in My MFA
- Delete individual saved scenarios
- Download a copy of your My MFA profile, saved scenarios, folders, synced guide progress, private watches, Bonus Tracker progress, Card Wallet preferences/reminders and user-controlled Gold history where that control is available
- Delete your saved My MFA profile, scenarios, folders, synced guide progress, private watches, Bonus Tracker progress, Card Wallet preferences/reminders and user-controlled Gold history where that control is available, or request deletion by contacting us
- Request a copy of other personal data we hold about you
Data Sources and Financial Information
Public market, economic, tax, bank-rate and product information can change after it is collected. MyFriendAlex labels source and freshness information where practical and may retain a last-verified snapshot when a live refresh is unavailable. See the Data, Sources & Methodology page for more detail on how MFA distinguishes sourced facts from modeled estimates.
Contact
If you have questions about this privacy policy or how your data is handled, please visit our contact page or reach out on 𝕏 (Twitter).