User-Facing Privacy Guide for Subscription Payment Security - #936
Merged
Conversation
|
@Ivenkili Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Add a comprehensive, non-technical privacy guide helping users maximize payment privacy when using SYNCRO for subscription payments via Tor and stealth addresses.
What this PR adds:
A user-friendly guide covering SYNCRO's privacy features and how to use them responsibly:
Stealth addresses — How they hide your wallet identity on-chain (plain language, no cryptography jargon)
Anonymous gift card purchases — Step-by-step: using Tor, choosing no-KYC providers, avoiding tracking
Reminder timing jitter — Why randomized reminder times prevent payment pattern inference
Encrypted on-chain data — How to verify encrypted transaction memos without exposing content
Payment channels — Using SYNCRO's recurring payment feature securely (when to use, limitations)
Browser privacy hardening — Disabling WebRTC leaks, using private browsing, clearing cookies
Wallet operational security — Best practices (separate wallets for different subscriptions, not reusing addresses, avoiding linked identities)
Legal/compliance notes — Using privacy tools responsibly (not for sanctions evasion, etc.)
Closes #851