Subprocessors
Third-party services that CueAPI uses to operate.
Infrastructure
| Service | Purpose | Data processed |
|---|
| Railway | Application hosting | API requests, execution data, cue definitions |
| Railway PostgreSQL | Primary database | User accounts, cues, executions, outcomes |
| Railway Redis | Caching & task queue | Auth cache, rate limits, job queue |
Payments
| Service | Purpose | Data processed |
|---|
| Stripe | Payment processing | Email, plan selection, payment methods |
Email
| Service | Purpose | Data processed |
|---|
| Resend | Transactional email | Email addresses, magic link tokens |
DNS & CDN
| Service | Purpose | Data processed |
|---|
| Cloudflare | DNS, CDN, DDoS protection | Domain routing, request proxying |
Monitoring
| Service | Purpose | Data processed |
|---|
| UptimeRobot | Uptime monitoring | Health check responses (no user data) |
Data residency
All infrastructure is hosted on Railway's US regions. Database backups are managed by Railway.
What CueAPI does NOT do
- CueAPI does not inspect, parse, or store the content of your webhook payloads beyond what's needed for delivery
- CueAPI does not read your handler script source code
- CueAPI does not access your callback URL endpoints outside of scheduled deliveries
- CueAPI does not share user data with any service beyond what's listed above
