Privacy Policy

Who operates these services

PixelGaps is the product name used for this website and the Lodey project. For privacy and data rights inquiries, use our support contact. This website describes projects and does not provide account registration.

Website visitors

Accessing pixelgaps.net sends standard network request information, which may include IP address, request URL, device/browser metadata and time, through our infrastructure provider Cloudflare. That infrastructure may process operational and security logs under its own service policies. We do not set advertising cookies or collect form submissions through this website.

Lodey application data

Lodey is currently an offline-first operator-run research tool, not a hosted consumer account service. It stores keyword hypotheses, sourced research observations, provider request metadata and research checkpoints in an operator-controlled local SQLite database. Mock and live evidence are identified separately. Database contents are managed by the operator; there is no public self-service data account or deletion interface.

Google user data and Google Ads API

The current public PixelGaps website does not ask users to sign in with Google or access their Google Ads data. The Lodey Google Ads integration has not run against a production Google Ads account. If authorized later, it is designed to request Google Ads Keyword Planner keyword ideas and historical advertising statistics for an explicitly selected account, country, language and keywords. The required OAuth permission is https://www.googleapis.com/auth/adwords; it is broad at the Google permission level, although Lodey currently implements keyword research requests rather than campaign creation, editing or publishing. An operator authorizes access for this research purpose and controls the connected account.

Authorized research observations may be stored in the local SQLite database with provider identity, timing and targeting context; credentials and OAuth access tokens are not research records. An operator may supply Google OAuth credentials and a refresh token securely at runtime, but the public website does not collect them. Lodey does not sell Google user data, share it with data brokers, use it for personalized advertisements, or use it to train generalized AI models. Google Ads research data is intended for the operator’s research workflow, not third-party marketing. No Google account data is currently collected by the public website.

Where a future operator authorizes Google access, the operator is responsible for access controls, retention and deletion of stored research and credential material. Research evidence is retained in an operator-controlled local database until the operator removes it; there is no automatic deletion schedule in the current MVP. OAuth credentials and tokens are held outside the public website, managed by the trusted operator, and are not included in its research records. Google authorizations can be revoked through the connected Google account's third-party access settings. To request review or deletion of data under PixelGaps' control, reach us through the support page.

Sharing and security

Website network information is processed by hosting and security infrastructure. Lodey research may involve third-party information providers when separately authorized; outbound query terms and required account identifiers may be sent to those selected providers. Access credentials are kept outside public website code and should be injected by trusted operators. We do not claim that any platform provides absolute security.

Your choices

You may contact us for questions, corrections, access or deletion requests where applicable. Relevant legal rights depend on your jurisdiction. We may update this notice when actual hosted functionality or data processing changes; the date above identifies this version.