solidusio / solidusio/solidus

Allow addresses to be truly deleted for GDPR and privacy compliance

Open
#6,108 15 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

changelog:solidus_core
Dominant language
Ruby
Stars
5.3k
Forks
1.4k
Avg merge
1d 22h
Merged PRs (30d)
62

Description

Concerns open PR: #3852 #3234 solidus_braintree #226

I am trying to wrap my head around this:

EU says clearly that personal data needs to be deleted upon customer request.

I do not see right now how we can make the address situation fit with that.

In Europe if the address is not needed for fiscal reason there's no reason to store it.

This means in Europe we need a solution to:

  • Delete an address after 10 + 1 years (in some countries it might even be less) for an address used within an order if, and only if, the address was used for a fiscal receipt created here (invoices are not included);
  • Delete an address immediately upon customer request if the address was not used on a fiscal receipt;
  • if an address reaches the age of consented storage (which can also be indefinitely if the privacy terms of a website are written accordingly) if not requested by a user earlier.

I don't see how to avoid that to comply with European regulations.

Solidus Version:
All

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Review open PRs #3852 and #3234, along with solidus_braintree #226, before choosing an entry point; this issue names no files or tests. Clarify the retention rules for fiscal and non-fiscal addresses, customer deletion requests, and consent expiry, then define completion as those cases being implemented and covered by project tests.

Written by the indexing model from the issue text.

Assessment

Tech stack
ruby
Domain
backend, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.