Privacy Policy

Last Updated: May 17, 2026

Cranix is a personal software project operated by Ciaran Moore. Cranix is not currently a registered limited company. In this policy, “Cranix”, “we”, “us”, and “our” refer to the Cranix project and the person operating it.

This policy explains how information may be handled when you use the Cranix website, download Cranix apps, take part in testing, use support channels, or use Cranix products such as Cranix One, Cranix Player, Cranix Notes, Cranix Scout, and future Cranix Core services.

1. Who Controls Your Data

For privacy and data protection purposes, Cranix is currently operated as a personal project by Ciaran Moore. The main contact route for privacy, support, deletion, or account questions is the Cranix support channel linked on the website.

If Cranix later becomes a registered business, adds a dedicated support email, or introduces a formal account system, this policy will be updated so users know who controls their data and how to contact us.

2. Information We May Process

• Website and download information: basic technical details such as browser type, device type, pages visited, download interactions, error information, and security logs where needed to keep the site available and safe.
• Support information: messages, usernames, Discord IDs, issue reports, screenshots, crash logs, diagnostic information, and anything else you choose to send when asking for help.
• Product information: local settings, preferences, saved accounts, diagnostic information, update checks, feature usage, and product-specific data depending on the Cranix app you use.
• Beta testing information: tester feedback, bug reports, account details used for testing, device or app logs, and reliability information needed to improve closed beta or early access builds.
• Account and platform information: if Cranix Core or Cranix accounts are introduced, we may process account details such as username, email address, login identifiers, account status, linked products, support history, and security events.
• Community and moderation information: usernames, platform IDs, server IDs, moderation actions, reports, and audit records where needed to protect users and enforce rules.

3. Why We Use Information

• To provide Cranix services: running downloads, apps, accounts, saved settings, support tools, game lookups, communication features, and update systems.
• To improve Cranix: fixing bugs, understanding crashes, improving performance, testing new features, and making products more reliable.
• To keep users safe: preventing abuse, detecting suspicious activity, moderating community spaces, protecting accounts, and maintaining service security.
• With your consent: where you choose to enable optional features such as account linking, cloud sync, public report sharing, analytics choices, or beta access.
• Where required by law: keeping or sharing limited information where we are legally required to do so.

4. Cranix One

Cranix One is a communication app currently in closed beta. It may process information needed for accounts, profiles, messages, direct messages, servers, channels, voice chat, video, screen sharing, moderation, and reliability.

• Messages and communication data: messages, attachments, channels, servers, direct messages, call participation, connection state, and related metadata may be processed so the app can function.
• Voice, video, and screen sharing: live communication features may process real-time audio, video, and screen data while those features are active. Diagnostic data may be used to fix connection, audio, or performance issues.
• Beta data: because Cranix One is still being tested, bug reports, crash details, and logs may be used to improve stability and safety.
• User responsibility: do not share private, illegal, harmful, or sensitive information in Cranix One unless you understand the risks of using beta software.

5. Cranix Player

Cranix Player is a desktop media application for music and video. It is not based on or limited to any single provider.

• Local app data: preferences, settings, playback state, queue state, library state, history, cached metadata, window state, and app configuration may be stored locally on your device.
• Local media: media files you open, import, organise, or play may be read by the app so media playback and library features can work.
• Provider integrations: if supported music or video provider integrations are added or enabled, Cranix Player may process the information needed for those integrations, such as account identifiers, media metadata, playlists, artwork, playback availability, and session details.
• Authentication: where provider sign-in is supported, authentication should be handled through the relevant provider or a secure Cranix flow. Cranix Player should not ask for third-party provider passwords directly.
• Third-party content: music, video, artwork, metadata, playlists, albums, channels, and other provider content remain subject to the relevant provider’s own terms, privacy policy, copyright rules, account rules, and service availability.
• Updates and downloads: Cranix Player may check GitHub releases, the Cranix website, or future Cranix update services to help users get the latest version.

6. Cranix Notes

