Privacy & Cookies Policy

1. Our role

For business account information, website analytics, website security information, billing administration and service communications, LEADRESTORE LTD acts as a controller. When a business uploads, pastes or manually enters customer or lead information for analysis, that business normally determines why the information is being used and LeadRestore processes it on that business’s instructions as a processor.

2. Information we handle

• Business account information such as business name, email address, authentication/session information and account/subscription status.
• Recovery history saved by signed-in users, including revealed opportunities, follow-up status, reminder dates and Actual Won Revenue entered by the user.
• Lead fields needed to run an audit or Business scan, such as customer name, status, value, days since contact and short notes.
• Billing identifiers and subscription status needed to connect a LeadRestore account with Stripe. LeadRestore does not receive or store full payment-card numbers.
• Security and anti-abuse information, including hashed identifiers used to enforce usage limits.
• Technical logs needed to operate, secure and troubleshoot the service.
• Business correspondence sent to or from our LeadRestore email addresses.
• For approved Partners: application and account details, referral clicks, pseudonymous referred-customer references, commission records, Partner Terms acceptance and payout administration details. Partners do not receive customer contact details or uploaded LeadRestore workspace data.
• If you accept optional analytics: a random browser identifier, session identifier, page and feature events, referring domain, device/browser information made available by the analytics service, and campaign attribution such as UTM source, medium, campaign and content.

LeadRestore is not designed for passwords, payment-card details inside lead uploads, bank-account details, government identifiers, medical information or other special-category/sensitive information. Businesses should remove those fields before uploading data.

3. How and why we use information

We use account information to provide and secure LeadRestore, maintain signed-in recovery history, administer subscriptions, send authentication and service emails, respond to account actions and prevent abuse. Where we act as a processor, we use uploaded or entered lead information to provide the requested audit and related recovery features.

If you consent to optional website analytics, we use LeadRestore acquisition analytics, Google Analytics 4 and the Meta Pixel to understand visits and feature usage, measure which campaigns and channels bring visitors to LeadRestore, improve the website and customer journey, and understand where people start or complete key product actions. We do not intentionally put uploaded lead names, email addresses, lead notes or uploaded file contents into website analytics events.

4. Lawful bases

Our controller-side processing may rely on taking steps to provide the service at your request, performing our agreement with you, complying with legal obligations, and our legitimate interests in operating a reliable service, preventing fraud or abuse and protecting LeadRestore and its users. Optional website analytics are only started after you choose Accept analytics. A business using LeadRestore remains responsible for having its own lawful basis to use and follow up customer information it provides.

5. Cookies, local storage and analytics consent

An approved Partner referral route sets a secure first-party referral token for up to 90 days so LeadRestore can attribute a later subscription and administer the Partner Programme.

LeadRestore uses browser storage and similar technologies. Storage that is strictly necessary for security, authentication, account, workspace or other functionality requested by you may operate without optional analytics consent where permitted by law.

When analytics are accepted, LeadRestore may store a random browser token, session information, campaign attribution and event-deduplication information in your browser. Google Analytics may also use analytics cookies or similar identifiers to measure visits and engagement. The Meta Pixel may use cookies or similar identifiers to measure visits and actions such as starting or completing an audit, starting checkout and completing a subscription, so LeadRestore can understand and improve Meta advertising performance. LeadRestore does not intentionally send uploaded lead names, email addresses, notes or file contents to Meta. Advertising storage and ad-personalisation signals are not enabled by LeadRestore’s GA4 implementation.

Your consent choice is stored on your device so we can remember it. You can change your choice at any time using the Privacy & cookies control on the website. If you reject analytics, LeadRestore removes its acquisition analytics identifiers from that browser, stops sending new LeadRestore acquisition analytics events, updates Google Analytics consent to denied and revokes Meta Pixel consent for subsequent optional analytics processing on that device.

6. AI processing

LeadRestore may send the mapped lead fields needed for an audit to the OpenAI API to assess whether a record looks suitable for follow-up and to draft a suggested message. The original CSV or Excel file itself is not sent to OpenAI. LeadRestore requires human review of AI suggestions and does not use the service to make solely automated decisions that produce legal or similarly significant effects.

Ask LeadRestore may send a support question, recent support conversation and minimum safe context needed to answer it to the OpenAI API. Users should not paste customer or lead personal data, passwords, payment details or other sensitive information into support chat.

7. File handling and retention

• Guest CSV files are read for the audit and are not deliberately stored by LeadRestore as account history.
• Excel files are parsed transiently by LeadRestore server infrastructure and are not written to the account database merely to parse them.
• Signed-in recovery history can be stored until the account owner deletes the account or the data is otherwise removed in line with the service.
• Account, agreement and billing-status information is retained while needed to administer or evidence the service relationship, subject to legal and security requirements.
• Operational, security and analytics records are retained only for as long as reasonably necessary for their purpose and are reviewed periodically.

8. Service providers

LeadRestore currently relies on Vercel for hosting/serverless processing, Supabase for authentication and recovery data, OpenAI for AI inference, Resend for transactional/authentication email delivery, Google Workspace for LeadRestore business email and communications, Google Analytics and Meta Platforms for optional website and advertising analytics, and Stripe for subscription checkout and billing management. The current provider list is available on the Subprocessors page.

9. International processing

Some service providers may process information outside the UK. Where UK data-protection law treats that as a restricted transfer, LeadRestore relies on the transfer mechanism and contractual safeguards applicable to the relevant provider relationship.

10. Your rights

Depending on the circumstances, individuals may have rights of access, rectification, erasure, restriction, portability and objection. Where processing is based on consent, you can withdraw that consent. Withdrawing consent does not affect processing that lawfully took place before withdrawal. If information was uploaded by a LeadRestore business customer, requests should normally be made to that business first because it is the controller.

11. Complaints

You can raise a data-protection concern with us at privacy@leadrestore.co.uk. You also have the right to complain to the UK Information Commissioner’s Office. See ico.org.uk/make-a-complaint.

12. Changes

We will review this notice as LeadRestore develops and before introducing materially new uses of personal information.