Data processing
Subprocessors
The third-party services that help us run Urganize, and what each one processes. This list reflects what is actually in use today.
LAST UPDATED: JUNE 11, 2026
Vercel
Purpose Hosting, deployment, and Vercel Analytics
Data App traffic, server logs, anonymized usage events
Supabase
Purpose App database, authentication, and file storage
Data Account data, release data, and the files you upload
Neon
Purpose Waitlist database (marketing site)
Data Waitlist signups: email and submitted answers
Paystack
Purpose Payment processing
Data Billing details and transactions. Card details go to Paystack directly. We never store them
Google Analytics
Purpose Marketing site analytics
Data Device identifiers, usage events, IP (may be processed), cookies
PostHog
Purpose Product analytics (inside the app)
Data Feature usage events tied to your account
Formbricks
Purpose In-product surveys
Data Survey answers you choose to submit
AI model provider (via our gateway)
Purpose Generating plan tailoring and status updates, only when you use the AI features
Data Release context (details, task progress). Never your uploaded files, and never used to train models
WhatsApp (Meta)
Purpose Customer support: the in-app founder chat
Data Messages you send us there, under Meta's own privacy policy
Google Workspace
Purpose Email correspondence (contact@urganize.app)
Data Email content and addresses
Slack
Purpose Internal team communication
Data Operational messages; may include support context if shared internally
We may add, remove, or replace subprocessors as Urganize evolves. When we do, this page changes in the same release. Questions: contact@urganize.app. See also our privacy policy.