Privacy Policy
Effective date: April 30, 2026. Plain language, no surprises.
What this policy covers
This policy applies to the Local Visibility Lab marketing site at localvisibilitylab.io. The platform itself has its own terms and privacy practices specific to account holders, which you accept when you create an account. This document covers what happens when you browse the marketing site and submit the contact form.
Information we collect
When you submit the contact form on the contact page, we collect: your name, your email address, your company name if you provide it, the subject you select, and the message you write. That data is used to respond to your inquiry. Nothing else.
If you browse the site without submitting a form, we do not collect personally identifiable information. The site may use standard browser cookies as part of Clerk's authentication flow for the sign-in and sign-up pages. If you do not create an account, no authentication cookies are set in your browser.
We do not run advertising pixels, behavioral tracking scripts, or third-party analytics that build profiles about individual visitors. Cloudflare, which hosts and serves the site, may log standard server-side request data (IP address, request path, browser string) as part of normal CDN operation. That data is governed by Cloudflare's own privacy policy and is not something we access or use to identify individual visitors.
How we use your information
Contact form submissions go to our email inbox via Resend, the email delivery service we use. We read them and reply. We do not add your email to a marketing list unless you explicitly ask to be included. We do not sell, rent, or trade contact form data to any third party.
If you sign up for an account on the platform, Clerk handles authentication, including storing your credentials securely and managing session cookies. Clerk's privacy policy applies to that data. We access only what Clerk surfaces to us through their API, primarily your user ID and email, for the purpose of managing your account.
Third parties involved
Three external services touch your data in limited, specific ways:
- Resend - email delivery service. Contact form submissions are routed through Resend so we receive them as email. Resend processes message content in transit and does not retain it for advertising purposes.
- Cloudflare Pages - the infrastructure that hosts and delivers this site. Standard CDN-level request logs are retained per Cloudflare's data retention policy.
- Clerk - authentication provider for the platform sign-in and sign-up flows. If you create an account, Clerk stores your authentication credentials and session data. You can review Clerk's privacy policy at clerk.com.
No other third parties receive your contact form data or any personally identifiable information from this site.
Data retention
Contact form submissions arrive as email and are retained as long as we retain business email generally, unless you ask us to delete your information. We do not maintain a separate database of contact form submissions beyond what lives in our email inbox.
Platform account data is retained as long as your account is active. If you delete your account, account data is deleted according to the platform's data retention policy, which you accept at signup.
Your rights
You have the right to request access to personal data we hold about you, ask us to correct inaccurate data, ask us to delete data we hold about you, and ask us to export your data in a portable format. These rights apply whether or not you are in a GDPR-regulated jurisdiction. We apply them generally because they reflect how we believe data should be handled.
To exercise any of these rights, reach out through our contact page. We will respond within 30 days. We may ask you to verify your identity before acting on a request, to make sure we are acting on behalf of the right person.
Security
Contact form data is transmitted over HTTPS. We do not store credit card numbers or payment credentials anywhere on this site. Platform payments are handled by Stripe, which is PCI DSS compliant. We take reasonable technical and organizational measures to protect data against unauthorized access, but no system is completely secure, and we cannot guarantee absolute security.
Changes to this policy
If we change this policy in a material way, we will update the effective date at the top of this page. We will not retroactively weaken protections for data collected under a prior version of this policy without explicit notice.
Contact
Questions about this policy, data access requests, or anything else related to privacy can be sent through our contact page. Choose the "Other" subject and mention "Privacy" in your message; we will route it to the right person.