• Arbitrations
• a20120409.1

• Case Number: a20120409.1
• Status: closed
• Claimants: Fabian Z
• Respondents: CAcert

• Initial Case Manager: AlexRobertson

• Case Manager: MartinGummi

• Arbitrator: EvaStöwe

• Date of arbitration start: 2013-11-27
• Date of ruling: 2014-01-13
• Case closed: 2014-01-13
• Complaint: Remove Assurer Account
• Relief: TBD

Before: Arbitrator Eva Stöwe (A), Respondent: CAcert (R), Claimant: Fabian Z (C), Case: a20120409.1

History Log

• 2012-04-09 (issue.c.o) case s20120409.220

• 2012-05-07 (iCM): added to wiki, request for CM / A
• 2013-11-27 (CM): I take care of this case as (CM) and select Eva Stöwe as (A)
• 2013-11-27 (CM): Mail to support for update on account
• 2013-11-28 (Support): state of account
• 2013-11-28 (CM): question to support about some of the assurance-entries
• 2013-11-28 (Support): gives idea what may have cause those dubious assurance-entries

• 2013-11-28 (C of a20131128.1): files dispute a20131128.1 to find all assurances of that kind and how they should be handled

• 2013-12-14 (A): combined init and info mail to (C) about status of case and need to clarify safekeeping of CAPs
• 2013-12-14 (C): does not care if his account is closed, but he will not use it annymore
• 2014-01-12 (A): asked (C) if it would be ok to keep the account open (with the option to lock it and initiate closing when all assurances are older than 7 years)
• 2014-01-13 (C): I will keep the account, please do not lock it
• 2014-01-14 (A): ruling sent to (C), (CM)
• 2014-01-14 (A): case closed

Original Dispute, Discovery (Private Part) (optional)

• Link to Arbitration case a20120409.1 (Private Part), Access for (CM) + (A) only

EOT Private Part

Discovery

• In the original dispute, C asked to remove his CAcert account.
• An investigation showed:
  • It is not known if C accepted CCA.
  • C does not have an active certificate.
  • No other involvement from C in arbitration cases is known.
  • C was an assurer. It looks like he even was a super-assurer according to the supper assurance program
    • 7 assurances were done within the last 7 years, so C is oblieged to safekeep the according CAPs and to maintain an active primary email address according to AP until the last of them is 7 years old.
    • 19 assurances are older than 7 years. C may have destroyed the CAP forms for those assurances, since the 7 years are over.

      • 3 are yellow assurances (FAQ to yellow assurances)

      • 2 are to the same assuree (which may have been ok at that time).

• A support member issued a20131128.1 to investigate such multiple assurances.

  • This case is currently running, but C is not involved.
• C has CAP forms for all assurances he did.
• When asked, C responded that he does not care if his account is closed, but he will not use it anymore.
• C was asked if he would keep his account in this case. He also got the offer that
  • his account would be locked, so that it could not accessed by anybody
  • his account would be closed automatically after the 7 years for the last assurance were over
• C decided to keep his account. He currently does not want it locked.
• Nothing has to be done.

Ruling

Since C declared that he does not want to remove his account and does not want any further actions on the side of CAcert to take place, the case can be closed without further actions. C's account will stay open and active.

--

Cologne, 2014-01-13

Execution

• 2014-01-14 (A): ruling sent to (C), (CM)
• 2014-01-14 (A): case closed

Similiar Cases

see also: Arbitrations Training Lesson 20 - Arbitration Case - Delete Account Request

• CategoryArbitration

• CategoryArbCaseAccountDelAssurer