Start hereMap the scope and national rules
~42 days leftOpen step
Guide library
Regulation Europe

Austria Data Protection Act (DSG)

Austria Datenschutzgesetz: confidentiality, GDPR rights and DSB complaints

Apply Austria’s national privacy rules alongside the GDPR. Put data secrecy into staff instructions and prepare for rights requests, breach notifications and authority complaints.

Issuing authority
Austrian Data Protection Authority (Datenschutzbehörde)
Timing
GDPR rights requests usually require a response within one month. Where Article 33 requires notice, notify the competent authority without undue delay and where feasible within 72 hours of awareness. DSG §24 has its own limitation periods for lodging complaints.
Reviewed
Inside this guide
4 steps · 4 templates

Who it applies to

Controllers and processors subject to Austria’s DSG. Check which jurisdiction and supervisory authority have competence and any specific rules for public authorities, research, employment or law enforcement.

What you’ll produce

A record of applicable DSG and GDPR duties, approved confidentiality and disclosure instructions, a rights response file and an authority communication procedure.

Under DSG §6, controllers and processors must take account of confidentiality and express employer instructions for employee disclosures. Route parliamentary processing issues by checking whether the Parliamentary Data Protection Committee is competent under §§35a and following.

TEAM KICKOFF

Run the project

Go to the roadmap

Decisions for leadership

What applies to each entity, product and activity?
Have Legal or Regulatory confirm scope and applicable deadlines for each entity, activity and jurisdiction. Assign owners for incident reporting, filings and lifecycle changes where required.
Who will do the work and who can sign?
Appoint a sponsor, a day-to-day lead and a named owner for every workstream. Set aside their time and decide who can approve the outcome, accept remaining risk or authorize a filing.
Which deadlines can we promise?
Separate fixed external dates from internal targets. Confirm dependencies such as a vendor, test lab or assessor, and approve a backup plan if their dates slip.

How to spend the first week

  1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
  2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
  3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.

What to review each week

Monitor obligations without a named owner, filings or notifications approaching deadline, and changes that should reopen the scope decision.

Kickoff brief to share with your team

Fill this in with your sponsor and send it to the people who own the work.

Austria Data Protection Act (DSG) kickoff brief
Business reason and required outcome  [Contract, obligation or approval]
Scope and exclusions  [Entities, systems or activities, and reasons]
Fixed deadlines and internal milestones  [Date, source and owner]
Executive sponsor and authorized signer  [Names]
Project lead and backup  [Names]
First workstream  Map the scope and national rules · Legal + privacy lead + business owners [Name and due date]
People, effort and external costs  [Estimate, owner and contingency]
Evidence folder and reviewer access  [Location, access owner and review date]
Decisions and blockers  [Item, options, owner and decision date]

First week
1. Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
2. Walk a real activity through the systems, suppliers and teams that run it. Verify the rule, authority and deadline that apply to the observed facts.
3. Record what the sponsor approved, open questions, work owners and the next date a decision is needed. Send the brief to everyone who needs to contribute evidence.
How to hand off evidence
  1. Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
  2. Include the version, system or product, date, and how you gathered the record. When a report covers a group of items, retain its filters and reconcile the count to the source.
  3. Ask the reviewer to open the evidence and reproduce the key check. Record their decision and date. Keep missing items or failures visible with an owner, a due date and a retest when needed.
  4. Share through the agreed channel. Keep sensitive originals in a restricted location and link any redacted copies to the corresponding originals.
BEFORE YOU START

How this works in practice

Two questions to check scope

  • Can an employee show the approved instruction for their latest disclosure of personal data?
  • Can the rights team identify who received the data when a person requests that information?

Worked scenario

A Vienna retailer receives an access request asking who received its customer’s details. The privacy lead asks fulfilment, advertising and support teams for the relevant disclosure records, documents the actual recipients and reviews how staff export data to suppliers.

What to read next

  • EU GDPR

    Use the GDPR guide for the broader EU requirements.

FROM THE SOURCE

Cases and numbers

Court of Justice · C-154/21

An access request can require the names of actual recipients

In Österreichische Post, the Court held that the controller must provide actual recipient identities for the data disclosed or to be disclosed, subject to the limits in the judgment. Categories may suffice if identification is impossible or the controller demonstrates the request is manifestly unfounded or excessive.

