{"id":6776,"date":"2026-06-05T08:10:45","date_gmt":"2026-06-05T07:10:45","guid":{"rendered":"https:\/\/www.superdocu.com\/en\/blog\/is-an-email-address-pii\/"},"modified":"2026-06-05T08:10:50","modified_gmt":"2026-06-05T07:10:50","slug":"is-an-email-address-pii","status":"publish","type":"post","link":"https:\/\/www.superdocu.com\/en\/blog\/is-an-email-address-pii\/","title":{"rendered":"Is an Email Address PII? a Practical Guide for Businesses"},"content":{"rendered":"<p>Yes, an email address is <strong>PII in almost all business contexts<\/strong>. If your business collects client, employee, or applicant emails, you should treat those addresses as personal data by default and handle them with the same care you&#039;d apply to other identifying information.<\/p>\n<p>That answer matters because most small businesses already know email feels sensitive, but many still handle it casually. They collect addresses through website forms, forward documents through inboxes, store exports in spreadsheets, and give broad staff access because it seems harmless. That gap between knowing and doing is where privacy problems start. It&#039;s also where trust breaks down. If you&#039;re collecting documents for onboarding, hiring, legal intake, or customer verification, understanding when an email address is PII, and what low-overhead controls are effective, helps you reduce compliance risk while showing clients you take their information seriously.<\/p>\n<p><a id=\"why-asking-about-email-and-pii-is-the-right-question\"><\/a><\/p>\n<h2>Table of Contents<\/h2>\n<ul>\n<li><a href=\"#why-asking-about-email-and-pii-is-the-right-question\">Why Asking About Email and PII Is the Right Question<\/a><\/li>\n<li><a href=\"#the-short-answer-is-yes-understanding-email-as-pii\">The Short Answer Is Yes Understanding Email as PII<\/a><ul>\n<li><a href=\"#why-email-counts-as-identifying-information\">Why email counts as identifying information<\/a><\/li>\n<li><a href=\"#why-businesses-get-this-wrong-in-practice\">Why businesses get this wrong in practice<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#how-major-privacy-laws-treat-email-addresses\">How Major Privacy Laws Treat Email Addresses<\/a><ul>\n<li><a href=\"#what-the-legal-definitions-mean-in-plain-english\">What the legal definitions mean in plain English<\/a><\/li>\n<li><a href=\"#a-practical-comparison-for-business-owners\">A practical comparison for business owners<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#beyond-the-inbox-context-and-risk-scenarios\">Beyond the Inbox Context and Risk Scenarios<\/a><ul>\n<li><a href=\"#when-a-role-address-may-not-be-pii\">When a role address may not be PII<\/a><\/li>\n<li><a href=\"#how-context-changes-the-risk\">How context changes the risk<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#practical-steps-for-handling-email-pii-securely\">Practical Steps for Handling Email PII Securely<\/a><ul>\n<li><a href=\"#start-with-collection-not-storage\">Start with collection not storage<\/a><\/li>\n<li><a href=\"#set-controls-that-small-teams-will-actually-follow\">Set controls that small teams will actually follow<\/a><\/li>\n<li><a href=\"#reduce-exposure-across-the-full-lifecycle\">Reduce exposure across the full lifecycle<\/a><\/li>\n<\/ul>\n<\/li>\n<li><a href=\"#building-trust-through-smart-data-handling\">Building Trust Through Smart Data Handling<\/a><\/li>\n<\/ul>\n<h2>Why Asking About Email and PII Is the Right Question<\/h2>\n<p>A lot of business owners ask this when they&#039;re setting up something ordinary. A contact form for new leads. An intake flow for legal clients. A hiring process that starts with a resume upload and an email field. The question sounds simple, but it&#039;s attached to a bigger operational decision: do you handle that email like basic contact info, or like regulated personal data?<\/p>\n<p>That&#039;s where people get stuck. They&#039;re not confused about whether email is important. They&#039;re unsure what the label changes in real life. Does it mean they need consent? Encryption? Tighter access? Different retention rules? A separate workflow for document requests?<\/p>\n<p>In practice, the question usually appears when a business moves from casual communication to structured collection. A law firm starts requesting IDs and proof of address. An HR team collects applicant files. A mortgage broker asks clients to upload financial documents. The email address becomes the anchor field that ties everything together: inbox messages, uploaded files, reminders, case notes, and status updates.<\/p>\n<blockquote>\n<p><strong>Practical rule:<\/strong> If an email address connects a person to a record, a workflow, or a set of documents, treat it as personal data from the start.<\/p>\n<\/blockquote>\n<p>That approach is safer and simpler than trying to sort every email field into a legal gray area after the fact. Most small businesses don&#039;t get into trouble because they misunderstood a definition. They get into trouble because they built everyday workflows around convenience, then discovered too late that the inbox, shared drive, and spreadsheet had become a shadow client database.<\/p>\n<p>The right question isn&#039;t only \u201cis an email address PII.\u201d It&#039;s \u201cwhat changes in my business if the answer is yes?\u201d That&#039;s the point where privacy stops being abstract and becomes operational.<\/p>\n<p><a id=\"the-short-answer-is-yes-understanding-email-as-pii\"><\/a><\/p>\n<h2>The Short Answer Is Yes Understanding Email as PII<\/h2>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/www.superdocu.com\/wp-content\/uploads\/2026\/06\/is-an-email-address-pii-digital-security-1.jpg\" alt=\"A digital key shaped like an envelope unlocking a high-security lock representing digital identity protection.\" \/><\/figure><\/p>\n<p>An email address works like a digital mailing address tied to a person. It gives you a direct way to identify or contact someone, which is why privacy programs usually treat it as <strong>personally identifiable information<\/strong>.<\/p>\n<p><a id=\"why-email-counts-as-identifying-information\"><\/a><\/p>\n<h3>Why email counts as identifying information<\/h3>\n<p>The clearest official statement comes from the U.S. government. The <a href=\"https:\/\/finance.ocfo.gsa.gov\/pii\/piinotice.aspx?token=PI002\" target=\"_blank\" rel=\"noopener\">U.S. General Services Administration guidance on PII<\/a> explicitly lists a <strong>personal email address<\/strong> as an example of PII, alongside names, home addresses, Social Security numbers, and phone numbers. It also says that information enabling physical or online contact with a specific individual counts as PII.<\/p>\n<p>That matters because it answers the practical business question directly. If a piece of data lets your team reach a specific person, or tie a record to that person, it isn&#039;t just harmless contact information. It&#039;s identifying data.<\/p>\n<p>For a small business, the distinction becomes obvious once you look at real workflows. A client&#039;s email isn&#039;t sitting alone in a vacuum. It appears in proposal software, billing tools, support threads, onboarding checklists, e-signature requests, and portal invitations. Once that happens, the email address becomes a stable identity marker across your systems.<\/p>\n<blockquote>\n<p>Email often feels low risk because people share it freely. That doesn&#039;t make it non-personal. It makes it widely exposed and easy to misuse.<\/p>\n<\/blockquote>\n<p><a id=\"why-businesses-get-this-wrong-in-practice\"><\/a><\/p>\n<h3>Why businesses get this wrong in practice<\/h3>\n<p>The common mistake is treating email as \u201cjust contact info\u201d while protecting only the document or attachment that comes with it. That creates a blind spot. If a staff member can browse a shared sheet of client emails, search past intake conversations, or export addresses from multiple systems, they can still access personal data even without opening a passport scan or tax form.<\/p>\n<p>A useful way to think about it is this:<\/p>\n<ul>\n<li><strong>An email address identifies the person<\/strong><\/li>\n<li><strong>The surrounding records add context<\/strong><\/li>\n<li><strong>The combination raises the privacy risk<\/strong><\/li>\n<\/ul>\n<p>That&#039;s why \u201cis an email address PII\u201d isn&#039;t really a trick question. In business operations, the answer is usually yes because the address points to a real person and often reveals a much wider record.<\/p>\n<p>If you want a workable default, use this one:<\/p>\n<ul>\n<li><strong>Personal email address:<\/strong> Treat it as PII.<\/li>\n<li><strong>Individual work email tied to a person:<\/strong> Treat it as PII unless you have a very narrow reason not to.<\/li>\n<li><strong>Shared mailbox or generic role address:<\/strong> Review context before deciding.<\/li>\n<\/ul>\n<p>That default won&#039;t solve every edge case, but it will stop most of the avoidable mistakes.<\/p>\n<p><a id=\"how-major-privacy-laws-treat-email-addresses\"><\/a><\/p>\n<h2>How Major Privacy Laws Treat Email Addresses<\/h2>\n<p>Business owners don&#039;t need to memorize legal text. They need to know what regulators and privacy frameworks generally expect them to do with an email field in the systems they already use. Across major rulesets, the direction is consistent: if an email address identifies or can be linked to a person, it falls inside the scope of protected personal data.<\/p>\n<p><a id=\"what-the-legal-definitions-mean-in-plain-english\"><\/a><\/p>\n<h3>What the legal definitions mean in plain English<\/h3>\n<p>Under broad privacy definitions, email qualifies because it can identify, distinguish, or contact an individual directly, and it can become even more revealing when combined with other data. <a href=\"https:\/\/piwik.pro\/blog\/what-is-pii-personal-data\/\" target=\"_blank\" rel=\"noopener\">Piwik PRO&#039;s overview of PII and personal data<\/a> explains that NIST-based guidance explicitly includes email addresses in PII, and public-PII examples also list work email addresses as identifying information.<\/p>\n<p>The GDPR frames this through the term <strong>personal data<\/strong>. If information relates to an identified or identifiable person, it&#039;s covered. In plain English, if you can connect an email address to a real individual in your business workflow, you should assume GDPR-style obligations can apply when that law is relevant to your operations.<\/p>\n<p>California laws use slightly different terminology, but the practical result is similar for most businesses. If the data identifies, relates to, or can reasonably be linked with a person or household, the email address won&#039;t sit outside the privacy program just because it looks routine.<\/p>\n<p>That&#039;s why the legal question for an SMB usually isn&#039;t \u201cdoes this exact law use the term PII or personal data?\u201d The better question is \u201cwould this email address help us identify, contact, or profile a real person?\u201d If the answer is yes, your handling should reflect that.<\/p>\n<p>For teams building intake and consent workflows, tools built for structured collection can help reduce ad hoc form problems. If you&#039;re reviewing options for privacy-friendly submissions, <a href=\"https:\/\/orbitforms.ai\/gdpr\" target=\"_blank\" rel=\"noopener\">Orbit AI for GDPR forms<\/a> is one example of a tool category designed around that need.<\/p>\n<p><a id=\"a-practical-comparison-for-business-owners\"><\/a><\/p>\n<h3>A practical comparison for business owners<\/h3>\n\n<figure class=\"wp-block-table\"><table><tr>\n<th>Regulation<\/th>\n<th>Is an Email Address PII\/Personal Data?<\/th>\n<th>Key Requirement<\/th>\n<\/tr>\n<tr>\n<td>GDPR<\/td>\n<td>Yes, when it relates to an identified or identifiable natural person<\/td>\n<td>Use a lawful basis, provide transparency, and apply appropriate security and governance<\/td>\n<\/tr>\n<tr>\n<td>CCPA\/CPRA<\/td>\n<td>Generally yes when it identifies, relates to, or can be linked to a consumer or household<\/td>\n<td>Disclose collection and use practices, and support applicable consumer rights<\/td>\n<\/tr>\n<tr>\n<td>NIST-based and public PII guidance<\/td>\n<td>Yes, including email addresses in common definitions of identifying information<\/td>\n<td>Classify it as protected data and control access and handling accordingly<\/td>\n<\/tr>\n<\/table><\/figure>\n<p>Small businesses often overcomplicate this. They assume compliance starts with a giant policy rewrite. It usually starts with classification. If your CRM, intake form, and document request tool all treat email as ordinary metadata, your privacy controls won&#039;t match the actual risk.<\/p>\n<p>A simple fix is to map where email enters your business, then ask what attaches to it. If a submitted address links to invoices, identity documents, HR notes, or legal files, the address should trigger controlled handling. A good companion resource for reviewing that broader operational posture is this <a href=\"https:\/\/www.superdocu.com\/en\/blog\/gdpr-compliance-checklist\/\">GDPR compliance checklist for document workflows<\/a>.<\/p>\n<p><a id=\"beyond-the-inbox-context-and-risk-scenarios\"><\/a><\/p>\n<h2>Beyond the Inbox Context and Risk Scenarios<\/h2>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/www.superdocu.com\/wp-content\/uploads\/2026\/06\/is-an-email-address-pii-email-comparison-1.jpg\" alt=\"A graphic illustration comparing a business email address and a personal email address with a question mark.\" \/><\/figure><\/p>\n<p>The simple answer is yes, but context still matters. Not every address creates the same privacy risk, and small businesses get better results when they stop treating every email field as identical.<\/p>\n<p><a id=\"when-a-role-address-may-not-be-pii\"><\/a><\/p>\n<h3>When a role address may not be PII<\/h3>\n<p>The most important edge case is the generic or role-based mailbox. <a href=\"https:\/\/www.iubenda.com\/en\/blog\/is-email-address-pii\/\" target=\"_blank\" rel=\"noopener\">Iubenda&#039;s guidance on whether an email address is PII<\/a> notes that addresses like <strong><a href=\"mailto:info@company.com\">info@company.com<\/a><\/strong> are often not considered PII because they identify an organization rather than a natural person.<\/p>\n<p>That&#039;s a real distinction. If you collect <code>support@vendor.com<\/code>, you usually aren&#039;t collecting a person-level identifier. If you collect <code>jane.smith@vendor.com<\/code>, you probably are.<\/p>\n<p>Many internal policies get clumsy. They label every email field \u201cPII\u201d without asking what the field identifies. That can create unnecessary friction in some low-risk workflows. But the opposite mistake is worse. Teams see a work email and assume business contact data is exempt from privacy controls, even when the address clearly points to one employee.<\/p>\n<p>A practical way to classify email addresses looks like this:<\/p>\n<ul>\n<li><strong>Generic mailbox:<\/strong> Lower identification risk on its own.<\/li>\n<li><strong>Named work email:<\/strong> Usually identifying.<\/li>\n<li><strong>Personal email:<\/strong> Clearly identifying.<\/li>\n<li><strong>Email plus case details or form metadata:<\/strong> Higher risk than the email alone.<\/li>\n<\/ul>\n<p><a id=\"how-context-changes-the-risk\"><\/a><\/p>\n<h3>How context changes the risk<\/h3>\n<p>An email address becomes more sensitive when it links other data points together. That&#039;s the part many SMBs miss.<\/p>\n<p>A single email in a mailbox may seem ordinary. The same email attached to a document request for immigration records, employee onboarding, or a financial review tells a much richer story. Add submission time, uploaded files, status notes, and staff comments, and you&#039;ve created a record that can reveal far more than contact details.<\/p>\n<blockquote>\n<p>A low-risk identifier can become a high-risk record key once your systems start attaching documents and internal notes to it.<\/p>\n<\/blockquote>\n<p>That&#039;s why secure transfer matters even before storage and retention enter the picture. If your team still asks clients to send files through ordinary email threads, it&#039;s worth reviewing <a href=\"https:\/\/www.superdocu.com\/en\/blog\/secure-file-transfer-methods\/\">secure file transfer methods for business documents<\/a>. The main operational benefit isn&#039;t only encryption. It&#039;s separating sensitive submissions from casual back-and-forth communication.<\/p>\n<p>Here&#039;s a common pattern that causes trouble:<\/p>\n<ol>\n<li>A client emails a shared inbox.<\/li>\n<li>Staff replies asking for documents.<\/li>\n<li>The client sends files back through email.<\/li>\n<li>Another employee forwards the thread internally.<\/li>\n<li>The email address now sits inside multiple inboxes, attachments, and side conversations.<\/li>\n<\/ol>\n<p>Nothing about that process feels dramatic. It&#039;s also exactly how personal data spreads beyond the people who need it.<\/p>\n<p><a id=\"practical-steps-for-handling-email-pii-securely\"><\/a><\/p>\n<h2>Practical Steps for Handling Email PII Securely<\/h2>\n<p><figure class=\"wp-block-image size-large\"><img decoding=\"async\" src=\"https:\/\/www.superdocu.com\/wp-content\/uploads\/2026\/06\/is-an-email-address-pii-data-lifecycle-1.jpg\" alt=\"An infographic illustrating the four-step data lifecycle process of collecting, storing, transferring, and deleting email addresses.\" \/><\/figure><\/p>\n<p>The easiest way to protect email PII is to stop thinking only about inbox security. You need a workflow that covers collection, storage, sharing, and deletion. Most small businesses don&#039;t need a massive privacy program to do this well. They need a smaller number of controls applied consistently.<\/p>\n<p><a id=\"start-with-collection-not-storage\"><\/a><\/p>\n<h3>Start with collection not storage<\/h3>\n<p>The first mistake usually happens before the data is stored anywhere. A business asks for an email address through a basic form, then requests the actual documents through follow-up email. That split process creates duplicate records and unnecessary exposure.<\/p>\n<p>Valimail notes that email communications often contain PII in HR, customer service, financial, and marketing contexts, and recommends protections such as <strong>DMARC, SPF, and DKIM<\/strong> to reduce phishing and impersonation risks in its <a href=\"https:\/\/www.valimail.com\/blog\/what-is-pii-data-safeguarding\/\" target=\"_blank\" rel=\"noopener\">guidance on safeguarding PII in email<\/a>. For document-collection platforms and client portals, that means email addresses should be minimized, protected in transit and at rest, and shared only on a need-to-know basis.<\/p>\n<p>That guidance leads to a practical rule for SMBs: collect the email once, in a controlled place, then use that same workflow to request whatever comes next.<\/p>\n<p>If you&#039;re replacing attachment-heavy email habits, one option is a secure document collection platform. <strong>Superdocu<\/strong> is one example. It lets teams send branded request links, collect documents through a portal instead of long email threads, and review submissions in a validation dashboard. That kind of setup reduces the number of places an email address and its attached records can spread.<\/p>\n<p><a id=\"set-controls-that-small-teams-will-actually-follow\"><\/a><\/p>\n<h3>Set controls that small teams will actually follow<\/h3>\n<p>Policy that nobody follows is decoration. Privacy controls work when they fit the pace of real business operations.<\/p>\n<p>Use a short operating standard:<\/p>\n<ul>\n<li><strong>Collect less:<\/strong> If you only need an email to send a portal link, don&#039;t also ask staff to copy it into side spreadsheets.<\/li>\n<li><strong>Limit visibility:<\/strong> Sales, HR, finance, and support don&#039;t all need the same view of the same address and attached history.<\/li>\n<li><strong>Prefer links over attachments:<\/strong> Keep documents inside controlled tools rather than inbox archives.<\/li>\n<li><strong>Protect transfer and storage:<\/strong> If you&#039;re reviewing vendor options, this overview of <a href=\"https:\/\/www.superdocu.com\/en\/blog\/what-is-file-encryption\/\">what file encryption means in business workflows<\/a> is a useful baseline for non-technical teams.<\/li>\n<li><strong>Define retention:<\/strong> Don&#039;t keep old intake exports forever just because nobody owns cleanup.<\/li>\n<\/ul>\n<blockquote>\n<p><strong>One useful test:<\/strong> If a team member leaves tomorrow, could you easily identify every place a client email and related documents were stored? If the answer is no, your workflow is too scattered.<\/p>\n<\/blockquote>\n<p>Small teams should also pay attention to email-channel protection itself, especially when staff still use email to send links, reminders, or status updates. For a practical security overview focused on smaller organizations, this guide to <a href=\"https:\/\/www.cloudorbis.com\/blog\/email-security-best-practices\" target=\"_blank\" rel=\"noopener\">email protection for Canadian SMBs<\/a> is a solid reference.<\/p>\n<p><a id=\"reduce-exposure-across-the-full-lifecycle\"><\/a><\/p>\n<h3>Reduce exposure across the full lifecycle<\/h3>\n<p>Think in terms of lifecycle rather than one-time compliance.<\/p>\n<p>At collection, keep the form narrow. Ask only for the email and the fields needed to start the process. When more data is required, request it through a portal or structured step, not a free-form reply chain.<\/p>\n<p>During processing, keep access role-based. The person confirming receipt may not need the same visibility as the person validating identity documents, since the email address often becomes the lookup key for everything else.<\/p>\n<p>For sharing, avoid forwarding internal threads that contain client identifiers and attachments. Route work through systems where access is controlled by role rather than by whoever happened to be copied on the original message.<\/p>\n<p>For deletion, set a rule that applies in ordinary language. Archived inboxes, downloaded CSVs, and desktop folders are where old email PII lingers. If you don&#039;t assign ownership for cleanup, the data stays forever.<\/p>\n<p>What works for SMBs is boring on purpose: fewer copies, fewer handoffs, fewer places to search, and fewer people with access. That&#039;s usually more effective than a complex policy document nobody remembers.<\/p>\n<p><a id=\"building-trust-through-smart-data-handling\"><\/a><\/p>\n<h2>Building Trust Through Smart Data Handling<\/h2>\n<p>The practical answer to \u201cis an email address PII\u201d is yes, and the more useful answer is what to do next. Treat the email field as a real identifier. Then build your document and intake workflows so that one identifier doesn&#039;t unintentionally spread through inboxes, exports, and shared folders.<\/p>\n<p>Most businesses don&#039;t need to become privacy specialists. They need discipline around a few basics: controlled collection, limited access, safer transfer, clear retention, and less dependence on ordinary email threads for sensitive tasks. When those controls are in place, compliance gets easier because the workflow itself is cleaner.<\/p>\n<p>Clients notice this. They may never ask how your systems are configured, but they notice whether your requests are organized, whether uploads happen in a secure portal, whether reminders are consistent, and whether their information seems to move through your business in a controlled way. That experience signals competence.<\/p>\n<p>Smart data handling also changes the internal cost of doing business. Staff spend less time hunting through inboxes, less time forwarding attachments, and less time fixing mistakes caused by fragmented intake processes. Privacy done well isn&#039;t just about reducing legal risk. It improves the way your business runs.<\/p>\n<hr>\n<p>If you want to move document collection out of messy email chains and into a more controlled workflow, <a href=\"https:\/\/www.superdocu.com\/en\">Superdocu<\/a> gives businesses a way to request, receive, review, and track documents through branded portals and automated workflows while keeping personal data handling more structured.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Yes, an email address is PII in almost all business contexts. If your business collects client, employee, or applicant emails, you should treat those addresses as personal data by default and handle them with the same care you&#039;d apply to other identifying information. That answer matters because most small businesses already know email feels sensitive, [&hellip;]<\/p>\n","protected":false},"author":1,"featured_media":6772,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_et_pb_use_builder":"","_et_pb_old_content":"","_et_gb_content_width":"","inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[371,370,303,369,372],"class_list":["post-6776","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","tag-ccpa-compliance","tag-data-privacy","tag-gdpr-compliance","tag-is-an-email-address-pii","tag-pii-handling"],"acf":[],"_links":{"self":[{"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/posts\/6776","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/comments?post=6776"}],"version-history":[{"count":1,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/posts\/6776\/revisions"}],"predecessor-version":[{"id":6780,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/posts\/6776\/revisions\/6780"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/media\/6772"}],"wp:attachment":[{"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/media?parent=6776"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/categories?post=6776"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.superdocu.com\/en\/wp-json\/wp\/v2\/tags?post=6776"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}