Skip to content

Writing an email privacy policy you can stand behind

On this page

An email privacy policy is the page on your website that says what your firm does with the email addresses people give you and the mail they send. It covers the contact form, the newsletter signup, the client intake and the inbox itself. Most small firms already handle that mail sensibly. The policy writes down what you already do, in words a client can read in two minutes.

This guide covers who asks a US firm for one, what goes in it, a sample you can adapt, and how to keep it true. It’s general guidance, not legal advice. Your lawyer, your bar or your regulator has the last word on your own wording.

What an email privacy policy covers

People type “email privacy policy” meaning one of two documents. Both are worth having, and they speak to different readers.

  • The public privacy policy. It lives on your website and speaks to clients, prospects and visitors. It says what you collect, why, who else handles it and how someone asks you about it. Most of this guide is about this one.
  • The staff email policy. It lives in your handbook and speaks to your team. It says the firm’s mailbox belongs to the firm and whether you monitor it. It has its own section below.

The public policy is broader than email, and that’s fine. For a professional firm, though, email is usually most of what you collect. Someone writes in through the form, you reply from your own address, and the thread becomes the client file. A policy that’s clear about that one path covers most of your real exposure.

Does a small firm need one?

Usually, yes. No single federal law tells every business to post a privacy policy. A handful of rules reach a small firm anyway, and the most common one reaches almost every website.

RuleWho it reachesWhat it asks for
CalOPPA, Cal. Bus. & Prof. Code § 22575Any commercial website that collects personal information from California residents. An email address counts.A posted policy with six required elements
CCPA, Cal. Civ. Code § 1798.140Businesses above the revenue or data thresholds belowA fuller notice with California privacy rights
Other state privacy laws, such as Virginia’sBusinesses that process data on at least 100,000 of the state’s residents a yearNotices and rights requests
GLBA Privacy RuleTax preparers, accountants, financial planners and advisors, as financial institutionsA separate privacy notice to customers
HIPAA, 45 CFR 164.520Covered health care providersA notice of privacy practices, posted on the website
FTC ActEveryoneWhatever your policy says must be true

California’s rule reaches past California

CalOPPA is the reason most US firms need a policy at all. It applies to any commercial site that collects personal information from Californians, wherever the firm sits. Its definition of personal information lists “an e-mail address” by name. So a contact form that a California prospect fills in brings you under it.

The penalty clause is gentle, which tells you what the law wants:

An operator shall be in violation of this subdivision only if the operator fails to post its policy within 30 days after being notified of noncompliance.

In other words, it wants a posted policy, and it gives you a month to fix a missing one.

The bigger state laws usually don’t reach a seven-person firm

The CCPA covers a for-profit business that meets any one of three tests:

(A) As of January 1 of the calendar year, had annual gross revenues in excess of twenty-five million dollars ($25,000,000) in the preceding calendar year, as adjusted pursuant to subdivision (d) of Section 1798.199.95. (B) Alone or in combination, annually buys, sells, or shares the personal information of 100,000 or more consumers or households. (C) Derives 50 percent or more of its annual revenues from selling or sharing consumers’ personal information.

The revenue figure has since been adjusted. The California Privacy Protection Agency set it at $26,625,000 from January 1, 2025. A small professional firm rarely meets any of the three tests.

Other states follow a similar pattern. Virginia’s law starts at data on 100,000 of its residents a year. It also exempts firms already covered by GLBA or HIPAA. If you’re growing toward those numbers, that’s the moment to ask a privacy lawyer about a fuller notice.

Tax, financial and health firms have a second document

If you prepare taxes or give financial advice, the FTC treats you as a financial institution under the Gramm-Leach-Bliley Act. Its guidance lists “tax preparers, accountants, and investment advisors” by name. That rule asks for a privacy notice to your customers, and it’s stricter about delivery than a website policy is:

Notices given orally or posted in your office(s) don’t comply with the rule.

Health care providers covered by HIPAA have a notice of privacy practices. The rule says where it goes:

A covered entity that maintains a web site that provides information about the covered entity’s customer services or benefits must prominently post its notice on the web site and make the notice available electronically through the web site.

Either of these sits beside your website privacy policy. The website policy can link to it and say which one governs client records.

Every policy has to be true

The FTC doesn’t require a policy. It does hold you to the one you post. Its privacy guidance covers promises made “either expressly or by implication,” and then says:

the FTC Act requires you to live up to those claims.

This is the one rule that turns a copied template into a risk. A template that promises things you don’t do is a promise you’re breaking. A short, true policy is safer than a long, borrowed one.

Your tools may ask for one too

Two tools most firms use make a privacy policy a condition of service. The Google Analytics terms say:

You must post a Privacy Policy and that Privacy Policy must provide notice of Your use of cookies, identifiers for mobile devices (e.g., Android Advertising Identifier or Advertising Identifier for iOS) or similar technology used to collect data. You must disclose the use of Google Analytics, and how it collects and processes data.

