Privacy Policy

Effective date: 4 August 2026

Beefydle is operated by Michael Sherriffs (“Beefydle”, “we”, “our” or “us”). This policy explains how information is accessed, stored, used and shared when you use our mobile applications.

Where consent is legally required, it is requested separately through the app, an advertising consent form or your device settings. Simply using an app is not treated as consent where affirmative consent is required.

1. Apps Covered Back to top

2. Advertising-Supported Games Back to top

The six games identified above use Google AdMob. Beefydle does not directly receive or store identifiable information collected by the advertising SDK. Information used for advertising is transmitted directly to and processed by Google through the Google Mobile Ads SDK, which may automatically process:

• IP address and general location inferred from it;
• advertising and other device or app identifiers;
• device type, operating system and app version;
• app launches, taps, video views and other interactions;
• advertisements shown and interactions with them; and
• performance, crash and diagnostic information.

Google may use this information for advertising, measurement, analytics, fraud prevention and security. Depending on region, consent choices, device settings and platform permissions, Google may provide personalised or non-personalised advertisements.

Beefydle does not use AdMob mediation. Its maximum advertising content rating is PG, although this does not guarantee that every advertisement is suitable for every user.

3. Hello Launcher Back to top

Hello Launcher contains no advertising or analytics SDK. Beefydle does not directly receive or store information entered or created within Hello Launcher. Information remains on your device or is sent directly from your device to a service you deliberately activate.

Installed applications

Hello Launcher accesses information about applications you can launch so it can display and open them. This stays on your device, is used only for launcher functionality and is not sent to Beefydle, advertisers or analytics services.

Weather

You may manually enter a city and your own OpenWeather API key. These are sent directly to OpenWeather to retrieve current weather and may be stored locally. Hello Launcher does not access GPS location, request location permission or automatically determine your location. You can change the city or remove the key by clearing the relevant field and using the app’s set function.

Microphone and speech recognition

Microphone access requires permission, begins only after you tap the microphone button and ends automatically when recognition finishes or no further speech is detected. Audio is handled by the speech-recognition service configured on your Android device, commonly Google, although another compatible provider may be used.

No audio is sent to or possessed by Beefydle. The transcription is returned to Hello Launcher and, when used for an AI conversation, sent directly to Cohere.

Camera and selected images

Hello Launcher may open your device’s camera application or Android’s image-selection interface when you deliberately choose those features. Images can be used as an in-app wallpaper or texture, or sent to Cohere as part of an AI conversation. Images may be copied to local app storage and are sent to Cohere only when you include them in a request and press send. Beefydle does not intentionally access embedded location metadata.

AI prompts and conversations

Hello Launcher sends requests directly to Cohere’s chat API using the API key you provide. Submissions may include typed text, speech transcriptions, relevant prior conversation history, images you include and technical information necessary for the request. It currently uses Cohere’s command-a-vision-07-2025 model or an equivalent replacement.

Requests travel directly from your device to Cohere. Beefydle does not receive, possess or log prompts, images, history or responses. Cohere processes them under the privacy policy and terms applicable to your Cohere account.

User-provided API keys

OpenWeather and Cohere keys are stored locally and sent only to their respective services. They are not sent to Beefydle or used for advertising or analytics. You can clear a key in the app and revoke it through the provider.

4. Local App Data Back to top

Our apps may locally store game progress, scores, settings, selected city, API keys, AI prompts and responses, conversation history, speech transcriptions, images, wallpapers or textures. This data generally remains until replaced, removed through an available feature, cleared through device settings or removed by uninstalling. Some individual images or conversation items may not have a separate deletion control.

5. How Information Is Used Back to top

• Provide app functionality and save progress or preferences;
• display launchable applications;
• retrieve weather for a city you enter;
• convert speech to text and provide AI responses;
• use selected images as wallpapers, textures or AI inputs;
• allow Google AdMob to display and measure advertisements in the six advertising-supported games;
• allow relevant third-party providers to detect fraud, abuse and technical problems; and
• comply with legal obligations.

