Porthos Lab Limited ("Porthos", "we", "us") operates porthoslab.com and quiz.porthoslab.com. Porthos is also building features that are not live yet. Throughout this policy, we clearly separate what is active today from planned future features that are not active yet — we never describe a planned feature as if it were already happening.
Porthos Lab Limited, an Irish company (company number 819718), with its registered office at Venture Hub, 136 Capel Street, Dublin 1, Dublin, D01 T2C9, Ireland. Contact: hello@porthoslab.com.
We are a small, early-stage team. This policy describes our systems honestly and will be revised — including a fuller description of legal basis, data retention periods, and a named contact for data requests — before any process described here processes real personal data at scale, particularly the planned presale/KYC features below.
This site (per our Cookie Policy) sets no cookies. We do not provide account creation or contact forms on porthoslab.com. Our hosting providers may process technical information necessary to deliver and secure website requests. We are confirming the exact log-retention arrangements.
Active todayThis application offers quizzes and, optionally, connecting a crypto wallet to claim PORTH token rewards for participation. It is built on Supabase (hosted in the EU) as its database. If quiz account, progress, or reward-claim functionality is enabled, the service is designed to process the following:
| Data | When |
|---|---|
| An account identifier | When the app creates a session for you |
| Your quiz answers, whether each was correct, and a timestamp | As you take quizzes |
| Points, streaks, and badges | As you take quizzes |
| An optional display name you choose | If you set one |
| Wallet address, claim timestamp, and the resulting blockchain transaction hash | If and when you claim a reward |
We do not currently use any analytics, advertising, or tracking tool on this site.
Planned — not active yetNot active today. There is no live, publicly accessible presale purchase flow on our sites. Before this feature is switched on, we will update this policy with final, specific details.
We are building a presale process in stages, starting with an initial pilot round and followed by later, larger rounds. We expect the purchase flow to require connecting a wallet and signing a message to prove you control it, along with the time of that signature. We do not yet consider the exact technical details of this flow final.
Planned — not active yetNot active today. No anti-abuse or human-verification check currently runs on any live page. We will update this policy before this is switched on.
We expect to add checks intended to prevent bots, scripts, or coordinated abuse of the presale — for example, a human-verification challenge, and rules limiting how presale access can be attempted. These may involve their own third-party service and are not final; we are not naming a specific provider here until one is actually active, at which point we will name it and describe what it does with your data.
Planned — not active yetNot active today. No payment processor is connected to any public page, and we do not currently collect any payment or purchase data from real users.
Once live, we expect a presale purchase to involve recording the wallet address that paid, the amount and token paid, the resulting on-chain transaction, and internal records used to reconcile that a purchase completed correctly and match it to the correct participant. We expect this to also cover applicable support/monitoring records used to resolve a participant's issue with their own purchase. Exact fields and retention are not final and will be published before this goes live.
Planned — not active yetNot active today. No identity verification (KYC) is currently active for any real user, on any round.
Our initial pilot presale round is designed to run without identity verification, bounded by a small maximum amount. Porthos expects that KYC may be required for later, larger rounds. The final scope, provider, data fields, and notices will be confirmed before activation. Our current backend code references a specific third-party identity-verification provider for this purpose — we are not naming or confirming that provider as final in this policy until this feature is actually active. We have not finalized how any identity documents involved in that process would be handled or where they would be held; we will publish full details of this flow, including the provider's name and how your data would be handled, before it is accessible to real users.
Planned — not active yetNot active for real users today. We have tested contracts on public testnets, which do not involve real participants or real funds. No live contract is currently reachable from a public page for real purchases.
Once a presale is live, if you interact with a smart contract we operate (for example, to claim a reward or make a purchase), your wallet address and the transaction itself would be recorded on a public blockchain. Public blockchains are, by design, public and permanent — this data would not be something we can alter or delete once a transaction is submitted, and it would exist independently of anything we store in our own database.
We do not sell personal data.
Active todayWe retain personal data only for as long as reasonably necessary for the purpose for which it was collected, to resolve disputes, and to meet applicable legal obligations. We will publish more specific retention periods before activating a KYC-enabled or larger presale process.
Depending on where you live, you may have rights to access, correct, or request deletion of personal data we hold about you. Contact us using the details below and we will respond directly. We intend to expand this section with a fuller, formally reviewed description of applicable rights and our legal basis for processing before this policy is relied upon for a live presale involving real personal data at scale.
Questions about this policy or your data: hello@porthoslab.com.
We will update this page and its "Last updated" date whenever what we actually collect or how we process it changes, and before any planned feature described above is activated.