How registration data is used.

1. Controller and contact

The public contact for this website and registration workflow is the NEOPORT organising team at info@neoportforum.com.

The contracting entity, registered details and applicable tax information for an accepted booking are stated in the written confirmation or invoice before payment is due. If you need those details before submitting a request, contact the team first.

2. Information processed

Registration information

Name, organisation, business email, selected pass quantities, preferred currency and any eligibility information supplied during follow-up.

Request identifiers

A random request ID and processing status used to prevent duplicate submissions and trace the request.

Essential session data

A short-lived, HttpOnly session cookie used to validate the form and protect it from cross-site submission. It expires when the browser session ends.

Anti-abuse information

Short-lived keyed hashes derived from network and submission signals. The registration log and notification email do not include the raw IP address.

3. Purposes and legal grounds

• Taking steps at your request before a possible participation agreement.
• Reviewing pass eligibility, availability and event administration requirements.
• Sending confirmations, invoices, delegate information and essential event updates.
• Protecting the service from spam, fraud and repeated automated requests as a legitimate operational interest.
• Meeting applicable accounting, dispute-resolution or legal obligations when a request becomes a booking.

4. Storage and delivery

A valid request is written to a private, access-restricted registration log before the website attempts to send an organiser notification. This prevents a lead from disappearing solely because mail delivery is delayed.

Information may be handled by service providers required for hosting, security, storage and business email delivery. They should receive only the information necessary for those services.

5. Retention

• Rate-limit and anti-abuse state is automatically pruned and is intended to remain for no more than 24 hours.
• Unsuccessful or duplicate technical request state is retained only as long as needed for security and troubleshooting.
• Registration and communication records may be retained through the event cycle and afterwards where reasonably needed for administration, accounting, legal claims or an accepted participation agreement.

6. Your choices and rights

Depending on the law applicable to you, you may request access, correction, deletion, restriction or objection. Send a request to info@neoportforum.com. Identity verification may be required, and some booking or accounting information may need to be retained where the law requires it.

7. Security and international processing

The workflow uses server-side validation, request-size limits, rate limiting, anti-duplication controls, private storage and restricted browser permissions. No internet service is risk-free, so do not submit unnecessary sensitive information.

Hosting or email providers may process information outside your country. Where required, the organising team should use an appropriate transfer mechanism and provider safeguards.

8. Third-party tools

Fonts, styles, images and scripts used by the normal page experience are served from the NEOPORT website. If an anti-bot challenge is enabled and displayed, its provider may receive the technical information necessary to verify that submission; the challenge itself will identify the provider.