data.coop/membersystem
7
2
Fork 4
Code Issues 14 Pull requests 1 Releases Wiki Activity

Privacy-shield for member's emails when paying with Stripe or other 3rd parties? #43

New issue
Open
opened 2024-08-04 09:43:24 +00:00 by decibyte · 7 comments
decibyte commented 2024-08-04 09:43:24 +00:00
Owner
Copy link
No description provided.
Screenshot_20240804-114233.png
154 KiB
Screenshot_20240804-114233.png
benjaoming commented 2024-08-04 10:01:31 +00:00
Owner
Copy link

It's a feature: If we shared people's email address with Stripe, we would need a privacy policy that stated this + a checkbox to agree because 1) an email is PII, 2) people cannot reasonably assume that we share their email if they click a button that says "Pay".

Many people also sign up with username+datacoop@provider.tld

It's a feature: If we shared people's email address with Stripe, we would need a privacy policy that stated this + a checkbox to agree because 1) an email is PII, 2) people cannot reasonably assume that we share their email if they click a button that says "Pay". Many people also sign up with username+datacoop@provider.tld
benjaoming commented 2024-08-04 10:02:41 +00:00
Owner
Copy link

But to answer the question: Yes, Stripe does support this: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-customer_email

But to answer the question: Yes, Stripe does support this: https://docs.stripe.com/api/checkout/sessions/create#create_checkout_session-customer_email
decibyte commented 2024-08-04 10:06:54 +00:00
Author
Owner
Copy link

Alright. I'll close this again :)

Alright. I'll close this again :)
benjaoming commented 2024-08-04 15:35:19 +00:00
Owner
Copy link

I was wondering if anyone would disagree with this, but I think that when we choose between user convenience and privacy, then privacy will probably always win :)

Unfortunately Stripe also doesn't support removing the email field entirely.

However, a "funny" way to fix it would be to supply Stripe with a /dev/null email address, thus hiding the field 🙃

I was wondering if anyone would disagree with this, but I think that when we choose between user convenience and privacy, then privacy will probably always win :) Unfortunately Stripe also doesn't support removing the email field entirely. However, a "funny" way to fix it would be to supply Stripe with a /dev/null email address, thus hiding the field 🙃
decibyte commented 2024-08-04 17:56:15 +00:00
Author
Owner
Copy link

I agree privacy is more important. The latter approach also sounds interesting!

I agree privacy is more important. The latter approach also sounds interesting!
benjaoming commented 2024-08-04 18:08:30 +00:00
Owner
Copy link

Let's keep this open! Maybe we would provide privacy-shielded emails for members some day? Here's a good use-case!

Let's keep this open! Maybe we would provide privacy-shielded emails for members some day? Here's a good use-case!
benjaoming commented 2024-08-04 18:09:18 +00:00
Owner
Copy link

(but we also don't want to violate Stripe TOS and get blocked)

(but we also don't want to violate Stripe TOS and get blocked)
benjaoming changed title from is it possible to pass on e-mail address to Stripe? to Privacy-shield for member's emails when paying with Stripe or other 3rd parties? 2024-08-04 18:09:40 +00:00
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
services
keycloak
stripe
vidir_refactor
feature/allauth-for-accounts
No results found.
Labels
Clear labels   
bug

Something is not working

  
duplicate

This issue or pull request already exists

  
enhancement

New feature

  
help wanted

Need some help

  
invalid

Something is wrong

  
question

More information is needed

  
wontfix

This won't be fixed

No labels
bug
duplicate
enhancement
help wanted
invalid
question
wontfix
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: data.coop/membersystem#43
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?