RevLauncher Privacy Notice

1. Who we are and how to contact us

EggBit Games LLC, an Iowa limited liability company, operates RevLauncher. RevLauncher is the platform name, not a separate legal entity or a registered trade name represented by this notice.

Contact us about privacy at support@eggbitgames.com or EggBit Games LLC, 1707 S Redtail Ave, West Des Moines, IA 50265, United States. Please identify your request as a privacy request. Do not send passwords, full payment-card numbers, security codes or identity documents in an ordinary email. We can arrange an appropriate way to verify and respond to a request when necessary.

This notice covers our website, its related launch-interest form, accounts, marketplace transactions, developer and creator participation, and related support. Initial customer purchases are US-only, in reviewed and enabled US jurisdictions. International developer and creator eligibility is separate; a purchase-country restriction does not mean that we process personal information only about US residents.

The service is intended for adults aged 18 and older. This is not a claim that every visitor’s age has been verified. Contact us if you believe a child has provided personal information through the service so we can assess and address it appropriately.

2. Information we process and its sources

We receive information from you, your organization and other participants, our service providers, and your interactions with the service. The information involved depends on the features you use:

• Launch-interest information: if you submit the website’s launch-interest form, we receive your name, email address and selected developer or creator interest, and record the signup time. The form requires a separate choice to receive launch emails. Joining this list does not create a marketplace account or establish payout eligibility. Form input may also be held temporarily to redisplay a form after a validation problem.
• Account and organization information: identifiers, names, email addresses, organization names and countries, membership and permissions, profile details, account status, and agreement versions and acceptance times. Adult self-declarations record the declaration version, time and account or checkout identity; they do not collect a birth date or identity document or establish verified age. Our identity provider handles marketplace sign-in; website administration may use separate local administrator credentials. Our services also maintain local account and session records.
• Purchases and earnings: games and key allocations, order identifiers, amounts, taxes, fee and earnings allocations, creator-code attribution, purchase access and delivery records, payment status, refunds, disputes, and relevant acceptance evidence. Guest checkout also creates a local customer record associated with the email address; guest information is not held only by Stripe.
• Payment and verification information: Stripe processes payment details supplied through its checkout and connected-account services. Our application receives provider identifiers, payment and verification status, billing country, state and postal code, card-issuing country, and tax and eligibility results. Where available, payment records can also retain payment outcomes, fraud-risk levels and scores, review references, 3-D Secure authentication results and flow, wallet type, and observation times. We keep related refund, dispute and fraud-review event information and evidence needed to investigate the transaction. These observations do not prove that an external game key was activated or that every payment was authenticated in the same way. Our hosted-checkout application flow does not collect full payment-card numbers or card security codes. Information available through provider systems is governed by the access and services involved.
• Developer and creator activity: submitted games, keys and listings; public profiles, creator codes, promotional URLs and media; evidence of ownership or promotion; review decisions, reputation and performance information; and payout account references and readiness information. Some information is supplied by another member of your organization or a participant reviewing or supporting an interaction.
• Support and communications: messages, names and email addresses, related orders and keys, decisions, internal case notes, email delivery status, recipient and authorized-response evidence, and the times and people associated with support, financial reviews and payout requests. Delivery evidence records a provider or service observation; it does not necessarily establish that a person read an email. Send private account or privacy requests to our contact address, not to a game-key support discussion intended for the relevant developer.
• Technical information: session and security identifiers, network addresses, request and error information, browser interactions needed to operate the service, and stored preferences. Providers serving sign-in, payments or remote media may receive technical information directly from your browser.

At a glance by account type

• Customers, including guests: we process checkout identity, purchases, key access and reveal history, payment and fraud-review information, refunds and support. The relevant developer can receive information needed to resolve a game-key issue; a guest purchase also creates a local customer record.
• Developers: we process organization and member details, games and key inventory, transaction and earnings allocations, payout readiness, and support and review evidence. Published listings and submitted public media are visible to others; financial and support records have separate authorized access.
• Content creators: we process profile and channel information, creator codes, promotional proof, attribution, earnings and payout readiness. Public profiles and rankings can reveal identity and relative performance; the public showcase does not display the underlying sales or earnings totals.

If you use more than one account role, the information relevant to each role applies. These highlights do not replace the details and rights described below.

3. Why we use information

