Security · Line Three

Four rules the design follows.

Keep no content.
Line Three discards prompts and answers once the response is delivered. Data that is never stored cannot leak later.
Encrypt every hop.
Requests travel over TLS 1.2 or later from your client to Line Three, and over TLS from Line Three to Amazon Bedrock.
Scope every key.
Each key belongs to one account and carries its own cap, so a leaked key has a known, small limit and can be turned off at once.
Say what isn’t done.
Every certification not held is listed as “Not held”. Anything planned is called planned.

The path of a request.

Every party a request touches, in order.

Your client
Your editor, agent, script or app, with your key.
Line Three gateway
Will check the key, its cap and its rate limit, forward the request, and count tokens for the month. Designed to store no content. Will run in Asen Technology’s own AWS account, with no third-party CDN in front of it.
Model provider
Amazon Bedrock runs the model that answers, in the AWS US West (Oregon) Region (us-west-2), through the Amazon Bedrock Runtime API (bedrock-runtime), using in-region inference.
Back to you
The answer streams back the same way. Line Three keeps no copy of it.

Line Three’s gateway and its usage records run in Asen Technology’s own AWS account, in the AWS US West (Oregon) Region (us-west-2), the same region where Amazon Bedrock answers your requests. The gateway calls the Amazon Bedrock Runtime API (bedrock-runtime) there, using in-region inference, not cross-region inference profiles, so requests are processed in that one region. Besides AWS, no other company is in Line Three’s request path, apart from DNS and certificate providers, which never see request content.

What is kept, and what isn’t

Kept

Account: Your organization’s name and the contact details of its administrators.
Billing: Prepaid credit, balances and refunds, monthly caps, monthly charges, payments, purchase orders and invoices.
Keys: Each key’s name and a one-way hash of the key. The key itself is shown once and never stored.
Usage: For each request: the time, the key, the model, tokens in and out, and the response status.
Connection logs: The source IP address and time of each connection, to the API and to this website.
Contact-form messages: What you typed into the contact form, the time it arrived and its reference number.

How long each is kept, record by record.

Not kept

By Line Three:

Your prompts.
The answers.
Files or documents you paste into a request.
Anything to train a model on.

Amazon Bedrock’s retention follows AWS’s terms, quoted in the data policy.

Read the data policy

Certifications held today: none.

Line Three is a new service. Each row changes only when the certificate, authorization or agreement exists. Line Three does not inherit any provider authorization.

Approved for DoD use: No. Line Three holds no authorization.; No
FedRAMP: No FedRAMP (federal cloud) authorization is held.; Not held
DoD Impact Level: No DoD Impact Level (IL) authorization is held. Line Three is for unclassified, non-CUI work and makes no IL claim.; Not held
ATO: No authority to operate (ATO) has been issued for Line Three.; Not held
CMMC: No Cybersecurity Maturity Model Certification (CMMC) is held.; Not held
SOC 2: No SOC 2 audit report exists.; Not held
GovRAMP (formerly StateRAMP): No GovRAMP authorization is held. StateRAMP now operates as GovRAMP.; Not held
TX-RAMP: No Texas Risk and Authorization Management Program (TX-RAMP) certification is held.; Not held
HIPAA · BAA: No business associate agreement (BAA) at launch. Do not send protected health information (PHI); send de-identified text only.; Not offered

The model marks, and where they apply

In US West (Oregon) (us-west-2), the commercial U.S. region Line Three uses, AWS lists all three launch models as FedRAMP Class C (formerly Moderate). FedRAMP Class D (formerly High) and the DoD Cloud Computing Security Requirements Guide (CC SRG; AWS’s table calls it “DoD CSP SRG”) Impact Levels 4 and 5 (IL4/IL5) apply only in AWS GovCloud (US), which Line Three does not use at launch.

The marks are the authorizations AWS lists for each model inside AWS, on its own compliance page. They describe the model at AWS, not Line Three. Line Three does not inherit any provider authorization.

AWS table checked on October 1, 2026.

AWS’s table of Amazon Bedrock model marks (another website) · AWS: these models’ IL4/IL5 approval, in AWS GovCloud (US) (another website)

For your cyber office or assessor.

Line Three is a commercial internet service; whether a government network can reach it is decided by that network’s owners. Printing this page prints only this sheet.

Line Three assessor sheet, ASEN ENTERPRISES LLC d/b/a Asen Technology. Pre-launch: Target: early access opens in the first quarter of calendar 2027. Version 1.0 (pre-launch), October 1, 2026. linethree.ai/security/

