The encryption methods used by DeepSeek and Make.com have significant implications for data privacy, highlighting stark differences in how each platform approaches security.
DeepSeek's Encryption Methods
DeepSeek's encryption methods have been criticized for being insecure and ineffective. The app uses 3DES (Triple DES), a symmetric encryption algorithm that is considered outdated and vulnerable to attacks[1][4][7]. Additionally, DeepSeek employs hardcoded encryption keys, which can be easily extracted from the app itself, further compromising data security[1][4][10]. The app also reuses initialization vectors (IVs) and uses NIL for the IV, which are practices that violate best security standards[1][4].
Moreover, DeepSeek transmits sensitive data without encryption over the internet, disabling App Transport Security (ATS), an iOS feature designed to prevent such unencrypted data transfers[7][10]. This exposes user data to interception and manipulation by malicious actors. The data is sent to servers managed by ByteDance, raising concerns about data sovereignty and potential access by Chinese authorities[4][7].
DeepSeek's aggressive data collection practices, including keystroke patterns and device data, are also transmitted to Chinese servers, which may be subject to foreign data regulations[3][4]. This lack of transparency and control over data handling poses significant risks to users, particularly in terms of privacy and compliance with international data protection standards.
Make.com's Encryption Methods
In contrast, Make.com (formerly Integromat) employs robust encryption methods to protect user data. The platform uses AES 256-bit encryption for data at rest, ensuring that all stored data is securely encrypted[2][5]. Additionally, Make.com utilizes SSL/TLS protocols to encrypt data in transit, safeguarding information as it moves between applications[2][5].
Make.com also implements full-disk encryption with AES-256 for all services and uses the AWS Key Management Service (KMS) to manage cryptographic keys securely[5]. This comprehensive approach to encryption ensures that user data is protected both in storage and during transmission.
Furthermore, Make.com adheres to strict access controls, allowing users to manage permissions and restrict access to specific IP addresses, which helps prevent unauthorized data access[2]. The platform complies with major industry standards such as GDPR, HIPAA, and SOC 2, ensuring that it maintains high levels of security and privacy[2].
Comparison of Implications for Data Privacy
The implications for data privacy are starkly different between DeepSeek and Make.com:
- Security Risks: DeepSeek's weak encryption methods and unencrypted data transmission expose users to significant security risks, including data interception and manipulation. In contrast, Make.com's robust encryption practices minimize such risks.
- Data Sovereignty: DeepSeek's data storage in China raises concerns about data sovereignty and potential government access, whereas Make.com stores data in geographically dispersed data centers, reducing such risks.
- Privacy Controls: DeepSeek lacks controls over data retention and sharing, while Make.com offers features like access controls and compliance with international privacy standards, giving users more control over their data.
In summary, DeepSeek's encryption methods pose serious risks to data privacy due to weak encryption, unencrypted data transmission, and aggressive data collection practices. In contrast, Make.com's robust encryption and compliance with industry standards provide a much safer environment for user data.
Citations:
[1] https://www.nowsecure.com/blog/2025/02/06/nowsecure-uncovers-multiple-security-and-privacy-flaws-in-deepseek-ios-mobile-app/
[2] https://www.automationunlocked.co/blogs/is-make-com-formerly-integromat-safe
[3] https://www.linkedin.com/pulse/ai-terms-service-exposed-how-deepseek-other-platforms-mitch-jackson-upujc
[4] https://www.linkedin.com/pulse/warning-deepseek-transmits-unencrypted-data-bytedance-pwk9e
[5] https://www.make.com/en/enterprise-security.pdf
[6] https://blogs.cisco.com/security/evaluating-security-risk-in-deepseek-and-other-frontier-reasoning-models
[7] https://thehackernews.com/2025/02/deepseek-app-transmits-sensitive-user.html
[8] https://www.make.com/en/help/app/encryptor
[9] https://securityscorecard.com/blog/a-deep-peek-at-deepseek/
[10] https://krebsonsecurity.com/2025/02/experts-flag-security-privacy-risks-in-deepseek-ai-app/