Privacy Policy

This policy applies to the ElyxS web application, public documentation, wallet-authenticated features, user-created draws, support forms, legal acceptance, and related services.

The public beta is developed and maintained under the public identifier ElyxS Maintainer. Privacy and data-processing requests related to the ElyxS interface are handled by ElyxS Maintainer. Contact: privacy@elyxs.com.

ElyxS does not store wallet keys or custody assets that remain in a user's wallet. Users interact with smart contracts through their own wallets.

Some disclosed prizes for user-created draws are transferred into smart-contract custody before a draw becomes active and remain there until a successful winner claim or an allowed pre-result return.

Wallet addresses, transactions, draw requests, immutable rule and content commitments, tickets, fee records, settlement events, winners, claims, and refunds may be public and permanent on Supra L1.

ElyxS cannot delete or rewrite public blockchain records. Third parties can copy and index them independently.

Depending on how you use ElyxS, we may process:

• wallet address, wallet-authentication challenges, session identifiers, and network selection;
• profile data you provide, such as username, display name, avatar, bio, timezone, language, and social links;
• participation, draw, claim, refund, and organizer-revenue history derived from chain data and supporting ElyxS data;
• user-created draw drafts and submitted content, including title, description, website, prize terms, cover image, content location, and its immutable commitment;
• uploaded-file metadata, security-scan results, storage identifiers, and delivery URLs;
• fungible-asset or NFT addresses, metadata, collection details, media URLs, ownership checks, and transferability checks requested by the creation flow;
• feature-access and availability data used to provide the service and handle audits, support, or disputes;
• transaction-attempt and status-check data, including action type, status, timestamps, and transaction hash when available;
• support requests, including name, email, category, optional wallet address, message, and attachments;
• legal acceptance records, including document set, wallet address, time, IP address, user agent, method, and document-set hash;
• consent, browser preferences, limited analytics, and sanitized diagnostics;
• operational and security logs used for abuse prevention, reliability, and incident review.

Submitted user-created draw content is intended for public display. The immutable content and rules commitments recorded by a successful request remain public even if ElyxS later hides a page or file.

Do not publish another person's personal data without a lawful reason and the right to do so. Never send seed phrases, private keys, identity documents, or financial credentials.

We process data to:

• provide wallet access and show balances, draws, tickets, claims, refunds, and profiles;
• create, review, moderate, organize, and display user-created draw requests and content;
• verify asset identity, ownership, metadata, and supported transfer behavior before submission;
• determine current feature availability and applicable costs before confirmation;
• check uncertain transactions without prompting an unsafe duplicate submission;
• enforce legal acceptance and respond to support requests;
• prevent fraud, spam, sanctions evasion, unsafe content, and other abuse;
• maintain security, reliability, and incident evidence;
• understand aggregate product usage when analytics consent is granted;
• meet legal obligations where they apply.

Where data-protection law requires a legal basis, ElyxS may rely on contract performance, legitimate interests (including security and abuse prevention), consent, or a legal obligation.

ElyxS uses necessary cookies and browser storage for sessions, legal checks, consent, security, drafts, uploads, and short-lived transaction recovery.

Optional preferences, analytics, and diagnostics follow your consent choices. The Cookie Policy lists the categories and examples.

Depending on deployment configuration, ElyxS may use:

• ElyxS application, data-storage, media-delivery, and logging services;
• public Supra L1 RPC and SupraScan data;
• public fungible-asset, NFT, collection, and media sources supplied by asset issuers;
• Plausible CE or PostHog for consent-based analytics;
• Resend for support email delivery.

Issuer-controlled metadata or media can change or disappear even when the asset address and ElyxS snapshot remain available.

When the browser or server requests issuer-controlled metadata or media, that operator may receive normal web-request data such as an IP address and user agent.

ElyxS does not use advertising networks, marketing pixels, social tracking cookies, or ad retargeting in the public beta.

Consent-gated browser diagnostics are sanitized before storage. The self-hosted diagnostic service keeps them for no more than seven days.

PostHog automatic capture is disabled. Session replay is disabled unless a separate privacy review approves it.

We keep data only as long as reasonably needed for the stated purpose, unless security, disputes, compliance, or backup integrity requires longer retention.

Typical treatment:

• public blockchain records: retained by the network, not controlled by ElyxS;
• immutable draw commitments: retained with the chain and relevant audit history;
• active draw content and covers: retained while the draw and public history are supported, subject to moderation and storage policy;
• abandoned drafts and temporary uploads: removed under operational cleanup rules;
• profiles: retained until the profile is deleted or ElyxS fulfills a valid deletion request, subject to backups and abuse records;
• feature-access, availability, and transaction evidence: retained for lifecycle, audit, support, and dispute handling;
• legal acceptance: retained as needed to prove the applicable acceptance;
• support requests: retained while needed to resolve and document the request;
• analytics: retained according to the configured tool and consent state;
• security logs: retained for a limited period unless needed for an investigation.

Depending on your location, you may have rights to access, correct, delete, or export data ElyxS controls; object to or restrict its processing; or withdraw consent.

You can disconnect the wallet, change cookie choices, edit or delete supported profile fields, remove an unfinished local draft, and contact privacy@elyxs.com.

We cannot delete public chain records, immutable commitments, third-party copies, or records we must preserve for legal acceptance, fraud prevention, security, or legal obligations.

Deleting an ElyxS-hosted cover or hiding a draw page does not erase the related on-chain commitment.

ElyxS is not intended for children. You must be at least 18 and meet the legal age required in your jurisdiction.

If you believe a child provided personal data through ElyxS, contact privacy@elyxs.com.

ElyxS infrastructure, maintainers, and providers may process data in different countries.

Where required, ElyxS uses reasonable safeguards for cross-border processing and selects providers with published privacy and security commitments.

ElyxS uses technical and organizational measures intended to protect data it controls. No website, wallet, network, storage provider, or blockchain integration can be guaranteed completely secure.

You remain responsible for wallet security, transaction review, and the content you publish.

ElyxS may update this policy as features, providers, or legal requirements change.

Material updates may enter the required legal bundle and require acceptance before protected actions.

Privacy questions and rights requests can be sent to privacy@elyxs.com.

Provide enough information to identify the relevant ElyxS data, but never send a seed phrase or private key.