Privacy Policy — AGNURA AI Assistant

1. Scope

This policy applies to:

• Users who install AGNURA AI Assistant from the Chrome Web Store or load it in developer mode.
• Data processed on your device through the Extension popup, background service worker, and content scripts on pages you open (including mail.google.com and linkedin.com when you use optional compose features).
• Users who create or sign in to an AGNURA cloud account at https://app.agnura.com (including sync, usage dashboards, billing, and managed AI).

The Extension is a sales and outreach research tool. Local analysis still runs on the active browser tab. When you sign in, optional sync and managed AI features send data to AGNURA's cloud service as described below.

2. Information we collect and process

We group data by how it is collected. The Extension does not send routine telemetry or full browsing history to AGNURA. Local analysis data stays on your device unless you sign in and sync, use managed AI, or trigger a third-party feature (Section 5).

2.1 Data from the active tab (when you run analysis)

When you open the Extension on an http or https page, we process:

• Tab URL — full URL of the active tab (origin, path, and query string; URL fragment/hash is not used for caching).
• Page title and meta description — from the page head.
• Public page content — visible text and structure used for research signals, including detected business emails and phone numbers, platform and technology hints, sitemap and catalog hints, chat widget and marketing stack heuristics, social profile links, JSON-LD business fields when published on the page, and a plain-text page excerpt (normalized visible text, capped in length) used only if you use AI email generation.

We do not collect passwords, payment card data, or content from pages you never analyze with the Extension.

2.2 Same-origin fetches initiated by the Extension

To find contacts and site metadata, the Extension may request public resources on the same website you are analyzing, for example sitemap files, common contact or about paths, optional same-origin product or catalog JSON endpoints when exposed, and optional Internet Archive (web.archive.org) CDX data for an approximate earliest capture hint for the hostname. These requests use credentials: "omit" where applicable. They go to the target site or Archive.org, not to AGNURA.

2.3 Data you provide in Settings

Stored locally in Chrome extension storage (chrome.storage.local) on your device:

• AGNURA account session (when signed in), credit usage metadata
• Email templates (name, subject, body)
• Prompts — email template prompt, Gmail reply prompt, LinkedIn reply prompt, LinkedIn rewrite prompt
• Knowledge base text (optional, used with some AI features)
• Gmail compose helpers — account index, default From address, meeting link
• Add Lead webhook URL (optional) — the HTTPS endpoint you configure for lead export (for example your own n8n, Zapier, or custom automation URL)
• Cached analysis results (approximately one hour per normalized tab URL)
• Cached sitemap counts (approximately one hour per origin)
• Apollo company rows after you initiate a scrape on Apollo.io
• AI email drafts saved per URL (when you use that feature)

2.4 Gmail (optional features on mail.google.com)

When you use optional Gmail compose enhancements, we process compose field content you paste or edit (for example original email text for Generate Reply) and settings you saved (From address preference, meeting link). The Extension does not use the Gmail API, does not read your inbox automatically, and does not send email without you confirming in Gmail.

2.5 LinkedIn (optional features on linkedin.com)

When you use Write Reply, Rewrite Message, or Voice to Text on classic LinkedIn Messaging or on LinkedIn Sales Navigator inbox (`linkedin.com/sales/…`), we process recipient profile or thread-header fields visible on the page, conversation thread text when loaded for reply generation, and draft message text you edit in the modal or compose box. Features run only on LinkedIn pages you have open and only when you click the relevant control. Sales Navigator uses a separate content script from classic messaging; it does not auto-send InMail or messages.

2.6 Apollo.io (optional capture)

When you click Get Apollo Data on an Apollo.io tab, we process visible table rows in the company list (for example company name, website, LinkedIn URL, employees, industries, keywords, location, score). Data is stored locally until you export CSV or clear extension storage. It is not uploaded to AGNURA by default.

2.7 AGNURA cloud account (app.agnura.com)

When you create an account or sign in (email/password or Google OAuth), we process:

• Account identifiers — email, display name, optional avatar URL, Google subject id when you use Google sign-in, and authentication tokens needed to keep you signed in.
• Synced settings — prompts, email templates, and non-secret general settings you choose to sync from the Extension (API keys and payment card numbers are not stored in AGNURA sync).
• Managed AI requests — when you use Extension AI features while signed in, prompts and feature context are sent to POST /api/ai-complete on our app so we can run the model, deduct credits, and return a draft.
• Usage and credits — credit balances and lots, AI generation metadata (feature key, token counts, credit cost). If an administrator enables prompt/response logging, we may store request and response text for a limited retention period (see Section 4).
• Billing identifiers — Stripe customer and subscription ids, subscription status, and current period end. Card numbers are processed by Stripe and are not stored by AGNURA.

You can use local research features without a cloud account. Managed AI credits and sync require an account.

3. How we use information

We use the information above to:

