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.
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.
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
Ask the first-step owner to bring the most recent system, activity or product inventory and the contract or rule driving the work.
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.
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
Record the requirement or claim, the person responsible, the period and the result. Link to the original report, configuration, test or case record.
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.
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.
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.
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.
Targets use illustrative calendar-day estimates and assume the steps run in sequence. Check official dates and agree real durations with your team.
01
Map the scope and national rules
Who Legal + privacy lead + business ownersWhen 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
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.
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.
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.
Who HR + Privacy + SecurityWhen 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
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.
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.
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.
Who Privacy operations + system owners + LegalWhen 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
Record the request, owner and date. Verify identity when needed and scope searches across the systems and recipients that may hold responsive information.
For recipient information, match disclosures to actual names from contract, communications and system records. Have Legal record any applicable limit before relying on categories.
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.
Who Privacy lead + incident lead + LegalWhen 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
Identify the type of matter, competent authority, date received and any assigned response deadline. Give Legal the notice and preserve evidence.
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.
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.