Privacy policy
Effective date: 8 October 2026
Last updated: 11 October 2026
This policy explains what OrgPulse collects, why, where it goes, how long it is kept and what you can do about it. OrgPulse is run by CloudCounsel Limited, a New Zealand company (NZBN 9429 0519 7088 8). CloudCounsel Limited is responsible for your personal information under the New Zealand Privacy Act 2020. Questions go to hello@cloudcounsel.co.nz.
What OrgPulse does to your org
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:
- Create a permission set named OrgPulse App Access. It grants no permissions; it only lets a user use the OrgPulse app.
- Assign it and OrgPulse Monitor to the integration user. Quick start does this instead: Assign it to you, the admin signing in.
- Set the OrgPulse app to admin pre-authorised, for OrgPulse App Access. Profiles and permission sets already listed stay.
It reads your org as the integration user you choose, or as you if you pick quick start. With quick start, OrgPulse reads as the admin who signed in, with that admin's own Salesforce permissions, and stores that admin's username in place of an integration user's. Otherwise it reads as the integration user, which holds a read-only permission set. The tools ChatGPT and Claude use only read your org; one of them can change your alert settings in OrgPulse, never anything in Salesforce, and none of them can run setup.
What we store
For each account (a workspace), OrgPulse stores:
- Your account id from our sign-in provider, and your workspace name if one is set.
- Your verified primary email address, which OrgPulse keeps so email alerts can go to it. Email alerts go only to your account's verified email address, never to anyone else.
- For each connected Salesforce org: the org id, a name you give it, the instance and login URLs, the API version, the Salesforce user id of the admin who connected it, the integration username (your own username if you chose quick start), whether quick start is in use, the connection status, the result of the connection check, and when it was last checked.
- The latest check: items that expire (for example certificates, passwords, permission set assignments, scheduled jobs and licences, named as they are in your org, which can include Salesforce users' names and usernames), org limits, licence counts and anything the check could not read. For each kind of check, OrgPulse also keeps what the last check that worked saw, so changes made while a check was failing are still recorded.
- Check history: one summary per org per day (counts of expiring items, limit percentages and which checks worked) and a record of every change between checks, such as an item appearing, its date changing, or it expiring or being resolved. A change record names the item as the check did.
- Watch settings (what to alert on and where), the state of each watch, and alert history: what was alerted, when, and whether it was delivered.
- Slack webhook URLs you add, stored encrypted.
- Usage records: for each day, how many checks, Run now checks, ChatGPT and Claude tool calls and alert emails your workspace used and roughly how much check data was stored, plus short-lived counters that enforce the plan limits. They hold numbers and your workspace id, never org names, usernames or email addresses.
- Billing references: your plan, billing interval, trial end date, the Stripe customer and subscription ids, and the ids of Stripe events we have processed. Card details go to Stripe and never reach OrgPulse.
What we never store
- Salesforce passwords. OrgPulse never asks for one.
- The admin's Salesforce sign-in. When you connect an org or run setup, the admin's access token is used within that one request and then discarded. It is never stored, logged or returned. A refresh token, if Salesforce sends one, is dropped.
- Card numbers or other payment details.
The integration user (or, with quick start, the admin) signs in with a signed assertion from OrgPulse, not a password. Salesforce access tokens for it are cached encrypted for up to 15 minutes so each check does not sign in again. After that the cached copy is never used, and the next check replaces it.
Why we use it
- To provide OrgPulse: connect your orgs, run the checks you ask for or your plan schedules, show results and history, and answer access questions.
- To send the alerts you set up, by email or Slack.
- To sign you in, and to let ChatGPT or Claude call OrgPulse for you if you connect it.
- To bill a paid plan and apply its features.
- To enforce plan limits and estimate what each workspace costs us to run. A daily cost report to us carries workspace ids and numbers only.
- To keep OrgPulse secure and to find and fix faults.
We do not use your information for advertising, sell it, or use it to train AI models.
How long we keep it
- Check history: on the free plan only the latest check and today's summary and changes are kept; on a paid plan, the latest check plus a daily summary and every change from the last 180 days. Older history is removed when a check runs and by a daily sweep, and if a paid plan ends, history beyond what the free plan keeps is removed at the next sweep.
- The latest check, connection details, watch settings and alert history for an org: until you forget the org or your account is deleted. Signing out of an org keeps them, and its history is still trimmed to your plan.
- Usage records: daily usage totals for 400 days; the counters that enforce plan limits for 2 days.
- Cached Salesforce access tokens: up to 15 minutes. Signing out of or forgetting an org deletes its cached token at once.
- The cookie set while you connect an org: 10 minutes.
- Account data (your account id, email address, workspace name and billing references): while your account exists.
Your controls
- Sign out of this org, on the org's Connection page, stops checks and drops OrgPulse's access to that org. History is kept so signing in again resumes it.
- Forget this org, on the same page, deletes the org's connection, latest check, history, watch settings and alert history immediately. It cannot be undone. Your account and its usage records stay.
- On the alerts page you can turn a watch off, stop email alerts, or remove a Slack webhook.
- To stop ChatGPT's or Claude's access, disconnect OrgPulse in that assistant's settings. Email us if you also want the access it was granted revoked on our side.
- To delete your account and everything stored for it, email hello@cloudcounsel.co.nz. We will delete it within 30 days.
Signing out and forgetting change nothing in Salesforce. To end access there too, remove the OrgPulse App Access permission set assignment from your users, or uninstall the OrgPulse package.
ChatGPT and Claude
If you connect OrgPulse to ChatGPT (run by OpenAI) or Claude (run by Anthropic), you sign in to OrgPulse and the assistant receives an access token for OrgPulse only. It never receives Salesforce credentials or tokens. When you ask a question, the assistant receives the tool's answer, which can include org names, Salesforce usernames and users' names, record names and ids, permission and sharing details, expiry dates, limits, licence counts, watch settings and alert history. Anything you type into the assistant, such as a Slack webhook URL for a watch, also passes through it. OpenAI and Anthropic handle that under their own terms and privacy policies. If you never connect an assistant, nothing goes to OpenAI or Anthropic.
Who else processes your data
OrgPulse uses these providers, only for the purpose listed:
- Vercel: hosts the website, runs the checks and counts page views on public pages.
- Neon: the Postgres database where the data above is stored.
- Clerk: accounts and sign-in, including the sign-in ChatGPT and Claude use. If you choose to sign in with Google, Clerk receives your name and email address from Google.
- Resend: sends email alerts, if you turn them on.
- Stripe: billing, if you subscribe. Stripe receives your email address and name to create the customer record.
- Slack: receives alerts, only if you add a Slack webhook.
- OpenAI: receives tool answers, only if you connect ChatGPT.
- Anthropic: receives tool answers, only if you connect Claude.
- Salesforce: your own org, which OrgPulse reads.
Pages load fonts from Fontshare and Google Fonts, so your browser asks those services for font files. Public pages (the home page, pricing and the other pages you can read without signing in) count page views with Vercel Web Analytics. It sets no cookies and records the page, the referring site, rough location, browser, operating system and device type, with a visitor identifier made from a hash of the request that is discarded after 24 hours, so a view is never tied to you or your IP address. Pages inside your account are not counted. OrgPulse uses no advertising trackers. Cookies are used for sign-in and, while you connect an org, for a short-lived encrypted cookie that expires after 10 minutes.
These providers store and process data outside New Zealand. We rely on each provider's data processing terms to protect it. We do not sell your information or share it with anyone else, unless the law requires it.
Security
- Slack webhook URLs and cached Salesforce access tokens are encrypted at rest with AES-256-GCM. Each value records which key sealed it, so keys can be rotated.
- Logs mask tokens, secrets, webhook URLs and keys before they are written, and the same masking runs over every tool answer ChatGPT or Claude receives.
- The checks only read. Only the setup step, which you start and consent to, writes to an org, and only the three changes above.
- All traffic to OrgPulse and to Salesforce uses HTTPS.
If a privacy breach is likely to cause serious harm, we will tell you and the Privacy Commissioner as the Privacy Act requires.
Your rights
Under the Privacy Act 2020 you can ask for a copy of the personal information we hold about you and ask us to correct it. Email hello@cloudcounsel.co.nz. If you are not happy with our response, you can complain to the Office of the Privacy Commissioner at privacy.org.nz.
If the EU or UK GDPR applies to you, we process your information to provide the service you signed up for (contract) and to keep it secure and within plan limits (legitimate interests). You can also ask us to delete your information, to restrict or object to its use, or to give it to you in a portable form, and you can complain to your local data protection authority.
Who this is for
OrgPulse is a tool for Salesforce administrators acting for a business. It is not meant for children.
Changes
If we change this policy, we will update it here and change the date at the top. If a change affects how we use information we already hold, we will email account owners before it takes effect.
Contact
CloudCounsel Limited, New Zealand. Email hello@cloudcounsel.co.nz.