Privacy Policy
Last updated: 27 March 2026
This Privacy Policy describes how Dyvr Limited (trading as Flint, "we", "us") processes personal data when you use the Flint platform—the web application where you sign in, build tools, manage leads, view analytics, and handle billing. It does not replace the privacy information your own customers see when they use a published Flint tool; that experience is covered by a separate in-tool Privacy Notice (and, where you configure it, your own policy link).
1. Who we are
Dyvr Limited is the data controller for personal data we process about Flint account holders and their authorised users when using the platform.
- Email: hello@useflint.co
- Registered address: 3 Swithland Lane, Rothley, Leicestershire, LE7 7SG, United Kingdom
- Company number: 15369152
2. Scope
This policy applies when you:
- Create or manage a Flint account, sign in, or use password reset;
- Use the builder, dashboard, leads, analytics, billing, settings, or integrations;
- Contact us for support or receive operational emails about your account.
If you are an end user of a tool someone built with Flint, our processing is primarily on behalf of that customer as data controller; see the Privacy Notice shown in that tool and our Platform Use Agreement for how those roles work.
3. Data we collect and why
3.1 Account and authentication
We collect your name, email, and credentials via our authentication provider so you can sign in securely, recover your account, and so we can identify your workspace, tools, and subscription.
3.2 What you create in Flint
We store tool configurations (including themes, questions, logic, knowledge-base content you upload, publish settings, and privacy profile fields you enter for your tools), leads and sessions associated with your tools, and integration settings (for example HubSpot or Slack connections you enable). This is necessary to provide the service you asked for and to display analytics and leads in your dashboard.
3.3 Analytics inside the Flint app
We process usage and funnel data derived from end-user sessions of your tools (for example completions, steps, and traffic sources you see in the analytics area). This helps you understand performance of tools you publish. It is tied to your account as controller of those tools.
3.4 Billing
If you subscribe to a paid plan, our payment provider processes payment details and we retain subscription status, customer identifiers, and related billing data needed for invoices, upgrades, and compliance with tax and contract obligations.
3.5 AI features in the builder
When you use AI-assisted features in the admin experience (generation, fill, chat, embeddings for knowledge bases), we send the relevant prompts and content to our AI provider to return results to you. Do not paste unnecessary personal data into prompts unless you accept it will be processed that way.
3.6 Communications
We send transactional emails (for example sign-in links from our auth provider, new-lead notifications, session limit notices, billing receipts, or results notifications where the product is configured to send them). We do not use this policy to cover optional marketing emails unless we specifically ask for consent and describe them separately.
3.7 Technical and security
We keep server and application logs, IP addresses, and device/browser signals as needed for security, debugging, abuse prevention, and reliable operation of the platform.
4. Legal bases (UK/EEA-style summary)
Where UK GDPR / EU GDPR applies, we rely on contract (providing Flint), legitimate interests (securing and improving the platform, analytics for your own tools, relevant account messaging), and where required consent (for example marketing). We process payment data as needed for contract and legal obligations.
5. Sharing and international transfers
We use trusted service providers (sub-processors) who may access data only to perform services for us. They may be located outside the UK/EEA where we use appropriate safeguards (such as standard contractual clauses) where required.
6. Sub-processors (platform)
Core providers we use to run Flint include, for example:
- Supabase — authentication, database, file storage, and related infrastructure
- Vercel — hosting and runtime for the application
- OpenAI — AI functionality in the product (generation, embeddings)
- Resend — transactional email delivery
- Stripe — subscription and payment processing
When you connect optional integrations (for example Meta Pixel on a published tool), those vendors may process data under your configuration and agreements in addition to our core stack.
7. Retention
We keep account and tool data while your account is active and for a reasonable period afterwards for backup, dispute resolution, and legal requirements. You can delete leads and other content in the dashboard; account deletion is subject to in-product controls. Some billing and legal records may be kept longer where the law requires.
8. Your rights
Depending on your location, you may have rights to access, correct, delete, restrict, or object to certain processing, and to port data or complain to a supervisory authority. Contact us at hello@useflint.co.
9. Security
We implement appropriate technical and organisational measures designed to protect personal data. No online service is completely risk-free; please use a strong password and protect access to your account.
10. Children
Flint is a business tool and not directed at children.
11. Changes
We may update this policy from time to time. We will publish the new version here and, where appropriate, notify you by email or in-product message.