kanNINJA

Subprocessors

The names behind the scenes.

kanNINJA uses the third-party services below to deliver its product. Each one is bound by a data protection agreement that limits what they can do with your data and requires them to maintain appropriate security.

Customers on the Data Processing Addendum receive at least 30 days' notice before we add a new subprocessor that processes personal information.

Last updated · April 24, 2026·Effective · April 24, 2026

01

Current subprocessors

Authentication

Clerk

DataName, email, hashed password, social-login identifiers, session cookies.LocationUnited StatesPrivacyclerk.com

Payment processing

Stripe

DataCardholder name, card details (Stripe-tokenized — we never see full card numbers), billing address, transaction history.LocationUnited StatesPrivacystripe.com

Database and realtime infrastructure

Supabase

DataAll customer content stored in kanNINJA — boards, lists, cards, comments, attachments, profile data, audit logs.LocationUnited States (managed Postgres + Realtime)Privacysupabase.com

Application hosting (AKS, West US 3)

Microsoft Azure

DataAll customer content while it is being processed by the application; logs and metrics.LocationUnited States (West US 3)Privacymicrosoft.com

AI features (suggestions, summaries, drafting)

OpenAI

DataCard content or prompt text you submit to an AI feature, plus the response. Per OpenAI API terms, not used to train models; deleted within 30 days unless required by law.LocationUnited StatesPrivacyopenai.com

Transactional email delivery

Resend

DataRecipient email, sender, subject, body of transactional messages (invitations, receipts, password resets); delivery metadata.LocationUnited StatesPrivacyresend.com

Web analytics

Google Analytics 4

DataAnonymized page views and events, approximate location from IP (IP anonymization enabled), browser metadata.LocationUnited StatesPrivacypolicies.google.com

Session replay and heatmaps

Microsoft Clarity

DataAnonymized recordings of in-app sessions with form input, passwords, and card content masked by default; heatmap aggregates.LocationUnited StatesPrivacyprivacy.microsoft.com

Optional integration

Google (Calendar)

DataOnly if you connect Google Calendar: OAuth tokens and the calendar events you grant access to.LocationUnited StatesPrivacypolicies.google.com

Optional integration

Slack

DataOnly if you connect Slack: OAuth tokens and the channel/message metadata you grant access to.LocationUnited StatesPrivacyslack.com

Optional integration

GitHub

DataOnly if you connect GitHub: OAuth tokens and the repository metadata you grant access to.LocationUnited StatesPrivacydocs.github.com

02

Subscribing to changes

We post changes here and announce them in the in-app changelog. To receive direct notice for your account, make sure your billing or admin contact email is current in Settings → Workspace.

If a subprocessor change is unacceptable under your data protection requirements, contact privacy@kanninja.com during the notice period to discuss alternatives or termination.

Questions

Email privacy@kanninja.com. A human reads it.

← Back home

Cookie preferences

Decide what we can use.

Necessary cookies stay on so the service can run. The other two are yours to choose.

Authentication, theme, billing fraud prevention. Required for the service to work.

Anonymized page views and events via Google Analytics 4. Helps us see which features matter.

Anonymized recordings via Microsoft Clarity. Form input, passwords, and card content are masked by default.

Subprocessors · kanNINJA