Security & data privacy

Your data stays on your computer.

Aieia is designed from the ground up to keep research data where it belongs: on your local machine. The Aieia Web Portal is used only for task control. This page explains exactly what moves, where it goes, and what controls your team and institution have over it.

💻
Fully local data storage
All logs, extracted data, screenshots, and session records are stored locally. Nothing is stored on Survon servers.
🌐
Portal for control only
The portal sends task instructions and can stop tasks. It cannot read logs, access extracted data, or retrieve any information from the device.
🛡
Zero retention policy
We operate a zero data retention policy. Data is not stored or used for model training.
🔒
No background services
No background services, no exposed network ports. Only outbound HTTPS for task instructions and AI inference.
☁️
Private Cloud Routing available
For labs with strict data governance requirements, route AI inference through your own AWS or Google Cloud account, governed by your existing cloud agreement.

Data flow

What leaves your device,
and where it goes

Aieia can be deployed in two modes. Understanding each mode helps your IT team make the right deployment decision for your lab.

Standard deployment mode
Default deployment
  • 1
    Screenshot captured on the instrument computer. Only the current screen is captured. No other application data or files are accessed. On device
  • 2
    Screenshot, task instructions, step history, and custom instructions are sent to an enterprise-grade AI via encrypted HTTPS. We operate a zero data retention policy and do not use this data for model training. AI model
  • 3
    AI response (next action decision) is returned to the instrument computer. No data is retained after the request completes. On device
  • 4
    Audit log entry is sent to Survon's Swiss-hosted servers, encrypted in transit and at rest. Log entries contain action metadata only: step number, action type, timestamp, and status. No experimental data, extracted results, or screenshots are included. Swiss servers
  • 5
    Screenshots, extracted data, and session records are saved locally on the instrument computer. Your team retains full custody. On device
Private Cloud Routing
For labs with strict data governance
  • 1
    Screenshot captured on the instrument computer. Only the current screen is captured. On device
  • 2
    Screenshot, task instructions, step history, and custom instructions are sent to the AI model via your own AWS or Google Cloud account. The API call is routed through your cloud environment and governed by your existing cloud agreement and security controls. Your cloud account
  • 3
    AI response is returned through your cloud account. Your IT team has full visibility in your AWS or GCP console. On device
  • 4
    Audit logs are saved locally on the instrument computer only. Nothing is sent to Survon servers. Your institution retains full custody. On device
  • 5
    Screenshots, extracted data, and session records remain on the instrument computer throughout. On device

Deployment comparison

Standard vs Private Cloud Routing

A side-by-side view of where each type of data goes in each deployment mode.

Data type Standard deployment mode Private Cloud Routing
Screenshots Sent to AI model (zero retention). Saved locally on device. Sent via your AWS or GCP account to AI model. Saved locally on device.
Task instructions and custom instructions AI model Your cloud account
Step history (session context) AI model Your cloud account
Audit logs Swiss servers — action metadata only, encrypted Local device only
Experimental data and extracted results Local device only — never sent to Survon Local device only
Device and task management Aieia Web Portal — task dispatch and stop only. No data access. Aieia Web Portal — task dispatch and stop only. No data access.

Note: The AI model provider operates a zero data retention policy for API usage. Screenshots and prompts sent to the AI model are processed and then discarded. They are not stored or used for model training. This applies to both Standard deployment mode and Private Cloud Routing.


Per-step data

Exactly what is sent to the AI model

Each time Aieia takes an action, it sends one request to the AI model. Here is what that request contains, and what it never contains.

Sent with each request
The AI model receives exactly this, and nothing else.
💻
A screenshot of the current screen
Only what is visible on screen at the time of capture
📝
The task instruction you sent via the portal
Plain text, as you wrote it
📋
Step history from the current session
A log of actions taken so far in this task run
⚙️
Custom instructions, if configured
Rules you have defined for this workflow
Never sent to any external server
These never leave the instrument computer under any configuration.
🚫
Experimental data and extracted results
Saved locally on device only
🚫
No data stored between sessions
When a task ends, nothing is retained on Survon's side. No session history, no results, no screenshots
🚫
Data from files or applications not on screen
Aieia only sees what is visible at the time of capture
🚫
Data from other open applications
Aieia captures only the active screen region

Aieia Web Portal

The portal controls tasks. It cannot see your data.

The Aieia Web Portal is the remote interface for sending tasks to connected instrument computers and stopping running tasks. That is the full extent of what it does.

The portal has no access to audit and experiment logs, extracted data, screenshots, or session records on the instrument computer. All of that stays on the local machine and is managed by your team under your own data policies.

What the portal can do
Send a task instruction to a connected device
Stop a running task on a connected device
Show a list of connected devices and their status
See a list of run logs, their status, and grant/project codes (For admins)
See credits transactions (For admins)
What the portal cannot do
Access experiment logs or audit records on the device
View or download extracted data or results
Access screenshots taken during a session
Read files or data from the instrument computer
Aieia Web Portal screenshot

Infrastructure

Where each component lives

Every part of the Aieia stack is designed to minimize data movement and maximize your team's control over research data.

💻

Runs directly on the workstation

Aieia runs directly on the instrument computer with no installation required. It does not run background services, does not expose network ports, and only communicates outbound over standard HTTPS to the AI model for reasoning, and to Survon's Swiss-hosted servers for audit logs (Standard mode only).

No inbound network access
📁

Local data custody

Screenshots, extracted data, session records, and audit logs (in Private Cloud Routing mode) are all stored on the instrument computer. Your IT team can manage retention, access, and deletion using your existing endpoint management policies. Survon has no access to any of this data.

Your device, your control
🇨🇭