• Display website research in the Extension popup.
• Cache results locally so you can reopen the popup on the same URL without re-scanning (for about one hour).
• Pre-fill outreach workflows — email templates, Gmail compose URLs, and JSON/CSV export.
• Generate AI-assisted drafts when you click AI features (via AGNURA managed AI / OpenRouter, or a provider you configure where still offered).
• Operate your AGNURA account — authentication, settings sync, usage dashboards, free and paid AI credits, and subscription billing.
• Export leads when you click Add Lead on eligible sites (see Section 5).
• Improve reliability of on-device features (for example parsing contacts from large HTML pages).

We do not use Extension data for advertising profiles, and we do not sell personal data.

4. How we store information

Uninstalling the Extension removes data stored in extension storage. It does not automatically delete your AGNURA cloud account. Data already sent to third parties (OpenRouter/AI providers, Stripe, your webhook) is governed by those parties' policies and your account settings. Page analysis caches and Apollo rows stay local unless you choose to export them elsewhere.

5. How we share information

We do not sell personal data. We share data only in these situations:

5.1 Third parties you invoke

OpenRouter and downstream model providers process prompts under their policies. Stripe processes payments under Stripe's privacy policy. Hosting for app.agnura.com is on infrastructure we operate or control.

5.2 Legal and safety

We may disclose information if required by law, court order, or to protect rights, safety, and security, to the extent applicable to AGNURA as the Extension and cloud service provider.

5.3 What is not shared automatically

We do not sell personal data. We do not upload full browsing history. Local page analysis caches and Apollo rows stay on your device unless you export them. Add Lead only runs when you click it. Managed AI and sync only run when you are signed in and use those features.

6. Permissions and why they are needed

• activeTab — Act on the tab you are viewing when you open the Extension.
• tabs — Read active tab URL and id to run analysis and return results to the popup.
• scripting — Inject the analysis script on demand when you run analysis, and inject Apollo scrape when you request it.
• storage — Save cache, templates, settings, and Apollo data locally.
• Host access (<all_urls>) — Fetch public sitemaps and contact pages on sites you analyze.
• Host access (https://app.agnura.com/* and related API hosts) — Sign in, sync, and call managed AI when you use cloud features.
• Content scripts on Gmail and LinkedIn — Optional compose and messaging helpers described above.

Broad host access is used so you can analyze customer domains without a fixed allowlist. Analysis and fetches run in connection with your use of the Extension, not as silent background monitoring of all tabs.

7. AI processing

Managed AI features send prompts and context to AGNURA's cloud API, which calls OpenRouter (or another configured model provider) to generate email or message drafts. Outputs are probabilistic and may be inaccurate. You must review all generated content before sending. You are responsible for compliance with applicable laws, email and messaging regulations, and third-party terms (including Google, LinkedIn, WhatsApp, Reddit, Stripe, and AI providers). AI usage consumes credits associated with your AGNURA account. See our Terms of Service and Refund & Billing Policy.

8. Security

We design the Extension to:

• Transmit third-party API calls over HTTPS (TLS).
• Store sensitive settings locally in Chrome extension storage on your profile.
• Omit credentials on same-origin contact fetches where configured.

No method of transmission or local storage is completely secure. Protect your device, Chrome profile, and AGNURA account credentials.

9. Your choices and rights

You can:

• Avoid managed AI — Do not use AI buttons, or stop when you have no credits remaining.
• Manage billing — Cancel or update payment methods via the Stripe Customer Portal linked from app.agnura.com/billing.
• Avoid Add Lead — Do not click Add Lead, or leave the webhook URL blank in Settings; no analysis JSON is sent to a webhook.
• Clear cached data — Use the popup reload control to bypass the analysis cache, or remove extension storage in Chrome settings.
• Remove Extension data — Uninstall the Extension from chrome://extensions.
• Cloud account requests — Email us to request access, correction, or deletion of account data we hold on app.agnura.com (Section 14).
• Export data — Copy or download analysis JSON or Apollo CSV to locations you control; view usage in the app dashboard.

Depending on your location, you may have privacy rights (access, deletion, correction, objection, portability). Contact us (Section 14) for requests relating to data AGNURA processes directly (account, billing identifiers, synced settings, AI logs, and support emails).

10. International transfers

If you use AGNURA cloud, OpenRouter or other AI providers, Stripe, Internet Archive, or other third-party services, data may be processed in countries other than yours. Those providers' terms and safeguards apply.

11. Children's privacy

The Extension is intended for business and professional use. It is not directed to children under 13 (or the applicable age in your jurisdiction). We do not knowingly collect personal data from children through the Extension.

12. Changes to this policy

We may update this policy to reflect product, legal, or operational changes. We will post the updated version on this page and revise the effective date. Continued use after changes constitutes acceptance of the updated policy where permitted by law. For material changes, we may provide additional notice (for example in Extension release notes or the Chrome Web Store listing).

13. Chrome Web Store

This Extension is distributed via the Chrome Web Store. Google's terms and policies also apply to installation and updates. The privacy policy URL listed on our store listing points to this document.

14. Contact

For privacy questions, account deletion requests, or billing-related privacy requests about AGNURA AI Assistant or app.agnura.com, email hello@agnura.com or use the contact channel on this website or on the Chrome Web Store listing.