Privacy Policy

toolulah Upload · Version 2026-10-15 · Effective 2026-10-15 · https://upload.toolulah.com/privacy

toolulah Upload (“the Service”) is a web service that helps you schedule video uploads to your own YouTube channel. If you choose, the same video is also posted at the same time to the Instagram, Facebook Page, Threads and TikTok accounts you connect. This policy explains what information the Service receives, how it is used, where and for how long it is stored, who it is shared with, and how it is deleted. The Service is operated by 박세준.

1. Use of YouTube API Services

This Service uses YouTube API Services. It calls the YouTube Data API, the YouTube Analytics API and the YouTube Reporting API to upload your videos and thumbnails to the channel you connected, to check the result of each upload, and to read that channel’s statistics when you ask for them on the Analytics page or through your personal API.

Information processed by Google is subject to the Google Privacy Policy: https://policies.google.com/privacy

Videos published on YouTube are governed by the YouTube Terms of Service.

2. Information we handle and how

The Service accesses, collects, uses and stores only the information below. You can create an account with a username and password or by signing in with Google. If you use Google sign-in, we receive only your Google account identifier, email address and name (openid, email, profile; no YouTube access is requested at that step). Channel connection is a separate consent that provides connection tokens, the channel ID and name, and the email address of the Google account used to connect.

InformationSourcePurposeStorage
Username, password, recovery email (optional)What you enter when signing upSigning in and telling accounts apart. The recovery email is used only to send password reset links, address confirmation links and address change notices (an unconfirmed address is never used for resets)Database. Passwords are never stored in plain text — only a scrypt hash
Google account identifier (sub), email address and name (only if you use Google sign-in)Google sign-in (OpenID Connect, scopes openid, email, profile)Signing in and telling accounts apart (identifier); showing which Google account you signed in with on My account (email, name). Never used to link accounts automatically, even if the email matchesDatabase. Deleted when you unlink Google or delete your account. Google sign-in access tokens are not stored
Recovery codesIssued by the Service (shown once at sign-up or when regenerated)Verifying it is you if you forget your passwordOnly a hash (sha256) is stored; used codes are marked as used
Connected YouTube channel ID and channel nameYouTube Data API (channels.list)Confirming and showing which channel videos go toService database
Email address of the Google account used to connect a channelChannel connection consent (scopes openid, email, Google ID token)Showing you, on the Channels page, which Google account each channel was connected withService database. Deleted when you disconnect the channel or delete your account
Channel nicknamesWhat you enterTelling your channels apart on screenService database
Google OAuth tokens (the refresh token issued when you connect a channel)Channel connection consent (scopes youtube.upload, youtube.readonly, yt-analytics.readonly, youtube.force-ssl)Uploading videos and thumbnails on your behalf at the time you scheduled, and reading that channel’s statistics and analytics when you ask for themEncrypted with AES-256-GCM in a separate secret store
Channel and video statistics (subscriber count, total views, video count; for recent videos: title, publish date, views, likes, comment count, duration, visibility)YouTube Data API (channels.list, playlistItems.list, videos.list), scope youtube.readonlyShown only to you on the Analytics page, and provided to your own tools through your personal API (analytics:read)Database, as a cache only (reused for 24 hours, at most 30 days)
Channel analytics (views, watch time, average view duration, subscribers gained and lost, likes, comments and shares per period; traffic sources; viewer age-group and gender shares; countries; devices — all channel-level aggregates)YouTube Analytics API (reports.query) and YouTube Reporting API (daily reports you turn on), scope yt-analytics.readonlySame as above (shown to you and provided to your own tools)Database, aggregated results cached only (reused for 24 hours, at most 30 days). Original Reporting files are aggregated in memory and discarded, never stored
Video and thumbnail files you uploadYouUploading to YouTubeServer disk (per-user folder). Deleted as soon as the upload finishes
Title, description, tags, category, language, made-for-kids setting, altered or synthetic content disclosure, visibility, scheduled timeWhat you enterSent to YouTube exactly as entered (the Service never edits or adds to it)Database, with the scheduled job
Upload results (YouTube video ID, processing status, failure reason code)YouTube Data APIShowing results in your job listDatabase, with the scheduled job
Device connection requests (tool name, hashes of the connection and device codes, approval result)The tool you connect (for example the upload factory app) and the approval page /linkDelivering a personal API token once to a tool you approvedDatabase. Codes are stored only as hashes; the token is kept encrypted until delivered and deleted immediately on delivery. Expired requests are deleted after 10 minutes
Personal API tokensIssued by youAuthenticating your own upload tools when they submit jobsOnly a hash (sha256) is stored, never the token itself
Copyright claims-mail forwarding metadata (only when enabled by you: dedicated claims-*@toolulah.com address, sender, subject, matched video ID, forwarding confirmation code, timestamps)YouTube copyright notification emails you configure Gmail/your mail provider to forward (processed via Cloudflare Email Routing & Worker)Detecting copyright claim alerts and pausing automated Publish Gate release on the affected channelMetadata only in the database (full email bodies are not stored). Deleted 90 days after resolution, and immediately upon address rotation, source removal, or account deletion
Consent records (document, version, time) and display languageYouChecking consent, showing pages in your languageDatabase
Security log (time, internal user number, hashed IP address, action, target number, result)The ServicePreventing abuse and investigating incidentsLog files. No email, names, video titles or tokens

