Can the vendor reach into our AI box? Only through a path that exists and a permission that was given, so find every path.
Short answer. Only if there is a path and a permission, so list every path before you buy. The usual ones are remote-support tools, management agents, licence or telemetry calls, update channels, cloud connectors, engineer visits and returned hardware. For each, ask whether it exists, who starts it, what it can read, whether it is logged and whether you can turn it off. NIST’s control on remote maintenance sets a good standard: approve and monitor each session, use strong authentication, keep records, and end the session and connection when the work is done. Under the DPDP Act the office stays responsible for personal data even when a processor handles it.
01
Seven paths in
Path
What it could allow
Question to ask
Remote support session
A support engineer sees or controls the box
Who starts it? Can we watch and end it? Is it recorded?
Management agent
Standing access for monitoring and updates
Does one exist? What can it read or change? Can we disable it?
Licence check
The box asks a vendor server whether it may run
What happens if the server cannot be reached? Is there a grace period?
Telemetry or usage reporting
Data about use leaves the box
What is sent, to where, and can we turn it off? Does it include content?
Update channel
The vendor pushes, or the box pulls, new software
Who decides when updates install? Are packages signed?
Cloud connectors and models
Prompts or files go to outside services
Who adds them? Are answers labelled? Can we block them?
Visit or returned hardware
An engineer touches the drive, or a failed unit leaves your premises
Is the drive wiped or kept? Who signs for it?
02
What good looks like
Each remote session is approved and monitored by someone in your office. NIST SP 800-53 control MA-4 (nonlocal maintenance) asks for exactly this.
Strong authentication to start a session: no shared password, and no standing open door.
Records of every session, available to you.
The session and the network connection end when the work is done.
Least privilege for the support account: it sees what the job needs and nothing else.
Customer-initiated by default. Emergency access, if any, is defined in advance with notice to you.
03
Put it in the contract
A written list of every remote access path and every outbound destination, kept up to date.
No access without your approval for each session, apart from emergency terms you agree in advance.
Named engineers, and logs shared with you.
A statement of what may be copied off the box. The default should be nothing.
Processor terms. The DPDP Act allows a data fiduciary to engage a processor only under a valid contract (section 8(2)), and the Rules ask for appropriate provision in that contract for reasonable security safeguards (rule 6(1)(f)).
Notice of incidents, and deletion of any data the vendor holds when the contract ends. NIST’s generative AI profile suggests incident response plans for third-party AI technologies, with defined ownership and rehearsal.
04
Test it in the pilot
Watch outbound connections at the firewall for a week and compare them with the vendor’s list.
Ask the vendor to run a support session while you watch, and confirm it appears in the logs.
Block the vendor’s addresses for a week and see what changes.
Ask what the vendor can still support with no access at all.
05
The law, briefly
This is general information, not legal advice. The DPDP Act makes a data fiduciary responsible for complying with the Act in respect of processing done on its behalf by a processor, whatever the contract says (section 8(1)). The Rules, which start about eighteen months after 13 November 2025, list reasonable security safeguards that include access controls, logs and monitoring, and contract provisions for processors. As of October 2026 those rules are not yet in force.
06
What ANVE says
ANVE keeps the office’s data on the box in the office. The paths ANVEAI has named are optional and under an administrator’s control. Cloud models are added by an administrator, and their answers are labelled. Connectors are approved by an administrator, and every connector call is logged on the box. The tools an agent can use must be approved by an administrator, and every tool call is logged. The research maker looks up sources online only when asked, and podcast narration uses a cloud voice today.
On the update channel, ANVEAI installs updates on site today, signed update packages applied offline by USB are not on ANVE yet, and ANVE does not update itself over the internet. There is no remote kill switch, and every order includes a perpetual licence for the software delivered with the unit (see /security). Whether ANVEAI has any remote-support, management or telemetry path into a box is not stated here. ANVEAI confirms each in writing before a paid pilot; ask for the table above answered line by line.
07
Questions people ask
Is remote support a bad thing?
No. It can fix problems faster than a visit. What matters is that your office starts and ends each session, can watch it and has a record.
Can we run the box with no vendor access at all?
Usually yes for day-to-day use, but updates and repairs then rely on checked media and visits. Ask what the vendor can support without access.
Who is responsible if a vendor misuses access?
Under the DPDP Act the office, as data fiduciary, remains responsible for processing done on its behalf, which is why the contract must set safeguards. Take legal advice on the terms.
08
What is not real yet
No sealed ANVE unit exists; every image of the appliance on this site is a labelled render. The software runs today on a development machine. No customers yet, no certifications, no delivery date, and the final price is not announced.
Reservations are ₹999 in India or US$12 elsewhere, refundable in full until you confirm an order in writing (terms). Offices that cannot use cloud AI can apply to be one of ten design partners.
