Terms of Service

§1 Platform Overview

VetterPlaces is a matching platform connecting software developers ("Developers" or "Providers") with beta testers and content creators ("Testers" or "Creators") for product testing, feedback, and promotional campaigns.

§2 User Roles & Eligibility

§2.1 Beta Testers & Content Creators

• Must be at least 16 years old
• Must have a valid GitHub account (for beta testers)
• Must provide accurate profile information
• Responsible for maintaining platform access credentials

§2.2 Developers & Providers

• Must represent a legitimate software development project or company
• Must have legal authority to issue software licenses
• Responsible for campaign content, reward fulfillment, and legal compliance
• Must not use platform for fraudulent or misleading purposes

§3 Data Processing and Consent

§3.1 Consent Requirement

GitHub and profile-based feature processing is optional and requires explicit consent where applicable:

• You must actively grant consent before consent-based feature processing starts
• Without consent, consent-gated features are unavailable
• You can revoke consent via platform controls where provided

§3.2 Data Collection Scope

Where consent is required and granted, we may process:

• candidate-provided handles and source links
• aggregate GitHub statistics for profile visibility
• candidate-provided structured timeline (Gantt) data

§3.3 No Automated Candidate Decisions

• VetterPlaces does not make fully automated hiring or admission decisions in MVP
• Recruiters and providers are responsible for their own human decisions
• Platform metrics are supporting information only

§3.4 Data Visibility

• With Active Consent: Authorized users can view permitted profile/statistics data within role scope
• After Revocation: Access and processing scope are reduced according to policy and legal obligations
• No Scope Creep: Data access remains bound to explicit purpose and permissions

§3.5 Delivery to Unframed Bit

• Where a tester or creator has granted outbound delivery consent in Vetter, Vetter may supply their Vetter-managed profile data to Unframed Bit as an authorized downstream recipient.
• A registration in Unframed Bit is not required: the consent granted in Vetter is sufficient.
• Unframed Bit is a separate product layer; it does not supply its locally maintained profile data back into Vetter.
• Vetter remains the source system and consent authority for Vetter-origin data delivered to Unframed Bit.
• Vetter does not ingest, read, or depend on data that a user enters locally in Unframed Bit.

§3.6 Developer Portfolio Statistics (VetterStats GitHub App)

To compute developer portfolio statistics, VetterPlaces connects to authorised GitHub repositories via the VetterStats GitHub App (slug vetter-stats, GitHub App ID 3110901).

• The app operates with read-only permissions: repository contents (commit metadata, file-extension distribution), pull requests, and issues
• No source code content is read, transmitted, or stored — only statistical metadata (commit timestamps, file-extension counts, PR counts, issue counts)
• Installation of the GitHub App is voluntary; portfolio statistics are unavailable without it
• You can revoke the GitHub App installation at any time from your GitHub account settings — this immediately stops any further repository access
• Generated statistics may be delivered to Unframed Bit where the developer has enabled outbound delivery consent

§4 Beta Testing Campaigns

§4.1 Application Process

• Testers apply to campaigns based on interest and skills
• Developers select testers at their discretion
• Application does not guarantee selection

§4.2 Testing Responsibilities

Testers agree to:

• Provide honest, constructive feedback
• Report bugs and issues promptly
• Respect confidentiality and non-disclosure agreements (if applicable)
• Use test products for evaluation purposes only

§4.3 Rewards & Compensation

• Rewards (licenses, discounts) are issued at developer's discretion
• Reward details are specified in campaign descriptions
• Rewards are non-transferable unless stated otherwise
• Platform is not responsible for reward fulfillment disputes (handled between developers and testers)
• If an accepted campaign is cancelled, affected participants will be informed and already-earned value is handled under the published reward policy.
• If all accepted participants are still at zero points and no accepted work is awaiting review, a campaign may be cancelled without compensation.

§4.4 Beta Test Access and Confidentiality

When a tester receives access to a beta artifact (download link, test URL, login credentials, or store link), a project-specific confidentiality gate may apply depending on the nature of the artifact (see §4 and Privacy Notice §9). Where required, testers must confirm a per-project agreement before access is revealed.

Testers additionally agree to:

• Credential confidentiality: Any login credentials issued for testing are strictly personal. Sharing credentials with third parties is a violation of these Terms.
• Source code confidentiality: Where beta access exposes partial or full source code (e.g. packaged extension archives, pre-release wheels, CLI binaries), the tester treats it as confidential and will not copy, share, or publish it without explicit written permission from the developer.
• Tracking awareness: Beta use may involve telemetry and usage logging by the developer and/or VetterPlaces. Details are disclosed in each project's access agreement and in the Privacy Notice.
• Consequences of misuse: Misuse (credential sharing, source leaking, abuse of test access) may result in immediate access revocation by the developer, permanent suspension from VetterPlaces, and potential civil or criminal liability.

The confidentiality gate is not required for artifacts that are already freely and publicly accessible (e.g. a publicly listed stable Marketplace extension, a publicly available PyPI package, or a test URL confirmed by the developer as fully public with no login). The platform evaluates this server-side based on project configuration.

§5 Developer Responsibilities

§5.1 Campaign Creation

• Provide accurate campaign descriptions, requirements, and reward details
• Ensure products are safe, legal, and functional
• Comply with intellectual property and licensing laws

§5.2 Tester Selection

• Select testers fairly and based on campaign requirements
• Do not discriminate based on protected characteristics
• Only view GitHub data of testers who have granted active consent
• Notify pending and accepted participants if a campaign is cancelled after applications were received
• Do not use campaign cancellation to avoid already-earned reward, review, or compensation obligations
• A no-compensation cancellation after acceptance is allowed only in the narrow zero-point case defined by platform policy