What the Service does with each scope:

  • youtube.upload: uploads the videos and thumbnails you scheduled to the channel you connected.
  • youtube.readonly: reads the connected channel’s ID, name and statistics and the list and statistics of videos on that channel. Nothing is changed or deleted with this scope.
  • yt-analytics.readonly: reads analytics reports for the connected channel (the metrics in the table above) and, if you turn them on, creates YouTube Reporting daily report jobs and reads those reports. The Service does not request the scope for revenue and ad-earnings data (yt-analytics-monetary.readonly).
  • youtube.force-ssl: strictly for videos this Service uploaded, (1) when you press “Edit” or “Delete”, changes the title, description, tags and visibility (videos.update, reading current values once with videos.list first) or deletes the video (videos.delete); and (2) when requested by your job, channel settings or personal API call, automatically adds the video to a playlist (playlistItems.insert), uploads captions (captions.insert), updates visibility via API, or transitions a private-first video to public/unlisted after passing the Publish Gate (videos.update). Other videos on the channel are never read, changed or deleted.

The Service does not read your watch history, subscriptions or comment text, and it does not access any channel other than the ones you connected. It receives no information that identifies individual viewers (age, gender, country and device data arrive only as shares and totals aggregated by YouTube).

2-1. Social auto-posting (Instagram, Facebook, Threads, TikTok)

Only users who connect an account on the “Social accounts” page (/app/accounts) use this feature. We receive only the permissions you grant on each platform's own sign-in and permission screen.

InformationSourcePurposeStorage
IDs and names of connected accounts (Instagram professional account ID and username, Facebook Page ID and name, Threads user ID and username, TikTok open_id and display name), Meta app-scoped user IDInstagram API with Instagram Login (instagram_business_basic), Facebook Graph API (pages_show_list), Threads API (threads_basic), TikTok (user.info.basic)Confirming and showing which account a post goes to, keeping each social account connected to only one account of this Service, matching platform disconnect and deletion requestsDatabase. Deleted when you disconnect or delete your account
Access tokens (Instagram and Threads long-lived tokens, Facebook Page tokens, TikTok access and refresh tokens)Each platform's OAuth consent (instagram_business_content_publish, pages_manage_posts and pages_read_engagement, threads_content_publish, threads_delete, video.publish)Posting your video on your behalf at the scheduled time and checking the result. Not used for anything elseEncrypted with AES-256-GCM in a separate vault. Deleted immediately when you disconnect, delete your account or revoke access on the platform
TikTok creator info (nickname, username, available privacy options, whether comments/Duet/Stitch are available, maximum video length)TikTok Content Posting API (fetched each time the posting screen opens)Shown on the posting screen and used to check your choices are allowed. The username is used to build the post linkDisplay data is not stored; only the username is saved with that post record
Post settings (text, privacy, allow comments/Duet/Stitch, commercial content disclosure, share to feed)YouSent to each platform exactly as entered (the Service does not change them or add watermarks or text)Database, with the post record
Post results (post ID, link, processing status, failure reason code)Each platform's APIShowing results in your schedule listDatabase, with the post record
  • Video delivery: the server sends the video file directly to Facebook and TikTok. Instagram and Threads only support fetching the video, so while posting we give that platform an unguessable signed link that expires after 2 hours; once posting is done the link no longer opens.
  • The Service does not read follower lists or statistics of connected accounts. It reads messages only when you open the Message inbox page, and comments only when you turn on a comment auto-reply rule (below).
  • TikTok posts are subject to TikTok's Music Usage Confirmation (and the Branded Content Policy for branded content). Information processed by Meta is covered by the Meta Privacy Policy, and information processed by TikTok by the TikTok Privacy Policy.

