DATA & PRIVACY

Your files. Your instructions.

Privacy policy · Updated 21 October 2026
Operator: Ahmed / IMG DESIGN · imgdesign999@gmail.com

Purpose and access

Abousaada Drive is a private integration used for the owner's brand, content and file-management workflows. Google OAuth authorization is provided by the account owner. The current Drive scope can read, create, edit, organize, share and delete Drive files; it is not technically restricted to a single folder. These permissions support the file operations the owner requests. The brand-task publishing path is configured to a private workspace.

Data used

The integration can access file and folder names, identifiers, metadata and the contents of files selected for a task. It uses Google account information to verify the connected account, and OAuth tokens to maintain the authorized connection. Task briefs, relevant reference content, outputs, revisions and operational status may be retained to carry out and review the work.

Use and sharing

Data is used to carry out the owner's requested tasks, review results, organize files and provide deliverables. Relevant file content or derived task context may be sent to the configured OpenAI or Anthropic tools when required for an authorized AI task. The providers' service terms and account settings also apply to that processing. Files may be shared with a recipient when the owner instructs the assistant to do so. Merely connecting Drive does not make files public.

The application does not sell Google data, use it for advertising or run a general-purpose model-training pipeline. Human access is limited to the owner and people authorized for the work or necessary support. Google API data use and transfers must follow the Google API Services User Data Policy, including its Limited Use requirements.

Storage and retention

Requested working files and outputs may be stored in the owner's Drive, on the owner's VPS and on authorized work devices. Connection tokens are stored in private server configuration, rather than in the public website or source repository. Task records and working copies remain until the owner removes them or requests cleanup. Existing backups may retain relevant copies until they are separately retired; revoking access does not erase existing files or backups.

Your controls

The owner can review and revoke access through Google Account connections. Revocation prevents future authorized Drive access once existing access tokens are no longer valid. To request removal of server-side working copies or task records, contact the operator and identify the relevant task or files. Do not email passwords, API keys or OAuth tokens. A deletion request will be reviewed for related working copies and backups rather than represented as an instant removal from every location.

This public website

These static pages have no sign-in, forms, advertising, analytics scripts, tracking cookies or third-party font requests. Hosting infrastructure and certificate services may process normal connection data such as IP addresses and request information to deliver and secure the website.

Updates

This page will be updated if the integration's data practices change. Material changes to Google data use require notice and any necessary renewed consent before the new use begins. This page describes the integration; it does not grant the assistant new permissions.