Statute of Limitations for Invasion of Privacy in South Dakota

5 min read

Published March 22, 2026 • By DocketMath Team

Overview

In South Dakota, claims framed as “invasion of privacy” are governed by South Dakota’s general statute of limitations for civil actions—not by a special, invasion-of-privacy-specific filing deadline. In other words, South Dakota does not appear to provide a separate statute-of-limitations rule tailored specifically to invasion of privacy (such as a different limitation for privacy torts). Instead, courts typically look to the general limitation period in the civil statute.

For planning and case management, that means the timeline usually turns on when the alleged wrongful conduct occurred (and, in some situations, when the claim “accrued”). DocketMath’s Statute of Limitations calculator helps you apply the South Dakota general rule consistently so you can forecast filing deadlines and compare different “trigger” dates (like date of event vs. date you discovered it).

Note: This page describes the general/default statute of limitations rule for South Dakota. If your facts involve a different legal theory (contract, defamation, product claims, etc.), the limitation period may be governed by a different statute.

Limitation period

Default period (general rule)

South Dakota’s general statute of limitations for civil actions is 3 years under SDCL 22-14-1.

Because no invasion-of-privacy-specific sub-rule was found for South Dakota, you should treat 3 years as the default limitation period for invasion-of-privacy claims in this jurisdiction.

What date you should use (the “clock starts” question)

Even with a fixed 3-year period, the most practical question is: when does the clock start running for your specific situation. Many claims are said to accrue when the wrongful conduct occurs and the plaintiff can reasonably bring the claim. Depending on the scenario, you may consider dates such as:

  • Date of the privacy-causing event (e.g., publication, disclosure, recording, or tracking)
  • Date you discovered the conduct (if discovery concepts apply to the accrual analysis)
  • Date the harm became apparent enough to bring the claim

DocketMath is designed to make these comparisons easy—use different candidate dates and watch how the estimated deadline shifts.

Quick example (how the 3-year period plays out)

If the privacy-causing event happened on March 1, 2024, the general filing deadline under the 3-year rule is typically March 1, 2027 (subject to accrual and any other legal timing adjustments your matter may involve).

If you instead use a discovery-related date—for example September 1, 2024—the projected deadline moves out to about September 1, 2027.

How output changes when you change inputs

When you use DocketMath’s calculator, you’ll generally influence the deadline through:

  • Accrual/trigger date you select
    • Earlier date → earlier deadline
    • Later date → later deadline
  • **Jurisdiction selected (US-SD)
    • Confirms the rule you’re applying: 3 years under SDCL 22-14-1

Key exceptions

South Dakota’s general rule is clear—3 years under SDCL 22-14-1—but real-world filing deadlines can still be affected by timing doctrines that either pause the clock or change how accrual is determined. Since these timing doctrines depend heavily on the underlying facts and claim posture, the safest workflow is to treat “3 years from the selected trigger date” as your baseline, then validate whether any exception-like timing concept applies.

Here are the most common categories to check when you’re mapping an invasion-of-privacy timeline:

  • Accrual timing disputes
    • The biggest moving part is often the accrual/trigger date: event date vs. discovery date.
  • Tolling / pause concepts
    • Certain circumstances can prevent the limitation period from running (for example, legal disabilities or specific procedural circumstances).
  • Legislative or procedural overlays
    • Some causes of action borrow rules from other statutes, or procedural prerequisites can affect timing.

Warning: Do not assume a “discovery” date automatically controls the clock for every privacy-related claim. For statute of limitations analysis in South Dakota, you’ll want to confirm what accrual rule applies to your specific facts and legal theory before relying on a discovery-based trigger.

A practical way to reduce timing risk is to run multiple scenarios in DocketMath (event date and discovery date) so you can see a range of potential deadlines and prepare accordingly.

Use-case checklist (practical)

Statute citation

South Dakota’s general statute of limitations for civil actions is:

  • **SDCL 22-14-1 — 3 years (general limitation period)

Because no invasion-of-privacy-specific limitation rule was found, SDCL 22-14-1 is the default starting point for invasion-of-privacy filings in South Dakota.

Use the calculator

Use DocketMath’s Statute of Limitations calculator.

To get the most reliable estimate, set:

  1. Jurisdiction: US-SD
  2. Rule type: General (default) — 3 years under SDCL 22-14-1
  3. Trigger date (accrual date):
    • Choose the date you believe the claim accrued (commonly the event date or a discovery-related date if applicable to your facts)

Inputs to run (recommended)

Run at least two calculator scenarios:

Output you should expect

The calculator will produce an estimated latest filing date based on:

  • 3-year limitation period, applied to your selected trigger date under SDCL 22-14-1
  • Any date-to-deadline arithmetic based on the calendar

If the deadlines differ by months or years, treat the earlier deadline as your risk-managed target for internal planning.

Note: A calculator output is a timing estimate based on selected dates and the statutory baseline. Your real deadline can be affected by accrual disputes, tolling arguments, or procedural timing rules unique to your case.

Sources and references

Start with the primary authority for South Dakota and confirm the effective date before relying on any output. If the rule has been amended, update the inputs and rerun the calculation.

Related reading