How SentinelIQ handles your data.

Account data: the email address you use to sign up, the display name you choose for your workspace, and the authentication identifiers maintained by our auth provider (session tokens, hashed password credentials if you choose password sign-in, or OAuth profile details if you sign in with a third-party identity provider).

Billing identifiers: when you subscribe, our payment processor (Stripe Connect) stores the data needed to bill you — card brand, card last four, billing country and postal code. We never see or store your full card number, expiry, or CVC.

Monitored brand keywords: the names, product names, executives, and competitor names you ask us to watch. These are your inputs and stay inside your workspace.

Product interactions: the mentions and sentiment we discover for you, the alerts you receive and act on, the AI-drafted responses you keep or discard, your annotation history, and an audit log of who did what in your workspace.

Observability telemetry: standard server logs, error reports, and aggregated usage analytics needed to keep the service running, detect abuse, and fix bugs.

To provide the service you signed up for: run the monitoring pipeline on the keywords you configured, classify and score the mentions we find, draft suggested responses in your voice, and deliver the alerts and dashboards you see in your workspace.

To bill you for the service via Stripe Connect, send receipts, and process refunds. We do not use your billing data for any other purpose and never share it with advertisers.

To improve the product: aggregate, de-identified usage statistics (for example, "X% of workspaces enable Slack alerts") that help us decide what to build next. We never sell your data, and we never share identifiable workspace data with third parties for their own use.

To respond to your support and security requests: when you write to us or report a problem, we use the information you give us to investigate and reply, and to keep a record of the conversation.

Stripe Connect — processes subscription payments on our behalf. Stripe receives the billing identifiers your card method exposes and is responsible for its own security and retention of that data.

Auth provider — our auth stack maintains your login sessions, hashed credentials, and OAuth connections. It only sees what is needed to authenticate you.

Hosting and observability provider — the infrastructure that runs SentinelIQ, plus the error-reporting and log-aggregation tools we use to keep the service healthy.

AI inference — any AI generation in the product (sentiment classification, draft responses) is routed through the Polsia AI proxy. We do not call model-provider SDKs directly, and we do not store third-party API keys for AI providers.

Email and file delivery — when we need to send transactional mail or store exported files on your behalf, we use our managed email and file-storage proxies rather than embedding third-party SDKs in the app.

Mention history: Starter workspaces retain the most recent 30 days of monitored mentions; Teams workspaces retain the full history of the workspace. Mention rows are retained only as long as your workspace exists, plus a short grace period to recover from accidental deletion.

Account and subscription data: retained for the life of your workspace. Closing your workspace triggers deletion of stored mention history and session data — your mention data does not outlive the workspace that produced it.

Billing records: kept as long as we are legally required to for tax and accounting purposes (typically seven years), and only the data Stripe exposes to us.

Backups: rolling infrastructure backups exist for disaster recovery. Backups are overwritten on a normal schedule and are not used to revive data you deleted.

Export: you can export every mention in your archive at any time from your dashboard. The export covers the full history your plan retains.

Delete: closing your account from your workspace settings removes stored mention history and session data for that workspace.

Update: account email, display name, and OAuth connections are editable from your account settings at any time.

Contact: any privacy question, access request, or complaint goes to our team via the contact form.

When we make a material change to this policy, we update the "Last updated" date at the top of this page, and — where the change affects existing customers — we send a notice to the email address on your account before the change takes effect.

Non-material edits (clarifications, typo fixes, rewording without a change in practice) are posted without a notice. The version history of this page is the source of truth.