Skip to content
GENAIRALISTGENAIRALISTby Andrejs Karpovs

Privacy notice

This notice explains what personal data GenAIralist uses, why it is used, who receives it, and the choices you have. It applies to this website, the fellowship waitlist, and messages you send us.

1. Who is responsible

Andrejs Karpovs, operating GenAIralist, is the controller of the personal data described here. Questions and data-rights requests can be sent to hello@genairalist.ai.

2. What we collect

  • Waitlist verification and membership: your email address, when the verification was requested, the page or campaign source that led to the form, when you confirm membership, and the version of the consent you confirmed. The first submission sends a verification email; it does not ask Loops to add the address to its Audience or the waitlist, or write custom profile/context fields.
  • Optional fellowship context: the role, self-description, current challenge, and feedback you choose to submit after confirming your email. Please do not include health information, identification numbers, or other sensitive personal data.
  • Speaking inquiries: your name, company or event, email address, optional location and timing, the topic you submit, and the submission time.
  • Meeting bookings: if you book a call, the name, email address, meeting time, and any details you enter on the booking page. That page is hosted by Calendly, not by this site, so you submit those details to Calendly directly.
  • Other messages: the contact details and content you choose to send when you email us.
  • Basic technical data: our server and hosting provider may process an IP address, browser and device information, requested URL, date and time, and security or error signals when serving the site. The server temporarily uses the IP address to limit form abuse; it is not added to your waitlist or speaking-inquiry record.

GenAIralist does not currently run advertising trackers or site analytics, or set cookies for tracking. We do not intentionally write waitlist emails, optional answers, or speaking-inquiry contents to application logs. After confirmation, two short-lived HttpOnly, Secure, SameSite=Strict cookies are set for one hour. One carries your confirmed address in encrypted form to authorize the optional context form, and is cleared as soon as you submit it. The other holds only a timestamp, so reloading the confirmation page still shows the confirmed state. Neither is used for tracking.

3. Why we use it

Mailbox verification. When you request to join, we send one verification email so only the person who controls the address can add it. The encrypted link expires after 24 hours. Opening it displays a confirmation screen; it does not add the address until you submit the confirmation. The legal basis is your request and our legitimate interest in verifying consent and preventing abuse.

Application-opening email. If you confirm the address, we add it to the waitlist, record the original consent request and its version, and use the address to tell you when fellowship applications open. The legal basis is the consent you expressed in the form and verified through the confirmation step. You can withdraw it at any time.

Optional answers. We use them to understand who is interested and plan the fellowship. The legal basis is the consent you give when you choose to send those answers. They are not required to join the waitlist, and you can withdraw that consent at any time.

Inquiries. We use messages to respond and follow up. Depending on the inquiry, the legal basis is taking steps at your request before a contract or our legitimate interest in answering you.

Security and operation. We use limited technical data to deliver the site, prevent abuse, and diagnose failures. The legal basis is our legitimate interest in operating a secure, reliable website.

An email address and consent are required to join the waitlist; without them, we cannot add you or send the verification and application-opening emails. You must also confirm the verification link before the address is added. Name, company or event, email, and topic are required to submit a speaking inquiry so we can understand and answer it. Fellowship context, speaking location, and speaking timing are optional.

We may also process information where necessary to comply with law or establish, exercise, or defend legal claims.

4. Who receives it

  • Loops (Astrodon Corporation) receives the address and encrypted confirmation URL solely to send the requested verification email. The request does not ask Loops to add the address to its Audience or the waitlist, or write custom profile/context fields. After confirmation, Loops processes the dedicated waitlist, consent record, optional answers, application-opening email delivery, and speaking inquiries for us.
  • Vercel hosts the website and processes the limited request and operational data needed to serve it.
  • YouTube receives technical data only if you choose to open a video player. The player uses YouTube’s privacy-enhanced youtube-nocookie.com mode. Google’s own terms and privacy notice then apply.
  • Calendly hosts the booking page linked from the contact page. It receives the name, email address, meeting time, and any details you enter there, and processes them so the meeting can be scheduled and held. Calendly’s own terms and privacy notice apply once you open the booking page.
  • Our respective email providers process messages when you contact us or receive the application-opening email.

