Skip to content

Privacy

Exactly what linkweave stores

linkweave counts clicks, not people. This page lists everything it keeps about the visitors of a creator page and about the owner who runs it.

About visitors

linkweave stores one table of visitor data: hourly click counts.

Stored

  • The link that was clicked
  • The UTC hour
  • A referrer category: direct, social, search or other
  • A count

Never stored

  • IP address
  • User agent
  • Referrer URL
  • Visitor id
  • Cookies

No cookies. The public page, the feed and the counted redirect /r set no cookies. /r answers with Cache-Control: no-store.

Rate limits without a record. The rate limiter keys its counters by an HMAC of the IP address under a random per-process salt. The key is held in memory only and is never persisted.

Retention. Click rows are kept 400 days and are deleted at once when the account is purged.

About owners

Your identity is the pair (issuer, subject) from sign-in, never your email address.

linkweave also stores your profile content, your links, your webhook URL and a sealed webhook secret. The session cookie on the app host is an encrypted token that holds the refresh token.

Deleting your account removes the profile, links, snapshots, clicks and webhook in one transaction.

Third parties

Cloudflare Web Analytics is off unless the operator sets CF_WEB_ANALYTICS_TOKEN. When it is on, public creator pages load Cloudflare’s cookieless beacon, so visitors’ browsers send page-view data (URL, referrer, user agent, performance timings) directly to Cloudflare. linkweave never receives or stores it.

Cloudflare as the edge sees all traffic, as any CDN does.

These marketing pages load no analytics and no third-party scripts.

Read the privacy reference in the docs