“Should we update our privacy policy this year” is the wrong question, and it’s also the one most businesses ask. It treats the policy like a piece of equipment due for annual maintenance, checked on a calendar regardless of whether anything actually changed underneath it. A privacy policy isn’t a maintenance item. It’s a factual statement about what your business does with personal data right now, and the correct time to update it is whenever that statement stops being true, not whenever twelve months happen to have passed since the last edit.

This isn’t a “rewrite it once a year” guide. It’s a trigger checklist: the specific business changes, new tools, and legal developments that should send you back to the policy you already have, so it stays a description of the business you’re actually running instead of the one you were running when someone last opened the document.

Why there’s no universal fixed schedule (with one real exception)

Most privacy laws, GDPR included, don’t specify a review interval for a privacy policy at all. What they require is accuracy: the policy has to reflect current practice, and it has to be updated when practice changes, whenever that happens to occur. A policy that hasn’t changed in three years because nothing about the business’s data practices has changed in three years isn’t out of compliance. A policy that hasn’t changed in three months, during which the business added a new payment processor and started serving customers in two new states, is.

There’s one genuine, narrower exception worth knowing. California’s CCPA regulations require covered businesses to review, and update as necessary, their privacy policy at least once every 12 months, specifically the sections addressing the categories of information collected, disclosed, and sold. That’s a real requirement, but it’s a floor for review, not a mandate to rewrite the document annually whether or not anything changed, and it doesn’t apply the same way outside California-covered businesses. Treat it as one input among several, not the whole system.

California regulations require a privacy policy review at least once every 12 months 12 months CCPA minimum reviewfor covered businesses

The system that actually works is the same one that already governs the rest of your site’s legal pages: a list of events that, when they happen, mean the policy is now out of date until you fix it.

A business change triggers a policy update so the policy stays accurate A new vendor or tool means the policy is out of date

The trigger checklist

The question isn’t “has it been a while.” It’s “did any of these specific things happen since the policy was last reviewed.” If the answer is yes to any of them, the current version is stale.

Walking through each branch, plus two that don’t fit neatly into a yes/no diamond:

You started collecting a new type of data, or added a required field. A new signup field, a precise-location prompt, a biometric check for account verification, or a new required document upload all expand what the policy needs to disclose. This is the most common trigger and the easiest to miss, because the person adding the field (product, engineering, growth) usually isn’t the person who maintains legal pages, and the two rarely talk to each other about it. Any data type your forms or your app now collect that the policy doesn’t mention is a gap, whether it’s sensitive data like health or biometric information or something as ordinary as a phone number that used to be optional and is now required.

A new vendor, processor, or AI tool started touching personal data. Swapping payment processors, adding a customer support platform, plugging in a new analytics tool, or routing support tickets through an AI assistant all mean a new party now has access to data your policy previously described as going only to the vendors you’d already named. This is the same category of drift covered in our guide on what changes should trigger an update to a mobile app’s privacy policy when a new SDK gets bundled into a release; the web equivalent is any new third-party service wired into your signup flow, backend, or support stack.

You expanded into a new state or country. US state privacy laws aren’t uniform, and the list of states with their own comprehensive privacy statute keeps growing. A business that starts actively serving customers in a state with its own law, or begins marketing into the EU or UK for the first time, may pick up disclosure obligations, new consumer rights, or opt-out mechanisms that weren’t relevant to the old footprint. The policy’s scope, its rights section, and sometimes its opt-out mechanics all need to reflect the new audience, not just the original one the business was built around.

Your data sale, sharing, or retention practices changed. Starting to share data with an ad network for the first time, changing whether that sharing counts as a “sale” under state law definitions, or simply changing how long you keep a given category of data all make specific claims in the policy wrong. If your retention section still says “kept as long as necessary” without tying that to an actual period or criteria, our GDPR data retention guide walks through building a specific retention schedule that a policy update can then just state plainly, rather than continuing to lean on the vague version.

