Privacy Policy

Last Updated: July 20, 2026

Cranix is an independent 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 its operator.

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 an independent 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, issue reports, bug reports you submit through the website form (including the app version and platform you enter, and an optional contact email), 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: your Cranix Core account holds your username, email address, display name, avatar, a securely hashed password (we never store your password in readable form), account status and role, sign-in sessions and devices, and security events (such as sign-ins and password changes).
• Two-factor authentication: if you enable it, we store your authenticator secret in encrypted form and your backup codes in hashed form. We cannot read either back as plain text.
• Encryption keys: for end-to-end encrypted features, we store your public key and an encrypted copy of your private key that only you can unlock with your password or recovery code. We cannot decrypt it.
• Community and moderation information: usernames, den and channel IDs, moderation actions, reports (including any content you choose to include when reporting), suspension records, 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, dens, channels, voice chat, video, screen sharing, moderation, and reliability.

• Messages and communication data: messages, attachments, channels, dens, direct messages, call participation, connection state, and related metadata may be processed so the app can function. Den-channel messages are stored so the conversation works and can be moderated.
• End-to-end encrypted messages: when you turn on encryption, the content of your direct messages (and some small private conversations) is encrypted on your device and stored only as ciphertext. Cranix and the server operator cannot read it. We can still see metadata that is not encrypted — such as who is talking to whom and when. Encrypted content only becomes readable to moderators if you choose to report a message, in which case your app attaches that content to the report.
• Where your den's data lives: Today, Cranix operates the servers that host dens and stores den messages, channels, and content in its databases so the app works and can be moderated. Self-hosting — running a den on hardware you or a community host control — is planned. When a den is self-hosted, the person running it controls the content stored on that server and Cranix provides only the shared account and sign-in layer, and Cranix does not receive or store the messages held on a server it does not operate.
• 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 Platform Services

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

• Accounts: Core processes email addresses, usernames, display names, avatars, securely hashed passwords, authentication tokens, sessions and devices, account status and role, and security events.
• Email: we send account emails such as verification and password-reset links through an email delivery provider, which processes your email address for that purpose.
• Support and moderation: the shared moderation queue stores support tickets, bug reports, and user reports forwarded from Cranix apps or submitted through the website, including any content a reporter chose to include, along with status and staff notes.
• Updates: update services 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 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 relies on third-party services to run. These currently include, among others:

• Cloud hosting for Cranix Core (currently Render) and database hosting for account and app data;
• Email delivery (currently Resend) to send verification and password-reset emails;
• Riot Games for Cranix Scout game data;
• Website and delivery infrastructure (such as Cloudflare and GitHub) for the website, downloads, and updates;

Some of these providers are based outside the UK, so your information may be transferred to and stored in other countries. Where that happens, we rely on appropriate safeguards permitted by data-protection law. Those services have their own terms and privacy policies, and 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.
• Account deletion: you can delete your Cranix account. Deleting it removes your account data; some app-specific data (for example your Cranix One profile) can be removed from within that app. Certain records may be kept where the law, security, or abuse-prevention requires 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 accounts and communication features are for people aged 13 and over (or older where local law requires a higher age). Cranix is not directed at children under 13, and we do not knowingly collect their data. If you believe a child under 13 has created an account, contact us and we will remove it.

15. Our Lawful Bases (UK GDPR)

Where UK data-protection law applies, we process your information on these bases: to perform our agreement with you (providing the account and features you ask for); our legitimate interests (keeping the service secure, preventing abuse, and improving it, balanced against your rights); your consent (for optional features you switch on); and legal obligation (where the law requires us to keep or share limited information).

16. Your Rights and Choices

Depending on where you live, you may have rights to access the information we hold about you, correct it, delete it, restrict or object to how we use it, and receive a copy of certain data (portability). You can exercise these by contacting Cranix through the support link on the website.

If you are in the UK and are unhappy with how we handle your data, you also have the right to complain to the Information Commissioner’s Office (ICO) at ico.org.uk, though we ask that you contact us first so we can try to help.

17. Changes to This Policy

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

18. Contact

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