Skip to content

[Feature Request] <Brief description> #305

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
rnaimi opened this issue May 6, 2025 · 0 comments
Open

[Feature Request] <Brief description> #305

rnaimi opened this issue May 6, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@rnaimi
Copy link

rnaimi commented May 6, 2025

🚀 Feature Request

The data returned from calling the API should match the same privacy and masking policies applied to it as it does if the query is performed on the app or on the website.

🔍 Problem Statement

The data returned from API/curl today is masked for sensitive information such as name, email, some URL's (LinkedIn), etc. The same query on the web or app returns unmasked data. This presents a problem for automating tasks via API which it's suppose to solve.

💡 Proposed Solution

Implement the same masking policy for both web and app and API data returned.

📌 API Impact

  • Which API component is affected? Returned data from all API endpoints as far as I can tell
  • Is this related to a specific model? All models
  • Would this require new API parameters or changes to existing ones? hopefully not

🔄 Alternatives Considered

Alternative is to scrape the perplexity web interface and look for returned data that is unmasked. It's not ideal and counter intuitive to using API.

📎 Additional Context

none


📧 For direct inquiries, please reach out to api@perplexity.ai

@rnaimi rnaimi added the enhancement New feature or request label May 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant