Privacy Policy — Perplexity to Obsidian

Last updated: September 20, 2026

This Privacy Policy explains how Perplexity to Obsidian (the “Extension”) handles information when you install or use the Chrome extension published by lite app. This policy applies to the Extension and its supporting subscription and diagnostic services. It does not replace the privacy policies of Perplexity, Google Chrome, Chrome Web Store, Paddle, or any other service that you use with the Extension.

1. What the Extension does

Perplexity to Obsidian converts content from your Perplexity account into Markdown files that are compatible with Obsidian. Depending on the workflow you choose, the Extension can:

• export the current Perplexity conversation;
• export conversations from open Perplexity tabs;
• export selected questions and answers to Markdown or the clipboard;
• preview and select content before exporting;
• export regular conversation history in bulk;
• export supported Perplexity Computer Tasks;
• export conversations from selected Perplexity Spaces;
• include sources, related questions, YAML frontmatter, uploaded files, generated images, and other supported assets; and
• skip records that have already been exported or export them again after they change.

The Extension does not write directly to an Obsidian vault and does not use the Obsidian API. It creates Markdown and asset files through Chrome Downloads. You can configure Chrome’s download location so that the downloaded files can later be moved into, or downloaded directly to, an Obsidian vault.

2. Information the Extension can access

The Extension accesses information only when required for a feature that you use or for the Extension’s initialization, subscription, reliability, and usage functions.

2.1 Perplexity account and page information

When a Perplexity page is open, the Extension may access:

• the current Perplexity page URL, page title, conversation UUID, and supported page type;
• the Perplexity user object returned by the signed-in Perplexity session, which may include the account email and account identifiers;
• the active Perplexity account identifier exposed by the Perplexity page’s local or session storage;
• conversation lists, titles, UUIDs, slugs, timestamps, status, mode, query counts, and Space information;
• conversation entries, including your prompts, Perplexity answers, Markdown blocks, sources, related questions, citations, metadata, and supported content blocks;
• uploaded or returned files, generated images, document-style content, and other assets that are part of a conversation; and
• information about open tabs when you use the open-tabs export workflow.

The Extension does not use the Chrome Cookies API and does not read raw cookie values. Requests to Perplexity may include the browser’s existing Perplexity session credentials so that Perplexity can authorize requests for your account. Those credentials are handled by the browser and Perplexity; the Extension does not send them to the Extension developer’s logging or subscription endpoints.

2.2 Exported content

If you start an export, the Extension may process the content that you selected or that is required by the selected export scope. This can include:

• questions and answers;
• conversation titles, dates, URLs, UUIDs, and other identifiers;
• sources, citations, related questions, and links;
• Space or project names;
• YAML frontmatter and export metadata;
• user-uploaded or Perplexity-generated attachments, images, and files; and
• content that is embedded in supported Perplexity document or asset blocks.

The Extension converts this information in the browser and saves the resulting Markdown and asset files through Chrome Downloads. The current Extension source does not upload the full conversation or generated Markdown file to an Extension developer server for storage or AI training.

The downloaded files are controlled by you. The Extension does not automatically delete files that have already been downloaded or moved into an Obsidian vault.

2.3 Local and synced Extension data

The Extension stores configuration and operational information in Chrome storage. Depending on the value, this can include:

• save path, filename preferences, YAML/source/attachment settings, Space-folder settings, and export delays;
• exported conversation identifiers and last-export timestamps used by skip logic;
• up to 50 recent export-history entries;
• up to 200 local export-failure entries, which can contain a conversation title, UUID, URL, attachment filename, error type, and error message;
• saved custom-preview records, which can include the selected conversation detail and preview configuration;
• cached Perplexity user information and active-account identifiers;
• subscription status, plan, last-check time, and the email used for activation;
• a randomly generated client identifier used to associate diagnostic events; and
• export counters, daily counters, subscription flags, and other Extension settings.