We use information to operate accounts and organization access; offer, authorize and deliver purchases; calculate attribution, taxes, fees and earnings; verify payout readiness; provide support and transactional messages; moderate submitted content; detect misuse and protect the service; investigate errors and disputes; retain evidence of accepted arrangements; and meet applicable tax, accounting and other legal obligations.

For the launch-interest list, we use the details and separate consent you provide to maintain the list and provide the launch updates you request when available. You can withdraw that consent using the contact details in section 1. Joining the list is optional and does not give blanket consent for unrelated marketing.

Providing information needed for an account, order, verification or support request is necessary to carry out that activity. If it is missing or cannot be verified, the activity may be unavailable or delayed. Optional profile content and promotional submissions are your choice, subject to the requirements of the feature you choose to use.

Where applicable law requires a legal basis, we rely on performance of an agreement or steps requested before it for relevant account and transaction processing; compliance with applicable legal obligations for required records and reporting; and legitimate interests, where permitted and balanced against individual rights, for service security, abuse prevention, business-contact administration and dispute handling. Where consent is required for a particular optional use, we must obtain it separately and provide a way to withdraw it. Accepting commercial terms is not blanket privacy consent. These bases are not interchangeable permissions to collect any information.

Automated country and payment-eligibility checks can prevent a checkout, and content-safety checks can reject submitted material. Payment providers can apply their own fraud and authentication checks. Contact us if you believe a restriction is incorrect or want to request review. Where applicable law gives you safeguards for a decision made solely by automated processing that has a legal or similarly significant effect, you can request information about the decision, put forward your view and relevant information, obtain human intervention and challenge the decision through our contact address. A provider’s decision or risk observation is not proof of misconduct. These rights are not limited to any discretionary review we offer.

4. Who receives information

Access depends on the activity and the recipient’s role:

• Identity, hosting, storage and communications providers process account, session, application and message information needed to operate the service. Content-moderation providers can process submitted text and image references.
• Support email providers and authorized team members handle messages sent to support@eggbitgames.com for support, privacy requests and incident response.
• Stripe supports checkout, payments, tax calculations and connected-account verification and payouts. Its own privacy information also describes processing for its services and obligations.
• Authorized organization members and relevant developers or creators receive information needed for the transactions, campaigns, administration or support available to them. A developer handling a game-key issue can receive the customer’s relevant identity, order and support details, including case notes visible to developer support. Creator attribution and participant reports can expose activity associated with their respective transactions or campaigns.
• Public profiles, listings and published promotional content can be viewed by others. The public creator showcase displays ranking position, display name and creator code, with an identifier used to link to the creator. Sales, revenue, earnings, reputation scores and other underlying ranking statistics are not included in that public showcase response. Rankings are derived from activity and can reveal relative performance, even when exact amounts are private. Authorized participant and administrator reports remain separate. Remote media providers, including YouTube/Google and Steam/Valve where used, receive requests when their resources load or their links are opened. Public copies and information already received by another person may not be under our control.
• We may disclose information when reasonably needed to comply with applicable law or valid legal process, protect rights and safety, or establish, exercise or defend legal claims, subject to applicable restrictions.

Provider and participant roles depend on the service and applicable law; not every recipient acts solely as our processor. Do not include confidential or unnecessary personal information in public submissions. A developer’s use of information outside RevLauncher’s instructions or service can also be subject to that developer’s own privacy obligations.

5. Cookies, browser storage and external media

Our application uses cookies for sign-in state and authenticated sessions. Browser storage also remembers the display theme and coordinates sign-in or sign-out state between tabs. Session duration depends on the identity session and renewal; these are not all fixed-duration cookies.

The related website also uses a session cookie for form security, temporary form state and administrator sign-in.

RevLauncher uses YouTube embedded-player services. In the storefront’s main gallery, the privacy-enhanced player loads when its video slide appears, before you press play; the video does not autoplay. Loading the player connects your browser to YouTube/Google and can send technical information needed to serve the player and apply its security and content rules. Privacy-enhanced mode does not mean that no information is sent. YouTube description and developer-proof players instead require you to choose to load that video. That choice is not stored as a site-wide preference; removing the video stops that embedded player but does not undo information already sent. See the Google Privacy Policy and YouTube Terms of Service for those services.

Opening an external link lets the destination receive the resulting request. Other remote images and supported direct videos can load as part of a page, without the YouTube load choice. Providers can serve their own content and use cookies or similar device storage under their policies and applicable law. Blocking browser storage or cookies can prevent sign-in and other features from working. A notice of this behavior does not replace consent or another choice where one is legally required.