§5.3 Data Usage

• Use candidate data only for permitted campaign/recruiting workflows
• Do not share, sell, or misuse tester personal information
• Respect consent and exclusion settings at all times

§5.4 GitHub Issue Integration (Proxy Mode)

If you enable GitHub issue integration for a project (including Proxy mode for private repositories), you agree that:

• You have the rights/permissions to connect the specified repository and to create issues there
• You will provide a least-privilege token (recommended: fine-grained PAT limited to the repository with Issues: Read/Write and Metadata: Read-only)
• You are responsible for keeping the token secure and for revoking/rotating it if needed
• You understand VetterPlaces may create/update issues in your repository to reflect tester reports and status changes
• You understand enabling proxy mode is intended to keep testers from requiring collaborator access to your private repository

§5.5 Test Access Credentials

Where a developer provides test login credentials for testers (general or personal), the developer agrees:

• The developer is fully responsible for the accuracy and validity of the credentials they provide.
• Credentials must have an expiry date. The platform enforces a maximum validity of 90 days per credential set.
• The developer must revoke credentials promptly if misuse is suspected. The platform also auto-revokes credentials when a tester's account status changes to rejected or blocked.
• The developer confirmation action at credential entry is logged by the platform (timestamp and IP) as part of the accountability record. See the Privacy Notice for retention details.
• Credentials are stored encrypted at rest by the platform. The platform does not log or expose plaintext passwords outside the defined visibility window.
• Developers must not provide credentials that grant access beyond the scope of the beta test.

§6 Prohibited Conduct

All users must NOT:

• Engage in fraud, scams, or deceptive practices
• Harass, threaten, or abuse other users
• Violate intellectual property rights
• Upload malware, viruses, or harmful code
• Scrape, data-mine, or reverse-engineer platform functionality
• Impersonate others or create fake accounts
• Circumvent security measures or consent requirements

§7 Intellectual Property

§7.1 Platform Content

• VetterPlaces logo, design, and code are owned by us
• User-generated content (profiles, contributions) remains owned by users
• By posting content, users grant us a license to display it on the platform

§7.2 Developer Products

• Developers retain all rights to their software products
• License terms are set by developers, not VetterPlaces

§8 Privacy & Data Protection

Data processing details are described separately in our Privacy Notice. These Terms govern service use and contractual platform rules; the Privacy Notice governs personal-data processing. Key privacy-related operational points:

• Consent-based processing requires explicit opt-in (GDPR Art. 6(1)(a))
• Processing is bounded by purpose, role permissions, and exclusion controls
• Audit records may be retained for accountability and legal obligations

§9 Disclaimers & Limitations

§9.1 Platform "As-Is"

VetterPlaces is provided "as-is" without warranties of any kind. We do not guarantee:

• Uninterrupted or error-free service
• Accuracy of user-provided information
• Successful campaign outcomes or reward fulfillment
• Compatibility of test products with user systems

§9.2 Limitation of Liability

To the maximum extent permitted by law, VetterPlaces is not liable for:

• Indirect, incidental, or consequential damages
• Loss of profits, data, or business opportunities
• Damages arising from user disputes, product defects, or reward disputes
• Third-party content or actions (GitHub, Payhip, etc.)

Third-party integrations: Features that connect to external services (e.g., GitHub Issues/Webhooks) depend on those services' availability and your configuration. You can disable integrations and revoke tokens at any time.

Liability limitations apply only to the extent legally permitted and are subject to mandatory consumer and data-protection law.

§10 Indemnification

Users agree to indemnify and hold harmless VetterPlaces from claims arising from:

• Your violation of these Terms
• Your infringement of third-party rights
• Your misuse of platform features or data

§11 Account Termination

§11.1 By User

• Users can delete accounts via profile settings or by emailing support
• Data retention follows Privacy Policy guidelines

§11.2 By VetterPlaces

We may suspend or terminate accounts for:

• Violation of these Terms or Privacy Policy
• Fraudulent activity or abuse
• Legal requirements or court orders
• Prolonged inactivity (with 30-day notice)
• Abuse, fake evidence, embargo/NDA breach, harassment, or security misuse, even during an active membership or subscription term
• Where fraud or serious misuse is proven, pending rewards may be blocked and non-final benefits may be revoked to the extent legally permitted

§12 Dispute Resolution

§12.1 Governing Law

These Terms are governed by the laws of Luxembourg, excluding conflict-of-law rules, unless mandatory law provides otherwise.

§12.2 Jurisdiction

Disputes shall be resolved by the competent courts in Luxembourg unless mandatory law provides otherwise.

§12.3 Arbitration

Arbitration is only applicable where explicitly agreed in writing by both parties.

§13 Changes to Terms

We may update these Terms periodically. Material changes will be notified via:

• Email to registered users
• In-platform banner notification
• 30-day advance notice for significant changes

Continued use after changes constitutes acceptance. If you disagree, you must stop using the platform.

§14 Miscellaneous

§14.1 Entire Agreement

These Terms and the Privacy Policy constitute the entire agreement between users and VetterPlaces.

§14.2 Severability

If any provision is invalid, the remaining provisions remain enforceable.

§14.3 Waiver

Failure to enforce a right does not waive that right.

§14.4 Assignment

Users may not assign these Terms. We may assign to successors or affiliates.

§15 Contact Us

For questions about these Terms:

Email: legal@vetter.alveos.eu
Web: ready-4-it.com

Privacy Notice | Legal Notice | Back to Home