- Case Number: a20100215.2
- Status: closed
- Claimants: ZG
- Respondents: CAcert
Case Manager: AlexanderPrinsier
Arbitrator: UlrichSchroeter
- Date of arbitration start: 2010-11-03
- Date of ruling: 2010-11-10
- Case closed: 2010-11-22
- Complaint: Delete Account Request
- Relief: TBD
Before: Arbitrator UlrichSchroeter (A), Respondent: CAcert (R), Claimant: ZG (C), Case: a20100215.2
History Log
- 2010-02-15 (issus.c.o) case [s20100215.152]
2010-02-16 (UlrichSchroeter): added to wiki, request for CM / A
- 2010-11-03 (CM): I'll take care about this case
- 2010-11-03 (A): I'll take care about this case
- 2010-11-03 (A): sent Init notification to (C) with deadline for response of 14 days
- 2010-11-07 (C): confirms delete account request
- 2010-11-08 (A): identified that (C) has two accounts and requests deletion of account #2, so this is a regular email dispute. Requesting from (C)'s account #2 email address CCA acceptance and confirmation of delete account request
- 2010-11-09 (C): accepts CCA/DRP under this arbitration and confirms deletion of account #2 for transfer of email address onto account #1
Discovery
- User has 2 accounts with 2 different email addresses
- User wants account #2 deleted to transfer email address of account #2 onto account #1, so this case is not a regular "delete account request". Its an email dispute case.
- 2010-11-08 CCA agreement has not realy been established
- 2010-11-09 CCA agreement has been established
Ruling
- This case moved from a "delete my account" request to "accounts cleanup"
- User confirmed, that both accounts are under his control
- User accepted CCA / DRP under this dispute filing and still continues to be a community member with his account #1 so there is no CCA termination in this case to handle
Support should execute the "delete my account" procedure on (C)'s account #2 to free the email address, so the user can add the email address from account #2 onto his account #1 by hijacking the account according to procedure Delete Account Procedure for SE and SE Manual - Delete and Deactivate Accounts
- a new password should be set (and later forgotten)
- the account to hijack
- A snapshot of the account information shall be taken and printed to pdf including all account informations, certs informations and so on, sending to arbitrator
- the secret answers to fill with junk
Givenname, Middlename, Lastname and Suffix to be filled with the arbitration number a20100215.2
- DoB to set to 1900-01-01 or 1970-01-01
- all flags to reset
- all certificates to revoke
- all domains to delete
- all email addresses deleted (except the primary email address)
add email address arbitration_a20100215.2@c.o
switch to primary email address arbitration_a20100215.2@c.o
- remove previous primary email address
- logoff from account
- The last action shall be to lock the account
Frankfurt/Main, 2010-11-10
Execution
- 2010-11-10 (A): sent ruling to (C), (Support), (CM)
- 2010-11-10 (A): exec req sent to (Support)
- 2010-11-10 (Support): sends [s20101110.7] Execution Request report
- 2010-11-11 (A): sends (C) exec report info with request to confirm that problem is now solved.
- 2010-11-19 (A): sending (C) a reminder confirmation request that problem is now solved.
- 2010-11-20 (C): problem is now solved
- 2010-11-22 (A): case closed.
Similiar Cases
User wants account deleted, no Assurance Points, no certificates |
|
User wants account deleted, no Assurance Points, no certificates |
see also: Arbitrations Training Lesson 20 - Arbitration Case - Delete Account Request