EveryShall
Log inRequest access
Security and data

Exactly what we do with your documents, and what we do not yet have.

Firms that sell to government are asked hard questions about their vendors. This page is written so you can answer them about us without guessing.

Where your data lives

All EveryShall infrastructure is hosted in the United States with a single infrastructure provider. Nothing is stored on laptops, personal drives, or third-party file services.

Encryption

Data is encrypted at rest with AES-256 using keys held in a managed key service, with a separate key per firm so that revoking one firm's key renders its data unreadable without touching any other firm. All connections use TLS 1.2 or higher. Backups are encrypted with the same per-firm keys.

Models and training

Language models are accessed under contractual terms that prohibit the provider from using customer inputs or outputs to train models. EveryShall does not train or fine-tune any model on customer data. Your documents are used to draft your bids and to score your opportunities, and for nothing else.

Isolation

Storage, retrieval indexes, and workflow executions are partitioned per firm. A workflow is bound to one firm's partition when it starts and carries no credential that can reach another. Isolation is enforced by access policy at the infrastructure level and checked by automated tests that attempt cross-firm reads and expect them to fail.

FIRM A · partition · key_astorageindexworkflow runsper-firm AES-256 keyFIRM B · partition · key_bstorageindexworkflow runsper-firm AES-256 keyFIRM C · partition · key_cstorageindexworkflow runsper-firm AES-256 keyA workflow is bound to one partition at start. Cross-partition reads are denied by policy and tested to fail.
Per-firm isolation. Storage, indexes, workflow executions, and encryption keys are separate for every firm.

Audit

Every automated decision, model call, and human edit is written to an append-only, hash-chained Ledger per bid, exportable as JSON and verifiable without us. All administrative and infrastructure activity is logged separately and retained for at least one year. See the Architecture page for the Ledger structure.

seq 146requirement.extractedprev 3a1f… → hash 5d2c…seq 147sentence.draftedprev 5d2c… → hash 9b0f…seq 148sentence.flaggedprev 9b0f… → hash c47e…seq 149export.renderedprev c47e… → hash 1e88…hash = SHA-256(canonical JSON of seq, at, actor, event, payload, prev_hash)Changing or removing any entry breaks every hash after it. Redaction replaces payload content and is itself an entry.
Ledger protocol. Each entry carries the hash of the previous one; the head hash is stamped into every export.

Access by our staff

Access to production systems is limited to the founder, requires hardware-key multi-factor authentication, and is logged. There are no shared accounts and no long-lived access keys; administrative sessions are time-limited. We do not open customer documents except to resolve an issue you have reported, and we tell you when we do.

Secrets and credentials

Source API keys and service credentials are held in a managed secrets store, never in code, configuration files, or email, and are rotated on a schedule. The system stores no procurement-portal credentials of yours, because it has no function that would use them.

Customer sign-in

Multi-factor authentication is required for every user, using an authenticator app or a hardware key. Sessions expire after inactivity. Firm administrators can remove a user immediately.

Availability and recovery

Data is backed up continuously with point-in-time recovery. Originals of every uploaded and retrieved document are immutable; derived data can be regenerated from them. We do not yet offer a contractual uptime commitment.

Deletion

Email privacy@everyshall.com and your documents, drafts, and derived indexes are deleted within 30 days. Ledger entries that reference deleted documents are retained in redacted form so that the audit record stays intact.

Submission

EveryShall holds no credentials for SAM.gov, any state or local portal, or any agency system, and has no submission capability. Submission is always performed by your staff.

What we do not have yet

We do not hold SOC 2, ISO 27001, FedRAMP, CMMC, or any other third-party certification. We do not offer a contractual uptime guarantee. We are a new company, and we would rather say so than imply otherwise. If your procurement process requires a certification we lack, tell us which one; it informs what we pursue next.

Reporting a security issue

Write to security@everyshall.com. We acknowledge reports within two business days and will tell you what we found and what we changed.