A deliberately small visitor-data surface.

Pilot-interest information

When intake is available, the form sends your email address, a general workflow description, optional Windows details, and separate consent choices to this website’s private intake database. The site owner—the creator behind BpManiac13—uses it to review fit and potentially reply. It does not promise a reply or product access. No logs, source files, attachments, account, payment, or health information are requested.

Optional Trace development and pilot updates have a separate, unchecked checkbox. No marketing email is sent automatically by this form. Consent to review your interest does not subscribe you to updates.

Control and retention

The success screen gives you a private management link. Save it: it is not emailed automatically. Anyone with the link can withdraw optional update consent or delete that submission. The raw management secret is not stored in the database. Treat the link as private.

A submission expires from active intake after 90 days. Expired records are removed when intake is next accessed or scheduled cleanup runs. Cleanup may therefore occur after the expiry date during inactivity. Deletion removes the personal information and consent record. A hash-only deletion marker is kept for up to 90 days to prevent an interrupted request from recreating it; the hosting provider’s recovery copies follow its own retention. The owner must exclude expired and withdrawn entries from follow-up lists. If you lose the link, the active record still expires.

Abuse prevention

The server validates fields, rejects cross-site submissions, limits request size, and limits submission attempts. A daily salted address fingerprint and its random salt expire after two days and are removed at cleanup. The application does not store the raw address in its intake tables. Hosting security logs are separate.

One device-local preference

If you use Calm mode, the browser stores one on/off preference named tfs-calm-mode. The site does not transmit that value or use it for profiling.

Small, aggregate website counts

To understand whether the website helps people reach the pilot, we count Trace page views, available pilot-form openings, and newly saved submissions. The measurement table contains only the UTC date, one of those three event names, and a daily total. It contains no email, form text, private management link, IP address, browser identifier, referrer, or full URL. No analytics cookie or visitor profile is created.

These are approximate activity totals, not unique people or a tracked journey. Reloads can add views, blocked requests can be missed, and retries of the same saved submission do not add another success. The site respects browser Do Not Track and Global Privacy Control signals for these counts. Clearly synthetic submissions using an .invalid email address are excluded from success totals.

Only the owner can read the totals through the private database. Daily totals are kept for 90 calendar days and removed at the next scheduled cleanup. They cannot be linked back to an individual submission, so withdrawing or deleting your interest does not change a past aggregate total.

Security-reporting email

If you email a security report, your email provider and Google’s Gmail service process the sender, recipient, routing metadata, subject, message, and any attachments under their own terms. The message is not stored in the website’s pilot-interest database or aggregate counts. Email is not presented as an end-to-end encrypted reporting channel.

Send the least sensitive information needed. Do not include credentials, access tokens, private management links, personal records, client data, or harmful payloads. If sensitive evidence is necessary, send a general summary first and ask for transfer instructions.

Hosting data

The hosting service may process ordinary request, session, reliability, and security metadata needed to deliver and protect the site. This site does not add a third-party analytics SDK or advertising tracker.

Before collection changes

Any change to accounts, analytics, payment, support, uploads, intake fields, or data purposes requires a reviewed purpose, data flow, retention rule, operator identity, visitor notice, and appropriate consent before it is enabled.