Privacy Policy

Version and effective date: 5 October 2026 (2026-10-05)

Spotter is a fitness and social activity app and website operated by Meraki Softworks LTD. We are responsible for the personal information we decide to collect and use for Spotter. This notice explains our app, website, support and marketing practices. It is a notice, not blanket consent to every use of your information.

Meraki Softworks LTD (company number 14223666), Flat 518, 101 Blackwall Way, London, England, E14 9QX. Legal and privacy contact: contact@merakisoftworks.com. App support: hello@spotterapp.co.uk.

1. Information we use and why

Accounts, profiles and community features

We use your account identifier, email, sign-in provider information, name, birthdate, gender, profile photos, biography, interests, fitness level, location label, social handles and visibility preferences to create and protect your account, check the 18+ age requirement, display the profile you choose to share and help you find activities and people. Birthdate is used to calculate age; your profile displays age rather than birthdate. Social sign-in providers supply the account information you authorise them to share.

We process workouts and group details, meeting locations and times, attendance, invitations, friend and blocking relationships, messages, attachments, replies, reactions and activity moments to deliver community features. Information you post in public profiles, feeds, groups or activities may be seen and copied by others. Chat participants can keep or share what they receive. Choose what to disclose carefully, especially health details or another person's information. We do not require medical records or health diagnoses.

We use reports, moderation decisions, verification status, account restrictions and support correspondence to handle abuse, enforce rules and respond to requests. Staff may review material you report or provide for support, and material needed to investigate a safety incident. We do not promise that every activity or user has been reviewed.

Location, maps and optional integrations

With device permission, the app uses foreground location for nearby discovery, map searches and meeting points. Buddy discovery is optional and uses coordinates rounded to two decimal places; meeting points and directions can involve precise coordinates. A location you publish in an activity or send in a message is shared with the relevant audience. Map providers receive technical connection information and map areas, search terms or coordinates needed for the request. You can decline device location access and use manually chosen locations where supported.

Optional calendar and wallet features use the event details you choose to add and the relevant Apple or Google services. Optional workout translation sends the selected workout text to Google's translation service. Avoid translating private or sensitive text you do not want to send to that provider. These features are used only when you select them or enable their setting.

Purchases, referrals and notifications

Apple or Google handles store payments. RevenueCat and our backend use account identifiers, transaction and subscription status, expiry times and referral or promotion redemptions to provide paid access and prevent duplicate rewards. We do not receive your full payment card number from an app-store purchase. Device notification tokens and account preferences let us deliver notifications and, where enabled, live activity updates. Manage notification and live activity permissions in your device settings.

Technical information, diagnostics and discovery

Services receive IP addresses and technical request information. The app uses Firebase Crashlytics and Sentry for error and performance diagnostics, including app version, operating system, device characteristics, stack traces and error context. Server logs help protect and operate the service. Discovery uses recent interactions and affinity signals to rank activities, groups and buddies; it does not make decisions with legal or similarly significant effects.

Session replay records app interactions and technical context for diagnosing problems. In the revised app it is off until you make a separate optional choice, with text, images and sensitive views masked. You can decline without losing app access and withdraw in Settings → Privacy choices. Withdrawal stops future replay; already received diagnostic data follows its retention schedule or an applicable erasure request.

App rollout: The revised privacy choices, account-erasure processing and private chat attachment storage are introduced through a coordinated app and server release. Where a control or erasure step is not yet available in your version, contact our privacy address for manual handling of your request. Older app versions may collect replay under their previous configuration and may use publicly accessible attachment links. Update to access the new controls. Contact us to request help or erasure if your version lacks them. During migration, previously shared attachment URLs can remain accessible until their originals are removed; we do not describe those older links as private. A message audience and storage-link access are different controls.

Website waitlist, emails and partner enquiries

When you join the waitlist or mailing list, we use your email for the launch, beta and Spotter product updates described beside the form. You can unsubscribe in each marketing email. We record signup time, form source, campaign labels and connection country to understand acquisition. A hashed email identifier and Resend contact identifier help avoid duplicate counts and welcome emails. Hashes are pseudonymous personal data. A hashed connection identifier limits requests in ten-minute windows; expired records are cleared on a subsequent waitlist request. Attribution does not use cookies or browser storage.

Cloudflare hosts the website and D1 signup records. Cloudflare Web Analytics is configured for page views and performance on the production website without analytics cookies. Hosting, security and CDN requests still involve connection and device information. Partner enquiry forms prepare an email containing the business and contact details you enter, including name, email, telephone, address and information about proposed activities. The email is sent only when you send it from your email app. Public listing and marketing permissions are separate choices.

2. Legal grounds and sensitive information

Where UK or EU data protection law applies, we rely on contract for account and requested community features, subscriptions and service messages; legitimate interests for security, proportionate moderation, support, fraud prevention, basic diagnostics and service improvement; legal obligation where a specific law requires a record or disclosure; and consent for marketing where required, optional replay, advertising/device technologies where required and optional biometric verification. We consider the effect of legitimate-interest uses on you, and you can object. We do not turn acceptance of our Terms into consent to optional processing.

