1Does any outside AI model provider receive my documents?
No. An open-weight model runs inside the sealed machine.
One may, only on terms that bar training. It is on our subprocessor list.
Trust center
What protects your documents, what we keep, who else handles data, and what has been audited.
About 3 minutes on a sample file. Your email and name open it. We never ask for your ACE login or bank details.
Modes
| What changes | SealedPrivate by default. Provable on request. | StandardMay use outside AI. Staff access logged. |
|---|---|---|
| Runs in | AMD SEV-SNP confidential virtual machines (NexQloud Sealed) | NexQloud cloud. Outside AI may be used. |
| Encrypted | In your browser before upload, at rest, and in memory while the run is live | In transit and at rest |
Where your data is processed, in both modes: our FAQ.
An outside AI provider may process your documents, only on terms that bar training. Nothing trains on them. Only named NexQloud staff can open them, to fix an exception or answer a support request, and every access is logged.
| Claim | Backed by | How you check | Limits |
|---|---|---|---|
| In Sealed mode, no outside AI provider receives your documents | Our architecture and the subprocessor list | Read the subprocessor list. In Sealed mode, the receipt lists everything that could leave | In Standard mode, an outside AI provider may process them, only on terms that bar training |
| Your documents are never used to train any model | Our terms; in Sealed, the measured code | The DPA clause; the receipt's Model line | In Standard mode, it rests on our terms and our controls, and on the AI provider's terms |
| In Sealed mode, no one sees your documents without your consent | The four conditions on the Sealed page | Verify any receipt | The ten limits on the Sealed page |
| Every Standard-mode staff access is logged | The access log | Ask for your account's access log | The log is ours; an audit tests it |
Retention
Sealed erases the working copy when the run ends. Standard keeps documents for the engagement, then deletes them on schedule.
| Data | Sealed | Standard |
|---|---|---|
| Your uploaded documents | Readable only inside the sealed machine during the run, then cryptographically erased | Kept for the engagement, then deleted on schedule |
| Extracted fields, matches and working files | Erased with the working copy | Kept for the engagement, then deleted with the documents |
| Exceptions and your answers | Seen only by you and your broker | Kept for the engagement |
| Claim package, CSV and evidence trail | Sent to your broker and you, encrypted to them. No readable copy kept by us | Sent to your broker and you |
| Claim totals and billing records | Kept with our billing records | Same |
| Receipts | Kept. Download yours any time | Not issued in Standard |
| Account details | Life of the account, then deleted on schedule | Same |
| Staff access logs | No staff access to log | Kept on schedule |
| System logs, with no document content | Kept on schedule | Same |
| Backups | No backups of document content | Documents stay in backups for a set time after deletion |
| Outside AI provider (Standard only) | Not used in Sealed | Per the provider's terms |
| Consents (broker sharing; adviser status view)[1] | Kept on schedule | Same |
The records CBP requires are yours and your broker's to keep: claim records for three years after the claim liquidates.[2] We are not your record keeper, so keep your own copies.
We can keep only what we hold. In Sealed mode, that does not include your documents.
Subprocessors
Sealed uses no AI model provider. Standard may use one, only on terms that bar training.
| Subprocessor | What it does for us | Data it receives | Mode |
|---|---|---|---|
| Sealed hosting provider | Hosts for sealed machines | Encrypted data. AMD hardware keeps the host from reading a sealed machine's memory (limits apply) | Sealed |
| Cloud hosting provider | Hosting for Standard | Documents and outputs, encrypted at rest | Standard |
| Email provider | Account and notice emails | Names, email addresses, notice text. No documents | Both |
| Error monitoring provider | Error reports | Error data with no document content | Both |
| Support tool | Support tickets | What you write to us | Both |
| Billing provider | Invoices | Claim totals and billing contacts | Both |
| AI model provider | AI model for Standard | Documents, only on terms that bar training | Standard |
Audits
| Item | Status |
|---|---|
| SOC 2 Type 2 | The report is available under NDA on request. |
| Vulnerability disclosure policy and security.txt | Published |
| AMD bulletins we track | Listed on the verify page |
We do not hold CMMC, FedRAMP, or ITAR or EAR authorizations for this service, and Sealed is not one.[3]
Certifications held by NexQloud's other services or by our hosting providers do not transfer to NexQloud Drawback. Our hosting providers' own reports are theirs, not ours.
Disclosure
Our vulnerability disclosure policy covers how to report, scope, safe harbor and timelines.
Our security.txt file lists the same contacts in the standard format (RFC 9116).[4]
Get started
Run the demo in Sealed mode. About three minutes.
Pick Sealed mode when you upload your records.
WhoYou
Your records are read inside AMD SEV-SNP hardware.
WhoThe agent
The working copy is erased. Anyone you share the receipt with can verify it.
WhoYou
Your email and name open the demo. We never ask for your ACE login or bank details.
Ready now? Start a claimIncidents
If we confirm an incident that affects your data, we notify you and your broker.
What happened and when; what data; which accounts; which importer numbers may be affected; what we have done; who to call.
Until the incident is closed.
A written report after it closes.
A breach of our servers can reach only what we hold: account details, claim totals, receipts, logs, and encrypted data we cannot open.
A flaw in a sealed release could affect its runs, so we log every release, revoke a bad one and tell you (how revocation works).
Vendor reviews
Tell us through our contact page. We reply within 2 business days.
Ten questions
Ten questions to ask any AI vendor, from Why Sealed.
No. An open-weight model runs inside the sealed machine.
One may, only on terms that bar training. It is on our subprocessor list.
Never. The model's weights hash is also published.
Never. The clause is in our data processing agreement (/legal/dpa/, section 2).
Only the people you approve, such as your broker. Exceptions go to you or your broker.
Named NexQloud staff, only for exception review and support. Every access is logged.
Yes. Check any run's receipt against AMD's keys at /sealed/verify/. Read the limits first.
Through our controls: your account's access log, our terms, and the dated audits.
We give notice before any change, and changes are never retroactive.
The same, and a change can't reach a working copy that no longer exists.
The same.
Only those on the subprocessor list. We give notice before we add one.
The same list. No outside AI provider, analytics tool or support desk receives your documents.
The same, plus the AI provider's own vendors.
Your workspace, your broker's queue and claim totals for billing. It has no tools that send data elsewhere.
The same, and the receipt names the exact code that ran.
The same.
A licensed customs broker, ours or yours, reviews every line and files.
The same.
No, never.
No, never.