What FedXchange holds, and how it protects it
Not FedRAMP certified, and designed with that in mind
Please don't put these in FedXchange
- Controlled Unclassified Information (CUI) or classified information
- System details such as addresses, host names, configurations, or findings
- Personal information beyond the names and work emails of the people who use it
For this reason, the System Security and Privacy Plan generator, which needs system details, stays out of the app.
A short list, on purpose
About people
- Name and work email of each member
- Passkeys and two-factor settings they add
- Their role in the agency
About your agency
- The service you chose for each function
- Your titles for offices and roles
- Your decisions on governance changes
- The audit log of changes
From this website
- What you send through this website's forms, kept 12 months
- No analytics or advertising trackers on this site. Concord stores your cookie and privacy choice, and you can change it on any page
The full details are in the privacy notice.
Controls built into the design
No passwords
People sign in with a link sent by email, a passkey, or both. Once someone sets up an authenticator app, an email link alone isn't enough.
One agency can't see another's data
Every record carries its agency's ID, and the service adds that ID to every query. No request can name a different agency. Tests check that one agency can't read another's records.
Roles decide what people can do
Each member is an owner, editor, reviewer, or viewer. AI assistants and access tokens act as the person who connected them, with that person's role.
Changes are previewed and recorded
Every change, from the web app, an assistant, or the governance watch, is written to your agency's audit log with who made it, how, and when.
Encrypted in transit and at rest
All traffic uses TLS. The database runs on Cloudflare D1, which encrypts stored data with AES-256.
Tokens are never stored in the clear
Personal access tokens are shown once and kept only as hashes. Assistant connections use one-hour tokens and end when you remove them.
Your setup is yours
Reporting a vulnerability
If you find a security problem in FedXchange, please tell us through the security report form. This covers this website, fedxchange.com, and the FedXchange app and its services at app.fedxchange.com, api.fedxchange.com, and mcp.fedx.io.
We read every report and reply by email to the address you give us.
What to send
- What you found, and where: the page, feature, or address
- The steps to see it for yourself
- What someone could do with it
Please don't
- test against other people's accounts or data, or try to reach another agency's data;
- overload, scrape, or disrupt the service;
- put other people's personal information in your report.