Is Perplexity to obsidian - Batch Export safe?
Perplexity to obsidian - Batch Export sends export telemetry with conversation URLs, titles, client ID, and email to cf-node-api.aluo.app.
When you export Perplexity content, the extension records export actions and sends them to cf-node-api.aluo.app. The telemetry can include the conversation URL, thread title or UUID, batch counts, a persistent client ID, subscription state, and an email value stored from Perplexity or Notion account data.
Who publishes italuojack - 1 other listing from the same operator, none carrying a finding
aluojack - 1 other listing from the same operator, none carrying a finding
What this publisher told the store about itself, and the other listings that told it the same thing.
Same store account
1 other listing published from this account, 2k+ users between them, none of them carrying a finding.
Shared hosts - 1 hostname
Hostnames hardcoded in this extension that few other listings call. That can mean one operator behind both, and it can equally mean a small shared vendor, so it is context rather than a conclusion. Hosts that many listings call are left out: they are services, not connections.
AI-generated. Findings may contain errors. Those marked Verified have been manually reviewed.
Publishers can request a review.
Findings
Export telemetry sends conversation URLs and titles to cf-node-api
Using the export features in Perplexity to obsidian - Batch Export sends export telemetry to cf-node-api.aluo.app, including the Perplexity conversation URL, conversation title, a stored client ID, and an email value from extension storage.
- Severity
- Medium unwanted
- Type
- Unexpected
- CWE
- CWE-359
- Source
- Dynamic sandbox
The user starts, completes, cancels, or encounters an error during an export.
The extension sends an export log containing the conversation URL, title-related data, stored client ID, and email value to cf-node-api.aluo.app.
- Perplexity conversation URLhttps://www.perplexity.ai/search/example-thread (illustrative)
Links the export event to a specific Perplexity thread.
- Conversation titleResearch notes for project planning (illustrative)
Adds readable context about the exported Perplexity thread.
- Stored account and client dataclientId d7f3a1b2-... and user@example.com (illustrative)
Can connect the export event to a stored client ID and email value from extension storage.
Where it sends data
Destinations our analysis observed Perplexity to obsidian - Batch Export contacting. Sending data somewhere is not a finding on its own - an extension that syncs your settings has to talk to its own server - but it is where your data can go, and who else it goes to.
- cf-node-api.aluo.app
Perplexity to obsidian - Batch Export sends data to cf-node-api.aluo.app. One other extension we have analysed sends data here.