Recon Privacy Policy

1. What Recon does

Recon is a user-triggered LinkedIn writing assistant developed by LunacyDev. It helps users generate profile insight, contextual reply suggestions, comment replies, connection notes, and post drafting assistance directly on LinkedIn pages.

Recon does not automatically send messages, comments, connection requests, or posts. Final control always remains with the user.

2. Data we process

When you trigger a feature, Recon may process the minimum visible LinkedIn context and account data required to complete that request and enforce access controls.

Visible LinkedIn profile details, such as name, headline, company, role, and profile summary
Visible message, comment, invite, or post-composer context needed for reply suggestions, profile insight, comment replies, connection notes, or post drafting assistance
Draft text that you choose to refine or rewrite
Local extension settings, language preferences, browser installation identifiers, signed-in session data, and personalization data stored in browser extension storage
If you enable personalization, limited visible context from your own LinkedIn profile, posts, and replies may be stored locally as writing-style signals for future post drafts
Saved content that you explicitly choose to keep from generated outputs
Feedback signals from actions you take on generated output, such as copy, insert, message, use text, or refine, when account-backed memory features are enabled
Authentication and account data, such as Google profile information or email login details, verified email status, and browser session metadata
Billing and entitlement data, such as plan status, trial eligibility and usage, per-feature usage counters, Stripe customer or subscription references, and checkout or billing portal state

Recon is designed to avoid collecting unrelated browsing data and to avoid processing more context than is needed for the requested feature, authentication, security, or billing.

3. How data is used

Processed data is used only to provide the user-facing features and account services requested by the user, including:

Generating profile insight
Generating contextual reply suggestions
Generating comment replies and connection notes for review
Improving post drafting assistance
Saving local preferences, extension settings, and optional local writing-style personalization
Saving and displaying content that you explicitly choose to keep
Using user feedback signals to improve saved writing preferences when those features are enabled
Authenticating your account, binding your session to a specific browser install, refreshing sessions, and preventing replay or abuse of install credentials
Enforcing billing, trial, and quota rules, including per-feature usage accounting and access decisions
Creating or managing Stripe checkout sessions, subscriptions, and customer portal access when you use paid billing features

We do not sell personal data, build advertising profiles, or use extension data for personalized advertising.

4. Local browser storage

Recon stores data locally in your browser through extension storage. Depending on the features you use, local storage may include:

Settings and preferences, such as language or feature configuration
Optional personalization data captured from your own LinkedIn profile, posts, and replies, including profile summary fields, recent authored samples, topic signals, and writing-style signals used for post drafting
Browser installation identifiers and extension metadata needed to secure the service
Signed-in session data and basic account profile details needed to show sign-in state
Temporary in-tab session state used only to complete the current user-triggered action

Local storage is used so the extension can maintain your settings, identify the current browser installation, and preserve sign-in state until you sign out, clear extension storage, or uninstall the extension.

5. Server-side records and service providers

When you use authentication, billing, or AI-powered features, relevant request data may be sent to LunacyDev infrastructure and to the third-party services needed to complete the requested feature.

LunacyDev infrastructure may store or process account, security, authentication, billing, usage, and service operation records needed to secure and operate the service.
Configured AI model providers may process the request content needed to generate profile insight, reply suggestions, comment replies, connection notes, or post drafting output.
If you choose Google sign-in, Google identity services and browser identity APIs may process OAuth-related sign-in data needed to complete sign-in.
If email login is enabled and you request a code, an email delivery provider may process your email address and login-code message content.
If you use billing features, Stripe may process billing identifiers, checkout requests, customer records, subscription records, and billing portal sessions.
We do not intentionally maintain a product database of full LinkedIn page contents or full user conversations beyond what is needed to complete a requested feature, enforce security, or support billing operations.

6. Permissions and host access

Recon requests only the browser permissions and host access needed to run the extension and the account flows it offers.

activeTab: to operate on the current LinkedIn tab when you trigger a feature
scripting: to inject and run the extension UI on LinkedIn pages
storage: to save local settings, browser installation identifiers, and signed-in session data
identity: to support browser identity APIs, Google OAuth sign-in, and related account flows
Host access: LinkedIn pages and LunacyDev service endpoints are used so the extension can read visible LinkedIn context that you trigger, authenticate, and call the service backend

If Google sign-in is configured for the current build, the extension may also request the Google OAuth scopes openid, email, and profile.

7. Sharing and retention

We only share data with service providers required to operate the feature you requested, such as hosting, authentication, email delivery, payment, or AI model services. We do not sell user data to advertisers, brokers, or resellers.

Server-side account, security, usage, and billing records may be retained for as long as reasonably necessary to provide the service, detect abuse, meet accounting or legal obligations, resolve disputes, and support customer service. We aim to delete or anonymize data when it is no longer needed for those purposes.

8. User control and deletion

You control when Recon runs. You can stop using the extension at any time.

Use the popup sign-out action to clear the local signed-in session from the extension
Use the personalization controls to disable or clear locally stored writing-style profile context
Delete saved content from the extension interface when saved-content features are available
Uninstall the extension or clear extension storage in your browser to remove locally stored settings, browser installation identifiers, and any remaining local session data
Contact support if you have account, billing, session revocation, or deletion questions that require server-side action

9. Contact

If you have any questions about this Privacy Policy, contact:

support@lunacydev.com