Privacy policy
Last updated: 29 June 2026
OO Insights (at ooinsights.space) is an independent project run by a solo developer. I try to collect as little personal data as possible — there are no tracking or advertising cookies, no ad networks, and no third-party analytics that profile you. This policy explains the little I do collect, why, and your rights over it.
Who I am
I am the operator of OO Insights and the data controller for the personal data described here. You can reach me about anything in this policy — and to exercise any of your rights below — at privacy@ooinsights.space.
What I collect, and why
Access cookie.While the site is in private preview it sits behind a password. When you log in, I set a cookie that simply records that you passed the gate, so you don't have to re-enter the password on every page. It contains no personal information beyond that. Lawful basis: it is strictly necessary to provide the service you asked for.
Feedback you send.If you use the feedback button, I store what you wrote, an optional name if you add one, the page you sent it from, and your browser's user-agent string (to help me reproduce any issue). I only get this if you choose to submit it. Lawful basis: your consent in sending it, and my legitimate interest in improving the product. Please don't include sensitive personal details in feedback — it isn't the place for them.
Server logs. Like any website, my hosting provider processes technical request data, including your IP address, to deliver the site and protect it from abuse. Lawful basis: my legitimate interest in operating and securing the site.
Cookies
I use only two strictly-necessary cookies — the access cookie above (named site_auth) and, for me, an admin cookie (admin_auth). Both are functional: they keep you (or me) signed in and nothing more. Because they are strictly necessary, they don't require a consent banner. For usage measurement I use Vercel Web Analytics, which is cookieless— it sets no cookies, builds no personal profiles, and doesn't track you across sites — so it likewise doesn't require a consent banner (my lawful basis is legitimate interest in understanding aggregate usage). I use no advertising or cross-site tracking cookies of any kind.
Who processes data on my behalf
I run OO Insights on a small number of trusted providers, who process data only to provide their service to me:
- • Vercel — hosting and content delivery (processes request data such as IP addresses), and cookieless Web Analytics (aggregate visit counts; no cookies, no cross-site tracking, no personal profiles).
- • Supabase — the database that stores feedback and cached space-data figures.
- • Anthropic — generates the weekly brief. It only receives aggregate space-economy figures (e.g. launch and satellite counts), never your personal data.
These providers are based in the United States, so the limited data above may be processed outside the EU/EEA. They offer standard data-transfer safeguards (such as Standard Contractual Clauses). I do not sell your data, and I don't share it with anyone except as described here or where I'm legally required to.
How long I keep it
The access and admin cookies expire after 30 days. Feedback is kept while I act on it and for a reasonable period afterwards, then deleted. Cached space-data figures contain no personal data. You can ask me to delete your feedback at any time.
Your rights
If you're in the EU/EEA (or UK), you have the right to access, correct, delete, or restrict the personal data I hold about you, to object to processing based on legitimate interest, and to data portability. To exercise any of these, email me at the address above and I'll respond as soon as I reasonably can. You also have the right to complain to your local data-protection authority.
Age restrictions
OO Insights is intended for a professional audience and is not directed at minors. I do not knowingly collect personal data from anyone under the age of 16.
Changes to this policy
I may update this policy as the site evolves (for example, if I add analytics or a paid tier). I'll change the date at the top when I do, and material changes will be made clear.
See also the disclaimer and the methodology.