Sentinel collects the minimum information required to run the service. We group it into three categories:

• Account data. Your name, email address, and authentication identifiers. This comes from Clerk, our authentication provider. We never see or store your password.
• Workspace data. The deals, activity events, integration tokens, and webhook configurations you create in Sentinel, plus anything we sync from a connected CRM or calendar on your instruction.
• Operational data. IP address, user-agent, request IDs, and timestamps tied to your sessions. We use this for rate limiting, error diagnosis, and abuse prevention.

Strictly to run the product and keep it working. Specifically:

• To deliver the features you signed up for - risk scoring, timelines, notifications, and integrations.
• To send transactional email you've opted into (risk alerts, stage-change notifications, weekly digests) and account email you cannot opt out of (billing, security).
• To generate AI-powered risk scores and summaries, scoped to your workspace. Your data is never used to train shared or cross-customer models.
• To monitor reliability, debug errors, and prevent abuse through standard application logs and performance monitoring.

We do not sell personal data, and we don't run third-party ad trackers on the marketing site or in the product.

A short list of subprocessors - the vendors we rely on to operate Sentinel. Each one receives only the data it needs to do its job.

Vercel

Application hosting and edge delivery.

Managed Postgres

Production database with daily backups and point-in-time recovery.

Clerk

User authentication and session management. Passwords never touch our servers.

PayPal

Subscription billing. Card details are handled by PayPal, not by us.

Sentry

Application error and performance monitoring. Scrubs known secret patterns before ingestion.

Upstash

Rate limiting and ephemeral storage. No durable workspace data stored here.

AI providers

Scoped per-request inference. No training on your data.

All traffic uses TLS 1.2+. Integration tokens and webhook secrets are encrypted at rest in the database. Content-Security-Policy and Permissions-Policy headers are set strictly on every response, and rate limiting runs on all mutating routes.

No transmission or storage system is perfect. We design for minimal exposure: least-privilege, scoped integration credentials that can be rotated without a full reconnect, and deletion that propagates within 24 hours. Details live on the security page.

We keep workspace data for as long as your account is active. When you delete your account, we:

• Revoke and delete all integration tokens and webhook secrets within 24 hours.
• Delete your user-scoped records and workspace content within 30 days.
• Retain a minimal set of billing and audit records only for as long as required by law.

Webhook delivery logs are kept for 30 days regardless of account status so you can audit recent deliveries.

You can access, export, correct, or delete your data at any time - most of it from Settings inside the product. Data export is available in CSV or JSON. To delete your account entirely or request an out-of-band export, email help@sentinels.in and we'll handle it within 7 business days.

You can opt out of marketing email at any time from the email footer or the Settings page. Transactional and security email cannot be opted out of while your account is active.

We may update this policy as the product changes. Material changes will be announced by email and with a banner in-product at least 30 days before they take effect. The Last updated date at the top of this page always reflects the most recent revision.

Privacy questions, deletion requests, and responsible-disclosure reports all go to help@sentinels.in. Replies come from a human, usually within one business day.