Privacy Policy
Last updated 5 October 2026.
- Controller
- Clifford Balinskas, a sole proprietor trading as Intraorbit
- Contact
- [email protected]
- Service
- Orbital Docket
This policy covers personal data we hold about visitors to this site and about subscribers to Orbital Docket. It is written to be specific: the lists below are what we actually hold, and not a catalogue of what a service of this kind might hold.
1. Visiting this site collects nothing about you
The public pages — this one, the home page, the terms and the refund policy — set no cookies, load no third-party scripts, embed no fonts from another origin and run no analytics. There is no tracking pixel, no advertising identifier and no session for a visitor who has not subscribed. The pages are static files and the figures on the home page come from a single file served from this same domain.
The one exception is the checkout page, which you reach only by choosing to subscribe. It loads Paddle's checkout script from Paddle's own domain, because the card form is Paddle's and must not run on ours. Paddle, as merchant of record, may set its own cookies there; they are described in Paddle's privacy notice. No other page loads it.
The subscriber sign-in page, on app.intraorbit.com, loads Cloudflare Turnstile: a check that a person, not a script, is asking for a sign-in link. It runs in your browser, is provided by Cloudflare as our processor, and sets no advertising or tracking cookie. We record a keyed hash of the requesting IP address for a day, to limit how many links can be requested, and then delete it.
Our host, Cloudflare, keeps standard server logs of requests reaching the site, which include IP addresses. We use them to keep the site up and to investigate abuse, and once a week we read from them how many requests each public page received, and how many arrived by a link we published (the campaign tag in the address). That count is a total per page: we do not read, store or keep any visitor's address for it, and it needs no script or cookie on the page.
2. What we hold about a subscriber
| Data | Why we hold it | Legal basis |
|---|---|---|
| Your email address | To sign you in, to identify your subscription, and to send service notices (and, once it is offered, the daily summary) | Performance of our contract with you |
| Your Paddle subscription and customer identifiers, the subscription status and the date the current period ends | To know whether your access is active. This is a copy of what Paddle holds; Paddle remains the record of truth for it | Performance of our contract with you |
If you reached the checkout through a link we published, that link's campaign
tag (for example learn-25-164), stored with your subscription |
To know which of our own articles and posts lead people to subscribe. The tag travels in the link only: we set no cookie and use no tracking script to record it | Our legitimate interest in knowing which of our publications are useful |
| A session cookie set when you sign in, and the sign-in times associated with your subscription | To keep you signed in, and to detect a single subscription being used by several people at once, which our terms do not permit | Performance of our contract, and our legitimate interest in preventing credential sharing |
| A count of the data requests your account makes in each minute, hour and day | To pause an account making requests far faster than a person reads, and to detect bulk extraction of the corpus, which our terms do not permit. Minute and hour counts are deleted after a day, daily counts after ninety days | Our legitimate interest in protecting the Service |
| Server logs of requests you make while signed in | Security, debugging, and detecting bulk extraction of the corpus | Our legitimate interest in protecting the Service |
We never hold your card details. Payment is taken by Paddle, which is the merchant of record; card and billing data go to Paddle and not to us. We receive the fact of a payment, the subscription identifier and the country used for tax purposes.
We do not collect special category data, we do not build profiles, and we do not make automated decisions that have a legal or similarly significant effect on you.
3. Cookies
We set one cookie, and only after you sign in: a session cookie that identifies your signed-in session. It is HTTP-only, restricted to this site, and it carries no advertising or analytics identifier. There is no cookie banner because there is nothing to consent to — the cookie is strictly necessary to provide a service you asked for, and no cookie is set for a visitor who has not signed in. The checkout page is the exception described in section 1: Paddle may set cookies there for the payment.
Cloudflare may set its own cookies for security and bot mitigation on requests to this domain. Those are set by Cloudflare as our processor and are described in Cloudflare's own documentation.
4. Who else processes it
| Processor | What they handle |
|---|---|
| Paddle.com Market Ltd | Payments, invoicing, tax, and the subscription record. Merchant of record for every purchase |
| Cloudflare, Inc. | Hosting, content delivery, the stored subscriber and session records, and access control |
| GitHub, Inc. | Runs the daily pipeline that builds the corpus. It processes public filings only and holds no subscriber data |
| Google LLC | Receives and stores the email you send to our support address. Cloudflare forwards it to a mailbox hosted by Google, so anything you put in a support message is held there |
| Resend (Plus Five Five, Inc.) | Delivers the email we send you: a welcome email when you subscribe, sign-in links and, once it is offered, the digest. It receives your email address and the message, and nothing else |
We do not sell personal data, we do not share it for advertising, and we do not pass it to anyone not named above except where we are legally required to.
These providers operate internationally, so your data may be processed outside your own country, including in the United States. Transfers rest on the providers' standard contractual clauses and equivalent safeguards.
5. How long we keep it
- Subscriber records — while your subscription is active, and for twelve months after it ends so that a returning subscriber keeps their history and their grandfathered price. After that we delete them.
- Sessions — deleted when they expire or when you sign out.
- Billing records — kept by Paddle for as long as tax law requires, under Paddle's own retention rules.
- Server logs — kept for a short operational period and then discarded.
6. Your rights
You can ask us for a copy of the personal data we hold about you, to correct it, to delete it, to restrict or object to how we use it, and to receive it in a portable form. Write to [email protected] and we will respond within one month.
Deleting your data ends your subscription, because the email address is what the subscription is attached to. Billing records that tax law requires Paddle to keep are not ours to delete.
If you think we have handled your data badly, please tell us first. You also have the right to complain to the data protection authority in your country.
7. Security
Access to the corpus requires a signed-in session. Sign-in is by one-time link sent to your email address, so there is no password for us to store or for anyone to leak. Subscriber records are held in our provider's managed database and are reachable only by the application and by the operator.
8. Changes
We will update this page when what we hold changes, and the date at the top is the date of the current version. Where a change materially affects you we will email the address on your subscription.