Stages, the last stage, and exceptions

Implementation plan

1. 1. Account

   Name, work email, a password of at least 12 characters with letters and numbers, and agreement to the terms and privacy policy. Enter the 6-digit code from that inbox. The account is created only after the code matches.

   Result: You can sign in.

2. 2. Company

   Search the directory or create a company profile.

   Result: A company page exists.

3. 3. Claim

   Enter the 6-digit work-email code. A code lasts 10 minutes. An email on the company domain is approved immediately.

   Result: The profile is claimed and the workspace opens.

4. 4. Readiness

   Complete the checklist.

   Result: A configuration score is saved. The number is not the last stage.

5. 5. Notice and purposes

   Publish a notice version and add at least one purpose.

   Result: A notice version and a purpose exist.

6. 6. Application

   Add an application and copy the API key. The raw key is shown once.

   Result: The website or app can call the hub.

7. 7. Last stage of implementation

   Record a consent choice for an opaque user reference, a purpose, and the notice version.

   Result: The consent record exists and the audit chain has that event.

Implementation is still in progress until stage 7. The checklist, a website scan, and a selected plan do not replace that record.

Modification plan

Use this after implementation, when something already live needs a change.

1. 1. Change

   Edit the notice, a purpose, a team member, a vendor, a webhook, the plan, or grievance handling. On Profile, an owner or an admin can save the grievance email, privacy contact, policy links, and whether the public page shows the readiness score. That score is a self-assessed configuration status. It is not a legal certification. The owner can change a teammate between Admin and Member, or remove them. The owner stays on the workspace. An owner or an admin can close an incident. A grievance status change is written on the audit trail. To change your password, open Profile, enter the new password twice, and match the 6-digit code emailed to your work address. The password changes only after the code matches.

   Result: The new values are saved.

2. 2. Publish

   If the notice text changed, publish the next version of that notice, such as 1.1. A brand-new notice still starts at 1.0. Older consent records keep the version they were given.

   Result: New choices use the new notice version.

3. 3. Last stage of modification

   Confirm the change on the hash-chained audit log. A withdrawal is finished when that consent history shows withdrawn.

   Result: The audit log contains the event.

Exception process

1. Read the message on the screen.
2. Stay on the stage that failed.
3. Use the matching row below.
4. Repeat that stage until its result exists.
5. Continue only after that. A failed step does not move the last stage forward.