What data do you keep and for how long?

The data that we store depends on the publishing and storage options used in your project:

• Squirrel365 account data

• The .sqrl file

• The published output

Projects are created using the Squirrel365 desktop client or cloud based designer. Throughout the project design process data is obfuscated and stored within an encrypted file (.sqrl) either locally, on your machine, or remotely on the Squirrel365 cloud platform. When you are ready to publish your app, you can either publish to our cloud platform or export it as a Web App (local export) and host it on your own servers.

Any project files (.sqrl files), published apps, and associated data that are hosted on our cloud platform are transferred securely and are saved in a secure repository which is encrypted at rest.

Squirrel365 Account data

Your Squirrel365 account contains information relating to your identity and profile, such as name and email address. Along with usage data relating to your published projects and statistics on how your apps/projects are being viewed.

The .sqrl file

The Squirrel365 file (.SQRL) contains the definition and properties of your Squirrel project as well as an obfuscated view of the embedded spreadsheet. All data, configuration and information entered in the spreadsheet and/or property panel are persisted in the SQRL file.

The published output

The Squirrel365 output is a client side web application. Whether hosted on the Squirrel cloud platform, or on an external web server. No data captured at runtime via input form controls is passed to the web server for processing or storage, with the exception of the scenario control which gives the ability to store a snapshot of data on the Squirrel cloud platform at runtime. Should a customer report to us that they wish to purge this scenario data from our systems, then they can request we permanently delete all scenario data by making a request via the support site.

Zapier connector

At design time, a snapshot is taken of the key/value pairs that Zapier will present when configuring a zap. This takes a copy of the fields selected in the Zapier property panel in Squirrel and presents them as "Dummy Data" to the Zapier platform. Any data in these spreadsheet cells (when configuring the property binding) will be included in the snapshot. No GDPR personally identifiable information should be included in the spreadsheet at design time, but it is worth noting that these key/value pairs are stored in the Squirrel365 cloud platform to facilitate Zapier's zap creation process. Should a customer report to us that they wish to purge this data from our systems, then they can request we permanently delete all Zapier dummy data by making a request via the support site.

At run time when executing the Zapier trigger, data is passed direct from the browser on client machine to the Zapier hooks endpoint on the Zapier platform over SSL. No data is processed or stored by the Squirrel365 cloud platform.

PPTX/PDF generator

With the PPTX/PDF Generation service, at design time, the PPTX template file is stored on the Squirrel365 cloud platform. This file is stored encrypted at rest, and all communication to generate outputs is performed over SSL.

At run time, when generating an output, data is passed from the browser on the client machine to the PPTX service running on the Squirrel365 cloud platform. This data is passed as key/value pairs and transferred over SSL as a browser POST request. The PPTX service receives this request and generates the output using the data provided. At no point is the request data (key/value pairs) stored or persisted on the Squirrel365 cloud platform. The request is state-less and runs in one transaction. It is not possible to recreate or regenerate an output, without making a request from the browser, passing the same key/value pair request data.