We do not sell or rent personal data, use it for behavioral advertising, or disclose it to unrelated third parties. We may disclose data if law requires it or if needed to protect legal rights.

GenAIralist is currently operated by Andrejs Karpovs as an individual. If it is incorporated, or the fellowship moves to another organisation, the waitlist and related records may transfer with it.

This notice does not cover the sites we link to, including LinkedIn, YouTube, Calendly, Substack, and the providers and authority named above. Their own privacy notices apply once you leave.

5. International transfers

Loops, Vercel, and Calendly are based in the United States and may use service providers in other countries. For Vercel transfers from the European Economic Area that require a safeguard, we rely on the European Commission’s 2021 Standard Contractual Clauses incorporated into Vercel’s data processing addendum. The Loops data processing agreement requires international transfers to use an approved safeguard, such as Standard Contractual Clauses or an adequacy decision. The booking page is hosted by Calendly, so details entered there reach Calendly directly under its own notice and terms. You can contact us for information about the safeguard relevant to your data. Provider terms and sub-processor information are available in the Loops data processing agreement and the Vercel data processing addendum.

6. How long we keep it

  • An unconfirmed verification link expires after 24 hours. The application does not create waitlist membership before confirmation. Unconfirmed requests do not ask Loops to add the address to its Audience or the waitlist, or write custom profile/context fields. Loops may retain transactional-delivery records according to the account settings and its legal obligations.
  • Unsubscribing or withdrawing the application-email consent stops that email. If you withdraw consent for the optional fellowship answers, we stop using and delete those answers, except for the minimum record needed to show that we honored the request or where law requires retention. We remove other non-essential waitlist data when you ask us to delete it, when the relevant fellowship application cycle has closed and no further update is needed, or after 24 months without a waitlist communication — whichever comes first.
  • We may retain the minimum consent, withdrawal, or suppression record needed to demonstrate compliance and make sure we do not email someone who has unsubscribed.
  • Speaking inquiries and other messages are kept only while needed to answer the inquiry, manage the resulting relationship, and meet legal obligations.
  • Operational records are kept according to our hosting settings and only as long as needed for security, reliability, or an active investigation. The application’s in-memory form abuse records hold an IP address and timestamps for about one hour. The verified-session cookie for optional fellowship context also expires after one hour.

7. Your choices and rights

Depending on the law that applies, you may ask us to give you a copy of your data, correct it, delete it, restrict its use, or provide it in a portable format. You may object where we rely on legitimate interests. Where we rely on consent, you may withdraw it at any time without affecting earlier lawful use.

Use the unsubscribe link in an email or write to hello@genairalist.ai. We may ask for enough information to verify that the request is yours. When the GDPR applies, we respond without undue delay and within one month. If the law permits an extension, we will tell you within that first month and explain why.

You may also complain to the data-protection authority where you live or work. In Latvia, that is the Datu valsts inspekcija.

8. Security and decisions

We use access controls, encrypted connections, data minimization, and processor agreements intended to protect your information. No online service can promise absolute security. Waitlist confirmation links are encrypted and expire after 24 hours. Opening a link is non-mutating; an explicit confirmation is required. Optional context is accepted only from a short-lived verified session, and the email address is derived on the server rather than accepted from that form.

We do not use personal data from this site for automated decisions or profiling that produces legal or similarly significant effects.

9. Children

This site, the waitlist, and the fellowship are meant for working adults. They are not directed to children, and we do not knowingly collect personal data from anyone under 16. If you believe a child has sent us personal data, write to hello@genairalist.ai and we will delete it.

10. Changes to this notice

If our practices materially change, we will update this page and its effective date. If a change requires new consent, we will ask before using the data for that new purpose.

Effective 3 August 2026.