1. Who is responsible
Pushing Knights BV runs GaiaHunt and Scavagent. We are the data controller for the processing we decide on. Our company is based in Brussels, Belgium; the registered office and company numbers are linked below.
For privacy questions or requests, email [email protected] or write to our registered office. General support is available at [email protected].
If a company, school or other organizer arranges your hunt, it may decide on additional uses of participant data. Ask for its privacy notice too. Where we process data on an organizer's instructions, the processing agreement sets out our respective roles. This notice does not replace the organizer's responsibilities.
2. Information we process
| Category | Examples and source |
|---|---|
| Account and organization information | Information you or your organization provide, such as email address, profile or display name, organization membership, permissions and account entitlements. |
| Hunts and authoring | Your requests, constraints, supplied facts, route places, drafts, generated content, creation-task records, organizer replies and saved edits. |
| Participation | Information supplied during a hunt, such as team or player nicknames, answers, scores and uploaded photos. The information collected depends on the hunt and the features you use. |
| Location | Places and route coordinates supplied for a hunt. Device location can also be processed for location-based play when you enable that feature and grant the relevant device permission. A route destination is not necessarily your current location. |
| Connected-app access | The account and client identifiers, consented permissions, authorization records and credentials needed to authenticate a connection and check access. Authentication secrets must be handled through the sign-in flow, not pasted into tool inputs. |
| Technical and support information | Request and security data, such as IP address, browser details, error information and the support messages you send. Optional measurement depends on your cookie choices. |
| Purchase records | If you buy a service separately on the website, the billing and transaction information needed to handle that order. Do not send card details through Scavagent or support messages. |
3. Purposes and legal bases
We use personal data for the purpose that applies to it. When we rely on a legitimate interest, we must weigh that interest against your rights. You can object as explained below.
Some account details and task inputs are needed to provide the feature you request. Without them, that feature may not work. You can use the core service without optional analytics consent. Connector permissions control access to your account; they do not give blanket consent for other uses of your data.
| Purpose | Legal basis |
|---|---|
| Provide your account, requested hunts and authoring tasks, and saved content | Performance of our contract with you, or steps you ask us to take before a contract. If the customer is an organization and the individual user's processing is not needed for a contract with that user, we rely on our legitimate interest in providing the authorized service. |
| Check connection access and permissions, enforce limits and prevent misuse | Our legitimate interests in protecting accounts and keeping the service secure and reliable. A check needed to provide a service you request may also be necessary to perform the contract. |
| Answer support questions, investigate problems and handle complaints | Performance of the contract for service requests, or our legitimate interest in answering enquiries and resolving problems. |
| Handle orders, accounting and legally required records | Performance of the order contract and compliance with legal obligations. |
| Optional analytics, advertising measurement and non-essential cookies | Consent where required. Use Cookies in the footer to reject these categories or change your choice. |
| Protect legal rights and respond to binding lawful requests | Compliance with a legal obligation, or our legitimate interest in establishing, exercising or defending legal claims. |
4. Scavagent and AI processing
Your AI assistant sends Scavagent the tool inputs it selects for your request. We receive those inputs and use your account permissions and relevant hunt or task data to answer. Connecting does not give us general access to your other chats or files.
Hunt creation and review use different AI providers. They can receive the parts of your request, supplied material and hunt context needed for the task. GaiaHunt can save the results and creation records as part of that task.
Share only what the hunt needs. Leave out passwords, payment-card details, government identifiers, health information and unnecessary details about children. Facts about a place or event can also include someone's personal data.
Your AI provider handles the conversation under its own terms and privacy settings. Retention and use for model improvement depend on the provider and service settings. Contact us to ask which model providers are involved in GaiaHunt's processing of your request, and check your assistant provider's notice for its handling of the chat.
If an automated access or allowance refusal seems wrong, ask support to review it. Hunt generation is not intended to make decisions about you with legal or similarly significant effects. We do not promise human review of every generated result.
5. Who can receive information
Connecting an assistant does not publish a private draft or open every hunt to it. Access depends on your account permissions and the action requested. Check who can see names and photos before sharing them.
- Staff and providers that run our hosting, databases, sign-in, storage, security, maps, email and support. Hetzner provides hosting. Each receives information relevant to its work.
- Model providers working on the requested AI task, and your AI assistant provider when it receives the result through the connection you authorized.
- Organizers and participants who need information for the relevant hunt, or other users when you choose to share or publish content.
- Payment providers for website purchases, advisers where needed, and authorities or other recipients when disclosure is legally required or needed for a lawful claim.
6. International processing
Hetzner provides our hosting. AI model providers and your AI assistant provider may process data in other countries, including outside the European Economic Area. The hosting location does not determine where an AI request is processed.
An international transfer we are responsible for needs a permitted GDPR transfer basis. This may be an applicable adequacy decision or safeguards such as the European Commission's standard contractual clauses, with extra measures where required.
Email [email protected] to ask which recipients and countries are involved in your use, which transfer basis applies, or how to obtain information about safeguards. Your assistant provider is responsible for transfers it makes independently when handling your chat.
7. Retention and deletion
How long we keep data depends on why it is needed. The table gives the known periods and the criteria used for other records. Disconnecting an app, cancelling a task or deleting a chat does not erase all related records in GaiaHunt.
| Category | Period or criteria |
|---|---|
| Accounts, hunts, drafts and creation records | Kept while needed to run the account or retain the content you choose to keep. On a deletion request, we check what can be erased and what is still needed for a service, legal obligation or justified claim. There is no single automatic deletion period for every task record. |
| Connector access | Access tokens last ten minutes. A connection needs renewed consent after 90 days, or 30 days without a qualifying token or session refresh. Revoking access stops new requests and clears its stored connection credentials. |
| Connection cleanup records | Configured cleanup removes replaced refresh-token records after 30 days and revoked-grant metadata after 90 days. Those periods apply to connection records, not saved hunts or conversations. |
| Cookie preferences | The cookie storing your GaiaHunt consent choice lasts 180 days. Individual analytics or advertising services can have other periods, described in their consent information. |
| Support, technical records and backups | Kept for a period justified by the support issue, service security, recovery needs or legal requirements. Relevant factors include an unresolved complaint, an active security investigation and the recovery cycle. Contact us about the period for a particular record. |
| Accounting and legal records | Kept for the statutory period or an identified legal obligation or claim. Access is restricted to that purpose. |
8. Control a connected app
Open Profile → Connected apps in GaiaHunt to review or disconnect an app. Disconnection blocks later requests, including reads, but an accepted task may finish. Extra permissions need a new consent flow.
Email [email protected] to request deletion of personal data from GaiaHunt. Your assistant provider has separate controls for its chat history. Both are separate from disconnecting the app.
10. Your data protection rights
Email [email protected] to ask for access, correction, erasure, restriction or portability of your personal data, or to object where the legal conditions apply. You can withdraw consent at any time. Withdrawing consent does not change whether earlier processing was lawful.
Tell us which account and data you mean. We may need proportionate information to check your identity. Send no passwords or identity documents unless we have agreed a secure, necessary verification method.
We respond without undue delay and normally within one month. If the law allows more time because of the request's complexity or the number of requests, we will explain the extension within that first month. If we cannot meet a request fully, we will explain why.
You can complain to the Belgian Data Protection Authority or another competent authority, including where you live or work. Contacting us does not take away that right.
11. Children and organizer responsibilities
For a family or school hunt, the responsible adult or organization should choose suitable activities and provide the information and permissions required by law. Avoid collecting unnecessary identifying or sensitive details about children.
Organizers should explain what participant data they collect and who can see it. An organizer's account authorization is not consent from every participant for every purpose.
Parents, guardians and participants can email [email protected] about a child's information. We will consider the child's rights and the law when assessing the request and checking identity.
12. Security and notice updates
We use access controls, scoped connections and other technical and organizational measures to protect data. They cannot remove every risk. Report suspected account misuse or exposed data to support, without sending authentication secrets.
We update this notice when our processing or legal requirements change. The date above identifies this version. We will give further notice or request consent before a new purpose or material change where the law requires it.