Trust Center
Security and data handling
A factual overview of the services involved in the o-early workflow, the data they handle, and the limits users should consider before submitting a site.
Authentication and access
Google sign-in is used for account authentication. Workspace routes require an authenticated session, and task records are scoped to the signed-in account.
Infrastructure and storage
o-early runs on Cloudflare infrastructure. Account, task, credit, and workflow records may be stored in D1; generated artifacts and downloadable bundles may be stored in R2; Queues coordinate background processing.
AI processing
OpenRouter may process selected website evidence and prompts to generate analysis. Submit only public websites you are authorized to assess, and avoid confidential content that should not enter a hosted AI workflow.
Payments and email
Creem handles checkout and payment processing; o-early receives relevant payment events but does not store full card numbers. Resend may process account and result email delivery.
Security reports
Report suspected vulnerabilities privately to feedback@o-early.com with reproduction details and impact. Do not access data that is not yours, disrupt the service, or publish sensitive details before they can be reviewed.