Some settings and identifiers are stored with chrome.storage.local. Some identifiers, email values, subscription flags, client identifiers, and export counters are stored with chrome.storage.sync. Chrome Sync behavior is controlled by your Chrome profile and Google’s services. Do not place sensitive conversation content in a setting or field unless you understand that it may be stored in Chrome storage.

3. How information is used

Information is used for the following purposes:

Information	Purpose	Where it is processed
Perplexity page, account, conversation, and asset data	Read the records you request and convert them to Markdown and downloadable assets	Your browser and Perplexity’s services
Export settings, identifiers, history, and failure records	Remember your preferences, skip unchanged records, show progress, and troubleshoot export failures	Chrome storage on your device and, for synced values, Chrome Sync
Email and subscription state	Check whether your account is eligible for the free or subscribed batch-export limit	The Extension and the subscription services described below
Client ID, event name, counters, URL, title/identifier, and error details	Understand feature use, detect failures, and improve reliability	The diagnostic service described below
Downloaded Markdown, images, and attachments	Provide the export result you requested	Your configured Chrome Downloads location

The Extension does not use exported conversation content to train a general-purpose AI model.

4. Information sent outside the browser

The Extension has two different categories of network activity. They should not be confused.

4.1 Requests to Perplexity

To retrieve data that you request, the Extension sends requests to Perplexity endpoints such as the signed-in session endpoint, conversation-list endpoint, thread-detail endpoint, and file-repository download endpoint. These requests can contain the conversation UUID, pagination parameters, the active Perplexity account header, and the browser’s existing Perplexity session credentials. Perplexity processes these requests under its own terms and privacy policy.

4.2 Subscription verification

When the Extension checks subscription status, it may send the email entered or discovered from the Perplexity session to product services operated under the *.aluo.app domain. Depending on the subscription state, the request may also include the product source or product name.

These requests are used to determine whether the free batch limit or subscribed batch behavior applies. The Extension does not send the full conversation body, the generated Markdown file, or your downloaded attachments as part of the subscription check.

4.3 Diagnostic and usage events

The Extension may send diagnostic and usage events to product services operated under the *.aluo.app domain.

The event can include:

• a randomly generated client identifier;
• the email available from the subscription or Perplexity account state;
• the event name, such as installation, export completion, export failure, or limit-related events;
• the product name and subscription state;
• the current page or conversation URL;
• export counters;
• the event time and browser language; and
• event-specific data such as export counts, titles, filenames, conversation identifiers, or error details.

The Extension’s current logging code does not intentionally send the complete answer body or complete Markdown output in these events. However, URLs, titles, UUIDs, filenames, and error messages can identify a conversation or may reveal information that you included in a title. Treat these events as potentially personal data rather than anonymous analytics.

The Extension does not currently provide a separate in-product analytics opt-out switch. You can stop future Extension activity by disabling or uninstalling the Extension. Events already sent before disabling may remain in the diagnostic service until they are deleted under the service’s operational retention process.

5. Chrome permissions and host access

The Extension requests the following Chrome permissions:

Permission or host access	Why it is needed
storage	Save configuration, export markers, local history, failure records, cached account/subscription values, and selected synced values.
tabs	Find supported Perplexity tabs and send export requests to the content script when you use open-tab or batch workflows.
downloads	Save Markdown files, images, and attachments to the Chrome Downloads location you configure.
https://www.perplexity.ai/* and https://perplexity.ai/*	Run the export content script on Perplexity pages and retrieve the Perplexity records and assets you request.
https://*.aluo.app/*	Contact product subscription, payment-status, and diagnostic endpoints.
https://*.chatgpt2notion.com/*	Open the product documentation and installation/help pages. The Extension does not use this host to upload your conversation files.

The Extension does not request the Chrome cookies, history, webRequest, identity, or scripting permissions. It does not read your general browsing history or the contents of unrelated websites.

6. Storage and retention

6.1 Data stored in Chrome