Device permission is an additional platform control and does not replace a legal basis. Information you voluntarily publish may reveal health, religion or other sensitive matters. We do not infer a consent to unrelated uses from that disclosure. We will obtain any additional permission required for sensitive processing or refrain from that use.

Optional identity verification and biometrics

If you choose verification, Didit processes identity documents, extracted identity details, selfies, liveness information, face comparisons and biometric templates for identity assurance and fraud prevention. We ask for explicit consent before starting a session and provide Didit's verification notice. Our backend stores session identifiers, decisions and status timestamps, rather than copies of your document or selfie. A verified badge is not a criminal-record check, fitness qualification or guarantee of safety.

Our retention instruction is to keep verification data while your account remains active, with earlier destruction when the original purpose is satisfied or applicable law requires a shorter period. You can request earlier erasure or withdraw verification consent by contacting us; this can remove your badge and features that depend on verification. Account deletion includes a full privacy-erasure instruction for attributable retained biometric templates and relevant blocklist data. Deleting an operational session alone is not treated as proof that all templates were erased. Any legally required exception must be explained and limited to that purpose.

3. Your choices and advertising

You can edit profile visibility, social sharing and discovery in the app; block or report users; disable optional integrations; manage device permissions; unsubscribe from marketing; and request access or deletion. Terms acceptance and acknowledgement of this notice are recorded with their document version and a server timestamp. Optional replay and verification choices are recorded separately. Existing users are asked to review revised terms; we do not invent an earlier acceptance record.

Free features may display Google AdMob ads. Google's consent message is checked before ad requests in the revised app, and Advertising privacy options lets you revisit choices where the consent platform requires it. Advertising partners may use device identifiers, IP addresses, approximate location and ad interaction data for delivery, measurement or personalisation as permitted by your choices and law. Apple's App Tracking Transparency permission, where applicable, is separate from advertising consent. See Google's partner-site and app information and our technology notice.

We do not exchange your profile or message content for money. Advertising identifiers or activity can nevertheless count as a “sale”, “sharing” or targeted advertising under some local laws. Where applicable, use advertising privacy options or contact us to exercise opt-out rights, including through an authorised agent. We will honour applicable recognised opt-out signals and will not discriminate for exercising a legal privacy right.

4. Sharing, providers and international transfers

We disclose information to the audiences you choose, providers needed to operate features, and authorities or other recipients where necessary to comply with law, protect people, investigate fraud or establish legal claims. A business transfer may involve limited disclosure subject to appropriate protection and notice. We do not authorise unrelated use of your private communications.

Some providers process information outside your country, including in the UK, EEA and United States. Where required, transfers must use an applicable adequacy decision or appropriate contractual safeguards, with additional measures where needed. Contact us for information about safeguards for your data. A link to a provider policy does not establish the location of a particular deployment or prove that a required contract has been signed.

Providers can act as our processors for service data and as independent controllers for their own services, store transactions or legally required records. Their public policies explain their own practices and may have a different scope from our contract with them. Meraki remains responsible for the processing it controls. Optional features do not share data with every provider listed below.

5. Service providers and their privacy notices

Map data source: OpenStreetMap contributors supply map data used by relevant maps and Photon. A data source is not automatically our processor or the recipient of every map request. See the OpenStreetMap Foundation privacy policy and map attribution and licence.

External social sites, stores and email apps you open have their own notices. Build tools, local libraries and development-only fixtures are not listed as recipients merely because they appear in our source code.

6. Retention and account deletion

We keep active-account information while needed to provide the features you use. Delete your account in the app or use our public account deletion request instructions. Your account is disabled when deletion is scheduled. Signing in does not automatically cancel deletion. The standard deletion window is 30 days; requests that legally require earlier action are assessed individually. Deleting an account does not cancel an Apple or Google subscription.

7. Your rights and complaints

Depending on the law that applies, you can request access, a copy, correction, deletion, portability, restriction, information about recipients or an objection to processing. You can withdraw consent without affecting earlier lawful processing. We may need proportionate identity checks before disclosing or deleting account data; do not email identity documents unless we provide a secure route. We respond within the applicable legal deadline and explain any permitted refusal or extension. Rights are not identical in every country.

Where applicable, you can opt out of sale/sharing and targeted advertising, limit certain sensitive uses, use an authorised agent and appeal a rejected request. Contact contact@merakisoftworks.com for requests or appeals. We will explain the decision and available escalation routes. You can complain to the UK Information Commissioner's Office, your EEA supervisory authority or the privacy regulator where you live; you do not have to contact us first where local law permits a direct complaint.

8. Children, security and changes

Spotter is for adults aged 18 or over. If we learn that an under-18 account or children's information has been supplied, we will investigate, restrict access and delete information as appropriate. Contact us with a concern. An age statement is not a guarantee that no child can access a service.

We use access controls and other measures appropriate to the service, but cannot promise perfect security or confidentiality. The revised chat-media design restricts new attachment access to current conversation members using short-lived links; legacy migration and app release must be completed before older public originals are removed. We do not describe chats as end-to-end encrypted.

We update this notice when our practices change, identify its version and date, and give additional notice or obtain a new choice where required. Previous privacy notice. For privacy concerns, write to the company address or email above.