Due it
Trust & Security

Your team’s work lives here.
We act like it.

Due it sits inside your Slack workspace, so it’s held to the same bar as the tools it lives beside. Here is exactly what we do - written from our code, not our marketing.

Every claim on this page verified against our codebase · Last audit: July 21, 2026

We can't read your messages

Due it requests seven narrow Slack permissions - and none of them include message history. Not reading your channels or DMs isn't a policy promise; it's technically impossible with the access we hold.

Tokens are encrypted at rest

Your workspace's Slack credential is sealed with AES-256-GCM before it ever touches the database, decrypted only in memory for the moment a request needs it, and scrubbed the instant you uninstall.

Every workspace is an island

Every database query is scoped to your workspace, resolved from a cryptographically signed Slack team ID. No shared lists, no cross-tenant paths, no exceptions.

Forged requests bounce

Everything Slack sends us is signature-verified against the raw payload with a 5-minute replay window and constant-time comparison. Stripe webhooks are signature-verified, stored in a durable inbox, and processed idempotently. Unsigned traffic is rejected.

Files never leave Slack

Attachments are re-hosted inside your own Slack workspace, under the governance your admins already run. The Due it database keeps only the filename, size, and link - never the bytes.

Uninstall means gone

Uninstalling revokes and scrubs your token immediately and schedules the Stripe subscription not to renew. Product data waits 90 days in case you come back, then is deleted. If billing is still nonterminal, only the minimum reconciliation records remain. Want eligible data gone sooner? One email.

The stack underneath

Standing on certified shoulders.

Due it runs entirely on independently audited infrastructure. Every layer below us holds the certifications security teams ask about.

VercelHosting & compute
SOC 2 Type 2ISO 27001
PlanetScaleDatabase
SOC 2 Type 2
StripePayments
PCI DSS Level 1SOC 1 & 2
SlackPlatform & file storage
SOC 2 Type 2ISO 27001

What we store

  • Tasks, reminders, and notes your team writes in Due it
  • Due dates, completion status, and who's tagged
  • Names, avatars, and emails from Slack profiles
  • File names and links (the files live in Slack)
  • Billing status, synced from Stripe

What we never store

  • Your Slack messages - we don't have the permission
  • File contents on our servers
  • Card numbers - checkout is hosted by Stripe
  • Passwords - Slack is the only sign-in
  • Anything from one workspace shown to another

If you ever leave

Day 0

You uninstall

Access is revoked, your encrypted token is scrubbed immediately, and the Stripe subscription is scheduled not to renew.

Days 1-90

Grace window

Your tasks and reminders are held so reinstalling picks up exactly where you left off. Nothing is shared, sold, or touched.

After day 90

Permanent deletion

An automated sweep deletes Due it product data. If Stripe billing is still nonterminal, Due it retains only the workspace and billing identifiers plus retryable billing events until terminal. Stripe retains invoices and legally required payment records under its own obligations.

Found something? Tell us first.

We read every security report and respond fast. If you believe you’ve found a vulnerability, email us before disclosing it anywhere else.

Report a security issue

Data export or early deletion requests: support@demosix.com