Legal
Privacy Policy
This policy explains which data Lead Command Center processes, why we process it, and how long we keep it. It covers both the people who use the application (our team) and the leads whose details reach us through connected forms and advertising platforms.
Who we are
Lead Command Center is a private lead management application operated by Digital Web Services Ltd. We use it internally to manage inbound leads, proposals, onboardings and client projects. For questions about this policy or about your data, contact us at digitalwebservicesltd@gmail.com.
Data we collect
Lead data. Name, email address, phone number, company, the message or form answers submitted, and campaign attribution details such as campaign, ad group, ad and keyword. This data is submitted by the lead through a form and delivered to us by the platform hosting that form.
Commercial data. Proposal documents, signature records (name, timestamp, IP address), payment status and invoice references, onboarding answers and uploaded files, and project or task records.
Account data. For team members: email address, role, department membership and sign-in metadata.
Technical data. Raw webhook payloads and delivery logs, kept so we can trace and correct failed or incomplete imports.
Where the data comes from
We receive data through webhooks and connected integrations, including Meta Lead Ads (lead form submissions from Facebook and Instagram), Google Ads and website forms, FunnelDash (appointments and payments), Stripe (payment events), Slack (internal notifications) and Resend (outgoing email delivery).
When you submit a lead form on an advertising platform, that platform passes your submission to us because the advertiser (us or our client) has connected this application to the form. We do not buy lead lists.
Why we process it
To respond to enquiries, plan and hold sales calls, send and sign proposals, collect payments, onboard clients, deliver the services agreed, report on advertising performance, and keep the records required for accounting and dispute handling.
The legal bases we rely on are: performing a contract or preparing one at your request, our legitimate interest in running and securing our business, consent where you gave it on the form you submitted, and legal obligations such as tax record keeping.
Sharing
We do not sell personal data and we do not use lead data for advertising to third parties. Data is shared only with the processors that make the application work: Supabase (database, authentication and file storage), Cloudflare and Lovable (hosting and delivery), Resend (transactional email), Stripe (payments), Slack (internal notifications) and Meta, Google or FunnelDash for the integrations you connected. Each processor receives only what its function requires.
Storage, security and retention
Data is stored in managed cloud infrastructure with encryption in transit and at rest. Access is restricted per user through row level security, role checks and department scoping, and every table containing personal data is protected by those rules. Access tokens for connected platforms are stored server side only and are never exposed to the browser.
We keep lead and client records for as long as the relationship is active and afterwards only where a legal or accounting obligation applies. Raw webhook payloads and delivery logs are operational troubleshooting data and are cleared once they are no longer needed.
Your rights
You can ask us for a copy of your data, correct it, restrict or object to its processing, or have it deleted. Where processing is based on consent, you can withdraw that consent at any time. Email digitalwebservicesltd@gmail.com and we will respond within 30 days. Deletion requests also remove the related webhook payloads and signature records, except where we must retain an invoice or a signed agreement by law.
If you believe we handled your data incorrectly, you can also lodge a complaint with your local data protection authority.
Changes
We update this policy when the application or its integrations change in a way that affects your data. The date below shows the current version.
Last updated: 24 August 2026