{"id":3118,"date":"2026-10-28T11:31:08","date_gmt":"2026-10-28T11:31:08","guid":{"rendered":"https:\/\/sawaryn.com\/us\/?p=3118"},"modified":"2026-10-28T11:31:26","modified_gmt":"2026-10-28T11:31:26","slug":"poland-job-postings-salary-candidate-data","status":"publish","type":"post","link":"https:\/\/sawaryn.com\/us\/poland-job-postings-salary-candidate-data\/","title":{"rendered":"Job Postings in Poland: Salary Transparency, Candidate Data and Recruitment Risk"},"content":{"rendered":"

Job Postings in Poland: Salary Transparency, Candidate Data and Recruitment Risk<\/h1>\n

Open the most recent job posting your company published for a position in Poland. Does it state the proposed base salary or a range? If not, the template may not have been updated since the changes that took effect on December 24, 2025. That may not be its only problem.<\/p>\n

A job posting can look like a routine HR document: a template reused from an earlier search, perhaps with a few fields changed. In Poland, however, employee recruitment must be assessed under both the Polish Labour Code<\/strong> and the General Data Protection Regulation (GDPR)<\/a><\/strong>. An overbroad \u201crequired documents\u201d section can result in unnecessary processing of hundreds of applicants\u2019 personal data. A question about current or previous pay\u2014prohibited in employee recruitment since December 2025\u2014can contribute to a compensation claim.<\/p>\n

For a company recruiting in Poland, the practical review is wider than the advertisement itself. It includes the application form, applicant tracking system (ATS), interview questions, privacy notice, access permissions and data-retention process.<\/p>\n

Key Polish rules and terms<\/h2>\n\n\n\n\n\n\n\n\n\n
Term<\/th>\nWhat it means for recruitment<\/th>\n<\/tr>\n<\/thead>\n
Article 22\u00b9 of the Polish Labour Code<\/strong><\/td>\nSets out the categories of information an employer may request from an applicant. These include name, date of birth and contact details; education, professional qualifications and employment history may be requested when necessary for the position.<\/td>\n<\/tr>\n
Article 18\u00b3ca of the Polish Labour Code<\/strong><\/td>\nIn force since December 24, 2025. It requires information about the proposed base salary or range and prohibits questions about pay in current or previous employment.<\/td>\n<\/tr>\n
Data minimization\u2014Article 5(1)(c) GDPR<\/strong><\/td>\nPersonal data must be adequate, relevant and limited to what is necessary for the purpose. In recruitment, collect only what you need.<\/td>\n<\/tr>\n
Privacy notice\u2014Article 13 GDPR<\/strong><\/td>\nApplicants must be told who processes their data, why, on what legal basis, for how long and what rights they have. Provide the notice when collecting their data.<\/td>\n<\/tr>\n
Special categories of data\u2014Article 9 GDPR<\/strong><\/td>\nThese include information about health, disability, religion, sexual orientation and trade union membership. At the recruitment stage, the source addresses processing data supplied on the applicant\u2019s own initiative and with consent.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Four questions to ask before publishing a job posting<\/h2>\n

1. Which rules apply to the recruiting organization?<\/h3>\n

A private employer recruiting employees in Poland must account for the Labour Code and GDPR. A local government entity is also subject to rules including the Act on Local Government Employees and a regulation on remuneration.<\/p>\n

Do not copy a public-sector recruitment notice into a private company\u2019s process without reviewing it. You may present applicants with procedural commitments that your organization is not required\u2014or prepared\u2014to follow.<\/p>\n

2. Which requirements are essential to the role?<\/h3>\n

In private-sector fields such as IT, SaaS and e-commerce, there is no general statutory list of qualifications for every position. The employer must be able to link each requirement to the work. Requiring a university degree where it is not necessary for the role, for example, does not meet the test described in Article 22\u00b9 \u00a7 2 of the Labour Code.<\/p>\n

Treat a requirement as essential<\/strong> if you can identify the task it serves, explain why a less intrusive way to assess the applicant is unavailable, and apply it consistently to all applicants. Place other criteria\u2014such as preferred experience or soft skills\u2014in an additional<\/strong> or \u201cnice to have\u201d category.<\/p>\n

3. What is the legal basis for each application field?<\/h3>\n

A common error is to rely on applicant consent for all<\/strong> personal data in an application. The source distinguishes information requested under the Labour Code, information needed to enter into a contract, and additional information voluntarily provided by the applicant.<\/p>\n\n\n\n\n\n\n\n\n
Data category<\/th>\nLegal basis identified in the source<\/th>\nExample<\/th>\n<\/tr>\n<\/thead>\n
Data requested under the Labour Code<\/td>\nArticle 6(1)(c) GDPR together with Article 22\u00b9 of the Labour Code<\/td>\nName in an application form<\/td>\n<\/tr>\n
Data necessary to enter into a contract<\/td>\nArticle 6(1)(b) GDPR<\/td>\nConfirmation of qualifications required for the role<\/td>\n<\/tr>\n
Additional data provided voluntarily<\/td>\nArticle 6(1)(a) GDPR\u2014consent<\/td>\nA photograph in a CV or additional certificates<\/td>\n<\/tr>\n
Special categories of data<\/td>\nArticle 9 GDPR and Article 22\u00b9b of the Labour Code<\/td>\nA disability certificate<\/a> supplied on the applicant\u2019s initiative<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

Consent is not freely given if an applicant cannot realistically refuse it. Refusing or withdrawing consent cannot justify unfavorable treatment or a refusal to hire under Article 22\u00b9a \u00a7 2 of the Labour Code.<\/p>\n

4. When will applicants receive salary information?<\/h3>\n

Since December 24, 2025, Article 18\u00b3ca of the Labour Code has allowed three alternative points for providing the proposed base salary or range:<\/p>\n

    \n
  1. In the job posting.<\/li>\n
  2. Before the interview, if the information was not in the posting.<\/li>\n
  3. Before the employment relationship begins, if it was not provided earlier.<\/li>\n<\/ol>\n

    The choice concerns timing<\/strong>, not whether to provide the information. The amount or range must rest on objective, gender-neutral criteria<\/strong>. The source recommends a pay scale or remuneration policy; an entirely discretionary range is not enough.<\/p>\n

    The same provision prohibits asking applicants what they earn or earned in current or previous employment. Remove that question from application forms, ATS fields and interview scripts\u2014not just from the published posting.<\/p>\n

    Recruitment checklist: allowed, prohibited or dependent on the role<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
    Posting or recruitment element<\/th>\nStatus in the approved source<\/th>\n<\/tr>\n<\/thead>\n
    Applicant\u2019s first name, surname and date of birth<\/td>\nMay be requested.<\/td>\n<\/tr>\n
    Contact details indicated by the applicant<\/td>\nMay be requested.<\/td>\n<\/tr>\n
    Education, qualifications and employment history<\/td>\nRequest only when necessary for the position.<\/td>\n<\/tr>\n
    PESEL number, home address or bank account number<\/td>\nDo not request at the recruitment stage. PESEL is Poland\u2019s personal identification number.<\/td>\n<\/tr>\n
    Current or previous earnings<\/td>\nDo not ask in employee recruitment from December 24, 2025.<\/td>\n<\/tr>\n
    Proposed base salary or range<\/td>\nInformation must be provided; choose one of the permitted points in the process.<\/td>\n<\/tr>\n
    Photograph as a mandatory CV requirement<\/td>\nDo not require it; consent to use an applicant\u2019s image cannot be forced.<\/td>\n<\/tr>\n
    Photograph supplied voluntarily<\/td>\nThe source identifies consent as the basis for processing it.<\/td>\n<\/tr>\n
    Certificate from the Polish National Criminal Register (Krajowy Rejestr Karny<\/em>, or KRK)<\/td>\nAssess whether a legal provision or justified need of the position supports requesting it. Do not make it a standard requirement.<\/td>\n<\/tr>\n
    Medical certificate<\/td>\nDo not require it as part of the recruitment application. The employer\u2019s pre-employment medical examination obligation concerns a person being hired.<\/td>\n<\/tr>\n
    Health or disability information<\/td>\nThe source addresses data supplied on the applicant\u2019s initiative, with consent in the form of a declaration.<\/td>\n<\/tr>\n
    Age range in a posting<\/td>\nDo not include it; the source identifies it as discriminatory.<\/td>\n<\/tr>\n
    \u201cYoung, dynamic team\u201d<\/td>\nRemove it; the source identifies it as indirect age discrimination.<\/td>\n<\/tr>\n
    Gender specified in a job title<\/td>\nDo not specify it unless it is a genuine occupational requirement.<\/td>\n<\/tr>\n
    GDPR Article 13 privacy notice<\/td>\nProvide it when collecting applicant data.<\/td>\n<\/tr>\n
    Consent to retain details for future recruitment<\/td>\nObtain it separately and voluntarily; it cannot be a condition of participating in the current process.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

    Five recurring mistakes\u2014and how to correct them<\/h2>\n

    1. No salary section in the template<\/h3>\n

    A template without a salary section is a useful signal that it needs review, even though the source identifies other lawful points at which salary information may be given. For operational consistency, add a \u201cProposed base salary\u201d section containing:<\/p>\n

      \n
    1. The amount or range.<\/li>\n
    2. A statement that it is based on objective, gender-neutral criteria, such as those set out in a remuneration policy.<\/li>\n<\/ol>\n

      If the organization has no pay scale, the source\u2019s recommendation is to create one. A range based only on discretion does not meet the stated objective-criteria requirement.<\/p>\n

      2. One blanket consent clause for every applicant\u2019s data<\/h3>\n

      A generic statement such as \u201cI consent to the processing of my personal data\u201d is not the right basis for information requested under the Labour Code. The Polish Personal Data Protection Office (UODO)<\/a> indicates that purported consent of this kind is not freely given when the applicant cannot realistically decline it.<\/p>\n

      Set out the legal bases separately in the privacy notice. Reserve consent for additional information voluntarily supplied beyond the Labour Code categories.<\/p>\n

      3. A \u201crequired documents\u201d list that collects too much<\/h3>\n

      A mandatory package consisting of a photo CV, diploma copy, KRK certificate, PESEL number and medical certificate is, for the most part, excessive at the application stage. Remove documents and fields that cannot be required before employment begins. Where confirmation of a fact is needed\u2014for example, the absence of a criminal record\u2014the source recommends considering an applicant declaration instead of routinely collecting a certificate.<\/p>\n

      Under Article 229 \u00a7 1 of the Labour Code, a pre-employment medical examination is an employer obligation concerning a person being hired. It is not part of the initial application package.<\/p>\n

      4. An undefined retention period<\/h3>\n

      \u201cWe keep applications for as long as necessary\u201d does not give a sufficiently specified or determinable period under Article 5(1)(e) GDPR. UODO indicates<\/a> that an unsuccessful applicant\u2019s data should be deleted promptly when recruitment ends; longer retention requires a separate basis.<\/p>\n

      State a defined period in the notice and retention policy, and make sure the system follows it. The source gives destruction or return of documents no later than three months after recruitment ends<\/strong> as an example and recommends setting a reminder. Any longer retention\u2014including for claims or future searches\u2014needs its own assessment and stated basis.<\/p>\n

      5. Discriminatory wording in an otherwise routine description<\/h3>\n

      Article 18\u00b3a \u00a7 1 of the Labour Code prohibits discrimination in access to employment. Poland\u2019s National Labour Inspectorate (Pa\u0144stwowa Inspekcja Pracy<\/em>, or PIP)<\/a> advises against postings that suggest preferences based on gender, age or characteristics unrelated to the work. Article 18\u00b3ca \u00a7 3 also requires gender-neutral postings and job titles.<\/p>\n

      Phrases such as \u201cyoung person,\u201d \u201cman for manual work\u201d and stated age ranges may be evidence of a discriminatory criterion. An applicant may seek compensation under Article 18\u00b3d of the Labour Code. The source states a minimum of one statutory minimum monthly wage\u2014PLN 4,806 gross from January 1, 2026<\/strong>\u2014with no upper limit. In judgment II PSKP 17\/21<\/a>, the Polish Supreme Court confirmed that this compensation has a sanctioning function and is not limited to proven financial loss.<\/p>\n

      The GDPR privacy notice: eight points to cover<\/h2>\n

      Provide the Article 13 GDPR information when applicants submit their data, whether through the posting or an application form. A complete notice in the source covers:<\/p>\n

        \n
      1. The controller\u2019s name, address and contact details.<\/li>\n
      2. Contact details for the data protection officer, if one has been appointed.<\/li>\n
      3. The purposes and legal bases for processing, distinguishing legal requirement, contract and consent.<\/li>\n
      4. Data recipients and processing by service providers, such as an ATS provider.<\/li>\n
      5. Whether data is transferred outside the European Economic Area (EEA)<\/a>, and the relevant safeguard mechanism if it is.<\/li>\n
      6. A specified retention period.<\/li>\n
      7. Applicant rights: access, rectification, erasure, restriction, portability, objection, withdrawal of consent and complaint to the President of UODO.<\/li>\n
      8. Whether providing data is voluntary, the consequences of not providing it, and information on automated decision-making and profiling.<\/li>\n<\/ol>\n

        If you use an ATS, confirm that applicants can see the full notice before submitting an application. The source treats an ATS provider processing data on the employer\u2019s behalf as a processor under Article 28 GDPR, requiring a data processing agreement. Before choosing a provider, check where data is stored, which subprocessors are used, the basis for any transfer outside the EEA and how records are deleted when the retention period ends.<\/p>\n

        Limit access to applications<\/h2>\n

        A shared recruitment inbox accessible to a large team creates risk. An applicant may independently attach a disability certificate or mention their health or trade union membership. Special-category data can then reach people who have no reason to see it.<\/p>\n

        Article 22\u00b9b of the Labour Code requires access to special categories of data to be limited to people authorized in writing. The source describes an authorization issued by the controller that specifies its scope and purpose and is acknowledged by the authorized person\u2019s signature.<\/p>\n

        Take three operational steps:<\/p>\n

          \n
        1. Limit access to recruitment inboxes and CV folders to those directly involved.<\/li>\n
        2. Put written authorizations in place for people who may view applicant data.<\/li>\n
        3. Configure ATS roles so that special-category data is visible only to designated people.<\/li>\n<\/ol>\n

          Employee hiring versus B2B contractor recruitment<\/h2>\n

          Polish companies also recruit individuals for business-to-business (B2B) contracts. Article 22\u00b9 of the Labour Code concerns recruitment for an employment relationship; it does not automatically extend to contractor selection.<\/p>\n\n\n\n\n\n\n\n\n\n\n
          Issue<\/th>\nEmployee recruitment<\/th>\nB2B contractor recruitment<\/th>\n<\/tr>\n<\/thead>\n
          Categories of data that may be requested<\/td>\nLabour Code Article 22\u00b9 applies.<\/td>\nNo equivalent separate list identified in the source; apply GDPR principles.<\/td>\n<\/tr>\n
          Processing basis identified in the source<\/td>\nArticle 6(1)(b) and (c) GDPR.<\/td>\nArticle 6(1)(b) GDPR for pre-contract steps, or Article 6(1)(f) for legitimate interests.<\/td>\n<\/tr>\n
          Salary or rate disclosure<\/td>\nArticle 18\u00b3ca applies.<\/td>\nNo confirmed equivalent statutory obligation identified.<\/td>\n<\/tr>\n
          Questions about prior earnings<\/td>\nProhibited under Article 18\u00b3ca from December 24, 2025.<\/td>\nNo confirmed equivalent statutory prohibition identified.<\/td>\n<\/tr>\n
          GDPR data minimization<\/td>\nApplies.<\/td>\nApplies.<\/td>\n<\/tr>\n
          GDPR privacy notice<\/td>\nRequired.<\/td>\nRequired.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

          For B2B recruitment, decide what data to request by reference to the proposed contract and GDPR principles, not by automatically importing Article 22\u00b9. Publishing a proposed contractor rate may be good practice, but the source does not identify a current statutory requirement to do so.<\/p>\n

          Directive (EU) 2023\/970<\/a>, with an implementation deadline of June 7, 2026, concerns employment relationships. The source notes that the scope of Polish implementing legislation should be checked before publishing a B2B posting, particularly where an individual contractor would perform the work personally without subcontractors.<\/p>\n

          Agencies and job boards: responsibility does not disappear<\/h2>\n

          Giving discriminatory requirements to a recruitment agency does not release the employer from responsibility. Responsibility for a posting rests primarily with an entity that creates, approves or knowingly publishes its content.<\/p>\n

          The agency\u2019s GDPR role depends on what it actually does:<\/p>\n

            \n
          1. Processor:<\/strong> If it handles data only on the employer\u2019s instructions, Article 28 GDPR applies and a data processing agreement is required.<\/li>\n
          2. Potential joint controller:<\/strong> If it jointly determines the purposes and means of processing, Article 26 GDPR may apply, requiring an arrangement that defines responsibilities.<\/li>\n
          3. Publication intermediary:<\/strong> Merely helping publish a posting does not, by itself, establish joint controllership. In Case C-683\/21<\/a>, the Court of Justice of the European Union addressed the need for joint determination of processing purposes and means.<\/li>\n<\/ol>\n

            The Polish Act of March 20, 2025 on the Labour Market and Employment Services<\/a> also prohibits vacancies that breach equal-treatment principles from being posted in the ePraca system.<\/p>\n

            Three areas of exposure from a defective posting<\/h2>\n\n\n\n\n\n\n\n
            Area<\/th>\nAuthority or claimant<\/th>\nPotential consequence identified in the source<\/th>\n<\/tr>\n<\/thead>\n
            GDPR<\/td>\nPresident of UODO<\/td>\nUnder Article 83 GDPR, an administrative fine of up to EUR 20 million or 4% of annual worldwide turnover (UODO<\/a>).<\/td>\n<\/tr>\n
            Employment discrimination<\/td>\nApplicant bringing a claim before a Polish labor court<\/td>\nCompensation under Article 18\u00b3d of the Labour Code: at least one minimum monthly wage, stated in the source as PLN 4,806 gross from January 1, 2026, with no upper limit.<\/td>\n<\/tr>\n
            Employment-law inspection<\/td>\nPIP<\/td>\nAn inspection concerning Articles 18\u00b3ca and 22\u00b9 of the Labour Code; potentially an offense under Article 282 \u00a7 1 if the conduct satisfies its statutory elements.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

            These routes can overlap. A posting may prompt excessive collection from many applicants, an employment-law inspection and an individual compensation claim. After recruitment, an applicant may also exercise GDPR rights, including access under Article 15 and erasure under Article 17.<\/p>\n

            Preparing for the EU Pay Transparency Directive<\/h2>\n

            Article 18\u00b3ca of the Labour Code anticipates part of Directive (EU) 2023\/970<\/a>. The Directive\u2019s implementation deadline is June 7, 2026, and its scope is broader than providing applicants with a salary figure. The source highlights:<\/p>\n

              \n
            1. An employee right to information on average pay levels broken down by sex, under Article 7.<\/li>\n
            2. Gender pay-gap reporting: annually for employers with at least 250 employees, with the first report due by June 7, 2027; every three years for those with 150\u2013249 employees; and every three years for those with 100\u2013149 employees, with the source identifying June 7, 2031 for that group.<\/li>\n
            3. A joint pay assessment with workers\u2019 representatives under Article 10 where a gap of at least 5% in a category is not justified by objective criteria and is not remedied within six months.<\/li>\n<\/ol>\n

              The approved source does not confirm that Poland has adopted comprehensive legislation implementing every Directive requirement. If your organization has at least 100 employees<\/strong>, begin preparing pay records broken down by sex and job category, and check the legislative position as implementation develops.<\/p>\n

              Action plan: what to change first<\/h2>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
              Priority<\/th>\nAction<\/th>\n<\/tr>\n<\/thead>\n
              1. Audit templates<\/strong><\/td>\nCheck every employee-recruitment posting template for proposed base salary information or a range. Update templates that lack it, while ensuring salary information is provided at a permitted point in the process.<\/td>\n<\/tr>\n
              2. Remove pay-history questions<\/strong><\/td>\nReview forms, ATS fields and interview scripts. Give recruiters explicit instructions not to ask about current or previous employment pay.<\/td>\n<\/tr>\n
              3. Correct processing bases<\/strong><\/td>\nSeparate legal requirement, contract and consent in the privacy notice. Do not use blanket consent for all data.<\/td>\n<\/tr>\n
              4. Cut excessive document requests<\/strong><\/td>\nRemove routine requests for PESEL, address, bank details, a photo, a medical certificate and a KRK certificate from the initial application package. Assess any role-specific exception.<\/td>\n<\/tr>\n
              5. Set retention rules<\/strong><\/td>\nState a defined period, configure deletion or return, and set a reminder. Assess a separate basis for any longer retention.<\/td>\n<\/tr>\n
              6. Complete the Article 13 notice<\/strong><\/td>\nCover the eight points above and make the notice available before applicants submit data.<\/td>\n<\/tr>\n
              7. Classify requirements<\/strong><\/td>\nSeparate qualifications necessary for the work from preferences. Record the rationale for essential requirements.<\/td>\n<\/tr>\n
              8. Review wording<\/strong><\/td>\nRemove age ranges, unjustified gender references and phrases such as \u201cyoung, dynamic team.\u201d<\/td>\n<\/tr>\n
              9. Control access<\/strong><\/td>\nRestrict recruitment inboxes and ATS permissions, with written authorizations where required for special-category data.<\/td>\n<\/tr>\n
              10. Train and approve<\/strong><\/td>\nTrain recruiters and hiring managers on permitted questions and data requests. Require approval before a posting goes live.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

              Correcting one advertisement is not enough if the same issue remains in the application form, ATS, interview process or retention settings. Support may range from a corrected posting and Article 13 notice to a full recruitment-process review, GDPR documentation, training and assistance during a PIP or UODO inspection. Contact us<\/a> to review the materials and process you currently use in Poland.<\/p>\n

              Frequently asked questions<\/h2>\n

              Must the salary range appear in the posting?<\/h3>\n

              Not necessarily. The source identifies three points under Article 18\u00b3ca: in the posting, before the interview, or before the employment relationship begins if it has not been provided earlier. The obligation to give the information remains. The amount or range must be based on objective, gender-neutral criteria.<\/p>\n

              Can recruiters ask about salary expectations?<\/h3>\n

              A question about what an applicant would like to earn<\/strong> is different from asking what they currently earn or previously earned<\/strong>. Article 18\u00b3ca prohibits the latter; the source does not treat a question about expectations as expressly prohibited. Its practical value may be lower once the employer provides its proposed amount or range.<\/p>\n

              Can unsuccessful applications be kept for future searches?<\/h3>\n

              UODO\u2019s position cited in the source<\/a> is that data should be deleted promptly when the recruitment process ends. Longer retention requires a separate basis. The source identifies defense against claims\u2014referring to the three-year limitation period in Article 291 \u00a7 1 of the Labour Code\u2014and consent for future recruitment as possible considerations.<\/p>\n

              A talent pool needs its own purpose, legal basis and stated retention period. Consent for future searches must be specific, voluntary and withdrawable, and cannot be a condition of the current application.<\/p>\n

              What if an applicant volunteers health or trade union information?<\/h3>\n

              Do not request it as a routine application field. The source states that special-category data supplied on the applicant\u2019s initiative may be processed with consent given in the form of a declaration under Article 22\u00b9b of the Labour Code and Article 9 GDPR. Limit access to people authorized in writing, including when the information arrives in a shared inbox.<\/p>\n

              Do these employee-recruitment rules apply to B2B contractors?<\/h3>\n

              Articles 22\u00b9 and 18\u00b3ca of the Labour Code address employee recruitment, not automatically B2B contractor selection. GDPR duties\u2014including data minimization, a privacy notice and a defined retention period\u2014still matter. The source identifies no confirmed equivalent B2B statutory duty to disclose rates or prohibition on pay-history questions; check for legislative developments when preparing a posting.<\/p>\n

              Could one posting lead to both an inspection and a claim?<\/h3>\n

              Yes. Excessive data collection may create GDPR exposure, employment-law issues may attract a PIP inspection, and discriminatory requirements may support an applicant\u2019s compensation claim. Reviewing the full recruitment process before reusing a template is more effective than correcting the published wording alone.<\/p>\n","protected":false},"excerpt":{"rendered":"

              Hiring in Poland? Review salary disclosures, applicant data, pay-history questions and GDPR notices across job postings, application forms and interviews.<\/p>\n","protected":false},"author":14,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"footnotes":"","sip_alt_url":"https:\/\/sawaryn.com\/publikacje\/ogloszenie-o-prace-rodo\/","sip_en_pl_url":"https:\/\/sawaryn.com\/en\/publikacje\/poland-job-posting-candidate-questions\/","sip_pair_uuid":"fe14f77a-ae53-4219-a07c-7a9612f658d3","sip_pair_state":"verified"},"categories":[1146,16],"tags":[1236,1206,1235,1237,506],"specialization":[1130],"practice_area":[],"class_list":["post-3118","post","type-post","status-publish","format-standard","hentry","category-employment","category-gdpr","tag-b2b-agreement","tag-gdpr","tag-labor-law","tag-personal-data-protection","tag-pip","specialization-employment-law"],"acf":[],"_links":{"self":[{"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/posts\/3118","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/users\/14"}],"replies":[{"embeddable":true,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/comments?post=3118"}],"version-history":[{"count":1,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/posts\/3118\/revisions"}],"predecessor-version":[{"id":3119,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/posts\/3118\/revisions\/3119"}],"wp:attachment":[{"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/media?parent=3118"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/categories?post=3118"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/tags?post=3118"},{"taxonomy":"specialization","embeddable":true,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/specialization?post=3118"},{"taxonomy":"practice_area","embeddable":true,"href":"https:\/\/sawaryn.com\/us\/wp-json\/wp\/v2\/practice_area?post=3118"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}