What Lurker reads, sends, stores, and leaves alone.
This notice describes Lurker's Chrome extension, authenticated app, billing path, support interactions, and public product website. Lurker is an AJAI product designed around visible content and operator review.
Last updated July 25, 2026. This notice does not claim that the unresolved backend purge gap is complete.
Eligible visible content and Lurker settings
Lurker can read eligible visible Facebook group post text, visible notification text, eligible visible comments, group names, post URLs, visible timestamps, and related metadata from supported pages opened in the operator's Chrome session.
The extension can also process Lurker account and workspace state, positive and negative keywords, watched-group settings, watcher mode, capture context, extension version, deduplication state, and diagnostic information needed to operate and troubleshoot the product.
What Lurker does not collect or automate
Lurker does not collect Facebook passwords, Facebook cookies, Facebook access tokens, browser profile archives, Facebook local or session storage, private messages, or hidden account data.
Lurker does not automatically log in, post, comment, react, send messages or direct messages, join groups, or click Facebook response controls. Operators decide whether and how to respond.
The app stores information needed to run the workspace
AJAI may process operator account details, company and workspace configuration, authentication state, plan and entitlement data, usage counters, notification preferences, and support or security records. Paid plan selection uses Stripe Checkout, and authenticated billing management uses Stripe's customer billing flow.
Payment-card details are entered into Stripe's hosted interfaces rather than the public getlurker.com pages. Do not send payment details through support messages.
AJAI stores observations and keeps a person in control
AJAI can use qualifying observations to compare eligible visible content with configured keywords and business context, identify possible opportunities, show operators relevant context, and prepare drafts or approved-media suggestions that operators may review, edit, ignore, copy, download, or use manually.
In an enabled AI-assisted mode, the backend may send submitted post text, eligible visible comments, group and source context, URLs, and relevant customer business context to an AI service for relevance classification or draft assistance. Lurker does not post the resulting draft to Facebook.
AJAI may also process information to suppress duplicates, maintain account and watcher state, enforce plan limits, diagnose reliability issues, improve product quality, protect the service, prevent abuse, and support customer-requested workflows.
Website analytics stays separate from extension activity
getlurker.com contains a guarded Google Analytics 4 module for a separate Lurker web stream. Collection remains disabled unless AJAI supplies the approved measurement ID and completes the consent decision. Blocking or omitting the analytics script does not prevent the website from functioning.
GA4 website analytics does not receive extension activity, Facebook content, group names, post text, usernames, message drafts, billing records, or user-linked extension identifiers. The Chrome extension does not include GA4 telemetry.
This implementation does not use Microsoft Clarity, advertising pixels, or extension analytics.
Infrastructure, delivery, billing, and AI providers may process data
AJAI uses service providers to host, authenticate, store, secure, analyze, bill for, and operate Lurker. The provider and data path depends on whether a person is using the public website, extension, authenticated app, AI-assisted mode, notifications, billing, or support.
AJAI does not sell personal data. Provider training settings, regional processing details, contractual terms, backup retention, and a publication-ready subprocessor list remain subject to owner, technical, privacy, and legal confirmation.
No fixed product deletion period is promised
The current product stores core observations, opportunity records, drafts, decision records, watcher configuration, account state, and related operational data without a verified automatic time-based purge for all of those records. Removing the Chrome extension clears extension-managed browser storage but does not by itself delete records already submitted to the Lurker backend.
AJAI retains Lurker-related information as needed to provide and protect the enabled service, support customers, maintain operational records, and meet approved business or legal requirements. Backup copies and provider systems may not be removed at the same time as active records. This notice does not promise a fixed deletion period.
Access, correction, export, or deletion questions
Customers may ask about access, export, correction, or deletion of applicable customer data. Lurker does not currently provide a verified complete self-service export or deletion workflow for all product records, and the backend purge gap remains unresolved.
Questions about this notice or AJAI data practices can be sent to legal@ajai.pro. The product-support alias is not published until external delivery is confirmed.
Do not send Facebook passwords, authentication cookies, access tokens, private messages, sensitive post content, customer data, payment details, or screenshots containing personal data unless AJAI specifically requests an artifact and provides a safe handling route.
Email the privacy contact