Security Practices for Advisors

Last updated: November 18, 2025

This guide outlines recommended security practices for financial advisors using Follow Through, a productivity and follow-up management tool provided by Beer Tech Studios LLC.

While Follow Through is designed to minimize sensitive data collection and avoid transmitting personal information to AI systems, advisors are still responsible for ensuring their use complies with firm policies and regulatory expectations.

1. What Follow Through Stores

Follow Through is intentionally narrow in scope. It stores:

  • Prospect and client names (optional)
  • Basic contact information (email only)
  • High-level tags (fit type, value tier, channel preferences, etc.)
  • Internal notes (entered by the advisor)
  • Follow-up interactions and scheduling
  • AI-generated email drafts (created locally in your browser)

Follow Through does not collect or request account numbers, financial balances, SSNs, income amounts, net worth, or investment holdings.

2. Recommended Data Entry Practices

To help maintain compliance and data security, advisors should:

  • Limit entered information to general relationship, follow-up, and high-level planning details.
  • Write notes in non-PII terms such as: "Client interested in retirement planning after upcoming job change."
  • Use internal firm systems for sensitive financial details.
  • Never type confidential numbers or documents into Follow Through.
  • Let the AI feature handle placeholders like [Client] — the app swaps real names locally.
Rule of thumb: If the information belongs in a client vault, account record, custodian form, tax return, or CRM secure file upload — it should not be typed into Follow Through.

3. Using the AI Email Generator Safely

The AI writing assistant in Follow Through uses carefully structured prompts and placeholders to ensure no client PII is transmitted.

  • The system sends zero client data to the AI provider.
  • All personal details including [Client] or advisor signature elements are inserted locally in your browser.
  • Advisors must review and approve each draft before sending via their own email system.
You remain the final reviewer. AI output is a draft, not a final recommendation or client communication.

4. What Not to Enter into Follow Through

For your safety and compliance, do not enter:

  • Account numbers
  • Statements or screenshots
  • Beneficiary information
  • SSNs, birthdates, driver's license numbers
  • Tax return data
  • Investment holdings or position-level details
  • Dollar amounts (income, balances, withdrawals)
  • Risk tolerance questionnaire results
  • Full client household data or family trees

Follow Through is designed to help you stay organized, not to store or transmit highly sensitive information.

5. Advisor Security Checklist

We recommend the following good practices:

  • Use a strong, unique password for your email and Follow Through.
  • Enable 2FA on your email and Supabase account (if applicable).
  • Lock your computer when stepping away.
  • Keep your browser and operating system fully updated.
  • Do not share access or logins with assistants or teammates.
  • Use firm-approved devices when possible.

6. Conversation Tips for Talking to Compliance

Advisors often need to explain how software works during a compliance review. Here is a simple, approved way to describe Follow Through:

“Follow Through is a lightweight follow-up tracker. It does not store financial data or account details. It only stores high-level tags, meeting notes, and email drafts. No client PII is ever sent to the AI model — placeholders are used instead, and the real client details are inserted locally on my device. AI output is a draft that I review before sending.”

You may also share this page, along with the full Privacy Policy, Terms of Service, AI Disclosure, and Security Overview.

7. Questions?

For security or compliance inquiries about Follow Through, contact Beer Tech Studios LLC:

  • Email: support@beertechstudios.com (placeholder)
  • Website: beertechstudios.com (placeholder)