Trust, data and accessibility.
Where our data comes from, how we handle it, and what we never do.
Updated
Where the data comes from
- Public job postings
- OPM federal workforce data
- Licensed people-data providers
Postings from 1,362 official sources. Profiles as our privacy policy explains.
How candidate data is handled
- One contact at a time
- Names and contacts for signed-in customers only
- One-click unsubscribe in every outreach email
- Removal on request, from every customer
To see or remove your profile: privacy@aylagov.com.
What we never do
- Sell data to advertisers or data brokers
- Verify a security clearance
Only a security officer verifies a clearance.
For a security review
- No connection to your systems
- Each client’s data in its own account
- Protected traits never inferred
- Eligibility asked of the candidate
- Security questionnaires on request
Send your questionnaire: ask for a security review.
Security basics
- Passwordless sign-in
- Signed session tokens (JWT)
- Encrypted in transit (HTTPS)
- Hosted on AWS, us-east-2
Sign in with an emailed code, Google or a passkey.
Built to WCAG 2.1 AA
Accessibility questionnaires on request. Something not working? Tell us at hello@aylagov.com.
How a government office buys
- Purchase card or purchase order
- A written quote and a W-9
- A 90-day prototype under an other transaction agreement
- Ayla as a subcontractor under your prime
Software: a subscription. Recruiting: a placement fee when you hire.
The quote and the W-9: ask for them here.
NAICS codes and contacts: our capability statement.
Conflicts of interest: our independence policy.
Questions we did not answer?
hello@aylagov.comprivacy@aylagov.comCiv Network, Inc., Dover, DE
Free market brief. Reply in two business days. Want the software instead? Request access