Privacy Policy

What Pulse is

Pulse is a private, internal tool operated by BlindspotLab for a single operator, Mojeeb Titilayo. It is not a public service, it has no sign-up, and it does not accept registrations. Access is limited to a hard-coded allowlist of email addresses held in the server configuration.

If you have arrived here and you are not on that allowlist, there is nothing here for you to use and no account for you to hold.

Google account data

Pulse uses Google Sign-In solely to confirm that the person opening the dashboard is the operator. When you sign in, Google provides Pulse with:

• Your email address. Used to check your account against the allowlist. This is the only access-control mechanism in the product.
• Your display name. Shown in the dashboard sidebar so the operator can see which account is signed in.
• Your Google subject identifier. A stable, opaque id Google issues for your account, stored so a later sign-in is recognised as the same account.
• Whether your email is verified. An unverified email is refused.

The OAuth scopes Pulse requests are openid, email and profile. Nothing else. Pulse does not request, and cannot read, your Gmail, Drive, Calendar, Contacts or any other Google service.

No Google tokens are stored

This is worth stating plainly because it is unusual. Pulse exchanges the one-time authorization code with Google's token endpoint, reads the identity claims from the response, and then discards the result. It does not store a Google access token, and it does not request or store a refresh token.

After sign-in, Pulse issues its own session cookie. It therefore has no standing ability to call any Google API on your behalf, at any point, for any reason.

Cookies

Pulse sets two cookies and no others. There is no analytics, advertising, or tracking cookie of any kind.

• pulse_session holds your email address, display name and an expiry time, signed with HMAC-SHA256 so it cannot be altered. It is HttpOnly, Secure and SameSite=Lax, and lasts 30 days. It is not readable by any script in the page.
• pulse_oauth_state holds a single-use random value during the sign-in round trip, to prevent request forgery. It lasts ten minutes and is cleared as soon as sign-in finishes.

Where your data is stored

Account data is stored in a Cloudflare D1 database controlled by BlindspotLab. One row per permitted operator, holding the email, display name, Google subject identifier, role, and the times the account was created and last seen.

That is the complete extent of personal data Pulse holds about a signed-in operator.

Third parties

Pulse sends data to several external services in the course of its work. None of them receives your Google profile data.

• AI providers (NVIDIA, OpenRouter). Receive the research material and drafting instructions the operator supplies, so content can be generated. They do not receive account identities.
• Notion. Receives finished editorial content as an archive the operator reads.
• Telegram. Carries notes and briefs between the operator and Pulse, to a chat id the operator configured.
• GitHub. Read-only. Pulse reads repository activity the configured token can already see, and never writes.
• Search providers, where configured. Receive research queries only.
• Cloudflare. Hosts the application and its database.

Your data is never sold, never licensed, and never shared for advertising. Pulse has no advertising relationship with anyone.

Content the operator creates

Separately from account data, Pulse stores the operator's own working material: notes, drafts, research sources, opportunity records, performance figures and revenue entries. This is BlindspotLab's business data rather than third-party personal data, and it is visible only to allowlisted operators.

Pulse scans this material for credentials before storing it and redacts anything that matches a known secret pattern.

Retention and deletion

Account rows are kept while an address remains on the allowlist. Removing an address from the allowlist revokes access on the next request, because the allowlist is re-checked on every request rather than trusted from the cookie.

To have an account row deleted outright, or to ask what is held, contact the address below. Since Pulse has at most a handful of operators, such a request is handled directly rather than through a form.

Security

• All traffic is served over HTTPS.
• Session cookies are HMAC-signed and HttpOnly.
• Scheduled jobs and the Telegram webhook require shared secrets, compared in constant time.
• Secrets are held in Cloudflare's secret store, never in the repository.
• Logs are scanned and redacted so a credential cannot leak through observability.

Children

Pulse is an internal business tool. It is not directed at children and is not usable by anyone outside the operator allowlist.

Changes

If this policy changes in a way that affects how Google account data is handled, the date at the top of this page is updated and the previous version remains in the project's version history.

Contact

BlindspotLab
mojeeb.eth@gmail.com