{"id":2764,"date":"2026-06-01T10:40:16","date_gmt":"2026-06-01T10:40:16","guid":{"rendered":"https:\/\/sawaryn.com\/uslugi\/collaboration-with-a-personal-data-processor\/"},"modified":"2026-07-14T17:04:25","modified_gmt":"2026-07-14T17:04:25","slug":"collaboration-with-a-personal-data-processor","status":"publish","type":"service","link":"https:\/\/sawaryn.com\/en\/uslugi\/collaboration-with-a-personal-data-processor\/","title":{"rendered":"Collaboration with a Personal Data Processor"},"excerpt":{"rendered":"

We define roles, responsibilities, and guidelines for working with the supplier, and then translate them into documents and simple guidelines for the teams.<\/p>\n","protected":false},"featured_media":0,"template":"","meta":{"_acf_changed":false},"specialization":[1215],"practice_area":[],"class_list":["post-2764","service","type-service","status-publish","hentry","specialization-gdpr"],"acf":{"short_description":"We organise roles, accountability and the rules of cooperation with the vendor, then translate them into documents and simple guidelines for teams.","full_description":"A secure model of cooperation with a data-processing vendor<\/strong>\n\nWe organise roles, accountability and the rules of cooperation with the vendor, then translate them into documents and simple guidelines for teams.\n\nA working meeting on the data-flow map and the split of accountability. HR should communicate: \u201cwe have a plan and we hold the helm\u201d.\n

CLIENT PROBLEM<\/h2>\nA vendor can be onboarded quickly. It is harder to repair a poorly set relationship later, when questions arise about accountability, data security or the partner\u2019s real scope of duties.\n\n\u201cThe greatest risk usually does not come from the absence of a single document. It comes from the fact that the real cooperation model does not match what the parties signed.\u201d\n\nIn practice it is rarely only about the data processing agreement. More often the problem is a lack of clarity: whether the vendor acts as a processor, a joint controller or a separate controller; who takes accountability for incidents; what the subcontractor chain looks like; where the data go; and what we do when the business wants to move faster than the documentation. The result? Chaos between legal, IT, security, procurement and the process owner. We bring that chaos into order.\n

MOST COMMON PROBLEMS \/ CHALLENGES<\/h2>\nIt is unclear what role the vendor really has<\/strong>\n\nA technology partner, outsourcer or agency processes data - but no one in the organisation is sure whether it is a processor, a joint controller or a separate controller.\n\nWe check how the cooperation works in practice and, on that basis, qualify the parties\u2019 roles (not by the name in the contract).\n\nBusiness benefit:<\/strong> a faster decision and a lower risk of misclassification.\n\nRisk of inaction:<\/strong> accountability \u201cin the dark\u201d, flawed documents and costly corrections after the fact.\n\nThere is a contract, but it does not protect what happens in practice<\/strong>\n\nCooperation started quickly and the documentation did not keep up with the process: the data scope, the roles and the parties\u2019 accountability.\n\nWe organise the cooperation model and prepare (or negotiate) provisions that match how the relationship works operationally.\n\nBusiness benefit:<\/strong> fewer disputes, less ambiguity and greater predictability.\n\nRisk of inaction:<\/strong> the document exists, but it does not give control over what the vendor actually does.\n\nCloud, transfers and subcontractors sit outside the organisation\u2019s visibility<\/strong>\n\nYou use SaaS or a global vendor, but you do not have the full picture: where the data are processed, who the further processor is and whether transfers are involved.\n\nWe verify the processing chain, the cloud model, subcontractors and the key risks linked to data transfers.\n\nBusiness benefit:<\/strong> greater control over what you hand outside - and on what terms.\n\nRisk of inaction:<\/strong> hidden problems surface only at an audit, an incident or an escalation to the management board.\n\nNo one knows what to do in an incident or a data subject request<\/strong>\n\nAn incident, a complaint or a data subject request arises - and it suddenly turns out that the vendor side has no clear operating rules.\n\nWe set the rules of operational cooperation: reporting, incident handling, audits, instructions and the split of accountability.\n\nBusiness benefit:<\/strong> a shorter response time and less improvisation in critical situations.\n\nRisk of inaction:<\/strong> chaos, delays and a dispute over who should have taken the first step.\n\nVendor onboarding slows the business down<\/strong>\n\nProcurement, IT and operations want to onboard a partner quickly, but simple assessment criteria and a repeatable decision path are missing.\n\nWe translate legal and contractual requirements into checklists, qualification rules and practical guidelines for internal teams.\n\nBusiness benefit:<\/strong> faster implementations and fewer escalations to the management board or lawyers for every cooperation.\n\nRisk of inaction:<\/strong> you analyse every relationship from scratch, friction between departments grows and the pace of decisions falls.\n

HOW OUR SOLUTION WORKS<\/h2>\nWe structure cooperation with the processor so it works in practice - not only on paper<\/strong>\n\nThis service does not end with a DPA. We start with a diagnosis, then decide on the cooperation model, finalise the contract and implement the rules into the teams\u2019 day-to-day work.\n\nDiagnosis of the relationship and data flow<\/strong>\n
    \n \t
  • we analyse the vendor, the service and the business process<\/li>\n \t
  • we identify the data scope and the touchpoints<\/li>\n \t
  • we review the current documents and operational arrangements<\/li>\n<\/ul>\nOutcome:<\/strong> A map of the relationship, data flow and key risk points.\n\nRole qualification and model decisions<\/strong>\n
      \n \t
    • we assess whether the partner acts as a processor, a joint controller or a separate controller<\/li>\n \t
    • we show the legal and operational consequences of each option<\/li>\n \t
    • we recommend the safest cooperation model<\/li>\n<\/ul>\nOutcome:<\/strong> A clear recommendation of the cooperation model - with a business rationale.\n\nContract documents and negotiations<\/strong>\n
        \n \t
      • we prepare or review the data processing agreement<\/li>\n \t
      • we refine provisions on accountability, audits, incidents and security<\/li>\n \t
      • we support alignment with the vendor or partner<\/li>\n<\/ul>\nOutcome:<\/strong> Contractual provisions ready to sign or negotiate.\n\nVerification of cloud, subcontractors and transfers<\/strong>\n
          \n \t
        • we check further processors and the full processing chain<\/li>\n \t
        • we assess data location and the cloud service model<\/li>\n \t
        • we indicate risks that require a decision or additional safeguards<\/li>\n<\/ul>\nOutcome:<\/strong> A list of key risks and recommendations for a SaaS, cloud or outsourcing model.\n\nRules of operational cooperation<\/strong>\n
            \n \t
          • we set reporting and incident-handling rules<\/li>\n \t
          • we define the audit mode and information exchange<\/li>\n \t
          • we clarify instructions and accountability on both sides<\/li>\n<\/ul>\nOutcome:<\/strong> A clear operating model for day-to-day work and critical situations.\n\nImplementation tools for the organisation<\/strong>\n
              \n \t
            • a checklist for procurement, IT, security and operations<\/li>\n \t
            • a set of requirements for new vendors<\/li>\n \t
            • recommendations for repeatable partner onboarding<\/li>\n<\/ul>\nOutcome:<\/strong> Ready tools that speed up decisions and organise cooperation across the organisation.\n

              WHO THIS SERVICE IS FOR<\/h2>\nFor organisations that want to move faster - without handing accountability outside their control<\/strong>\n\nThis service is especially useful when the topic must be closed commercially, but also set so it does not return at the next audit, incident or vendor implementation.\n\nProcurement Manager \/ Vendor Manager - when you need to assess a vendor quickly, set the cooperation terms and give the business a clear \u201cgo \/ stop \/ change the model\u201d.\n\nData Protection Officer \/ Compliance Manager - when you need a clear qualification of roles, order in accountability and a solution that can be implemented beyond the legal team.\n\nCOO \/ management board member \/ business process owner - when you want to limit hidden accountability, speed up decisions and organise cooperation with external partners at scale.\n

              STAGES OF WORK<\/h2>\nFour steps to an organised relationship with the processor<\/strong>\n\nThe process is simple: first we check how this cooperation actually works. Then we organise the model, the documents and the implementation rules.\n\nStage 1. Diagnosis of the model and risk points<\/strong>\n\nWe gather information about the vendor, the data flow, the partner\u2019s role and how the service works day to day.\n\nWhat the client gains:<\/strong> A full picture of the relationship - not only what is in the contract, but also how practice looks.\n\nStage 2. Qualification and model decisions<\/strong>\n\nWe assess the parties\u2019 roles, identify gaps and recommend a cooperation model matched to how the process actually runs.\n\nWhat the client gains:<\/strong> A clear decision on how to \u201cset\u201d the relationship and what that means for the business, compliance and accountability.\n\nStage 3. Documents and alignment with the partner<\/strong>\n\nWe prepare or negotiate contractual provisions and set the key rules of operational cooperation.\n\nWhat the client gains:<\/strong> A relationship organised contractually - with less room for disputes and misunderstandings.\n\nStage 4. Operational implementation and handover of tools<\/strong>\n\nWe translate the arrangements into checklists, guidelines and simple recommendations for the client\u2019s teams.\n\nWhat the client gains:<\/strong> A model that works day to day - including with subsequent vendors and implementations.","icon":"","order_within_specialization":0,"flexible_content":[{"acf_fc_layout":"hero","section_header":{"section_header":{"eyebrow":"","heading":"Before the vendor receives the data","heading_highlight_mode":"split","heading_split":{"small_part_text":"who has access","strong_part_text":"to client data?","":null,"small_part_size":"h1","strong_part_size":"hero","tag":"h2","style":"inherit","alignment":"inherit"},"description":"We will check which data reach the vendor, who is accountable for them and whether the contract properly describes the cooperation. If needed, we will prepare documents, procedures and checklists for the team.\n\n","":null,"heading_tag":"h1","heading_style":"h1","alignment":"left"}},"actions":{"button_cluster":{"intro":"","buttons":[{"button":{"link":{"title":"Book a brief call","url":"#contact","target":""},"variant":"primary","icon":"arrow","icon_size":"inherit","size":"default","aria_label":""}}],"alignment":"left"}},"media":{"media":{"image":"","mobile_image":"","object_position":"center","object_position_custom":""}},"section_meta":{"anchor_id":"","is_enabled":true},"variant":"split","mobile_body_card":false},{"acf_fc_layout":"person_cta","person":2697,"section_header":{"section_header":{"eyebrow":"","heading":"do not start with the contract","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"In a vendor relationship we too often jump straight to a document. Someone asks for a data processing agreement, someone else sends a ready template, and the management board is already under pressure to launch the service.\n\nBut first you need to establish what actually happens to the data: who decides on the purposes, who has access, where the data go, whether there are subprocessors, how deletion works and who responds to an incident. Only then does the document match the cooperation.","":null,"heading_tag":"h2","heading_style":"compact","alignment":"left"}},"carousel_settings":{"carousel_settings":{"autoplay_mode":"default","autoplay_delay":6.5}},"actions":{"button_cluster":{"intro":"","buttons":null,"alignment":"left"}}},{"acf_fc_layout":"expandable_box","section_header":{"section_header":{"eyebrow":"Most common challenges","heading":"When it becomes unclear","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"A vendor is meant to help with the work: implement a system, run a process, deliver a campaign, maintain a tool or take over part of the tasks. Along the way, however, it gains access to data. That is when you need to know whether the contract, the operating model and the parties\u2019 accountability truly align.\n\n","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"problem_title":"You do not know what role the vendor plays","teaser_description":"The vendor runs a system, a campaign, payroll, hosting or an IT process. In practice it may act solely on your instructions, but it may also decide itself on part of the data operations. That determines which documents are needed and who takes accountability for the cooperation.","solution_title":"that is why we verify it","solution_description":"We will establish the vendor\u2019s role in the specific cooperation model: processor, controller, joint controller or a mixed model. We will check whether a data processing agreement is enough, or whether other provisions, additional instructions or a contract change are needed.","icon":"","accent":"pink","open":false},{"problem_title":"The contract does not explain what happens to the data","teaser_description":"A document may be signed and still fail to answer the most important questions: which data reach the vendor, who has access to them, where they are stored, whether the vendor engages subcontractors and what happens after the cooperation ends.","solution_title":"that is why we make sure it clearly explains the rules of cooperation","solution_description":"We will review the contract, GDPR annexes, instructions, the subcontractor list, transfers and deletion rules. We will indicate what needs to be added, corrected or clarified with the vendor so the documents describe the service as it works in practice.","icon":"","accent":"violet","open":false},{"problem_title":"You do not control where the data go","teaser_description":"You use SaaS, cloud or a global tool. In the contract you see one vendor, but hosting, support, subcontractors, integrations or entities outside the EEA may also be involved in the service.","solution_title":"that is why we verify the processing chain","solution_description":"We will check who really takes part in working with the data: where they are stored, who has access, whether the vendor uses subcontractors and whether data leave the EEA. ","icon":"","accent":"blue","open":false},{"problem_title":"You do not know what to do in an incident ","teaser_description":"An incident, a complaint or a data subject request arises. There is then no time to work out from scratch who contacts the vendor, where the data are, what information must be gathered and which deadlines are already running.","solution_title":"that is why we create a process","solution_description":"We will set out the rules for such situations. You will know who reports the matter, who responds on the vendor\u2019s side, what information must be shared, how to document the response and when to involve legal, the DPO or the management board.","icon":"","accent":"orange","open":false}],"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"box_variants","variant":"process-detail","section_header":{"section_header":{"eyebrow":"Our solution","heading":"We will improve your relationship with the vendor","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"We do not stop at a DPIA, a question table or a list of items \u201cfor further analysis\u201d. If a vendor is to work on data, we help take the whole topic through: from defining roles and data flows, through document review, to contract corrections, procedures and working rules for the team.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"title":"We will define the roles","description":"","body":"Before a contract is drafted, you need to know whether the vendor is a processor, a controller, a joint controller or plays several roles at once.\n\n \n

              We can:<\/p>\n\n

                \n \t
              • analyse the vendor cooperation model,<\/li>\n \t
              • establish who decides on the purposes and means of processing,<\/li>\n \t
              • check whether a data processing agreement is the right document,<\/li>\n \t
              • identify where the parties\u2019 roles are unclear,<\/li>\n \t
              • prepare a rationale for the DPO, the management board or the business.<\/li>\n<\/ul>\n \n\nThe result of this stage is","tags":"roles and data-flow matrix","count":"","accent":"pink","icon":""},{"title":"We will check what the vendor does with the data","description":"","body":"

                Before you sign a contract or grant access, you need to know what service the vendor is to perform, which data it will receive, who else may see them and whether the documents describe what the vendor may do with the data.<\/p>\n

                We can:<\/p>\n\n

                  \n \t
                • review the contract, annexes, service description, vendor policies and tool information<\/li>\n \t
                • establish which data will reach the vendor and what they will be used for<\/li>\n \t
                • check whether the vendor uses subcontractors, cloud, support or tools outside Europe<\/li>\n \t
                • prepare questions for the vendor, without leaving you with a list of doubts alone<\/li>\n \t
                • turn the vendor\u2019s answers into a decision: what can be accepted, what must be corrected, and what should not be signed without changes<\/li>\n<\/ul>\n \n\nThe results are:","tags":"vendor cooperation assessment\naccess map","count":"","accent":"violet","icon":""},{"title":"We will prepare the contracts","description":"","body":"

                  If the relationship requires documents, we will prepare them for the specific service, not a template. The contract should describe precisely and simply what the vendor does with the data, not merely repeat the legislation.<\/p>\n

                  We can:<\/strong><\/p>\n\n

                    \n \t
                  • prepare a data processing agreement,<\/li>\n \t
                  • correct the GDPR annex to the main contract,<\/li>\n \t
                  • add processing instructions, data categories and the parties\u2019 duties,<\/li>\n \t
                  • regulate subprocessors, transfers, audits, incidents and termination of cooperation,<\/li>\n \t
                  • prepare provisions for a contract with a controller or joint controller if processing on behalf does not fit the relationship.<\/li>\n<\/ul>\n \n\nThe results of this stage are:","tags":"contracts\ncontract annexes\nclauses, including NDAs\ninstructions for each vendor separately","count":"","accent":"blue","icon":""},{"title":"We will implement procedures","description":"","body":"The problem does not end when the contract is signed. Someone in the company must know when to check the vendor, which questions to ask and who approves the cooperation before the service goes live.\n\n \n\nWe can:\n
                      \n \t
                    • prepare a vendor selection and approval procedure,<\/li>\n \t
                    • create a checklist for procurement, HR, marketing, IT or operations,<\/li>\n \t
                    • describe the vendor approval path through legal, the DPO, compliance or the management board,<\/li>\n \t
                    • establish what must be checked before signing the contract,<\/li>\n \t
                    • prepare rules for updating documents after a change of vendor or service.<\/li>\n<\/ul>\n \n\nThe result is:","tags":"processor cooperation procedure","count":"","accent":"orange","icon":""},{"title":"We will check whether your documents are correct","description":"","body":"Sometimes the documents look fine but do not match how the service works. More people have access to the data, data are exported, the vendor uses subcontractors, and deletion after the cooperation ends is not described.\n\n \n

                      We can:<\/p>\n\n

                        \n \t
                      • compare the contract with how the service operates,<\/li>\n \t
                      • check access, the data scope, retention periods and deletion methods,<\/li>\n \t
                      • identify gaps between the vendor\u2019s declarations and the documents,<\/li>\n \t
                      • prepare a list of questions to clarify with the vendor.<\/li>\n<\/ul>\n \n\nThe results of this stage are","tags":"audit\nlist of gaps and corrections\nrecommendations","count":"","accent":"pink","icon":""},{"title":"We will prepare the team","description":"","body":"

                        The best document will not help if the people buying services do not know when to involve legal, the DPO or compliance. That is why we can prepare simple materials for working with vendors.<\/p>\n

                        We can:<\/p>\n\n

                          \n \t
                        • prepare guidance for people selecting vendors,<\/li>\n \t
                        • write a checklist before buying a tool or services,<\/li>\n \t
                        • prepare a team message about the new cooperation rules,<\/li>\n \t
                        • indicate when the matter requires consultation with legal, the DPO or the management board,<\/li>\n \t
                        • help explain to the team what not to declare without checking first.<\/li>\n<\/ul>\n \n\nThe results are","tags":"checklist\nguidance\nmessage\nimplementation materials\naction path before vendor selection","count":"","accent":"violet","icon":""}],"footer_heading":"","footer_tags":"","actions":{"button_cluster":{"intro":"","buttons":null,"alignment":"left"}},"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"box_variants","variant":"box-point","section_header":{"section_header":{"eyebrow":"Who this service is for","heading":"For organisations that want data under control","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"Working with a processor rarely belongs to one department alone. Someone selects the tool, someone negotiates the contract, someone is accountable for the data, someone must prepare the company for an audit, and someone ultimately takes accountability for the decision.\n\nWe help those people structure the vendor relationship so it is clear who is accountable, what must be signed and how to work with the vendor after the service starts.\n\n","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"title":"Legal | in-house","description":"When the contract is almost ready, but you need to check whether roles, GDPR annexes, subprocessors, transfers and the parties\u2019 accountability are properly described.\n\nWe help translate the cooperation model into provisions that can be signed and applied.","body":"","tags":"contracts\nroles\nprovisions","count":"","accent":"orange","icon":""},{"title":"DPO | Compliance","description":"When you need to assess a vendor, check data flows, prepare documentation or answer questions from an auditor, a client or the management board.\n\nWe organise information about the data, the vendor, safeguards, transfers and subprocessors.","body":"","tags":"data\naudit\nprocedures","count":"","accent":"orange","icon":""},{"title":"Operation Manager ","description":"When you are selecting a vendor, but before signing the contract you need to know which questions to ask and which documents to collect.\n\nWe will prepare a checklist, an approval path and requirements worth sharing with the vendor before cooperation starts.","body":"","tags":"purchase\nvendor\napproval","count":"","accent":"orange","icon":""},{"title":"HJR","description":"When your team is implementing a tool, system, agency or service that will work on employee, client, candidate or user data.\n\nWe will help check what needs to be reported, which documents to prepare and when to involve legal, the DPO or compliance.","body":"","tags":"tools\ndata\nimplementation","count":"","accent":"orange","icon":""},{"title":"Management board | COO | CEO","description":"When cooperation with a vendor may affect the organisation\u2019s accountability, an audit, client relationships or data security.\n\nWe will prepare a short recommendation: what requires a decision, what must be corrected and whether cooperation can be launched in the current model.","body":"","tags":"decision\naccountability\nrisk","count":"","accent":"orange","icon":""}],"footer_heading":"","footer_tags":"","actions":{"button_cluster":{"intro":"","buttons":null,"alignment":"left"}},"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"cooperation_process","section_header":{"section_header":{"eyebrow":"Stages of work","heading":"Four steps to an organised relationship with the processor","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"The process is simple: first we check how this cooperation actually works. Then we organise the model, the documents and the implementation rules.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"steps":[{"title":"We analyse","description":"We establish who the supplier is, what service will be provided and what data will be processed.","accent":"pink"},{"title":"We review","description":"We review the roles, data scope, subprocessors, transfers, safeguards, incidents and termination of the relationship.","accent":"violet"},{"title":"We prepare","description":"We prepare or revise the data processing agreement, annexes, procedures, checklists or a recommendation for decision-makers.","accent":"blue"},{"title":"We implement","description":"If needed, we help explain the new rules to the team and establish a way of working with future suppliers.","accent":"orange"}],"cta_text":"Book a short call.","actions":{"button_cluster":{"intro":"","buttons":[{"button":{"link":{"title":"Book a brief call","url":"#contact","target":""},"variant":"primary","icon":"arrow","icon_size":"inherit","size":"default","aria_label":""}}],"alignment":"left"}},"section_meta":{"anchor_id":"","is_enabled":true}},{"acf_fc_layout":"contact","section_header":{"section_header":{"eyebrow":"Contact us","heading":"Let\u2019s start with a conversation about the vendor","heading_highlight_mode":"none","heading_split":{"small_part_text":"","strong_part_text":"","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"You do not need a ready diagnosis or full documentation. Tell us which service you want to launch, who is to receive access to the data and what decision you face. We will help establish what really needs to be checked before the next step.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"person":2654,"person_eyebrow":"Twoj\u0105 wiadomo\u015b\u0107 czyta","person_body":"They will get back to you with follow-up questions or a proposed next step.","response_title":"Quick response","response_body":"We usually respond within two hours on business days.","form":{"cf7_form":"","name_label":"Imi\u0119 lub nazwa podmiotu","name_placeholder":"Wpisz swoje dane","phone_label":"Telefon","phone_placeholder":"+48 000 000 000","email_label":"E-mail","email_placeholder":"twoj@email.pl","message_label":"Napisz, czego potrzebujesz","message_placeholder":"Opisz kr\u00f3tko sytuacj\u0119, etap rozm\u00f3w i termin decyzji.","privacy_text":"O\u015bwiadczam, \u017ce podane dane kontaktowe mog\u0105 zosta\u0107 wykorzystane do odpowiedzi na moje zg\u0142oszenie.","newsletter_text":"","button_label":"Wy\u015blij wiadomo\u015b\u0107"},"background":"","section_meta":{"anchor_id":"","is_enabled":true}}]},"_links":{"self":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service\/2764","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service"}],"about":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/types\/service"}],"version-history":[{"count":0,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service\/2764\/revisions"}],"wp:attachment":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/media?parent=2764"}],"wp:term":[{"taxonomy":"specialization","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/specialization?post=2764"},{"taxonomy":"practice_area","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/practice_area?post=2764"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}