Last updated: April 2025
LinkProof records technical events to power your analytics dashboard: proposal page views, trackable-link views and clicks, internal-calendar booking details (name, email, note, time slot), and proposal responses (email, name, accept or decline, optional message). No sensitive personal data (health, financial, biometric) is collected by the product itself.
"Intent" in LinkProof is approximated from visits and in-product actions — similar to the read-receipt on a sent email. A page view is recorded when a browser loads the proposal or link page; a click is recorded when the visitor follows the redirect. These events are attributed to an approximate country (from the request IP or edge headers) and a browser fingerprint when an IP is not available. No content read out of context is inferred.
All collected data serves a single purpose: showing you (the account holder) statistics about proposals and links you created. We do not sell data to third parties, use it for advertising, or share it with anyone outside your instance.
You can delete proposals and links in your console at any time. Data tied to those items is removed in cascade within the technical limits of your instance. For self-hosted deployments, retention, backups, and deletion schedules are your responsibility.
Public proposal and link pages display a short privacy notice informing visitors that visits and interactions are recorded for the sender. No cookie consent banner is shown by default because the events are server-side and do not use tracking cookies. If your deployment requires a banner under local law, add it at the infrastructure level.
When a visitor accepts, declines, or books a time slot on a proposal, the email and name they provide are visible only to the proposal sender in the Responses and Bookings consoles. This information is not published on any public page.
Console access is password-protected by a server-side credential you set. Webhooks are HMAC-signed so your endpoint can verify authenticity. For self-hosted deployments, network-level security is your responsibility.
We may update this policy as the product evolves. Significant changes will be announced in-product at least 30 days before taking effect when feasible.
Questions about privacy? Reach us through the contact information in your deployment documentation or the console support channel.