What to check Keep disclosure logs that identify each recipient and make those logs searchable by the data covered in a request.

Court of Justice judgment in C-154/21 (opens in a new tab)

Austrian DSB activity report · 2025

5,300Domestic individual complaints received by the DSB in 2025

Domestic individual complaints rose from 2024 to 2025

The authority reported 3,019 domestic individual complaints received in 2024. Its annual report tracks receipts and dispositions separately.

What to check Track complaint intake and outcomes as separate measures. Preserve the facts and dates for each case before comparing them.

DSB 2025 activity report, authority activity table (opens in a new tab)
DATES AND TRIGGERS

Official milestones

See the deadline calendar
  • Usually within one month of receipt

    Respond to a GDPR rights request

    For an eligible extension, notify the person and explain why within one month under Article 12(3).

    Official reference (opens in a new tab)
  • Without undue delay, within 72 hours where feasible

    Notify a breach when Article 33 requires it

    Use the awareness time and document the risk decision, any delay and all follow-up.

    Official reference (opens in a new tab)
  • One year from knowledge, at most three years from the event

    Check the DSG §24 complaint filing limits

    These periods apply to the admissibility of a complaint. Follow the deadline in any notice you receive from the competent authority.

    Official reference (opens in a new tab)
The whole journeyabout 42 days across 4 steps
  1. 01Map the scope and national rules, Legal + privacy lead + business owners, about 7 days
  2. 02Put data secrecy into daily work, HR + Privacy + Security, about 14 days
  3. 03Handle access requests and preserve proof, Privacy operations + system owners + Legal, about 14 days
  4. 04Prepare for complaints and breach notices, Privacy lead + incident lead + Legal, about 7 days
IMPLEMENTATION ROADMAP

Step by step

Checklist, instructions and 4 templates.

