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, 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:

• 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. Microsoft identity services handle the sign-in flow; our service also maintains 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. 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, and email delivery status. 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.

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.

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.

4. Who receives information

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

• Microsoft/Azure services support identity, hosting and storage, session and application data, email delivery, message queues and content moderation. Submitted text and image references can be processed by the content-moderation service.
• Google Workspace handles our support email. Messages sent to support@eggbitgames.com are distributed through a group alias to the three EggBit Games cofounders who handle support, privacy requests and incident response. Copies can exist in the group or recipient mailboxes depending on the configured email service.
• 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.

YouTube players in the storefront gallery and developer proof views load only after you 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. 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 choice. Blocking browser storage or cookies can prevent sign-in and other features from working.

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.

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, with primary application hosting in Azure East US 2. Use of our service by an international participant can involve processing in the United States and in locations used by relevant providers. The application hosting region is not a guarantee that identity, payment, email, backups or other provider operations all occur there. A participant’s country and a provider’s service configuration matter; US-only customer sales are not a data-residency guarantee.

Our Microsoft/Azure, Google Workspace and Stripe subscriptions use the providers’ standard business terms. Their data-processing terms describe the protections and transfer arrangements for the services and processing they cover:

• Microsoft/Azure: the Microsoft Products and Services Data Protection Addendum describes contractual protections for covered services, including international transfers. Primary application hosting is in the United States; the selected service and its support, backup and subprocessor arrangements can involve other locations.
• Google Workspace: the Cloud Data Processing Addendum permits processing in countries where Google and its subprocessors maintain facilities, subject to applicable location and transfer commitments. Google’s Workspace subprocessor directory identifies relevant entities, activities and locations. Our support email is not represented as confined to Azure or to a single country.
• Stripe: its Data Processing Agreement describes transfers to Stripe, LLC in the United States and global processing by affiliates and subprocessors. Its Data Transfers Addendum provides standard contractual clauses and UK transfer provisions for transfers within their scope. Stripe can act as a processor or as a controller, depending on the activity.

Where applicable law requires safeguards for an international transfer, the applicable provider terms describe their contractual clauses or other recognized transfer arrangements and the conditions for using them. Standard subscriptions do not remove our own obligations to assess a transfer, apply required settings or provide additional protections where needed. Contact support@eggbitgames.com to ask about relevant 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 used as 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.

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.

You can choose not to submit optional public content, not to load an embedded video, or not to proceed to an external provider. 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.