What Lurker reads, sends, stores, and leaves alone.

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.

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.

Optional Meta advertising measurement

Meta measurement is off unless you separately allow it through Ad privacy. When allowed, our isolated measurement page and server-side Conversions API send browser identifiers and page-view, completed workspace signup, checkout-start and verified paid checkout events to Meta to measure Facebook and Instagram ads. Purchase events include the amount and currency. A random measurement identifier is hashed for server matching; browser type may also be included. Consent given when starting a checkout is saved with that checkout to report its resulting payment, including if you do not return to Lurker. We do not send names, emails, account identifiers, Facebook content, groups, posts, messages, or form contents. Meta may associate measurement with your Meta account under its privacy policy. Your choice is shared between getlurker.com and app.getlurker.com for up to six months. Change or withdraw it through Ad privacy on either site to stop new measurement activity; browser privacy signals also disable new collection. Previously initiated checkouts may still report their payment result. Browser blocking can prevent browser delivery; consented server delivery can continue. Website analytics consent alone does not enable Meta measurement.

If you accept analytics, AJAI also records public pages viewed, return visits, referral sources, general device type, and categories of links clicked in its private CRM. A random browser identifier lasts up to 90 days on this website. It does not identify you across unrelated websites or devices. Visitor events exclude form values, URL queries and fragments, and raw IP addresses. History is limited to 90 days, with older records removed as new visits are processed. Declining or withdrawing analytics stops collection and clears the identifier. Authenticated app activity is excluded.

Website analytics stays separate from extension activity

With your permission, getlurker.com uses a separate Google Analytics 4 web stream and Microsoft Clarity heatmaps and session recordings to understand public-site visits and masked interactions. Optional tags remain off until you accept analytics. Choose Essential only to decline, or use Privacy choices to withdraw future collection. Blocking analytics 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.

Clarity is limited to this public website; it is not installed in the extension or authenticated Lurker app. Page text is masked and advertising personalization is disabled. Our GA page URLs exclude query strings. See Microsoft’s privacy statement and Google’s privacy policy.

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. Product and account support is available at support@getlurker.com.

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.