Mailchimp’s terms ask for a link of their own, covered in the newsletter section.

What goes in an email privacy policy

Start from CalOPPA’s list, because it’s short and it’s the one most likely to apply. Section 22575(b) says the policy shall:

(1) Identify the categories of personally identifiable information that the operator collects through the Web site or online service about individual consumers who use or visit its commercial Web site or online service and the categories of third-party persons or entities with whom the operator may share that personally identifiable information. (2) If the operator maintains a process for an individual consumer who uses or visits its commercial Web site or online service to review and request changes to any of his or her personally identifiable information that is collected through the Web site or online service, provide a description of that process. (3) Describe the process by which the operator notifies consumers who use or visit its commercial Web site or online service of material changes to the operator’s privacy policy for that Web site or online service. (4) Identify its effective date. (5) Disclose how the operator responds to Web browser “do not track” signals […] (6) Disclose whether other parties may collect personally identifiable information about an individual consumer’s online activities over time and across different Web sites when a consumer uses the operator’s Web site or service.

For a small firm, that turns into eight short sections:

  1. Who you are. The firm’s legal name, address and an email address for privacy questions.
  2. What you collect. Names, email addresses and phone numbers from forms, the content of messages people send you, and anything your analytics tool records.
  3. Why you collect it. To answer inquiries, do client work, send invoices and, if you have one, send a newsletter.
  4. Who else handles it. The categories of service providers, such as your email host, your forms tool, your practice software and any newsletter or analytics tool.
  5. How long you keep it. A plain statement of your practice. How long to keep client email covers setting that period.
  6. How someone reaches you about it. How a person asks to see, correct or delete what you hold.
  7. Tracking. How you respond to Do Not Track signals, and whether third parties such as an analytics provider track visitors across sites.
  8. Changes. How you’ll announce a material change, and the effective date at the top.

Two things are worth adding, though no small-firm law asks for them. Say that you don’t sell personal information, if that’s true. And say which document governs client files, such as your engagement letter or a GLBA or HIPAA notice.

Who else handles it: the line most templates get wrong

Templates say “trusted third parties” and stop. Your clients would rather know the kinds of businesses involved. Write the list from what you actually use. Open your email admin console, your website builder and your billing tool, and note every service that receives a name or an email address.

A seven-person firm usually ends up with something like this:

What it doesTypical examplesPolicy wording
Hosts your emailGoogle Workspace, Microsoft 365“our email provider”
Runs your website and formsSquarespace, WordPress, a forms plugin“our website and form providers”
Holds client recordsPractice management or tax software“our practice management software”
Sends your newsletterMailchimp, Constant Contact“our newsletter provider”
Counts visitorsGoogle Analytics“our analytics provider”
Helps with the inboxAI drafting or triage tools“service providers that help us manage our email”

Categories satisfy CalOPPA. Naming the vendors is kinder to the reader, and it’s what Google and Mailchimp ask for in their own cases. If an AI tool reads your mail, read its privacy policy before you describe it in yours. How AI tools handle your data covers what to check.

An email privacy policy example for a small firm

Here’s a short policy for a fictional seven-person accounting firm. It’s written to be read, so it’s in plain English and the first person. Swap in your own facts, and delete any line that isn’t true for you. Have your lawyer read the result before it goes live.

Privacy policy

Effective October 1, 2026

Who we are. Harbor & Pine CPAs, LLP, 100 Main Street, Springfield, IL 62701. Questions about this policy go to privacy@harborpine.example.

What we collect. When you use our contact form or email us, we collect your name, email address, phone number and whatever you choose to write. If you join our newsletter, we collect your email address. Our website uses Google Analytics, which records which pages you visit and a general location.

Why we collect it. We use it to answer your questions, provide services you engage us for, send invoices, and send the newsletter if you asked for it. We don’t sell your personal information.

Who else handles it. Our service providers handle information for us under contract. They are our email provider (Google Workspace), our website host, our practice management software, our newsletter provider (Mailchimp) and Google Analytics. Mailchimp’s own practices are in its Global Privacy Statement. You can read how Google uses data from sites that use its services at policies.google.com/technologies/partner-sites.

Client records. If you’re a client, our engagement letter and our separate privacy notice govern your tax and financial records.

How long we keep it. We keep inquiry emails for two years if you don’t become a client. Client records are kept for the period in our engagement letter. Newsletter addresses are kept until you unsubscribe.

Your choices. Every newsletter has an unsubscribe link. To see, correct or delete the information we hold about you, email privacy@harborpine.example and we’ll reply within 30 days.

Tracking. Our site doesn’t respond to Do Not Track signals. Google Analytics may collect information about your activity over time and across websites.

Changes. If we make a material change, we’ll update the date above and post a notice on our home page for 30 days.

Each section maps to one of CalOPPA’s six elements, plus the two extras. The two-year inquiry period and the 30-day reply are your firm’s choices. Pick ones your firm will actually keep.

Where to put it

