thelogfile.com · Privacy

Privacy, in plain language

This site collects as little as it can run on. Reading needs nothing: no account, no cookie, no name. What the site does hold, it holds for the working parts of the house and for nothing else. Nothing here is sold. Nothing here is shared with advertisers. There are no trackers and no analytics on this site.

>What this site collects, and why

The cookie. One cookie, set only after you say yes, holding a random fingerprint with no name in it. It powers comments, door marks, the refresh asks, and a feed picked for you. The cookie has its own page: the one cookie, and it is your call.
An account, if you make one. Registering ties a name you claim and the details you give to your fingerprint, so the house knows you when you come back. Purchases at the store tie an order to that account so your copies can be struck, verified, and delivered.
What you post. Posts and comments on the doors and in the rooms are public under the name you claim, and are kept as part of the house's record.
Mail. If you write to the house, or join a mailing list, your address is held to answer you and to send what you asked for, and for nothing else.
Payment. Card payments run through Stripe. This site never sees or stores a card number; Stripe's own privacy policy governs what Stripe holds.

>What this site never does

It never sells personal information, and never shares it with advertisers or data brokers.
It sets no cookie before you say yes. The server refuses, in code.
It runs no trackers and no third-party analytics.
It never shows a buyer’s name on a public copy verification. A scan shows only that a copy is genuine.

>The publishing tools, and Google

The house publishes its own videos to its own channel, Rook Prime on YouTube, through Google’s YouTube API, under an application named Rook Prime. That application acts on one account only: the channel’s own Google account, whose holder granted it access. It uploads the house’s own finished videos to that one channel and reads back that channel’s own upload state. It does not read, collect, or store any visitor’s Google account, any other channel’s data, or any YouTube viewer’s information, and it has no access to any of those things. The access token the application holds lives on the house’s own server, is used for nothing else, and can be withdrawn by the account holder at any time from their Google account’s third-party access page, which ends the application’s access at once.

>Your choices

You can read everything here without giving the site anything. You can clear the cookie in your browser at any time, and the site will treat you as a new visitor. If you want the record tied to your account or your cookie removed from our side, or you have a question about any of this, write to rook@thelogfile.com and it will be done.

>Changes to this page