Data Residency & GDPR Compliance

Flint is designed so your visitor data stays in your stack. This page covers where Flint-hosted pages are served from, what data Flint processes, and how to configure your setup for GDPR and other privacy regulations.

Flint pages are hosted on Vercel's global edge network. Assets are served from the edge location closest to your visitor, with origin infrastructure in the United States.

Flint stores your page content — the HTML, CSS, images, and assets that make up your landing pages. This is your marketing content, not visitor data.

Flint does not store visitor data by default. Visitor interactions (form submissions, clicks, conversions) are handled by the third-party tools you integrate: your analytics platform, your CRM, your form handler. Those tools' own data residency policies apply.

If your compliance requirements call for it, Flint can disable all Flint-side data collection so no visitor-level data is processed or stored by Flint's infrastructure. Contact your account manager or reach out to support@tryflint.com.

• •Use reverse proxy (subfolder) hosting. Pages appear under your domain, keeping all cookies first-party and under your existing consent framework. See Hosting Options.
• •Embed your own CMP. See Cookie Consent & CMP Integration for setup instructions.
• •Keep analytics in your stack. GTM, GA4, and any tracking you add via Custom Code runs through your own accounts. Flint does not intermediate or duplicate this data.
• •DPA available. If your legal team requires a Data Processing Agreement, contact privacy@tryflint.com.

If you operate in healthcare, finance, or another regulated sector and need specifics on data flows, subprocessors, or infrastructure certifications, contact support@tryflint.com. We can walk your compliance team through the details.