Privacy Notice
Approved final version: 9 November 2026
Effective date: 20 November 2026
This notice has been approved for publication before launch. It applies from the effective date above.
This notice explains how My Pocket Marketer Ltd handles personal data through the MyPocketMarketer website and application, including the free marketing snapshot, paid Marketing Intelligence Suite, customer comparison, Ask MPM, Create and file-library features (together, the Service).
Some features may not yet be available. Where a feature is switched off, we do not carry out the processing described for that feature until it is enabled.
1. Who we are and our data-protection roles
My Pocket Marketer Ltd is registered in England and Wales under company number 17312916, with its registered office at 2 Claridge Court, Lower Kings Road, Berkhamsted, England, HP4 2AF (we, us or our).
We are a controller when we decide why and how to use personal data, for example to administer accounts, take payment, keep the Service secure, communicate with users and meet our own legal obligations.
We are a processor for a business customer where that customer submits personal data in a customer list, question, instruction, document or image for us to process on its behalf. That customer is normally the controller and is responsible for its own privacy notice, lawful basis and instructions. Our Data Processing Terms are in Schedule 1 to the Terms of Use.
For privacy questions or to exercise rights concerning data for which we are controller, contact privacy@mypocketmarketer.com.
2. Who the Service is for
The Service is for adults acting for business purposes, including property professionals. It is not intended for children or for personal or household use. Users must be at least 18. The Terms prohibit users from putting children's personal data into Customer Content.
3. Personal data we handle
3.1 Personal data for which we are controller
| Category | Examples | How we obtain it |
|---|---|---|
| Identity and contact data | Name, business email address and display name | From you when you request a snapshot, create an account or contact us |
| Business profile data | Business name, business type, business context and optional website or social-media URLs | From you |
| Report-selection data | The geographic area selected and report preferences | From you |
| Account and security data | Email address, password hash, authentication data and account status | From you and generated by the Service. The password is hashed before storage and is not stored in readable form |
| Subscription and transaction data | Stripe customer, subscription and price reference IDs, selected package and subscription option, payment status, transaction records, billing name and address, and VAT invoices | From you and Stripe. We do not receive or store the full card number |
| Service output and account-history data | Free snapshots, paid reports, source references, scores, recommendations, plan and task records, feature-use records and previous versions | Generated by the Service from user choices and licensed or aggregate data. To the extent an output contains personal data submitted for a business customer's purposes, we handle that part as processor rather than for our own purposes |
| Technical and usage data | IP address, request time, browser/device information, feature usage, security signals and error logs | Automatically from the device and from hosting, security and error-monitoring providers. To limit repeated registration, sign-in and password-reset attempts, we keep the IP address, and for sign-in the email address, in a security counter for up to two days |
| Communications data | Support, cancellation, privacy and other messages, plus our responses | From you and generated by us |
| Marketing preference data | Consent, opt-out and suppression records | From you and generated by us when we record or update the preference |
3.2 Personal data we process for a business customer
Customer Content means customer lists, questions, instructions, documents, images and other material submitted to the Service. It may contain personal data about the submitting business's customers, prospects, staff, contacts, testimonial providers or people shown in photographs.
For the customer-list feature, the uploaded file is read once in memory and is not stored. The customer chooses the columns to use. We retain only the postcode and selected address fields needed for matching, for up to 30 days. A customer reference may be used temporarily to identify duplicates but is not saved. Names, email addresses, telephone numbers and ignored columns are not retained.
Other Customer Content depends on what the business chooses to submit. It may include names, contact details, address or location data, customer or prospect records, business relationship information, testimonials, correspondence and images. We process this information only on the business customer's instructions, to provide and secure the requested feature.
The Terms of Use prohibit special-category data, criminal-offence data, children's data and personal data that is unnecessary for the stated business purpose. Please do not submit that information.
If you give us personal data about another person for a purpose for which we are controller, you must have authority to do so and give them this notice where appropriate. If you submit it on behalf of a business customer, that customer is responsible for giving the required information to the person.
4. Required and optional information
We need the identifying, contact, business, area and security information shown as required in the relevant form to provide a free snapshot or create and administer an account. We need the selected package, subscription option and billing information to provide a paid subscription. If required information is not provided, we cannot supply that part of the Service.
Website and social-media URLs, customer lists, Ask MPM questions and files for Create are optional. Some paid features cannot work unless the user provides the relevant input. Entering a URL does not by itself authorise us to collect unrelated personal data from that page. If a user actively includes selected online content in business context or a request, we process that content in the same way as other Customer Content.
5. How and why we use personal data as controller
UK data-protection law requires a lawful basis for each use. This table applies where we act as controller.
| Purpose | Data used | Lawful basis |
|---|---|---|
| Provide a requested free snapshot | Identity, contact, business profile, report-selection and report data | Taking steps at your request before entering a contract, where you will be the contracting party; otherwise our legitimate interests in providing and protecting the Service for the business you represent |
| Create, authenticate and administer an account | Identity, contact, business profile, account and security data | Performance of our contract where you are the contracting party; otherwise our legitimate interests in administering the business account and keeping it secure |
| Provide and preserve paid reports and account history | Business profile, report-selection, subscription, Service output and account-history data | Performance of our contract where you are the contracting party; otherwise our legitimate interests in providing the Service to the business customer. Personal data in Customer Content and outputs created from it is processed on the business customer's instructions |
| Take payment and manage a subscription, renewal or cancellation | Identity, contact, subscription and transaction data | Performance of our contract where you are the contracting party; otherwise our legitimate interests in administering the business subscription; compliance with accounting and tax obligations |
| Prevent fraud, bots and abuse and secure, monitor and troubleshoot the Service | Technical, usage, account, security and relevant error data | Our legitimate interests in a secure and reliable service; compliance with applicable security obligations |
| Provide support and deal with privacy requests | Identity, contact, account and communications data | Performance of our contract where you are the contracting party; compliance with legal obligations; our legitimate interests in customer administration and legal claims |
| Send account, security, payment, renewal and material-change notices | Identity, contact, account and subscription data | Performance of our contract where you are the contracting party; our legitimate interests in administering the business account; legal obligation where applicable |
| Send direct marketing | Identity, contact and marketing preference data | Consent, where obtained through the separate optional marketing choice |
| Comply with law, obtain advice, manage disputes or support a corporate transaction | Data relevant to the issue | Legal obligation; our legitimate interests in protecting legal rights and administering our business |
Where we rely on legitimate interests, we consider the impact on the people concerned and do not use the information where their interests or rights override ours.
Where we act as processor, the business customer decides the lawful basis and purpose. We process the personal data only on its documented instructions, subject to the Terms of Use and any overriding legal requirement.
6. AI-assisted features
We use Anthropic's Messages API directly through a commercial account held by My Pocket Marketer Ltd to help produce parts of snapshots, plans, answers and draft marketing. We do not use Anthropic's Files API. Depending on the feature and choices made by the user, we may send:
- a written summary prepared by our software of the selected area, audience and channel rankings, in words and ranks, never the figures or scores and never the underlying licensed dataset;
- the business type, business name and business context supplied by the user;
- an Ask MPM question and the relevant parts of the user's plan, tasks, previous conversation and business context needed to answer it; and
- for a Create request, the contact details the user chooses to publish in the marketing and, once this is switched on, the text of documents that the user actively selects. Images are never sent to Anthropic; they are kept with the request for the user's reference.
We do not send the uploaded customer list to Anthropic. The customer-list comparison and matching are carried out on our systems. We do not send account passwords, payment-card details or the login email to Anthropic merely because they are held on the account. A name, email address or other identifier may nevertheless be sent where the user includes it in a question, instruction, business context or selected file, or chooses it as a contact detail to publish in Create output.
Our Anthropic organisation is configured for its standard 30-day retention, not zero-data retention. Anthropic may access inputs and outputs for safety and security. If its automated systems flag content as potentially violating its Usage Policy, it may keep the input and output for up to two years and the related safety classification scores for up to seven years. It may also retain information where required by law. We have not joined Anthropic's Development Partner Program and user feedback sharing is switched off, so we do not authorise it to use Service inputs and outputs to train its general models. Anthropic's data-processing terms form part of its Commercial Terms.
Scores and rankings in reports are calculated by our software, not by the AI provider. The Service is not designed to use AI to make a decision about an identifiable person that produces legal or similarly significant effects. AI-assisted content can be incomplete or inaccurate and must be reviewed before use.
7. Who receives personal data
We use service providers and may disclose data to other recipients where necessary. A provider receives only the information needed for its function.
| Recipient | What it does and receives |
|---|---|
| Neon | Hosts the production database in London, including account, business, report and Service records, retained customer-list address rows, Ask MPM conversations and Create or library files |
| Vercel | Hosts and delivers the application from London, processes application requests and holds time-limited request logs. It also provides aggregate, non-identifying visit analytics through Vercel Web Analytics |
| Sentry | Records and helps us investigate application errors. It receives the error, page or request address and account identifier, but our application does not write prompts, answers, business context or file content to Sentry. Session replay is not used |
| Stripe | Processes payments and subscriptions. Stripe acts on our instructions for some activities and as an independent controller for its own legal, security and fraud-prevention purposes |
| Anthropic | Acts as a subprocessor for the AI-assisted functions described in section 6. It may receive business context, the business name, contact details the user chooses to publish and, once switched on, the text of documents actively selected for a Create request (never images). It does not receive the uploaded customer list, the login email merely because it is held on the account, or payment details |
| Google reCAPTCHA | Helps prevent bots, fraud and abuse and may process IP address, device/browser information, cookies and security signals under Google's terms |
| Adobe (Adobe Fonts) | Supplies the font our headings use, which is licensed through Adobe. It receives the visitor's IP address to deliver the font and receives technical details such as our website's domain for licensing and service operation. Adobe says it does not store the visitor's IP address and does not set a cookie when serving the font |
| Microsoft 365 | Hosts privacy, support, cancellation and other business email |
| Mailchimp (Intuit) | Sends marketing email and manages the marketing list where a person has opted in. It receives the email address and contact name |
| Resend | Sends service emails, including email confirmation, password reset, receipts, renewal and payment notices, plan-ready messages and billing changes. It receives the email address and message |
| Professional advisers, insurers, courts, regulators and authorities | Receive relevant information where needed for advice, insurance, legal claims or compliance |
| A buyer, investor or successor | May receive appropriately protected and minimised information during a proposed or completed sale, investment or reorganisation |
Our processors may use their own subprocessors. We require them to protect personal data and use it only for the contracted service. We do not sell personal data or disclose it to another organisation for that organisation's own marketing.
8. International transfers
Some providers, support teams or subprocessors may access personal data outside the UK. Where UK transfer restrictions apply, we use an approved safeguard. Depending on the provider and destination, this may be:
- UK adequacy regulations, including a valid UK Extension to the EU-US Data Privacy Framework;
- the UK International Data Transfer Agreement; or
- the UK Addendum to the EU Standard Contractual Clauses,
together with any transfer-risk assessment and supplementary measures that are required. Contact us for more information about the safeguard used for a particular provider.
9. How long we keep personal data
We keep personal data only for as long as reasonably necessary for its purpose. We consider the type of information, why we need it, legal and contractual requirements, security and dispute risks, and provider settings.
| Information | How long we keep it |
|---|---|
| Free snapshot information where no account is created | Normally for up to 12 months after the last interaction |
| Account, business profile, reports, plans, tasks and generated marketing | While the account remains open and the information is needed to administer it or preserve the user's history. Cancelling a subscription does not delete the account. The user may request deletion at any time, subject to records we must retain |
| Customer-list uploads | The source file is not stored. Address and postcode rows from an unconfirmed upload are deleted within two days; rows from a confirmed upload are deleted within 30 days of upload. A deletion audit record containing dates and counts is retained. The resulting Customer Profile contains totals rather than addresses or rows and remains with the account |
| Files added to one Create request | Until 30 days after the draft is made, then deleted from the live file store. A file added but never used in a draft is deleted 30 days after it was added |
| Files saved to the company library and text extracted from them | Until the user deletes them or closes the account, then deleted from the live file store within 24 hours |
| Ask MPM conversation history | While the account is open, unless the user deletes the conversation earlier |
| Ask MPM and Create operational logs | Questions, answers, business context, extracted text, images and file content are not written to our application logs. Ordinary request, security and error metadata is covered by the technical-log period below |
| Registration, sign-in and password-reset attempt counters | Up to two days |
| Support and routine correspondence | Normally for 24 months after receipt. It may be kept longer for an ongoing complaint, dispute, incident or legal claim |
| Technical, security and error information | For the shortest period reasonably needed to secure, operate and troubleshoot the Service. Routine records are normally kept for no more than 90 days. Records relating to an active incident, investigation or claim may be kept longer |
| Marketing information | Until consent is withdrawn or the person objects. We may retain a minimal suppression record for as long as needed to honour an opt-out |
| Financial, legal and compliance records | For the applicable statutory or legal-claims period. Accounting and transaction records are normally kept for six years after the end of the relevant financial year |
| Anthropic API inputs and outputs | Normally 30 days. Content flagged by Anthropic's safety systems may be kept for up to two years and related safety classification scores for up to seven years. Legal retention may also apply |
| Backups | Information deleted from the live system may remain in restricted rolling backups for up to seven days, where it is put beyond ordinary use and is not restored to live use except for disaster recovery |
Deleting a source file does not remove text or an image that is already part of a separately saved draft or conversation. The user must delete that output separately. Detailed periods for individual systems and providers are recorded in our internal retention schedule and should be reviewed regularly.
10. Direct marketing
We send marketing email only to people who have asked to receive it. When a person requests a free snapshot, they may tick a separate optional box to opt in. It is not pre-ticked, and leaving it unticked does not affect the report or another part of the Service.
Where a person opts in, we record the date, place and wording of the choice. We pass the email address and contact name to Mailchimp to send marketing on our behalf. We do not pass the customer list or Customer Content to Mailchimp.
A person may object to direct marketing or withdraw consent at any time by using the unsubscribe route in the message or contacting us. This does not stop service, payment, security or legal notices. Withdrawal does not affect processing that was lawful before it.
11. Cookies and similar technologies
We use authentication and security technologies, including Auth.js cookies and Google reCAPTCHA, and aggregate, non-identifying visit analytics through Vercel Web Analytics, which does not use cookies. We do not currently use advertising or individual-tracking analytics technologies. More detail is in our Cookie and Similar Technologies Notice.
12. Security
We use technical and organisational measures intended to protect personal data. These include password hashing, encrypted connections, provider encryption at rest, access controls, multi-factor authentication for administrative accounts, rate limiting, bot protection, environment separation, backups and time-limited logging.
When a password is created or changed, we check it against the Have I Been Pwned breached-password service using a range-search method. Only the first five characters of a one-way cryptographic hash are sent, not the password, email address or other account information.
No system is completely secure. Users are responsible for choosing a strong, unique password and telling us promptly if they suspect unauthorised access.
13. Rights and requests
Depending on the circumstances, a person may have the right to:
- obtain a copy of their personal data and information about its use;
- correct inaccurate or incomplete personal data;
- have personal data deleted;
- restrict how personal data is used;
- receive personal data they provided in a portable form;
- object to processing based on legitimate interests;
- object at any time to direct marketing; and
- withdraw consent at any time where processing relies on consent.
Some rights are conditional and exemptions may apply. For example, we may need to keep transaction records to comply with law. We will explain a decision not to comply fully.
Contact us to exercise a right concerning personal data for which we are controller. We may ask for proportionate information to confirm identity. Requests are normally free and we respond without undue delay, normally within one month.
If the request concerns personal data submitted by one of our business customers, contact that business first because it normally controls the information. If the requester contacts us, we may refer the request to the relevant business and assist it in accordance with our Data Processing Terms.
Account deletion is handled manually. Cancelling a subscription does not automatically delete an account, and deleting an account does not by itself cancel a Stripe subscription. Tell us clearly whether cancellation, account deletion or both are required.
14. Complaints
You may complain to us if you believe we have not handled personal data in accordance with data-protection law. Contact privacy@mypocketmarketer.com. No special wording or form is required.
We will acknowledge a data-protection complaint within 30 days, investigate it appropriately, keep the complainant informed where necessary and give the outcome without undue delay.
If the complaint concerns Customer Content controlled by one of our business customers, we will acknowledge it, refer it securely to that customer where appropriate, and assist the customer under our Data Processing Terms.
A complaint may also be made to the Information Commission, the UK data-protection regulator operating as the Information Commission's Office (ICO), through ico.org.uk/make-a-complaint. The right to contact the ICO is not affected by complaining to us first.
15. Changes to this notice
We will update this notice when our handling of personal data changes and change the date at the top. We will give registered users direct advance notice of a material change where practical and appropriate.