Beta Tester Agreement

The Hyparrow Beta Testing Programme ("Programme") is an invitation-based programme where selected testers help us identify bugs, usability issues, and areas for improvement across the Hyparrow Platform before features are released to the general public.

By participating in the Programme, you agree to the terms outlined in this agreement in addition to the general Hyparrow Terms & Conditions and Privacy Policy. In the event of a conflict, this agreement takes precedence for matters specific to beta testing.

Beta Testers must have an active Hyparrow account and be approved by the Hyparrow team. Enrollment may be by invitation or application. We reserve the right to accept or decline any applicant without providing a reason.

Upon enrollment, you will receive access to the beta testing dashboard where you can submit observations, track their status, and view your earnings.

An "Observation" is a report submitted by a Beta Tester describing a bug, usability issue, broken feature, or improvement opportunity discovered while using the Hyparrow Platform. Each observation is assigned a unique tracking code (e.g., HB-A3X9K2) for reference.

A complete observation includes: (a) A clear, descriptive title; (b) A detailed description of the issue; (c) Step-by-step instructions to reproduce the bug; (d) At least one screenshot, video recording, or supporting attachment; (e) A severity level assessment by the tester; (f) An optional improvement suggestion.

Observations can be saved as drafts before submission. Once submitted, they enter our review pipeline and cannot be modified by the tester.

Every observation requires a severity level — your honest assessment of how serious the issue is. Our admin team independently verifies and may adjust the severity during review. The final (admin-assigned) severity determines the reward amount.

We use four severity levels:

Definition: Minor visual or cosmetic issues that do not affect functionality.

Examples: (a) Misaligned text, icons, or spacing inconsistencies; (b) Typos or grammatical errors in labels or messages; (c) Minor colour or font inconsistencies between pages; (d) Tooltip not displaying correctly; (e) An image slightly cropped or pixelated.

Impact: The Platform works correctly. The issue is noticeable but does not hinder any user action or workflow.

Reward: ₦1,000 per verified observation.

Definition: The feature works but with noticeable issues that degrade the user experience.

Examples: (a) A form submits successfully but shows a confusing or incorrect success/error message; (b) A page loads slowly or requires an extra refresh to display data; (c) Dropdown menu options are missing or in the wrong order; (d) Pagination not working correctly (e.g., showing wrong total count); (e) A filter or search feature returns incomplete results; (f) Dark mode inconsistencies where some elements don't theme properly.

Impact: Users can still complete their task, but the experience is confusing, slow, or requires workarounds.

Reward: ₦3,000 per verified observation.

Definition: A feature is significantly broken or a core workflow fails.

Examples: (a) Unable to complete a payment, transfer, or invoice creation; (b) Profile update fails silently or returns a 500 error; (c) Uploaded documents not saving or appearing blank after upload; (d) Wallet balance shows incorrect amount; (e) Notifications not being delivered; (f) API keys not generating or not working after creation; (g) Checkout page failing to load for customers.

Impact: Users are blocked from completing an important action. The feature does not work as intended and there is no reasonable workaround.

Reward: ₦5,000 per verified observation.

Definition: App crashes, data loss, security vulnerabilities, or financial discrepancies.

Examples: (a) Application crash or blank/white screen that requires force-restart; (b) Data loss — user data, transactions, or documents disappearing; (c) Security vulnerability — ability to access another user's data, bypass authentication, or exploit API endpoints; (d) Incorrect money movement — wrong amounts debited/credited, duplicate charges, or funds lost in transit; (e) Payment processed but transaction not recorded; (f) Able to perform actions without proper authorisation (e.g., accessing admin features as a regular user).

Impact: The issue causes or risks causing financial loss, data breach, or makes the Platform completely unusable. Requires immediate attention.

Reward: ₦10,000 per verified observation.

After you submit an observation, it goes through the following stages:

Submitted: Your observation has been received and is in the review queue. A Hyparrow team member will review it within 1–5 business days.

Reviewed: An admin has examined your report. If the issue is valid, the admin assigns the final severity level (which may differ from your initial assessment). If the observation is a duplicate, not reproducible, or outside scope, it may be dropped with an explanation.

Fixed: The issue has been resolved in the Platform. Once marked as fixed, a reward is calculated based on the admin-assigned severity.

