Statute of Limitations for Invasion of Privacy in District of Columbia

Overview

Run this scenario in DocketMath using the Statute Of Limitations calculator.

In the District of Columbia, a lawsuit for invasion of privacy is generally governed by the general civil statute of limitations—not a special, invasion-of-privacy-only clock.

For DocketMath users, this means the first and most important step is identifying when your claim accrued (the date the actionable harm is treated as having begun) because the limitations period typically starts from that moment, not from the date you discovered the conduct.

If you’re tracking deadlines or preparing a case timeline, you’ll want your dates ready:

• the event date(s) (or the span of ongoing conduct)
• the accrual date you’re using (often tied to when the harm became actionable)
• the date you plan to file or the date you already filed

DocketMath’s statute-of-limitations calculator can help you model those dates in a consistent way (see Use the calculator).

Limitation period

General rule: 3 years

District of Columbia’s general limitations period for certain civil actions is:

• 3 years under **D.C. Code § 23–113(a)(1)

Because no invasion-of-privacy-specific SOL rule was identified here, treat 3 years as the baseline for invasion-of-privacy claims in DC—unless a different statute applies based on the claim’s specific legal theory or the facts trigger a distinct exception.

How the deadline typically moves with different inputs

When using DocketMath, the output will primarily change based on the following:

• Accrual date

  • Earlier accrual date → earlier deadline
  • Later accrual date → later deadline
• Filing date (or proposed filing date)

  • Filing after the calculated deadline → higher risk the claim is time-barred
  • Filing on or before the deadline → generally within the limitations window

Practical checklist for your timeline

Before running the calculator, collect:

If the privacy issue involves multiple acts, you may need to determine which act is treated as starting the clock for your claim (that determination is often fact-driven). The calculator can model different accrual dates so you can see how the deadline changes.

Key exceptions

Even with a 3-year baseline, the limitations period can be affected by exceptions or procedural rules. The goal of this section is to show you what to look for, not to advise litigation strategy.

1) Tolling (pausing the clock)

Some legal circumstances can pause (toll) the SOL so the deadline moves later. Common categories in civil practice include:

• certain disability-based tolling concepts
• statutory tolling tied to specific procedural events

For invasion of privacy in DC, the key point for your workflow is: tolling can change the end date even if the baseline is 3 years. DocketMath can’t automatically infer tolling from facts unless you input a tolling-adjusted accrual date or use a workflow that reflects the tolling outcome.

2) Accrual timing disputes

A frequent real-world issue isn’t that the statute length is wrong—it’s that the accrual date is contested.

Examples of why accrual can vary:

• the claim may be treated as accruing when the act occurred versus when the impact became actionable
• ongoing conduct can complicate whether the SOL runs from the first act, last act, or another event tied to legal accrual

This matters because DC’s general rule is a set period—3 years—and your end date is computed from your selected start date.

3) Different statutory theories may have different clocks

Even though no invasion-of-privacy-specific sub-rule was found for DC in this summary, the legal theory you plead can sometimes point to different statutory limitations—particularly when privacy-related claims overlap with other statutory causes of action.

If your facts could be framed under more than one legal theory, you may need to compare SOL timelines across theories rather than relying only on the invasion-of-privacy label.

Statute citation

• D.C. Code § 23–113(a)(1) — 3-year general limitations period

Source: https://law.justia.com/codes/district-of-columbia/2014/division-iv/title-23/chapter-1/section-23-113/

Use the calculator

You can run the DocketMath statute-of-limitations calculator here: /tools/statute-of-limitations.

Before you press calculate, decide what your inputs will represent:

1. Jurisdiction: District of Columbia (US-DC)
2. Statute used: D.C. Code § 23–113(a)(1) (general default)
3. Accrual date: the date you’re treating as when the claim accrued
4. Optional: any adjusted accrual date if you have a tolling reason you’re accounting for in your timeline

How outputs change with common input choices

To make the output actionable, consider these scenarios:

• Scenario A: Accrual = event date

  • If your accrual date is the date the privacy intrusion occurred, your SOL end date will be exactly 3 years later (subject to how the calculator handles exact-day counting).
• Scenario B: Accrual = later “actionable” date

  • If you move the accrual date forward (for example, to a date the harm became actionable under your theory), the SOL end date moves forward by the same amount of time.
• Scenario C: Adjusted accrual for tolling

  • If you’re accounting for tolling, you may input a tolling-adjusted accrual date so the computed deadline reflects the pause.

If you want to sanity-check your timeline, you can also review other DocketMath tools (for example, using /tools/statute-of-limitations alongside your case timeline workflows).

Related reading

• Choosing the right statute of limitations tool for Vermont — Tool comparison
• Statute of limitations in Singapore: how to estimate the deadline — How-to guide
• Choosing the right statute of limitations tool for Connecticut — Tool comparison