Privacy Policy

OwlEye is operated by Shrinath Prabhu, operating as OwlEye, based in Mumbai, India. For privacy questions or requests, contact privacy@owleye.dev.

This policy covers OwlEye’s website, hosted Console, and hosted analytics service. If someone runs the open-source edition on their own server, that operator is responsible for their own data handling and notice.

What we process and why

Account and service information. We process your email address, profile, organization and app memberships, authentication records, and service settings to provide access, administer your account, and protect the service. If you choose Google sign-in when available, Google provides your account identifier, verified email, and profile information for authentication.

Analytics. Customers configure collection from their websites and apps. Events can include page paths, referrer information, event names, allowed custom properties, browser/device information, approximate location, campaign attribution, and optional performance data. We process those signals to provide reports and the features the customer requests. Customers control their instrumentation and are responsible for their own visitor notices and collection choices.

We also use OwlEye on our own website and Console to measure page visits, page duration, website links to the Console and quickstart, pricing-plan clicks, successful app creation, and successful tracking-code copies. This instrumentation excludes arbitrary query parameters and URL fragments. SDK 1.0.3 adds automatic bounded campaign tags. We do not include account emails, app names, tracking-code contents, form inputs, or AI prompts as custom event properties. We have not enabled Web Vitals or other performance collection on these surfaces.

Our website and Console configure the SDK to continue collecting when a browser sends Do Not Track or enables Global Privacy Control.

The SDK does not store cookies or persistent visitor identifiers in browser storage. Arbitrary query parameters and URL fragments are excluded by default; SDK 1.0.3 automatically captures bounded campaign tags. Incoming IP addresses are used in memory for location lookup and identifier derivation, not stored as raw source IPs in analytics facts. Site-scoped pseudonyms can still link activity and should not be treated as guaranteed anonymity. The technical privacy guide explains these collection and storage controls in more detail.

Billing and support. We process subscription and payment identifiers, billing status, and information you send us to administer purchases, resolve issues, and answer requests. Payment card entry is handled by Dodo’s checkout. Please do not send card details or secrets to support.

AI. When used, the assistant sends your question, clarification context, a bounded analytics catalog, and aggregate reports through OpenRouter to a model provider. Catalog discovery omits raw visitor IDs and event payloads; information typed into your question can still reach the provider. Do not submit personal information or secrets. Requests require provider routing with zero retention and no data collection; this is not a claim that every provider operation has zero retention. AI data handling explains the boundary.

Cookies and browser storage

The analytics SDK’s cookie-free behavior is separate from account authentication. The Console uses secure HttpOnly session cookies. It uses local storage for session-refresh coordination and expiry timestamps, not visitor identification. Infrastructure and payment providers may use their own cookies or request metadata when you use their services.

Hosting and providers

Our hosted API and primary account and analytics databases run on AWS in Ireland (eu-west-1). This is our primary storage region; it is not a claim that every provider processes data only in Ireland.

OwlEye is operated from Mumbai, India. Operating the service can involve access to account and service information from India for administration, troubleshooting, and support.

Provider	Purpose and information involved
AWS	API hosting and primary SQLite and ClickHouse database storage in Ireland.
Cloudflare	Website and Console delivery, network routing, and edge security; processes requests including network addresses and headers.
Dodo Payments	Checkout, subscription billing, payment processing, and receipts; receives customer and purchase details.
Better Stack	Service availability monitoring and the public status page; configured endpoint URLs and check results.
Resend	Sign-in codes and transactional emails; receives recipient addresses and message contents.
MaxMind	Supplies a GeoIP database for approximate location. Lookups happen on our API server, without sending each visitor’s IP to MaxMind.
Google	Optional sign-in; exchanges authentication and basic profile information when selected.
OpenRouter and the selected model provider	AI questions, clarification context, bounded catalogs, and aggregate analytics used to produce answers.

Provider processing, network delivery, and support can involve locations outside Ireland. Their policies describe their own handling: AWS, Cloudflare, Dodo, Resend, MaxMind, Google, and OpenRouter.

Retention and deletion

Active analytics retention depends on the confirmed plan: 12 calendar months on Free, 24 calendar months on Pro, and 36 calendar months on Business. Expired data leaves ordinary reports before physical deletion completes. Grace periods and scheduled reconciliation are described in the retention table.

Account information is used while providing your account and handling security, billing, and support needs. Account holders can export their account information and request deletion after resolving app and organization ownership. App owners can request deletion of their app’s analytics. Deletion from live databases does not instantly remove independent backups, security logs, transaction records, or records held by providers. Some records may need to be retained for legal or dispute-handling purposes.

Your choices and requests

By default, the SDK stops tracking when the browser enables Global Privacy Control. Do Not Track is no longer consulted. The ingestion API does not filter DNT or GPC headers; browser and server-side integrations must apply their collection choices before sending events. Site operators can also wait to start collection and stop it when appropriate. Cookie-free analytics does not remove a site’s responsibility to assess its own notice and consent requirements.

Contact us to ask about access, correction, deletion, or other privacy choices. We may need to verify your account or authority before disclosing or changing information. If your request concerns a website using OwlEye, contact that website’s operator first; they control collection and access to that site’s analytics. Applicable privacy rights continue to apply regardless of whether a particular law is named here.

We update this page when our data handling changes. The date above identifies the current version.