run-llama/llama_cloud_services
1
0
Fork 0
mirror of https://github.com/run-llama/llama_cloud_services.git synced 2026-08-26 16:56:36 -04:00
Code Issues 352 Packages Projects Releases 10 Wiki Activity

No mention of privacy #119

New Issue
Open
opened 2026-02-16 00:16:55 -05:00 by yindo · 7 comments
yindo commented 2026-02-16 00:16:55 -05:00
Owner
Copy Link
Copy Source

Originally created by @joeyfortuna on GitHub (May 19, 2024).

Please add documentation about how calls to the API are treated.
Are they stored and used for training?
Are they otherwise saved?
This service looks very promising but without that clarification, we can't endorse using it for business.

Thanks!

Originally created by @joeyfortuna on GitHub (May 19, 2024). Please add documentation about how calls to the API are treated. Are they stored and used for training? Are they otherwise saved? This service looks very promising but without that clarification, we can't endorse using it for business. Thanks!
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@lukebelbina commented on GitHub (May 22, 2024):

Agreed, I'd like to use this for a business use case but the documents are not to be shared or used for training

@lukebelbina commented on GitHub (May 22, 2024): Agreed, I'd like to use this for a business use case but the documents are not to be shared or used for training
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@etiennerev1222 commented on GitHub (May 26, 2024):

Please answer, it's an important topic

@etiennerev1222 commented on GitHub (May 26, 2024): Please answer, it's an important topic
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@spreeni commented on GitHub (Sep 18, 2024):

Agreeing that this is a very important point that will hinder adaption within projects.

It would also be nice to be transparent or to chose in which region to process documents. This is relevant for the european GDPR, where sensitive data should not leave EU servers.

@spreeni commented on GitHub (Sep 18, 2024): Agreeing that this is a very important point that will hinder adaption within projects. It would also be nice to be transparent or to chose in which region to process documents. This is relevant for the european GDPR, where sensitive data should not leave EU servers.
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@spreeni commented on GitHub (Sep 18, 2024):

Also further transparency about which third-party services (and in which regions) are used would be nice.

@spreeni commented on GitHub (Sep 18, 2024): Also further transparency about which third-party services (and in which regions) are used would be nice.
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@marco-bertelli commented on GitHub (Nov 21, 2024):

Same Situation Here, the tool is awesome but unless we have GDPR info i can't use it with my team for production EU projects

@marco-bertelli commented on GitHub (Nov 21, 2024): Same Situation Here, the tool is awesome but unless we have GDPR info i can't use it with my team for production EU projects
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@neuralnoy commented on GitHub (Nov 26, 2024):

Have the same issue here. Is there any news on this?

@neuralnoy commented on GitHub (Nov 26, 2024): Have the same issue here. Is there any news on this?
yindo commented 2026-02-16 00:16:56 -05:00
Author
Owner
Copy Link
Copy Source

@jdeepwell commented on GitHub (Nov 27, 2024):

When I read about the cooperation with Microsoft/Azure

Announcing the LlamaIndex integration with Azure AI

I was hoping that there might be a way to run LlamaParse on Azure instances in the EU – but it does not seam so…

As long as there is no clear declaration in regards to GDPR, LlamaParse is basically unusable in Europe 😥

@jdeepwell commented on GitHub (Nov 27, 2024): When I read about the cooperation with Microsoft/Azure > [Announcing the LlamaIndex integration with Azure AI](https://www.llamaindex.ai/blog/announcing-the-llamaindex-integration-with-azure-ai?utm_source=drip&utm_medium=email&utm_campaign=LlamaIndex+Newsletter+2024-11-26) I was hoping that there might be a way to run LlamaParse on Azure instances in the EU – but it does not seam so… As long as there is no clear declaration in regards to GDPR, LlamaParse is basically unusable in Europe 😥
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
LlamaCloud
LlamaExtract
LlamaParse
bug
client
complex layout
documentation
duplicate
enhancement
figure
font
header footer
help wanted
ocr
parser
pdf_debug
pdf_debug
pull-request
Mirrored from GitHub Pull Request
 python-lib
question
server_issue
server_issue
ui
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: run-llama/llama_cloud_services#119
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?