Beyond the dashboardAI & Measurement · Independent guides
TrackingByAI Journal
← All guidesPrivacy and choice / Guide 25

Retention should match the question

Keeping data forever is rarely needed to answer a defined measurement question. Set a period and deletion path before collecting.

Casual dressed man smiling with headphones in a modern office setting, showcasing a relaxed work environment.

First, define the question

Different records serve different purposes: security logs, campaign events, correction emails, and aggregate reports need not share one retention period. Document the reason for each period and the owner who can change it.

Privacy begins with purpose. Before adding an identifier or sending an event, describe why the information is needed and whether a less detailed record would answer the same question. That description should be visible to the people building the page and to the people reviewing the policy. A broad promise of better experiences is not a substitute for a concrete purpose.

The boundary of the measure

A live site can involve several operators: the publisher, its host, an analytics provider, and an advertising service. Each may receive different data and apply different controls. Follow actual network requests and contracts rather than assuming that a first-party-looking hostname tells the whole story. The notice should describe the deployed configuration, not a generic imagined one.

Start retention design with a question: what future review genuinely needs the detailed record? If only a monthly trend is required, preserving aggregates may be enough. If an incident investigation needs event-level data, define a shorter operational window for that purpose.

Choice has to exist in the interface and in the code. If optional processing requires consent, a notice by itself does not stop a script from running. Test a fresh browser session before and after each choice, and verify that a declined option has the stated effect. Revisit the test after changing templates or vendors.

Try a small example

A team that needs a monthly trend may be able to preserve aggregated history while deleting detailed events sooner. Test whether the aggregate still answers the intended question.

Retention and access are part of collection design. Decide how long a detailed event is useful, who may see it, and how it is removed from exports and backups. An aggregate trend may serve a long-term question without keeping every individual event indefinitely. Document exceptions rather than allowing a default setting to become an accidental policy.

Before drawing a conclusion

A retention schedule must work in backups, exports, and vendor systems as well as the primary database. Otherwise the stated period can be misleading.

Deletion is a workflow, not a line in a policy. Check backups, exports, test environments, and vendor dashboards. A team should be able to explain what happens when a period expires and how it confirms that the rule was applied.

Readers should not have to supply more private information to ask a privacy question than the question requires. A page URL and a concise description are often enough to start. If identity verification becomes necessary for a specific record request, use a proportionate process and explain why it is needed.

A review path for this question

External links and embedded services create different data flows. A link normally takes a reader to another site only after a click; an embedded script can contact a provider while the current page is loading. Describe that difference plainly. It helps a reader understand which choices belong to this site and which belong to another operator.

Three things to record

  • The exact definition or decision behind “Retention should match the question”.
  • The source and date for the information being compared.
  • At least one limitation or alternative explanation.

A privacy review should remain open to correction. Compare the written notice with the scripts, forms, cookies, logs, and contact route that are actually present. Record when a feature changes and update the notice before the old wording becomes misleading. Transparency is a maintained practice, not a one-time page written for launch.

Use the guide as a starting point for reviewing a real service. Check the live configuration, current provider documentation, and applicable requirements before making a consequential change. If a page here is unclear or outdated, send its URL and the disputed passage through our contact route.

Continue reading

More perspectives