Privacy
Updated November 15, 2026 · Notice version 2026-11-15
Embercast is an independent game developed by Berkeley Malagon and operated by Malagon Legacy, LLC. This notice covers our game, websites and related services. Contact play@embercastgame.com about privacy or your data.
Embercast is in alpha. Usage measurement, service monitoring and debugging help us find failures, reproduce bugs, tune gameplay and improve performance. The routine diagnostics below are part of operating the alpha; extra diagnostic reports and advertising cookies have separate choices.
Game emails
If you give us your email address on a signup form, we use Resend to email your download links, and Berkeley may email you about Embercast development, new builds, playtests, launch announcements, and special offers, as the form says. Every email has an unsubscribe link. You can also download the game without giving us your email address.
We keep your address, the invitation you agreed to, its version, signup source, signup time, and subscription status in private Vercel storage. We retain an unsubscribe record so you are excluded from future mailings. Resend processes messages and delivery logs. Replies go to the developer. When you sign up or download, the developer is notified. We do not sell your email address.
Game accounts and collections
When online accounts are available, PlayFab processes your account email, password, player identifier, sign-in information, and game inventory. Passwords entered on our account page go directly to PlayFab and are not stored by the website. The account page keeps its sign-in session in memory until you leave or reload and does not load analytics or session recording.
If you choose to connect an earlier download signup, we verify the current login email with PlayFab and require a confirmed matching contact email before storing the association between that signup and your PlayFab player ID in private Vercel storage. This does not subscribe you to emails or award items. Unsubscribing does not delete your game account or collection.
Development log and administration
Published development notes and game files are hosted on Vercel. Private drafts, release records, and email campaign status are stored in private Vercel storage. Admin sign-in uses a short-lived email link and a secure session cookie.
Website analytics
We use PostHog to understand visits, preview plays, download requests, email-send failures, and clicks on download links. A random browser identifier is stored in local storage. Download links include an identifier so we can connect a request with a subsequent click. Once you sign up with your email address, your visits, signup and download clicks in this browser are connected to that address in PostHog, so we can understand how people find the game. PostHog also collects page views, interactions, browser/device information, referral and campaign information, and approximate city, region and country derived from your IP address. We use session recordings on public website pages to understand navigation and usability. Form inputs are masked; request bodies, headers and console logs are not recorded. Administration and account pages are excluded. Hosting and email providers may process IP addresses and technical logs to run the service.
Campaign labels from a tagged link are saved in this browser for up to 30 days. If you request a download email, we also save those labels with your signup and include them when you later use the emailed download link.
Advertising cookies
With your permission, we use the Meta Pixel on public pages at embercasting.com and embercastgame.com to measure Embercast advertising and help show relevant ads. Meta may receive the page you visit, referral and campaign information, browser and device information, IP address and cookie identifiers. We measure public page visits, successful requests for a download email, clicks on game downloads and clicks on our Discord invitation. These actions do not tell us that you installed or played the game or joined Discord.
Advertising tags stay off until you choose “Allow ad cookies.” Choose “No thanks” to continue without them, or use “Ad cookie preferences” to change your choice. We honor Global Privacy Control and Do Not Track signals by keeping advertising tags off. Your choice is stored in this browser. Withdrawing permission reloads the page to stop the tags and removes their accessible first-party advertising cookies; it does not delete information already received by the providers. We do not send email addresses, game account identifiers or form contents to advertising tags, and do not enable enhanced or advanced matching. Advertising tags are excluded from account, shop, administration and private email-link pages. Product analytics described above are separate from advertising cookies.
Learn more in the Meta privacy policy. For questions about advertising data or your choices, contact support@malagonlegacyllc.com.
In-game analytics
The game uses PostHog for play time, modes, match results and tutorial progress, always on from version 0.4.12 (earlier builds had a Usage analytics setting): it is how the game gets fixed and tuned. Builds with account-linked analytics include your PlayFab account ID, player name and account email when signed in, so we can understand player activity across sessions and devices. Signed-out events use a random identifier. Events may include approximate city, region and country derived from your IP address. Usage analytics never include passwords, chat or gameplay recordings; match replays are covered below. There is no in-game setting to turn it off from version 0.4.12; in earlier builds, turning it off stopped sending and cleared unsent events, and never deleted events already delivered. This does not subscribe you to emails or connect your download signup to your account. Earlier builds used anonymous usage analytics.
Alpha monitoring and debugging
Alongside usage events, we collect limited operational evidence from the game, website and backend: app and build versions; session, match, request and job identifiers; service names, operation stages, error classes, status codes and retry counts; connection and delivery outcomes; and performance summaries. Game performance evidence can include processor and graphics-card models, memory, display settings, frame durations, timing counters, garbage-collection counts, whether the game was focused, and names of game-code functions involved in a stall or error. Newer builds send small samples of long frames and grouped runtime errors automatically, even when extra diagnostic reports are off.
We use this information to investigate failures across clients and service providers, reproduce and fix bugs, test releases, diagnose compatibility and latency, improve gameplay and reliability, provide support, and protect accounts and services against fraud and abuse. Evidence can be linked to the account, session or match involved and compared across builds and devices. Automated tools, including AI-assisted development and analysis tools, may help authorized developers inspect limited diagnostic evidence for these purposes.
Our structured diagnostic events exclude passwords, session tokens, raw request or response bodies, email contents, chat and voice. Runtime error summaries contain error classes and game-code symbols, not raw exception messages, arguments or file paths, unless you turn on the extra diagnostics setting described below. We limit event volume and retained samples; this means an absent report does not prove that no problem occurred. Providers also process technical logs, such as IP addresses and request timing, to operate and secure their services. To investigate dropped matches, our game service notes when a signed-in player’s internet address changes between requests and records both addresses.
Extra diagnostics you choose to send
The game’s Send diagnostics to Embercast setting, under Settings, Privacy & credits, is off unless you turn it on. While it is on, the game sends an additional report after a match or trial, at most once every ten minutes, and soon after an error or a lost connection, to help us investigate performance and reliability. Reports contain hardware and display settings, up to 32 structured long-frame samples and the game’s recent log lines, including the text and code location of errors, linked to your account, build and session. Log lines can include player names, room codes, network error details and your computer’s network adapters and addresses. While the setting is on, the runtime error summaries described above also carry the error’s text. Builds from October 25 to November 15, 2026 sent no log lines. If you had the setting on in one of those builds, the next update turns it off and you can turn it on again under this description. Reports do not include chat, voice or recordings.
We retain the latest five extra reports per account. Turning the setting off stops further reports and clears pending reports on that device; it does not delete reports already received or stop the routine analytics and operational evidence described above. We continue to use reports collected under an earlier, narrower notice only for the support purpose stated when they were collected.
In-game conversations
Supported game builds send newly delivered party messages and submitted post-match messages to a private Embercast store for support and moderation. Records include the message, the sender’s account ID, the names and account-entity identifiers of party members present when it was recorded, the party ID and timestamps. Authorized Studio administrators can search and review these records. They are not included in analytics or diagnostics and are not exposed to other players through this review system. Records stop being available for review after 30 days; routine storage cleanup removes them afterward. Older builds, interrupted connections and departed parties can leave gaps. Post-match records identify the registered match participants; they do not establish that every participant received or read a message. You can contact play@embercastgame.com about these records or request deletion.
Match replays
From version 0.3.19, when you are signed in, the game shares replays of your online matches (quick matches and room-code matches) with Embercast, always on from version 0.4.12 (earlier builds had a Share my replays with Embercast setting): the replays are how we check that both players saw the same match and fix the game. Nothing is sent while you are signed out. Matches against bots, local matches, trials, clips and imported replays are never sent. For each online replay saved on your computer, including ones saved before this setting existed, it sends a summary of what your game recorded: both players' names and PlayFab player IDs, their skins, items and embercasts, the score and moments, the field, ruleset and game version. When we need it, it also uploads the replay file itself, which contains the recorded match: both wizards' movement, your camera and the effects your game showed. Private matches are included; private means nobody can watch them, not that they are not recorded. We use replays to check that both players' games showed the same match and to fix bugs. They are stored privately in Microsoft Azure, are never published or shown to other players, and are linked to the PlayFab ID of the account that uploaded them, and are kept until you ask us to delete them. Your replay files stay on your computer; sharing never deletes or changes them. Signing out stops sending right away and does not delete replays already received. To ask about or request deletion of your replays, contact play@embercastgame.com.
Your choices
To ask about or request deletion of your email information, reply to your download email. Clearing this site’s local storage resets its browser identifier. No account is required for direct downloads or offline play. Online collections require an account. For account access or deletion requests, contact play@embercastgame.com.
Service providers and access
We use service providers to host and operate Embercast, manage accounts and online play, deliver email, measure usage and investigate issues. These include Microsoft Azure and PlayFab, Unity online services, Vercel, Resend and PostHog. Authorized developers and providers may process the information needed for those functions. We may disclose information when required by law or reasonably necessary to protect rights, safety and the security of the service.
When you purchase something, the payment provider named at checkout handles payment credentials. We keep account and purchase references, amounts, confirmations and payment or refund status to deliver purchases, prevent abuse, provide support and meet accounting obligations. Our checkout does not receive your full card number. When you request generated content, the submitted content and necessary job information may be processed by the generation providers used for that feature. Avoid putting sensitive personal information in those requests.
Our services and providers may process information in the United States and other countries. Where applicable law requires safeguards for international transfers, those requirements still apply; this notice does not waive them. Advertising providers and their separate choices are described above.
Retention
We keep account and collection records while needed to provide the account and honor purchases, and subscription and suppression records while needed to manage your email choices. Private match replays follow the retention and deletion terms in the replay section. Extra diagnostic reports rotate at five per account; the backend’s recent failure sample is capped at 128 entries. These caps apply to those specific stores, not to every analytics event or provider log.
Analytics, provider logs and operational evidence have different retention limits. We retain them for the time reasonably needed to investigate incidents, compare builds, resolve support issues, improve the alpha and meet security or legal obligations. A limited incident record may be kept longer when needed to reproduce an unresolved defect or document its resolution. We review retained information and delete or de-identify it when it is no longer needed. Deletion requests may be subject to required accounting, fraud-prevention, legal and backup retention.
Legal bases and privacy rights
Where a legal basis is required, we process information as needed to provide requested services and fulfill purchases, to meet legal obligations, and for our legitimate interests in developing, measuring, debugging and securing Embercast, subject to your rights and the safeguards described here. Where consent is required, including for applicable advertising or device-storage technologies, we must obtain it separately; this notice alone is not consent.
Depending on where you live, you may have rights to access, correct, delete or obtain a copy of your information, restrict or object to processing, withdraw consent, or complain to your privacy regulator. Contact play@embercastgame.com; we may need to verify your request. Withdrawing consent does not undo processing that was lawful before withdrawal. Local-storage resets and signing out do not erase information already received. We do not sell your email address.
Changes to this notice
We update this notice as the alpha develops and show the revision date here. We will provide any additional notice or choice required before materially changing how we use personal information. A policy update does not override earlier promises about already-collected information.