Privacy Policy
Schedia (schedia.co) · Last updated July 31, 2026
Schedia is a production-management tool for video creators. This page explains what data Schedia stores, where it goes, and how to get rid of it.
What we store
Your account (name, email, a salted hash of your password — never the password itself) and the content you create in the app: workspaces, boards, videos, deliverables, team rosters, expense records and settings. This data exists so the app can show it back to you and sync it between your devices. If you sign in with Google or Discord instead of a password, we also store that provider's account id for you, plus the name, email address and profile picture it gives us.
We also record counts of which features get used — that a video was created or a review was opened, and how often — so we can see what the app is actually used for; these are tallies only, never the titles, notes, messages or amounts you typed, and they stay on our own hub rather than going to any analytics company.
Google (YouTube & Drive)
If you connect a YouTube channel, Schedia reads your channel's statistics
(views, subscribers, watch time, revenue) to display them to you. If you connect
Google Drive, Schedia can only see and manage files it created itself (the
drive.file scope) — it never has access to the rest of your Drive.
OAuth refresh tokens are stored server-side only and are never sent to your
browser or any third party. Disconnecting an integration deletes its token.
Two things about Drive are worth saying plainly. First, files Schedia uploads to Drive are private to the connected Google account. They only become readable by others when someone in the workspace uses "Send to editor" to hand a video's footage folder over: that sets the folder to anyone with the link can view, which means anyone who is ever given or forwarded that link can open it, whether or not they use Schedia. Second, the same action gives edit access to the team members you are handing the footage to, and to do that it sends their email addresses to Google as permissions on your folder. Google will hold those addresses. Both are shown in the app before you hand a folder over. You can undo either at any time in Google Drive's own sharing settings.
Schedia's use of Google user data complies with the Google API Services User Data Policy, including the Limited Use requirements.
Discord
If a workspace is connected to Discord, the bot reads only the channels Schedia is tracking. A channel created in Discord is never tracked on its own: it is ignored until you add it in the app, and a server the bot merely sits in is never read. The exception is a server Schedia builds for you — if you ask Schedia to build or sync your Discord server, the channels it creates for that workspace (per-person, per-role, #general, #scheduling, group chats) are tracked from the moment they are made, because making them is you asking for them. You can untrack any of them in the app.
From those tracked channels the bot stores the message text, the author's Discord user id, timestamps, attachments and link previews, reply context, and reactions (the emoji, the count, and up to 24 of the user ids who reacted). Stored messages are deleted automatically after 90 days. Images posted in a tracked channel are copied to our server, because Discord's own image links expire after about a day. Those copies are deleted too, 90 days after the last time anything in the app referred to them — so an image still in use on a card stays, and one nothing has touched for 90 days goes.
If you link a Discord server to a workspace, the bot also records who joins and leaves it — Discord user id, username, display name, avatar picture, the role they pick, and the join and leave times — so the app can build your team roster. If a team member sends the bot a direct message asking to be paid, the amount and the note they wrote are stored as a payment request for the workspace owner. Direct messages are not otherwise stored.
AI channel summaries (beta, off by default)
Schedia can write a one-line summary of what's happening in a tracked channel. This is the only feature that sends Discord message text off our server: it goes to Anthropic (Claude) to produce the summary. It is off by default and stays off until the hub owner turns it on in Settings. While it is off, no message content is sent to Anthropic or to anyone else. When it is on, what gets sent is the recent messages of the channel being summarised (up to 40 messages) with each author's display name.
Email-confirmation links, password-reset links and "a new device signed in" notices are sent through Resend, our email provider. They receive your email address and the contents of that message. Nothing else is emailed, and the Discord bot never sends reset links.
Hosting
Schedia runs on Railway, and its data is stored in a Railway-hosted Postgres database and disk volume. Railway hosts the data; they are not given it for any purpose of their own.
Trello
If you point a workspace at a Trello board, Schedia reads that board to mirror it in the app. The mirror is read-only — Schedia never writes anything back to Trello.
What we don't do
Schedia does not sell or rent your data. There is no advertising, no third-party analytics and no tracking scripts in the app. Your data is not used to train any AI model. Apart from Anthropic for the opt-in summaries above, Resend for those emails, and Railway for hosting, data is only sent to the services you choose to connect (Google, Discord, Trello) as needed to make those features work.
Deleting your data
Disconnect integrations at any time in Settings; disconnecting deletes that integration's stored token. You can delete your own account from Settings — it asks for your password, signs you out everywhere, and stops any workspace you own being shared with anyone.
Your data is then kept for 30 days before it is erased. That window exists so that a deletion nobody meant, because of a shared password or an account someone else got into, is not the end of a team's work. During it your account cannot be signed into, and nobody you shared a workspace with can reach it. We email the account's address a single-use link that undoes the deletion and puts everything back; it works once, and only within those 30 days. After 30 days your account, app data, archive, uploaded images and any subscription record are deleted permanently and we cannot get them back.
The workspace owner's account holds the hub's own data and can't be self-deleted that way; owners, and anyone who wants the Discord side wiped or wants their data erased sooner than 30 days, can email [email protected]. Removing the bot from a Discord server, or untracking a channel, stops any further collection from it.