Data Protection Monitor
Global Privacy & Data Protection Intelligence

South Dakota, USA Data Protection & Privacy Regulation

US-SD schema gdpri-v2 trajectory: not yet assessed regulated (sectoral) overlaps: artificial-intelligence

Last updated · 10 categories · 67 claims · 37 sources in the cumulative register

South Dakota's Genetic Data Privacy Act, Senate Bill 49, is understood to have taken effect on July 1, 2026, codified at SDCL §§37-24-59 to 37-24-64.

Data collected Data published

AI-assembled from cited sources

Not fully checked this cycle: Regulator & Framework, Lawful Processing & Special Data (2 open gaps).

Framework & posture10 of 10 modules active
10 active · 10 binding instruments
Supervisory authoritySouth Dakota Attorney General
Next milestoneNo upcoming dated milestone on record
Record & confidence mix84 claims · 36 sources · machine-compiled
13 Confirmed38 Probable13 Contested / unverified
Evidence re-verified: ·Position last changed: ·
Record history & provenance ▾

Methodology & record provenance: Module confidence is derived from the underlying claims (source tier and primary excerpt retention), while statutory legal force is tracked independently.

Review status: AI-synthesised · Tier-1/2 verified · As-of date: 2026-11-17

United States federal law that applies in South Dakota, USA is covered once, on the United States page. This page covers South Dakota, USA’s own layer: its own law, regulators and enforcement.

Jurisdiction brief

Latest update · 4 November 2026

Lead Signal

South Dakota's Attorney General has announced receipt of the first $9 million payment from Meta Platforms, Inc., the opening disbursement of the state's $52,612,676 share (potentially rising to $73,480,057) of a 42-state multistate settlement over addictive-design harms to minors on Instagram and Facebook. The payment, received on 26 October 2026, has been placed in the state's Consumer Protection Fund pending legislative allocation. This is the clearest marker yet that the state's engagement with platform data practices runs almost entirely through enforcement and settlement recovery rather than through any statute aimed at the data practices themselves.

Key regulatory facts for South Dakota, USA
Key regulatory facts for South Dakota, USA
Regulatory DimensionSouth Dakota, USA Standing Position
JurisdictionSouth Dakota, USA (US-SD)
Regulatory ScopeData Protection & Privacy Regulation (10 modules, 67 sourced findings)
Regulator & FrameworkA functioning breach-notification regime and applicable federal FTC authority exist, but there is no comprehensive material/territorial scope regime or registration framework at state level.
Lawful Processing & Special DataGeneral lawful-processing regime is absent (red), but a sector-specific special-category development (genetic data) has emerged in 2026, warranting amber rather than uniform red.
Data Subject RightsComplete absence of a comprehensive consumer-rights regime at state level.
Controller/Processor DutiesBreach notification is a live, in-force obligation; all other accountability duties are absent at state level.
Primary Instruments CitedDataGuidance (secondary aggregator citing primary statute), IAPP, South Dakota, USA Official Instrument (recordinglaw.com data-breach-notification), South Dakota, USA Official Instrument (dataprotection.gi south-dakota-usa), South Dakota Attorney General's Office
Last Confirmed / Updated (37 sources in cumulative register)

#

A functioning breach-notification regime and applicable federal FTC authority exist, but there is no comprehensive material/territorial scope regime or registration framework at state level.

Primary frameworkFederal FTC Act Section 5 + South Dakota data-breach notification statute (SDCL §22-40-1 et seq.)
Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberA functioning breach-notification regime and applicable federal FTC authority exist, but there is no comprehensive material/territorial scope regime or registration framework at state level.

Sub-modules (5)

Regulator and authorityAmber

No dedicated South Dakota DPA exists; the South Dakota Attorney General exercises general consumer-protection and breach-notification enforcement, while the FTC is the de facto federal privacy regulator reaching South Dakota-based conduct.

Claims (4):

  • South Dakota Attorney General exercises general consumer-protection and breach-notification enforcement authority absent a dedicated state privacy regulator No dedicated South Dakota data-protection authority exists; SD AG holds general consumer-protection/breach-notification authority while the FTC exercises federal Section 5 authority reaching SD-based conduct. Baseline regulator-mapping finding; South Dakota lacks a dedicated privacy authority.
  • The South Dakota Attorney General is the de facto privacy enforcer in the absence of a dedicated state DPA.
  • South Dakota has no comprehensive consumer-privacy statute; data-protection matters are governed by the AG's general deceptive-practices authority and sector-specific federal law.
  • South Dakota Attorney General — The AG may prosecute breach-notification failures as deceptive acts under SDCL 37-24-6, with a civil penalty of up to $10,000 per day per violation plus attorney's fees

Act and instrumentsAmber

The FTC Act Section 5 baseline and South Dakota's 2018 breach-notification statute (SDCL §22-40-1 et seq.) constitute the operative instruments; South Dakota was one of the last two states to adopt a breach law.

Claims (6):

  • South Dakota data-breach notification statute is codified at SDCL §§22-40-19 to 22-40-26 (breach-notification-specific provisions), corrected from the initially miscited §22-40-1 et seq. Citation corrected per challenger fold f-002; confirmed by two independent T1 anchors (Justia, SD Legislature).
  • South Dakota breach-notification statute enactment was adopted in 2018, making South Dakota one of the last two US states to enact a data-breach notification law. Historical enactment context for the breach-notification statute.
  • FTC Act Section 5 provides the federal unfair/deceptive-practices baseline applicable to South Dakota-based conduct FTC Act Section 5 (federal) plus the SD breach-notification statute constitute the operative instruments for this jurisdiction. Federal baseline framework applicable absent a state comprehensive statute.
  • South Dakota's primary data-protection-adjacent instruments are the breach-notification act and the new Genetic Data Privacy Act, effective 2026-07-01.
  • South Dakota privacy legislative framework — South Dakota has no comprehensive consumer-privacy statute comparable to GDPR or US state omnibus laws; its only dedicated instruments are the breach-notification statute and the Genetic Data Privacy Act (effective 2026-07-01)
  • South Dakota Genetic Data Privacy Act (2026 SB 49) — privacy-policy, consent, security and deletion duties on direct-to-consumer genetic-testing companies

Material scopeRed

Material scope is limited to the breach-notification statute's definition of computerized personal information; no independently-verified statutory text defining broader material scope (e.g., general 'personal data' categories) was retrievable in this run.

Claims (2):

  • South Dakota has no comprehensive consumer-privacy statute, so there is no state-law consent standard for trackers, no registration/notification regime for controllers/processors, and no DPIA/DPO/ROPA requirements.
  • South Dakota breach-notification statute — any person or business that conducts business in the state and owns or licenses computerized personal or protected information of South Dakota residents

Territorial scopeRed

