Linnik

Linnik

Privacy policy

Effective 1 October 2026. This page says what Linnik stores and why.

Linnik is operated by Ben Clatterbuck of ROM Solutions, Washington State. The app is at https://linnik.app. Questions go to romsolutionsllc@gmail.com.

What you give us

An account needs an email. If you make a password, we store a hash of it, not the password. If you use Sign in with Google, Google sends us your email, your name, and a Google account id. We use those to open the same account next time.

A pack needs the meeting dump you paste, plus the company, date, type, and attendees you type. We keep that text, the note built from it, and the PDF. Profile can also hold a display name, default company, default attendees, meeting types, and SMTP settings if you save them. An SMTP password is stored so the app can send a pack you ask it to send.

How a pack is built

The dump is sent to an AI service to pull out decisions and named work. That text is used to build the pack. It is not sold, and it is not used to train a public model by us.

Cookies

A login sets a cookie named closeout_session so you stay signed in. Sign in with Google sets a short-lived cookie named google_oauth_state for that sign-in only. Both are needed for the app to work.

Who else sees it

The app runs on a server we control. Google sees the sign-in if you use Sign in with Google. An email you send from Profile goes through the SMTP server you entered. We do not sell accounts or meeting text.

How long it stays

Packs stay until you delete them. You can delete a pack in the app. To close an account, email romsolutionsllc@gmail.com.

Changes

If this page changes, the date at the top changes. The new page replaces the old one.