Cookies and browser storage
Every cookie and browser storage item nexstella.com uses, what each one is for, and how to change your choice.
Legal
Privacy notice
This notice covers nexstella.com and its publication, Nexstella Insights, at blog.nexstella.com. The two sites do little with personal data: they take the details you choose to send, run Google Analytics only if you allow it, and count visits with cookieless Cloudflare beacons that set nothing in your browser.
In short
Across nexstella.com and blog.nexstella.com, Nexstella collects only what you choose to send: your message and contact details, or the email you give to book a call. Google Analytics runs only if you allow it, and we honor the Global Privacy Control signal. Cloudflare's cookieless, aggregate page-view measurement runs for everyone. We never sell personal data. To see, correct or delete what we hold, write to [email protected].
Last updated
01 Scope
What does this notice cover?
This notice covers the nexstella.com website (its pages, the contact form, the booking flow and the analytics) and Nexstella Insights at blog.nexstella.com. How we handle data inside an engagement is agreed in writing for that engagement, not on this page.
Two things are worth knowing up front. The booking calendar and the spam check load from their providers when you use those steps, which shares your network address with them. And the context you brought, meaning what you picked on the site, travels with a booking or a message. We never ask for more than we need to answer you.
Nexstella Insights has no forms and no accounts of its own. Its booking buttons take the email you type to the Meet step on nexstella.com, where this notice applies as it does to any booking. Your analytics choice is kept in one cookie on .nexstella.com, so a choice made on either site holds on both, and the blog counts visits with its own cookieless Cloudflare Web Analytics beacon.
02 What we collect
What do we collect, and why?
The table lists everything the site collects. A personal address from a free email provider typed into a booking field is kept too, so the reminder still reaches you, and the form points you to the contact tab instead.
| What | Which details | Why |
|---|---|---|
| Your message | First and last name, email, and optionally phone, company and role; the topic you chose, your message, and a short note of how you reached the form. The brief form also takes the scope, timeline, decision date, budget, a link to documents and whether you want an NDA. | To read your message, reply to it, and judge whether we are the right fit for what you need. |
| The email you give to book a call | The email you enter in a booking field, the kind of call you chose, the page you were on, the context you brought and your network address. If you book, the name and time you enter in the calendar. | To send the calendar invite. If you stop before picking a time, we send one reminder, by default about an hour later, with a link back to the calendar and a way to write to us. When it goes out, Nexstella's inbox gets a short "booking not finished" note. |
| Page views and interactions, if you allow analytics | The page, the referring page, approximate location from the network address, and the kind of device. Also which call-to-action was seen or used, whether an email typed on the Meet step is a work or personal address (never the address itself), a completed booking, and a sent message with the page of the form. Google Analytics adds its standard interaction measurement: scrolls, video engagement and file downloads. | To see which pages and calls to action help visitors and which do not. Never your name or email address. |
| Abuse limits | One-way hashes of your network address and of the email address you use, never the address itself. | To stop a script from flooding the forms. They are kept for about an hour, or twelve hours for the check that allows one booking reminder per address. |
| Server and security logs | Request logs kept by our hosting providers, including network addresses. The email typed on the Meet step is briefly in the page address before the site removes it, so it may appear in these logs. | To deliver the site, keep it available and block abuse. |
03 How you reached us
How do we know how you reached a form?
When you book a call or send a message, a short note goes with it: the page you wrote from, the page before it, the button you used, the first page of your visit and any campaign tags in the link that brought you. It tells us which pages lead to conversations. It records the page and the campaign tags you arrived with, and campaign tags can carry identifiers.
The note is kept in your browser's storage until you send a message or give an address to book a call. Nothing is sent before that. The cookies page lists the storage items by name.
04 Processors
Who processes your data?
These providers run parts of the site for us. Each one sees only what it needs for its role, and they may process data outside the country you write from. The table names each provider, what it does and what it sees.
| Provider | What it does | What it sees |
|---|---|---|
| Hostinger | Hosts the files of both sites, and nexstella.com's form endpoints. | Requests to the site, including network addresses, and the messages and booking emails passing through. |
| Cloudflare | Serves both sites in front of the host, runs the spam check on the forms, and counts visits with a cookieless beacon on each site. | Requests to the site, including network addresses. The spam check loads from Cloudflare when you use a form. |
| Resend | Delivers your message to our inbox and sends the one booking reminder. | The full content of your message, delivered to Nexstella's inbox. For a booking you did not finish, the reminder email to you and the note to our inbox. |
| HubSpot | Keeps your enquiry as a customer record, so it is not lost between people. It is used only when we have connected it. Cal.com's HubSpot app, if connected, may also add visitors who book, with their name. | When connected: the fields of your submission or of the unfinished booking, the context lines, the page you came from and your network address. For a booking you did not finish, this is passed on when the reminder goes out. |
| Cal.com | Runs the booking calendar and sends the invite and the video link. | The email you gave, the call you chose, the note of how you reached the page, and the name and time you enter. It loads from Cal.com when you reach the calendar step, which shares your network address with it. |
| Google Analytics, only with consent | Measures page views and interactions, and runs only if you allow it. | Page views, the kind of device, which call-to-action was seen or used, whether an email typed on the Meet step is a work or personal address (never the address itself), a completed booking, a sent message with the form's page, and its standard interaction measurement (scrolls, video engagement, file downloads). Never your name or email address. |
05 Retention
How long do we keep it?
We keep personal data only as long as there is a reason to, and we delete it when you ask. This is what applies to each kind of record the site creates, from your message to the logs our hosting providers keep.
- Your message: while the conversation is live, and for as long as there is a reason to remember it, such as an engagement that followed.
- The customer record: while you are a client or an active prospect, and removed when you ask.
- A pending booking reminder: deleted when it is sent, when you book or send a message, or automatically after 7 days. While it is pending it holds your email, the page, the context you brought and your network address.
- If a reminder cannot be sent, it is retried a few times. Reminders over the daily limit wait for the next day.
- Abuse limits: one-way hashes, kept for about an hour, or twelve hours for the one-reminder-per-address check.
- Analytics: aggregated reports with no identifier attached to you, kept under the provider's retention settings.
- Server and security logs: kept by the hosting providers under their own settings.
06 What we never do
What do we never do with your data?
Some things are worth saying plainly, because many sites do them. None of them happens on nexstella.com, and a change to any of them would be reflected on this page.
- We do not sell personal data, and we do not share it with advertising networks.
- The site runs no advertising cookies, no tracking pixels and no cross-site identifiers.
- We do not build profiles of visitors, and we make no automated decisions with legal or similarly significant effects.
- Google Analytics runs only if you allow it, and we honor Global Privacy Control even if you agreed earlier. Cloudflare's cookieless, aggregate page-view measurement runs for everyone and sets nothing in your browser.
- We never ask for passwords, access keys or other secrets. Please do not send them through the form.
07 Your choices
What can you ask us to do?
Write to [email protected] with "Privacy" in the subject line, and a person will handle the request. You do not need to cite a regulation first. Depending on where you live, you may have further rights, such as objecting to processing or complaining to a supervisory authority.
- See what we hold about you.
- Have it corrected.
- Have it deleted, with a confirmation once it is done.
- Change your analytics choice at any time; the cookies page explains how.
08 Responsible
Who is responsible for your data?
Nexstella is responsible for the personal data described on this page. Questions, requests and complaints about privacy go to [email protected], with "Privacy" in the subject line.
If we change this notice, the "Last updated" date changes, and a change to what we collect is announced on the site rather than made quietly.