• Offline-first storage: Cranix Notes is designed to store notes locally on your device by default.
• Local content: notes, notebooks, pages, widgets, settings, preferences, and workspace layout may be stored on your device.
• Future sync: if cloud sync is introduced, synced notes may be processed by Cranix systems or third-party infrastructure. Cranix should use encryption and clear user controls where possible.
• Backups: you are responsible for backing up important notes, especially when using beta or experimental versions.

7. Cranix Scout

Cranix Scout is a game statistics and information platform. League of Legends is the first supported game, but Cranix Scout may support additional games and data sources over time.

• Game lookup data: player names, tags, regions, match history, live game data, champion data, and public game statistics may be processed to provide reports and analysis.
• Third-party game data: Cranix Scout may rely on Riot Games or other game data providers. Their rules, terms, and data availability may affect what Cranix Scout can show.
• Saved profiles: if saved accounts, favourites, dashboards, or public reports are used, the selected game identifiers and report data may be stored.
• Public reports: shared report links may be visible to anyone with the link until removed, expired, or disabled.

8. Cranix Core and Future Platform Services

Cranix Core is planned as the shared platform layer for Cranix accounts, product access, update delivery, support, and cross-product services.

• Accounts: future account systems may process email addresses, usernames, hashed passwords or authentication tokens, profile details, product access, and security logs.
• Support: future support systems may store tickets, reports, attachments, messages, product versions, and status history.
• Updates: future update services may process app version, operating system, release channel, and update status so Cranix apps can check for and install updates.
• Cross-product features: integrations between Cranix apps may process only the information needed to make those features work.

9. Cookies, Local Storage, and Analytics

• The Cranix website may use cookies, local storage, or similar browser features for basic site behaviour, preferences, security, and performance.
• Cranix apps may use local storage, app storage, cache files, logs, or configuration files on your device.
• If optional analytics are added, the aim should be to collect only what is useful for improving Cranix and to give users clear information where practical.

10. Third-Party Services

Cranix may rely on third-party services for hosting, downloads, updates, identity, music, game data, community support, and infrastructure. These may include services such as Cloudflare, GitHub, Discord, Riot Games, Microsoft, supported media providers, and other providers used by Cranix products.

Those services have their own terms and privacy policies. Cranix does not control how third-party platforms process data outside Cranix products.

11. Sharing Information

• We do not sell user data.
• Information may be shared with service providers where needed to host, secure, update, support, or operate Cranix products.
• Information may be shared when required by law, to protect users, to prevent abuse, or to investigate security issues.
• Information you choose to make public, such as public Scout reports or public profile details, may be visible to other users.

12. Data Retention and Deletion

• Local app data remains on your device until you delete it, uninstall the app, clear the relevant storage, or use an app feature that removes it.
• Support messages, reports, and beta feedback may be kept while needed to resolve issues, maintain records, improve Cranix, or protect users.
• Moderation and security records may be kept while needed for safety, abuse prevention, and audit purposes.
• Where possible, you can ask for account, support, or stored product data to be deleted. Some information may need to be kept where required for security, legal, or abuse-prevention reasons.

13. Security

Cranix aims to use reasonable technical and organisational steps to protect information, including access controls, secure configuration, limited data collection, and safer defaults where possible. No website, app, server, or beta system can be guaranteed to be completely secure.

14. Children and Young Users

Cranix products are not aimed at very young children. If you are under the age required to use a relevant platform, product, or third-party service, you should only use Cranix with permission from a parent or guardian.

15. Your Rights and Choices

Depending on where you live and what data is involved, you may have rights to access, correct, delete, restrict, or object to certain processing of your information. You can contact Cranix support to ask about your data, request deletion, or raise a privacy concern.

16. Changes to This Policy

This policy may be updated as Cranix products change, as Cranix Core is introduced, as new features are added, or if Cranix becomes a registered business. The “Last Updated” date will be changed when the policy is updated.

17. Contact

For privacy questions, deletion requests, support issues, or account questions, use the support link on the Cranix website.