Docs

Privacy policy

What PostLens collects, where it goes, how long it is kept, and what it never does: no cookies, no draft storage, no address logging, one hovered card only.

Effective 21 September 2026. PostLens is operated by TechTide AI (Alex Cinovoj), Ohio, United States — the data controller for this site. Contact: alex@techtideai.io. PostLens is built to store as little as possible, as late as possible; this page says exactly what that means.

Cookies

PostLens sets no cookies — first-party or third-party, on any page — and loads no tracking pixels, ad tags, or third-party analytics scripts. That is why there is no cookie banner: there is nothing to consent to. The browser's own storage on your device holds at most two things: your light/dark choice (postlens-theme) and, for the founder only, the sign-in session. Neither leaves your device as a cookie.

The public check page

When you press Check on /check, the draft and the audience line you typed leave your browser once, to the PostLens server, which forwards them to TypeSafe AI for scoring by the Jev model and returns the result. Nothing else is sent: no name, no email, no account, no page contents beyond that draft.

  • Not stored. The draft is never written to disk, a database, or a log. For five minutes the server holds a keyed hash of the draft plus its result (the result carries the audience line and word counts, not the draft text) so an identical paste is answered from memory rather than re-scored; that entry expires on its own and is gone on restart.
  • Not logged. The server log line for a check is structural only: outcome, status, provider, timings, character count, and how many free reads remain. Never the text, the audience, the verdict, the score, or your address.
  • No address stored. The daily free-read allowance is keyed by a one-way keyed hash of your network address bucket, held in memory only and gone on restart. The address itself is never written anywhere.
  • The receipt is drawn on your device. Sharing it is your choice; it never contains the draft text.

TypeSafe AI processes the draft on our instructions to return the score. Its handling of that request is governed by its own terms; PostLens sends only what is described above. The check page and the browser extension send text to TypeSafe AI only, never to a second provider.

Page-view counting

The public pages count views with a first-party, cookieless beacon so we can see which pages are read and where visitors come from. Each view records three things: the page path (for example /docs/the-rubric), the referring site's hostname (never the full URL), and a per-day visitor key — a keyed one-way hash of your network address bucket that cannot be reversed, is different every day, and is never stored beyond the day's count. What survives is daily totals: views, visitors, top pages, top referrers. There is no per-person record, no session replay, no fingerprinting, and the founder's own visits are excluded. Browsers sending *Do Not Track* or *Global Privacy Control* are acknowledged and not counted.

The founder account and the swipe file

  • Sign-in is by email (magic link or code) through Supabase Auth, restricted to the configured founder addresses. There is no public sign-up.
  • Saved swipe-file rows — a draft you chose to save, or a hovered public post with its visible attribution and counts — live in one owner-scoped database table reachable only by the founder account and the server's scoped key. Saving happens only on an explicit click after confirming the rights on the text.
  • Drafts written in the Studio are analysed in memory and never persisted or logged unless saved.
  • The signed-in founder surfaces (the Studio and the desktop app) score each text with two backends at once: TypeSafe AI and OpenRouter (model z-ai/glm-5.3-flash). So a Studio draft, and post text hovered in the desktop app, is sent to both processors, each under its own terms. Both results are labelled by provider; neither is stored by PostLens.

The extension and the desktop app

When you enable the optional LinkedIn extension, it reads exactly the single post card you hover or the composer you are typing in, on a page you opted into, and sends that text to the PostLens server, which forwards it to TypeSafe AI only, the same way the check page does. It never enumerates the feed, opens “see more”, reads messages, touches cookies, or collects a corpus. Its access token lives only in the browser's extension storage and never reaches page code.

The desktop app follows the same one-card rule, with two differences. Hovered post text is scored by both TypeSafe AI and OpenRouter, as described above. And when the founder hovers a person rather than a post, or opens a profile page, the app sends that profile's visible headline and the founder's audience line to TypeSafe AI to read who the person seems to be, plus, only when it is already on screen, the person's own post excerpt or the visible About paragraph (clipped to 900 characters) so the headline can be disambiguated. Since 22 September 2026 the desktop app also sends that profile's public LinkedIn URL to MoltSets, a business-data provider, which returns the person's current title, seniority, company, industry and country; PostLens keeps only those professional fields (the record's email addresses and phone numbers are discarded on the server and never shown, stored or logged), passes them to TypeSafe AI and OpenRouter as context for the read, and caches them in memory for a day. The founder's swipe file does the same lookup for the author of a saved third-party post when that post is opened, using the author link that was visible on the card. Nothing is scraped from LinkedIn or clicked, no other profile section is read, and the person read is never saved.

Hosting and logs

The server runs on Railway (United States) behind TLS; the database is Supabase. Hosting logs hold the structural lines described above and standard request metadata kept by the platform for operations. No draft text or scoring result is ever in a log.

What is never done

No auto-posting, no auto-commenting, no auto-scroll, no background feed reading, no cookie extraction, no scraping of a corpus, no automated engagement, no sale or sharing of data, and no advertising. These are hard invariants in the code and tests, not settings — see what PostLens never does.

Your rights and contact

Because nothing identifies a public visitor, there is usually nothing to look up or delete; if you have used the founder features, or believe PostLens holds something about you, email alex@techtideai.io and it will be answered promptly. If you are in the EU, UK, or a jurisdiction with similar law, you may have rights of access, correction, deletion, and objection — the same address handles them. PostLens is not directed at children under 16.

Changes

This page is the policy; changes are made here, with the effective date updated at the top. The terms describe what you agree to when you use PostLens.