Config Export & Audit privacy

This section describes how Config Export & Audit handles data. It supplements the site-wide privacy policy.

Where the application runs

The application runs in your browser inside Freshdesk, on the Freshworks Developer Platform. It has no server-side component. Atesen Software does not operate a server or a database for it.

What it reads

Configuration only: automation rules, SLA policies, ticket fields, groups, canned responses, business hours, scenario automations, ticket forms, and the names of agents, roles and products so that IDs can be shown as names. It does not read tickets or contacts. Every request is a read addressed to your own account through the platform's request templates.

Files and snapshots

Excel files, reports and snapshot files are assembled in the browser tab and handed to your browser as a download or to its print dialog. The application stores nothing: no configuration, no snapshots and no history beyond the installation parameters. A snapshot file you load for comparison is read in the browser and is not uploaded anywhere.

Credentials

Your API key is stored as a Freshworks secure installation parameter and inserted into request headers by the platform. It is not returned to the browser and not visible to Atesen Software.

Support correspondence

If you email support, that message and anything you attach reaches an Atesen Software mailbox. Please do not send API keys or exported files; a description of the problem is enough to investigate.