bedrocktapwaitlist

Privacy

This site measures demand while BedrockTap is built, so it would be absurd to be vague about what it measures. Everything it records is listed below.

What is recorded on every request

  • Timestamp, HTTP method and path.
  • The User-Agent header as sent, and the headers used to classify the request as agent or browser.
  • A salted SHA-256 hash of your IP address combined with your user agent. This is used to count distinct callers. The IP address itself is not stored, and the hash cannot be reversed to recover it.
  • Country, when the hosting platform supplies it.
  • The srcquery parameter, to learn which of this site’s own machine-readable surfaces you arrived from.
  • The inbound channel, to learn who sent the traffic: the via, ref or utm_source query parameter when a link carries one, and the Referer header reduced to its host. Other utm_* parameters are not read. Arrivals with no tag are recorded as exactly that.

What is recorded when you call a tool

  • The tool name and the arguments you passed, truncated at 8 KB.
  • An automated score of how realistic those arguments look.

Do not put secrets, credentials or personal data belonging to someone else in a tool argument. Nothing here needs them, and everything you send is written to a log.

What is recorded when you volunteer it

  • The waitlist form: your email address, your description of the use case, and your stack.
  • The register_interest tool: whatever you pass, including a callback URL or contact address if you choose to supply one.

What it is used for

Deciding which BedrockTap capability to build first, and in what order the rest follow. Email addresses are used to notify you when it ships, and for nothing else. Nothing is sold, and nothing is shared with a third party for advertising.

Where it is stored

In the hosting platform’s request logs, in a hosted Redis instance, and — for higher-signal events — in a private Discord channel. If website analytics are enabled, an analytics provider also receives standard page-view data from browsers; agents that do not execute JavaScript are invisible to it, which is precisely why the server-side record above exists.

Removal

Email contact@bedrocktap.com and it will be deleted. If you are an agent, you can say so in a register_interest call and a human will read it.

Cookies

This site sets no cookies of its own. If analytics are enabled, that provider may set its own.