1. Scope and operator
This policy describes Hikma Publisher, the owner-operated application used to manage the في أرض الحكمة (Fi Ard Al Hikma) channel, its Telegram administration workflow, and this information website. Contact the operator at aljishari1@gmail.com.
The application is configured for its operator, not as a public service for connecting other people's channels. Visiting this website does not authorize Google access. The application uses YouTube API Services; Google's processing is described in the Google Privacy Policy.
2. Information used
| Information | Purpose and storage |
|---|---|
| Google authorization | Access and refresh tokens allow the authorized server to act for the connected channel. Tokens are stored in a server-side credential file, separate from this public website. Hikma Publisher does not request or store the operator's Google password. |
| Channel and video data | Channel IDs, source URLs, names, video titles, metadata, license information, and upload/processing status are used for source checks, attribution, channel management, and publishing. |
| Production files | Source media, audio segments, selected frames, transcripts, generated text, thumbnails, and output media are processed in server work directories. |
| Analytics | Video-level views, estimated watch time, average viewing duration/percentage, and subscriber gains/losses are retrieved for channel reports. The implemented reporting request does not retrieve viewers' identities or individual viewing histories. |
| Operations and messages | Job records, source settings, upload identifiers, error records, Telegram administrator/chat identifiers, and submitted links support administration, recovery, and avoiding duplicate uploads. Support email contents are processed when you contact the operator. |
The configured Google scopes are youtube.force-ssl for channel/video operations and yt-analytics.readonly for reports. Google's permission wording can cover more operations than this application's current features use.
3. How information is used and shared
The server uses this information to run the publishing features the operator configures. Google/YouTube receives API requests and uploaded videos, thumbnails and metadata. Material marked public is available to the public through YouTube; private or unlisted visibility follows YouTube's rules.
Google Gemini receives source audio segments, selected frames, transcripts, source titles/channel names, and editorial instructions to transcribe material and prepare or review presentation text. The current AI request code does not send Google OAuth tokens, Telegram credentials, or channel Analytics reports to Gemini. Provider handling can depend on billing status and region: unpaid Gemini services may use inputs and outputs for product improvement and human review, subject to regional exceptions. See Gemini API terms. This policy does not promise zero retention by an AI provider.
Telegram processes administration messages, requested reports/previews, and media sent to configured Telegram destinations. The server and website hosting providers process the files or network information needed to operate their services. Email providers process support correspondence. Their own policies also apply. The operator may inspect content and logs to handle review cases and technical problems.
Hikma Publisher's implemented workflow does not sell user data, serve personalized advertisements, or train its own general-purpose AI model.
4. Storage and retention
Production files for a completed YouTube job are removed from that job's work directory after the application confirms its requested upload and visibility state. Failed or unfinished work is kept for recovery. Completed-job records, source records, upload IDs and license evidence remain in the database; the current version does not automatically expire these records.
Authorization credentials remain on the operator's server until they are replaced or removed. The latest Analytics report is overwritten when a new report is generated. Operator-created backups and server logs can retain earlier records separately and require separate handling. This policy does not describe an automatic account-data deletion feature.
The operator restricts administrative access. Production website and API traffic should use HTTPS; credential files are kept outside the public website directory. Storage is not represented as end-to-end encrypted or guaranteed immune to unauthorized access.
5. Your control, revocation and deletion
The channel operator can pause future publishing, change sources and settings, and revoke Hikma Publisher's Google authorization through Google Account third-party connections. Revoking access does not automatically remove locally stored records or videos already published on YouTube.
To request deletion of stored data or ask a privacy question, email aljishari1@gmail.com with the relevant channel ID and the data or activity concerned. Do not send passwords, API keys or authorization tokens. Requests are handled manually by the operator, who may need to verify that the request comes from the account owner.
Deletion handling must include relevant stored account data and any copies retained in backups. Deleting a local application record does not delete a video on YouTube; channel owners manage those videos in YouTube Studio. The operator must follow the applicable deletion and retention requirements of the YouTube API developer policies.
6. This website and external services
These static pages contain no advertising scripts, Analytics trackers, embedded video players, login forms, or application cookies. The hosting service may record ordinary connection information such as IP address, request path, time and browser information in its access/security logs. Hosting-level settings and retention are controlled by the operator and hosting provider.
Links to YouTube, Google and Telegram take you to those services. Their data collection and cookies are governed by their own policies, including Google's Privacy Policy and Telegram's Privacy Policy. Email links open your email application.
7. Changes
This policy reflects the reviewed application configuration, with Gemini as its AI provider. The operator should update this notice before enabling a different AI provider or materially changing data handling. The revision date below identifies this version.
Last updated: 7 October 2026.