Legal

Privacy & Cookies

Effective 12 September 2026

Deeptech Navigator (at deeptechnavigator.com) is operated by Analystology LLP ("we", "us"). This page says what we collect about the people who use the Service, why we collect it, how long we keep it and who else sees it. It sits alongside our Terms of Use & Data License, which governs the data the Service publishes about companies - a different thing from this page, which is about you.

The short version: we ask for an email address so you can sign in, we keep a record of what the account fetched so a subscription cannot be resold or scraped, and we use two analytics products to see which parts of the site are worth building. We do not sell personal data, and we do not run advertising.

1. What we collect, and why

Your email address

The only thing we ask for to create an account. Sign-in is a one-time code sent to that address - there is no password, so we never hold one. Authentication is handled for us by Supabase (§4).

A record of gated fetches

For each request to a subscriber-only page or dataset: the time, the account, the route, the shape of the query (which filters, not what you typed), how many records came back, and the IP address. This is what enforces the fair-use limit and is how we detect an account being used to bulk-extract the database.

Searches

The normalised text of searches run on the Service, with the number of results, alongside the account and a hashed IP. We read these in aggregate to find questions the Service answers badly. Search text is not sent to either analytics provider (§3).

Things you save

Items you add to Saved, with any label or note you write on them. Visible only to your account.

Enquiries and demo requests

Whatever you type into those forms - name, email, organisation, message - so we can reply.

Sign-in session state

One row recording the current session for your account. A subscription is for one person, so signing in on a new device ends the session on the old one; this row is what makes that work, and it is deleted when you sign out.

API tokens

If you connect an AI tool, we store a hash of the token (never the token itself), a short non-secret prefix so you can tell your tokens apart, and when it was last used.

A browser check on our forms. Automated submissions were flooding the contact and sign-up forms, so before one of those forms is sent your browser is asked to finish a small piece of computation we set it. The whole exchange is between your browser and this site: it sets no cookie, it sends nothing to any third party, and it collects nothing about you or your device. All it establishes is that a real browser spent a moment of work before the form was submitted.

2. Why we are allowed to hold it

Your email and session state are needed to perform the contract you entered into when you signed up - without them there is no account. The access record, the rate limits and the abuse flags rest on our legitimate interest in keeping a paid research product from being resold or scraped, and on our obligation to the people who pay for it. Analytics rests on consent where consent is required, and otherwise on our legitimate interest in knowing which parts of the Service are used. Enquiry forms are simple consent: you chose to write to us.

3. Analytics, and what it is not told

We use two products to understand how the Service is used: Google Analytics 4 (Google) and PostHog (PostHog Inc., US cloud). Both receive the pages you visit, rough location derived from IP, and technical details of your browser and device. PostHog additionally records anonymised interaction with the page - clicks, scrolling, and session replay - which we use to find where the interface fails people.

Three limits we impose on our side, which are worth stating plainly:

Your searches are not sent. The address of a results page is rewritten before it leaves your browser: the filters you picked are kept, the words you typed are removed.
Nothing you type is recorded. Session replay masks every input field, so form contents never reach the recording, and replay pauses altogether on any page whose address carries a search term.
Your account pages are not filmed. Replay is switched off on the account and billing screens, and on the admin console, which is ours rather than yours.

Where PostHog is concerned we identify you to it by your internal account identifier, with your email attached as a property of that profile so we can recognise a subscriber. If you would rather not be identified at all, tell us at contact@analystology.com and we will exclude your account.

You can also stop both products at the browser level: Google Analytics offers a browser opt-out add-on, and either can be blocked by any tracker-blocking extension or by a "Do Not Track" / Global Privacy Control setting, which PostHog honours by default.

4. Who else processes it

Supabase

Database, authentication and the sending of sign-in codes. Hosted in ap-south-1 (Mumbai).

Google (Analytics 4)

Site analytics.

PostHog Inc.

Product analytics and session replay, US cloud region.

Our email provider

Delivers sign-in codes, welcome mail and any digest you are subscribed to.

Our hosting provider

Runs the application server and keeps standard web server logs.

We do not sell personal data, do not share it with data brokers, and do not use it to target advertising. Some of these providers are outside India, so using the Service involves your data being processed abroad.

5. Cookies and similar storage

We set no advertising cookies. What the site does store falls into three groups:

Strictly necessary

Supabase authentication cookies that keep you signed in, and - for us - an admin session cookie. The Service cannot work without these, so they are set whether or not you accept anything else.

Analytics

Google Analytics sets _ga and related identifiers; PostHog sets one cookie holding a random device identifier. Both exist to tell one visit from another and neither contains your name or email.

Local storage

Small preferences kept in your own browser - the state of a filter or a dismissed notice. These never leave your device.

Clearing site data in your browser removes all of it, and signs you out.

6. How long we keep it

Account and email

For as long as the account exists, and then as needed to settle billing or disputes.

Gated access record

Retained as an audit trail of how a subscription was used. We keep it for the life of the account.

Search log

Read in aggregate; individual rows are of no use to us once a question has been answered.

Enquiries

Kept while the conversation is live and for our own record of it afterwards.

Analytics

Held by Google and PostHog under their own retention schedules.

7. Your rights

You can ask us for a copy of what we hold about you, ask us to correct it, or ask us to delete your account and the personal data attached to it. Write to contact@analystology.com and we will respond within 30 days. Deleting an account removes your email, saved items and session state. We may keep a minimal record that an account existed and how much data it drew, because that is the evidence of how a subscription was used - it is not linked to a live account once yours is gone.

If you are in a jurisdiction that gives you a right to object to analytics, you may exercise it by the means in §3, or by writing to us. Depending on where you live you may also have the right to complain to a data protection authority.

8. Security

Traffic is served over HTTPS only. Passwords are not stored because there are none. API tokens are stored only as hashes. Access to the production database is restricted to the operators of the Service, and the administrative console is behind its own authentication. No system is perfect: if you believe you have found a vulnerability, please write to contact@analystology.com rather than testing it against other people's accounts.

9. Children

The Service is a professional research tool and is not directed at children under 18.

10. Changes, and how to reach us

If this policy changes materially we will move the effective date above and, where the change affects your rights, tell account holders by email. Questions, requests and complaints all go to the same place: contact@analystology.com, Analystology LLP.