Card posts (photo posts)

When you submit text and several photos on the “Card posts” screen (/app/cards), the Service publishes them as a photo post to the Instagram, Threads, Facebook Page and TikTok accounts you selected, at once or at the time you choose.

  • What we receive: the text, the photo files (shrunk to JPEG by your browser) and their order, the TikTok title, privacy level, comment setting and commercial-content disclosure, the publish time, and the YouTube channels you chose for “text to post yourself”. Publish results (post ID, link, status, failure reason code) are stored in the database with the post record.
  • Photo retention: uploaded photos are kept on the server disk for publishing and for the manual-posting helper (photo download), then deleted. The retention deadline is the later of the publish deadline and 7 days after creation; photos are deleted once it has passed and no publish is in progress. If you cancel a card the deadline is brought forward and the photos are deleted when no publish is in progress.
  • Publishing permissions: we publish only with the permissions you granted to each platform — Instagram instagram_business_content_publish, Threads threads_content_publish, Facebook Pages pages_manage_posts, TikTok video.publish. We request no new permissions.
  • How photos reach the platforms: all four platforms fetch photos from a URL, so during publishing only we give the platform an unguessable signed link that expires after 2 hours; the link stops working when publishing ends.
  • YouTube Community: there is no official API, so the Service posts nothing to YouTube. It only shows you, when logged in, the copy-text and photo-download helper.

Editing and deleting posts the Service uploaded

This applies only when you yourself press the Edit or Delete button in the schedule list. The Service sends the edit or delete request to the platform with the permissions below, only for posts this Service uploaded. Other posts on the same account are never read, changed or deleted.

  • YouTube (youtube.force-ssl): edit the title, description, tags and visibility; delete the video.
  • Threads (threads_delete): delete the post (Threads has no edit function).
  • Facebook Pages (pages_manage_posts): edit the video description; delete the video.
  • Instagram and TikTok offer no edit or delete after posting, so no such request is sent.
  • What is stored: only a processing record (time and result code) plus the time of the edit or delete, and the edited Facebook description. Deleting cannot be undone, so it runs only after a recent identity check (password or Google re-confirmation).

Post performance and images

For the SNS accounts you connect, we read view, reach, like, comment, share and save counts and the cover (thumbnail) image address of the posts published through this Service, using each platform's API (Instagram instagram_business_manage_insights, Threads threads_manage_insights, TikTok video.list, Facebook Page pages_read_engagement), and show them on screen. For YouTube videos we read view, like and comment counts with the existing read-only permission (youtube.readonly). Only posts between 1 hour and 30 days old are read, at most 4 times a day per post. The numbers are stored temporarily and deleted immediately when you disconnect the account.

Profile pictures of YouTube channels and SNS accounts and post thumbnails are not saved as files; only the address given by the platform is stored, and your browser loads the image directly from the platform's image servers (YouTube, Instagram, Facebook, Threads, TikTok), which may therefore receive your IP address.

The preview frame (poster) shown in your lists is a small JPEG your browser makes from one frame of the video you pick on the new schedule screen; only you can see it, and it is deleted 30 days after the related upload or post finishes.

Comment auto-replies

