Last updated: 5 November 2026
This notice explains how Kinder Naturals handles personal information through KN Wholesale CRM, also identified as KN Wholesale CRM Mail in Google authorisation. The CRM is a private business tool for wholesale prospect research, approved email outreach and relationship management. It is operated by Kinder Naturals. For privacy questions or requests, email linda@kindernaturals.co.uk.
For information about browsing or purchasing from our online shop, see our website privacy policy. The CRM is covered by the separate CRM Terms of Service.
Information we handle
We record relevant business names, public business contact details, professional roles, locations, websites, source links and buying signals. Where a relevant sourcing post is public, a record may include the poster’s profile name, profile link, group name and the business context of that post. Information may also be supplied directly by a contact or imported by an authorised team member. Public availability does not remove an individual’s privacy rights.
Relationship records may include message drafts, sent email bodies, recipients, subjects, thread identifiers, dates, reply excerpts, contact preferences, activity notes, samples, follow-up tasks, ownership and order or opportunity information. We use only information relevant to the business relationship and do not seek private social profiles, unrelated personal information or sensitive personal data.
Google account connection and Gmail
Only an authorised Kinder Naturals account owner connects the business Gmail account through Google’s permission screen. The integration requests permission to send email and read Gmail information. These permissions are broader than an individual conversation; the operating workflow checks the connected account and its permitted sender, then reads tracked wholesale email threads to identify replies and prepare the next action.
The connection uses Google authorisation tokens rather than asking for or storing your Google password. Persistent access credentials are encrypted before being stored on the server. Tokens and email records are not placed in the public source-code repository.
We use Gmail information to display and send messages approved by the authorised user, record outreach, identify replies, stop unanswered follow-ups when a reply arrives and support response tasks. Sending a message requires a specific approval. Reply suggestions are editable starter templates; this mail integration does not send Gmail content to an AI model or use it for model training.
Google data and Limited Use
We comply with the Google API Services User Data Policy, including its Limited Use requirements, when using and transferring information received through Google APIs. Google-derived information is used to provide the disclosed email and relationship-management features. We do not sell it, use it for advertising or credit decisions, or use it to train general-purpose AI models. Access by people is restricted to authorised business use and other access permitted by that policy.
Telegram and other providers
A private, designated Telegram group acts as a review inbox. It may receive business contact details, lead cards, email drafts, recipient addresses, subjects, reply excerpts, task information and action confirmations. Group members who can view those messages can see that information. Sending and record-changing actions are limited to authorised accounts; group membership alone does not grant sending authority.
We use Google/Gmail for email, Supabase for the database and server functions, Telegram for the review group, and GitHub Pages for the CRM interface and public source code. The public interface and code do not give public access to CRM records. Public prospect research may be assisted by AI tools, separately from the Gmail integration. Relevant provider notices are available from Google, Supabase, Telegram and GitHub.
Purposes and legal bases
We use relevant business-contact information for our legitimate interests in identifying suitable wholesale opportunities, managing enquiries and conducting proportionate business communications, taking account of the contact’s interests and expectations. We may also process information to take requested steps towards a contract, perform a contract, meet legal obligations or act on consent where it is required. Google account permission authorises the mailbox connection; it does not constitute a prospect’s consent to marketing.
Storage, access and retention
CRM access is restricted by account and workspace permissions. The primary CRM database is hosted in the EU. Connected providers and their infrastructure or support operations may process information in other countries, including the United States. Applicable international-transfer requirements must be addressed for the services used; contact us for information about the arrangements relevant to your data.
We retain information while it is needed for an active enquiry, business relationship, follow-up, transaction, security purpose or legal obligation. We assess ongoing need when a relationship ends or a record becomes inactive, rather than promising one fixed period for all records. A minimal suppression record may be retained to respect a request not to be contacted. Removing information from the CRM does not automatically remove copies from Gmail, Telegram, provider logs or backups; those copies must be considered separately.
Your choices and rights
You can ask us to stop marketing, correct information, explain our use of your information or consider a request for access, deletion, restriction, objection or portability, where applicable. Send requests to linda@kindernaturals.co.uk. We may need to verify identity and consider any lawful reason to retain particular records. Requests are handled by the business rather than through an automatic self-service deletion button. You may also complain to the UK Information Commissioner’s Office.
The connected account owner can revoke Google access through Google Account connections and ask us to remove stored credentials. Revocation stops further authorised API access but does not itself delete existing CRM, email or Telegram records.
Changes to this notice
We will update this page when the CRM’s data handling changes. The date above identifies the current version. Material changes to Google-data use will require appropriate notice and any further permission required before that use begins.