{"id":2699,"date":"2026-06-01T10:36:12","date_gmt":"2026-06-01T10:36:12","guid":{"rendered":"https:\/\/sawaryn.com\/uslugi\/gdpr-for-a-new-project\/"},"modified":"2026-07-14T16:42:09","modified_gmt":"2026-07-14T16:42:09","slug":"gdpr-for-a-new-project","status":"publish","type":"service","link":"https:\/\/sawaryn.com\/en\/uslugi\/gdpr-for-a-new-project\/","title":{"rendered":"GDPR for a new project"},"excerpt":{"rendered":"<p>We help companies clarify roles, data flows, legal frameworks, documentation, and risks before launching a new product, service, process, or sales channel. This allows the team to work more quickly and enables management to make the decision to launch the project with greater confidence. <\/p>\n","protected":false},"featured_media":0,"template":"","meta":{"_acf_changed":false},"specialization":[1215],"practice_area":[],"class_list":["post-2699","service","type-service","status-publish","hentry","specialization-gdpr"],"acf":{"short_description":"We help companies organise roles, data flows, legal bases, documents and risks before launching a new product, service, process or sales channel. This enables the team to move faster and allows the management board to decide whether to launch the project with greater confidence.","full_description":"<strong>Privacy by Design that does not slow down the launch of a new project<\/strong>\n\nWe help companies organise roles, data flows, legal bases, documents and risks before launching a new product, service, process or sales channel. This enables the team to move faster and allows the management board to decide whether to launch the project with greater confidence.\n\n<strong>Check your project's launch readiness<\/strong>\n<h2>THE CLIENT'S PROBLEM<\/h2>\nGDPR gaps most often emerge just before launch - when fixes cost the most\n\nTowards the end of implementation, it usually becomes clear that essential information is missing. Who is the controller, what data are you actually collecting (and why), how are you informing users, do you need a DPIA and what provisions must be included in contracts with suppliers? And because the product is already \u201calmost ready\u201d, every change means adjustments to IT, the user journey and another round of approvals.\n\n\u201cThe best time to address GDPR is while changes can still be made without undue difficulty. If we become involved a week before launch, we are no longer discussing strategy - we are trying to keep the deadline.\u201d\n\nThat is why we conduct this review before launch. Rather than adding clauses at the end, we establish the foundations: roles, legal bases, data flows, information obligations and the areas where problems may genuinely arise. At the end, you receive a short list of what must be done before launch, what would be beneficial and what can safely be added to the backlog.\n<h2>THE MOST COMMON PROBLEMS \/ CHALLENGES<\/h2>\n<strong>The project is ready, but personal data is addressed only at the end<\/strong>\n\nThe product is developed first, while personal data is left until the end. Suddenly, forms, consents, notices or access permissions in tools need to be changed.\n\nWe get involved earlier and put the processing model in order: what you collect, where it goes, who has access and on what legal basis. You receive a clear indication of what is required for launch and what can wait.\n\n<strong>Business benefit:<\/strong> fewer last-minute fixes and a smoother launch.\n\n<strong>Risk of inaction:<\/strong> a delayed implementation or rushed changes after launch.\n\n<strong>The team is unclear about who is responsible for what<\/strong>\n\nAt some point, a familiar problem arises: who is the controller, who is the processor and who is responsible for providing information to the user? Without clarity on this, it is difficult to proceed with contracts, policies and communications.\n\nWe define roles and responsibilities in practical terms: who is responsible for what, which contractual provisions are needed and how this should be communicated to users.\n\n<strong>Business benefit:<\/strong> faster alignment and less passing the issue back and forth between departments.\n\n<strong>Risk of inaction:<\/strong> unclear accountability, particularly when an incident occurs or a client raises a question.\n\n<strong>The new project uses forms, automation, integrations or profiling<\/strong>\n\nA new project quickly accumulates \u201cadd-ons\u201d: forms, CRM integrations, marketing automation tools, lead scoring and sometimes AI features. At some point, the team is no longer sure whether all of this can be launched without taking a risky shortcut.\n\nWe map the data flows and identify areas of heightened risk. Rather than causing alarm, we present the options: what to simplify, what to address organisationally and what to leave unchanged.\n\n<strong>Business benefit:<\/strong> a predictable launch without \u201csurprises\u201d along the way.\n\n<strong>Risk of inaction:<\/strong> launching a process that will need to be redesigned after its first few weeks of operation.\n\n<strong>Documents and communications are not keeping pace with the project<\/strong>\n\nThe product is ready, but the documents and communications are not keeping pace: privacy notices are out of date, consents do not \u201cmatch\u201d the form, the terms and conditions do not cover the new feature, and suppliers are waiting for contractual provisions.\n\nWe review what you have and tell you plainly what must be corrected before launch, what can be simplified and where discrepancies between the product and the documentation most often arise.\n\n<strong>Business benefit:<\/strong> a prompt, specific list of changes - without weeks of iterations.\n\n<strong>Risk of inaction:<\/strong> changes made \u201cin several places at once\u201d and unnecessary friction between teams.\n\n<strong>The management board must approve the project launch without a clear picture of the risks<\/strong>\n\nThe management board must decide whether to launch, but lacks a single, clear document setting out what data are involved, why they are needed, the applicable legal basis, where the risks lie and what is required for the \u201cgreen light\u201d.\n\nWe prepare decision-making material in plain language: the key risks, priorities and launch conditions. No lengthy legal memorandum, just a clear list of actions.\n\n<strong>Business benefit:<\/strong> a faster decision and risk control without paralysis.\n\n<strong>Risk of inaction:<\/strong> launching \u201con instinct\u201d or unnecessarily putting the project on hold.\n<h2>HOW OUR SOLUTION WORKS<\/h2>\nGDPR translated into project decisions - before you spend your budget on fixes\n\nYou do not receive a \u201clegal opinion\u201d that then needs to be explained to the team. You receive a launch-readiness plan: what to change in the product and process, what to finalise in documents and contracts, and whether you need a DPIA. Everything is prioritised so that it can simply be implemented.\n\n<strong>Project model analysis<\/strong>\n<ul>\n \t<li>reviewing the new product, service, process, tool or implementation,<\/li>\n \t<li>identifying the points at which personal data arise,<\/li>\n \t<li>understanding the business objective and planned launch.<\/li>\n<\/ul>\n<strong>Outcome:<\/strong> A brief description of the project's operating model from a personal-data perspective (what is collected, why and where it goes).\n\n<strong>Defining roles, legal bases and obligations<\/strong>\n<ul>\n \t<li>defining the parties' roles in the project,<\/li>\n \t<li>identifying the legal bases for processing,<\/li>\n \t<li>clarifying information, organisational and contractual obligations.<\/li>\n<\/ul>\n<strong>Outcome:<\/strong> A clear allocation of roles and responsibilities + a list of the required legal bases and information obligations.\n\n<strong>Data flow map (Privacy by Design)<\/strong>\n<ul>\n \t<li>organising data sources and the points at which data are used,<\/li>\n \t<li>identifying access to data by teams and suppliers,<\/li>\n \t<li>recommendations on data minimisation and adequacy.<\/li>\n<\/ul>\n<strong>Outcome:<\/strong> A data flow map with recommendations (data minimisation, access and retention).\n\n<strong>Assessment of gaps in documents and communications<\/strong>\n<ul>\n \t<li>reviewing notices, consents and provisions for terms and conditions and contracts,<\/li>\n \t<li>identifying gaps in user communications,<\/li>\n \t<li>identifying the changes needed before launch.<\/li>\n<\/ul>\n<strong>Outcome:<\/strong> A list of documents and communications to prepare or revise (what, where and in what order).\n\n<strong>Risk assessment and decision on a DPIA \/ additional safeguards<\/strong>\n<ul>\n \t<li>analysing areas of heightened risk,<\/li>\n \t<li>assessing profiling, automation, new integrations and unusual use cases,<\/li>\n \t<li>determining whether a DPIA or other safeguards are needed.<\/li>\n<\/ul>\n<strong>Outcome:<\/strong> Decision-making material: risks, priorities and a recommendation on whether a DPIA is needed and which safeguards are appropriate.\n\n<strong>Pre-launch implementation recommendations<\/strong>\n<ul>\n \t<li>prioritising actions,<\/li>\n \t<li>aligning GDPR requirements with marketing, sales, operations, IT and documentation,<\/li>\n \t<li>supporting the sequencing of pre-launch actions.<\/li>\n<\/ul>\n<strong>Outcome:<\/strong> A single prioritised list of pre-launch actions (for the team and the management board).\n<h2>WHO THIS SERVICE IS FOR<\/h2>\nWho will benefit most from this service\n\nThis service works best when the project has a specific launch date, involves several teams (marketing\/IT\/sales\/operations) and you need a clear \u201cyes, subject to conditions\u201d, rather than endless discussions about consents and documents.\n<ul>\n \t<li>Project Manager - is responsible for implementation and needs a specific action list to keep the project moving through the final stages.<\/li>\n \t<li>Product Manager \/ Head of Product - must translate personal-data issues into recommendations that marketing, IT, operations and partners can understand.<\/li>\n \t<li>Management Board Member \/ COO \/ CEO - wants to approve the project launch with a clear picture of the risks, responsibilities and conditions for a safe launch.<\/li>\n<\/ul>\n<h2>STAGES OF WORK<\/h2>\nHow we work together\n\nThe process is simple: first, we gather the facts about the project; then we make key decisions about data and risks; and finally, we prepare a list of pre-launch actions.\n\n<strong>Stage 1. Defining the project's objective and scope<\/strong>\n\nWe establish exactly what you are launching, when you plan to launch, where you collect data, which tools and suppliers you use, and who makes decisions on your side.\n\n<strong>What the client gains:<\/strong> a clear scope and no surprises during the project.\n\n<strong>Stage 2. Analysis of the processing model and risks<\/strong>\n\nWe review roles, legal bases, data flows and points of contact with marketing, sales, operations and technology.\n\n<strong>What the client gains:<\/strong> a structured picture of the risks and areas requiring a decision.\n\n<strong>Stage 3. Designing solutions and recommendations<\/strong>\n\nWe prepare practical recommendations: what to implement, what to change, which documents to prepare and whether a DPIA is needed.\n\n<strong>What the client gains:<\/strong> a specific action plan instead of a general opinion.\n\n<strong>Stage 4. Launch readiness<\/strong>\n\nWe provide an action list and help finalise critical items. If necessary, we review the final versions of communications\/documents before launch.\n\n<strong>What the client gains:<\/strong> confidence that the project can launch without rushed fixes afterwards.","icon":null,"order_within_specialization":0,"flexible_content":[{"acf_fc_layout":"hero","section_header":{"section_header":{"eyebrow":"","heading":"Privacy by Design, kt\u00f3re nie spowalnia wdro\u017cenia nowego projektu","heading_highlight_mode":"split","heading_split":{"small_part_text":"Privacy by Design,","strong_part_text":"that does not slow down the launch of a new project","":null,"small_part_size":"","strong_part_size":"","tag":"h2","style":"inherit","alignment":"inherit"},"description":"We help companies organise roles, data flows, legal bases, documents and risks before launching a new product, service, process or sales channel. This enables the team to move faster and allows the management board to decide whether to launch the project with greater confidence.","":null,"heading_tag":"h1","heading_style":"hero","alignment":"left"}},"actions":{"button_cluster":{"intro":"","buttons":[{"button":{"link":{"title":"Assess your project\u2019s readiness to launch","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":2654,"section_header":{"section_header":{"eyebrow":"","heading":"GDPR gaps most often emerge just before launch - when fixes cost the most.","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":"Towards the end of implementation, it usually becomes clear that essential information is missing. Who is the controller, what data are you actually collecting (and why), how are you informing users, do you need a DPIA and what provisions must be included in contracts with suppliers? And because the product is already \u201calmost ready\u201d, every change means adjustments to IT, the user journey and another round of approvals.","":null,"heading_tag":"h2","heading_style":"section","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":"CHALLENGES","heading":"the most common problems we solve","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":"","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"problem_title":"The project is ready, but personal data is addressed only at the end","teaser_description":"The product is developed first, while personal data is left until the end. Suddenly, forms, consents, notices or access permissions in tools need to be changed.","solution_title":"","solution_description":"<p>We get involved earlier and put the processing model in order: what you collect, where it goes, who has access and on what legal basis. You receive a clear indication of what is required for launch&quot; and what can wait.<\/p>\n\n<p><strong>Business benefit:<\/strong> fewer last-minute fixes and a smoother launch.<\/p>\n\n<p><strong>Risk of inaction:<\/strong> a delayed implementation or rushed changes after launch.<\/p>","icon":"","accent":"pink","open":false},{"problem_title":"The team is unclear about who is responsible for what","teaser_description":"At some point, a familiar problem arises: who is the controller, who is the processor and who is responsible for providing information to the user? Without clarity on this, it is difficult to proceed with contracts, policies and communications.","solution_title":"","solution_description":"<p>We define roles and responsibilities in practical terms: who is responsible for what, which contractual provisions are needed and how this should be communicated to users.<\/p>\n\n<p><strong>Business benefit:<\/strong> faster alignment and less passing the issue back and forth between departments.<\/p>\n\n<p><strong>Risk of inaction:<\/strong> unclear accountability, particularly when an incident occurs or a client raises a question.<\/p>","icon":"","accent":"violet","open":false},{"problem_title":"The new project uses forms, automation, integrations or profiling","teaser_description":"A new project quickly accumulates \u201cadd-ons\u201d: forms, CRM integrations, marketing automation tools, lead scoring and sometimes AI features. At some point, the team is no longer sure whether all of this can be launched without taking a risky shortcut.","solution_title":"","solution_description":"<p>We map the data flows and identify areas of heightened risk. Rather than causing alarm, we present the options: what to simplify, what to address organisationally and what to leave unchanged.<\/p>\n\n<p><strong>Business benefit:<\/strong> a predictable launch without &quot;surprises&quot; along the way.<\/p>\n\n<p><strong>Risk of inaction:<\/strong> launching a process that will need to be redesigned after its first few weeks of operation.<\/p>","icon":"","accent":"blue","open":false},{"problem_title":"Documents and communications are not keeping pace with the project","teaser_description":"The product is ready, but the documents and communications are not keeping pace: privacy notices are out of date, consents do not \u201cmatch\u201d the form, the terms and conditions do not cover the new feature, and suppliers are waiting for contractual provisions.","solution_title":"","solution_description":"<p>We review what you have and tell you plainly what must be corrected before launch, what can be simplified and where discrepancies between the product and the documentation most often arise.<\/p>\n\n<p><strong>Business benefit:<\/strong> a prompt, specific list of changes - without weeks of iterations.<\/p>\n\n<p><strong>Risk of inaction:<\/strong> changes made &quot;in several places at once&quot; and unnecessary friction between teams.<\/p>","icon":"","accent":"orange","open":false},{"problem_title":"The management board must approve the project launch without a clear picture of the risks","teaser_description":"The management board must decide whether to launch, but lacks a single, clear document setting out what data are involved, why they are needed, the applicable legal basis, where the risks lie and what is required for the \u201cgreen light\u201d.","solution_title":"","solution_description":"<p>We prepare decision-making material in plain language: the key risks, priorities and launch conditions. No lengthy legal memorandum, just a clear list of actions.<\/p>\n\n<p><strong>Business benefit:<\/strong> a faster decision and risk control without paralysis.<\/p>\n\n<p><strong>Risk of inaction:<\/strong> launching &quot;on instinct&quot; or unnecessarily putting the project on hold.<\/p>","icon":"","accent":"pink","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":"GDPR translated into project decisions - before you spend your budget on fixes","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 receive a \u201clegal opinion\u201d that then needs to be explained to the team. You receive a launch-readiness plan: what to change in the product and process, what to finalise in documents and contracts, and whether you need a DPIA. Everything is prioritised so that it can simply be implemented.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"title":"Project model analysis","description":"","body":"<ul>\n \t<li>reviewing the new product, service, process, tool or implementation,<\/li>\n \t<li>identifying the points at which personal data arise,<\/li>\n \t<li>understanding the business objective and planned launch.<\/li>\n<\/ul>\n&nbsp;","tags":"A brief description of the project's operating model from a personal-data perspective.","count":"","accent":"pink","icon":""},{"title":"Defining roles, legal bases and obligations","description":"","body":"<ul>\n \t<li>defining the parties' roles in the project,<\/li>\n \t<li>identifying the legal bases for processing,<\/li>\n \t<li>clarifying information, organisational and contractual obligations.<\/li>\n<\/ul>\n&nbsp;","tags":"A clear allocation of roles and responsibilities + a list of the required legal bases and information obligations.","count":"","accent":"violet","icon":""},{"title":"Data flow map (Privacy by Design)","description":"","body":"<ul>\n \t<li>organising data sources and the points at which data are used,<\/li>\n \t<li>identifying access to data by teams and suppliers,<\/li>\n \t<li>recommendations on data minimisation and adequacy.<\/li>\n<\/ul>\n&nbsp;","tags":"A data flow map with recommendations.","count":"","accent":"blue","icon":""},{"title":"Assessment of gaps in documents and communications","description":"","body":"<ul>\n \t<li>reviewing notices, consents and provisions for terms and conditions and contracts,<\/li>\n \t<li>identifying gaps in user communications,<\/li>\n \t<li>identifying the changes needed before launch.<\/li>\n<\/ul>\n&nbsp;","tags":"A list of documents and communications to prepare or revise.","count":"","accent":"orange","icon":""},{"title":"Risk assessment and decision on a DPIA \/ additional safeguards","description":"","body":"<ul>\n \t<li>analysing areas of heightened risk,<\/li>\n \t<li>assessing profiling, automation, new integrations and unusual use cases,<\/li>\n \t<li>determining whether a DPIA or other safeguards are needed.<\/li>\n<\/ul>\n&nbsp;","tags":"Decision-making material: risks, priorities and a recommendation on whether a DPIA is needed.","count":"","accent":"pink","icon":""},{"title":"Pre-launch implementation recommendations","description":"","body":"<ul>\n \t<li>prioritising actions,<\/li>\n \t<li>aligning GDPR requirements with marketing, sales, operations, IT and documentation,<\/li>\n \t<li>supporting the sequencing of pre-launch actions.<\/li>\n<\/ul>\n&nbsp;","tags":"A single prioritised list of pre-launch actions (for the team and the management board).","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":"who will benefit most from this service","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":"This service works best when the project has a specific launch date, involves several teams (marketing\/IT\/sales\/operations) and you need a clear \u201cyes, subject to conditions\u201d, rather than endless discussions about consents and documents.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"items":[{"title":"Project Manager","description":"","body":"is responsible for implementation and needs a specific action list to keep the project moving through the final stages.","tags":"","count":"","accent":"pink","icon":""},{"title":"Product Manager \/ Head of Product","description":"","body":"must translate personal-data issues into recommendations that marketing, IT, operations and partners can understand.","tags":"","count":"","accent":"violet","icon":""},{"title":"Management Board Member \/ COO \/ CEO","description":"","body":"wants to approve the project launch with a clear picture of the risks, responsibilities and conditions for a safe launch.","tags":"","count":"","accent":"blue","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":"how we work together","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 gather the facts about the project; then we make key decisions about data and risks; and finally, we prepare a list of pre-launch actions.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"steps":[{"title":"Project scope and objectives","description":"We clarify exactly what you plan to launch, when you plan to launch it, where you collect data, which tools and suppliers you use, and who makes decisions on your side.","accent":"pink"},{"title":"Processing model and risk analysis","description":"We review roles, legal bases, data flows, and touchpoints with marketing, sales, operations and technology.","accent":"violet"},{"title":"Solutions and recommendations","description":"We prepare practical recommendations: what to implement or change, which documents to prepare, and whether a DPIA is needed.","accent":"blue"},{"title":"Ready to launch","description":"We provide an action list and help close critical items. If needed, we review the final versions of communications and documents before launch.","accent":"orange"}],"cta_text":"Check whether the project is ready to launch.","actions":{"button_cluster":{"intro":"","buttons":[{"button":{"link":{"title":"Assess your project\u2019s readiness to launch","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":"Do you have a project to launch? Let us conduct a quick pre-launch GDPR review","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 30-60 minutes, we will review the project with you and explain plainly what is blocking the launch, what needs to be done now and what can wait.\n\nBriefly tell us what the project involves, when you plan to launch and where personal data arise. We will send you a proposed scope and the first 3-5 steps worth taking.","":null,"heading_tag":"h2","heading_style":"section","alignment":"center"}},"person":2654,"person_eyebrow":"","person_body":"","response_title":"","response_body":"","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":"Sprawd\u017a gotowo\u015b\u0107 projektu do startu"},"background":"","section_meta":{"anchor_id":"","is_enabled":true}}]},"_links":{"self":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/service\/2699","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\/2699\/revisions"}],"wp:attachment":[{"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/media?parent=2699"}],"wp:term":[{"taxonomy":"specialization","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/specialization?post=2699"},{"taxonomy":"practice_area","embeddable":true,"href":"https:\/\/sawaryn.com\/en\/wp-json\/wp\/v2\/practice_area?post=2699"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}