Managed cloud
Facts reviewed:
OwlEye hosts the reports and tracking configuration so you can focus on where visitors drop off. Install the optional rules module once, configure supported interactions in the dashboard, and compare the steps in a funnel. Stable selectors are required, and new tracker starts or page loads fetch saved rule changes.
Create a Free account to collect up to 10,000 billable events per month, or choose a paid plan for more capacity. Check the service status page for current reported availability.
Start free · Compare plans · Service status
One hosted product
Section titled “One hosted product”OwlEye runs the API, ClickHouse analytics storage, and console for hosted customers. The visitor SDK writes no cookies or browser storage. The authenticated console uses secure HttpOnly cookies for team access.
Customer-site uptime checks are not offered in current plans. OwlEye service availability and incident updates are published at https://status.owleye.dev/. Existing monitor configuration is retained for a possible future release; the service does not perform scheduled URL checks or send monitor alerts.
Hosting and verification
Section titled “Hosting and verification”The Privacy Policy identifies AWS Ireland (eu-west-1) as the primary API and database region, matching the documented deployment configuration. Cloudflare serves the public website and Console. Better Stack publishes the service’s status page; that service monitoring is separate from the unavailable customer-facing uptime feature.
As of October 21, 2026, the website, Console and public API responded successfully. The API readiness endpoint reported SQLite and ClickHouse ready, with the most recent successful retention reconciliation on October 20, 2026. The status page reported the listed services operational at the time of review. These are observations at that time, not an availability guarantee.
This review checked application behavior, deployment documentation and those public endpoints. It did not independently inspect AWS resources, complete a payment or email-delivery test, or verify backup encryption, expiry and restore results. The regional statement above identifies the published hosting commitment; it is not a new infrastructure attestation.
Monthly collection buffer
Section titled “Monthly collection buffer”Your included allowance is a soft limit. A no-charge buffer keeps billable collection running up to twice that allowance within the same UTC calendar month. There are no automatic overage charges. The console shows usage and the final collection limit, and queues owner email notices at 80% and 100% of the included allowance. If the buffer is exhausted, billable collection stops until the next month or an allowance increase; dropped events cannot be recovered. Free also has a separate raw-telemetry safety limit. Paid duration and performance measurements remain subject to their existing collection limits.
Verified, allowlisted bots may contribute page views and page sessions, but those records are never billable. Identified bots cannot submit custom events. Normal rate and raw-collection safeguards still apply. Overview hides identified bot views by default; turn off Hide bot views to include them without changing billing. These records must reach the ingestion API; crawlers that do not execute the browser SDK are not automatically recorded.
Analytics retention
Section titled “Analytics retention”Active retention and grace periods use calendar months. Free retains 12 calendar months. Active data is queryable normally. Post-active grace removes data from normal analytics but delays purge eligibility. Paid grace includes a controlled owner export; the one-time Free grace does not provide an archive or ordinary export.
| Cloud tier | Active analytics | Post-active grace | Purge eligibility |
|---|---|---|---|
| Free | 12 calendar months | One inactive month before the account/site subject’s first purge; no archive/export feature | First purge: 12 calendar months + one month; later data: 12 calendar months |
| Pro | 24 calendar months | 1 calendar month with owner export | Month 25 |
| Business | 36 calendar months | 1 calendar month with owner export | Month 37 |
| Custom | 36 calendar months | 2 calendar months with owner export | Month 38 |
The Free grace happens once per customer account; a legacy standalone site is the fallback subject. It does not restart after inactivity, creating or renaming another site, upgrading, or downgrading. Free has no user-facing backup or archive product. A legally required access export remains available regardless of plan.
Upgrades can extend facts that still exist but cannot resurrect purged data. A downgrade applies the shorter tier to new facts after the paid entitlement ends; it does not silently shorten dates already stamped on older facts.
Tuesday reconciliation
Section titled “Tuesday reconciliation”Tier retention is reconciled every Tuesday at 12:00 Asia/Kolkata. A row can therefore wait up to seven additional days before eligible purge work is enqueued. Physical ClickHouse deletion is asynchronous and must be verified separately; “up to seven days” describes the normal scheduling lag, not an unbounded deletion-completion promise.
Upcoming-cutoff notifications are deduplicated. Retention work is queued and ClickHouse deletion completes asynchronously; an email is not confirmation that a deletion has finished.
A verified erasure request overrides the tier, grace period, and Tuesday schedule. A narrow, documented legal hold can delay only the data counsel identifies. Access and portability requests are rights workflows, not paid backup features.
Email and disaster recovery are different things
Section titled “Email and disaster recovery are different things”A retention email is metadata-only notification. It contains no analytics attachment and is not an export or backup.
Internal disaster-recovery backups are separate from customer-facing analytics and exports. The operating policy requires restricted access, encrypted storage, a documented expiry and replay of erasure and retention tombstones before restored service resumes. These are operational requirements; this content review did not verify a deployed backup schedule or a completed restore. A plan’s analytics-retention period does not establish a backup-expiry period or a customer restore guarantee.
Service boundaries
Section titled “Service boundaries”Availability does not imply an SLA or compliance certification. Analytics are estimates and can be incomplete because of browser settings, blocked requests, and network failures. Read privacy controls and data handling for implementation choices and responsibilities.