Paldorin Digital Policy Center
Contact the Paldorin Digital policy team
Use this page to reach the team that maintains Paldorin Digital's policies, style standards, and compliance documentation. Questions, corrections, and feedback all arrive here.
To get a useful answer quickly, name the document and section your message is about. A note saying "the retention rule in the Privacy Policy" is actionable. "Your policies are confusing" isn't, though we'll still read it.
Where to reach us
-
1201 Wilson Boulevard, Suite 700
Arlington, VA 22209, United States - +1 202-432-8110
- [email protected]
- Monday to Friday, 9:00 AM – 6:00 PM Eastern Time
Messages sent through the form below and messages sent by email reach the same team. Pick whichever is easier for you to describe the problem in.
What to write to us about
Most messages fall into one of a few shapes. Knowing which one yours is helps it land with the right person instead of being forwarded twice.
If you are unsure, describe what you were trying to do and which page you were reading. That is enough to start.
Questions about what a policy means
Ask whether a published rule applies to your situation, and where the boundary sits. Include the section heading so we can point at the exact wording you are reading.
Corrections to published pages
Tell us when a page is wrong, stale, or contradicts another page. If two documents disagree, send both links — that is a governance problem worth fixing at the source.
Feedback on a hard-to-follow section
Say which paragraph lost you, and why. A section that reads clearly to its author and badly to everyone else usually needs a rewrite, not a longer explanation in an email.
Requests for an alternate format
If you need an accessible version of a document you cannot currently get, ask here. These requests go to the document owner rather than sitting in a general inbox.
What happens after you submit
Your message routes to the document owner named on the page you reference. Nobody triages it by keyword; it goes to the person who maintains that page.
Typographical corrections
Usually handled within a few days. These are the cheapest fixes and the easiest to close, so they move first.
Questions about interpretation
You get a written answer. If the same question keeps arriving, that is a signal the underlying page needs an edit rather than another reply, and we treat it that way.
Reports that change a rule
If your report would actually change what a policy says, it goes through the governance process before anything published changes. We will tell you where it stands.
How to report an accessibility barrier
Accessibility reports jump the queue. Tell us the page, the section, and what happened, plus the browser and any assistive technology you were using.
"The focus outline disappears in the review table" is the kind of detail that leads straight to a fix. You don't need to diagnose the cause; describing what you experienced is enough for us to reproduce it.
Report an accessibility barrierInclude what you can
- The page and section where it happened
- What you expected to happen and what did instead
- Your browser and any screen reader, magnifier, or switch device you were using
- Whether it blocks the task entirely or just slows you down
Partial reports are still useful. A page name and a rough description beats waiting until you can write it up properly.
Asking about a specific policy
If your question is about a specific document, include the section heading in your message. Headings are stable across revisions, so they work as precise references even after the wording underneath them changes.
If you aren't sure which document applies, describe the situation instead: what you're trying to do, and which rules you think might cover it. We'll point you at the right page rather than guess on your behalf.
Include the section heading
Even an approximate heading narrows a long document down fast, and it survives the next revision.
Or describe the situation
No heading? Write what you are trying to do and what you think might apply. We will route it from there.
Response times and limits
What we can do
- Explain what our published policies say and where the wording sits
- Help you apply a rule to the situations that policy covers
- Answer accessibility reports and route alternate-format requests to the document owner
- Acknowledge every message and answer substantive questions in writing
What we cannot do
- Give legal advice or opinions on how a rule would apply in a dispute
- Interpret another organization's rules or decisions
- Discuss confidential matters belonging to clients or personnel
- Commit to a rule change before it has gone through governance
Requests that fall outside these limits get a referral instead of an answer, so you are not left wondering whether anyone read your message.
Send us your message
Everything you write here reaches the team that maintains these documents. Fields marked required are the ones we need to route a reply.
Feedback on this page
This page follows the same standards as the rest of the library, and the same reporting path applies to it.
If the form or the instructions here are unclear, say so through the form itself. A contact page that's annoying to use is a governance problem, not just an inconvenience, and it's one we'd rather fix than defend.
Suggest a correctionWhere our office is
1201 Wilson Boulevard, Suite 700, Arlington, VA 22209, United States. Visits are by appointment, arranged by phone or email.
Common questions about contacting us
Do I need to be a Paldorin Digital employee to contact you?
No. Readers, vendors, and anyone with a question about the published documentation can use this page. If a rule affects you and it is published here, you are entitled to ask about it.
Will I get a reply?
We aim to acknowledge every message and answer substantive questions in writing. Referrals for out-of-scope requests are also answered, so you always hear back about where your message went.
Can I ask about a policy that isn't published yet?
Yes, and the answer may simply be that the rule is still going through governance. We won't describe a draft as final, but we will tell you where it stands and which published page is closest in the meantime.
Where should documentation feedback go instead?
Here is the right place for corrections, clarity problems, and alternate-format requests. If you are looking for the rule itself rather than a conversation about it, start from the Policy Handbook, the Documentation Style Guide, or the Accessibility Standards, and send anything you find back through this page.
Still not sure where to start?
Send a short note describing what you were reading and what you need. If another page answers it better, we will point you there.