KASPABOTS · LAST UPDATED OCTOBER 24, 2026
1. Who we are
KaspaBots LLC, 99 Wall Street #5857, New York, NY 10005, runs kaspabots.com and decides how your personal data is used. You can reach us at [email protected].
2. The short version
We use PostHog to learn how the site is used, including recordings of how visitors use some of our pages, such as checkout and the application, with what they type and their personal details hidden. X’s pixel tells X which of our pages you view and whether you sign up, save a cabin or apply, so we can see which of our ads on X work, and X can show them to people likely to be interested. In Europe (the EEA, the UK and Switzerland), neither runs unless you say yes. Elsewhere, neither runs if your browser sends Global Privacy Control or Do Not Track. You can change your choice at any time under Your privacy choices, next to the link to this policy. We never see your card details. When you save a cabin, we send your name, email and phone number to Norwegian Cruise Line, so it can call you to book it. We do not sell your personal information, and only the KaspaBots team reads applications. Apart from X’s pixel, we share nothing for advertising.
3. What we collect, and why
| When | What we collect | Why |
|---|---|---|
| You visit any page | Your IP address, browser and the page you asked for, received by our host, Cloudflare | To deliver the site and block abuse |
| You sign in or create an account | Your email address, the IP address and browser of each sign-in session, and a log of sign-in events. Before we send a code, a bot check (Cloudflare Turnstile) reads signals from your browser | To let you sign in, see your tickets, application and membership, and keep out automated abuse |
| You save a cabin | Your name, email address and phone number, and the cabin you chose. We email them to Norwegian’s group sales consultant, record when we did, and mark the cabin booked once Norwegian tells us | So Norwegian can call you and book the cabin you chose |
| You buy the on-demand ticket | Your email address and account ID, which we pass to Stripe’s checkout, and a record of the purchase: the amount, the currency and Stripe’s references. Link, which processes the payment as merchant of record, collects your payment and billing details | To sell you the ticket and give you access to the recordings |
| You apply to the accelerator | Founders’ names, a contact email, country and city, company name and description, your answers and a link to your unlisted YouTube video. Once you have an account, we save your draft as you type, and the team can see a draft you have not submitted | To review applications and invite founders |
| You sign the standard deal or the Founder Promise | Each signer’s name, title and email, the time, the IP address and the version of the document signed | To keep a record of the agreement that both sides can rely on |
| You become a member | Your email and account ID, when your membership began, when we sent your welcome email and the invite codes we made for you | To let you into the network |
| You sign up for news | Your email address, the label of the post that brought you, if any, and the exact line you saw when you signed up, with the time | To send you the news you asked for, and to show you asked for it |
| You write to us | Whatever you send to [email protected] | To answer you |
| You browse the site, where analytics runs (section 13) | The pages you view, where you click and how far you scroll, the page, post or email that brought you, your browser, device and approximate location (from your IP address), the errors a page runs into, and, on some pages, such as checkout and the application, a recording of the page as you used it, with what you type and your personal details hidden. When you are signed in, your account ID | To see what works, fix what doesn’t and help you if something goes wrong |
| X’s pixel runs (section 13) | The pages you view, whether you sign up, save a cabin or apply, your browser and IP address, and the identifiers in X’s cookies, which X can match to an X account | To see which of our ads on X work, and so X can show them to people likely to be interested |
4. What stays on your device
The site keeps a working copy in your browser’s local storage so pages load without waiting on the network: your sign-in, your ticket status, your saved cabin with the name and phone number you gave, your application draft, when your membership began and the email you signed up for news with. That working copy is never used for tracking or shared with anyone. Signing out clears it, and you can clear it at any time in your browser’s settings. We use this storage only where it is strictly necessary for what you ask the site to do, so we do not ask for consent. You stay signed in on that browser until you sign out. Analytics and ads are different, and run only as section 13 describes: PostHog keeps a random ID in local storage to recognize your browser between visits, and X’s pixel uses cookies. We also keep your privacy choices in local storage, so we do not ask again.
5. Who handles your data for us
Cloudflare hosts the site, runs the bot check and stores the KaspaBots app. Supabase runs our accounts and database, on servers in Oregon. Resend sends our emails from the United States, including news from launch. Stripe runs checkout, and Link, as merchant of record, handles your payment details under its own privacy policy. Namecheap hosts our inbox. PostHog measures how the site is used and keeps its recordings, on servers in Virginia. X runs its pixel and uses what it collects under its own privacy policy (section 8). When you paste your video’s link, your browser loads its thumbnail from YouTube. When you save a cabin, Resend carries your name, email and phone number to Norwegian Cruise Line’s group sales consultant, whose reply reaches you directly. Norwegian then books your cabin and takes payment on a call, and handles what you give it under its own privacy policy. Norwegian’s privacy policy lets it use these details for marketing and share them with its affiliates.
6. The KaspaBots network
The network runs on Buzz, an app and service from Block, Inc., which hosts our community. We send Block no personal data: the invite codes it makes for us carry none. When you join, Block handles what you share in Buzz as its own data controller, under Buzz’s Privacy Notice. Messages in the network are not end-to-end encrypted, and Block keeps them for up to 365 days. As the community’s administrator, we can see what members share in the channels we belong to, and we moderate the community.
7. Who sees it
The KaspaBots team, through our database’s, our email provider’s and our analytics service’s dashboards. Norwegian’s group sales consultant sees each cabin request. When you are signed in, you see only your own records, and applicants never see the team’s notes or decisions while they are being made. If we accept you and you choose to take part in an investor brief, we share your brief with potential investors.
8. Transfers
We are based in the United States, and our providers store data there. For data from the EU or UK, our providers’ data processing agreements include the EU Standard Contractual Clauses and the UK Addendum; PostHog relies on them. Cloudflare, Stripe and Resend are also certified under the EU-US Data Privacy Framework and its UK Extension. X’s pixel is different. X decides how it uses what the pixel collects, under its own privacy policy, and we and X are jointly responsible only for collecting that data on our pages and sending it to X. For people in the EU, the EFTA States and the UK, X’s controller is X Internet Unlimited Company, in Ireland, and X participates in the EU-US Data Privacy Framework and its UK Extension.
9. How long we keep it
Your account, until you ask us to delete it. Applications, saved cabins and messages to [email protected], until you ask us to delete them. Ticket records, 7 years, for tax and accounting. Signature records, while the agreement they record is in force and 10 years after. A member’s record and invite codes, until the membership ends and 10 years after. The news list, until you unsubscribe; we then keep a record of when you signed up and when you left. Analytics, 1 year; recordings of the site in use, 30 days. A cabin request also stays in the inbox it was sent to, and Norwegian keeps its booking records under its own rules. Our database backups roll over every 7 days, and request logs are short-lived. Stripe, Link, Resend and X keep their records under their own rules.
10. Your rights
You can ask to see, correct, export or delete your data, or object to how we use it. Write to [email protected] from the email on your account, so we know it is you, and we will answer within six months. If a request is complex, we may need up to twelve more months, and we will tell you so. Deleting your account removes your application and our review notes with it. Saved cabins and tickets are kept under your email, so ask us to remove those too. We keep the signature records an agreement needs.
11. Email
We send the messages you need: sign-in codes, links and tickets, our decision on your application and a new member’s welcome. News goes only to people who signed up for it, from launch, and each news email carries our postal address and a one-click way to stop. News emails also tell us whether they were opened and which links were clicked; the messages you need are never tracked this way. Links in our emails carry a label naming the email, so our analytics can show which email brought you back. Planned: reminders to finish an application you started. Each will carry our postal address and a one-click way to stop them.
12. Children
The site is for adults: you must be 18 or older to use its accounts, and we do not knowingly collect data from children.
13. Your privacy choices
In Europe (the EEA, the UK and Switzerland), we ask before PostHog or X’s pixel runs, and each is a separate choice. Until you choose, neither runs. If you decline analytics, PostHog only counts your visit, without storing anything on your device or recording it. Elsewhere, both run unless your browser sends Global Privacy Control or Do Not Track; if it does, we load neither. Wherever you are, you can turn either off, or back on, under Your privacy choices, next to the link to this policy.
14. Security
Our secret keys live only in our hosting and database providers’ settings, never in the site’s code. Our database returns only your own records to you, and the team’s review list sits where the website cannot reach it. The app’s download link works for one hour, and only after we check your sign-in and membership.
15. Planned features
We will update this policy before we add sign-in with Google, Discord or X, or the video library (played through Vimeo). X’s pixel will not run on the library’s pages.
16. Changes
We will post each new version with its date, and email account holders before a material change takes effect.
17. Contact
[email protected], 99 Wall Street #5857, New York, NY 10005.