Scoop Analytics

Description Features Permissions Security & Compliance

Bring your data directly into Slack with Scoop Analytics - the AI-powered analytics assistant that eliminates the need for another dashboard or BI tool.Why Scoop in Slack?Stop the dashboard madness. Your team lives in Slack, so why make them log into yet another tool? Scoop brings analytics directly into your workspace, ensuring everyone works from the same data instead of creating conflicting spreadsheets.How It Works:Connect data sources through Scoop or upload files directly to Slack
Each dataset gets its own dedicated Slack channel
Ask questions in plain English like "What's our pipeline by stage?" or "Which customers are at risk?"
Get instant answers with charts, predictions, and explanations
Share insights with your team in real-timeTwo Ways to Get Started:1. Connect via Scoop - Link Salesforce, HubSpot, Google Analytics, and 100+ other sources
2. Upload to Slack - Drop CSV or Excel files directly into Slack for instant analysisKey Benefits:No New Interface - IT stays happy, no additional tools to manage
Single Source of Truth - Everyone uses the same data, no more spreadsheet chaos
Instant Insights - Ask questions, get answers with visualizations in seconds
Team Collaboration - Discuss insights right where the data lives
ML-Powered Intelligence - Discover patterns, predict outcomes, all in plain EnglishPerfect for Teams Who:Are tired of logging into multiple analytics tools
Want everyone working from the same numbers
Need quick answers without SQL or technical skills
Value collaboration over static dashboards
Want to actually use their data, not just look at itWhat You Can Ask:"What drove revenue growth last quarter?"
"Which deals are likely to close this month?"
"Show me customer churn trends"
"What segments have the highest LTV?"
"Why did conversion rates drop?"Each dataset lives in its own channel where your team can explore together. No more "which spreadsheet are you looking at?" or "let me share my screen" - just data-driven decisions happening where work already happens.Stop building dashboards nobody looks at. Start getting answers where your team already works.:warning: AI-Powered Insights Notice: Scoop Analytics uses artificial intelligence and machine learning to generate insights, answer questions, and identify patterns in your data. While our AI is designed to be helpful and accurate, it may occasionally produce incorrect or incomplete results. Always review AI-generated insights and recommendations before making important business decisions. For best results, verify critical findings against your source data and use your domain expertise to validate conclusions.

Permissions

Scoop Analytics will be able to view:

Scoop Analytics 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

Our data retention policy is designed to balance operational needs, legal requirements, and customer privacy while maintaining SOC 2 Type II compliance. Retention Periods: Active Customer Data: Retained for the duration of the customer's subscription/contract period Message and File Data: Retained according to customer's workspace retention settings (customer-configurable) Metadata and Logs: Application logs: 90 days Security logs: 12 months Audit logs: 7 years Backup Data: 30 days rolling retention for disaster recovery purposes Compliance Framework: Adheres to SOC 2 Type II requirements for availability and confidentiality Configurable retention periods to support customer compliance needs (GDPR, HIPAA, etc.) Automated retention enforcement through AWS lifecycle policies Regular audits to ensure policy compliance

Data archiving and removal policy

Archival Process: Automated Archival: Data exceeding active retention periods is automatically archived to AWS S3 Glacier or S3 Glacier Deep Archive Archive Encryption: All archived data maintains AES-256 encryption at rest Archive Access: Retrieved only upon authorized customer request with 12-48 hour retrieval window Data Removal/Deletion: Customer-Initiated Deletion: Soft delete: Immediate removal from active systems, 30-day recovery window Hard delete: Permanent removal within 30 days of request Automatic Deletion: Data exceeding retention policy: Deleted within 7 days Account termination: All data removed within 90 days Secure Deletion Methods: AWS S3 object deletion with versioning Cryptographic erasure for encrypted data Certificate of deletion available upon request Right to Erasure (GDPR): Individual user deletion requests processed within 30 days Automated workflows for bulk deletion requests Deletion logs maintained for compliance verification

Data storage policy

Storage Infrastructure: Primary Storage: AWS S3 with cross-region replication Database: AWS RDS with Multi-AZ deployment for high availability Caching: AWS ElastiCache with encryption in transit Security Measures: Encryption: At rest: AES-256 encryption for all stored data In transit: TLS 1.2+ for all data transmission Key management: AWS KMS with automatic key rotation Access Controls: IAM roles with least privilege principle Multi-factor authentication required for administrative access Regular access reviews and audit trails Geographic Considerations: Data Residency: Customer data stored in customer-selected AWS regions No Cross-Border Transfer: Data remains within selected geographic boundaries unless explicitly authorized Region Options: Currently supporting [list your supported AWS regions] Backup and Resilience: Backup Frequency: Daily incremental, weekly full backups Geographic Redundancy: Backups stored in separate AWS availability zones Recovery Objectives: RTO (Recovery Time Objective): 4 hours RPO (Recovery Point Objective): 1 hour Regular Testing: Quarterly disaster recovery drills Monitoring and Compliance: Continuous monitoring via AWS CloudTrail and CloudWatch Real-time alerting for unauthorized access attempts Annual third-party security assessments SOC 2 Type II audit covers all storage practices

Data hosting details

We are hosted in AWS.

Data hosting company

AWS

App/service has sub-processors

App/service uses large language models (LLM)

yes

LLM model(s) used

Anthropic

LLM retention settings

Anthropic's Zero Retention Policy: No Content Storage: Anthropic does not retain conversation content, inputs, or outputs from API calls Immediate Deletion: Data is deleted immediately after response generation No Model Training: Customer data is never u

LLM data tenancy policy

Data Isolation and Tenancy Model: API-Based Architecture: All interactions with Anthropic occur via secure API calls with no persistent storage of customer data on Anthropic's infrastructure Stateless Processing: Each API request is processed independent

LLM data residency policy

Geographic Processing: API Endpoints: Anthropic's API is accessed via secure HTTPS endpoints Processing Location: LLM inference occurs in Anthropic's infrastructure (primarily US-based) No Data Storage: Since Anthropic doesn't store customer data, tradit

Certifications & compliance

Security