aboutsummaryrefslogtreecommitdiff
path: root/content/blog/2022-08-31-privacy-com-changes.org
diff options
context:
space:
mode:
Diffstat (limited to 'content/blog/2022-08-31-privacy-com-changes.org')
-rw-r--r--content/blog/2022-08-31-privacy-com-changes.org4
1 files changed, 2 insertions, 2 deletions
diff --git a/content/blog/2022-08-31-privacy-com-changes.org b/content/blog/2022-08-31-privacy-com-changes.org
index 73967df..9a558d0 100644
--- a/content/blog/2022-08-31-privacy-com-changes.org
+++ b/content/blog/2022-08-31-privacy-com-changes.org
@@ -1,5 +1,5 @@
#+date: <2022-08-31 Wed 00:00:00>
-#+title: Analysis of Recent Privacy.com Terms and User Impact
+#+title: Privacy.com Shifts From Prepaid Debit to Charge Card: What Users Need to Know
#+description: Detailed examination of modifications to Privacy.com service terms and their implications on user privacy and payment security protocols.
#+slug: privacy-com-changes
#+filetags: :privacy:finance:terms_changes:
@@ -27,7 +27,7 @@ card").
I have used Privacy.com for 1-2 years, and the process was always that
you would create a single-use or merchant-locked card. This card could
be used for any dollar limit you set and would immediately draw the
-funds from whatever funding source you connected, e.g. PayPal account or
+funds from whatever funding source you connected, e.g. PayPal account or
a bank account.
The benefit this service provides with a premium account is masking the