CipherDrive™ uses infrastructure that may operate across multiple locations and jurisdictions. The location of an encrypted file object is not necessarily the location of every type of information associated with your account.
CipherDrive can place or replicate encrypted objects across Ackaia-operated or provider-supported storage infrastructure according to the current service architecture, region, reliability requirements, and product configuration.
The Legal Request Response Policy recognizes that Ackaia may maintain region-placement or replication metadata for encrypted CipherDrive objects.
For supported encrypted-storage workflows, file contents are encrypted before ordinary storage. Under normal operation, Ackaia does not ordinarily possess the user-controlled keys required to decrypt stored file contents.
This security boundary applies regardless of the fact that the encrypted blob itself must physically exist on storage infrastructure somewhere.
Even if an encrypted object is stored or replicated in a particular region, other information can be processed in different locations. This can include:
Ackaia ID and account information;
authentication and security logs;
billing and payment metadata;
support communications;
email delivery;
telemetry and monitoring;
trust-and-safety records;
legal and compliance records.
A product-specific storage region should therefore not be interpreted as a guarantee that all personal information remains exclusively in that same region.
Ackaia is headquartered in the United States and may use infrastructure and service providers in multiple countries. Global processing can be necessary for storage, network delivery, security, payments, support, reliability, or other service functions.
Ackaia may have region-placement or replication metadata for some objects, but exact availability can depend on current product configuration, retention, and infrastructure design.
Use the current CipherDrive Trust Center or product documentation for region-specific information that Ackaia makes publicly available.
Not by itself. Storage location and key custody are different concepts.
If the provider infrastructure stores only an encrypted blob and does not possess the user-controlled key needed to decrypt it, physical possession of the ciphertext is not the same as ordinary plaintext access.
Think in two layers: where encrypted bytes are stored, and where account/operational information is processed. Those locations do not have to be identical.