This applies only if you turn on a rule on the Comment auto-replies page (/app/social/replies). When a comment contains one of your keywords, the Service sends, on your behalf, a private message (DM, once per comment) and an optional public reply on Instagram, or a public reply on Threads. Permissions used: Instagram instagram_business_manage_comments and instagram_business_manage_messages (when the follow check is on); Threads threads_read_replies and threads_manage_replies. You can set a different reply rule for each post.

  • What is read: the IDs of your 5 most recent posts (plus posts that have their own rule, up to 20 posts within 30 days of posting) and, for comments and replies on them, the ID, text, time and the commenter's username. Checked every 3 minutes.
  • How it is used: comment text is used only to check whether it contains a keyword and is never stored; it is discarded from memory right after the check.
  • What is stored: for comments that received a reply, the comment ID, post ID, commenter's username, matched keyword, what was sent and the result (so the same comment never gets two replies). This is deleted automatically after 30 days. Rules (name, keywords, message text) are kept until you delete them or disconnect the account.
  • Messages sent: only the text you wrote in the rule. Commenters' information is never used for advertising, analytics or AI training, and is never shared.
  • Send material after a follow check (optional): if turned on in a rule, when the person replies to the first DM the Service checks whether they follow your account (is_user_follow_business). Followers receive the “material” text you wrote (such as a link); others receive a reminder (up to 3 follow checks and 2 reminders). Instagram shares follow status only after the person has replied.
  • Information used for the follow check: the person's Instagram-scoped ID (IGSID), the sender and time of their messages in that conversation (to tell whether they replied; message text is not read), and the follow status. Only the IGSID, the step reached (waiting, material sent, etc.), the number of checks and the time of the last DM are kept with the log for 30 days; the follow status itself is not stored. Checks stop if there is no reply within 7 days.
  • Disconnecting the account, a Meta deauthorization or data deletion request, or deleting your account removes that account's rules and log immediately.

Message inbox

This applies only when you open the Message inbox page (/app/inbox). Only when the page is opened, the Service reads the conversation list and messages (sender name or username, time, text, attachment links) of your connected Instagram accounts and Facebook Pages from the platform and shows them on screen, and also looks up the other person's name and profile picture. A reply is sent on your behalf only when you press Send. Permissions used: Instagram instagram_business_manage_messages, Facebook pages_messaging.

  • Not stored: message text and the other person's information are never written to the database or to files. To reduce repeated reloads they are kept only in server memory for about 45 seconds, separately per user. The follow check described above still does not read message text; only the Message inbox reads it, for display.
  • Replies: under platform rules a reply can be sent only within 24 hours of the other person's last message. The operations log keeps only who sent, which connection and whether it succeeded, never the content.
  • Threads, TikTok and YouTube have no DM API and are not supported.

3. How Google user data is used and limited

  • Google user data is used only to provide the features you ask for: connecting your channels, scheduled uploads, showing their results, showing your own channel statistics and analytics to you, and providing them to your own tools through a personal API token you issue.
  • Channel statistics and analytics are shown only to the user who connected that channel and are never shared with other users or third parties.
  • It is never sold, never used for advertising and never used to train AI models.
  • A person (the operator) looks at your data only when you ask, to investigate a security incident, or to comply with the law.
  • toolulah Upload’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.

4. Sharing and service providers

The Service does not sell or give your information to other companies. To run the Service, it relies on the following providers:

  • Google: channel connection and YouTube uploads. The videos you schedule and the details you enter are sent to YouTube on your instruction.
  • Meta Platforms (Instagram, Facebook, Threads) and TikTok: only when you connect that account and choose to post there, the video and post settings are sent on your instruction.
  • Oracle (Oracle Cloud Infrastructure): hosting the server and storing data.
  • Cloudflare: the network path between the internet and the server (TLS is terminated and re-established at Cloudflare) and, when you enable claims-mail monitoring, inbound forwarding and metadata parsing for dedicated claims-*@toolulah.com addresses (Cloudflare Email Routing & Worker).
  • HaiIP (Korean fixed-IP egress proxy provider): only for YouTube channels explicitly assigned an operator-provisioned Korean fixed-IP egress line, Google OAuth and YouTube API traffic for that channel routes through the fixed-IP proxy over encrypted TLS.

Information may be disclosed only to the extent required by law.

5. Cookies

  • Session cookie (__Host-sid): keeps you signed in. It expires after 12 hours of inactivity or 7 days at most. The anti-forgery (CSRF) token is tied to this session and kept on the server.
  • Language cookie (lang): remembers your display language for one year.

There are no advertising, analytics or tracking cookies, and no third-party analytics or ad scripts.