The application reviewed for this notice has no advertising or audience-analytics integration identified. This is not a promise that payment, identity, hosting or media providers perform no telemetry or use no storage of their own. New advertising, analytics or other optional tracking requires a new assessment and any necessary notices, choices and consent before enablement.

6. Retention and security

We retain information according to its purpose and applicable requirements: account and membership records while needed to administer participation; order, payment, tax and agreement evidence for relevant reporting, reconciliation, claims and recordkeeping obligations; support and security records while needed to resolve issues and protect the service; and public submissions while they remain part of the service or are needed for an associated review or dispute. Applicable legal holds can require longer retention of particular records, not unrestricted retention of all information.

Launch-interest details are used for the requested updates until you withdraw consent or that purpose ends, subject to lawful retention of necessary consent and request-handling evidence. Withdrawal requests are handled through our contact address.

Account deactivation does not automatically erase historical purchases, earnings, accepted terms or support records. An expired session or access link does not mean every related record has been deleted. Backups, delivery records and provider systems have their own retention and deletion handling that must be included when assessing a request. We assess deletion requests against applicable rights and lawful retention requirements and explain relevant limitations.

We use safeguards appropriate to the service, including access restrictions and protected sign-in and session handling. No service or transmission method is completely secure. Keep access links and account credentials private, and tell us promptly about suspected unauthorized access.

7. International processing

EggBit Games LLC is based in the United States. Personal information may be processed in the United States and other countries where our service providers operate, which may differ from your country.

Where international-transfer requirements apply, we must use a permitted mechanism for the particular transfer, such as an applicable adequacy decision or approved contractual safeguards, and complete any required assessment. Standard provider data-processing terms can contain standard contractual clauses or UK transfer provisions; their availability does not establish that every transfer is covered or that our assessment and implementation duties have been completed.

Contact support@eggbitgames.com to ask about processing destinations and obtain information or a copy of applicable safeguards, subject to necessary redaction of confidential or security-sensitive information. Agreement to this notice is not a substitute for required safeguards.

8. Your choices and privacy requests

Contact us using section 1 to request access to, correction of, or deletion of personal information, or to ask about other privacy choices. Depending on the law that applies, rights may also include a portable copy, restrictions on or objections to certain processing, withdrawal of consent, an opt-out of certain uses, appeal of a decision, or a complaint to a supervisory authority. Rights, exceptions, verification requirements and response periods differ; we do not limit a mandatory right through the commercial terms or this notice.

Where UK GDPR applies, an access request generally requires a response without undue delay and within one month, subject to the law’s identity-check, clarification and extension rules. We will explain an applicable extension and its reasons as required. Other applicable laws can impose different periods. A complaint acknowledgement period is not permission to postpone work on a rights request.

Right to object: where applicable law provides this right, you can object to processing based on legitimate interests and to direct marketing. Contact us using section 1 and identify the processing you object to. If UK data-protection law applies to you, you can also complain to the Information Commissioner’s Office; contacting us first does not remove that right.

We may request proportionate information to verify identity or an authorized representative’s authority and protect other people before disclosing or changing records. We will explain a decision where required, including applicable reasons for refusing or limiting a request and available review or appeal routes. Organization membership does not entitle a requester to every other member’s personal information. We do not require acceptance of a new commercial agreement as a condition of submitting a privacy request.

Privacy complaints and appeals: you can complain about our handling of your personal information or ask us to review a privacy-request decision by email or post using section 1. No particular form or legal wording is required. Where the UK controller-complaint duty applies, we must acknowledge a complaint within 30 days, take appropriate steps to investigate and respond, and communicate the outcome without undue delay. Where another applicable law gives you an appeal right, we will apply its response period and explain the outcome and any required further complaint route. This does not replace your right to contact a competent regulator or seek another remedy available under applicable law.

You can choose not to submit optional public content, not to load a click-to-load description or developer-proof video, or not to proceed to an external provider. Gallery players load as described in section 5. Essential purchase, security and legal communications are different from optional marketing; a privacy request or account closure may not end communications needed to resolve an existing transaction or obligation.

9. Changes to this notice

The publication or revision date appears with this notice. Material changes will receive any notice or choice required by applicable law. A revised notice does not retroactively provide consent or erase an existing right. This informational notice does not itself amend a role agreement or authorize a new processing purpose.