Herlad's use and transfer to any other app of information received from Google APIs will adhere to Google API Services User Data Policy, including the Limited Use requirements.
Our code can only access your data while you're accessing the app. We don't sync your data to our own servers and we don't have any direct access to your data.
We use GoogleTM's PropertyService which allows us to attach limited data (channel prefferences & license information) to the user, on GoogleTM servers. Channels and their settings are saved on our server as well. We then use Google Apps ScriptTM which runs exclusively on GoogleTM servers. The only data that syncs to our servers is the data entered and sent to Stripe (our payment processor) during the subscription process. When you install the app, we also collect your email address and name for licence and email marketing purposes.
We at Herlad do not have access to view any of the information stored in your Google ChatTM. An example of the data collected is that a user with name John Doe and with email john.doe@gmail.com installed the addon on 17.09.2026.
Herald does not share any of your personal data with our api service.
Every app that GoogleTM approves must go through a strict security & privacy approval process, including ours. Google CloudTM Platform/API Trust & Safety Team has approved the Aegis add-on for the following scopes, which you can see on the OAuth screen in the screenshot above:
Scope:
https://www.googleapis.com/auth/script.external_request
This permission
allows the
Herald to send and receive licence information and space alert settings.
Scope:
https://www.googleapis.com/auth/chat.messages.create
This
permission allows the
app to render jobs and settings cards and return success and error messages.
Scope: https://www.googleapis.com/auth/userinfo.email
This
permission
allows the add-on to view user's email address.
When you install and open the Google ChatTM for the first time, GoogleTM will ask you to allow access for the permissions listed above.
We do not have access to view any of the information in your Google ChatTM account. All of your chat information is stored by GoogleTM and we don't have access to it.
None of your Google ChatTM information is synced to our servers.
Your payments and credit card information is stored by Stripe.
We also store your email address and name when you install the app for licence and email marketing purposes. We do not share your name or email address with any third-parties. You can unsubscribe from our emails at any time.
Security
The protection of your data is important to us. We are striving to use, to the best of our knowledge, available means of protection. However, please be aware that no method of transmission over the internet, or method of electronic storage is 100% secure or reliable, and we cannot guarantee the absolute security of the Service.
Data Accessed
Email address (via Google ChatTM event payload): Used to identify the user within the application. This data is accessed when the user adds the app to a space, sends a message, or uses a slash command.
Data Usage, Storage & Sharing
-
Licensing - The user's email address is stored alongside their license type and license code for the sole purpose of verifying their license. Herald communicates with its own backend server to check whether a license is active and retrieve relevant license details. No payment information is stored by Herald — payment processing is handled entirely by Stripe, which operates under its own privacy policy. Herald receives no payment details from Stripe.
-
User Settings - The user's email address is used as an identifier to associate their personal preferences with their account. These preferences — including the channel ID where newsletter jobs are delivered, category, skills, search terms, and other search-related settings — are stored in JSON format on the Herald (Red Hood Syndicate) organization's Google DriveTM. This data is used exclusively to personalize and operate the Herald service for that user. Settings are automatically removed when the user removes Herald from a space.
External Requests - Herald makes external requests exclusively to its own backend server for license validation and retrieval of license details. No GoogleTM user data is shared with any third-party service.
Message Creation - Herald uses the chat.messages.create scope to post job listings and notifications directly into Google ChatTM spaces, based on the user's saved preferences. No personal user data is included in these messages.
Data Retention & Deletion - User settings are automatically deleted when Herald is removed from a space. License records — which consist solely of the user's email address, license type, and license code — are retained for as long as a valid license exists, as they are necessary to authenticate the user and prevent duplicate license issuance. Users who wish to inquire about their data may contact us here.
Changes to this Privacy Statement
We may update our Privacy statement from time to time. Thus, you are advised to review this page periodically for any changes. These changes are effective immediately after they are posted on this page.