Skip to main content

Legal

Privacy Policy

Last updated: August 16, 2026

This policy explains what information Deepstory Research ("we", "us") collects when you use deepstoryresearch.com (the "Site"), how we use it, and the choices you have. By using the Site you agree to this policy.

Information we collect

  • Account information. If you create an account, we collect your email address and authentication details through our authentication provider (Supabase). Passwords are stored hashed; we never see them in plain text.
  • Usage and analytics. We record first-party, privacy-respecting product events (for example, which articles are viewed, charts expanded, tables or context files downloaded, and searches run) to improve the Site. Logged-out visitors are attributed to a randomly generated session identifier stored in a first-party cookie (ds_sid), not to your identity.
  • Search demand feedback. If a search returns no results, you can tell us what data you expected and optionally leave your email so we can follow up if we build it. We store the search terms and your answer as first-party demand data, kept separately from product analytics, to prioritize what to add next — never to personalize your feed, and never shared with any analytics or advertising provider.
  • Newsletter. If you subscribe, we store the email address you provide to send you updates. You can unsubscribe at any time.
  • New-dataset notifications. If you tick the notification box during onboarding or when downloading a context file, we store your email address, the sectors you follow, and the date, page, and wording of the consent you gave. We use this only to email you — at most once a week — when a new dataset matching those sectors is published. If nothing relevant is published, we send nothing.
  • Technical data. Standard server and CDN logs (IP address, browser type, pages requested) are processed by our hosting provider (Netlify) for security and reliability.

Cookies

We use cookies that are strictly necessary to operate the Site (such as the session cookie and, when you log in, authentication cookies) and a first-party analytics cookie. If and when we display advertising (see below), our advertising partner may set additional cookies. You can control cookies through your browser settings; disabling necessary cookies may affect Site functionality.

Advertising

We may display advertising provided by Google AdSense. Google and its partners use cookies and similar technologies to serve ads based on your prior visits to this and other websites, and to measure ad performance. Google's use of advertising cookies enables it and its partners to serve ads to you based on your visit to our Site and/or other sites. You can opt out of personalized advertising by visitingGoogle Ads Settings. For visitors in the EEA, UK, and Switzerland, we present a consent banner via a Google-certified consent management platform before any non-essential or advertising cookies are set, and serve non-personalized ads where consent is not given. SeeGoogle's advertising policiesfor details.

Onboarding & personalization

If you complete our onboarding questionnaire, we collect only what we use to personalize your experience — every field is optional and declared by you, never inferred. The "For You" page never shows a reason for a recommendation that isn't one of the fields below, and never says a recommendation is "because you viewed" or otherwise names inferred browsing behavior:

  • What you're usually making (a deck, spreadsheet/ model, report, memo, article, AI-agent/RAG context, or "just exploring"). Used to rank what we surface and to default the context-file/task-pack builder's export format.
  • A current task prompt, if you give one. Free text describing what you're working on right now, offered on one onboarding screen so we can hand it straight to the task builder prefilled. This is never stored — it never reaches our database, an analytics event, a URL, or a page title — and exists only in your browser tab for that one handoff.
  • Sectors you pick (up to three) and an optional geography. Used to match and prioritize research in your feed, and to pre-check relevant datasets.
  • Who it's usually for (yourself, your manager or board, a client, an investor, an academic audience, or the public). Used to default tone and depth in the builder.
  • Tools you use (ChatGPT, Claude, Gemini, NotebookLM, Excel/Sheets, PowerPoint/Slides, other, or none). Used only for product copy and export-format defaults — never for recommendations.
  • Persona (student / professional / entrepreneur) and its follow-up answers (field of study, function, or stage). Used for cold-start recommendations before we have any other signal, and to pre-fill the builder. Asked only where it changes a default — we do not ask for your employer by default; we only ask for a company name when you explicitly start a company-specific task, it is always optional, and it is never used to infer anything else about you.
  • Missing-dataset feedback. Free text describing a dataset or visualization you expected but didn't find. Used to prioritize what we build next — not used to personalize your own feed.
  • Behavior (views, saves, downloads, return visits, and which task packs you explicitly choose to follow). Blended with the above daily to keep your recommendations current — but never named in a visible "because" line; only declared fields and your own explicit follows are ever cited back to you.

You can review or change any of this anytime fromEdit preferences(also linked directly from the top of the "For You" page), and clear everything we've learned from your behavior and persona answers withReset recommendations inSettings— your account, saves, and declared sectors are kept (sectors are removed separately, from "Edit preferences").

Email consents

The weekly newsletter and new-dataset notifications are two separate consents. Neither is ever pre-ticked, opting into one never opts you into the other, and each can be withdrawn on its own — the unsubscribe link in a notification email stops notifications and leaves the newsletter untouched, and vice versa. Unsubscribing takes effect immediately, needs one click, and does not require you to log in.

To decide whether a new dataset is relevant to you we use the sectors you declared and, if you have an account, the interest weights described above. If a notification email includes a "because" line, it only ever cites something you told us yourself.

How we use your information

To provide and secure the Site, deliver content and downloads you request, personalize recommendations, send newsletters you opt into, measure and improve the product, and comply with legal obligations. We do not sell your personal information.

Service providers

We share data only with providers that help us run the Site, under agreements that limit their use of it: Supabase (database and authentication), Netlify (hosting and CDN), and — where advertising is enabled — Google (advertising and, optionally, analytics). These providers process data on our behalf.

Data retention

We keep account data for as long as your account is active and analytics data for as long as needed to understand and improve the Site. You can ask us to delete your account and associated personal data at any time.

Your rights

Depending on where you live, you may have rights to access, correct, export, or delete your personal data, and to object to or restrict certain processing. To exercise any of these, email us atcontact@deepstory.co.

Children

The Site is not directed to children under 16, and we do not knowingly collect personal data from them.

Changes

We may update this policy from time to time. Material changes will be reflected by the "last updated" date above.

Contact

Questions about this policy? Emailcontact@deepstory.co.