Schedra is built to help you run your own content workflow. This page explains what information the product touches, why it is needed, and how it may move when you use hosted or connected features.
We collect the details needed to let you sign in, keep your workspace available across sessions, and remember the setup you choose inside the app. That can include your email address, basic account profile, workspace settings, profile names, schedule data, and the metadata needed to run your library and queue views.
If you connect third-party services, we may also store connection metadata and tokens needed to keep those integrations working. Sensitive credentials are meant to stay server-side or in encrypted storage rather than being exposed to the browser.
We use your information to authenticate you, load your workspace, sync your connected profiles, and carry out the actions you ask Schedra to run. That includes imports, scheduling, queue management, and any publishing flows you explicitly enable.
We do not treat your content library as advertising inventory. Schedra is designed to help you operate your own workflow, not to sell or repurpose your content for unrelated tracking.
Schedra can display media from your machine through browser-local folder access. When you use that mode, the folder binding stays in your browser on your device. Local files are not uploaded unless you explicitly trigger a workflow that sends them elsewhere.
If you later enable remote storage or publishing destinations, only the files and metadata involved in those flows are transferred.
Schedra may rely on third-party services for hosting, authentication, email delivery, storage, DNS, and connected publishing workflows. That can include providers such as Vercel, Railway, Supabase, Cloudflare, Resend, and any social platform you choose to connect.
Those providers may process data according to their own privacy policies while acting as infrastructure or integration partners for the service.
You can disconnect providers, remove local browser bindings, rotate credentials, and request deletion of stored account data for hosted environments you control. For self-hosted deployments, you remain responsible for your own backups, retention settings, and access controls.
If you have a privacy question or need an account-data request handled for a hosted deployment, use the support or operator contact channel published for the deployment you are using.