Template activity and privacy

Creators can see aggregate views, source-download responses, run counts and verified purchase membership counts for their work. This dashboard does not reveal your prompt inputs, files, outputs or buyer identity.

Page views and entry channels

A visible template page can send its template ID and a coarse entry label, such as search engine, creator page or shared link, to SecondBrain. Classification happens in your browser; the activity request does not include the referrer URL, search terms or other query values. Shared links and embedded-card buttons include the same public channel tag for everyone, without a unique identifier or affiliate code. No analytics cookie, visitor ID, IP address or referrer is stored in the daily activity bucket. Your tab can retain a timestamp per template in session storage to avoid counting another view within 30 minutes. This is not a visitor identifier and is not sent to the server. Browser Do Not Track and Global Privacy Control signals suppress optional view reporting and channel labels.

Source downloads

An authorized source response can increment a daily count with an optional channel label. A count means the server prepared the download response; it does not prove the file was saved. Do Not Track and Global Privacy Control suppress this optional recording through request headers or the hydrated page controls. Before JavaScript determines your privacy choice, source links opt out of recording. Download access does not depend on analytics being available.

Runs and purchases

Run counts and outcomes come from the records needed to operate templates. Inputs and results remain private and are scheduled for erasure after 24 hours. When optional activity recording is allowed, the run also captures its source price category and validated completion time. Later template edits and private-result erasure do not change those values. Do Not Track and Global Privacy Control suppress these optional values together with the channel label. Commerce records are used to verify access. The creator dashboard returns aggregate counts, not your payment identifiers or account details.

The verified free-to-paid cohort includes accounts with a successful free run requested and completed in the selected period, excluding creator self-tests, operators, known earlier payments and accounts whose observed commerce history has not been verified. Verified history with no paid payment is distinct from unknown history. A paid conversion requires a currently verified purchase whose earliest provider payment time follows that free result within the same period. Each account counts at most once; the rate divides paid conversions by eligible free-run accounts, and is unavailable when that denominator is zero. Unknown payment history is disclosed separately. Payment dates come from authoritative provider history, never membership-record creation or webhook arrival. They remain private commerce verification metadata, separate from optional run activity. This observed cohort does not prove free use caused a purchase or cover unobserved external sales. Missing optional metadata, expiry, refunds and stale verification can affect the result. Historical price categories and completion times are not guessed from current templates.

Optional feedback and reuse

After a successful run, you can mark its result helpful or not helpful and change your response while the result remains available. This response is optional. It is kept privately with the run record within a rolling 90-calendar-day reporting window and removed by scheduled maintenance after that window. Creators receive aggregate response counts without your account, inputs or output.

Save counts and repeat usage use the run and saved-library records already needed for your account. A later-day saved-template return means a successful run on a UTC day after the save, while that save remains in your library. Reports do not add a visitor identifier or expose individual account activity. Removing a save can reduce these counts.

Retention and limits

Daily view and download buckets and optional run activity metadata are retained within a rolling 90-calendar-day window by scheduled maintenance. Operational run and budget records remain after their optional labels, price category and completion timestamp are erased. Counts are approximate and can be affected by blocked scripts, repeated requests and service interruptions. Channel labels can be spoofed; they do not track journeys across pages, establish that a view caused a run or purchase, or determine affiliate credit. These counts are not unique visitors or an audited sales ledger.