Swiss-hosted audit servers

In Standard mode, audit logs are stored on SOC 2 certified and HIPAA compliant infrastructure hosted in Switzerland. Logs contain action metadata only — step number, action type, timestamp, and status. No experimental data, results, or screenshots are ever included.

SOC 2 certified and HIPAA compliant
🗄️

No data stored between sessions

Aieia holds no persistent state on Survon's side. When a task ends, nothing is retained. No session history, no results, no screenshots.

Nothing retained after task completion
🤖

Zero retention AI model

Screenshots and task instructions are sent to an enterprise-grade AI to determine the next action. We operate a zero data retention policy. Data is processed and then discarded. It is not stored after the request completes and is not used for model training.

Zero retention policy
☁️

Private Cloud Routing

With Private Cloud Routing, AI inference is routed through your own AWS or Google Cloud account. The API call is subject to your cloud provider agreement and visible in your own cloud console.

Governed by your cloud agreement

Private Cloud Routing

Route AI inference through your own cloud account

For labs and institutions with strict data governance requirements, Private Cloud Routing routes all AI inference through your own AWS or Google Cloud account via Amazon Bedrock or Google Cloud Vertex AI.

This means the API call is governed by your existing cloud provider agreement, visible in your own cloud console, and subject to your institution's cloud security controls. Your infosec team has full visibility and audit capability within your own environment.

In Private Cloud Routing mode, audit logs are saved locally on the instrument computer only. Survon servers receive nothing during task execution.

Discuss Private Cloud Routing
What changes with Private Cloud Routing
AI inference route
Standard: Direct to our AI provider.
Private: Via your AWS or GCP account.
Audit logs
Standard: Swiss-hosted Survon servers.
Private: Local device only. Survon receives nothing.
Governance
Standard: Survon and AI provider agreements.
Private: Your existing cloud provider agreement applies.
What does not change
Experimental data always stays on device. The Aieia Web Portal never accesses local data.

Security FAQ

Questions from IT and research teams

Does any research data leave our workstation? +
No. Experimental data, extracted results, and session records never leave the workstation. The only data that leaves the device during a session is the screenshot sent to the AI model for reasoning and the audit log entry sent to Survon's Swiss-hosted servers in Standard mode (action metadata only — no experimental data). With Private Cloud Routing, even the audit log stays on device and Survon receives nothing during task execution.
What does the Aieia Web Portal have access to? +
The Aieia Web Portal can send task instructions to connected devices and stop running tasks. That is all it can do. It has no access to audit and experimental logs, extracted data, screenshots, or any files on the instrument computer. The portal shows a list of connected devices and their current task status, but cannot read any data from those devices. All experimental data and session records remain on the local instrument computer under your team's control. Admins can see a list of runs, their status, and project/grant codes, as well as credits transactions.
How does the AI model handle our data? +
Aieia sends screenshots and task instructions to the AI model to determine the next action to take. Our AI provider operates a zero data retention policy: screenshots and custom instructions are processed and then discarded immediately after the request completes. They are not stored, logged, or used for model training. This applies to both Standard deployment mode and Private Cloud Routing.
What is Private Cloud Routing and when do we need it? +
In Standard deployment mode, AI inference is routed directly to our AI model provider. With Private Cloud Routing, the same API call is routed through your own AWS or Google Cloud account using Amazon Bedrock or Google Cloud Vertex AI. This means the traffic is subject to your existing cloud provider agreement, visible in your cloud console, and governed by your institution's cloud security controls. Additionally, in Private Cloud Routing mode, audit logs are stored locally on the device. Survon servers receive nothing during task execution. Private Cloud Routing is recommended for institutions with strict data governance requirements or existing cloud agreements that they want to extend to cover AI inference.
Does Aieia work without an internet connection? +
Aieia requires an internet connection during active task execution for two purposes: sending screenshots to the AI model for reasoning (outbound HTTPS only), and writing audit log entries to Survon's Swiss-hosted servers in Standard deployment mode. The Aieia Web Portal also requires connectivity for task dispatch and device management. If the connection is lost mid-run, Aieia stops at the current step and logs the interruption. It does not require any inbound network access and does not expose any network ports.
How are screenshots handled after a session? +
Screenshots are saved locally on the instrument computer in a dated folder within the Aieia application directory. They are not transmitted to Survon servers at any time. Your IT team can manage retention, access, and deletion of these files using your existing endpoint management policies. The screenshots are useful for reviewing what Aieia saw during a session, debugging unexpected behaviour, and providing a local visual audit record of the run.
What if we need to restrict Aieia to specific software only? +
Custom Instructions allow you to set hard constraints on what Aieia is permitted to do. For example: "only interact with the chromatography software, do not interact with any other application", or "read only — do not modify any values or settings." These instructions are applied to every run of that workflow. Screen Region Lock (coming soon) will further restrict Aieia to interact only within a defined area of the screen, preventing it from reaching other open applications entirely.
Can multiple people in our lab send tasks to the same instrument? +
Yes. Multiple authorized people can access the Aieia Web Portal and send tasks to connected instruments. However, each instrument computer runs a single Aieia instance, which can only execute one task at a time. To send a new task to a device, the current task must first be completed or stopped.
How do we report a security concern? +
Email aieia@survon.co with a description of the concern, steps to reproduce if applicable, and any supporting information. We acknowledge all security reports within two business days and provide an initial assessment within seven business days. We ask that you give us a reasonable period to investigate before public disclosure. For general security questions about deployment, data handling, or architecture, the same email address is the right starting point.

Security questions or concerns

For security reviews, vulnerability reports, or any data handling questions, contact our security team directly.

We respond within three business days.

✉ aieia@survon.co