Ackaia ID vs. Your Product Account

Your Ackaia ID and your state inside an individual Ackaia product are related, but they are not the same thing.

Ackaia ID is the identity layer

Ackaia ID is responsible for shared account and authentication functions such as:

identifying your account;
sign-in and authentication;
account-level security;
sessions;
recovery;
account continuity;
authorization and entitlement context for participating services.

A product account is the product-specific relationship

An individual product may maintain its own records and state associated with your Ackaia ID.

Depending on the product, this can include:

whether you have access to the product;
product-specific permissions;
subscription or plan state relevant to that product;
usage and quotas;
product settings;
product objects and metadata;
organization or workspace membership;
product-specific security state.

Why does the distinction matter?

It explains several situations that can otherwise seem contradictory.

Your Ackaia ID can be valid while a particular product entitlement, organization membership, regional requirement, or permission is missing.

A product can be restricted without deleting your Ackaia ID

An enforcement, billing, subscription, or product-specific restriction can affect one service without necessarily deleting the broader identity account.

Deleting product data is not necessarily deleting the identity

Removing or closing a product-specific account, subscription, workspace, vault, or dataset is not automatically the same as deleting the Ackaia ID itself.

Account recovery may not recover product cryptographic material

This is especially important for encrypted services.

For CipherDrive, Ackaia ID account recovery can restore access to the identity layer without necessarily recreating user-controlled cryptographic material that has been permanently lost.

What information can a product receive from Ackaia ID?

A participating product can receive information reasonably needed to provide and secure access, such as:

account identifier;
basic identity information;
account status;
subscription or entitlement status;
applicable security settings.

The exact fields depend on the product and should be documented by that product where appropriate.

A simple way to remember the difference

Ackaia ID answers: “Which account is this, and is it authorized to request access?”

The product answers: “What can this account do here, and what product-specific data or state belongs to it?”

Authentication is shared. Product responsibilities remain scoped.