MyLawn App Privacy Policy
This is the privacy policy for the MyLawn app (mylawn.mowd.uk). The same policy is shown inside the app under Account → Privacy. If you shop with us at mowd.uk, the mowd.uk privacy policy covers that.
Effective date: 2026-10-23
Version: 1.10.0
This policy explains how the Mowd lawn-care app collects, uses, and protects your personal data. It applies to the Mowd app at mylawn.mowd.uk (and its installable PWA). Our public storefront mowd.uk has its own policy.
1. Who we are
The Mowd lawn-care app is provided by Mowd Ltd (company number 14913717), a company registered in England and Wales with its registered office at 2 Hoden Lane, Cleeve Prior, Evesham, England, WR11 8LH. We are the data controller for personal data you give us when you use the app. Mowd Ltd has applied to the UK Information Commissioner's Office (ICO) for data protection registration; we will add the registration number to this section as soon as it is issued.
Privacy queries: help@mowd.uk — a triaged inbox; privacy requests are tagged on receipt and handled within statutory deadlines (one calendar month for UK GDPR data subject requests, extendable by up to two further months for complex requests).
2. What we collect, why, and on what lawful basis
| Data | Why we have it | Lawful basis (UK GDPR Art. 6) |
|---|---|---|
| Account data — email address, optional display name | To create and identify your account; to send service emails (account changes, password reset). | Contract — we can't run an account without it. |
| Postcode + your lawn details (size, grass type, sun exposure, soil type, and which of your lawns each of your plans is for) | To tailor the lawn-care advice the app gives you, to fetch the right local weather forecast, and to show each plan's treatments, sized to the area, on the right lawn. | Contract — these are how the app works. |
| Lawn-care log — what you applied, when, free-text notes | To time future advice (e.g. don't seed too soon after weed killer) and to power your dashboard. | Contract. |
| Photos you upload | To let you track your lawn over time. We strip GPS and other location metadata on upload. We may also use anonymised photos to improve our lawn-care AI and in marketing — see §5. | Contract for storage; consent (see §5) for marketing and AI-training uses. |
| Subscription tier, plan and progress | To unlock subscriber features, and to show you your plan on the My Plan page. Synced from Shopify (the storefront) when you link your Mowd account. If you subscribe to a plan, we also copy your subscription's current state into the app from our subscription back-office, about once an hour: the plan, how it's billed and its status, your lawn-size band, how many payments you've made towards your next box and when the next one is due, which box comes next and when it ships, where your current box is in delivery (with the carrier and tracking link when there is one) and the date it arrived, and the treatments in it with their timings and amounts. This copy is matched to you by your email address or Shopify customer reference, and in the app only you can see it. We only copy this into the app once you have a MyLawn account; if you delete your account, the copy is removed within the hour. We also keep an internal audit log of when your tier changed (gained or lost subscriber access) so support staff can answer billing-history questions without re-querying Shopify. The log records only the change event, source, and timestamp — never anything you typed or any of your lawn-care data. | Contract. |
| Reminder choices — when you tell the app "not now" about a reminder, or stop a reminder for good: which lawn and task, and until when | So the app stops showing or sending that reminder until it's due again, on every device you use. | Contract — this is how reminders work. |
| Push subscription endpoint | To send the lawn-care reminders you've opted into. Browser-issued opaque token, not an identifier. | Consent — you choose to enable notifications. |
| Device + technical data — browser, OS version, app version, IP address (transient) | Diagnostics; abuse prevention; minimum required to serve the app. | Legitimate interest — running a secure, working service. We balance this against the limited intrusion of standard server logs. |
| Support tickets you submit — your message + a snapshot of your tier, plan, and lawn-area at submission time | To answer your support query quickly. Snapshot avoids needing to ask follow-up questions. | Contract. |
| Feedback you submit | To improve the app. When you tap "Send feedback", the app captures a screenshot of the page you were on (so support can see what you saw) and a small diagnostic bundle — the last few console error / warning messages and the last twenty page paths you visited within the app. The screenshot appears in the feedback form with a Remove button before you submit; the diagnostic bundle is not editable. Diagnostics never include your typed input, lawn details, photos, or credentials. URL query parameters are stripped before recording. | Legitimate interest. |
| Anonymous analytics + error reports — page navigation, app version, device type, error stack traces, and product usage events: which lawn-care action you logged (e.g. mow, feed), which screen you logged it from, whether you attached notes or a product (a yes/no flag only — never the notes themselves), and whether the entry was back-dated. When you upload a photo we record only its pixel dimensions, file size, and whether it was attached to a log entry. Never your email, postcode, address, the text of your notes, or the photo itself. | When you accept the consent banner shown on first launch, we send these to PostHog (analytics) and Sentry (error reporting) so we can identify bugs, understand which features are actually used, and prioritise improvements. | Consent — you opt in via the banner; revocable from Account → Privacy. |
| Share events — when you tap a "share with a friend" button on the home page, we record which channel you picked (WhatsApp / Email / X / Facebook / your device's native share sheet / Copy link / QR code), your browser user-agent (truncated to 500 characters), and the timestamp. We do not send any data to the destination platform on your behalf — your own device handles the actual share. The link itself doesn't identify you. It only carries a label showing it came from a Mowd share and which channel you used (for example WhatsApp). | To identify engaged sharers ahead of a future referral / loyalty programme, and to size how the share feature is used. | Legitimate interest — recognising users who help us grow, balanced against the limited intrusion of recording your own button-tap. |
| App-open record — at most one row per day you open the app, containing your account's internal profile ID and the UTC date. We do not record the time of day, the number of opens that day, or any device details in this record. Removed automatically when you delete your account. | To produce an internal aggregate count of how many users opened the app on each day, used by Mowd staff on the admin dashboard to gauge engagement. Not shared with any third party. | Legitimate interest — measuring service engagement, balanced against the limited intrusion of one day-stamped row per user per day. |
We do not collect:
- Precise location (we keep your postcode, not your address; we strip GPS from uploaded photos).
- Browsing or behavioural advertising data — the app has no third-party advertising trackers.
- Special-category data (health, biometrics, etc).
- Payment details — when you subscribe, payment goes through Shopify; we never see your card.
3. Where your data is stored, and who processes it
We host on Supabase (data and auth) and Vercel (the app frontend), both with EU data residency for our project. The following service providers (data processors under UK GDPR) handle your data on our behalf, under written contracts:
| Provider | Purpose | Region |
|---|---|---|
| Supabase, Inc. | Database, auth, file storage | EU (Frankfurt) |
| Vercel, Inc. | Frontend hosting + edge functions | EU |
| Resend | Transactional emails (support, account) | EU |
| Klaviyo | Marketing emails + support ticketing (when you submit a ticket) | EU |
| Apple / Google / Mozilla push services | Delivering push notifications you've opted into | Worldwide infrastructure; we send only the minimum payload needed |
| Shopify | Storefront + subscription management; we read your tier and link via your Mowd customer ID | EU |
| Sentry (opt-in via consent banner) | Error reporting | EU |
| PostHog (opt-in via consent banner) | Anonymous product analytics | EU |
| Met Office DataHub | Weather forecasting (no personally-identifying data sent — we send postcode-derived coordinates only) | UK |
Where a provider operates infrastructure outside the UK or EEA, transfers are protected by the UK's International Data Transfer Addendum to the EU Standard Contractual Clauses, or by the relevant adequacy regulations.
4. How long we keep it
| Data | Retention |
|---|---|
| Account data | Until you delete your account. |
| Lawn details + lawn-care log | Until you delete the lawn (or your account). |
| Reminder choices | Until they run out or you change them, and always when you delete the lawn (or your account). |
| Photos | Tiered: weekly photos are kept for ~3 months, monthly for ~1 year, quarterly for ~3 years, yearly indefinitely. You can delete any photo at any time. |
| Push subscription endpoint | Until you turn off notifications, sign out on that device, or 90 days after the device last failed to receive a push. |
| Support tickets | 24 months after resolution, then deleted unless you ask us to keep them longer. |
| Subscription-tier change log | Retained alongside your account. If you delete your account, the log entries that referenced you are detached from your profile but kept indefinitely keyed by your Shopify customer reference, so we can answer billing-reconciliation queries from Shopify after the fact. |
| Subscription details (tier, plan and the progress shown on My Plan) | While you have a MyLawn account and your subscription (active, paused or cancelled) is in our records. The copy is refreshed about once an hour. If you delete your app account, the app's copy is removed within the hour; your subscription itself, and Mowd's record of it, are not part of your app account — see Deleting your account below. |
| Share events | Retained alongside your account. If you delete your account, the rows are detached from your profile and the link to you is severed — they remain only as anonymous "someone tapped channel at time" entries used for service-wide analytics. |
| Server logs containing IP addresses | 30 days. |
Backups and recovery
We back up your account data once per day — we do not run continuous (point-in-time) backups. In the unlikely event we need to restore from a backup, up to 24 hours of recent activity (lawn-log entries, reminder updates, profile changes) may be lost. Where that happens to you specifically, we will tell you what was affected.
Photos you upload are stored separately and aren't covered by these database backups. If a storage incident affects the photo bucket, photos may not be recoverable; otherwise photos follow the retention table above.
Deleting your account
When you delete your Mowd app account, your data is removed from our active systems immediately — profile, lawns, log entries, photos, reminders, and notification subscriptions. Three narrow exceptions: (a) the subscription-tier change log described in §4 — the rows that referenced you are detached from your profile (the link to your profile is severed) but kept keyed by your Shopify customer reference, so we can answer billing-history queries that arrive from Shopify after deletion; (b) the share events described in §4 — the rows are detached from your profile and remain only as anonymous channel + timestamp entries with no link back to you; (c) your subscription details described in §2 — the app's copy of your plan, payments and deliveries is held against your email address and Shopify customer reference rather than your app login, so it is not deleted at the same moment; the app only keeps it for people with a MyLawn account, so it is removed within the hour. Mowd's own record of your subscription stays with your subscription, not your app login. Deleting your app account does not cancel your subscription. To cancel it, or to ask us to erase your subscription records, email help@mowd.uk; we'll erase them except where the law requires us to keep them (for example, financial records). No app data about you (lawn details, log, photos, support history) is retained. Your data may continue to appear in routine database backups for up to 7 days, after which it ages out automatically. We do not access these backups except to recover from a service incident; if a recovery falls in that window, we re-apply your deletion to the restored database within 14 days as part of the recovery process.
5. Photos you upload — marketing and AI uses
When you take a photo of your lawn in the Mowd app, you choose whether to upload it. The first time you upload a photo, we ask you to acknowledge the following uses; you can withdraw consent at any time from your Account page in the app.
- What we do with your photos. We store them for you to track your lawn over time. We strip GPS and other location metadata on upload — we never keep where you took the photo.
- Marketing use. We may show your photos on mowd.uk, in our social posts, in app guides, or in product imagery. Always anonymous: never your name, postcode, or anything identifying. We never include faces or other people in shot, and we won't use a photo if there's any chance of identifying the lawn's location.
- AI training. We may use anonymised photos to train our internal lawn-care models so the advice we give the next gardener is better. This is in-house only — photos are not shared with third-party AI providers as training data.
- What we don't do. We don't sell your photos. We don't share them with advertisers. We don't use a photo you've asked us to delete.
- Your control. Delete individual photos any time from the Feed. Switch off marketing and AI use any time from your Account page (this stops us using any future or past photo for those purposes — we keep storing them for your own use unless you also delete them).
- Lawful basis. UK GDPR Article 6(1)(a) — your consent. You give it the first time you upload a photo in the app, and can withdraw it at any time without affecting the rest of our service.
6. Cookies and local storage
The app uses localStorage and IndexedDB to keep you signed in, cache content for offline use, and remember small UI preferences. We do not use third-party advertising or analytics cookies. The PWA service worker caches static assets and recent guidance content.
Links from the app to mowd.uk carry a short label saying they came from the app and from which screen (for example utm_source=mylawn&utm_campaign=plan). It never includes your name, email, account or any ID. What mowd.uk records about your visit is covered by the mowd.uk privacy policy and its cookie banner.
7. Push notifications
Push notifications require your active permission via the browser prompt. You can revoke at any time in your browser or device settings, or under Account → Notifications in the app. We respect per-category quiet hours and rate limits — see the app's notification preferences for the categories you can enable or disable.
8. Your rights under UK GDPR
You have the right to:
- Access — ask for a copy of the personal data we hold about you. The app's Account → Export my data button gives you a complete machine-readable export immediately.
- Rectification — correct anything that's wrong (most fields are user-editable in the app).
- Erasure — delete your account and your data (Account → Delete my account; takes effect within 30 days, with up to a further 60 days for backup roll-off). Your subscription records are separate from your app account: to have those erased, email help@mowd.uk (see §4, Deleting your account).
- Restriction — ask us to stop processing your data while a complaint is investigated.
- Portability — get your data in a machine-readable format (the export above is JSON).
- Object — to processing based on legitimate interests.
- Withdraw consent — for the consent-based processing above (push, photo marketing/AI use), at any time, without affecting the rest of the service.
- Complain to the ICO — if you think we've handled your data badly. You don't need to come to us first, but it usually helps if you do. The ICO's website is ico.org.uk.
To exercise any of these rights, email help@mowd.uk with "Privacy request" in the subject line.
9. Security
- Data in transit is encrypted with TLS.
- Data at rest is encrypted by Supabase (AES-256).
- Photo storage is owner-readable (Row Level Security) — no other user can see your photos.
- Service-role keys (full DB access) are never bundled into the app; they're used only by server-side functions.
- We follow the OWASP Top Ten checklist when reviewing app changes, including SAST scanning of every code change before merge.
We can't promise zero risk — no online service can — but we'll tell you within 72 hours if a breach affects your data, in line with UK GDPR Article 33.
10. Children
The Mowd app is not intended for children under 13. We don't knowingly collect data from children under 13. If you believe a child has signed up, contact us and we'll remove the account.
11. Changes to this policy
We may update this policy. Whenever we do, the version number above changes and a summary appears in CHANGELOG.md alongside the policy in the app's source code (publicly viewable). Material changes — anything that affects what data we collect, how we use it, or who we share it with — will trigger an in-app banner the next time you sign in, asking you to acknowledge the new version. You can compare versions in the changelog.
12. Contact us
For privacy queries, complaints, or to exercise the rights in §8:
Email: help@mowd.uk (subject: "Privacy request")
Post: Mowd Ltd, 2 Hoden Lane, Cleeve Prior, Evesham, England, WR11 8LH
If we can't resolve a complaint to your satisfaction, you have the right to lodge a complaint with the Information Commissioner's Office (ICO): ico.org.uk.
Mowd Ltd is registered in England and Wales (company number 14913717). ICO data protection registration: applied for — the number will appear here once issued.