The bottom line for your Authorizing Official

Line Three holds no authorization. Using it on government systems needs your Authorizing Official’s risk decision. We’ll supply what they ask for.

Scope: Encrypted in transit. For unclassified work. Not an accredited secure communications line.
Hostname: api.linethree.ai, for the API. No fixed IP ranges are published, so allow it by hostname.
Ports and protocol: HTTPS on port 443 only, TLS 1.2 or later.
Where it’s processed: In the United States: Amazon Bedrock in the AWS US West (Oregon) Region (us-west-2), in-region inference only.
Gateway and records: Line Three’s gateway and its usage records run in Asen Technology’s own AWS account, in the AWS US West (Oregon) Region (us-west-2), the same region where Amazon Bedrock answers your requests. The gateway calls the Amazon Bedrock Runtime API (bedrock-runtime) there, using in-region inference, not cross-region inference profiles, so requests are processed in that one region. Besides AWS, no other company is in Line Three’s request path, apart from DNS and certificate providers, which never see request content. No third-party CDN is in the request path.
Authorizations: None held: no ATO, DoD Impact Level or FedRAMP authorization. Line Three does not inherit any provider authorization. The government has no agreement with AWS through Line Three. The model marks, and where they apply.
TLS: Designed to be encrypted in transit from your client to Line Three, and from Line Three to Amazon Bedrock.
TLS inspection: Line Three uses publicly trusted certificates and doesn’t require certificate pinning, so a TLS-inspecting proxy your machines already trust can sit in the path. That proxy then sees the content, under your organization’s rules.
What is logged: Account, billing, key and usage records are logged, with connection logs kept 30 days; contact-form messages are kept 13 months. No prompt or answer content. Full list.
Key handling: A key is shown once, when it is created, and Line Three stores only a one-way hash of it. Keys belong to your organization’s account, not to a person. An administrator can turn any key off at any time, and it stops working at once.
Control: Asen Technology controls Line Three’s AWS account and its gateway; AWS runs the infrastructure underneath.
Admin access: Multi-factor authentication on every administrative account. Every access to account, billing and usage records goes to an append-only access log, available on request for your review.
Sign-in: No single sign-on at launch.
Subprocessors: Amazon Web Services, for hosting and for model inference through Amazon Bedrock. A card payment processor and an email provider, each named at launch; neither sees prompts or answers. This website and the contact form run on Asen Technology’s own servers in the United States, with no hosting company. Changes are announced 30 days ahead, with a right to object and to end the agreement. The subprocessor table.
Data you must not send: Do not send classified information, CUI, covered defense information under DFARS 252.204-7012, or export-controlled technical data (ITAR or EAR). If you’re unsure, don’t send it.
Abuse monitoring: By AWS, under its terms. AWS lists the models whose traffic it may keep for abuse detection; none of Line Three’s launch models is on that list. If AWS changes how it retains data for a model, we stop routing to that model at once and tell you within 2 business days. AWS’s terms, quoted.
Prompt injection: If a tool lets a model act (run commands, edit files, call other tools), treat what the model returns as untrusted input, whichever service answers it.

What Line Three can’t provide yet

An authorization of any kind: ATO, DoD Impact Level, FedRAMP, GovRAMP or TX-RAMP.
A SOC 2 audit report.
A penetration-test report.
A completed standard security questionnaire.
A detailed architecture document beyond this page.

Ask for anything else on your checklist: you will get the document, or a plain answer that it doesn’t exist.

Line Three is a product of ASEN ENTERPRISES LLC, doing business as Asen Technology, a 100% U.S.-owned Wyoming LLC. Only its founder, a U.S. citizen, holds administrative access.

Found a vulnerability? Tell us.

Security problems in Line Three or this website: a person reads every report. This page is listed in security.txt.

Report to: The contact form, topic “Security report”
Include: What you found, how to reproduce it, and what an attacker could do with it.
Please don’t: Access other people’s data, degrade the service for others, or use social engineering.
We will: Acknowledge your report within 2 business days, tell you what we will do about it, keep you updated until it is fixed, and credit you if you want credit.
Safe harbor: If you act in good faith, follow this page, and give us reasonable time to fix a problem before you disclose it, we will not take legal action against you for your research.

Questions for an assessment?

Tell us what your security review needs.

Contact us Procurement details