Windows UI automation · Desktop toolkit
Deskrun: Privacy
Updated
This page explains how Deskrun is designed to work. It is a draft: your order or access agreement confirms the final terms before you pay or start using Deskrun.
Scope
This privacy information is specific to Deskrun, which Timastra LLC provides and is responsible for. The website privacy policy separately covers visits to timastra.com and correspondence with Timastra LLC.
Information the product handles
- Flow files, variables and recorded steps, stored as JSON on your machines
- Screenshots, JSON run logs, JUnit XML reports and other run evidence, written to local folders
- Placeholders for recorded typing, whose values stay in Windows Credential Manager
- Licence files naming the licensed organization and its Studio seat and runner counts
Purpose
Drive Windows desktop applications through their user interface, verify the results, and report them to people and CI systems.
Providers, permissions and sharing
Deskrun runs entirely on your machines. It makes no network connections, sends no telemetry and uses no licence server: licences are signed files checked offline. Credentials are read from Windows Credential Manager on the machine running a flow. Emailing support or sharing screenshots and run logs is a separate action that can disclose data outside your machines.
Your workspace or deployment notices identify enabled providers, processing locations and optional permissions. Review those details before connecting a service.
Retention and deletion
Flows, run evidence and credentials remain on your machines until you or your organization remove them. Screenshots and logs can capture anything the automated application showed, including personal information, so check your organization's retention rules before keeping or sharing them.
Deskrun has no hosted account to close. Flows, screenshots, run logs and reports stay in the folders you choose, and Timastra cannot remotely erase them. Flow Studio can delete a run's evidence, and stored credentials can be removed with the deskrun cred command, Flow Studio's Credentials dialog or Windows Credential Manager. Uninstalling Deskrun does not necessarily remove flows, run evidence or credentials.
Your requests
For access, correction, deletion or questions about processing, email support@timastra.com. Identify the relevant organization if applicable. Available rights and exceptions depend on the circumstances and applicable law.