6. Retention

  • Video and thumbnail files: deleted as soon as the YouTube upload and any social posts scheduled with it have all finished. Files that were not uploaded are deleted when the upload deadline passes (default 14 days); files not used by any job after 48 hours; files of failed jobs or jobs that need checking after at most 30 days.
  • Data received from Google APIs: never kept unchanged for more than 30 days. Channel names are re-checked and refreshed every 30 days and deleted if they cannot be refreshed. Upload results (video ID, processing status) are deleted 30 days after the job ends.
  • Channel statistics and analytics: kept only as a cache. Reused for 24 hours, then refreshed or deleted (a retention cleanup that runs every 6 hours removes expired entries), and never kept longer than 30 days. Deleted immediately when you disconnect the channel or delete your account. Original Reporting files are not stored.
  • Job records (including the title, description and other details you entered): deleted together 30 days after the job ends.
  • Job event history (records of status changes): deleted after 30 days.
  • Claims-mail forwarding records: deleted 90 days after resolution, and deleted immediately when you rotate your forwarding address, remove a source, or delete your account.
  • Authorization check: for every connection, the Service confirms at least once every 30 days that the Google token can still be refreshed. If not, the connection is marked “needs reconnection” and uploads stop.
  • Google sign-in information (Google account identifier, email, name): kept until you unlink Google or delete your account. The email and name are refreshed at each sign-in.
  • Account information (username, password hash, recovery email, recovery code hashes, channel nicknames, consent records): until you delete your account. Password reset link records expire after 30 minutes and are removed when you delete your account.
  • Security log: rotated at 10 MB per file, at most 5 files; the oldest is deleted first.
  • Database backups: one per day, seven kept, oldest deleted first. Deleted information therefore disappears from backups within 7 days at the latest.

7. Deletion policy

You can delete your data at any time. When you request deletion or withdraw consent, the data is deleted within 7 days.

  1. Disconnect a channel — the “Disconnect” button on the Channels page (/app/accounts): the Service asks Google to revoke the token, deletes its stored token immediately, deletes that channel’s cached statistics, analytics and report-job records immediately, and cancels that channel’s pending jobs.
  2. Delete your account — “Delete account” on the My account page (/app/account): disconnects every channel (token revoked and deleted), revokes your personal API tokens, deletes your uploaded files and account information, and ends your sessions. This happens immediately; copies in backups disappear within 7 days.
  3. Ask by email — write to support@toolulah.com with your username. After confirming it is you, we delete the data within 7 days and let you know.
  4. Revoking from Google — if you revoke access from your Google Account as described in section 8, the Service can no longer upload to that channel. Once the Service detects the revocation, it stops uploads for that connection and deletes that connection’s token and channel information within 7 days.
  5. Disconnecting social accounts — use “Disconnect” on the “Social accounts” page (/app/accounts), remove this Service under “Apps and websites” in Instagram, Facebook or Threads settings, or revoke it in TikTok. We immediately delete that account's access token and account information and cancel posts that have not been sent. You can check the result of a Meta data deletion request with its confirmation code at /meta/data-deletion.

8. Revoking access from your Google Account

Separately from the buttons in the Service, you can revoke this Service’s access at any time from your Google Account security settings:

Select toolulah Upload in the list and choose “Delete all connections” (or “Remove access”).

9. Your rights

  • Access and export: download your data (account, connected channel details, jobs, events) as a JSON file from the My account page. Tokens and hashes are not included.
  • Correction: you can change your password and recovery email on the My account page (usernames can’t be changed). A scheduled job can be canceled and created again.
  • Deletion and withdrawal of consent: available at any time as described in section 7.

10. Security

  • All traffic is encrypted with HTTPS.
  • Google tokens are encrypted with AES-256-GCM; personal API tokens are stored only as hashes.
  • Session cookies are HttpOnly, Secure and SameSite, and every state-changing request is checked for an anti-forgery token and its origin.
  • The administration screen is restricted to authorized administrator accounts and protected by recent password re-authentication, CSRF validation, and audit logging; non-admin requests receive a 404 response.
  • Uploaded files are not served back over the web (exception: 2-hour unguessable signed links provided during publishing so Instagram and Threads can fetch videos/photos and Facebook Pages and TikTok can fetch photos/card posts). Each user can see only their own data.

11. Changes to this policy

When this policy changes, its version number goes up and every user must accept the new version before using the Service again.

12. Children under 14

We do not knowingly collect personal information from children under 14. Children under 14 may not use the Service, and we ask every user to confirm that they are 14 or older when signing up.

If we learn that we have collected personal information from a child under 14, we will delete that account and its data without delay and revoke Google access for any connected channel.

If you become aware of such a case, please contact us: 박세준 · support@toolulah.com

13. Contact

Operator
박세준 · support@toolulah.com
Privacy officer
Name: 박세준 · Contact: support@toolulah.com

Send privacy questions, complaints, and requests to access, correct or delete your data to the contact above. We reply within 10 business days.

Related: Terms of Service · Help