Beefydle does not sell personal information.

6. Third-Party Services Back to top

• Google: AdMob and commonly Android speech recognition. Privacy policy
• Cohere: AI prompts, context, speech-derived text and submitted images. Privacy policy
• OpenWeather: the city and API key provided for weather. Privacy policy
• Your speech provider: another provider may apply depending on your device configuration.

7. Information Sent Directly to Beefydle Back to top

Beefydle does not receive information from users through the apps themselves. If you independently contact us by email or post, we will receive the contact details, message, attachments, correspondence and other information that you voluntarily provide.

Electronic and postal correspondence may be accessed and handled by authorised persons who assist Beefydle with communications, customer support and administration. This may include receiving correspondence, relaying its contents to the data controller and sending responses on Beefydle’s behalf. These persons may use the information only for those purposes, protecting legal rights, maintaining security and complying with legal obligations.

8. Legal Bases Back to top

Where the UK GDPR, EU GDPR or similar laws apply, processing may rely on:

• Performance of a contract where processing is necessary to provide an app feature you deliberately request;
• consent for advertising personalisation, optional processing or where otherwise required;
• legitimate interests in security, fraud prevention, support, technical stability and legal claims, where not overridden by your rights; or
• legal obligations and valid legal requests.

9. Sharing and Disclosure Back to top

Information may be disclosed to the services above when you use the relevant feature and accessed by authorised persons when handling communications and administration on Beefydle’s behalf. Information may also be disclosed when required by law, to protect rights or safety, or to establish, exercise or defend legal claims. Locally stored information is inaccessible to Beefydle unless you deliberately send it to us.

10. Retention and Deletion Back to top

App information remains on your device or is handled directly by the applicable third-party service. You can generally remove local information by clearing a field, using an available app control, clearing app storage or uninstalling. Beefydle cannot remotely access, recover or delete information stored on your device.

Third-party providers retain information under their own terms. Electronic and postal correspondence may be kept as reasonably necessary for support, administration, records, security, disputes or legal compliance.

11. Security Back to top

We use reasonable protective measures, but no transmission or storage method is completely secure. Cohere requests use HTTPS, and network requests use encrypted HTTPS connections where supported and configured. Locally stored API keys may not be separately encrypted. If a key may have been exposed, revoke and replace it with the provider.

12. International Processing Back to top

Providers may process information outside your country. Where required, they may rely on adequacy decisions, contractual safeguards or other approved transfer measures. Authorised persons may also access correspondence from a country other than your own. Consult each provider’s policy for details of its processing.

13. Your Rights and Choices Back to top

Depending on where you live, you may have rights to access, correct, delete, restrict or object to processing; withdraw consent; request portability where applicable; and complain to a data-protection authority.

Because Beefydle normally cannot identify app users or access local data, some requests must be completed on your device or directed to the provider. You can disable permissions, avoid optional features, remove API keys, change the city, review advertising choices, clear app storage or uninstall.

14. Children’s Privacy Back to top

Our games are rated for a general audience, including children, and we are aware that children may use them. Hello Launcher, including its AI chat, camera and microphone features, is not designed or intended for use by children, although we cannot fully prevent a child from accessing these features on a shared or family device.

Beefydle does not knowingly collect personal information directly from children through the apps. Where a feature could result in information being sent to a third-party service, such as Hello Launcher’s AI chat, parents and guardians should supervise use of that feature or restrict access to it. If a parent or guardian believes that a child has provided personal information directly to Beefydle or to a third-party service through our apps, they may contact us using the details below so we can assist.

15. Changes to This Policy Back to top

We may update this policy when our apps, providers, legal requirements or information practices change. The revised policy will be published at this URL and its effective date updated when material changes are made.

16. Data Controller and Contact Back to top