The majority of the application is Salesforce-native, keeping all configuration and email generation within the platform, where you can monitor the app and back up your data.

We use a Heroku microservice to generate some of the files needed for the emails. This microservice is built to temporarily process your data, then delete any files shortly after they are sent back to Salesforce.

We use the reporting API, so the application needs OAuth access. This OAuth access can be revoked from any user at any time if you want them to stop sending reports and dashboards.

Private custom settings are used to store security secrets, which are visible only to the application code.

Configuration options are stored in records in your org for ease of backup, validation, and monitoring.

The reports run as the user who scheduled the report, so the user knows what data will be in the report.

The app is regularly scanned for security flaws and approved by the Salesforce security team. Read more about the security review.

When you install the app or do certain interactions on the AppExchange, Salesforce sends us your contact information and some basic info about what you did (for example: installed report sender).

When interacting with the app, we collect some usage data. For example, when pages are viewed, when custom object records are changed, and when users interact with application pages.

Paid subscribers will be asked to provide their name, address, and billing information, which will be stored securely and used for billing.

If you are having any issues with the app, and we determine we need login access to debug, one option we may ask is for you to grant us login access through the Salesforce setup menu. This allows our support agents to log in with the same permissions as the user who granted the access. Our support agents are trained on how to securely debug in a customer org and do not export any data or make changes unless approved by you and necessary for the fix.