Overview
schedbuilder is primarily a consumer planning product. Most users create personal schedules for themselves. This page summarizes how we process data when you use our cloud features on behalf of yourself or your organization.
Roles
For individual accounts, schedbuilder acts as the data controller. For Teams or organizational use (when available), your organization may act as the controller andschedbuilder as a processor for schedule content stored in our cloud database (Supabase, hosted in secure data centers).
Sub-processors
We rely on Supabase (database and auth), Stripe (payments), and Google (optional OAuth and calendar sync) to deliver the service. A current list of processing activities is described in our Privacy Policy.
Security measures
We implement HTTPS encryption, authenticated access, row-level security on database tables, and least-privilege API access. Schedule data is scoped to the account that created it unless explicitly shared via share links you generate.
Data subject requests
Users may request access, correction, or deletion of personal data by emailing schedbuilderofficial@gmail.com. Organizations with specific DPA requirements may contact us for a custom agreement as Teams features roll out.
Contact
Data protection inquiries: schedbuilderofficial@gmail.com