Your business structure changed. An acquisition, a merger, a rebrand, or simply a new registered address, data protection contact, or support email all need to show up in the policy’s contact and identity sections. Data subjects and regulators use that information to reach you; a policy that still names an acquired company’s old legal entity, or an email address nobody checks anymore, fails at that basic job even if every other clause in it is accurate.

A new law took effect, or an existing one was amended, that applies to your business. State privacy laws get amended on their own schedule, independent of anything you did. A new right added to a state statute, a threshold change that newly brings your business into scope, or an amendment to an existing law’s disclosure requirements all mean the policy needs a look even though nothing on your end changed. This is the trigger that’s easiest to miss entirely, since it requires tracking legal developments rather than noticing your own product changes, which is also why it’s worth checking against your own applicable state and country list on a recurring basis rather than assuming you’d hear about it.

What a drifted policy actually looks like next to a current one

The failure mode usually isn’t a policy that says nothing. It’s one that says something specific and confidently wrong, which reads worse under scrutiny than a shorter, honest version would.

Drifted policy
  • We may share data with service providers as needed for our business.
  • We retain your information for as long as necessary.
  • This policy addresses users in the United States.
Current policy
  • We share data with Stripe for payments and Zendesk for support requests.
  • Account data is kept for your active subscription, plus 3 years for tax records.
  • This policy addresses rights under the CCPA, VCDPA, CPA, and applicable state laws.

The left column wasn’t dishonest the day it was written. It was overtaken by a new support vendor added six months later and a customer base that grew into two new states nobody updated the scope section for. That’s the ordinary way these documents drift: not through bad faith, through normal business changes outpacing a page nobody assigned continuing ownership of.

A quick way to sort a given change into “update now” or “leave it” before you second-guess yourself on every commit:

Is This a Trigger to Update?

Update needed?Why
New required signup field addedYesNew data type collected
New payment processor or AI vendorYesNew processor, new data flow
Started serving a new state or countryYesNew jurisdiction, new rights
Retention period changed for a data typeYesRetention claim now wrong
Homepage redesign, same data practicesNoNo new data practice
Site colors or logo updatedNoCosmetic only
Fixed a typo in the footer textNoNo substance change

Building the check into a process you already have

The checklist above only helps if something actually surfaces these events to whoever maintains the privacy policy. Two habits cover most businesses without adding a standalone compliance task nobody remembers to run.

Tie it to whatever launch checklist already exists. If your team reviews new vendors for security or reviews new features for a data-mapping step, add “update privacy policy if applicable” as one more line on that same checklist, the same way the deployment-time discipline covered in our guide on when a cookie policy needs an update rides along with a release process rather than existing as its own separate task. The advantage is the same in both cases: it attaches to a process that’s already mandatory instead of depending on someone remembering a second one.

New tools and legal changes should trigger an update, a date on the calendar alone should not new vendor new law new data use date alone

Run a periodic gap check independent of memory. Even with a launch checklist, changes get made by people who don’t know the checklist exists, and a vendor’s own product changes (a new default retention period, a new data category collected) can happen with no code change on your side at all. A quarterly read-through of your own policy next to what your product, vendor list, and served jurisdictions actually look like today catches what the checklist misses, and it’s also the moment to fold in California’s 12-month review requirement if that applies to you, rather than treating it as a separate calendar reminder.

Keeping the policy honest, not just current

None of this requires rewriting the document from scratch every time a trigger fires. Most updates are additive: a new vendor named, a new state added to the scope section, a retention period corrected. The document’s overall structure and legal language usually stay put; what changes is the small number of sentences that were actually made wrong by whatever happened since the last edit.

Our Privacy Policy Generator rebuilds those sections from the data types, vendors, and jurisdictions you tell it apply to your business, so a new processor or a new state becomes a form update instead of a rewrite, and the published page keeps describing the business you’re actually running rather than the one you were running the last time someone happened to open the file.

The information in this article is for informational purposes only and should not be construed as legal advice on any matter, and does not create a lawyer-client relationship.