Privacy

The full privacy text is being written and will be published here before launch. Until then, write to support@example.com with any question.

In short: OrgPulse's checks only read your org. The only time OrgPulse changes anything is setup, and only if you ask it to: it then makes three changes, all scoped to OrgPulse itself, using your admin sign-in for that one request. It does not keep that sign-in. The three changes are:

1. Create a permission set named OrgPulse App Access. It grants no permissions; it only lets a user use the OrgPulse app.
2. Assign it and OrgPulse Monitor to the integration user.
3. Set the OrgPulse app to admin pre-authorised, for OrgPulse App Access. Profiles and permission sets already listed stay.

It reads your org as an integration user you choose. It stores the org id, the integration username, your alert settings and the results of its checks.

On the free plan only the latest check is kept; on a paid plan, checks from the last 180 days, with the most recent check always kept.

Salesforce access tokens for the integration user are cached encrypted for up to 15 minutes so each check does not sign in again. Slack webhook URLs are stored encrypted.

Email alerts go only to your account's verified email address, which OrgPulse keeps for that purpose.