Privacy Policy

1. Information We Collect

When you submit a message through our contact form, we collect your name, email address, and the contents of your message. Readers of privately shared document pages may also have engagement information collected as described in Section 5.

2. How We Use Your Information

We use contact-form information to respond to your inquiry and communicate with you about potential partnerships or investments. We use private document engagement information to understand document access and reading progress, including repeat visits. We do not sell, trade, or rent your personal information to third parties.

3. Form Processing

Submissions from our contact form, the stakeholder portal access-request form (name, email address and role), and the newsletter signup (email address) are processed through Formspree, a third-party form processing service acting as our data processor. Please review Formspree’s Privacy Policy for details on how they handle form data.

4. Analytics

After you allow analytics, our server sends anonymous public page counts to PostHog. We send only a known public page address and a random identifier limited to your browser tab. We do not send form contents, contact details, query strings, referrers, private document addresses or account identifiers to PostHog. There is no PostHog browser script or screen recording. Essential only, Do Not Track and Global Privacy Control keep this measurement off.

We use Vercel Web Analytics on the public website. It reports aggregated page-view data and may include page URLs, referrers, approximate location (country, region and city), browser, operating system and device type. Vercel uses a daily hash derived from the incoming request for visitor statistics rather than a cross-site tracking cookie. Private document URLs are excluded before analytics events are sent. See Vercel’s Web Analytics privacy details.

Public analytics runs only after you choose Allow analytics. Essential only, Do Not Track and Global Privacy Control keep it off. You can reopen Analytics choices using the link in the footer of a public page. Counts can include a fixed LinkedIn placement code, public page visits, calls to action and form acceptance receipts. A receipt means the delivery provider accepted a submission; it is not a qualified lead or a completed investment. We do not record sessions or join these counts to contact details. The browser stores your choice and, after acceptance, a campaign code for the current tab. It does not create a campaign visitor identifier.

5. Private Document Engagement

Some privately shared document pages send engagement events to our server. These events may include the document link token and page slug; open, heartbeat and close events; time on page; maximum scroll depth; the furthest section reached and time spent by section; the page referrer; the browser user-agent; and approximate country, region and city derived from hosting request headers. The page may also create a random browser identifier in localStorage to distinguish a return visit in the same browser from a forwarded link opened elsewhere. This identifier is not a name and is not stored in a tracking cookie. The event table does not store a raw IP address. The beacon does not run when the browser signals Do Not Track or Global Privacy Control. Event data is stored in our private document database when that database is configured. The application does not currently configure an automatic deletion schedule for these event records. You may contact us to request access to or deletion of information associated with a private document link.

6. Cookies

This website does not use cookies for tracking purposes. Essential cookies may be set by our hosting provider (Vercel) for security and performance purposes.

7. Data Security

We implement reasonable security measures to protect your personal information. However, no method of transmission over the Internet is 100% secure, and we cannot guarantee absolute security.

8. Your Rights

You may request access to, correction of, or deletion of your personal information at any time by contacting us at daniel@gildedge.com.

9. Changes to This Policy

We may update this Privacy Policy from time to time. Changes will be posted on this page with an updated revision date.

10. Contact

If you have questions about this Privacy Policy, contact us at daniel@gildedge.com.