diff --git a/src/routes/blog/post/security-is-a-revolving-door/+page.markdoc b/src/routes/blog/post/security-is-a-revolving-door/+page.markdoc
index 0a100be206a..7dca496c49f 100644
--- a/src/routes/blog/post/security-is-a-revolving-door/+page.markdoc
+++ b/src/routes/blog/post/security-is-a-revolving-door/+page.markdoc
@@ -141,7 +141,7 @@ This protection is infrastructure-level and requires no configuration on your pa
 
 Appwrite's [audit logs](/docs/advanced/security/audit-logs) record events across all products (authentication, databases, storage, functions, and messaging) including the user, event type, IP address, location, and timestamp for each action.
 
-Audit logs are available at the project level, table or bucket level, and per-user level. For Pro plans, logs are retained for 7 days. For applications where compliance or incident response requires event tracing, audit logs provide the trail needed to understand what happened and when.
+Audit logs remain useful for compliance and incident response, and the current retrieval guidance lives in the [audit logs documentation](/docs/advanced/security/audit-logs). For Pro plans, audit logs are retained for 7 days.
 
 # Compliance certifications
 
diff --git a/src/routes/docs/advanced/security/audit-logs/+page.markdoc b/src/routes/docs/advanced/security/audit-logs/+page.markdoc
index 4499f50f9a8..ef02304deb9 100644
--- a/src/routes/docs/advanced/security/audit-logs/+page.markdoc
+++ b/src/routes/docs/advanced/security/audit-logs/+page.markdoc
@@ -12,20 +12,14 @@ and effectively.
 
 # Access audit logs {% #access-audit-logs %}
 
-You can access audit logs for different products under the **Activity** tab where applicable.
-Logs are available for tables, rows, and individual users.
+Audit logs are no longer available through **Activity** tabs in the Appwrite Console.
 
-{% only_dark %}
-![Project settings screen](/images/docs/advanced/security/dark/activity.avif)
-{% /only_dark %}
-
-{% only_light %}
-![Project settings screen](/images/docs/advanced/security/activity.avif)
-{% /only_light %}
+For user-specific audit data, use the [Users API references](/docs/references/cloud/server-nodejs/users)
+from a server environment with an API key.
 
 # Format {% #format %}
 
-Audit log entries under the **Activity** tab has the following structure.
+Audit log entries have the following structure.
 Each entry describes an event.
 
 {% table %}
diff --git a/src/routes/docs/advanced/security/hipaa/+page.markdoc b/src/routes/docs/advanced/security/hipaa/+page.markdoc
index 63ea0974d46..a6a8cb4fdc1 100644
--- a/src/routes/docs/advanced/security/hipaa/+page.markdoc
+++ b/src/routes/docs/advanced/security/hipaa/+page.markdoc
@@ -46,7 +46,10 @@ Appwrite provides access to different types of logs depending on the context:
 
 - **Function logs**: Each serverless function or hosted sites includes stdout and stderr logs you can access per execution. Those are retained for different periods per plan.
 
-- **Audit logs**: For users or teams with compliance needs, we provide structured audit logs covering authentication events, permission changes, and other relevant activities directly on your console, under an activity tab in the different products the platform offers. Those are retained for different periods per plan.
+- **Audit logs**: For compliance needs, we provide structured audit logs covering authentication events, permission changes, and other relevant activities.
+  Audit logs are no longer available through Activity tabs in the Appwrite Console.
+  For user-specific audit data, use the [Users API references](/docs/references/cloud/server-nodejs/users) from a server environment with an API key.
+  Audit logs are retained for different periods per plan.
 
 Please note that while Appwrite Cloud serves as a HIPAA-compliant platform to handle data,
 it is the responsibility of developers to ensure that their application is also compliant with HIPAA regulations.
diff --git a/src/routes/docs/tooling/command-line/tables/+page.markdoc b/src/routes/docs/tooling/command-line/tables/+page.markdoc
index 9f3e9311cab..917b00de09c 100644
--- a/src/routes/docs/tooling/command-line/tables/+page.markdoc
+++ b/src/routes/docs/tooling/command-line/tables/+page.markdoc
@@ -254,7 +254,4 @@ appwrite tables-db [COMMAND] [OPTIONS]
 * `delete-index [options]`
 * Delete an index.
 ---
-* `list-table-logs [options]`
-* Get the table activity logs list by its unique ID.
----
 {% /table %}
diff --git a/src/routes/docs/tooling/command-line/teams/+page.markdoc b/src/routes/docs/tooling/command-line/teams/+page.markdoc
index 89c458317b3..437a3f56d9b 100644
--- a/src/routes/docs/tooling/command-line/teams/+page.markdoc
+++ b/src/routes/docs/tooling/command-line/teams/+page.markdoc
@@ -92,9 +92,6 @@ appwrite teams [COMMAND] [OPTIONS]
 * `delete [options]`                  
 * Delete a team using its ID. Only team members with the owner role can delete the team.
 ---
-* `list-logs [options]`               
-* Get the team activity logs list by its unique ID.
----
 * `list-memberships [options]`         
 * Use this endpoint to list a team's members using the team's ID. All team members have read access to this endpoint.
 ---  
diff --git a/src/routes/docs/tooling/command-line/topics/+page.markdoc b/src/routes/docs/tooling/command-line/topics/+page.markdoc
index 3a8892df4c9..0c3fad4711a 100644
--- a/src/routes/docs/tooling/command-line/topics/+page.markdoc
+++ b/src/routes/docs/tooling/command-line/topics/+page.markdoc
@@ -114,9 +114,6 @@ appwrite messaging [COMMAND] [OPTIONS]
 * `delete [options]`        
 * Delete a message. If the message is not a draft or scheduled, but has been sent, this will not recall the message.
 ---
-* `list-message-logs [options]`          
-* Get the message activity logs listed by its unique ID.
----
 * `list-targets [options]`
 * Get a list of the targets associated with a message.
 ---
@@ -189,12 +186,6 @@ appwrite messaging [COMMAND] [OPTIONS]
 * `delete-provider [options]`
 * Delete a provider by its unique ID.
 ---
-* `list-provider-logs [options]`   
-* Get the provider activity logs listed by its unique ID.
----
-* `list-subscriber-logs [options]`
-* Get the subscriber activity logs listed by its unique ID.
----
 * `list-topics [options]`            
 * Get a list of all topics from the current Appwrite project.
 ---
@@ -210,9 +201,6 @@ appwrite messaging [COMMAND] [OPTIONS]
 * `delete-topic [options]`          
 * Delete a topic by its unique ID.
 ---
-* `list-topic-logs [options]`           
-* Get the topic activity logs listed by its unique ID.
----
 * `list-subscribers [options]`       
 * Get a list of all subscribers from the current Appwrite project.
 ---
diff --git a/static/images/docs/advanced/security/activity.avif b/static/images/docs/advanced/security/activity.avif
deleted file mode 100644
index 187bc664804..00000000000
Binary files a/static/images/docs/advanced/security/activity.avif and /dev/null differ
diff --git a/static/images/docs/advanced/security/dark/activity.avif b/static/images/docs/advanced/security/dark/activity.avif
deleted file mode 100644
index 3f3ca28cb2e..00000000000
Binary files a/static/images/docs/advanced/security/dark/activity.avif and /dev/null differ