Home Arrow Icon Knowledge base Arrow Icon Global Arrow Icon How does the data storage location impact the security of user data in DeepSeek versus Make.com


How does the data storage location impact the security of user data in DeepSeek versus Make.com


The data storage location significantly impacts the security of user data in both DeepSeek and Make.com, though in different ways.

DeepSeek

DeepSeek stores user data on servers located in China, which raises several security concerns:

1. Data Sovereignty and Government Access: Under Chinese laws, such as the Personal Information Protection Law (PIPL) and the Data Security Law (DSL), the government can request access to data stored within the country for national security purposes. This means that sensitive user data, including location, browsing habits, and personal messages, could potentially be accessed by Chinese authorities without users' knowledge or consent[3][4][9].

2. Data Privacy Regulations: Since the data is stored in China, it falls outside the protections offered by regulations like the General Data Protection Regulation (GDPR) in Europe. Users cannot demand to see what information is stored about them or request its deletion, as they would under GDPR[6].

3. Security Risks: DeepSeek has faced significant security breaches due to inadequate measures, such as a misconfigured cloud storage instance that exposed over a million sensitive records. The app also employs weak encryption and has vulnerabilities like hardcoded keys and SQL injection risks[1][4][10].

Make.com

Make.com, on the other hand, employs robust security measures to protect user data:

1. Data Storage and Encryption: Make.com stores data in multiple, geographically dispersed data centers, primarily using Amazon AWS infrastructure. All data is encrypted at rest using AES 256-bit encryption, and data in transit is secured with SSL/TLS protocols[2][5].

2. Access Controls and Compliance: The platform offers strict access controls, allowing users to manage permissions and restrict access to specific IP addresses. Make.com complies with industry standards like GDPR, HIPAA, and SOC 2, ensuring regular security audits and adherence to best practices for data privacy[2][8].

3. Third-Party Integrations: Make.com vets all third-party integrations to ensure they meet its security and privacy standards, further reducing the risk of data breaches[2].

In summary, DeepSeek's data storage in China poses significant risks due to potential government access and lack of protection under international privacy laws, while Make.com's use of secure data centers and compliance with international standards provides a more robust security framework for user data.

Citations:
[1] https://securityscorecard.com/blog/a-deep-peek-at-deepseek/
[2] https://www.automationunlocked.co/blogs/is-make-com-formerly-integromat-safe
[3] https://www.securitymagazine.com/articles/101374-dangers-of-deepseeks-privacy-policy-data-risks-in-the-age-of-ai
[4] https://aldridge.com/deepseek-ai-understanding-the-security-risks/
[5] https://www.make.com/en/enterprise-security.pdf
[6] https://neontri.com/blog/deepseek-features-and-risks/
[7] https://krebsonsecurity.com/2025/02/experts-flag-security-privacy-risks-in-deepseek-ai-app/
[8] https://www.make.com/en/security
[9] https://www.zdnet.com/article/what-is-deepseek-ai-is-it-safe-heres-everything-you-need-to-know/
[10] https://www.wiz.io/blog/wiz-research-uncovers-exposed-deepseek-database-leak