What happens to your data.
Nookivia keeps the information needed to look after your trips, and tries hard not to collect things it doesn't need. Here's what we use, why we use it, and the choices you have.
At a glance
Your trips belong to your account.
Nookivia uses Clerk for sign-in and keeps a small account record of its own. We do not store passwords, OAuth access tokens or the raw profile data held by your identity provider. Optional website analytics are only used after you choose the Analytics category in Cookie settings.
Travel data you put into a trip can be personal. Treat a shared trip as shared information: only add information you are comfortable making available to the people you choose to share it with.
Who is responsible
Nookivia is the service operator.
For this privacy notice, “Nookivia” means the operator of nookivia.com and the Nookivia service. For privacy questions or rights requests, contact privacy@nookivia.com.
This notice applies to the Nookivia website and the account and trip features provided through it. It does not change the privacy policies of the third-party services Nookivia uses; those providers publish their own information about how they handle data.
The useful bits
What we collect
Account information
When you sign in, Nookivia keeps an internal account ID plus the Clerk user ID needed to connect your session to that account. We also keep your primary email address, display name and avatar URL so your account and shared trips can work properly.
Trip information
Nookivia stores the travel information that forms your trips, such as dates, places, routes, booking references, providers, prices and other itinerary details you add or edit. The exact fields depend on the trip data you use.
Technical information
Our hosting and security providers may process technical request information such as IP address, browser information and request timing to deliver and protect the service. Nookivia does not keep these values as part of your normal account record.
Messages to support
When you write to us through the contact form, or by email to help@nookivia.com or privacy@nookivia.com, we keep what you wrote, your name and email address and, if you were signed in or emailed from your sign-in address, which account it came from, with the topic and trip you picked. From an email we keep its subject and text, up to 2,000 characters for a new message and 5,000 for a reply, and its message ID so your replies join the conversation. We don't keep attachments, only how many there were, and we never forward your email anywhere. If you use the form without signing in, we keep a scrambled key made from your IP address (for an IPv6 address, from the first half of it), rather than the address itself, to limit how many messages can be sent in an hour; it's deleted with the next message sent without signing in after that hour, or with your message. A scrambled key is not anonymous: the same address always makes the same key, so we treat it as your personal data.
The waiting list
When you join the waiting list, we add your email address to it. The list is kept by Clerk, our sign-in provider, who emails you to say you're on it and, when your place is ready, to invite you. To stop the form being used to fill someone else's inbox, we also keep scrambled keys made from your email address and your IP address (for an IPv6 address, from the first half of it), rather than the addresses themselves, to count how often each is used in an hour; they're deleted with the next request to join after that hour. As above, a scrambled key is not anonymous, so we treat it as your personal data.
Cookie and analytics choices
The site stores your cookie-consent choice in an essential consent cookie. Microsoft Clarity, Google Analytics 4 and Cloudflare Web Analytics are optional and are only started after you allow Analytics. See our Cookie Policy for the current inventory.
Where it comes from
We get information from a few places.
Most information comes directly from you, either when you use Nookivia or when you choose to add or edit trip details. Sign-in information comes from Clerk and its supported identity providers. Technical information comes from the systems that deliver the website. Where another service supplies information on your behalf, we only use it to provide the feature you asked for.
Why we use it
What your data lets Nookivia do
| Purpose | Typical data | Lawful basis |
|---|---|---|
| Run your account and keep you signed in | Account ID, Clerk ID, email, profile claims | Contract |
| Store and display your trips | Trip and itinerary information | Contract |
| Provide sharing and attribution features | Trip data, display names, avatars | Contract |
| Answer your messages to support | What you wrote, your name and email, the account and trip it is about | Contract for account holders; legitimate interests otherwise |
| Keep your place on the waiting list and invite you | Your email address | Steps you ask us to take before a contract |
| Stop the contact form and the waiting list being flooded, and the waiting list being used to fill someone's inbox | A scrambled key made from your IP address (and, for the waiting list, your email address), not the addresses themselves | Legitimate interests |
| Keep the service secure and troubleshoot failures | Technical and operational information | Legitimate interests |
| Understand how the public site is used | Analytics events and device information | Consent |
| Meet legal obligations and respond to lawful requests | Relevant records | Legal obligation |
The supporting cast
Who we share data with
Nookivia uses a small number of service providers to run the product. They act only to the extent needed for the service they provide and have their own privacy information.
Clerk
Our identity and session provider. Clerk handles provider sign-in, verified identity information and session cookies, and keeps the waiting list. Nookivia does not store passwords.
Clerk Privacy PolicyCloudflare
Our website and application infrastructure provider. Cloudflare may process technical request data to deliver, secure and operate the service.
Cloudflare Privacy PolicyAnalytics providers
Microsoft Clarity, Google Analytics 4 and Cloudflare Web Analytics receive optional analytics information only after Analytics consent. They are not required to use the core trip service.
See the Cookie Policy for the current analytics details.If Nookivia introduces another processor or integration that materially changes what personal data is processed, this policy will be updated before that use begins where required.
Where data is processed
Some providers operate globally.
Nookivia and the providers it uses may process information in countries outside the UK. Where UK data protection law requires a safeguard for an international transfer, we rely on the mechanism applicable to that transfer, such as an adequacy decision or appropriate contractual safeguards.
Keeping things tidy
How long we keep information
Account data
We keep your account information for as long as your Nookivia account exists, unless the law requires a longer period.
Trip data
Trip information is kept while the account owns it. When an account is deleted, account-owned data is intended to be deleted rather than kept indefinitely.
Messages to support
A message from your account, and our replies, are kept with your account and deleted with it. A message sent without an account isn't deleted automatically yet; email privacy@nookivia.com and we'll delete it.
The waiting list
Your email stays on the waiting list until we invite you, and Clerk keeps the invitation with it. Email privacy@nookivia.com and we'll take you off the list. The scrambled keys that limit how often the form can be used are deleted with the next request to join after the hour they count.
Consent and analytics
The essential consent cookie currently lasts 182 days. Optional analytics are controlled by the providers' own retention settings and our consent configuration.
Operational records
Security and operational records are retained only for as long as needed for the purpose they serve, subject to the retention controls of the infrastructure provider.
Your choices
You have rights over your information.
Depending on the circumstances and the lawful basis involved, UK data protection law gives you rights to ask for access to your personal data, correction of inaccurate data, deletion, restriction of processing, objection to certain processing, and portability. Where we rely on consent, you can withdraw it at any time. Withdrawing cookie consent does not undo processing that already happened before withdrawal.
To make a privacy request, use the contact form or email privacy@nookivia.com. We may need to verify your identity before completing a request. We will respond within the timeframe required by applicable law.
You can also complain to the UK Information Commissioner's Office if you think your information has been handled unlawfully. See ico.org.uk/make-a-complaint.
No black box decisions
We do not make significant decisions about you automatically.
Nookivia does not currently use solely automated decision-making that produces legal effects or similarly significant effects on you.
Keeping it safe
Security is part of the design.
Nookivia uses encrypted connections, provider-managed authentication, access controls and data minimisation to reduce the amount of personal information that can be exposed. No internet service can promise perfect security, but we will investigate and respond to security incidents according to our obligations.
When things change
This notice will change as Nookivia grows.
We'll update this page when our data practices change materially. The effective date and version at the top of the page tell you which notice you are reading. Where a change requires renewed consent or another notice before processing begins, we'll provide it in the appropriate place.
Questions about your data?
We'd rather make the answer clear than hide it in small print.
Contact Nookivia