Dropped: The observation was reviewed but not accepted. Common reasons include: duplicate of an existing report, cannot be reproduced, works as intended, or outside the scope of the current beta.

You will receive feedback from the admin team at each stage. You can view all updates and admin feedback on your observation detail page.

Rewards are earned when your observation is verified, assigned a severity level by an admin, and the issue is marked as fixed. The reward amounts are:

Low Severity: ₦1,000 | Medium Severity: ₦3,000 | High Severity: ₦5,000 | Critical Severity: ₦10,000

The final reward is based on the admin-assigned severity, not the tester's initial assessment. If an admin upgrades the severity of your observation, you earn the higher reward. If they downgrade it, the lower reward applies.

Earned rewards accumulate as pending earnings. Pending earnings are approved by the admin team and then credited to your Hyparrow merchant dashboard wallet bi-weekly (on the 1st and 15th of each month). You can track your total earnings, pending amounts, and payout history on the Earnings page.

Hyparrow reserves the right to adjust reward amounts, payout schedules, or the reward structure at any time with notice to active testers.

To ensure your observations are accepted and processed quickly: (a) Be specific — describe exactly what happened, what you expected, and what went wrong; (b) Provide clear steps to reproduce — another person should be able to follow your steps and see the same issue; (c) Attach evidence — screenshots or screen recordings are required. Annotate screenshots to highlight the issue when possible; (d) One issue per observation — do not bundle multiple unrelated bugs into a single report; (e) Search before submitting — check if the issue has already been reported to avoid duplicates; (f) Be honest about severity — inflating severity does not increase rewards, as the admin team independently verifies all severity assessments.

Low-quality observations (vague descriptions, no reproduction steps, no attachments) may be dropped without reward.

As a Beta Tester, you agree to: (a) Test the Platform honestly and in good faith; (b) Report issues through the official observation submission system, not through social media or public channels; (c) Not intentionally introduce bugs, exploit vulnerabilities, or perform destructive actions on the Platform; (d) Not use beta testing access to gain unfair advantage, extract data, or harm other users; (e) Keep confidential any unreleased features, internal tools, or non-public information you encounter during testing; (f) Not share your beta testing access credentials with others; (g) Use only test data and sandbox environments where instructed — do not test on production accounts with real funds unless explicitly told to do so.

During the Programme, you may encounter unreleased features, internal processes, or proprietary information. You agree to treat all such information as confidential. You may not disclose, publish, blog about, share on social media, or otherwise make public any information about unreleased Hyparrow features or internal systems without prior written approval.

This confidentiality obligation survives the termination of your participation in the Programme.

All observations, bug reports, improvement suggestions, and other content you submit through the Programme become the property of Hyparrow. You grant us an irrevocable, perpetual, royalty-free licence to use, modify, and incorporate your feedback and suggestions into our products and services.

You retain ownership of any original screenshots or recordings you create, but grant us a non-exclusive licence to use them internally for debugging, quality assurance, and product development.

We may remove you from the Programme at any time if: (a) You violate these terms or the general Hyparrow Terms & Conditions; (b) You submit fraudulent or fabricated observations; (c) You disclose confidential information; (d) You engage in destructive testing that harms the Platform or other users; (e) We discontinue the Programme.

Upon removal, any pending (unpaid) rewards for verified observations will still be honoured. Unverified or in-review observations at the time of removal may not be processed.

You may voluntarily leave the Programme at any time by contacting us at Info@hyparrow.com.

Beta features may be unstable, incomplete, or contain known issues. By participating in the Programme, you acknowledge that: (a) Beta features are provided "as is" without any warranties; (b) You may experience bugs, crashes, data inconsistencies, or service interruptions; (c) Hyparrow is not liable for any loss, damage, or inconvenience arising from your use of beta features; (d) You should not rely on beta features for production or critical business operations unless explicitly instructed.

Your participation in the Programme is subject to the Hyparrow Privacy Policy. In addition to standard data collection, beta testing involves: (a) Collection and storage of observation reports, screenshots, videos, and voice messages you submit; (b) Tracking of your testing activity, submission history, and earnings; (c) Admin review of your submitted content.

Observation data is retained for the duration of the Programme and for two (2) years after completion for quality assurance purposes.