Trust Center
Safety, Data, And Launch Boundaries
WarpIntel is being built public-first with conservative boundaries. This page gives players, reviewers, and service providers one place to inspect how the app handles EVE data, safety, security contact, production health, attribution, and launch revenue rules.
EVE App Boundaries
WarpIntel is an independent third-party advisory app. It helps players review information without automating gameplay.
- No EVE client modification, packet inspection, botting, gambling, betting, raffles, lotteries, or real-money trading.
- SRP, access, recruiting, buyback, payout, and organization decisions stay human-reviewed.
- Public tools can be used without EVE sign-in.
Data Posture
The first launch favors public ESI, user-provided text, browser-local storage, and privacy-safe operational metrics.
- Private EVE SSO scopes are requested feature by feature instead of forced during general signup.
- Consent-preview checks show which scopes will be requested before OAuth redirects to CCP.
- Raw pasted analyzer inputs are not stored in account reports.
- Private EVE SSO data is kept out of public pages, ads, screenshots, analytics, and logs.
- Export, deletion, browser-local storage, and EVE disconnect controls are documented before public SSO launch.
Security Contact
Security reports have a public contact path and a machine-readable security.txt file for responsible disclosure.
- Reports should include the affected page, route, steps, expected behavior, actual behavior, and impact.
- Testing must not access another user's data, cause service abuse, or bypass provider controls.
- The support mailbox is the first public security intake while the project is in buildout.
Production Health
Public status and health routes expose readiness, release metadata, and service boundaries without admin data.
- The public health endpoint reports readiness and sanitized release metadata only.
- Protected ops monitoring tracks route smoke, service checks, queues, and launch blockers.
- Auth, account, analyzer API, analytics API, EVE tool/read API, Discord API, manual intake, protected admin, setup packet/action/export, admin action, and cron health-check responses use private no-store/no-cache headers.
- External services stay behind feature flags until provider setup and approvals are ready.
Sources And Ownership
Source notes separate official public EVE data, community context, user-provided inputs, local calculations, and AI summaries.
- WarpIntel is not affiliated with, endorsed by, sponsored by, or operated by CCP hf., Fenris Creations, or EVE Online.
- EVE Online names, images, data, logos, and marks remain the property of their respective owners.
- AI summaries are treated as explanation and planning support, not hidden authority.
Launch Revenue Rules
Revenue lanes are launch-safe, opt-in, and separated from private EVE permission decisions.
- Support payments are voluntary and do not unlock EVE app features at launch.
- Ads are planned for public pages only after provider review and UX checks.
- Paid private dashboards or hosted alliance products stay approval-gated.
Public Trust Feed
The Trust Center is also available as no-secret JSON for reviewers, monitors, and public launch checks.