On this page
Contact Ansight
Ansight is provided by Ansight, Inc., a Delaware corporation. Contact support@ansight.ai for product assistance, billing questions, privacy requests, accessibility issues, and to arrange a private security report. Use the subject line to identify the request: Support, Billing, Privacy request, or Security report.
Our mailing address is Ansight, Inc., 131 Continental Dr, Suite 305, Newark, DE 19713, United States.
For technical guidance, start with the documentation, CLI guide, and security guidance. Support availability and any committed response times depend on your signed agreement. This page does not promise continuous monitoring, emergency assistance, or an uptime or response-time service level.
Help us reproduce the problem
Include your Ansight version and build number, operating system, app framework, affected command or feature, the time of the problem with time zone, and what you expected to happen. Explain whether you were working locally, using cloud sharing or AI analysis, or connecting to a remote machine. For billing issues, provide the account email and invoice reference, never a full payment-card number.
Start with a short, redacted error message. A small example using synthetic data is usually more useful than a complete customer capture. We may ask you to run ansight version --json or ansight doctor --json; review the output before sending it because it can include local paths and machine details.
Do not send passwords, API keys, pairing codes, signing certificates, provisioning secrets, private repository credentials, health or financial records, or an unreviewed session archive in your initial email. If an attachment or remote access is needed, agree a suitable transfer method and scope with us first.
Sharing diagnostic evidence
Session evidence can contain screenshots, text, logs, requests, app state, files, and personal information. Review it before sharing. Cloud session sharing uploads the raw capture by default unless you select sanitization. A sanitized export is a separate copy; it does not remove information from the original capture, and automated redaction can miss sensitive values.
Prefer a synthetic reproduction, a narrow evidence extract, and a team-restricted audience. An authenticated sharing link is not necessarily restricted to your team, and a public link can be viewed without sign-in. Do not create a public link for confidential support material. See data handling and sanitizers.
Sending a support request does not grant unrestricted access to your computer, app, organisation, or cloud environment. If remote assistance is agreed, confirm who will connect, which machine or session is in scope, what actions are allowed, whether evidence will be recorded, and when access will end. Revoke temporary access when work is complete. Ansight does not use support messages, attachments or diagnostic evidence to train or fine-tune models. See our Privacy Policy.
Security reports
Email us with Security report in the subject line and a non-sensitive summary. Include the affected component and version, suspected impact, and a safe contact method. Ask for a private channel before sending exploit details or sensitive evidence.
Do not access another customer’s data, disrupt services, establish persistence, or run destructive tests. If you encounter data that is not yours, stop testing and report the minimum details needed for us to locate the issue. This page does not authorise penetration testing or promise a bounty; arrange any active assessment with us in writing.
If you believe your own credentials are exposed, revoke or rotate them through the relevant service and tell us which Ansight feature may be affected. Do not send the exposed credential to prove the problem.
Privacy, account access, and deletion
Send Privacy request to support@ansight.ai and describe your request and relationship to the data. We may ask for information proportionate to verifying your identity and authority. Do not attach identity documents unless requested through an agreed channel. For an appeal of a privacy decision where applicable, use Privacy appeal.
For information inside an app operated by an Ansight customer, contact that app’s operator first: they normally decide why it is collected. We can help route a request where appropriate. For your own Ansight account, use available account controls or contact us. Organisation ownership, billing records, organisation content, local captures, exports, and cloud copies have different lifecycles; deleting an account does not erase every copy everywhere. See our Privacy Policy.
Remote companion connections
For help with a remote companion connection, include the Ansight version, operating systems of the machines involved, time of the problem with time zone, and the stage at which the connection fails. Describe whether the issue affects pairing, connection, screen display, controls or access to the app. Include a redacted error message if available.
Do not send pairing codes, access tokens, private keys or an unreviewed screen recording. If the issue may involve unauthorised access, end the connection, revoke temporary access where available, and contact us with Security report in the subject line. Remote assistance requires an agreed scope as described above.