Privacy

The short version

This site stores what it needs to run an account and a file exchange, and nothing else. There is no advertising, no third-party analytics and no tracking across other sites.

If you only read

Browsing and downloading need no account. A session cookie is set so that forms work and so we can tell an abusive request rate from a normal one. Web server logs record request details including IP address in the ordinary way, and are kept for a short period for security and debugging.

If you download the app

A counter goes up. That is the whole of it: one number per file per day, so we can see which builds people actually use. Nothing about who downloaded is stored alongside it — no address, no browser, no identifier — so the number cannot be turned back into a list of people, by us or by anybody who obtained it.

The same is true of the download count shown on a button set: it counts downloads, not downloaders.

If you have an account

We store your name, email address, hashed password, and anything you choose to put in your profile (a short bio, links). Passwords are hashed with bcrypt; nobody can read them back, including us.

Your display name appears publicly next to any button set you publish. Your email address does not.

If you publish a button set

The file you upload is stored exactly as you sent it, along with the parsed contents, its SHA-256 checksum, and your account as the owner. All of that is public — that is the point of publishing. Check the file before uploading: hostnames or customer names typed into a command are published along with everything else.

If you subscribe to the newsletter

We store the address, when you asked, which page you asked from, your IP address and browser at the time, and when you confirmed. That record exists to prove consent if it is ever questioned.

Nothing is sent until you click the confirmation link. Every email has a one-click unsubscribe link that needs no login.

The list is currently held on our own server and is not shared with a mailing list provider.

If you report a bundle

Your account, the reason and any detail you write are stored and visible to moderators. They are not shown to the person who published the bundle.

Cookies

• Session cookie — keeps you signed in and makes CSRF protection work. Necessary; the site does not function without it.
• Theme preference — stored in your browser, not sent to the server.

There are no analytics or advertising cookies.

How long things are kept

• Account and published bundles: until you delete them.
• Unconfirmed newsletter signups: expire automatically.
• Unpublished uploads waiting for confirmation: two hours, then deleted automatically.
• Download counts: kept indefinitely. They are numbers, and they are not about anybody.
• Moderation records: kept, because they are the record of why something was removed.

Your rights

Ask for a copy of what we hold, ask for corrections, or ask for deletion: hello@smartcomrevisited.com. Deleting an account removes the account and its bundles. Moderation records referring to a deleted account are kept without the personal details.

The desktop application

SmartCom Revisited runs on your machine and does not report to this site. Connection details and session logs stay local. Credentials are held in the operating system's vault.

The AI assistant is the one part that can send data off your machine, and only if you switch it on: with Claude or OpenAI selected, the session transcript you share with it goes to that provider under their terms. With Ollama selected it stays on your machine. It is read-only either way — it proposes commands and never runs them.

Contact

hello@smartcomrevisited.com, or security@smartcomrevisited.com for anything security related.