# Etheraio / Digidash legal policy pack Version: 2026-10-08-draft-1 Prepared: 8 October 2026 Status: Draft; operator details and legal review pending. ## Public operator details - legalName: Not supplied - businessAddress: Not supplied - supportEmail: Not supplied - privacyEmail: Not supplied - operatingCountry: Not supplied - companyNumber: Not supplied - vatNumber: Not supplied - jurisdiction: Not supplied # Terms of use ## Status and scope Draft prepared 8 October 2026. Etheraio is the platform and research network; Digidash is its proposed marketplace, food and mobility service. The legal operator, address and contact information are pending in the [legal centre](/legal#operator). These release policies explain the prototype and proposed terms; they are not a completed commercial contract or evidence of regulatory approval. Paid services must not launch on the strength of this draft alone. The current release is a centralized test coordinator with signed records, safe bounded jobs, experimental Points, a browser game and source downloads. It is not an independently secured production blockchain, clinical research service, bootable operating system or completed Earth-scale game. Read the relevant product policy before using a feature. ## Accounts and eligibility Active account, supplier and Node participation is intended for adults aged 18 or over who have authority to act for themselves or the business they represent. This is a proposed eligibility rule, not a claim that age verification is implemented. Child-directed account participation needs a separate safeguards review. Do not impersonate another person, share invitations publicly or enter third-party personal information without a lawful reason. Authentication is provided through the hosting service's ChatGPT sign-in. You remain responsible for protecting your own device and local Node keys. ## Acceptable use Use the service lawfully and respect other people's rights. Do not submit stolen or confidential material, patient records, credentials, malicious code, fraudulent payment evidence or misleading scientific claims. Do not harass people, manipulate rewards, evade limits, compromise other Nodes or attempt to obtain account data. No hidden mining, arbitrary remote execution, credential access, harmful chemistry instructions or weapon development is authorized. Fictional game activity does not authorize real-world misconduct. ## Content and intellectual property You retain rights you hold in your submissions. For requested features you give only the permission necessary to store, display, verify and deliver that content as explained in its product policy. You must hold the relevant permissions yourself. A ledger entry does not create ownership, establish novelty, clear a patent or grant a commercial research licence. Separate express agreements are required for commercial research licensing or a broader reuse of private data. Downloaded source files remain governed by their included licences, including the MIT licence where stated. Dependency notices also apply. These website terms do not revoke open-source rights. The company emblem and names must not be used to imply official endorsement of another business. No trademark registration or clearance is represented. ## Availability, safety and responsibility Models can be incomplete or wrong. Do not use outputs as medical advice, clinical evidence or an engineering approval. Production hardware enforcement and independent consensus remain unfinished. Keep your own copies of important research and local saves. Access may be interrupted for maintenance, capacity, security or legal reasons; reasonable notice should be given where possible. No uptime, earnings, scientific discovery or investment return is promised. These terms do not exclude liability that cannot lawfully be excluded, including applicable liability for death or personal injury caused by negligence, fraud or fraudulent misrepresentation. They do not remove mandatory consumer remedies, privacy rights or duties of reasonable care. No blanket waiver of device damage or statutory rights is required to use the prototype. ## Restrictions, changes and disputes Access may be proportionately restricted for credible abuse, security or legal concerns. The operator should explain the reason and provide a review channel unless doing so would compromise security or breach law. Supplier evidence and legitimate disputes must not be dismissed merely because a ledger state says completed. Material future policy changes should be notified before they take effect; new paid rights or obligations require an appropriate agreement and may not be applied retroactively to remove accrued rights. Governing jurisdiction has not been finalized. Any future choice of law must preserve mandatory protections and competent courts available to consumers in their home jurisdiction. No compulsory private arbitration or waiver of class, court or regulatory remedies is imposed by this draft. See [complaints](/legal/complaints). --- # Privacy notice ## Controller and notice status Draft notice for the current implementation. The controller's legal identity and privacy contact are not yet supplied; see [operator details](/legal#operator). This is a material transparency gap, not a completed UK GDPR notice. Controller/processor roles, lawful bases, hosting agreements, international transfers, retention and rights-handling arrangements need confirmation. Do not submit patient data, identity documents, financial credentials or other sensitive material to this prototype. ## Information used by current features - Sign-in supplies the application with an account identifier through trusted hosting headers. It is used to isolate workspaces and authorize requested actions. The application does not ask for your ChatGPT password, browser credentials or wallet private key. - Private workspace records include notes, hypotheses, exclusions, submitted accounting references, funding settings, resource preferences, purchase records and applications. They are scoped to the signed-in account by the application; authorized hosting administration and lawful operational access may still apply. This is not end-to-end encrypted storage. - Public network records include Node names, IDs, platform labels, activity timestamps, signing public keys, signed job results, commitments, ledger transactions and research-asset references. Pool names, descriptions and member Node IDs are public. These identifiers can be linkable to people; pseudonymous does not mean anonymous. - Published product slabs expose listing descriptions, licence text, content hashes, prices and supplied public business/fulfilment details. Product delivery content and drafts are not intended as public catalogue data. Never put a home address, private phone number or secret in a public listing field. - Driver/rider applications currently store the display name, city, country, licensing authority, work and vehicle type, consent flags and provider status references. No document-upload or live screening flow is currently connected. - Sandbox checkouts store the quote, product reference, total, fee, invoice/session reference and verified test settlement status. The application does not collect card numbers. Payment details would be entered on the provider's hosted page only after a configured connection and explicit user action. - Local game saves, browser Node keys and offline assets use device storage as described in [cookies and storage](/cookies). Optional portrait/video input is processed locally by the current game; it is not uploaded or saved with the local game save. - Hosting infrastructure may process IP addresses, request URLs, authentication/security records and error logs to deliver and secure the service. Exact provider settings, locations and log retention have not been verified in this release. ## Purposes and lawful bases to confirm The proposed purposes are providing the features you request, keeping accounts and signatures secure, recording contribution/fulfilment evidence and responding to legal obligations and complaints. The named controller must assess the appropriate basis for each processing activity: requested service performance, a documented legitimate-interest assessment where applicable, specific legal obligations or genuine consent for optional processing. Reading or accepting terms is not blanket consent to all data uses. This draft does not assert that an incomplete commercial contract establishes a lawful basis. There is no advertising or analytics code added by Etheraio in this build. There is no facial identity matching, medical profiling, model training on portraits or solely automated employment/licensing eligibility decision. Any future sensitive-data research, biometric identification, marketing or materially different purpose requires separate review and notices before collection. ## Recipients and transfers Sites/OpenAI and Cloudflare provide hosting/authentication infrastructure. Stripe, BitPay and Certn are selected integration candidates; merchant and screening connections are not active. A user opening an external link is subject to that provider's notice. Future supplier fulfilment, processors and cross-border transfers must be mapped with appropriate contracts and safeguards. No blanket permission to sell personal data is created. Contributions explicitly published to the ledger can be read and copied by anyone. ## Retention and deletion Workspace and ledger records currently persist in the hosted database. Automatic account erasure and a full retention schedule are not implemented. Invitations expire after ten minutes and jobs after two minutes; expired records are pruned on related operations, not by a guaranteed timed deletion service. Game media remains in the local session until replaced, removed or the page closes; device saves, keys and cache remain until you remove them or clear that site's storage. The operator must justify retention periods for each category and implement deletion/archival procedures before production use. Public ledger copies may remain outside the operator's control; publication is not an excuse to ignore lawful erasure, restriction or correction requests. Never publish sensitive personal data to the ledger. Backups, provider logs and legal retention exceptions need a documented policy rather than an invented deletion deadline. ## Your choices and rights Depending on the circumstances, privacy law provides access, correction, erasure, restriction, portability and objection rights, and withdrawal of consent where consent is used. A working operator privacy contact and proportionate identity-checking procedure must be supplied before this notice is finalized. You can independently complain to the [ICO](https://ico.org.uk/make-a-complaint/) or the relevant authority in your country. Rights requests must not require disclosure of Node private keys. Removing local browser storage is not deletion of hosted records. References: [ICO privacy information](https://ico.org.uk/for-organisations/advice-for-small-organisations/getting-started-with-gdpr/data-protection-self-assessment-medium-businesses/what-information-you-must-supply-under-the-gdpr/) and [ICO retention guidance](https://ico.org.uk/for-organisations/uk-gdpr-guidance-and-resources/data-protection-principles/a-guide-to-the-data-protection-principles/storage-limitation/). ## Optional research memory Research prompts are saved privately only when the Remember choice is checked (64 prompts per account, maximum 2000 characters each). They can be cleared on /learning. Raw prompts are never shared or used to train model weights in this release. Querying can retrieve up to five relevant opt-in verified computation lessons with their evidence and applicability conditions. Matching words is not scientific confidence. A Node must separately opt in per job to add a successful deterministic computation to public memory (latest 256 lessons). This does not establish clinical efficacy or generalize beyond the recorded task. Public block evidence remains on the chain after local or account memory is cleared. ## Downloadable local AI starter The optional local AI starter sends chat prompts only to its loopback Ollama runtime and stores question history locally only when requested. Network-learning opt-in downloads public verified evidence without uploading prompts. It can train a small local classifier from verified examples and retrieve evidence for a separately installed model; it does not retrain that model’s weights. Optional live sync occurs only while its window is visible. Model and runtime downloads are separate third-party products with their own published licences and notices. --- # Cookies and device storage ## What this build uses Etheraio does not add advertising, analytics, tracking pixels or marketing cookies. Hosting sign-in and security may use provider-managed cookies or equivalent storage; their exact names, durations and provider inventory still need verification. This draft does not claim all hosting cookies have been audited. Necessary authentication storage supports the sign-in feature you request; optional tracking must not be introduced without a valid consent or applicable exception assessment. ## Optional local features - Clicking Create my Node creates a non-exportable signing key in IndexedDB database etheraio-browser-node-v1, object store device, record identity. It stays in that browser profile; the server receives its public key. Deleting it can remove access to that local Node identity. - Clicking Save game stores the etheraio-game-v1 localStorage record with character settings, progress and bounded experiment results. It does not store the portrait image/video. Load game reads that record only when requested. - Clicking Save game for offline play registers /game-sw.js and caches game assets in etheraio-game-v1. It does not cache account API calls, payment records, Node traffic or portrait media. Network features still need a connection. - Research scenario edits live in page memory. Private funding settings are written to the server only after the explicit signed-in save action, not as a cookie. These optional features begin with a labelled user action, not merely by continuing to browse. No bundled permission for future marketing is implied. You can remove local game progress or offline files through the corresponding browser site-storage controls; clearing all site data also removes the browser Node key and may sign you out. Export important information first. Hosted workspace records are separate. ## Future changes Before adding non-essential analytics or marketing, the operator must assess the applicable rules, explain each purpose and provide the required granular choices, including an easy way to withdraw consent. Essential cookies do not become exempt merely because they are convenient. There is no unnecessary Accept all banner in this release because no optional tracking integration has been added. [ICO storage and access guidance](https://ico.org.uk/for-organisations/direct-marketing-and-privacy-and-electronic-communications/guide-to-pecr/cookies-and-similar-technologies/). ## Optional mining web app Pressing Install may register a service worker scoped to /mining and cache only the public mining shell, scripts and artwork (etheraio-mining-shell-v1). It does not cache API, account, authentication or reward records and never runs computation. Contributions require a fresh online session. Uninstalling a web app may not erase its browser signing key; manage site data in browser settings. --- # Node and pool terms ## Explicit participation Background contribution starts OFF. Creating an identity, downloading software, joining a pool or visiting a page does not authorize continuous mining. The browser client connects its device identity automatically after an explicit Start and runs bounded allowlisted jobs for up to 10 minutes, with at most one job per minute. Stop, hiding or closing the app ends that session. The desktop source client remains manual. Stop controls and closing the client prevent further requested work. A submitted result or already-published block cannot be recalled by emergency stop. The OFF, Browsing, Gaming, Normal, Turbo and custom profiles record requested limits. Gaming requests 8% of available CPU with GPU OFF and never permits a policy allocation above 10% of the available user-visible compute budget. Actual game performance impact cannot be guaranteed. Native CPU/GPU quotas and reliable temperature, battery, foreground-app and performance enforcement remain incomplete; native background work stays unavailable. Browser sessions use low duty cycles and small fixed buffers; percentages describe requested policy budgets, not measured OS quotas. Optional WebGPU is OFF until separately enabled in Normal, Turbo or Custom, and is always OFF in Gaming and Browsing. No device or future GPU compatibility is guaranteed. Do not treat a saved ceiling as measured enforcement. ## Local costs and keys You choose whether to use your own electricity, hardware and bandwidth. No electricity reimbursement, employment, earnings or payment promise is made. Use equipment you are permitted to use and inspect the published software. Do not run on employer, school, shared or third-party devices without authorization. Keep private keys and invitations private; no pool operator receives your key or remote control of your device. Custom servers are independent destinations whose operator and terms you should assess before connecting. ## Verification and rewards Only correctly signed, reproducible eligible results can receive test rewards. Failed, stale, replayed or excluded work receives none. Verification confirms the specific deterministic computation; it does not establish scientific truth or clinical efficacy. The hosted coordinator currently controls admission, sequencing and state. No independent decentralized consensus is claimed. The configured initial work reward is 22 closed-loop test Points with separate blockchain test units. Halving and a trusted hardware-throughput adjustment can reduce rewards. The throughput feed is not connected to a reliable production hardware collector. Rewards may be zero and do not create a cash claim. Protocol changes need clear prospective notice; no promised financial value is attached to these experiments. ## Pools Pool membership is optional. The pool's fixed disclosed share, currently limited to 0–10%, applies to blockchain test-unit rewards according to the recorded membership/job snapshot; Points are credited separately to the contributor. Joining requires confirmation of that exact share. Leaving stops participation in future pooled jobs; an already-issued job retains its signed snapshot. A pool is not hash-power rental, an investment or a custody arrangement. A pool owner cannot promise returns on behalf of Etheraio or change the recorded fee silently. ## Publication and conduct Node names, IDs, public keys, contribution evidence and pool membership may be public. Do not include personal secrets in names or results. Do not fake telemetry, invent provider signatures, submit other companies' work as yours or tamper with rewards. Resource consent is distinct from agreeing to website terms and must remain revocable for future work. Open-source licences continue to govern the code. --- # Research contribution terms ## Research only Etheraio is for safe in-silico modelling, reproducibility and research hypotheses. Current jobs are bounded descriptive statistics, fixed benchmarks and procedural design searches. They do not discover approved medicines, conduct clinical trials, establish safety or replace a qualified scientist, engineer or clinician. Medicines are prioritized only when an eligible reviewed task exists; no fabricated discoveries or preloaded medicine results are presented as new work. Do not submit identifiable patient data, clinical samples, private company results, trade secrets, unsafe wet-lab instructions, controlled-drug synthesis chains, weapon designs or executable remote workloads. Public/synthetic non-sensitive data and allowlisted modelling recipes are the permitted input scope. Recreational-drug requests do not create an exception to these restrictions. ## Eligibility, provenance and novelty Supply accurate source, licence, authorship and permission references. Other companies' known/excluded candidates are removed from the eligible pool when recorded. This is a recorded exclusion mechanism, not a comprehensive patent search or proof that all outside research has been identified. Independently review novelty, permissions, conflicts and scientific validity before any commercial use. Signed timestamps and hashes show recorded provenance, not intellectual-property clearance. Keep hypotheses, simulations, replications and independently validated findings distinct. Clearly state assumptions, units, limitations and unsuccessful results. A deterministic result verifies a computation, not a real-world effect. Concept spacecraft, medicines and engineering outputs must remain labelled unvalidated unless supported by appropriate external evidence and review. ## Rights and reuse You retain rights you actually hold. Submitting a private hypothesis permits storage, processing and display within your requested workspace. Publishing a signed result or asset permits verification, reproduction of its recorded computation and display of its contribution record; public readers may copy published records. Publication does not automatically transfer your patent, copyright or confidential know-how to Etheraio. Commercial licensing, sale of research, allocation of proceeds, authorship and any revenue rights require a separate express agreement identifying the actual parties, scope, permitted uses, evidence and payment obligations. Node rewards or Points alone are not such an agreement. Do not submit data under terms that conflict with these requested uses. No platform ownership claim can authorize taking another company's work. ## Accounting and safety Unsold ideas and unvalidated results are not settled sales or liquid funds. Funding calculations use documented settled receipts and matching-period deductions; they are not company valuations. No clinical, aerospace, marine or electrical certification follows from a game test. Stop a task if its inputs exceed the permitted safe scope and request review. The operator must implement qualified review, appropriate approvals and separate contracts before expanding to regulated research or commercial licensing. ## Optional research memory Research prompts are saved privately only when the Remember choice is checked (64 prompts per account, maximum 2000 characters each). They can be cleared on /learning. Raw prompts are never shared or used to train model weights in this release. Querying can retrieve up to five relevant opt-in verified computation lessons with their evidence and applicability conditions. Matching words is not scientific confidence. A Node must separately opt in per job to add a successful deterministic computation to public memory (latest 256 lessons). This does not establish clinical efficacy or generalize beyond the recorded task. Public block evidence remains on the chain after local or account memory is cleared. --- # Etheraio Points terms ## Current closed-loop test rewards Points are experimental platform rewards, separate from transferable crypto, fiat, blockchain test units and local game credits. They have no promised monetary value in this release. Points sales, public market pricing, cash redemption, peer-to-peer transfers, crypto conversion and holder income rights are disabled. No interest, dividend, ownership stake, deposit protection or guaranteed appreciation is offered. Qualifying verified work can earn Points under the current reward policy. Account balances start at zero. Spending reserves or uses eligible Points for a supported test service. Verified fulfilment can credit a supplier's internal Points balance; refunds of eligible held Points return them to the buyer. Redeemed service Points may enter the work-reward treasury and later recirculate. Moving Points between these states is not a cash supplier payout or proof of liquidity. ## Proposed research funding calculation The planning calculator deducts recorded costs, refunds, paid taxes, unpaid tax reserves, matching-period annual business costs and committed liabilities from settled research sales. Available funding is floored at zero; it is multiplied by your proposed loyalty allocation and divided by total issued Points, including held balances and the reward treasury. Zero supply gives N/A. This is a scenario, not an enforceable price, a reserve audit or a claim against research income. Saved accounts are owner-entered; no bank connection verifies liquidity. Personal expenses are not automatically allowable deductions, and taxes/costs must not be counted twice. Taxes and individual reporting need appropriate assessment. Calling this a loyalty share or utility token cannot decide the legal outcome. [FCA perimeter guidance](https://handbook.fca.org.uk/handbook/perg18/perg18s1). ## Fair treatment and future changes Do not manipulate balances, exploit duplicate rewards or claim real-money value for test Points. Disputed contributions or fulfilment should be reviewed on evidence. This draft does not permit arbitrary confiscation, removal of mandatory consumer remedies or retroactive conversion into an investment. Any future expiry, fees, purchased balances, cash rights or transferable token must be explained and assessed before introduction; no such rights arise merely because this page changes. Purchased-value protections would need separate terms and implementation. A wide third-party marketplace also needs an appropriate payments/e-money analysis. Closed-loop terminology alone does not establish a limited-network exclusion. [FCA limited-network guidance](https://www.fca.org.uk/firms/limited-network-exclusion). --- # Digidash buyer terms ## Prototype status and parties Digidash is the supplier marketplace name. Physical goods, digital goods, game products and food have category scaffolding. The current implementation supports test Points records and sandbox payment preparation; no real-money purchase, real delivery commitment, licensed taxi booking or cash payout is created by a test record. The legal platform operator and seller-contract model must be finalized before a commercial launch. A future order must identify the actual seller, its address/contact, the platform's role, product description, licence where applicable, delivery area/time, full tax-inclusive consumer price and charges before commitment. A slab mint records a signed listing; it does not certify authenticity, safety, stock or title. Do not assume Etheraio is the seller or that disclaiming an intermediary role removes obligations it actually performs. ## Order steps and fulfilment Review the description, seller, licence, quantity, total and fulfilment conditions, and correct errors before confirming. No paid subscription or optional extra may be added without express choice. A future paid order needs an unambiguous payment action and a durable order/terms confirmation. Neither a payment callback nor a supplier's unsupported status alone establishes delivery. Current test Points purchases can hold credits pending recorded fulfilment. Digital text delivery checks the content hash; physical test fulfilment progresses through accepted, shipped and delivered states with references. Buyer confirmation is a prototype evidence step, not independent inspection or a waiver of later defects. Chain records do not overrule a valid consumer dispute. Read [returns and cancellation](/legal/refunds). ## Cash/card and crypto routes Stripe GBP/card and BitPay crypto integration code is sandbox-only. Physical cash collection is not implemented. No real account is connected. A disclosed platform service fee is shown separately and applies consistently across routes; card processing costs are absorbed by the merchant. UK consumer card surcharges must not be disguised as service fees. A crypto wallet/provider may show network fees before you approve a transfer. [UK surcharge rules](https://www.gov.uk/government/news/card-surcharge-ban-means-no-more-nasty-surprises-for-shoppers). Before a live crypto order, terms must identify the invoice currency, accepted asset/network, expiry, exact settlement, refund handling and who bears applicable network costs. A crypto transfer is not generally reversible, but that does not remove statutory rights. Real refunds, disputes, VAT, supplier settlement and payment reconciliation need implementation; a sandbox status does not deliver a real product or mint Points. ## Restricted products and services No illegal, counterfeit, stolen or unsafe goods, controlled drugs, weapons, financial investments, gambling or unauthorized medical claims may be listed. Products requiring licences or age checks must remain unavailable until those controls exist. Food and mobility require their own verified operational arrangements. Do not make allergy, emergency travel or medical decisions based on prototype listings. --- # Digidash supplier terms ## Signup and authority You must be authorized to represent the supplier and have rights to sell each listed product. Give accurate public trading/contact details and distinguish your private account data. Current signup and product minting are test features; they do not constitute approval of a merchant, licence or live supplier contract. The operator's identity and commercial fee/settlement agreement remain pending. ## Listing and delivery duties Describe the actual product, condition, specification, price, currency, stock, delivery area, times, returns and support. Digital licences must identify permitted use, restrictions and compatibility. Hold content, brand and distribution rights; a blockchain hash does not grant them. Do not imply an affiliation with another company. Keep claims accurate and correct outdated listings. Customer statutory rights take priority over conflicting supplier text. In a dropshipping model the identified seller remains responsible for its consumer obligations; outsourcing fulfilment does not remove them. Verify suppliers, product safety, required registrations, labelling, insurance and lawful imports. Keep customer information confidential and use it only for agreed lawful fulfilment. No live buyer addresses are currently distributed by this prototype. ## Food Food listings need the relevant business registration, hygienic preparation, accurate allergen information, safe storage/transport and a clear fulfilment area. Prototype fields are not food-safety verification. Allergy information must be available at the appropriate order and delivery stages; substitutions must not silently change allergen risk. No food sale or delivery should launch without operational checks. [Food Standards Agency guidance](https://www.food.gov.uk/business-guidance/allergen-guidance-for-food-businesses). ## Minting, orders and settlement An authorized producer Node signs the manifest; the slab is a provenance record, not an NFT ownership promise. Test Points orders hold the buyer's credits until eligible evidence and confirmation allow settlement. Do not fabricate shipment, delivery or buyer acceptance. Refunds of held credits follow the implemented state rules. This escrow-like internal test state is not a regulated safeguarded-money account. No cash/crypto supplier payout, tax withholding service or guaranteed payment timetable is active. Before live trading, a separate agreement must specify the provider platform arrangement, merchant verification, fees, settlement timing, fulfilment checks, reserves, disputes, refunds, chargebacks, insolvency treatment and taxes. Charges must not be invented after an order. Do not advertise real payment availability before these arrangements are connected. ## Enforcement and exit Fraudulent, unsafe or infringing listings may be restricted on proportionate grounds with reasons and a review channel where lawful. An exit process must address open orders, valid refunds and owed sums rather than forfeiting them arbitrarily. Supplier confidentiality and necessary order records should be preserved appropriately. Applicable mandatory marketplace and trading obligations cannot be waived by selecting Accept terms. --- # Returns and cancellation ## Current test release No real payments are accepted through the current disconnected sandbox integrations. Test Points and sandbox settlement records do not represent paid consumer orders. The implemented test refund can return eligible held Points before payout; post-settlement disputes and real cash/crypto refunds require operational handling that is not yet implemented. These limitations are not a future no-refunds policy. ## Consumer protections for a future UK sale Mandatory rights remain intact. Goods must meet the applicable description, quality and fitness requirements. Faulty goods and defective digital content/services have statutory remedies; seller guarantees do not replace them. An order marked delivered or confirmed does not end valid rights. [Government returns guidance](https://www.gov.uk/accepting-returns-and-giving-refunds). For eligible distance-sold goods, a consumer can notify cancellation within 14 days after receipt, then normally has 14 days to return them. Refunds must follow the applicable deadline and include standard outward delivery where required. Responsibility for return costs and any lawful handling deduction must be disclosed and assessed; no automatic administrative penalty applies. Perishable, personalized and certain unsealed goods can have exceptions, while defect rights remain. Service and digital-content cancellation rules differ. Immediate paid digital delivery requires separate express consent and acknowledgment of any lawful loss of cancellation rights, plus durable confirmation. A generic terms tick or clicking Download is not a universal waiver. This release does not implement that paid-content waiver, so it must not be asserted against a buyer. [Government digital-selling guidance](https://www.gov.uk/online-and-distance-selling-for-businesses/online-selling). ## Reporting a problem Retain the order, seller, product, date, amount/currency and a brief description or evidence. Do not send card numbers, passwords, private keys or unnecessary medical details. The seller and operator need verified contact routes before paid launch. The draft contact fields are in the [legal centre](/legal#operator); no functioning support inbox is currently represented. Food-safety or immediate personal-safety issues should be raised with the relevant authority or emergency service as appropriate. No dispute is rejected solely because a crypto payment is irreversible or an on-chain state cannot be edited. A future crypto refund method, valuation and network-cost policy must be stated before payment and preserve mandatory remedies. Provider refunds and chargebacks depend on the actual payment arrangement; this release makes no unsupported promise that they are connected. ## Model cancellation notice Save this wording and send it to the identified seller's supplied cancellation contact when that service launches: - To: [Seller legal name, postal address and cancellation email supplied with the order] - I give notice that I cancel my contract for: [goods / service / digital content description] - Ordered on / received on: [dates] - Order reference: [reference] - Consumer name and contact/address: [details needed to identify the order] - Date of notice: [date] - Signature: [only if submitted on paper] The model form is optional; an unambiguous valid cancellation notice must not be refused merely because this form was not used. It is not a submission form or a promise of a connected refund service. --- # Drivers, riders and vetting ## No live dispatch Digidash currently records pending applications and screening/payment states. Taxi dispatch and real delivery allocation are disabled. Certn is a selected screening candidate, not a connected service, licensed operator, endorsement or guarantee of suitability. Passing a test status does not authorize carrying passengers or working as a courier. ## Separate screening choices Applicants must receive the actual screening provider's identity, privacy notice, check scope, lawful basis and fee quote before proceeding. A generic signup checkbox does not authorize undisclosed criminal-record checks or sensitive-data processing. Identity and screening documents should go directly through an appropriately secured provider workflow, not public product or research fields. Additional criminal-offence/special-category conditions and proportionality assessments need review. The intended fee payer is the driver/rider applicant. No fee is charged in the current release. The exact provider amount, applicable taxes, cancellation/refund treatment and any repeated check must be disclosed and specifically accepted before payment. No surprise fee, blanket future charge or automatic deduction from earnings is authorized. Any employment/recruitment restrictions on charging applicants must be assessed for the actual arrangement. ## Licensing and worker arrangements A live mobility service needs the correct operator arrangement, current driver/vehicle licences, insurance and local approvals. England/Wales PHV bookings require appropriate licensed operations; Scotland and Northern Ireland have different rules. Screening alone is insufficient. [Government operator-licensing guidance](https://www.gov.uk/operator-licence-private-hire-vehicle). The actual engagement may have employment, worker, tax, minimum-pay, working-time and health/safety implications. Calling someone an independent contractor does not decide their legal status. Pay, deductions, service area, cancellation, insurance, incident handling and suspension rights require a separate reviewed agreement with the actual operator before work starts. ## Fair review and safety Applicants should receive an appropriate explanation and human review of disputed results or adverse eligibility decisions. A system flag must not be treated as conclusive evidence of wrongdoing. No automatic high-impact eligibility decision or live passenger allocation is represented in this release. False licence, insurance, identity or fee evidence is prohibited. Do not use Digidash for emergency transport; urgent safety concerns require the appropriate emergency service. --- # Game and avatar terms ## Experimental fictional world Etheraio is a playable browser prototype with driving, sports practice, life activities and a fictional vault mission. It is not a finished GTA-scale or photorealistic AAA production. Earth/planet addressing and an Unreal Engine source foundation do not mean every planet or Earth location is fully built. Availability and graphical performance depend on hardware and browser capabilities. Game credits, fictional offences and experiment scores do not represent money, real licences or real-world permissions. No wagering, paid loot-box system or cash prizes are included. Fictional heists must remain entertainment without real robbery instructions. The release contains crime-themed content and is intended for adult prototype participation; no independent age rating or implemented age-verification system is claimed. ## Characters, portraits and media Custom characters require no scan. An optional image or local video frame can texture a portrait; this is not a validated 3D face scan or identity check. Use your own likeness, or obtain lawful permission from anyone depicted and the media rights holder. Do not impersonate others, use intimate material or submit a child's image. The current game keeps media in the local page session, does not upload it, train on it or include it in the Save game record. Replace/remove it or close the page to stop use. No biometric recognition is performed. Any future cloud avatar generation, public sharing, persistent media storage or biometric identification needs a separate clear opt-in, retention rules and rights assessment before use. No perpetual commercial licence to your likeness is created by these draft terms. ## Resources and contributions Rendering starts when Enter Etheraio is selected. The game pauses when hidden, with manual pause controls and quality choices. Rendering is distinct from Node contribution; playing does not turn on mining. Nodes can publish reproducible bounded world recipes after eligible reviewed medicine and other science tasks. A game experiment alone does not earn rewards or establish a scientific discovery. Read [Node terms](/legal/nodes) and [research terms](/legal/research). ## Saves and licences Local game saves and offline files are optional; browser cleanup can remove them. You control whether to save. No cloud backup or cross-device transfer is promised. Source downloads are governed by their included open-source and dependency licences. Third-party names or publicly sourced vehicle/physics data do not imply brand endorsement, rights to copy a vehicle's protected design or official game licensing. Original game models and simulations must retain the relevant attribution and limitations. --- # Complaints and rights requests ## Contact route pending The operator's public support and privacy contacts must be added to the [legal centre](/legal#operator). No connected helpdesk, mailbox or service-level promise has been established by this release. This is an outstanding launch requirement, not a requirement that customers give up a complaint. For a future purchase the identified seller must also provide its own contact and cancellation route. ## Information to include State the feature or order, reference, relevant dates, a short description, the remedy you seek and a contact for the reply. Provide only necessary evidence. Never disclose private keys, passwords, full card details, patient data or identity documents in public ledger, listing or research fields. Identity verification for private records should be proportionate and handled through a secure channel. ## Proposed handling process The operator should acknowledge the request, preserve relevant evidence, identify the responsible party, give a reasoned response and an appropriate escalation/human-review route. Published response targets, trained handlers, a dispute log and lawful data-request deadlines need operational setup. Evidence of fraud, infringement, unsafe goods or contested screening should be reviewed fairly; a minted slab, automated flag or supplier delivery assertion is not conclusive. Urgent vulnerabilities should use a verified security contact once supplied. Do not exploit another person's account or publish private data to prove a flaw. Immediate danger should be reported to the appropriate emergency service; the website is not an emergency channel. ## External remedies These policies do not require you to exhaust an internal process before exercising a right that law gives you. Privacy complaints may be made to the [ICO](https://ico.org.uk/make-a-complaint/) or your relevant supervisory authority. Consumer advice is available through [Citizens Advice](https://www.citizensadvice.org.uk/consumer/). Regulators, licensing authorities, courts and payment-provider processes remain available where applicable. No membership of an ombudsman or ADR scheme is claimed; applicable ADR information must be supplied when required and the actual scheme is known. ---