Who is responsible
Hackmamba Inc., a Delaware corporation, operates River. In the initial pilot, we decide how information is used for the Hackmamba programmes we run and are responsible for that processing.
Contact us about privacy or your information at [email protected], or write to:
Hackmamba Inc.1111B S Governors Ave
Dover, DE 19904
United States
If River is later provided to another organisation to run its own programme, that organisation's notice will explain its decisions about participant information. Our role for information processed on its instructions will depend on the applicable service arrangement.
Information River handles
We receive information from you, authorised programme managers, connected services and public professional sources:
- Accounts and access: names, email addresses, profile details, workspace memberships, invitations, sign-in and session records, and security information such as IP addresses and browser details. A connected sign-in provider supplies the identity information authorised through its sign-in flow.
- Champion profiles and applications: your biography, country or city, languages, topics, social accounts, work links, products you use or want to try, previous collaborations, rates, application answers and recorded permissions. We also keep programme reviews, notes and decisions.
- Public professional evidence: profiles, posts, engagement and audience information, network relationships and related evidence obtained from supported public sources or services. You may also submit metrics or proof files yourself. River can produce classifications, programme-fit assessments, scores and explanations from this material.
- Programme participation: invitations, event registrations, tickets, attendance, campaign offers, agreements, deliverables, feedback, reports and relevant correspondence. Where payment or tax features are used, this can include payee details, payment references and status, and tax documents or review records.
- Messages and agent activity: emails sent through River, replies to supported programme threads, their addressing and delivery information, agent conversations, relevant tool results, prepared actions, approvals and usage records. Agent conversations are stored in River; they are not confined to your device.
- Website and operations: requests, errors, security counters, audit records and information you send to support. River uses authentication cookies and browser storage for preferences and unfinished application drafts. Draft answers are removed from that browser storage after a successful application submission; you can also clear them through your browser.
Please provide accurate information and avoid unnecessary sensitive information, private credentials or information about other people that you are not entitled to share.
Why we use it
We use this information to authenticate users, assess and manage applications, match people with programmes, organise events and collaborations, communicate with participants, administer agreed payments, answer requests, and protect and maintain River.
Where European or UK data-protection law applies, we rely on the basis appropriate to the activity: providing a service or carrying out an agreement you request; consent for the directory, contact and enrichment permissions described in the application; legitimate interests in administering professional programmes, responding to enquiries, preventing abuse and keeping reliable records, balanced against your rights; and legal obligations where they apply. We do not treat acknowledging this notice as consent to every possible use of your information.
The current champion application asks for permission to list an approved profile in River's shared champion directory, allow participating workspaces to contact you about relevant opportunities, and enrich and assess the application using public professional information. These permissions are currently required by that application flow. You can withdraw directory-listing permission in your portal profile. Contact us to withdraw other permissions or discuss the effect on a programme. Withdrawal does not undo earlier lawful processing or necessarily remove records needed for another lawful purpose.
Signing in or registering for an event does not by itself subscribe you to unrelated marketing. Programme and service messages support the activity you requested. Use an unsubscribe option in a marketing email, where offered, or contact us to object to further marketing. We retain suppression information to respect those choices and delivery complaints.
AI-assisted assessments and actions
River uses AI to help assess applications and public professional evidence, suggest matches, draft material and respond to workspace requests. Relevant messages, application material and workspace context can be sent through OpenRouter to the model providers used for that request. Information returned by workspace tools can also become part of that context.
River configures model requests to disallow provider data collection and requests zero-data-retention routing for selected tasks. These settings do not mean that every request has zero retention, that River deletes its own stored conversations, or that all processing takes place in Europe. Provider handling also depends on the selected route and applicable provider terms. See OpenRouter's privacy policy and data-handling information.
Automated assessments can influence which applications or opportunities a manager reviews. They can be inaccurate or incomplete. Human managers decide admission to the champion directory and are responsible for programme decisions and approved actions. You can ask us to correct evidence, review an assessment or explain a decision affecting you. Do not put information into an agent conversation that you do not want processed for that request.
Who receives information
Authorised Hackmamba programme staff can access information needed for their roles. An approved champion profile can be visible to authorised participating workspaces through the shared directory, according to its permissions. A directory listing is not a promise that every field, private message, payment record or tax document is public. If a programme involves another organiser or company, we share the information needed for the collaboration and explain additional collection or sharing where required.
We use providers to operate River:
- Hetzner hosts the application and its main database in Germany and provides server backups.
- Amazon Web Services provides object storage and backups, email sending and receiving, queues and operational monitoring. Our configured AWS storage and email region is Ireland, eu-west-1.
- Cloudflare delivers and protects the service. Forms use Turnstile, which processes browser and network signals to limit automated abuse; see its privacy addendum.
- OpenRouter and the model providers involved in a selected request process AI inputs and outputs as described above.
Support correspondence also passes through the services that host our business mailbox. When a supported integration is connected or used, its provider processes information needed for that feature. This can include a sign-in provider, an event service such as Luma, a payment service such as Stripe or Wise, or a professional-data service. The choices available in the programme determine which integrations apply; their own notices explain information they hold independently.
We may disclose information when required by law, to address a valid legal request or a security incident, or to protect people and legal rights. A business transfer may involve relevant information, subject to applicable law.
Hackmamba Inc. is a US company and providers operate internationally. Information may be accessed or processed outside your country, including in the United States. EU hosting does not make all processing EU-only. Contact us for information about the locations and transfer safeguards applicable to your information.
How long information remains
We keep programme, account, correspondence, agent and uploaded-file records while needed for the relationship or programme and related support, security, payment, legal and dispute purposes. The pilot does not yet apply a single automatic deletion deadline to these database records. We review deletion requests and retention needs against those purposes.
Our configured shorter retention controls are:
- Sign-in links and portal codes expire after 15 minutes. Manager and portal sessions normally expire after 30 days unless revoked earlier. Expiry does not necessarily mean the underlying record is immediately removed.
- Raw public-enrichment evidence in its dedicated object store is configured to expire after 90 days. Normalised profiles, assessments and programme records have separate retention.
- Raw incoming email copies are configured to expire after seven days. These copies can contain attachments; the application imports message content and limited attachment metadata rather than attachment files. Processing notifications can remain in the main queue for up to four days and the failed-processing queue for up to 14 days. Imported thread messages remain programme correspondence.
- Database backup objects are configured to expire after 30 days, with noncurrent versions expiring one day after replacement or expiry. Final removal can take longer because storage lifecycle cleanup is asynchronous. Hetzner's automatic server backups rotate through seven daily-backup slots as new backups succeed.
Deleting a profile does not necessarily remove financial records, required audit material, suppression hashes, correspondence or existing backup copies. The portal can remove or de-identify core profile information and queue deletion of associated raw enrichment evidence; a broader request may need manual review of other records. Protected backups remain for recovery until their retention controls remove them. Providers can also retain information independently under their own terms and legal duties.
Your choices and rights
In the participant portal, you can edit supported profile fields, withdraw directory-listing permission, report a profile problem, and request a profile export or deletion. The current portal export covers your profile, linked social accounts and workspace relationships; contact us for a request covering other personal information we hold.
Depending on applicable law, you may have rights to access, correct, erase or receive a portable copy of information, restrict or object to processing, withdraw consent, and complain to the relevant supervisory authority. Send requests to [email protected]. We may verify your identity and will respond within the period required by law. We will explain any relevant retention exception or limitation. Where another organisation independently holds your information, you may also need to contact it.
Cookies needed for authentication and security, and browser storage for preferences and drafts, support these features. Clearing or blocking them can sign you out or remove saved drafts and preferences. River's pilot application does not include third-party advertising or product-analytics scripts; infrastructure providers still process information needed for delivery and protection.
Security and updates
We use measures such as encrypted connections, restricted service credentials, access controls and protected object storage. No service can guarantee complete security. Contact us promptly if you believe River information has been exposed or misused.
We will update this notice when River's practices change and provide additional notice or choices where required. The date above identifies this version.