Configuration, export markers, history, failure records, cached account information, subscription cache, and custom previews remain in Chrome storage until they are cleared by the Extension, cleared by you, removed during an uninstall, or overwritten as part of the Extension’s normal limits. Export history is capped at 50 entries and failure records are capped at 200 entries, but an entry can remain until it is removed or displaced by a newer entry.

Clearing the Extension’s export cache removes export markers. It does not delete Markdown files, images, attachments, or existing export-history and failure records unless you use the corresponding clear action. Uninstalling the Extension may remove its Chrome storage, but it does not remove files already saved in your Downloads folder or Obsidian vault.

6.2 Subscription and diagnostic services

Subscription and diagnostic records are retained by the respective product services for as long as reasonably necessary to provide subscription verification, prevent abuse, troubleshoot reliability, maintain accounting or operational records, comply with legal obligations, and resolve disputes. Retention can vary by record type and service. We do not use diagnostic events as a repository for your exported conversation content.

Payment details, if you purchase a subscription, are handled by the payment provider. The Extension does not request or store your full card number, card security code, or bank account password.

6.3 Perplexity and downloaded files

Perplexity controls retention of data in your Perplexity account and Perplexity services. Chrome controls the Downloads location and Chrome Sync data. You control downloaded Markdown, images, attachments, and any files copied into an Obsidian vault. Deleting an account or uninstalling this Extension does not automatically delete those third-party or local copies.

7. Your choices and deletion requests

You can control the Extension’s local data by:

1. using the Extension’s clear-cache, clear-history, clear-failures, or related settings where available;
2. removing saved subscription or email information in the Extension settings where available;
3. clearing the Extension’s site data or Chrome storage through Chrome settings;
4. disabling or uninstalling the Extension; and
5. deleting downloaded Markdown, images, attachments, and exported folders from your Downloads location or Obsidian vault.

To request deletion of personal information held by the product services, contact [email protected]. Please identify the Extension as Perplexity to Obsidian and describe the information you want deleted. We may request enough information to verify the request and may retain information that must be kept for legal, security, accounting, fraud-prevention, or dispute-resolution purposes.

A deletion request to us cannot delete data held by Perplexity, Google/Chrome, Paddle, or other independent providers. You must use those providers’ own privacy or account controls for their copies. It also cannot delete files already downloaded to your computer or copied to an Obsidian vault; those files are under your control.

8. Security

The Extension uses HTTPS for its product-service requests and relies on Chrome’s storage and extension security model. No method of transmission or storage is completely secure. You should keep Chrome updated, protect your Perplexity account, review the download folder and exported files, and avoid sharing exported files or exported-storage JSON files without checking them for private content.

9. Children’s privacy

The Extension is not directed to children under 13, and we do not knowingly design it to collect personal information from children under 13. If you believe a child provided personal information to the product services, contact us at [email protected].

10. International processing and third-party policies

Product subscription and diagnostic services may be hosted or processed in countries other than your own. By using the Extension’s subscription or diagnostic features, you understand that the limited information described in this policy may be transferred to those services. Perplexity, Google/Chrome, Chrome Web Store, and payment providers process information under their own policies and terms. Review those policies before using the corresponding service.

This policy does not make the Extension responsible for the privacy practices, security, retention, or deletion controls of Perplexity, Google, Chrome, Paddle, or any other independent provider.

11. Changes to this policy

We may update this policy when the Extension’s data practices, services, or legal obligations change. The “Last updated” date at the top of this page will change when a new version is published. If a change materially changes how the Extension handles personal data, we will take reasonable steps to provide notice through the Extension, the product website, or another appropriate channel.

12. Contact

The data controller for the product services is lite app.

For privacy questions, access or deletion requests, or questions about this Extension’s data handling, contact:

Email: [email protected]

When contacting us, use the subject line “Perplexity to Obsidian Privacy Request” and include only the information needed to identify your request. Do not email your Perplexity password, session cookies, payment-card details, or a complete exported conversation unless we specifically request a redacted example for support.