imperial64 imperial64dev scheduler
imperial64dev scheduler — Privacy Policy
Effective date: 3 October 2026 · Policy version 1 · See also the terms of service
Who runs it
The imperial64dev scheduler ("the scheduler") is a private tool made and run by Efe Kerim Ayvaz, an independent game developer in Türkiye who publishes as imperial64. Contact for anything on this page: hello@imperial64.dev.
Who uses it
Only its owner, imperial64. The scheduler publishes posts to imperial64's own social media accounts at the times the owner sets, and reads the statistics of those posts so the owner can compare how they did. It runs at social.imperial64.dev behind a Cloudflare Access login that admits only the owner. Nobody else can sign up, log in or connect an account, and it is not offered to anyone as a service.
Accounts and permissions
The scheduler connects only to these accounts, all owned by imperial64, and asks each platform only for the permissions below.
| Platform and account | Permissions | Used for |
|---|---|---|
X, @imperial64dev | tweet.read, tweet.write, users.read, media.write, offline.access | Publishing posts and replies with images or video; reading the posts' statistics and the follower count. |
Bluesky, @imperial64.dev | An app password | Publishing posts with images or video; reading likes, reposts, replies and quotes, and the follower count. |
Facebook, Page Imperial64dev | pages_show_list, pages_read_engagement, pages_manage_posts, pages_manage_engagement, publish_video, read_insights, business_management | Publishing posts, photos and Reels to the Page; reading the posts' statistics and the follower count. |
Instagram, imperial64dev (linked to the Page) | instagram_basic, instagram_content_publish, instagram_manage_comments, instagram_manage_insights | Publishing images, carousels and Reels, and the first comment under them; reading the posts' statistics and the follower count. |
YouTube, @imperial64dev | youtube.readonly, yt-analytics.readonly, youtube.upload | Reading the channel's videos, their view, like and comment counts and the subscriber count. Uploading Shorts to this channel; for now the owner uploads them by hand and the upload permission is not used yet. |
TikTok, @imperial64dev | user.info.basic, user.info.stats, video.list, video.upload, video.publish | Reading the account's basic details, follower count and its videos' views, likes, comments and shares. Uploading videos to this account; for now the owner uploads them by hand and the upload permissions are not used yet. |
The scheduler reads counts, not people. It does not read other users' profiles, direct messages or the text of comments, and it does not post anywhere except the accounts above.
What it stores
- Access tokens for the accounts above and the Bluesky app password, encrypted (AES-256-GCM) before they are saved. The encryption key and the platforms' app secrets are kept as Cloudflare secrets, never in the code or its repository. Tokens are never shown back by the scheduler or written to its logs.
- Account details: each account's id, handle, display name, follower count and the permissions it granted.
- Posts: the text, links, hashtags, schedule and media the owner writes, and the id and address of each published post.
- Media: the images and videos the owner uploads, kept in private storage until the owner deletes them. Instagram and Facebook have to fetch some images from a public address, so for those the scheduler makes a temporary copy under a random, unlisted name at
media.imperial64.dev. Each copy is deleted 30 minutes after the post is published, and after 4 hours at most whatever happens. - Post statistics: the numbers listed in the table above, taken at intervals for up to 90 days after a post is published, together with the platform's answer as it was returned. They are kept for as long as the owner runs the scheduler.
- Logs: a record of each call to a platform (address, status and a shortened answer, with tokens and secrets removed), deleted after 90 days.
Where it is stored
Everything above is stored on Cloudflare, Inc.: the scheduler runs on Cloudflare Workers, keeps its records in a Cloudflare D1 database in the western Europe region and keeps media in Cloudflare R2 storage. All connections use HTTPS. Cloudflare processes the data only to run the scheduler.
Who receives it
Nothing is sold, rented or used for advertising. Data leaves the scheduler only in these ways:
- A post and its media go to the platform the owner chose for that post, and only that platform.
- Short status messages, for example that a post needs attention, go to the owner's phone through the notification service ntfy (
ntfy.sh). They contain no tokens, passwords or statistics. - The owner works on the scheduler with an AI coding assistant (Claude Code, by Anthropic) that runs the scheduler's command-line tool on the owner's computer. It can see post texts and statistics reports there, and it never receives tokens or passwords.
The operator does not use the data to develop or train AI or machine-learning models.
Google API Services (YouTube)
The scheduler's use and transfer to any other app of information received from Google APIs will adhere to the Google API Services User Data Policy, including the Limited Use requirements. In particular, data from the YouTube permissions above:
- is used only to show the owner the statistics of the owner's own channel and videos and, later, to upload the owner's own Shorts to that channel;
- is not transferred to anyone else, except as needed to provide those features, to comply with the law, or as part of a merger, acquisition or sale of assets;
- is not used for advertising, and is not used to determine credit-worthiness or for lending;
- is not read by any person other than the owner, except where needed for security, to comply with the law, or with the owner's agreement.
The scheduler uses YouTube API Services. What YouTube and Google process themselves is covered by the YouTube Terms of Service and the Google Privacy Policy.
Revoking access
Disconnecting an account in the scheduler's dashboard deletes its stored tokens. Access can also be removed on each platform (menu names may differ slightly between app versions):
- X: Settings and privacy › Security and account access › Apps and sessions › Connected apps.
- Bluesky: Settings › Privacy and security › App passwords, then delete the scheduler's password.
- Facebook and Instagram: Facebook Settings and privacy › Settings › Business integrations, and in Instagram, Settings › Website permissions › Apps and websites.
- YouTube (Google): myaccount.google.com/connections, then remove the imperial64dev scheduler.
- TikTok: Settings and privacy › Security and permissions › Apps and services permissions.
To have any stored data deleted, write to hello@imperial64.dev.
Changes
If what the scheduler accesses or stores changes, for example when it starts uploading to YouTube or TikTok, this page and its policy version are updated first.