Security & responsible use
Clear controls. Defined responsibilities.
Security review depends on the data, systems and providers in your deployment. Confirm the controls and agreements your use case needs before launch. A tool or certificate alone does not make a workflow compliant.
Access and connected actions
Give users and agents only the permissions their tasks require. Keep credentials in approved controls, review administrator access and remove unused connections. A prompt is not a substitute for access controls.
Verify consequential actions and keep a human fallback. Customers are responsible for their configurations; we remain responsible for our own obligations under the Terms and applicable law.
Data and processing
Identify what data a workflow receives, where it is sent and how long it is kept. Confirm the relevant processing agreement, transfer terms, provider scope and export or deletion process before using data that requires them.
Our Privacy Notice describes our data-handling commitments. Ask us for deployment-specific information about access controls, encryption coverage, storage, providers and retention; do not infer an assurance about every component from a general description.
Certificates have a defined scope
No. A certificate or audit report applies only to the organization, systems and scope it identifies. It does not automatically certify NECESSARY SYSTEMS LLC, a customer workflow, or every model, integration and channel. Ask for current evidence relevant to your proposed deployment.
We do not represent on this page that Supported.tech itself holds an ISO certification or a SOC 2 report. Compliance requirements must be evaluated against the actual service and contract.
Restricted and health information
Not through standard service. Do not send protected health information unless Supported.tech has expressly approved the deployment in writing and all required business associate agreements, eligible providers and safeguards are confirmed before use. Availability must be assessed, not assumed.
Do not put card security codes, passwords or unnecessary sensitive information into transcripts, prompts or knowledge files. The Acceptable Use Policy explains restricted data, communications and high-risk workflows.
Report a concern
Email describe@supported.tech about suspected unauthorized access, data exposure or a security issue. Include the affected workspace, approximate time, a concise description and safe reproduction steps. Do not send credentials or expose another person’s data.
Contact us before security testing. A report does not authorize probing, disruption or access to other customers’ information. We will handle reports and any required notifications under applicable law and our agreements.
Operator and contact
Supported.tech is operated by NECESSARY SYSTEMS LLC.
Mailing address
NECESSARY SYSTEMS LLC
30 N GOULD ST STE N
SHERIDAN, WY 82801 USA
Email: describe@supported.tech
Updated September 9, 2026.
Need a deployment-specific review?
Contact us →Security details
Plain answers.
Does a provider’s certification cover our deployment?+
No. A certificate or audit report applies only to the organization, systems and scope it identifies. It does not automatically certify NECESSARY SYSTEMS LLC, a customer workflow, or every model, integration and channel. Ask for current evidence relevant to your proposed deployment.
Can we send HIPAA-protected information?+
Not through standard service. Do not send protected health information unless Supported.tech has expressly approved the deployment in writing and all required business associate agreements, eligible providers and safeguards are confirmed before use. Availability must be assessed, not assumed.
What should we confirm before launch?+
Confirm the data and recipients, provider scope, access permissions, recording and retention choices, required consents, human escalation, and processing agreements. Test important actions and failure paths. Contact describe@supported.tech for a deployment-specific review.