docs(policypak): add USA datacenter and data residency info to Cloud …

[jeremymoskowitz-netwrix]

…data safety article

Adds that customer data is stored exclusively in USA (East and West coast) datacenters with redundancy, and that no alternative data residency regions are available.

Generated with AI

[github-actions]

Documentation PR Review

Editorial Review

docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md

• Clarity — Line 59: "at this time" is a time-relative phrase that violates Netwrix standards (alongside "currently", "presently", and "as of this writing"). It also dates the statement — if availability changes, the doc will be silently wrong. Suggested fix: remove the phrase entirely: "...locations such as Ireland or Germany are not available."
• Clarity — Line 59: "Data is redundant and split between East and West coast USA datacenters" repeats "USA datacenters" from the prior sentence and reads awkwardly. Suggested fix: "Data is replicated across East Coast and West Coast facilities to ensure availability during an outage."
• Completeness — Line 59: "locations such as Ireland or Germany are not available" lists two examples but leaves the reader unsure whether other non-USA regions are also excluded or whether these are the only two unavailable. Suggested fix: state the rule directly, then give examples: "No non-USA regions are available, including Ireland and Germany."
• Structure — Line 59: The new sentence introduces data residency, which is conceptually distinct from the surrounding content about encryption at rest. Consider adding a short subheading (e.g., #### Data residency) above the new paragraph so readers scanning for residency information can find it, rather than burying it inside the encryption-at-rest section.

Summary

4 editorial suggestions across 1 file. Vale and Dale issues are auto-fixed separately.

---

What to do next:

Comment @claude on this PR followed by your instructions to get help:

• @claude fix all issues — fix all editorial issues
• @claude help improve the flow of this document — get writing assistance
• @claude explain the voice issues — understand why something was flagged

You can ask Claude anything about the review or about Netwrix writing standards.

Automated fixes are only available for branches in this repository, not forks.

[github-actions]

Auto-Fix Summary

27 issues fixed, 11 skipped across 1 files

Category	Fixes
Contractions	1
Substitutions	2
BoilerplateCrossRef (rewrite)	1
FirstPersonPlural (rewrite)	2
FormalHedging (rewrite)	1
QuestionHeadings (rewrite)	1
Dale: passive-voice	15
Dale: positional-references	2
Dale: undefined-acronyms	1
Dale: wordiness	1

Skipped (needs manual review)	Reason

| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:2 — Dale: passive-voice | Frontmatter title preserved as-is; the title is a question and rewording risks altering the document's stored title. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:7 — Dale: passive-voice | Top-level heading uses an established noun-phrase pattern ('Data stored ... and how it's safely communicated and stored'); rewording the H1 risks breaking external links and changing the article's identity. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:9 — Dale: passive-voice | Section heading 'What is stored:' is part of an FAQ-style heading set; rewording risks changing meaning. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:30 — Dale: passive-voice | 'a unique hardware ID assigned to every physical and virtual machine by the manufacturer' — the manufacturer is the agent, but the sentence's focus is the BIOS UUID; rewriting would shift the subject and change emphasis. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:37 — Dale: passive-voice | 'The FQDN computer name it has been assigned' — the agent that assigns the name is ambiguous (admin? domain controller?); a rewrite would invent context. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:40 — Dale: passive-voice | Heading 'Other items which are stored in PolicyPak Cloud are:' — heading rewrite could affect anchors and FAQ-style consistency. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:55 — Dale: passive-voice | FAQ-style heading 'How is data is stored at rest with PolicyPak Cloud:' contains a typo ('is data is') but rewriting risks anchor/meaning changes; left for editorial review. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:60 — Dale: wordiness | 'at this time' in 'aren't available at this time' is a Vale-style concern, not specifically covered by a Dale rule; left as is. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:65 — Dale: undefined-acronyms | TDE is used after 'Transparent Data Encryption' appears in body prose on line 62 (the previous sentence establishes the term), so it is defined on first use. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:73 — Dale: passive-voice | FAQ-style heading 'How is data communicated to and from PolicyPak Cloud:' — heading rewrite could affect anchors and FAQ consistency. |
| docs/policypak/deliverymethods/cloud/knowledgebase/cloudportalsecurity/datasafety.md:78 — Dale: misplaced-modifiers | 'tries HTTPS ... using port 443 first using an encrypted ... certificate' has stacked '-ing' phrases that read awkwardly, but the intended order/meaning is ambiguous (does 'first' modify the attempt order or the certificate use?); rewriting risks changing technical meaning. |

Ask @claude on this PR if you'd like an explanation of any fix.