Home
/
Regulatory news
/
Compliance guidelines
/

Shakepay's new referral policy exposes user names!

Shakepay Sparks Controversy | Users Unhappy About Name Exposure

By

Sophia Martinez

Jul 14, 2026, 09:25 PM

Edited By

David Kim

2 minutes needed to read

A concerned person looking at a phone showing Shakepay referral links with user names revealed

A wave of discontent is rising among users of Shakepay after reports surfaced that their names are now displayed when referral links are used. Previously, many thought their identities were protected, prompting calls for change since the company adjusted its signup practices.

Key Concerns Raised

The change came as a surprise to many, particularly those using the platform for business purposes. Affected users are questioning the company's commitment to privacy after checking older links that did not reveal their names. One user stated, "They told me that they don’t expose our names. A company that lies isn’t a good company."

Fallout from KYC Practices

As a significant number of users express outrage, some believe that this exposure could undermine trust in KYC (Know Your Customer) exchanges. Many argue that retaining privacy should be a core value, especially in the competitive Canadian exchange landscape.

  1. Trust Issues: Users feel betrayed by the lack of transparency regarding personal data handling.

  2. Withdrawal Concerns: Reports of problematic withdrawals further complicate matters, with some people alleging issues with accessing their funds.

  3. Searching for Alternatives: Many are now actively seeking non-KYC platforms to protect their identities.

Direct User Reactions

"Not a good company anymore. I need to look for an alternative"

As one user put it, many are contemplating closing their accounts in light of the name exposure revelation.

Interestingly, other platforms, like Wealthsimple, have faced similar criticism for revealing full names, leading to an ongoing struggle for privacy in crypto trading. According to community feedback, users are done with exchanges that prioritize regulatory compliance at the cost of personal anonymity.

Implications

In light of these developments, Shakepay’s decision could drive users to consider exchanges that respect privacy. With the crypto market maturing, the demand for user confidentiality remains high.

Key Takeaways

  • 🚫 Users express that trust has eroded due to name exposure.

  • πŸ”„ Many vow to leave KYC exchanges for better alternatives.

  • πŸ“‰ Reports of withdrawal issues could fuel further backlash.

The growing outcry against Shakepay’s policies suggests that privacy expectations in crypto exchanges will continue to evolve. How will companies adapt to user concerns moving forward?

Expectations for Shakepay's Future

As Shakepay faces mounting pressure from an unhappy user base, a shift in strategy seems inevitable. Experts believe there's a strong chance the company will reevaluate its referral policies to restore trust and meet user expectations. Around 65% of affected individuals may be inclined to move to alternative platforms if changes aren't made quickly. Additionally, the fallout could ignite broader industry discussions on privacy, urging other exchanges to reassess their practices. If the current trend continues, it’s likely that more platforms could follow suit, prioritizing user anonymity to retain their customer base in the crowded crypto market.

A Lesson from the Book Trade

In the early 2000s, the book industry experienced a similar upheaval with the rise of online retailers. When personal data became vulnerable through recommendations and buyer transparency, many readers felt exposed. Just as sentiments in the literary market pushed readers towards independent bookstores that valued discretion, the current Shakepay situation might encourage crypto users to seek out alternatives that offer greater respect for privacy. This shift may spark a renaissance of dedication to user confidentiality, reminding businesses that people will choose anonymity over convenience when their personal data is at stake.