Privacy notice

Testnet demo · Updated 4 November 2026

This notice describes the current NearPortal testnet demo. Do not enter sensitive personal information in bounty descriptions, pull requests or public project messages.

Information used by the demo

NearPortal uses your connected GitHub identity and authorized repository information to display repositories, manage bounties and track pull requests and checks. Bounty records can include titles, descriptions, acceptance criteria, assignments, deadlines and payment status.

The payment workflow uses the destination details you provide, such as a wallet address or sandbox bank details where that payment method is available. Session cookies support sign-in, and browser storage can keep unfinished drafts on your device.

How it is used

This information supports account access, repository permissions, funding verification, contribution tracking, payment reconciliation and troubleshooting. Provide only information needed for the task. Do not provide a wallet seed phrase or private key.

Public information and external services

Bounty briefs and contributor activity may be visible through the app’s public views. Private repository code remains subject to GitHub access permissions. Blockchain addresses and transactions are publicly observable; information recorded on a blockchain cannot be removed by deleting an app record.

GitHub, wallet providers, blockchain RPC services and supported payment providers process information under their own policies. Opening an external link takes you to that service.

Your controls

You can sign out and revoke NearPortal’s GitHub authorization through GitHub settings. Browser drafts can be removed by clearing the site’s browser storage. Revoking access does not erase existing bounty records, external GitHub activity or on-chain transactions.

Privacy questions

Contact @Nearportal on X for the appropriate private channel for a data request. Do not publish account details, bank information or credentials in a public post.