BizNavi Hub

Tester Terms

BizNavi Hub · Operator: Sekimosoft合同会社 · Last updated: 2026-08-28

1. Tester program agreement

These Tester Terms apply when you apply to, are approved for, or participate in a BizNavi Hub tester program operated by Sekimosoft合同会社. They supplement the Terms of Service and Privacy Policy.

Tester programs are product- and language-specific. Certification limits apply per product and recruitment locale. Meeting application requirements does not guarantee approval or certification.

2. Application data and eligibility

When you apply, you must provide accurate information including contact email, country, preferred language (matching the program’s recruitment locale), platform, device, OS version, occupation or use case, and your reason for testing.

  • For Android programs, you must supply a valid Google Play account email when required. This may differ from your contact email.
  • You must accept these Tester Terms and consent to privacy processing at submission.
  • Duplicate applications to the same program, unsupported locales, ineligible countries, or closed programs will be rejected.
  • Only one active application per program per user unless we explicitly allow otherwise.

3. Human review and decisions

Applications pass through human review. We may approve, reject, or request clarification. Rejection reasons may be recorded internally and, where appropriate, summarized to you.

Approval does not equal certification. After approval, you enter a testing phase subject to missions, reporting, surveys, and final certification review.

4. Google Group provisioning (Phase 1)

Approved testers may require access to a Google Group or similar distribution channel for test builds. In Phase 1, provisioning uses MANUAL_FALLBACK: administrators mark provisioning jobs success or failure after manual steps. Automated Google Workspace Admin SDK provisioning (AUTO_MODE) is not enabled without separate Operator authorization.

We use the Google Play account email or contact email you supplied for provisioning as applicable. Real group addresses are configuration data and are not published on public pages.

5. Missions, reports, and surveys

  • Assigned missions must be started and completed honestly within stated expectations.
  • Test reports must use structured fields and must not include prohibited PII or secrets (see Privacy Policy).
  • Screenshot upload may be disabled in early phases; follow on-screen instructions.
  • Final surveys (and other required surveys) must be completed before certification review where marked required.
  • Submitting a PASS report does not require discovering a bug; accurate completion of assigned testing is sufficient unless a program states otherwise.

6. Certification and limits

Certification requires, where applicable: completion of required missions, submission of required reports, completion of required surveys (including final survey), and human certification review.

Certification limits count active certified testers per product and language—not the number of applications. When a limit is reached, new certifications may be paused even if applications remain open or testing continues for existing participants.

7. Hub benefit records

Upon certification, the Platform may create a benefit grant record showing product, active status, start date, end date, and duration in years (as configured for the program, typically up to the stated maximum).

  • Benefit records are maintained in BizNavi Hub for tester recognition and operational tracking only.
  • They do not automatically grant, extend, or revoke paid app entitlements, Play Billing subscriptions, or store purchase rights.
  • Any separate promotional or paid access is governed by product-specific terms outside this Platform.

8. Lifecycle: inactive, suspension, reactivation, revocation

  • Certified active testers may enter survey-requested lifecycle stages (for example, survey requested, reminder, grace period) leading to certified inactive status if ongoing obligations are not met.
  • Ordinary missed survey follow-up does not automatically revoke certification; inactive status and reminders are used before stronger measures unless a serious violation occurs.
  • Administrators may suspend certification and benefits for policy violations, abuse, or security concerns. Suspension is distinct from inactive status due to survey non-response.
  • Reactivation may be granted when administrators determine policy allows, restoring active certification and benefit records where applicable.
  • Revocation is reserved for serious or repeated violations and may end certification and benefits. Revocation reasons are recorded in audit logs.

9. Distinction from CAMPFIRE and Founder programs

CAMPFIRE crowdfunding support, Founder benefits, and similar campaigns are separate from BizNavi Hub tester certification. Supporting a campaign or holding a Founder role does not substitute for tester application, approval, missions, reports, surveys, or certification under these Tester Terms.

10. Tester conduct and termination

You must not share confidential build access, circumvent certification limits, impersonate other testers, or access other users’ applications, missions, reports, or surveys. We may withdraw, suspend, or revoke tester status for violations.

You may withdraw from a program where withdrawal flows are available; previously submitted data and audit history may be retained as described in the Privacy Policy.

11. Program and terms changes

Programs may be paused, closed, or changed (including certification limits, missions, and benefit duration). Material Tester Term changes will be posted on the Platform. Continued participation after effective date constitutes acceptance where permitted by law.