Multi-Field Bulk Update privacy

Where the application runs

The application runs inside Freshsales Suite on the Freshworks Developer Platform: its page runs in the browser of the person using it, and every call to Freshsales runs in the application's server methods on Freshworks-hosted serverless infrastructure. Atesen Software does not operate a server or a database for it and never receives your data.

What it reads

Through the Freshsales API of your own account, with the API key of the person using it: the list of views (names and IDs), the field definitions of contacts, accounts and deals, the selector lists (users, territories, pipelines and deal stages, contact statuses, lifecycle stages), the records of the chosen view, of which only the ID, name, pipeline and deal stage and the fields used in the conditions and operations are passed to the page, and each record again just before and just after it is changed. From Freshworks it reads the login email and user ID of the person using it, to check the list of people allowed to use it.

What it stores

As installation parameters: your Freshsales account name and the email addresses of the people allowed to run bulk updates.

In the Freshworks app data store of your installation: settings (plan, API share, CSV separator, records per run, batch size); the kill switch (on or off, when, and the Freshsales user ID of the person who changed it); a run lock that expires after 30 minutes without activity; saved operations (name, record type, view, conditions, fields, operations and the values you entered; up to 25); a history list of the last 30 runs (record type, field names, operations, counts, status and result codes, no values); and for each run, kept 90 days: its settings (the Freshsales user ID of the person who started it, the fields, operations and values entered), the record IDs with a short checksum of the values seen in the preview, and the undo log written before every change (record ID, the previous and new values of the changed fields, the result code and any error message from Freshsales).

Record names and the values of fields that are not changed are not written to the data store.

What it writes

Only after the typed confirmation: the fields you chose on the records in the preview, through the Freshsales API with the API key of the person running the application. Undo writes the previous values back. The application sends no email.

Credentials

No API key is stored. The key entered on the installation page is used once to check the account name. The key of the person using the application is kept only in the memory of the open browser tab for at most 15 idle minutes and is sent only to the application's server methods, which pass it to Freshsales. It is never stored or logged.

Deletion

Each run's settings, record list and undo log expire after 90 days. Settings, saved operations and the history list stay until you change or delete them. When the application is uninstalled, the Freshworks platform deletes the application's data store. CSV files you download are under your control.

Support correspondence

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