AEU Content
Privacy
Effective date:
AEU Content is an owner-operated application for Ancient Egypt Uncovered. Privacy questions, deletion requests and disconnection requests can be sent to mahmoudabdelrahman687@gmail.com. This website does not offer Google sign-in or connect visitors' accounts.
Information and use.
With the owner's Google authorization, AEU Content uses channel identity, selected video information including private metadata, caption information and content, and non-revenue performance reports. Selected management functions can also use playlist, comment and channel-setting information. These data support owner-approved channel management, result verification and performance review.
The current connection requests youtube.readonly, youtube.force-ssl and yt-analytics.readonly. The force-ssl permission has broader powers than the description and caption actions shown in the demonstration. The connection does not request Gmail access or monetary-Analytics permission. Google handles authorization; AEU Content does not ask for the owner's Google password.
Storage and access.
Application data are stored on the owner's Hostinger VPS. The current connection stores authorization material in a passphrase-encrypted vault; unlocked credentials are temporarily present in the running process. The application does not store the vault passphrase. This does not mean that the whole server, original client exports or legacy authorization files are encrypted.
Local files and a SQLite archive retain selected metadata, identifiers, approved changes, observations, timestamps, operation records, diagnostics, captions and reports. These data have account-level file permissions but are not application-encrypted like the vault. Encrypted prior-grant and candidate records can remain for recovery. Privileged server administrators can access the host; the website does not provide access to these records. Historical helper records remain separate from the current vault and archive.
Providers, backups and support copies.
Google provides authorization and YouTube API services. Hostinger supplies the VPS. Weekly automatic backups of the entire VPS are enabled and may include application data and encrypted authorization records.
According to Hostinger support's answer supplied by the owner, automatic backups cannot be manually deleted, are removed through rotation, and have no promised seven-day purge or guaranteed total-erasure date. Deleting data from the live VPS therefore does not establish that its backup copies have been erased.
The API runtime does not automatically forward API responses to an AI service. Separately, the app operator may share selected sanitized records with ChatGPT/Codex for troubleshooting and review. Those records can include identifiers, metadata or report results. Credentials, authorization codes, passphrases and raw authentication URLs are excluded from support sharing. Existing support messages and attachments are distinct from VPS backups; their retention, deletion and relevant data-use settings have not been confirmed. Sanitization does not itself establish deletion or remove all data-handling obligations.
Retention, deletion and disconnection.
Retention and deletion require manual handling; there is no automatic purge. A local inventory and handling plan exist, but the recurring authorization/retention checks and complete deletion procedure have not yet been established as an operating process.
For requested data in live application storage under the app operator's control, the app operator commits to verifying the request, arranging deletion as soon as possible and within seven calendar days, and confirming the result. This is a live-data commitment, not a guarantee that Hostinger automatic backups or separately retained support copies are erased within seven days. Requests affecting those copies require separate follow-up, and any unresolved copies will be identified in the response.
A disconnection request also asks the app operator to stop application access and remove the Google authorization. You can revoke access directly through Google's account permissions page. Revoking access does not itself erase local files, backups or support copies. Deleting application records does not delete the channel or data stored by YouTube.
Website and contact.
The website provides information and external links. It does not offer account connection, booking or payment forms. Hosting infrastructure processes connection information to serve the pages; infrastructure-log retention has not been established here. Gmail processes messages sent to the contact address, and the app operator uses them to handle the request. Correspondence is handled manually without an automatic deletion schedule. External services have their own privacy practices. An unlisted demonstration video, if published, can be viewed by anyone with its link.
AEU Content uses YouTube API Services. See the Google Privacy Policy and YouTube Terms of Service.
Changes to these practices will be reflected in this policy, with additional consent obtained where required.