database Data Collection
SeerOps collects only the data necessary to provide our incident management services. We collect:
- Account information: email address, organization name, and billing details when you sign up
- Alert data: monitoring alerts sent to SeerOps via webhooks from your configured integrations (Datadog, PagerDuty, Grafana, CloudWatch, and others)
- Incident metadata: AI-generated root cause analysis, recommended actions, and resolution history
- Usage data: API call counts, feature usage, and performance metrics for service improvement
- Slack interaction data: button clicks and feedback provided through Slack interactive messages
analytics Data Usage
Your data is used exclusively to:
- Process and correlate incoming alerts to identify incidents
- Generate AI-powered root cause analysis and remediation recommendations
- Build your organization's institutional memory — past incident resolutions that improve future recommendations
- Send notifications through your configured channels (Slack, email, etc.)
- Improve the accuracy of our AI models within your tenant's isolated environment
- Provide billing, support, and account management
We never use your incident data to train models shared across tenants. Your institutional memory is yours alone.
cloud Data Storage
All data is stored in Supabase (PostgreSQL) hosted in the EU-West-1 (Ireland) region. Alert embeddings are stored as 768-dimensional vectors using pgvector. Data is encrypted at rest using AES-256 and in transit using TLS 1.3. Backups are automated and encrypted.
share_off Data Sharing
We do not sell, rent, or share your data with third parties. Period.
The only external services that process your data are:
- Google Gemini API — for generating embeddings and AI analysis. Data is sent via encrypted API calls and is not retained by Google for training.
- Slack API — for delivering notifications to your configured workspace. Only the data you choose to include in notifications is sent.
- Stripe — for payment processing. We never store credit card numbers on our servers.
cookie Cookies
SeerOps uses a single HttpOnly session cookie (seerops_session) for authentication. We do not use tracking cookies, advertising cookies, or any third-party analytics scripts. Your session cookie is:
- HttpOnly — inaccessible to JavaScript for security
- Secure — transmitted only over HTTPS
- SameSite — protected against CSRF attacks
shield_person Your Rights
Under GDPR and applicable data protection laws, you have the right to:
- Access — request a copy of all data we hold about your organization
- Rectification — correct any inaccurate personal data
- Erasure — request deletion of your data ("right to be forgotten")
- Portability — receive your data in a machine-readable format
- Objection — object to certain types of data processing
To exercise any of these rights, contact us at the address below. We will respond within 30 days.
mail Contact
For privacy-related inquiries:
Email: info@seerops.com
Data Protection Officer: Raziel Amir
Response time: Within 30 days for formal requests