EazeProEazePro policies
Subprocessors
Service providers that may process customer data to help Codepaper Technologies Inc. operate EazePro.
Effective and last updated: October 5, 2026
Current providers
| Provider | Purpose | Processing location |
|---|---|---|
| Vercel | Application hosting, content delivery, and platform infrastructure | United States / global infrastructure |
| Neon | Managed PostgreSQL database infrastructure | United States / configured cloud region |
| Stripe | Payment processing, connected accounts, and financial services | Canada, United States, and global infrastructure |
| Resend | Transactional email delivery | United States / global infrastructure |
| Inngest | Background jobs, event processing, and workflow execution | United States / global infrastructure |
| Expo | Mobile application build, update, and push-notification services | United States / global infrastructure |
| Apple | iOS distribution and push-notification delivery | Global infrastructure |
| Android distribution, push notifications, maps, and place services | Global infrastructure | |
| Meta / Muse | Optional user-authorized AI connector and MCP client | United States / global infrastructure |
Optional connected services
A customer may direct EazePro to connect to Muse or another supported service. Optional providers receive data only when an authorized user enables the integration and grants the displayed scopes. Access can be revoked from EazePro at any time.
Changes
Providers and processing locations may change as the platform evolves. We evaluate providers according to their role and update this page when a material subprocessor is added or replaced. Questions may be sent to info@codepaper.com.