Privacy Policy

1. Application and operator

Farah Digital operates websites, software products, and a private digital-operations automation application for authorized users. Questions or data requests may be sent to [email protected].

2. Information collected outside Google integrations

Farah Digital may collect information that a person submits directly, such as a name, email address, project inquiry, support message, account information, or billing-related details. Websites may also collect limited technical and analytics information such as browser type, device information, referring pages, approximate location, and usage events.

3. Google user data accessed

Google data is accessed only after the user selects a Google account and grants the permissions displayed by Google. The exact data available depends on the permissions granted, the user's account-level access, and the workflow requested. Farah Digital may access the following categories:

• Gmail: messages, threads, headers, labels, drafts, attachments, and ordinary Gmail settings needed for user-requested email workflows.
• Google Calendar: calendars, events, attendees, scheduling details, and related metadata.
• Google Drive and Drive-backed files: files, folders, metadata, permissions, and content, including Docs, Sheets, Slides, PDFs, archives, videos, and ordinary image files such as JPG and PNG.
• Google Contacts and Tasks: contact records, task lists, tasks, and related metadata.
• Google Ads: accessible customers, accounts, campaigns, ads, assets, audiences, conversions, reporting, and supported configuration data.
• Google AdSense: account, site, ad-client, payment, alert, and reporting data supported by the AdSense API.
• Google Analytics: accounts, properties, streams, configuration, access bindings, and reporting data.
• Google Search Console: sites and properties, sitemaps, Search Analytics, and related configuration or reporting data.
• Google Site Verification: ownership-verification resources required for user-requested verification workflows.
• Google Tag Manager: accounts, containers, workspaces, tags, triggers, variables, versions, environments, publishing state, and user permissions supported by the granted scopes.
• YouTube: channel, video, playlist, comment, caption, rating, subscription, and related data supported by the granted permissions.

4. How Google user data is used

Google user data is used only to provide or improve visible, user-requested features, including:

• finding, reading, drafting, sending, organizing, archiving, or trashing email;
• creating and managing schedules and events;
• searching, reading, organizing, uploading, sharing, exporting, backing up, or trashing Drive files;
• managing contacts and tasks;
• reviewing and operating authorized Ads, AdSense, Analytics, Search Console, Site Verification, and Tag Manager resources;
• reviewing and managing authorized YouTube resources; and
• producing user-requested summaries, reports, recommendations, or automation results.

Where an automation or language-model processor is used to complete a requested workflow, only the data reasonably necessary for that request is provided to the processor. Google user data is not sold, used for personalized advertising, or used to train a general-purpose model by Farah Digital.

5. Storage, retention, and security

OAuth credentials, configuration, operational state, logs, reports, and user-requested output may be stored on access-controlled infrastructure and approved backup systems. Farah Digital limits access to authorized operators and services, applies reasonable technical and organizational safeguards, and does not publish OAuth refresh tokens or client secrets.

Data is retained only for as long as reasonably needed to provide the requested workflow, maintain security and auditability, meet legal obligations, or preserve an authorized backup. Temporary working data should be removed when it is no longer needed. Backup copies may remain until their defined retention period expires.

6. Sharing and transfers

Farah Digital does not sell Google user data. Data may be transferred only to service providers acting on Farah Digital's behalf when necessary to provide or improve a user-requested feature, operate secure infrastructure, process an authorized workflow, or comply with law. Providers are expected to use the data only for the contracted purpose and to protect it appropriately.

Farah Digital may also disclose information when required by law, to protect users or systems, to investigate abuse or security incidents, or with the user's explicit direction or consent.

7. Google API Services User Data Policy — Limited Use

Farah Digital's use and transfer to any other app of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.

8. User choices, revocation, and deletion

• Users can review the permissions displayed by Google before granting access.
• Users can decline authorization and can stop using the integration at any time.
• Users can revoke Farah Digital's access through their Google Account permissions.
• Users can request access to, correction of, or deletion of applicable application-held data by emailing [email protected].

A deletion request may not immediately remove data from immutable security records or backups; those copies will be isolated from ordinary use and removed through the applicable retention cycle unless a longer period is legally required.

9. Cookies and website analytics

Farah Digital websites may use essential cookies and privacy-respecting analytics to operate the site, understand aggregate usage, and improve performance. Browser controls can be used to limit non-essential cookies where available.

10. Children

Farah Digital's Google Operations application is intended for authorized business users and is not directed to children.

11. Policy changes

This policy may be updated when services, legal requirements, or data practices change. The effective date will be revised, and material changes to Google data use will be disclosed before the new use begins where required.