No independently verified statutory text on territorial application (e.g., extraterritorial reach to out-of-state controllers processing South Dakota residents' data) was retrievable in this run.

Claims (2):

  • South Dakota information holder — notify affected SD residents no later than 60 days from discovery of a breach of system security, regardless of the information holder's own location
  • South Dakota breach-notification statute — Applies to any person or business conducting business in South Dakota that owns or licenses computerized personal information of residents, with no minimum size threshold

Regulator registration and filingRed

Consistent with the absence of a comprehensive privacy statute, South Dakota imposes no general controller/processor registration or filing regime with a state privacy authority.

Claims (1):

  • South Dakota imposes no general controller/processor registration or filing regime No state privacy-authority registration/filing requirement exists. Absence-of-regime finding via negative evidence from IAPP tracker.

Key findings (1)

  • — source on file
Category narrative 71 words

South Dakota has no comprehensive state consumer-privacy statute and no dedicated state data-protection authority. The operative framework is (a) the federal FTC Act Section 5 unfair/deceptive-practices baseline, enforced by the FTC, and (b) South Dakota's own data-breach notification statute (SDCL Chapter 22-40), enforced by the South Dakota Attorney General under general consumer-protection authority. IAPP's comprehensive state privacy tracker does not list South Dakota among the states with enacted comprehensive privacy laws.

No periodic updates recorded in this cycle

Sources and claims (15)
  1. Probable Federal Trade Commission — South Dakota Attorney General exercises general consumer-protection and breach-notification enforcement authority absent a dedicated state privacy regulator No dedicated South Dakota data-protection authority exists; SD AG holds general consumer-protection/breach-notification authority while the FTC exercises federal Section 5 authority reaching SD-based conduct. Baseline regulator-mapping finding; South Dakota lacks a dedicated privacy authority. observed
  2. Confirmed Primary statutory record — South Dakota data-breach notification statute is codified at SDCL §§22-40-19 to 22-40-26 (breach-notification-specific provisions), corrected from the initially miscited §22-40-1 et seq. Citation corrected per challenger fold f-002; confirmed by two independent T1 anchors (Justia, SD Legislature).
  3. Probable DataGuidance (secondary aggregator citing primary statute) — South Dakota breach-notification statute enactment was adopted in 2018, making South Dakota one of the last two US states to enact a data-breach notification law. Historical enactment context for the breach-notification statute. observed
  4. Probable Federal Trade Commission — FTC Act Section 5 provides the federal unfair/deceptive-practices baseline applicable to South Dakota-based conduct FTC Act Section 5 (federal) plus the SD breach-notification statute constitute the operative instruments for this jurisdiction. Federal baseline framework applicable absent a state comprehensive statute. observed
  5. Probable IAPP — South Dakota imposes no general controller/processor registration or filing regime No state privacy-authority registration/filing requirement exists. Absence-of-regime finding via negative evidence from IAPP tracker. observed
  6. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/south-dakota-data-privacy-laws/data-breach-notification/ — South Dakota information holder — notify affected SD residents no later than 60 days from discovery of a breach of system security, regardless of the information holder's own location
  7. Probable https://dataprotection.gi/jurisdictions/south-dakota-usa/ — The South Dakota Attorney General is the de facto privacy enforcer in the absence of a dedicated state DPA.
  8. Probable RecordingLaw.com — South Dakota has no comprehensive consumer-privacy statute; data-protection matters are governed by the AG's general deceptive-practices authority and sector-specific federal law. observed
  9. Probable RecordingLaw.com — South Dakota's primary data-protection-adjacent instruments are the breach-notification act and the new Genetic Data Privacy Act, effective 2026-07-01. observed
  10. Probable South Dakota Attorney General's Office — South Dakota Attorney General — The AG may prosecute breach-notification failures as deceptive acts under SDCL 37-24-6, with a civil penalty of up to $10,000 per day per violation plus attorney's fees observed
  11. Probable South Dakota Attorney General's Office — South Dakota privacy legislative framework — South Dakota has no comprehensive consumer-privacy statute comparable to GDPR or US state omnibus laws; its only dedicated instruments are the breach-notification statute and the Genetic Data Privacy Act (effective 2026-07-01) observed
  12. Probable South Dakota Legislature — South Dakota breach-notification statute — Applies to any person or business conducting business in South Dakota that owns or licenses computerized personal information of residents, with no minimum size threshold observed
  13. Probable OpenAgreements — South Dakota has no comprehensive consumer-privacy statute, so there is no state-law consent standard for trackers, no registration/notification regime for controllers/processors, and no DPIA/DPO/ROPA requirements. observed
  14. Probable South Dakota Attorney General's Office — South Dakota Genetic Data Privacy Act (2026 SB 49) — privacy-policy, consent, security and deletion duties on direct-to-consumer genetic-testing companies observed
  15. Probable South Dakota Attorney General's Office — South Dakota breach-notification statute — any person or business that conducts business in the state and owns or licenses computerized personal or protected information of South Dakota residents observed

#

General lawful-processing regime is absent (red), but a sector-specific special-category development (genetic data) has emerged in 2026, warranting amber rather than uniform red.

Traffic-light rationale — AmberGeneral lawful-processing regime is absent (red), but a sector-specific special-category development (genetic data) has emerged in 2026, warranting amber rather than uniform red.

Sub-modules (4)

Lawful basesRed

No enumerated lawful bases for processing exist under South Dakota state law.

Claims (1):

  • South Dakota has not enacted any enumerated lawful-basis framework for data processing. Negative-evidence finding; no comprehensive statute exists to found lawful bases.

Special categoriesAmber

A 2026 South Dakota genetic-data protection bill was introduced to the Senate and subsequently reported as signed into law, representing an emerging special-category (genetic data) overlay; precise scope, obligations, and effective date are unverified.

Claims (3):

  • South Dakota's Genetic Data Privacy Act creates a distinct protection regime for genetic data, effective 2026-07-01.
  • South Dakota breach-notification statute and Genetic Data Privacy Act — The breach statute's definition of personal information includes health and biometric data for breach-trigger purposes; a separate Genetic Data Privacy Act (SB49) addresses genetic data from 2026-07-01
  • direct-to-consumer genetic testing company — A DTC genetic-testing company that violates the Genetic Data Privacy Act's consent, disclosure, security or privacy-notice duties is liable for a civil penalty of up to $5,000 per violation, recoverable only via AG petition to the court.

Pseudonymisation and anonymisationRed

No statutory pseudonymisation/anonymisation safe-harbour definitions exist at South Dakota state level.

Claims (2):

  • SB 49 (SDCL Ch. 37-24) — 'de-identified data' as genetic data that cannot reasonably be used to infer or be linked to an identifiable consumer; HIPAA-covered entities and business associates are expressly exempt from the Act
  • SB 49 requires notice (not consent) before sharing de-identified genetic data for research.

Key findings (1)

  • — source on file
Category narrative 56 words

South Dakota has not enacted a general lawful-basis, consent-threshold, or special-category framework of the GDPR/CCPA type. The one notable 2026 development is state legislation addressing genetic data, following a Senate bill on genetic data protection that was reported signed into law by the Governor; full statutory text and scope were not independently verified in this run.

Periodic update · new data 2026-10-25

South Dakota's Genetic Data Privacy Act, enacted as Senate Bill 49 and effective July 1, 2026, establishes the jurisdiction's first dedicated consent regime for a sensitive data category. The Act requires a direct-to-consumer genetic testing company to obtain the consumer's express consent before collecting, disclosing, or using the consumer's genetic data, with that express consent taking the form of an affirmative written response that may be captured electronically. The consent standard is layered: an initial express consent covers the company's own collection and use, while a separate, named-recipient consent is required for each additional transfer or disclosure of genetic data beyond the company's own vendors and service providers. This named-recipient structure means a single blanket consent cannot cover an unbounded set of future disclosures; each new recipient outside the company's direct service-provider relationships requires its own consent event.

The Act draws a clear line between identified and de-identified genetic data. Where data is de-identified, the Act requires only that the company give a clear and complete notice that such data may be shared with or disclosed to a third party for research purposes, consistent with the federal human-subjects research framework at 45 C.F.R. part 46; no separate consent is required for that de-identified sharing. This two-tier structure, consent for identified data and notice for de-identified research sharing, is the Act's central lawful-processing architecture.

The Act also expressly carves out protected health information collected by a HIPAA covered entity or business associate, so it operates as an addition to the jurisdiction's privacy landscape for a specific commercial context (direct-to-consumer testing) rather than as a general sensitive-data law reaching all genetic data collection in the state.

Outlook

The practical scope of the Act's consent architecture will depend on how direct-to-consumer genetic testing companies operating in South Dakota implement the named-recipient consent requirement in practice, particularly where data-sharing arrangements involve multiple downstream recipients. No further legislative or regulatory activity on this topic was evidenced this period beyond the Act's July 1, 2026 effective date.

2 earlier distinct updates
Periodic update · new data 2026-10-11

South Dakota's lawful-processing landscape for a specific category of personal data, genetic data, tightened materially this cycle with SB 49, the Genetic Data Privacy Act, entering force on 1 July 2026. The statute, read directly from the South Dakota Legislature's enrolled bill text, requires a direct-to-consumer genetic testing company to obtain express consent before collecting, disclosing, or using a consumer's genetic data. The consent standard is defined specifically as an affirmative written response, which the statute permits to be captured electronically, a formulation that sets a comparatively precise bar relative to the looser notice-and-opt-out standards found in many general-purpose state privacy statutes. The Act further requires separate express consent for each transfer of genetic data beyond the company's own vendors or service providers, meaning a single blanket consent obtained at the point of testing does not, on its own, authorise onward transfer to a new category of third party; each additional transfer destination appears to require its own consent event.

The Act also establishes a definitional boundary relevant to lawful processing: de-identified genetic data, defined as data that cannot reasonably be used to infer or be linked to an identifiable consumer, falls outside certain of the Act's obligations, consistent with the general pattern in US state privacy statutes of relaxing obligations once data no longer identifies a natural person. The Act expressly exempts HIPAA-covered entities and their business associates from its scope, a carve-out that is significant because many direct-to-consumer genetic testing companies operate adjacent to, but not strictly within, HIPAA's covered-entity definition; a company able to characterise itself as HIPAA-covered, or as a business associate of one, would fall outside SB 49's consent regime entirely, a boundary question that is likely to matter in practice.

This is a structural development in the sense that South Dakota, which previously lacked any consent-based regime for a specific sensitive-data category, now has one, confirmed and in force, specifically for genetic data. The Act reflects a broader, multi-state legislative pattern of sector-specific genetic-privacy statutes rather than omnibus general privacy law, and South Dakota's version follows that pattern by regulating a narrow entity category, direct-to-consumer genetic testing companies, rather than controllers or processors generally.

Outlook

The principal open question is how the HIPAA/business-associate exemption will be applied in practice to direct-to-consumer genetic testing companies that have some but not all of the characteristics of a covered entity, since the scope of that exemption will determine how many companies in this space are actually subject to the Act's consent regime. A second open question is how the separate-express-consent-per-transfer requirement will be operationalised by companies whose business models depend on data sharing with multiple categories of research or commercial partners beyond their immediate vendors and service providers.

Periodic update · new data 2026-09-28

South Dakota's treatment of special-category data tightened materially this cycle with the entry into force of the Genetic Data Privacy Act, SB49, on 1 July 2026. It is understood that the Act imposes a sectoral consent requirement specifically for genetic data: covered entities must obtain consent before genetic data is shared with third parties. This creates the states first explicit consent-based lawful-processing standard for a defined special category of data, genetic data, where previously no such state-level consent requirement existed for this category.

It is understood, at a somewhat more qualified confidence level than the consent requirement itself, that the Act additionally requires disclosure when de-identified genetic data is shared for research purposes. This disclosure obligation is distinct from the third-party-sharing consent requirement: it applies specifically to the research-sharing context and specifically to de-identified data, suggesting the legislature drew a deliberate line between the higher bar of affirmative consent for identifiable third-party sharing and a lower, disclosure-based bar for de-identified research use. This distinction, if borne out by the final codified text, would represent a considered, risk-calibrated approach to genetic-data lawful-processing rules rather than a blanket restriction.

Before this cycle, South Dakota had no dedicated special-category data statute of any kind; genetic data, like other categories of sensitive personal information, was governed only indirectly, if at all, through the general breach-notification law's security-incident framework, which does not itself impose any lawful-processing or consent standard for the collection or sharing of sensitive data in the ordinary course of business. The Genetic Data Privacy Act therefore represents a genuinely new lawful-processing regime for this jurisdiction, not an amendment to an existing one.

The scope of covered entities and the precise definition of genetic data under the Act, including whether the definition extends to raw biological samples, derived genetic profiles, or both, was not fully detailed in the evidence available this cycle, representing an area for further research to fully characterize the reach of the new consent and disclosure requirements.

Outlook

The principal forward-looking task for this module is independent verification of the Act's consent and disclosure mechanics against the final codified statutory text, since the disclosure-for-research-sharing provision is currently evidenced only to a Probable confidence level. Observing how covered entities, including direct-to-consumer genetic testing companies operating in or serving South Dakota residents, implement consent-capture mechanisms in practice over the coming cycles will also help clarify how the new lawful-processing standard functions outside the statutory text itself.

Sources and claims (8)
  1. Probable IAPP — South Dakota has not enacted any enumerated lawful-basis framework for data processing. Negative-evidence finding; no comprehensive statute exists to found lawful bases. observed
  2. Confirmed https://mylrc.sdlegislature.gov/api/Documents/SessionLaw/306540.pdf?Year=2026 — SB 49 introduces an express-consent requirement for DTC genetic testing companies, effective 2026-07-01.
  3. Confirmed https://mylrc.sdlegislature.gov/api/Documents/306539.pdf — direct-to-consumer genetic testing company — express consent (affirmative written response, capturable electronically) to collect, disclose, or use a consumer's genetic data, including separate express consent for each transfer beyond the company's own vendors/service providers
  4. Confirmed https://mylrc.sdlegislature.gov/api/Documents/306539.pdf — SB 49 (SDCL Ch. 37-24) — 'de-identified data' as genetic data that cannot reasonably be used to infer or be linked to an identifiable consumer; HIPAA-covered entities and business associates are expressly exempt from the Act
  5. Confirmed South Dakota Legislature — SB 49 requires notice (not consent) before sharing de-identified genetic data for research. observed
  6. Uncertain RecordingLaw.com — South Dakota's Genetic Data Privacy Act creates a distinct protection regime for genetic data, effective 2026-07-01. observed
  7. Probable KOTA TV — South Dakota breach-notification statute and Genetic Data Privacy Act — The breach statute's definition of personal information includes health and biometric data for breach-trigger purposes; a separate Genetic Data Privacy Act (SB49) addresses genetic data from 2026-07-01 observed
  8. Confirmed South Dakota Legislature — direct-to-consumer genetic testing company — A DTC genetic-testing company that violates the Genetic Data Privacy Act's consent, disclosure, security or privacy-notice duties is liable for a civil penalty of up to $5,000 per violation, recoverable only via AG petition to the court. observed

#

Complete absence of a comprehensive consumer-rights regime at state level.

Traffic-light rationale — RedComplete absence of a comprehensive consumer-rights regime at state level.

Sub-modules (5)

Access rightRed

No general state-law subject-access-request right exists.

Claims (2):

  • South Dakota confers no general state-law data subject rights No access, rectification, erasure, restriction, objection, or portability rights exist under SD state law absent a comprehensive consumer-privacy statute. Single claim covers four DSR sub-modules (access, rectification/erasure, restriction/objection, portability) since all rest on the same absence-of-comprehensive-statute finding.
  • South Dakota data-subject-rights regime — South Dakota confers no general state-law access, rectification, erasure, restriction, objection or portability right on data subjects

Rectification and erasureRed

No general state-law rectification or erasure right exists.

Claims (1):

  • direct-to-consumer genetic testing company — provide a process enabling consumers to access their account and genetic data and to request deletion of their account or destruction of their biological sample

Restriction and objectionRed

No general state-law restriction or objection (including profiling opt-out) right exists.

Data portabilityRed

No general state-law portability right exists.

Claims (1):

  • social media company (>100 million active monthly users, not primarily religious/charitable) — on user request, provide the user's personal data in a portable, readily-usable format, and allow the user to export all or a chosen subset of their social-graph data to other social media services via a transparent interoperability interface

Deadlines and response windowsRed

No statutory response-window framework exists for consumer rights requests, as no underlying rights regime exists to attach deadlines to.

Key findings (1)

  • — source on file
Category narrative 30 words

South Dakota confers no general state-law rights of access, rectification, erasure, restriction, objection, or portability to consumers with respect to personal data, as no comprehensive consumer-privacy statute has been enacted.

Periodic update · new data 2026-10-11

South Dakota's data-subject-rights landscape tightened on two separate tracks this cycle, one already in force and one enacted but not yet effective. On the first track, SB 49, the Genetic Data Privacy Act, in force from 1 July 2026, requires a direct-to-consumer genetic testing company to provide a process enabling consumers to access their account and genetic data, and to request deletion of their account or destruction of their biological sample. This access-and-deletion right is specific to genetic data and to the direct-to-consumer genetic testing sector; it does not establish a general right of access or erasure applicable to personal data held by controllers across sectors. The finding is read from secondary commentary rather than the statute's own text as independently verified this cycle, so while treated as confirmed in substance given the primary source confirming the Act generally, the specific access-and-deletion mechanics rest on a lower-tier source.

On the second track, SB 111, signed on 10 March 2026, establishes a data-portability and interoperability right that had not yet commenced as at this cycle, with a legal effective date of 1 July 2027. The right applies specifically to social-media companies with more than 100 million active monthly users, a materiality threshold that confines the obligation to a small number of large platforms rather than applying generally across the social-media sector. On user request, a covered company must provide the user's personal data in a portable, readily usable format, and must separately allow the user to export all or a chosen subset of their social-graph data to other social-media services via a transparent interoperability interface. This is a confirmed finding, drawn directly from the South Dakota Legislature's enrolled bill text, though its future effective date means the obligation itself has not yet commenced and covered companies retain a compliance-build runway before the duty becomes operative.

The distinction between these two tracks, immediate genetic-data access and deletion rights now in force, and future-dated social-media portability and interoperability rights not yet in force, illustrates South Dakota's incremental, sector-by-sector approach to building out data-subject rights rather than adopting a general, omnibus access-and-portability framework applicable across all personal data categories.

Outlook

For the genetic-data access and deletion right already in force, the open question is how direct-to-consumer genetic testing companies are operationalising the required access, account-deletion, and biological-sample-destruction processes in practice, a matter on which this cycle's evidence base does not provide direct insight. For the social-media portability and interoperability right, the relevant period for monitoring compliance-build activity runs between now and the 1 July 2027 effective date, at which point the obligation will commence for companies exceeding the 100-million-monthly-active-user threshold.

Sources and claims (4)
  1. Probable IAPP — South Dakota confers no general state-law data subject rights No access, rectification, erasure, restriction, objection, or portability rights exist under SD state law absent a comprehensive consumer-privacy statute. Single claim covers four DSR sub-modules (access, rectification/erasure, restriction/objection, portability) since all rest on the same absence-of-comprehensive-statute finding. observed
  2. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/south-dakota-data-privacy-laws/ — direct-to-consumer genetic testing company — provide a process enabling consumers to access their account and genetic data and to request deletion of their account or destruction of their biological sample
  3. Confirmed South Dakota Legislature — social media company (>100 million active monthly users, not primarily religious/charitable) — on user request, provide the user's personal data in a portable, readily-usable format, and allow the user to export all or a chosen subset of their social-graph data to other social media services via a transparent interoperability interface observed
  4. Probable South Dakota Attorney General's Office — South Dakota data-subject-rights regime — South Dakota confers no general state-law access, rectification, erasure, restriction, objection or portability right on data subjects observed

#

Breach notification is a live, in-force obligation; all other accountability duties are absent at state level.

Primary frameworkSouth Dakota data-breach notification statute (SDCL §22-40-1 et seq.)
Supervisory authoritySouth Dakota Attorney General
Traffic-light rationale — AmberBreach notification is a live, in-force obligation; all other accountability duties are absent at state level.

Sub-modules (7)

Accountability & DPIARed

No DPIA or general accountability-principle statute exists at state level.

Claims (2):

  • South Dakota imposes no general accountability, DPIA, DPO, RoPA, joint-controller, security-measures, or retention/disposal duties Absent from state law outside the breach-notification statute. Single claim covers six controller/processor-duty sub-modules; breach notification is the sole operative duty, tracked separately.
  • South Dakota imposes no state-law DPIA duty, no DPO-appointment threshold, no mandatory processor-contract terms and no records-of-processing requirement, apart from the narrow Genetic Data Privacy Act confidentiality duty on DTC genetic-testing companies effective 2026-07-01.

DPO requirementsRed

No DPO appointment threshold or independence requirement exists at state level.

Ropa requirementsRed

No records-of-processing-activities requirement exists at state level.

Joint controller arrangementsRed

No joint-controller statutory framework exists at state level.

Security measuresRed

No general technical/organisational security-measures statute exists beyond the implicit expectations underlying the breach-notification law.

Claims (1):

  • direct-to-consumer genetic testing company — take measures to safeguard the confidentiality, integrity, privacy and security of a consumer's genetic data, including publishing a privacy policy and prominent public privacy notice

Breach notificationAmber

South Dakota's breach-notification statute requires disclosure of security breaches compromising unencrypted computerized personal information to affected South Dakota residents; precise notification deadlines and AG-notice thresholds were not independently verified from full statutory text in this run.

Claims (9):

  • South Dakota data-breach notification statute requires disclosure of security breaches compromising unencrypted computerized personal information to affected SD residents Breach-notification duty codified at SDCL §§22-40-19 to 22-40-26 (corrected citation); precise notification deadline and AG-notice threshold not independently verified from full statutory text in this run. Citation corrected per challenger fold f-002.
  • South Dakota information holder — disclose a breach of system security to any affected South Dakota resident no later than 60 days from discovery, unless a longer period is required by legitimate law-enforcement needs
  • South Dakota information holder — notify the Attorney General where a breach affects more than 250 South Dakota residents; an information holder regulated by federal law (HIPAA, GLBA) is deemed compliant with SD law if it follows its federal breach-notification procedures
  • SD breach notification must occur within 60 days of discovery.
  • South Dakota's breach-notification statute requires notification to affected residents within 60 days of discovery, subject to a law-enforcement delay.
  • AG notification is required where a breach affects more than 250 South Dakota residents; HIPAA/GLBA-compliant entities are deemed compliant.
  • South Dakota breach-notification statute — Notification of affected residents no later than 60 days from discovery (subject to law-enforcement delay); AG notification required where more than 250 residents are affected; HIPAA/GLBA-regulated entities deemed compliant via their federal regime
  • South Dakota breach-notification statute (SDCL 22-40-20) — disclosure of a breach of system security to affected South Dakota residents not later than 60 days from discovery, extendable 30 days after a law-enforcement delay ends
  • South Dakota breach-notification statute — disclosure to the Attorney General by mail or electronic mail where a breach exceeds 250 South Dakota residents

Retention and disposalRed

No general statutory retention-limit or disposal-duty framework exists at state level.

Key findings (1)

  • — source on file
Category narrative 43 words

Outside of breach notification, South Dakota imposes no general statutory duties on controllers or processors regarding DPIAs, DPO appointment, records of processing, joint-controller arrangements, minimum security-measure standards, or retention/disposal limits. The breach-notification statute (SDCL §22-40-1 et seq.) is the one operative duty-bearing instrument.

No periodic updates recorded in this cycle

Sources and claims (12)
  1. Probable IAPP — South Dakota imposes no general accountability, DPIA, DPO, RoPA, joint-controller, security-measures, or retention/disposal duties Absent from state law outside the breach-notification statute. Single claim covers six controller/processor-duty sub-modules; breach notification is the sole operative duty, tracked separately. observed
  2. Probable Primary statutory record — South Dakota data-breach notification statute requires disclosure of security breaches compromising unencrypted computerized personal information to affected SD residents Breach-notification duty codified at SDCL §§22-40-19 to 22-40-26 (corrected citation); precise notification deadline and AG-notice threshold not independently verified from full statutory text in this run. Citation corrected per challenger fold f-002.
  3. Confirmed https://mylrc.sdlegislature.gov/api/Documents/306539.pdf — direct-to-consumer genetic testing company — take measures to safeguard the confidentiality, integrity, privacy and security of a consumer's genetic data, including publishing a privacy policy and prominent public privacy notice
  4. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/south-dakota-data-privacy-laws/data-breach-notification/ — South Dakota information holder — disclose a breach of system security to any affected South Dakota resident no later than 60 days from discovery, unless a longer period is required by legitimate law-enforcement needs
  5. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/south-dakota-data-privacy-laws/data-breach-notification/ — South Dakota information holder — notify the Attorney General where a breach affects more than 250 South Dakota residents; an information holder regulated by federal law (HIPAA, GLBA) is deemed compliant with SD law if it follows its federal breach-notification procedures
  6. Probable https://www.recordinglaw.com/us-laws/data-privacy-laws/south-dakota-data-privacy-laws/data-breach-notification/ — SD breach notification must occur within 60 days of discovery.
  7. Probable Legal 500 — South Dakota's breach-notification statute requires notification to affected residents within 60 days of discovery, subject to a law-enforcement delay. observed
  8. Probable https://openagreements.org/practice-guides/privacy/us/south-dakota — AG notification is required where a breach affects more than 250 South Dakota residents; HIPAA/GLBA-compliant entities are deemed compliant.
  9. Probable South Dakota Legislature — South Dakota breach-notification statute — Notification of affected residents no later than 60 days from discovery (subject to law-enforcement delay); AG notification required where more than 250 residents are affected; HIPAA/GLBA-regulated entities deemed compliant via their federal regime observed
  10. Probable OpenAgreements — South Dakota imposes no state-law DPIA duty, no DPO-appointment threshold, no mandatory processor-contract terms and no records-of-processing requirement, apart from the narrow Genetic Data Privacy Act confidentiality duty on DTC genetic-testing companies effective 2026-07-01. observed
  11. Probable South Dakota Legislature — South Dakota breach-notification statute (SDCL 22-40-20) — disclosure of a breach of system security to affected South Dakota residents not later than 60 days from discovery, extendable 30 days after a law-enforcement delay ends observed
  12. Probable South Dakota Attorney General's Office — South Dakota breach-notification statute — disclosure to the Attorney General by mail or electronic mail where a breach exceeds 250 South Dakota residents observed

#

No state-level transfer regime exists; federal-level mechanisms are out of scope for a state JID.

Traffic-light rationale — RedNo state-level transfer regime exists; federal-level mechanisms are out of scope for a state JID.

Sub-modules (6)

Transfer mechanismsRed

No state-specific transfer mechanism exists.

Claims (2):

  • South Dakota has no state-specific cross-border transfer, adequacy, SCC/BCR, TIA, or data-localisation regime Cross-border transfer analysis operates at the federal level only; no state mechanism exists. Single claim covers six cross-border sub-modules; not applicable at state level by design.
  • South Dakota has no state-specific cross-border transfer mechanism, adequacy regime, SCC/BCR framework, transfer-impact-assessment requirement or data-localisation mandate; genetic-data transfers under SB 49 (requiring separate express consent) are the only sectoral exception.

Adequacy receivedRed

Not applicable at state level; adequacy determinations are a federal/EU-level construct.

Adequacy grantedRed

Not applicable at state level.

SCCs and BCRsRed

No state-level SCC/BCR framework exists.

Transfer impact assessmentRed

No state-level TIA requirement exists.

Data localisationRed

No state-level data-localisation mandate exists.

Key findings (1)

  • — source on file
Category narrative 35 words

South Dakota has no state-specific cross-border transfer mechanism, adequacy regime, SCC/BCR framework, transfer-impact-assessment requirement, or data-localisation mandate. Any cross-border transfer analysis (e.g., EU-U.S. Data Privacy Framework) operates at the federal level, outside this state-level baseline.

Sources and claims (2)
  1. Probable IAPP — South Dakota has no state-specific cross-border transfer, adequacy, SCC/BCR, TIA, or data-localisation regime Cross-border transfer analysis operates at the federal level only; no state mechanism exists. Single claim covers six cross-border sub-modules; not applicable at state level by design. observed
  2. Probable dataprotection.gi — South Dakota has no state-specific cross-border transfer mechanism, adequacy regime, SCC/BCR framework, transfer-impact-assessment requirement or data-localisation mandate; genetic-data transfers under SB 49 (requiring separate express consent) are the only sectoral exception. observed

#

No independent state-level sectoral overlays exist except the emerging genetic-data statute; federal sectoral law is out of scope for this JID.

Traffic-light rationale — AmberNo independent state-level sectoral overlays exist except the emerging genetic-data statute; federal sectoral law is out of scope for this JID.

Sub-modules (7)

Financial sector overlayRed

No South Dakota-specific financial-sector privacy overlay identified beyond federal GLBA (out of scope for this JID).

Claims (2):

  • South Dakota has no independent state-level sectoral privacy overlays Federal sectoral statutes (HIPAA, GLBA, COPPA) apply but are out of scope for this state JID; no SD-specific financial, telecoms, employment, credit, education, or insurance privacy overlay identified. Covers six sectoral sub-modules besides health, which is tracked separately (amber) due to the genetic-data overlay.
  • South Dakota breach-notification statute (SDCL 22-40-26) — an information holder regulated by federal law (HIPAA or GLBA) that notifies affected South Dakota residents under its federal regulator's breach regime

Health sector overlayAmber

No South Dakota-specific health-sector privacy overlay beyond federal HIPAA (out of scope), except the 2026 genetic-data protection legislation which touches health-adjacent genetic information.

Claims (1):

  • SB 49 exempts HIPAA-covered PHI, layering on top of rather than displacing HIPAA.

Telecoms and eprivacyRed

No South Dakota-specific telecoms/ePrivacy overlay identified.

Employment dataRed

No South Dakota-specific employment-data privacy overlay identified.

Credit and scoringRed

No South Dakota-specific credit/scoring privacy overlay identified beyond federal FCRA (out of scope).

educationRed

No South Dakota-specific education-sector privacy overlay identified.

insuranceRed

No South Dakota-specific insurance-sector privacy overlay identified.

Key findings (1)

  • — source on file
Category narrative 56 words

Federal sectoral statutes (HIPAA, GLBA, COPPA) apply to covered entities operating in South Dakota but are federal-level frameworks properly attributed to the US federal JID rather than this state baseline. The notable 2026 South Dakota-specific sectoral development is genetic-data protection legislation, apparently targeting direct-to-consumer genetic testing/analysis, paralleling similar statutes in other states; full scope is unverified.

Periodic update · new data 2026-10-25

The Genetic Data Privacy Act is this period's clearest sectoral development in South Dakota, and its interaction with the existing HIPAA framework is the key structural feature to track. The Act does not apply to protected health information collected by a covered entity or business associate as those terms are defined under HIPAA. This means the Act's reach is confined to genetic data collected in the direct-to-consumer testing context, which typically falls outside traditional HIPAA-covered relationships because the testing company is usually not itself a covered entity or business associate acting on behalf of one. The practical effect is a layering rather than a displacement: HIPAA continues to govern genetic data collected within a covered healthcare relationship, while the new Act governs the commercial direct-to-consumer testing channel that HIPAA does not reach.

This sectoral carve-out is consistent with a broader pattern across many state genetic-privacy statutes, which are typically drafted to target the direct-to-consumer testing industry specifically rather than to create a general genetic-data law applicable to all contexts in which genetic information is collected. The Act's own health-sector overlay provision makes this scope explicit rather than leaving it to inference, which reduces the risk of a company mistakenly believing the Act displaces its existing HIPAA compliance obligations or, conversely, mistakenly believing HIPAA compliance alone satisfies the new Act's express-consent and named-recipient disclosure requirements.

Outlook

The key open question is how direct-to-consumer genetic testing companies with business arrangements that straddle the HIPAA/non-HIPAA line are instructed to apply both regimes concurrently where a single data flow could plausibly touch both. No additional sectoral guidance beyond the Act's own HIPAA carve-out was identified this period.

1 earlier distinct update
Periodic update · new data 2026-09-28

The Genetic Data Privacy Act, SB49, functions this cycle as a new health-adjacent sectoral overlay specifically targeting the direct-to-consumer genetic testing industry and any other entity that collects, processes or shares genetic data in connection with South Dakota residents. Signed on 23 March 2026 and in force since 1 July 2026, the Act adds new sections to SDCL Chapter 37-24 establishing consent, disclosure, access, deletion and biological-sample-destruction obligations specific to this sector, discussed in greater detail under the lawful-processing and data-subject-rights modules respectively.

As a sectoral matter, the significance of the Act lies in its targeting of an industry, direct-to-consumer genetic testing and related genetic-data services, that had not previously been subject to any dedicated state-level data-protection statute in South Dakota beyond the general breach-notification law's security-incident framework. The genetic-testing sector nationally has drawn increasing legislative attention given the sensitivity of the data involved, its permanence, its relevance to biological relatives beyond the individual tested, and its potential use in contexts such as law enforcement, insurance underwriting or research, all of which the new consent and disclosure requirements appear designed to address at least partially.

The Act's research-sharing disclosure provision, requiring disclosure when de-identified genetic data is shared for research purposes, is particularly relevant to entities operating in or partnering with the genetic-research sector, since it establishes a transparency obligation specifically calibrated to that use case, distinct from the higher consent bar applied to third-party commercial sharing.

No other sector-specific data-protection development, such as a health-data statute beyond genetics, a financial-sector-specific privacy overlay, or an education-sector privacy statute, was identified for South Dakota this cycle.

Outlook

The genetic-testing sector operating in South Dakota should be expected to generate the primary compliance activity to watch under this new statute over the coming cycles, given that it is the sector most directly targeted by the Act's substantive obligations. Whether the legislature extends comparable sectoral treatment to other categories of especially sensitive data, such as biometric data more broadly or health data outside the genetic context, in a future session remains an open question this cycle's evidence does not resolve.

Sources and claims (3)
  1. Probable DataGuidance — South Dakota has no independent state-level sectoral privacy overlays Federal sectoral statutes (HIPAA, GLBA, COPPA) apply but are out of scope for this state JID; no SD-specific financial, telecoms, employment, credit, education, or insurance privacy overlay identified. Covers six sectoral sub-modules besides health, which is tracked separately (amber) due to the genetic-data overlay. observed
  2. Confirmed South Dakota Legislature — SB 49 exempts HIPAA-covered PHI, layering on top of rather than displacing HIPAA. observed
  3. Probable South Dakota Attorney General's Office — South Dakota breach-notification statute (SDCL 22-40-26) — an information holder regulated by federal law (HIPAA or GLBA) that notifies affected South Dakota residents under its federal regulator's breach regime observed

#

No state-level adtech/commercial-privacy regime exists.

Traffic-light rationale — RedNo state-level adtech/commercial-privacy regime exists.

Sub-modules (6)

Cookies and trackersRed

No state-level cookie/tracker consent law exists.

Claims (1):

  • South Dakota has no state-level adtech/commercial-privacy statute No cookie/tracker consent, dark-pattern, opt-out-signal, clean-room, cross-context-advertising, or direct-marketing-specific privacy law exists; federal TCPA/CAN-SPAM/FTC Section 5 govern. Covers six adtech sub-modules; absence-of-regime finding.

Dark patternsRed

No state-level dark-pattern prohibition exists.

Opt out signalsRed

No state-level universal opt-out-signal (e.g., GPC) recognition requirement exists.

Clean rooms and dcrRed

No state-level clean-room/data-collaboration-room rules exist.

Cross context advertisingRed

No state-level 'sale'/'share' cross-context-advertising framework exists.

Direct marketingRed

No state-level direct-marketing consent/suppression statute exists beyond general federal telemarketing/spam law.

Key findings (1)

  • — source on file
Category narrative 38 words

South Dakota has not enacted state-level cookie/tracker consent, dark-pattern, opt-out-signal (e.g., GPC), clean-room, cross-context-advertising, or direct-marketing-specific privacy statutes. General marketing communications remain governed by federal law (TCPA, CAN-SPAM) and FTC Section 5, which are outside this state-level baseline.

Sources and claims (1)
  1. Probable IAPP — South Dakota has no state-level adtech/commercial-privacy statute No cookie/tracker consent, dark-pattern, opt-out-signal, clean-room, cross-context-advertising, or direct-marketing-specific privacy law exists; federal TCPA/CAN-SPAM/FTC Section 5 govern. Covers six adtech sub-modules; absence-of-regime finding. observed

#

Broad algorithmic/biometric/ADM regime is absent (red), but the emerging genetic-data statute provides a partial, unverified signal.

Traffic-light rationale — AmberBroad algorithmic/biometric/ADM regime is absent (red), but the emerging genetic-data statute provides a partial, unverified signal.

Sub-modules (6)

Profiling restrictionsRed

No state-level profiling-restriction statute (Art 22-analogue) exists.

Claims (1):

  • South Dakota has no biometric, ADM-transparency, AI-risk-assessment, or profiling-restriction statute No Art-22-analogue profiling restriction, ADM transparency right, AI risk-assessment law, or biometric-data statute exists at state level. Covers four algorithmic-governance sub-modules; genetic_data sub-module tracked separately (amber).

Automated decision making transparencyRed

No state-level ADM transparency or explanation-right requirement exists.

AI risk assessmentsRed

No state-level AI-specific risk-assessment law exists.

Biometric regimeRed

No state-level biometric-data statute (facial recognition, fingerprint, gait) exists.

Claims (1):

  • South Dakota has no dedicated biometric-privacy statute and no consent requirement for collecting biometric identifiers; biometric identifiers fall within 'personal information' for the general breach-notification statute only.

Genetic dataAmber

A South Dakota genetic-data protection bill was introduced to the Senate in early 2026 and reportedly signed into law by the Governor; precise scope (e.g., direct-to-consumer genetic testing companies), consent requirements, and effective date were not independently verified from full statutory text in this run.

State surveillance carveoutsRed

No South Dakota-specific state-surveillance carveout statute was identified in this run.

Key findings (1)

  • — source on file
Category narrative 41 words

South Dakota has not enacted a biometric-privacy statute, AI-specific risk-assessment law, or automated-decision-making transparency requirement applicable to private-sector processing. The 2026 genetic-data protection legislation is the one relevant development, touching the genetic-data sub-module; its interaction with biometric/ADM governance is otherwise unverified.

No periodic updates recorded in this cycle

Sources and claims (4)
  1. Probable Primary statutory record — South Dakota Senate Bill 49 (Genetic Data Privacy Act) was signed into law by Governor Larry Rhoden and became effective SB49, codified at SDCL §§37-24-59 to 37-24-64, effective July 1, 2026; applies to direct-to-consumer genetic-testing companies, requiring a privacy policy and consent for collection/use/disclosure of genetic data, plus consumer rights to access, delete data/account, and require destruction of biological samples, enforced via AG civil penalties. Detail enriched per challenger fold f-001: bill number, codification, effective date, scope and rights confirmed via Hunton Andrews Kurth and OpenAgreements, cross-verified against SD AG press release.
  2. Probable Primary statutory record — South Dakota Genetic Data Privacy Act (SB49) creates a health-adjacent sectoral overlay for direct-to-consumer genetic testing SB49 (SDCL §§37-24-59 to 37-24-64), effective July 1 2026, imposes privacy-policy, consent, and consumer-rights obligations on DTC genetic-testing companies, enforced by SD AG civil penalties. Detail enriched per challenger fold f-001, cross-referencing Genetic data claim CLM-USSD-2f7d3c99.
  3. Probable IAPP — South Dakota has no biometric, ADM-transparency, AI-risk-assessment, or profiling-restriction statute No Art-22-analogue profiling restriction, ADM transparency right, AI risk-assessment law, or biometric-data statute exists at state level. Covers four algorithmic-governance sub-modules; Genetic data sub-module tracked separately (amber). observed
  4. Probable RecordingLaw.com — South Dakota has no dedicated biometric-privacy statute and no consent requirement for collecting biometric identifiers; biometric identifiers fall within 'personal information' for the general breach-notification statute only. observed

#

No South Dakota-specific children's or vulnerable-groups data-protection regime exists.

Traffic-light rationale — RedNo South Dakota-specific children's or vulnerable-groups data-protection regime exists.

Sub-modules (5)

Age verificationRed

No state-level age-verification statute exists.

Claims (2):

  • South Dakota has no state-specific children's or vulnerable-groups data-protection statute No age-verification, parental-consent, minor-profiling, education-settings, or dependent-adults data-protection law exists beyond federal COPPA. Covers five children/vulnerable-groups sub-modules.
  • A covered platform whose regular trade or business is to create, host or make available material harmful to minors must implement reasonable age verification to confirm a user is at least 18, excluding general-purpose search engines, ISPs/affiliates and cloud service providers.

Minor profiling bansRed

No state-level minor-profiling ban exists.

Claims (1):

  • South Dakota received the first $9 million of its multistate settlement share from Meta Platforms over addictive-design harms to minors.

Education settingsRed

No state-level education-settings-specific data-protection rule was identified.

Dependent adultsRed

No state-level dependent-adults (elderly, mentally incapacitated) data-protection statute was identified.

Key findings (1)

  • — source on file
Category narrative 32 words

South Dakota has not enacted a state-specific children's online privacy, age-verification, parental-consent, minor-profiling, education-settings, or dependent-adults data-protection statute. Federal COPPA governs children's data processing at the federal level, outside this state-level baseline.

No new data since the standing brief. 1 periodic run re-emitted it unchanged.

Sources and claims (4)
  1. Probable IAPP — South Dakota has no state-specific children's or vulnerable-groups data-protection statute No age-verification, parental-consent, minor-profiling, education-settings, or dependent-adults data-protection law exists beyond federal COPPA. Covers five children/vulnerable-groups sub-modules. observed
  2. Confirmed South Dakota Attorney General's Office — South Dakota received the first $9 million of its multistate settlement share from Meta Platforms over addictive-design harms to minors. observed
  3. Confirmed South Dakota Legislative Research Council — A covered platform whose regular trade or business is to create, host or make available material harmful to minors must implement reasonable age verification to confirm a user is at least 18, excluding general-purpose search engines, ISPs/affiliates and cloud service providers. observed
  4. Probable agegating.org — South Dakota children's online-privacy legislative landscape — South Dakota has not enacted a children's design-code law or a social-media minor-access law; an app-store age-verification/parental-consent bill (HB 1275, 2026) passed the House 50-17 but was defeated in a Senate committee in March 2026. observed

#

Federal enforcement machinery is robust; state-specific enforcement activity and capacity data are thin, and no private right of action was confirmed.

Primary frameworkFTC Act Section 5 + South Dakota breach-notification statute
Supervisory authorityFederal Trade Commission
Traffic-light rationale — AmberFederal enforcement machinery is robust; state-specific enforcement activity and capacity data are thin, and no private right of action was confirmed.

Sub-modules (6)

Regulator powers and penaltiesAmber

The FTC can pursue injunctive relief, mandated compliance programs, and civil penalties for order violations; the South Dakota AG enforces breach-notification and consumer-protection law under general state authority.

Claims (6):

  • Federal Trade Commission can pursue injunctive relief, mandated compliance programs, and civil penalties for order violations FTC Section 5 enforcement powers reaching South Dakota-based conduct. Federal enforcement machinery applicable to SD-based conduct.
  • South Dakota Attorney General enforces breach-notification and consumer-protection law, including via multistate NAAG-coordinated actions SD AG general consumer-protection authority plus breach-notification enforcement, often coordinated multistate via NAAG. State enforcement authority operating through general consumer-protection statute and NAAG coordination.
  • Attorney General (South Dakota) — civil penalties not exceeding $5,000 per violation for violation of the Genetic Data Privacy Act
  • SB 49 carries a $5,000-per-violation AG civil penalty.
  • The South Dakota AG may prosecute breach-notification failures as deceptive acts, recovering up to $10,000 per day per violation.
  • South Dakota breach-notification law — criminal penalties for failing to disclose a breach; no private right of action

Enforcement activity indexRed

No South Dakota-specific 12-month enforcement-activity index (major decisions, fines) was identified in this run.

Claims (2):

  • AG Jackley announced South Dakota received the first $9 million payment from Meta Platforms under the multistate settlement on 2026-10-26.
  • South Dakota reached a $15 million settlement with Roblox Corporation on 2026-07-13.

Regulator funding and capacityRed

No South Dakota AG privacy-unit funding or headcount data was identified in this run.

Collective redress and class actionsRed

No South Dakota-specific collective-redress or class-action mechanism specific to data-protection claims was identified.

Private right of actionAmber

South Dakota's breach-notification statute does not appear to create an express private right of action; enforcement responsibility rests with the Attorney General, though this was not independently confirmed against full statutory text.

Claims (5):

  • South Dakota breach-notification statute does not appear to create an express private right of action; enforcement responsibility rests with the Attorney General (not independently confirmed against full statutory text). Unverified negative finding on private right of action; flagged as open question in self_audit.
  • SD privacy statutes are AG-enforced only; no private right of action.
  • South Dakota's breach-notification statute provides no private right of action.
  • South Dakota breach-notification statute — Does not confer a private right of action on affected individuals
  • South Dakota Attorney General — Enforcement of the Genetic Data Privacy Act runs exclusively through the Attorney General, who alone may petition a court to impose the civil penalty; there is no private right of action for individual consumers.

Recent developments 180dAmber

Within the preceding 180 days, the principal South Dakota development is the introduction and reported signing into law of a genetic-data protection bill (reported March 2026).

Claims (1):

  • South Dakota genetic-data protection legislation (SB49) was introduced and signed into law within the preceding 180 days Reported March 2026 signing, now confirmed effective July 1, 2026, per challenger fold f-001. Most material recent development this cycle; enriched via challenger fold f-001.

Key findings (1)

  • — source on file
Category narrative 62 words

The FTC holds broad federal investigative and enforcement powers under Section 5 reaching South Dakota-based conduct, while the South Dakota Attorney General enforces the state's breach-notification statute and general consumer-protection law, including through multistate NAAG-coordinated actions. The most significant 2026 South Dakota-specific development is the genetic-data protection bill signed into law; no South Dakota-specific enforcement-activity index or regulator funding/capacity data was identified.

Periodic update · new data 2026-11-04

The Attorney General announced on 26 October 2026 that South Dakota had received the first $9 million payment from Meta Platforms, Inc. under the multistate settlement, with the funds placed in the Consumer Protection Fund pending legislative allocation. This followed the state's $15 million settlement with Roblox Corporation on 13 July 2026, funding the Internet Crimes Against Children Task Force and an online-safety campaign.

Outside these settlements, the Attorney General retains standing authority to pursue breach-notification failures as deceptive acts, with civil penalties of up to $10,000 per day per violation plus attorney's fees. South Dakota's breach-notification statute does not create a private right of action, so redress for breach failures runs through the Attorney General rather than through individual suits.

Outlook

The two settlements together represent the most active enforcement period for the office in this area, and the pattern of directing recovered funds to institutional child-safety purposes rather than to affected individuals is likely to continue as further settlement tranches arrive.

3 earlier distinct updates
Periodic update · new data 2026-10-25

South Dakota's enforcement architecture for data-protection matters remains Attorney-General-led and civil in character, with no private right of action created by either of the state's two principal data-protection statutes. The pre-existing breach-notification statute allows the Attorney General to prosecute breach-notification failures as deceptive acts and to recover a civil penalty of up to $10,000 per day per violation, plus attorney's fees. The new Genetic Data Privacy Act adds a parallel but distinct enforcement track: its enforcement provision authorizes the Attorney General to petition for a civil penalty of up to $5,000 per violation for breaches of the Act's express-consent, named-recipient-disclosure, and de-identified-data-notice duties.

The two penalty structures differ meaningfully in scale and triggering logic. The breach-notification penalty accrues per day per violation, which can compound quickly for an unresolved or ongoing notification failure, while the genetic-data penalty is a flat per-violation amount without the same daily-accrual mechanism. Both, however, share the same structural feature: enforcement runs exclusively through the Attorney General's office, and no South Dakota resident has an independent statutory cause of action to sue a company directly for either a breach-notification failure or a Genetic Data Privacy Act violation. This consolidates enforcement discretion entirely with the state's chief law-enforcement officer rather than distributing it to private litigants or a dedicated privacy regulator, of which South Dakota has none.

Outlook

Whether the Attorney General has brought, or intends to bring, any enforcement action under either statute was not confirmed this period. The absence of a private right of action under both statutes means that the practical bite of this enforcement architecture depends entirely on Attorney General enforcement priorities and resources, a variable not observable from this period's sourcing.

Periodic update · new data 2026-10-11

South Dakota's enforcement architecture for data-protection matters gained a new, sector-specific civil-penalty mechanism this cycle. The Attorney General may impose civil penalties not exceeding 5,000 USD per violation of the Genetic Data Privacy Act, SB 49, which entered force on 1 July 2026. This finding is sourced to a single law-firm commentary piece restating the statutory penalty figure, rather than to the statute's own enforcement section as independently verified this cycle, and is accordingly read as probable rather than confirmed; it is nonetheless consistent with the Act's broader effective date and general shape as confirmed from the primary legislative text.

This per-violation penalty structure is notable for its specificity: a 5,000 USD cap per violation, applied to a narrowly defined sectoral statute governing direct-to-consumer genetic testing companies, is a materially different enforcement posture from a general-purpose civil-penalty regime applicable across a broader population of controllers. The Attorney General's enforcement role here is consistent with South Dakota's general approach to data-protection enforcement, which proceeds through Attorney-General authority under sectoral statutes rather than through a dedicated data-protection authority exercising broader supervisory powers.

The Genetic Data Privacy Act's enforcement mechanism should be read alongside South Dakota's standing breach-notification enforcement architecture, under which the Attorney General receives notification of breaches affecting more than 250 residents, though no distinct civil-penalty figure for breach-notification violations was identified in this cycle's evidence base. The emergence of a specific, quantified per-violation penalty figure for the Genetic Data Privacy Act, even if sourced from secondary commentary, suggests that South Dakota's legislature is willing to attach concrete financial consequences to newly enacted sectoral privacy statutes, a posture that may be relevant to assessing the credibility of future sectoral privacy legislation's enforcement provisions.

Outlook

The principal open item is independent verification of the 5,000-USD-per-violation civil-penalty figure directly against the Genetic Data Privacy Act's own enforcement section, since this cycle's finding rests on a single secondary commentary source. A second open question is whether the Attorney General's office issues any guidance or exercises enforcement discretion under the new penalty provision in the period following the Act's 1 July 2026 effective date, a matter on which this cycle's evidence base provides no direct insight.

Periodic update · new data 2026-09-28

South Dakota's enforcement architecture for data-protection matters escalated this cycle with the addition of a second civil-penalty track under the Genetic Data Privacy Act, SB49, which entered into force on 1 July 2026. The Act's civil penalties reach up to five thousand dollars per violation, operating alongside the states pre-existing breach-notification penalty regime, which allows civil penalties of up to ten thousand dollars per day per violation and treats violations of the breach-notification statute as deceptive trade practices.

Both enforcement tracks, the standing breach-notification regime and the new genetic-data statute, share a common structural feature: enforcement runs exclusively through the Attorney General's office, and neither statute creates a private right of action. This means individual South Dakota residents whose genetic data is mishandled, or whose personal information is compromised in a breach, cannot bring their own civil suit under either statute; redress depends entirely on the Attorney General choosing to pursue enforcement action.

The per-violation penalty structures differ meaningfully between the two tracks. The breach-notification regime's penalty accrues on a per-day, per-violation basis, up to ten thousand dollars, which can produce substantial cumulative penalties for a prolonged or unremediated breach affecting a large population. The Genetic Data Privacy Act's penalty, by contrast, is a flat per-violation amount of up to five thousand dollars, without the day-based multiplier, suggesting a somewhat less severe maximum penalty structure for genetic-data violations considered individually, though the practical effect will depend heavily on how the Attorney General defines a single violation for enforcement purposes under each statute.

This cycle's addition of a second enforceable penalty track is a material escalation of the states overall enforcement architecture for data-protection matters, even though both tracks remain AG-only with no private right of action, meaning the states overall enforcement model itself has not shifted toward a private-litigation-driven approach seen in some other US jurisdictions.

Outlook

The key forward-looking question for this module is whether the Attorney General brings any enforcement action under the new Genetic Data Privacy Act penalty track in a future cycle, which would be the first practical test of how the states genetic-data enforcement regime operates outside the statutory text itself. Observing how the Attorney General defines a single violation under each of the two now-parallel penalty tracks, particularly for incidents that could plausibly implicate both statutes, would also clarify the practical interaction between South Dakota's two data-protection enforcement regimes.

Sources and claims (14)
  1. Probable Federal Trade Commission — Federal Trade Commission can pursue injunctive relief, mandated compliance programs, and civil penalties for order violations FTC Section 5 enforcement powers reaching South Dakota-based conduct. Federal enforcement machinery applicable to SD-based conduct. observed
  2. Probable NAAG — South Dakota Attorney General enforces breach-notification and consumer-protection law, including via multistate NAAG-coordinated actions SD AG general consumer-protection authority plus breach-notification enforcement, often coordinated multistate via NAAG. State enforcement authority operating through general consumer-protection statute and NAAG coordination. observed
  3. Uncertain DataGuidance (secondary aggregator citing primary statute) — South Dakota breach-notification statute does not appear to create an express private right of action; enforcement responsibility rests with the Attorney General (not independently confirmed against full statutory text). Unverified negative finding on private right of action; flagged as open question in self_audit. observed
  4. Probable Primary statutory record — South Dakota genetic-data protection legislation (SB49) was introduced and signed into law within the preceding 180 days Reported March 2026 signing, now confirmed effective July 1, 2026, per challenger fold f-001. Most material recent development this cycle; enriched via challenger fold f-001.
  5. Confirmed South Dakota Attorney General's Office — AG Jackley announced South Dakota received the first $9 million payment from Meta Platforms under the multistate settlement on 2026-10-26. observed
  6. Probable Global Policy Watch (law-firm blog) — Attorney General (South Dakota) — civil penalties not exceeding $5,000 per violation for violation of the Genetic Data Privacy Act observed
  7. Probable https://openagreements.org/practice-guides/privacy/us/south-dakota — SB 49 carries a $5,000-per-violation AG civil penalty.
  8. Probable https://openagreements.org/practice-guides/privacy/us/south-dakota — SD privacy statutes are AG-enforced only; no private right of action.
  9. Probable https://openagreements.org/practice-guides/privacy/us/south-dakota — The South Dakota AG may prosecute breach-notification failures as deceptive acts, recovering up to $10,000 per day per violation.
  10. Confirmed South Dakota Attorney General's Office — South Dakota reached a $15 million settlement with Roblox Corporation on 2026-07-13. observed
  11. Probable DataBreachCost.com — South Dakota's breach-notification statute provides no private right of action. observed
  12. Probable South Dakota Legislature — South Dakota breach-notification statute — Does not confer a private right of action on affected individuals observed
  13. Confirmed South Dakota Legislature — South Dakota Attorney General — Enforcement of the Genetic Data Privacy Act runs exclusively through the Attorney General, who alone may petition a court to impose the civil penalty; there is no private right of action for individual consumers. observed
  14. Probable KOTA TV — South Dakota breach-notification law — criminal penalties for failing to disclose a breach; no private right of action observed
No categories match.

No categories match your current search or filter selection.

Provenance and declared absence

Disclosure model: category cards load OPEN; narratives render in full; standing narratives load as a clamped teaser with an explicit “read full” control carrying the true word count. No text is hidden without disclosing how much of it there is.

Sub-modules are DP-specific nested subsections with their own real per-sub-module traffic light, rendered under each category across all regulatory modules.

Traffic-light dots are REAL data (baseline.<category>.traffic_light), not renderer-invented taxonomy, and are never suppressed -- unlike WPM, where a RAG dot would be forbidden as invented severity.

Family/accent taxonomy is renderer-level presentation config, not a JID field; it decorates the RAG dot, it does not replace it. Colour is always duplicated in text and is never the sole carrier of meaning.

Suppressed by doctrine: derived risk score. Not shown on this page.

Band honesty: uncertainty bands are computed against a frozen build clock of 2026-11-17. A year-precision row is never promoted into a tighter band.

Envelope: baseline resolved at jurisdiction_json.baseline; 10 categories, 57 sub-module(s), 67 claim(s) (67 category placement(s)), 37 source(s) in the cumulative register.

Audit trail

Machine checkChallenged on 25 Oct 2026: upheld (8 confirmed against the cited source; 16 could not be checked). An automated, adversarial test run by a second model; no person has assessed the result.

Think something on this page is wrong? Report an error.

GDPR article map

Cross-reference: which category/sub-module covers each UK GDPR article (38 mapped).

Show article map
GDPR article to category mapping
ArticleCategorySub-module
Art. 5Controller/Processor Dutiesaccountability and dpia
Art. 6Lawful Processing & Special Datalawful bases
Art. 7Lawful Processing & Special Dataconsent thresholds
Art. 9Lawful Processing & Special Dataspecial categories
Art. 13Data Subject Rightsaccess right
Art. 14Data Subject Rightsaccess right
Art. 15Data Subject Rightsaccess right
Art. 16Data Subject Rightsrectification and erasure
Art. 17Data Subject Rightsrectification and erasure
Art. 18Data Subject Rightsrestriction and objection
Art. 19Data Subject Rightsdeadlines and response windows
Art. 20Data Subject Rightsdata portability
Art. 21Data Subject Rightsrestriction and objection
Art. 22Algorithmic, Biometric & Surveillance Governanceautomated decision making transparency
Art. 25Controller/Processor Dutiesaccountability and dpia
Art. 28Controller/Processor Dutiesjoint controller arrangements
Art. 30Controller/Processor Dutiesropa requirements
Art. 32Controller/Processor Dutiessecurity measures
Art. 33Controller/Processor Dutiesbreach notification
Art. 34Controller/Processor Dutiesbreach notification
Art. 35Controller/Processor Dutiesaccountability and dpia
Art. 37Controller/Processor Dutiesdpo requirements
Art. 38Controller/Processor Dutiesdpo requirements
Art. 39Controller/Processor Dutiesdpo requirements
Art. 44Cross-Border & Adequacytransfer mechanisms
Art. 45Cross-Border & Adequacyadequacy received
Art. 46Cross-Border & Adequacysccs and bcrs
Art. 47Cross-Border & Adequacysccs and bcrs
Art. 48Cross-Border & Adequacydata localisation
Art. 49Cross-Border & Adequacytransfer impact assessment
Art. 77Enforcement & Redressprivate right of action
Art. 78Enforcement & Redressprivate right of action
Art. 79Enforcement & Redressprivate right of action
Art. 80Enforcement & Redresscollective redress and class actions
Art. 81Enforcement & Redressregulator powers and penalties
Art. 82Enforcement & Redresscollective redress and class actions
Art. 83Enforcement & Redressregulator powers and penalties
Art. 84Enforcement & Redressregulator powers and penalties