Keep your work email.
Create a SendITAR account using the email you already use. There’s no separate mailbox to set up or monitor.
File exchange for defense teams
Built for exchanging ITAR and CUI files.
Keep your existing email and workflows. Choose your files, name your recipient, and share a link. Your browser encrypts the files before they leave your device.
Designed to simplify the file-exchange part of CMMC and NIST SP 800-171 workflows—with encrypted files, authenticated pickup, and a clear transfer history.
First file free. Then $7/month, billed annually at $84/year. View pricing.
A simpler handoff
SendITARRecipient view
Design review package
3 files 24.8 MB
design-review.stepassembly-notes.pdfspecifications.pdf
Named recipientengineer@example.com
Filenames unlocked locallyReady to decrypt
senditar.com/t/8a41…
The right file. The right person.A clear path from upload to pickup.
Illustrative example. No files are being transferred.
Built around the way
defense teams work.
The workflow
From your files
to the right hands.
A familiar link-sharing experience, with an intentional check at every handoff.
Choose. Encrypt. Share.
Choose your files and name your authorized recipient. SendITAR generates a six-word passphrase on your device; share it by phone or an approved encrypted messenger.
They verify. They download.
Your recipient signs in and verifies their email. They enter the passphrase you shared separately to decrypt and save files on their device.
Purposefully straightforward
Keep your inbox.
Simplify the handoff.
You need to send a file. Your recipient needs to receive it. The process should feel that simple.
Explore the transfer workspaceSimple file exchange, with fewer steps.
Choose files, save the generated passphrase, and name your recipient. One focused workflow takes you from encrypted upload to authenticated pickup.
Simpler CMMC and NIST SP 800-171 workflows.
Encryption, individual accounts, MFA, and transfer records support the file-exchange portion of your security program. Compliance depends on your complete environment and the applicable requirements and assessments.
Keep your existing email and workflows.
Use your work email and the inbox you already check. SendITAR emails a recognizable pickup link, so there’s no new mailbox or email platform to manage.
Follow the file
Your device. Encrypted handoff.
Their device.
See what happens at every step—and where your passphrase stays.
File contents and filenames: encrypted before uploadFile passphrase: shared outside SendITAR
- 1
Sender · your device
Sign in securely
Use your work email and multi-factor authentication. Confirm who is authorized to receive the files.
- 2
Sender · your device
Choose files + passphrase
SendITAR generates a six-word passphrase on your device; share it by phone or an approved encrypted messenger.
- 3
Inside your browser
Encrypt before upload
Your browser encrypts the file contents and filenames. Your passphrase is used locally and is not sent to SendITAR.
- 4
SendITAR · encrypted storage
Store encrypted files
Only encrypted file data is uploaded over HTTPS. Private cloud storage adds a separate layer of encryption.
- 5
Sender + recipient
Share the pickup link
SendITAR emails a personalized pickup notification with your name. Share the passphrase by phone or your organization's approved encrypted messenger — never by email, text message or in the link.
- 6
Recipient · their device
Authenticate for pickup
The named recipient signs in with MFA and proves access to their email. A forwarded link alone is not enough.
- 7
Inside their browser
Enter the file passphrase
The recipient enters the passphrase you shared separately. Their browser unlocks the filenames locally.
- 8
Recipient · their device
Decrypt and save
Encrypted bytes download and decrypt on their device. Integrity checks reject altered data before the completed file is saved.
- 9
SendITAR · automatic cleanup
Delete the server copy after pickup
Each file gets a fixed five-minute deletion timer after its first complete download. Access ends at the deadline, and automatic cleanup removes the stored object versions. Repeat downloads do not reset the timer. Other files keep their own pickup windows.
SendITAR sees account details, sender names, recipient addresses, file counts and sizes, and transfer activity. It cannot read file contents or filenames from the encrypted data it stores. Required preservation holds or storage failures can delay physical deletion; access still ends on time. After decryption, protecting the saved copy is the recipient’s responsibility.
Multiple layers of protection
We deliver your files.
We don’t read them.
End-to-end encryption protects the contents. Authentication, protected storage and access controls add further layers around the handoff.
Layer 1 · End-to-end encryption
File contents and filenames are encrypted in the sender’s browser and decrypted in the recipient’s browser. The file passphrase stays outside SendITAR.
Layer 2 · Protected transport + storage
HTTPS protects the connection. Private cloud storage and an additional storage-encryption layer protect the encrypted files held by the service.
Layer 3 · Named-recipient access
Individual accounts, MFA and mailbox verification control who can retrieve encrypted files. A link alone does not grant access.
Layer 4 · Automatic deletion
Each server copy is scheduled for deletion five minutes after its first complete download. Repeat pickups cannot extend the clock. Expiration and revocation can end access sooner.
Launch readiness comes first.
SendITAR is in prelaunch validation. Live cloud verification, cryptographic review and independent assessment are not complete. No certification or government approval is claimed. Do not upload ITAR technical data or CUI to this preview.
A few practical answers
Less guesswork.
A clearer process.
How are transferred files protected?
The implemented design protects files throughout the handoff. These controls are written in code and deployment configuration; live AWS verification is still pending.
| Stage | Protection |
|---|---|
| Upload and download | HTTPS encrypts traffic. Checksums detect corrupted upload parts. |
| Stored in AWS | The design uses private S3 storage, encrypted with keys managed through AWS KMS. Public access is blocked. |
| Before pickup | Your browser encrypts file contents and filenames before upload. SendITAR finalizes the encrypted object and makes it available to the authorized recipient. It does not inspect or malware-scan file contents. |
| Recipient access | The named recipient must sign in with MFA and prove access to the specified email address. A forwarded link alone grants no access. |
| During download | The server checks authorization and rechecks active transfers every 10 seconds. Revocation, expiration or account suspension causes access checks to fail and stops the stream. Production response times still need verification. |
| After pickup | Each file has a fixed deletion deadline five minutes after its first completed download. Access ends at that deadline; automatic cleanup removes all stored object versions. Expiration or revocation can end access sooner. Explicit holds or storage outages can delay physical deletion. |
End-to-end encrypted file contents: SendITAR generates a six-word passphrase on your device; share it by phone or an approved encrypted messenger. Your browser encrypts contents and filenames before upload; the recipient decrypts locally with that passphrase. SendITAR receives neither your passphrase nor the decryption key. Share the passphrase by phone or your organization's approved encrypted messenger — never by email, text message or in the link.
After download, protecting the recipient’s copy becomes their organization’s responsibility. Revoking a transfer cannot erase copies already downloaded.
Current status: Live integrations are enabled for non-controlled test files only. Production verification and the applicable assessments must be completed before controlled-data use.
How does SendITAR support CMMC and NIST SP 800-171?
SendITAR is being built to support the file-exchange portion of an organization’s security program. It has not yet demonstrated compliance or completed the applicable assessment. Using SendITAR does not by itself make a customer CMMC compliant.
DoD’s CMMC overview currently references the 110 NIST SP 800-171 Revision 2 requirements for Level 2. The examples below use those requirement numbers. NIST has published Revision 3; your contract and current program guidance determine the applicable baseline.
| Requirement area | Supporting design controls |
|---|---|
| Access control3.1.1, 3.1.2 | Named-recipient grants, account checks and database isolation help restrict who can access files and which actions they can perform. |
| Identification and authentication3.5.1–3.5.3 | Individual accounts and authenticator-based MFA support user identification and authentication. Mailbox verification provides an additional check on recipient access. |
| Transmission and storage confidentiality3.13.8, 3.13.16 | Client-side file encryption, HTTPS and KMS-backed encryption of stored ciphertext support confidentiality. The browser cryptographic implementation and production operating environment still require validation. |
| Audit and accountability3.3.1, 3.3.2 | Transfer event records tied to individual accounts support traceability. Complete logging coverage, retention, protection and review also need to be established and assessed. |
FIPS verification remains outstanding. Requirement 3.13.11 calls for FIPS-validated cryptography when protecting CUI confidentiality. An encryption setting or FIPS endpoint alone does not prove that every deployed cryptographic module and operating configuration meets that requirement.
These are supporting-control examples, not a complete requirements mapping or an assessment finding. Compliance also depends on the assessed system boundary, people, policies, operator access, endpoint protection, configuration management, incident response and supporting evidence. Senders must confirm recipient eligibility and sharing authorization; recipients must protect downloaded copies.
For covered defense information under DFARS 252.204-7012, the cloud service offering must meet the clause’s FedRAMP Moderate-equivalent security requirements and applicable incident obligations. SendITAR has not established that status. Hosting on AWS GovCloud alone does not establish it for the application.
Current status: Cloud verification, the applicable SaaS assurance work and assessment evidence remain pending. No CMMC certification, FedRAMP authorization, NIST approval or government endorsement is claimed.
Official references: CMMC overview, NIST SP 800-171 Rev. 2, Rev. 3 and DFARS 252.204-7012. Checked October 29, 2026.
Do I need a different email account?
No. Create a SendITAR account with your existing individual work email. You don’t need a new email address or another mailbox.
Can SendITAR see file contents or filenames?
SendITAR sees account details, sender names, recipient addresses, file counts and sizes, and transfer activity. It cannot read file contents or filenames from the encrypted data it stores.
Does this satisfy the ITAR end-to-end encryption provision?
SendITAR delivers the browser code that performs encryption. Do not rely on SendITAR to satisfy the ITAR end-to-end encryption provision in 22 CFR 120.54; consult your export-control advisor.
When are my files deleted?
Each file's encrypted server copy is scheduled for permanent deletion five minutes after its first complete download. Access ends at that deadline; a required preservation hold or storage outage can delay physical deletion. Copies the recipient saved are not affected.
Do both people need to sign in?
Yes. Senders and recipients use authenticated accounts with MFA. Recipients also prove access to the email address the sender specified.
Can someone else use a forwarded link?
The link alone does not grant access. Pickup is restricted to the named recipient’s authenticated account and mailbox verification.
Does SendITAR confirm recipient eligibility?
The sender confirms the recipient’s eligibility, export authorization, need to know, and applicable sharing restrictions before sending. The service enforces the named-recipient access rules.
Is SendITAR certified or ready for controlled files?
Not yet. Production security verification, legal review, and the applicable independent assessment remain outstanding. This deployment is for non-controlled test files and test users only.
Does SendITAR scan my files or guarantee they are malware-free?
No. SendITAR stores and delivers encrypted file data without inspecting its contents. Encryption does not make a file safe to open. Sender and recipient organizations need appropriate endpoint protection, and SendITAR’s own service security obligations remain part of its assessment.
What does end-to-end encryption protect against?
Stored file contents and filenames are encrypted without a passphrase held by SendITAR. Someone who obtains only the stored encrypted data cannot read it without deriving the key from your passphrase. The generated passphrase helps resist offline guessing. A compromised endpoint or malicious change to the browser application can still expose information while it is being entered or decrypted. Production cryptographic validation remains pending.
Is there a separate file passphrase?
Yes. SendITAR generates a six-word passphrase on your device; share it by phone or an approved encrypted messenger — never by email, text message or in the link. The recipient enters it locally after authenticating. SendITAR cannot recover a forgotten passphrase; the sender must create a new transfer if it is lost.
A simpler way to exchange files
Send the file.
Keep the process simple.
Get started with SendITAR
Your work email. One focused service.