Cookie & App Technologies Policy

1. Purpose and scope

This policy forms part of the Mosey Legal Suite and should be read with the Privacy Policy, Terms & Conditions, Security Statement and Third-Party Services Register.

Although commonly called a Cookie Policy, the relevant rules can also apply to SDKs, local storage, identifiers, pixels, scripts, tags and other technologies that store information on or access information from a user’s device.

2. Public Mosey website

The public Mosey website is currently published as a static informational website.

Mosey does not currently place advertising cookies, analytics cookies, tracking pixels or similar behavioural-tracking technologies on visitors through the public website.

Because the website does not currently use non-essential tracking technologies, Mosey does not display a consent banner merely to ask for consent to tracking that is not taking place.

The hosting/content-delivery/security infrastructure may necessarily process network information such as an IP address to deliver and protect the website. This is distinct from Mosey placing behavioural advertising or analytics cookies on the visitor’s device.

3. Website Cookie Schedule

Current Mosey-set website cookie and tracking schedule:

• Advertising cookies: none
• Analytics cookies: none
• Behavioural tracking pixels: none
• Marketing cookies: none
• Mosey-set profiling or fingerprinting technologies: none

If this changes, this schedule and the relevant privacy information will be updated before or when the new technology is introduced, and consent or other controls will be implemented where required.

4. Country/region selection on the static website

The website may remember a visitor’s selected UK or US region so that the correct currency, rewards information and legal content can be shown. If this preference is stored on the visitor’s device, it is used for that user-requested preference and not for behavioural advertising or profiling.

Automatic country selection may also use country information supplied as part of the website delivery infrastructure. It is used to select regional content and is not used by the public website for behavioural advertising.

5. The Mosey mobile app

The Mosey mobile application is different from the static website. It may use SDKs, secure tokens, application/device identifiers, local storage and similar technologies to provide app functionality.

These technologies may support:

• authentication and account security
• fraud and abuse prevention
• app preferences and session functionality
• crash diagnostics and performance monitoring
• analytics where enabled
• advertising and attribution where enabled
• rewarded advertising and offerwall functionality where enabled
• push-notification delivery where enabled

6. App consent and non-essential technologies

Where applicable law requires consent before an app technology stores information on or accesses information from a device for a non-exempt purpose, Mosey will obtain the required consent before activating that purpose.

Consent to non-essential app technologies will not be obtained merely by accepting the Terms & Conditions or by continuing to use Mosey.

Where consent is required, members must be able to refuse the non-essential purpose and withdraw consent as easily as it was given, subject to technical limitations outside Mosey’s control.

Technologies genuinely necessary for a service requested by the member, security, authentication or another applicable legal exception may operate without consent where the law permits.

7. Advertising, rewarded ads and offerwalls

Advertising, attribution, rewarded-ad and offerwall SDKs are app technologies and are not described as core application functionality merely because they are integrated into Mosey.

Where these technologies require consent or an opt-out under applicable law, Mosey will provide the appropriate in-app choice before or in connection with their use.

Apple Health/HealthKit and Health Connect activity data will not be provided to advertising networks, advertising SDKs or offerwall providers for advertising, targeting or profiling.

8. App Technology Schedule

Because SDK behaviour can change with app releases, Mosey will maintain an app technology schedule identifying the principal technologies actually included in the released app.

For each principal technology the schedule should identify: provider; technology/SDK; purpose; information stored or accessed; whether it is essential or optional; consent/choice basis where relevant; and an appropriate retention or persistence description.

The schedule must reflect the production app rather than planned or unused integrations. The Third-Party Services Register should identify the corresponding principal providers.

9. Device and operating-system controls

Members may also have controls supplied by Apple, Google or their device operating system, including permissions, advertising settings and notification controls. These controls operate alongside any choices Mosey is legally required to provide in the app.

Changing a device permission may cause a feature that depends on that permission to stop working, but declining an unrelated optional advertising or analytics purpose will not be treated as a Fair Play breach.

10. Changes to website or app technologies

Mosey will review this policy and the technology schedules when relevant website or app technologies materially change and at least annually.

If Mosey later adds analytics, advertising, pixels or other non-essential tracking to the static website, the current “none” statements will be updated and any legally required consent/choice mechanism will be implemented before the non-essential technology is activated.

If a new app SDK introduces a materially different storage/access purpose, Mosey will assess whether fresh consent or another user choice is required before enabling that purpose.

11. Contact

[email protected] – privacy and app-technology enquiries

[email protected] – general support

[email protected] – legal enquiries

22. Equal Choice and Withdrawal

Where consent is required, the first-layer consent interface will offer an equally clear way to accept or reject non-essential technologies. Choosing reject will not activate non-essential advertising or analytics technologies that require consent. Users can revisit their choices later through the published privacy/cookie controls.