Privacy notice

How we handle your information, share Letters of Interest and respect your choices.

Last updated:

Notice being finalised. Provider agreement and transfer details, legal-basis assessments and provider-managed retention arrangements still need confirmation. The sections below describe the current website and LOI flow; this is not yet a complete final notice for production reliance.

Who is responsible

Aurora Confinement is a student-led initiative in formation, not yet an incorporated company. University affiliations do not make DTU or the University of Copenhagen responsible for this website.

Data controller: Etienne Gras, operating the Aurora Confinement initiative.

Email for privacy questions and rights requests: [email protected].

Information we collect

Letters of Interest

When you use Register interest, you provide your name, work email, role, organisation, country and capacity to make the statement. You select a product and type of interest, and give the intended application, primary use and indicative timing for each selected product.

You may also provide a phone number, department, procurement role, explanation of usefulness, preferred date or event, quantities, expected audience or reach, budget information, conditions and product-specific requirements. Those fields are optional. Please do not include sensitive personal information, other people's unnecessary details, or confidential or patent-sensitive material.

We store the submitted answers and confirmed letter in our database, together with its reference, confirmation date, template and wording versions, sharing permission, and source category (Register interest or the Nordic Fusion Forum link). We may add relevant follow-up notes, status and authority-review information. An audit history records creation, permission changes, withdrawal, follow-up and exports.

The draft updates in your browser while you type. The form sends its answers to our registration endpoint when you submit; the form does not autosave draft answers to the LOI database. Your email is not verified. Confirmation records your statement, not proof of identity, institutional authority or an order. After saving, you can print or save the letter as a PDF using your browser; the website does not email a receipt or PDF.

Email enquiries

If you email us, we receive your email address, message, attachments and other information you choose to include. Contact enquiries do not create an LOI or grant permission to show your message to investors.

Website and security information

Our servers and delivery providers receive connection information such as IP address, request details and browser information. The registration endpoint uses the client IP address in temporary, in-memory rate-limit counters to limit abuse. Its time window is ten minutes; inactive counter entries may remain in memory until cleanup or a server restart. The LOI record does not contain an IP-address field. We do not operate routine website access logs or separate backups. This does not include the LOI audit history described above or technical records and recovery copies that providers may keep under their own service arrangements.

Why we use information and the legal bases

We use LOIs to record the statement you requested, understand institutional requirements, manage relevant follow-up, and prepare evidence of potential demand. This is separate from newsletters, public testimonials or logo permissions.

  • LOI administration and requested enquiries: the proposed basis is legitimate interests under GDPR Article 6(1)(f), specifically managing professional correspondence, product requirements and accurate records of requested statements. The controller must complete the necessity and balancing assessment before adopting this basis.
  • Identifiable investor or grant-provider sharing: the proposed basis is your consent under Article 6(1)(a), limited to the confidential fundraising and due-diligence use explained below. The current combined, required confirmation needs assessment against Article 7's requirements for freely given, specific consent. Making a checkbox mandatory does not itself establish valid consent.
  • Security and abuse prevention: the proposed basis is legitimate interests under Article 6(1)(f), specifically protecting the website, its users and records. Provider logging and any terminal-device access need their own documented assessment, including applicable Danish cookie rules.
  • Legal obligations or claims: where applicable, specific processing may be required by a legal obligation (Article 6(1)(c)) or justified by a documented legitimate interest in establishing, exercising or defending a legal claim (Article 6(1)(f)). These are not reasons to retain every record indefinitely.

Submitting an LOI is voluntary and is not required by law or a purchase contract. Without its required fields and confirmation, the current form cannot create a completed LOI. Optional answers may be left blank. A private email enquiry remains available. No purchase, payment, supply or participation commitment is created.

Sharing with investors and grant providers

The current single checkbox confirms the letter and permits confidential sharing with prospective investors and grant providers for fundraising and due diligence. The letter can include your name, role, organisation, capacity, application and other answers you chose to put in it. Your dedicated email and phone fields are excluded from investor exports and the letter. Anything you put into free-text answers may still appear in a shared copy.

Investor exports also omit internal follow-up status and acquisition-source fields. Exported letter answers must be reviewed for unnecessary personal information before disclosure.

This permission does not authorise public publication, public testimonials, use of your organisation's logo, or marketing updates. Older letters without sharing permission are not made shareable by a later wording change. The investor export selects only confirmed letters with sharing currently permitted.

You can withdraw sharing permission or ask us to withdraw the LOI by emailing [email protected], quoting the reference if available. Withdrawal does not affect processing lawfully carried out before withdrawal. We will stop future consent-based sharing and assess whether the data must be erased or whether a separate lawful reason requires limited retention. Existing copies are not automatically recalled; where applicable, GDPR requires us to communicate corrections, erasure or restrictions to recipients, subject to its exceptions. We can explain the recipients relevant to your record.

See sharing details. No public testimonial, logo licence or newsletter subscription is included in an LOI.

Who else receives information

Etienne Gras, based in Denmark, administers LOIs and enquiries and decides how the information is used. Authorised technical administrators and service providers may process information as needed to operate the website, database, email and security services. Arthur Toppenberg administers the server and database from Denmark as a team member under Etienne's instructions. Etienne alone uses the LOI administration interface and manages Cloudflare and the contact mailbox. Database administration may nevertheless provide technical access to stored LOI information; such access must be limited to necessary technical work on instructions.

  • Contabo: hosts the website's origin server in Germany, behind Cloudflare.
  • Prisma Postgres: hosts the LOI database. The project's selected database region is eu-central-1, Frankfurt, Germany, on the Free plan. This database-region setting is not a guarantee that all provider support, account or technical processing stays there.
  • Cloudflare: provides domain and website delivery/proxy services and routes incoming email.
  • Google Gmail: receives incoming enquiries forwarded through Cloudflare to the controller's personal Gmail mailbox. A specific email storage region has not been confirmed.

