Privacy Policy
Effective date: 19 November 2026.
About this installation
AHT OpenPost is an owner-operated, self-hosted installation of OpenPost for AI-assisted content creation, media preparation, planning, scheduling and authorized social publishing. Registration is currently closed. This policy describes this installation, rather than every deployment of the upstream OpenPost software.
Information processed
The application stores local account and workspace information, authentication records, connected social account identifiers and profile metadata, OAuth permissions and tokens, drafts, captions, uploaded media, schedules, publication results and operational records. Depending on enabled platform features and granted permissions, connected providers may also supply engagement, messages or analytics. TikTok is not connected at the time this policy was prepared; requested permissions do not establish approval or consent.
Purpose and authorized connections
Information is processed to authenticate users, prepare and organize content, maintain authorized social connections, schedule and carry out approved publishing operations, and diagnose problems. Official OAuth flows take place with the social provider. Provider permissions determine the information and actions available.
The intended TikTok scopes are user.info.basic for basic identity, video.upload to submit a video to TikTok for completion there, and video.publish for Direct Post where permitted. Display API access is not assumed. Connecting TikTok does not grant public publishing approval. Publishing or uploading sends the selected media and metadata to the relevant platform.
Hosting, media and credential storage
The service runs on the operator's Windows computer. Application records are in a local SQLite database and media in local storage. Social access and refresh tokens use OpenPost's configured application encryption. The encryption key, application secrets and developer credentials are referenced from files in the operator's NTFS user profile with restricted permissions. This does not mean the entire database, media, logs or disk is encrypted.
Tailscale Funnel currently forwards the social account routes and media routes over public HTTPS; it does not expose the complete web interface through the current configuration. Authorized media delivery can use signed URLs. Anyone who obtains a usable media URL may be able to retrieve the associated file while that URL remains valid. Network intermediaries and social providers process connection/request information under their own terms. Local backups exist separately and can include application data and credentials.
AI processing
When an AI feature is invoked, OpenPost sends the relevant prompt and context through a local gateway to Google's Gemini API. The gateway can add stored brand rules; selected image content may be included for image-related requests. The gateway is configured with a limit of 20 requests per day. AI is not confined to the local computer.
The configured service uses Gemini's free tier. Under Google's unpaid-service terms, submitted content and responses may be used to improve products and models and may be reviewed by humans, subject to the terms applicable to the account. Do not submit patient data, confidential client material, credentials or other sensitive personal information. Read Google's Gemini API terms. AI output requires human review.
Cookies, logs and telemetry
OpenPost uses authentication/session mechanisms to maintain signed-in access. Operational logs and gateway usage counters support troubleshooting and quota control. OpenPost telemetry is disabled in the current configuration. This is not a guarantee that the hosting network, browser, social platforms or Google collect no data.
Retention and deletion
There is no verified automatic retention schedule for this installation. Drafts, media, records and companion planning files remain until removed through the available application functions or by the operator. Moving media to Trash is not permanent erasure. Backup and log copies need separate handling; no immediate or universal erasure is promised. Content already sent to a social platform is subject to that platform's controls and retention.
Your controls and requests
You can stop new AI requests and publishing operations. OpenPost supports disconnecting a social destination and separately revoking its provider grant, which disconnects all destinations using that grant. A destination disconnect alone does not revoke the provider grant. You may also remove AHT OpenPost's access in the social provider's connected-app/security settings. Revocation does not delete existing posts or local drafts.
The installed API contract includes account-data export, a deletion-impact preview and account deletion. Access checks and ownership dependencies may apply. These capabilities were inspected without executing a deletion or promising that every companion file or backup is included. To request access, correction, export or deletion of retained information, email ahmedmostafa150it@gmail.com. State whether you request access, correction, export or deletion and identify the relevant account or content. Do not send passwords, API keys, OAuth tokens or patient information. Identity or authority may need to be verified before action. The operator should review local application data, companion content, logs and backups as appropriate, and explain any remaining copies or provider-controlled data.
Contact and changes
For privacy, deletion and support requests, contact ahmedmostafa150it@gmail.com. Requests are intended for manual review by the operator; no automated deletion portal or response deadline is promised. Material changes to actual processing should be reflected in this page with an updated effective date.