CalOPPA’s “conspicuously post” includes a text link with the word “privacy” on your home page. The usual place is the site footer. Link it from every form that collects an email address too, right beside the submit button. What you say at that moment is a short notice of its own, covered in what to say when you ask for someone’s email address.

The newsletter and Mailchimp lines

If you send a newsletter, the privacy policy for email marketing is mostly three sentences. Say that you collect the address for the newsletter, name the tool that sends it, and say how to unsubscribe.

Mailchimp asks for a little more, in its Standard Terms of Use:

If and to the extent required by Data Protection Laws, you will clearly post, maintain, and abide by a publicly accessible privacy notice on the digital properties from which the underlying data is collected that (a) satisfies the requirements of applicable Data Protection Laws, (b) describes your use of the Service, and (c) includes a link to our Global Privacy Statement.

In practice, that’s one line naming Mailchimp and one link to its privacy statement. The sample above has both. Other newsletter tools have similar terms, so check yours.

Consent, unsubscribe rules and the law on commercial email are a subject of their own, and this guide leaves them there. The FTC’s CAN-SPAM guide is the primary source for US commercial email.

Keeping it true after you post it

A policy is only as good as its last review. Firms change tools more often than they change policies. A new forms plugin or an AI assistant can make a correct policy wrong overnight.

A light routine keeps it honest:

  • Review it once a year. Put it on the calendar beside your insurance renewal.
  • Review it when you add a tool. Any new service that receives a name or an email address belongs in the “who else handles it” list.
  • Read it as a client would. Each sentence should describe something you could show someone.
  • Change the date. Update the effective date every time you change the text, and keep the old version on file.

The other email privacy policy: the one for your staff

Your team’s work email is the firm’s record. A staff email policy says so plainly. It sets expectations before anyone needs them.

Most staff policies cover the same short list:

  • Ownership. The firm’s mailboxes and their contents belong to the firm.
  • Monitoring. Whether, and how, the firm may review work email.
  • Personal use. What’s allowed, and that personal mail in a work account isn’t private.
  • Leaving. What happens to a mailbox when someone leaves, and who takes over client threads.

Two states write the monitoring part into law. Connecticut requires prior notice of electronic monitoring:

each employer who engages in any type of electronic monitoring shall give prior written notice to all employees who may be affected, informing them of the types of monitoring which may occur.

New York’s Civil Rights Law § 52-c asks an employer who monitors email to give written notice on hiring, get an acknowledgment, and post the notice. If you have staff in either state, an employment lawyer can check your handbook language.

The rest of the set

A privacy policy is one of several documents a firm keeps around its mail. Each of these stands on its own:

Point as a line in your policy

If you use Point, it’s one of the service providers your policy names. Point is an AI assistant that works in your own Gmail or Outlook mailbox. It reads, sorts and drafts so your morning starts calm. Your mail stays in your mailbox, and replies go out from your own address.

Point publishes its own privacy policy and list of subprocessors. That’s what you need to describe it accurately. Its privacy policy says it doesn’t use your content to train generalized third-party large language models. A line like “service providers that help us manage our email” covers it. Point isn’t a compliance, archiving or retention tool, so those jobs stay with the tools you already use for them.

Common questions

Is an email address personal information?

Yes, under most US privacy laws. California’s CalOPPA lists “an e-mail address” by name in its definition of personally identifiable information. Collecting one through your website is usually enough to need a posted policy.

Do I need a privacy policy if I only have a contact form?

Usually, yes. A contact form collects names and email addresses. If any Californian can fill it in, CalOPPA asks for a posted policy. Analytics tools often require one in their terms as well.

Can I use a free privacy policy template or generator?

You can, as a starting point. Edit it until every sentence describes what your firm actually does. The FTC holds you to what the policy promises, so a borrowed promise you don’t keep is worse than a short policy.

Does my newsletter need its own privacy policy?

No. Your website policy covers it with a few lines. Say what you collect, name the tool and say how to unsubscribe. Mailchimp also asks for a link to its Global Privacy Statement.

Is a GLBA privacy notice the same as a website privacy policy?

No. A tax or financial firm’s GLBA notice goes to customers and covers their financial information. Your website policy covers visitors and inquiries. Keep both, and have the website policy point to the GLBA notice for client records.

How often should I update my privacy policy?

Review it once a year and whenever you add a tool that receives personal information. Change the effective date each time you change the text.

No. This guide explains what an email privacy policy is for and what small firms usually put in it. For your own policy, ask a lawyer, your state bar or your regulator.

Ready for a calmer inbox?

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.

Private beta

What you're joining

It runs on the mail you have

Point sits on top of Gmail or Outlook. Your address, your history and your contacts stay exactly as they are, so there is nothing to migrate.

You set how much Point does

Out of the box everything waits for your review, replies included. You hand over only what you trust, one kind of work at a time.

Join the private beta

We're onboarding a few teams at a time. Leave your email, confirm it once, and we'll send an invitation the moment a place opens.

By joining you agree to our privacy policy.