Balto Notifications & Slack Integration

Balto Notifications

Description Permissions Security & Compliance

Get the moments that matter delivered to the right manager, in Slack, the instant they happen.Balto Notifications connects your Balto account to Slack. When an agent raises their hand, a QA dispute is filed, a scorecard fails, or you're mentioned in a call note, Balto sends you a direct message that links straight back to the call or task. No new tab, no noisy channel.Requirements
• An active Balto subscription. Balto Notifications is available to existing Balto customers.
• Your Slack account email must match the email on your Balto account, so alerts reach the right person.How to turn it on
1. A Balto admin opens Organization Settings → Manage Slack notifications
2. Click "Add to Slack" and approve the app in your workspace
3. Each manager picks which alerts they want in Slack from their notification preferencesPricing
Balto Notifications is included with every Balto subscription at no additional cost. Balto is licensed per seat under enterprise agreements, so pricing is quoted for each organization. To get a quote, contact our sales team at https://www.balto.ai/contact, or reach out to your Balto account manager if you're already a customer.

Balto Notifications will be able to view:

Balto Notifications will be able to do:

Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.

General

Privacy & data governance

Data retention policy

Slack data: Balto Notifications stores only your Slack workspace ID, the bot token issued at install, and the Slack user IDs of Balto users whose Slack email matches their Balto email. This data is kept for as long as the app is installed. We do not read or store Slack messages, channels, or files. Balto data: Notification content stays in Balto and follows Balto's default retention periods, unless a different period is set in the customer's agreement: - Call transcripts: up to 2 years - Call audio: up to 180 days - Screen recordings: up to 120 days

Data archiving and removal policy

When a workspace uninstalls Balto Notifications or revokes its token, Balto deletes the stored token, workspace ID, and Slack user mappings. Customers can also request deletion of their data at any time by contacting support@balto.ai. Balto backs up its production database once a day. Backups are encrypted, kept for 30 days, and then permanently deleted. Deleted data is fully removed from backups within 30 days.

Data storage policy

Balto Notifications stores your Slack workspace ID, the bot token issued at installation, and the Slack user IDs of matched Balto users. Balto stores all of this in its production database on Amazon Web Services (AWS) in the United States. Data is encrypted at rest with 256-bit encryption and in transit over TLS, including all communication between Balto and Slack's API. The bot token is used only to send direct messages to matched users and is never shared with third parties. Access to production data is restricted to authorized Balto personnel through role-based access controls. Balto backs up the database once a day; backups are encrypted and kept for 30 days.

Data center location(s)

United States

Data hosting details

Cloud-hosted on Amazon Web Services (AWS) in the United States. Balto runs as a multi-tenant SaaS application. Data is stored in a managed AWS database, encrypted at rest and in transit, with daily encrypted backups.

Data hosting company

AWS

App/service has sub-processors

App/service uses large language models (LLM)

Certifications & compliance

SOC attestation

https://trust.balto.ai/

Privacy Shield notice

https://www.balto.ai/terms/privacy-policy/

GDPR commitment

https://trust.balto.ai/

Data deletion request procedure

Data Storage Policy: Balto for Slack stores only what it needs to send direct messages to managers: the bot token Slack issues at install (encrypted), your Slack workspace ID (so we know which Balto organization the install belongs to), and the Slack user IDs of people who have received the app's one-time welcome message (so we don't send it twice). We never read or store Slack messages, channels, files, or user profiles. To find the right person to message, we look up one manager's work email when we send and don't keep the result. Balto stores this data in its encrypted database on AWS in the United States. Our service logs record which manager a notification was for (by their work email) and whether it was delivered. Those logs are searchable for 7 days, then moved to Balto's long-term log archive. Data archival/removal policy: We keep the bot token only while your workspace is connected. When an admin clicks Disconnect in Balto, or anyone removes the app from your Slack workspace, we mark the connection inactive right away and stop sending messages. If the app is removed from Slack, Slack also revokes the token, so the stored copy can't be used. The inactive, encrypted record stays in our database as install history until you ask us to delete it. Messages the app already sent stay in your Slack workspace and follow your workspace's own retention settings. Removing the app doesn't delete them. Procedure for handling requests for data deletion: Email privacy@balto.ai or your Balto account team. We confirm the request comes from an admin of that organization, then permanently delete the stored token, workspace ID, and welcome-message list from our database and confirm by email. To stop the app right away, an admin can disconnect it in Balto (User Management > Manage Slack Notifications) or remove it from the workspace in Slack. Requests to delete other Balto data, like call data or user accounts, follow our Privacy Policy: https://baltosoftware.com/privacy-policy/

HIPAA compliant

yes

While this app may offer HIPAA compliance, Slack does not have a business associate agreement with any third-party application providers, including those in the Slack Marketplace, so you are responsible for validating the provider's compliance and executing an appropriate agreement before enabling.

Security