These terms cover access to the Schedra web app, hosted dashboard, and connected scheduling features. They are written to support a product built around user-owned workflows and connected services.
Schedra is a scheduling and workflow product for people and teams managing their own content, profiles, queue, and publishing process. By using the service, you agree to use it lawfully and only with content, accounts, databases, and media you are allowed to control.
You are responsible for the setup you provide, including workspace settings, database connections, provider credentials, upload targets, and local folder bindings.
You are responsible for keeping your sign-in methods, connected provider accounts, API credentials, and publishing destinations secure. If you believe a connected account or secret has been compromised, rotate or revoke it immediately.
Schedra may depend on third-party services such as Supabase, Vercel, Railway, Cloudflare, Resend, storage providers, and connected social networks. Their availability, terms, rate limits, and policies can affect how the service behaves.
You remain responsible for the content you import, schedule, attach, upload, or publish through Schedra. You must make sure you have the rights to use that content and that your use complies with platform rules, local law, and any obligations you owe to clients, collaborators, or rights holders.
You may not use Schedra to abuse third-party services, evade platform restrictions, distribute unlawful material, or interfere with the operation of the service or another user’s environment.
Schedra may change over time, and some features may still be in beta or under active development. Features can be added, changed, limited, or removed as the product evolves.
The service is provided on an as-is and as-available basis. To the fullest extent permitted by law, we do not guarantee that every workflow, integration, or deployment path will remain uninterrupted or error-free.
Access may be limited or suspended if the service is used in a way that creates security risk, violates these terms, or harms the platform or its connected providers. Self-hosted users remain responsible for their own uptime and operational controls.
These terms may be updated as the service matures. Material changes should be reflected on this page along with a revised update date.