Privacy Policy
Effective date: November 20, 2026
1. Who operates the app
StreamAutomation by AyDeA ("the app") is a private publishing tool operated by Anthony Ambot, who creates content as AyDeA ("the operator"). The app publishes highlight clips from the operator's own gaming livestreams to the operator's own social media accounts. It has no public sign-up and is not offered to other users.
2. Whose data the app handles
The app handles data about the operator's own accounts and the operator's own videos. It does not request access to, collect or process data about viewers, followers, commenters or any other person's account.
Stream recordings and clips can contain the operator's voice, webcam image and gameplay. They may also capture anything audible or visible during a stream, such as another person speaking nearby. Before a clip can be approved, an automated privacy screen and the operator's own review check it, and flagged clips are held back from publishing.
3. Where data is processed and stored
| Data | Where | Details |
|---|---|---|
| Raw stream recordings | Operator's computer, then Dropbox (cloud) | Recordings are uploaded to the operator's own Dropbox account for archiving. The app checks each upload against Dropbox's content hash. The local copy is deleted automatically about 2 hours after the archive copy is verified (the two most recent recordings are always kept). The app never deletes anything from Dropbox. |
| Generated clips, subtitles, cover images and clip metadata | Operator's computer | Created and stored locally. They are not currently archived to Dropbox. Copies of approved clips are uploaded to the publishing platforms listed below. |
| Highlight analysis (transcripts, scores, the privacy screen, review decisions) | Operator's computer | Processed with software and models that run on the operator's computer, and kept in local databases. No third-party AI or clipping service currently receives recordings or transcripts. |
| Publishing records | Operator's computer (local database) | For each publish attempt: clip, destination platform, time, the platform's video or post ID, URL, processing status, restriction or error messages, and the file's checksum. The app also keeps a local append-only log of upload receipts (the platform IDs of upload sessions, used to prevent duplicate posts) and a record of the operator's explicit authorizations for individual posts. |
| Account identifiers | Operator's computer (local database and macOS Keychain) | Used to confirm the destination account before every upload: YouTube channel ID, Facebook Page ID, Instagram account ID, TikTok open ID and display name. |
| Authorization credentials | macOS Keychain on the operator's computer | OAuth refresh tokens, Page access tokens and app credentials. They are not written to project files or logs and are never shown in the app's output. |
| Application logs | Operator's computer | Operational logs about uploads, archiving and publishing, rotated automatically by size (older log files are overwritten). Credentials are removed from log output. |
4. Third-party services
Data leaves the operator's computer only to these services, and only to the operator's own accounts:
- Dropbox: archive of raw stream recordings.
- YouTube (Google), Facebook and Instagram (Meta), TikTok: approved clips, with their titles and captions, are uploaded to publish them, and the app reads back processing status. These services handle the data under their own privacy policies.
The app has no server of its own, shows no ads, uses no analytics or tracking scripts, and does not sell or share data with anyone else. This website itself sets no cookies and runs no analytics or tracking scripts.
5. Permissions the app requests
| Platform | Permission | Used for |
|---|---|---|
| YouTube | youtube.upload | Uploading approved clips to the operator's channel. Uploads are private first, and the operator makes them public. |
| YouTube | youtube.readonly | Confirming the authorized channel, checking for duplicate uploads, reading processing status. |
| pages_show_list, pages_read_engagement, pages_manage_posts, business_management | Finding the operator's Page, checking for duplicate posts, uploading approved Reels. | |
| instagram_basic, instagram_content_publish | Confirming the operator's Instagram professional account and publishing Reels the operator has approved. | |
| TikTok | user.info.basic | Confirming the authorized TikTok account (open ID, display name, avatar). |
| TikTok | video.upload | Sending approved clips to the operator's TikTok inbox as drafts. |
6. Analytics (not active)
The app does not currently collect performance analytics such as views or watch time. If that is added later, for example reading statistics for the operator's own posts through the platforms' APIs, this policy will be updated first to describe what is collected, which extra permissions it needs, where it is stored and how long it is kept.
7. Retention
- Local raw recordings: deleted about 2 hours after their Dropbox archive copy is verified.
- Dropbox archive: kept until the operator deletes it. The app never deletes from Dropbox.
- Generated clips, local databases and publishing records: kept until the operator deletes them. Publishing records are kept on purpose, so that the same clip is never uploaded twice.
- Logs: overwritten automatically as they rotate.
- Credentials: kept in the Keychain until the operator revokes or deletes them, or the platform expires them.
- Published videos: stay on each platform until the operator deletes them there.
8. Access, revocation and deletion
- The app's data is accessible only to the operator, on the operator's computer and the operator's own Dropbox and platform accounts.
- Access can be revoked at any time in each platform's settings: Google Account → Security → Third-party connections; Facebook → Settings → Business integrations; Instagram → Settings → Apps and websites; TikTok → Settings → Security → Manage app permissions; Dropbox → Settings → Connected apps.
- The operator can delete the stored credentials from the macOS Keychain, and delete local databases, clips and logs, at any time.
9. Security
Credentials are kept only in the macOS Keychain and removed from logs. All transfers use the platforms' official HTTPS APIs, and archive uploads are checked by content hash. No method of storage or transmission is completely secure.
10. Children
The app is not directed at children and does not collect data from children.
11. Changes
Changes will be posted on this page with a new effective date before they apply.