View plan as a table
Project roadmap with current target dates and completion status
StepOwnerWhen to actEstimated targetDeliverablesStatus
Map the scope and national rulesLegal + privacy lead + business ownersBefore starting or changing processingSet a start dateAustria DSG applicability and ownership memoOpen
Put data secrecy into daily workHR + Privacy + SecurityAt onboarding and before an employee discloses dataSet a start dateAustria data secrecy and disclosure instructionsOpen
Handle access requests and preserve proofPrivacy operations + system owners + LegalAt receipt of a GDPR rights requestSet a start dateAustria access request and recipient recordOpen
Prepare for complaints and breach noticesPrivacy lead + incident lead + LegalAt a complaint or potential breachSet a start dateAustria DSB complaint and breach fileOpen
0 of 4 completeOpen workspace

Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.

  1. 01

    Map the scope and national rules

    Who Legal + privacy lead + business owners When Before starting or changing processing

    List the legal entity, purpose, people, role, disclosures and retention. Check the GDPR legal basis and safeguards, then review §1 confidentiality and additional DSG rules that match the activity. Identify the competent supervisory authority.

    What to produce

    Austria DSG applicability and ownership memoMemo

    Gather first

    • Entity and establishment list
    • Processing inventory
    • Existing GDPR analysis
    • Sector rules
    • Current DSG text

    How to prepare it

    1. For each activity, map who decides the purpose and means, whose information is used and where it goes. Record the GDPR basis and the evidence for necessity, limits and safeguards.
    2. Have Legal check §1 confidentiality and DSG provisions that apply to the purpose or category of data. Record review notes for employment, research or public-sector processing if applicable.
    3. Name the accountable owner, the privacy contact and the competent authority. For a cross-border case, document the authority analysis and any applicable cooperation route.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional activity
    Donau Cart, a Vienna online retailer, uses a named logistics provider to deliver orders. Legal documents the role analysis, approved fields, contract and retention limits.
    Owner and open issue
    Operations owns the disclosure flow. Privacy reviews a proposed address reuse for analytics before the additional use is approved.

    Check before handing it over

    Legal and business owners can connect each decision to the data flow and the applicable GDPR and DSG provisions.

    Give system owners the approved uses, access conditions and review owner.

  2. 02

    Put data secrecy into daily work

    Who HR + Privacy + Security When At onboarding and before an employee discloses data

    Issue explicit instructions for permitted disclosures. Where §6 requires contractual obligations, address disclosure only on instructions and confidentiality after departure. Train staff on applicable instructions, consequences and a route to flag an unlawful disclosure.

    What to produce

    Austria data secrecy and disclosure instructionsMemo

    Gather first

    • Approved purposes
    • Staff roles and access configuration
    • Supplier list
    • Existing employment terms
    • DSG §6

    How to prepare it

    1. Write role-based instructions that name permitted recipients, purposes, approved transfer channels and who can authorise exceptions. Confirm that each instruction covers only lawful disclosures.
    2. Check whether §6 requires a contractual commitment and have HR address secrecy after employment. Train covered staff on the instructions and the consequences of breaches.
    3. Have a team member demonstrate how to report or refuse a potentially unlawful disclosure. Keep the approved instruction, training evidence and any later amendment.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional instruction
    Donau Cart fulfilment may send agreed delivery fields to the named logistics provider in the approved order system. Staff escalate any request for extra fields to Privacy.
    Retention evidence
    HR saves the version acknowledged at onboarding, the training date and the reminder provided when staff leave.

    Check before handing it over

    An employee can identify the applicable instruction and prove who authorised a disclosure.

    Give signed instructions to the relevant team leads and match permissions to the approved workflow.

  3. 03

    Handle access requests and preserve proof

    Who Privacy operations + system owners + Legal When At receipt of a GDPR rights request

    Log the request date and response deadline, verify identity when needed, and ask systems and partners for responsive evidence. Check whether actual recipient identities must be provided under C-154/21. Have a reviewer approve exceptions and preserve the written response and delivery record.

    What to produce

    Austria access request and recipient recordSpreadsheet

    Gather first

    • Request and receipt record
    • Data sources and vendors
    • Disclosure logs
    • GDPR Articles 12 and 15
    • C-154/21 judgment

    How to prepare it

    1. Record the request, owner and date. Verify identity when needed and scope searches across the systems and recipients that may hold responsive information.
    2. For recipient information, match disclosures to actual names from contract, communications and system records. Have Legal record any applicable limit before relying on categories.
    3. Check dates and completeness, then send the reply through an approved secure channel. Keep the search log, reviewed reply and delivery evidence.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional request AT-014
    A shopper asks which organisations received their details. The privacy analyst checks the order, payment and marketing records and records the specific third parties where they can be identified.
    Evidence of response
    The authorised reviewer checks the response, restrictions and dates. The case record contains the sent version and proof of delivery.

    Check before handing it over

    The case record shows which sources were searched, which named recipients were found, and what the requester received.

    Return changes in recipient or system ownership to the team that maintains the processing inventory.

  4. 04

    Prepare for complaints and breach notices

    Who Privacy lead + incident lead + Legal When At a complaint or potential breach

    Route any authority notice, preserve the timeline and assign a legal owner to its deadlines. For a breach, document awareness, affected records, risk and mitigations. Use the competent authority’s form when required and assess any high-risk duty to inform affected people.

    What to produce

    Austria DSB complaint and breach fileChecklist

    Gather first

    • Notice or incident report
    • Timeline and awareness evidence
    • Competent authority details
    • DSB forms
    • Decision and correspondence

    How to prepare it

    1. Identify the type of matter, competent authority, date received and any assigned response deadline. Give Legal the notice and preserve evidence.
    2. For an incident, log awareness, data and people affected, likely harm and mitigation. Apply Articles 33 and 34 and use the competent authority’s reporting route as applicable.
    3. Keep submitted versions, receipt, reasons for delay if relevant, communications with affected people and follow-up actions. Log any correction made during a complaint procedure.

    Worked example

    Fictional details. Use the same fields with evidence from your work.

    Fictional awareness time
    Support confirms a misdirected customer export on Tuesday at 10:15. The incident lead records awareness, contains the disclosure and escalates the risk decision immediately.
    Authority evidence
    Record the verified submission channel, signed response or report, the receipt and who is responsible for further correspondence.

    Check before handing it over

    A reviewer can trace timelines, authority selection, notices and actual mitigation to preserved evidence.

    Give unresolved deadlines to Legal and corrective actions to the people who operate the system.

PRIMARY REFERENCES

Official sources

How we build these guides

Keyboard shortcuts

⌘K or /
Search everything
?
This list
g h
Home
g l
Guide library
g f
Find my path
g t
Templates
g p
Playbooks
g w
My workspace
g d
Deadline calendar
g c
Regulatory changes