Privacy notice · August 3, 2026
This notice follows the current source code’s actual data flow: sign-in, local storage, sync, page checks, AI, SEO, billing, and deletion.
LinkJuice signs you in with a Google or GitHub account and keeps and refreshes the session locally in the extension; it requests no GitHub repository access. Site profiles, backlink targets, submissions, drafts, images, and preferences are stored in browser storage isolated by signed-in account. Export files contain only site profiles and business records. They never contain session tokens, identity bindings, plans, quotas, or sync internals.
When sync is enabled, site profiles, current-site selection, preferences, domain blacklist, targets, submissions, drafts, images and their metadata, modification times, and deletion records are sent to LinkJuice’s cloud service. Data is isolated by signed-in account and encrypted in transit, and LinkJuice can process synced data on the server.
The extension reads only the active tab URL. On the first Side Panel read, domain backlink check, or cross-origin logo fetch, Chrome asks once for optional access to HTTP and HTTPS websites; after approval it does not prompt for each site. This grant is never used for background scanning: only an explicit action lets LinkJuice read the current page’s public title, summary, relevant text, discussion, form structure, and robots directives, or fetch a logo. When you explicitly run a domain backlink check, your browser requests robots.txt, sitemaps, and a bounded set of same-domain public pages; the target site receives the usual IP address and request metadata. Private-network, localhost, and intranet pages are not sent to AI or server-side SEO services.
Only after you click Generate does AI generation send selected site facts, generation settings, and the public page URL, title, summary, relevant excerpt, and discussion excerpt to LinkJuice’s cloud service and then an AI provider. Clicking AI Fill first sends the public page URL, title, language, selected profile field names, and sanitized labels and control types for uncertain empty fields. If visible controls remain uncertain, the same action may send a local crop containing at most eight relevant empty controls to LinkJuice’s cloud service and then through OpenRouter to a Google vision model. Before transport, the extension masks existing inputs, passwords, payment fields, and other sensitive controls and limits the crop to 1400×1000 CSS pixels and a 1.5 MiB JPEG; it is not retained as an asset or sync record. LinkJuice sends no raw form values, HTML, cookies, browsing history, file contents, or other-tab data, and does not overwrite existing values or click Next, Publish, or Submit. AI may return only requested closed field semantics and confidence. LinkJuice does not separately retain prompts, screenshot crops, or raw model responses from this request; the provider may still process them under its own terms. Drafts or comments you choose to save become synced business records.
Only after you click Analyze SEO is a public target domain sent to LinkJuice’s cloud service and then to DataForSEO for domain and organic-search metrics and Ahrefs for domain strength. Only after you click Verify All are the selected public source domains and destination pages sent in a batch to DataForSEO for backlink discovery. Saving, importing, changing submission status, individual checks, and background jobs do not call a backlink-data provider. The service temporarily caches public metrics, source labels, and lookup time and records monthly SEO and backlink-discovery usage. Form values, images, cookies, and browsing history are not sent.
LinkJuice stores your plan, monthly AI, SEO, and backlink-discovery usage, storage usage, and subscription state. New checkout sends the selected plan, interval, account identifier, and email to Creem. Payment credentials are entered at Creem checkout; LinkJuice does not receive card numbers. LinkJuice retains only the customer, subscription, order, and payment-event identifiers needed for subscription management, reconciliation, and fraud prevention.
Clear local data affects only the active user. Deleting cloud data removes synced business records and images and writes a persistent local ‘sync disabled’ marker. Every device is blocked from uploading until you explicitly re-enable sync. Necessary deletion records sync across devices to prevent deleted content from reappearing. Deleting cloud business data does not automatically delete the sign-in account, usage, plan, or payment records that must be kept for legal or accounting reasons. Contact support to access, correct, or request deletion of account data.
We do not sell backlink lists, turn private targets into a searchable database, read pages for advertising, or click Submit, Publish, Next, terms acceptance, or marketing consent for you. The extension does not request cookies, browsing history, or clipboard-read permission; Downloads access is requested only when you add or capture an asset, explicitly save existing assets locally, or export or reveal an asset.
Use of information received from Google APIs will adhere to the Chrome Web Store User Data Policy, including the Limited Use requirements. Such data is used only to provide or improve the user-facing LinkJuice features you explicitly use.
Contact us if you want to access, export, or delete data associated with your account.
hello@linkjuice.dev