Urganize uses trusted third-party services (“subprocessors”) to help us operate the platform. This page lists the subprocessors we may use and what they do.
Purpose: Hosting and deployment
Data involved: App traffic, server logs, operational data
Purpose: Usage analytics
Data involved: Device identifiers, usage events, IP (may be processed), cookies
Purpose: AI processing for guidance and recommendations
Data involved: User inputs and context needed to generate outputs
Purpose: Payment processing
Data involved: Billing metadata and transaction details (we do not store card details)
Purpose: Email communications
Data involved: Email content and addresses
Purpose: Database infrastructure
Data involved: User account and product data stored by Urganize
Purpose: Authentication and storage services
Data involved: Auth identifiers, tokens, and files you upload (if enabled)
Purpose: Internal team communication
Data involved: Operational messages (may include support context if shared internally)
Purpose: Customer messaging and support
Data involved: Messages and identifiers needed to communicate with you
Purpose: Customer messaging and support
Data involved: Messages and identifiers needed to communicate with you
Purpose: Product updates and marketing emails
Data involved: Email address, subscription preferences, email engagement metrics
We may add, remove, or replace subprocessors as Urganize evolves. If you have questions about this list, contact us at theurganization@gmail.com.