These services can receive connection/request information as well as the information needed to provide their respective services. Provider-managed technical records and recovery copies may exist even where we have not enabled our own access logs or backups. Applicable contracting entities, processing agreements, support access and transfer arrangements are being checked. A hosting or database region does not establish EEA-only processing. Where a recipient acts as an independent controller, it is responsible for its own subsequent processing and notices.

Website analytics

This version of the website does not load the previously used Umami analytics script or send website analytics requests to that service. Disabling the script does not erase historical analytics records; their deletion or remaining retention must be confirmed with the former service operator.

LinkedIn content

The Team page offers embedded LinkedIn posts. They are blocked by default and only load after you select Accept LinkedIn in the consent panel over the blurred post placeholders. Decline LinkedIn leaves the original-post links available and does not block the rest of this website. The panel controls LinkedIn content only; it does not enable website analytics.

When you allow embeds, LinkedIn receives your IP address and browser information and may use cookies or similar technologies for recognition, analytics and advertising. Processing may take place outside the EEA. See LinkedIn's privacy policy and cookie policy. The provider's actual cookie/transfer arrangements still need to be verified; this notice does not certify them.

Use Cookie settings in the footer to change your choice in the Team page’s post section. From other pages, settings open in a separate tab so form answers are preserved. Declining removes the frames and stops further embed loads from this site. It cannot erase cookies or data already held by LinkedIn; those are managed through LinkedIn and your browser's settings.

Cookies and browser storage

We store your LinkedIn preference, its version and decision/expiry timestamps in local browser storage under aurora.linkedin-consent.v1 for 180 days. It contains no visitor identifier, and both accepting and declining are remembered for the same period. If storage is unavailable, the choice applies for the current visit. Expired or unrecognised choices require a new decision. The registration form does not use cookies or persistent browser storage to save answers. Administrators who sign in receive a necessary admin_session cookie with an eight-hour expiry; it is not used to track ordinary visitors. The presence and settings of Cloudflare, LinkedIn or other provider cookies must be checked against the deployed site.

Transfers outside the EEA

Our website origin server and selected LOI database region are in Germany. Cloudflare, Google, Prisma and LinkedIn may nevertheless involve processing or access outside the European Economic Area. The database-region setting does not cover every provider activity. Our service-specific destination and safeguard inventory is still being completed; we cannot claim that all information stays in the EEA.

Before a restricted international transfer, the applicable destination and protection must be established, such as a relevant adequacy decision or appropriate contractual safeguards and any necessary supplementary measures. A general provider policy or acceptance of a data-processing agreement alone does not identify the safeguard for every transfer. Contact us for information about the arrangements relevant to your data. Ordinary LOI sharing permission is not an international-transfer safeguard. See also Google's transfer framework information.

How long information is kept

LOIs and enquiries: up to 24 months after the last meaningful contact. This covers inactive letters, their associated follow-up records and ordinary email correspondence. Meaningful contact means a substantive discussion about the relevant enquiry, product, pilot or collaboration; an automated message or website visit does not restart the period.

Information must be erased or anonymised earlier if it is no longer needed or a valid erasure request requires it. Withdrawing consent stops future consent-based sharing; it does not automatically justify keeping the complete letter for another 24 months. Minimal evidence of permission or withdrawal may be retained only for a separately justified purpose and period.

Longer retention is possible only where a specific continuing purpose or legal requirement justifies it, for example a live project or an actual legal claim. The reason, scope and review/end date must be documented. This is not permission to retain all letters indefinitely for possible future fundraising.

Implementation status: the 24-month period is the controller's selected policy. The application does not yet enforce automatic expiry. Marking a letter withdrawn or superseded restricts investor export eligibility but does not erase it; the operational review and deletion procedure must implement this policy across the database, emails and exported copies.

Technical records and recovery copies: we do not operate routine website access logs or separate backups. Provider-managed logs, recovery snapshots and their actual retention remain to be confirmed. The 24-month LOI policy does not determine their overwrite periods. If a recovery copy is restored, applicable erasures must be reapplied. Historical analytics retention and deletion must be addressed separately with the former operator; this website no longer loads its analytics script.

Your rights and how to use them

Depending on the processing and applicable conditions, you may request access, correction, erasure or restriction, object to processing based on legitimate interests, and receive portable data where consent or contract and automated processing make that right applicable. You may withdraw consent at any time. We do not use the LOI flow to make solely automated decisions producing legal or similarly significant effects about you.

Email [email protected]. A reference number helps but is not mandatory. If we reasonably doubt your identity, we may request proportionate information to verify a rights request. The normal response deadline is one month; where a lawful extension is necessary because of complexity or number of requests, we must explain it within that month. Requests are normally free; GDPR contains limited exceptions for manifestly unfounded or excessive requests.

You may complain to the Danish supervisory authority, Datatilsynet, or to a competent supervisory authority in the country of your habitual residence, workplace or an alleged infringement. You do not need our permission to complain.

Changes to this notice

We will update the date when this notice changes. A revised notice does not expand an earlier LOI's sharing permission. If we propose a new purpose, we must provide the required information and establish the appropriate legal basis before using the information for that purpose.