Survey Assistant

Terms of Service

Effective date: March 8, 2026

Core usage rules for Survey Assistant

These terms describe the current operating rules for participants, researchers, and platform operators using Survey Assistant. They reflect the current implementation and product policy rather than a fully expanded commercial legal package.

1. Roles and access

  • The service separates participant, researcher, and platform-operator roles.
  • Participants join surveys with anonymous-style accounts and access codes.
  • Researchers and platform operators sign in through Google and must pass role checks.

2. Free core features

  • Standard Likert template creation, package operations, participant response collection, ZIP/CSV exports, and BYOK AI chat belong to the free open-source core.
  • The purpose of this free core is to keep baseline survey operations reusable as public middleware.

3. Paid operational features

  • Special-template requests, the SkillBook store, Managed AI, credits, and subscription operations belong to the paid service layer.
  • The app already contains request and approval flows, but hosted checkout and recurring billing remain pending external gateway onboarding.

4. AI features and responsibility

  • BYOK AI uses the researcher's own API key to call external LLM providers.
  • Managed AI uses platform-provided compute resources and will follow platform credit policy.
  • AI output is assistive research material and does not replace final professional judgment.

5. Open-source publication boundary

  • Core code, documents, sanitized examples, and publishable implementation artifacts may appear in public repositories.
  • Legacy database backups, member data, access logs, and raw survey responses are outside that public boundary.
  • Special-template implementation code may be published depending on request consent and publication policy, while compensation remains a separate matter.

6. Prohibited use

  • Privilege bypass, unauthorized access, ledger tampering attempts, and sensitive-data leakage attempts are prohibited.
  • Uploading or sharing personal data or raw response data without proper basis is prohibited.
  • Abusive automation or activity that harms service stability is also prohibited.

7. Service changes and interruptions

  • Because the product is still evolving, features, policies, UI, and external integrations may change.
  • Material changes will be announced through the service UI, documentation, or operational notices.

8. Contact

  • Questions about terms, access policy, operations, collaboration, or custom work can be sent through the contact page or the email below.
  • Support email: mow.coding@gmail.com