Contact Us
Canvas Cat is currently in active build and rollout. The best contact path for project questions, access requests, partnership interest, or early-user communication should route through the primary project contact methods connected to this site.
For product questions, account concerns, automation requests, or setup help, use the support and contact channels linked from this site as they become active. As the platform matures, this section can be expanded with a direct support email, form, and response expectations.
Best for
General questions, product interest, onboarding requests, and account follow-up.
Future additions
Dedicated support form, billing contact path, and technical issue intake.
Support
Support for Canvas Cat is intended to focus on practical help: connecting Canvas, understanding automation settings, managing rules, resolving worker or cron issues, and answering platform-use questions.
As support tooling expands, users should expect help topics such as account setup, Canvas API connection issues, automation troubleshooting, background job behavior, and dashboard access. Support may eventually include a ticket form, help articles, and guided onboarding for new customers.
- Connection help for Canvas accounts and tokens.
- Guidance for creating and editing automation rules.
- Troubleshooting for worker runs, cron timing, and job execution.
- Billing and subscription support as paid plans expand.
FAQ
What is Canvas Cat?
A Canvas-focused automation platform designed to help instructors reduce repetitive course-management work.
Who is it for?
Primarily instructors and educational users who manage recurring Canvas tasks across one or more courses.
What kinds of tasks will it help with?
Quiz workflows, discussion workflows, automation rules, and other repeatable Canvas actions managed from a dashboard.
Does it run jobs automatically?
Yes. The platform is being built around background worker processes so jobs can run on schedule without manual intervention.
Will there be subscriptions?
Yes. The project is being organized with account structure and subscription billing in mind as it grows into a SaaS offering.
Is Canvas Cat affiliated with Canvas or Instructure?
No. Canvas Cat is an independent tool and is not affiliated with or endorsed by Instructure, Inc.
Privacy Policy
Canvas Cat is designed to use only the account access and course information needed to deliver the requested automation features. The platform is intended to handle instructor data, course settings, and automation-related records with care and restraint.
The project goal is to avoid unnecessary collection, avoid selling user data, and limit access to the minimum information required for account management, job execution, billing, and support. Stored information may include account details, automation settings, job history, and technical records used to keep the service running.
As the system matures, this section should be updated with a formal production privacy policy covering data retention, third-party services, billing providers, support access, and security practices in plain language.
Terms of Service
By using Canvas Cat, users agree to use the platform in a lawful and responsible way and to provide accurate information needed for account setup, subscription management, and automation configuration.
Users remain responsible for how they choose to use the platform within their own institution, course environment, and Canvas account. Canvas Cat is intended to assist with workflows, not to override institutional policy, academic policy, or local approval requirements.
As paid plans and broader access are added, formal terms should define service scope, account responsibilities, billing terms, acceptable use, limitation of liability, and conditions for suspension or termination.
Acceptable Use
Canvas Cat must be used in ways that support legitimate educational workflows and respect institutional rules, student protections, and the intended purpose of Canvas-connected automation.
- Do not use the platform to violate school, district, university, or LMS policies.
- Do not use automation to harass, mislead, spam, or overwhelm students or instructors.
- Do not attempt to use the service to gain unauthorized access to courses, accounts, or data.
- Do not misuse API access, background jobs, or rule systems in ways that create instability or abuse.
- Do not use the platform for unlawful activity or activity that undermines academic integrity or platform trust.
Accounts that misuse the service may be limited, suspended, or removed in order to protect users, connected systems, and the platform itself.
Accessibility
Canvas Cat is being built with a preference for clear layouts, readable text, simple navigation, and straightforward instructor-facing pages. The project aims to support accessible use across common devices and screen sizes while keeping interfaces uncluttered and practical.
As development continues, accessibility work should include keyboard-friendly navigation, sensible color contrast, informative labels, logical page structure, and continued improvement of interactive dashboard components.
Security
Security is central to a tool that connects to instructor accounts and course systems. Canvas Cat is intended to store credentials, tokens, and account-related settings in a protected manner and limit exposure of sensitive data wherever possible.
The platform architecture is moving toward secure account separation, controlled admin access, protected login flows, and safer handling of automation rules, job logs, and billing-related records. As the SaaS expands, this section should be updated with formal details about encryption, credential handling, backups, access control, monitoring, and incident response.
Focus areas
Account protection, token handling, login security, job integrity, and safer admin workflows.
Planned growth
Subscription-aware account security, stronger audit visibility, and clearer production security documentation.
System Status
Canvas Cat is in an active build stage. Core dashboard functions, account work, rule creation, and worker-based automation features are being developed and expanded. Some pages, help materials, and public-facing documentation may still change as the system evolves.
During this stage, users should expect iterative improvement. Features may be added, refined, reorganized, or expanded as real workflows are tested. A more formal public status page can be added later if you want separate uptime, maintenance notices, and service alerts.