Privacy policy.

Who we are and how to contact us

AMDII Studios LLC operates the AMDII Studios website and Report Card. This policy describes the website, Report Card’s web/PWA experience, and its planned iOS and Android releases. The initial native release is planned for the United States; the public website and PWA may be accessed from other countries.

For support or privacy requests, email [email protected]. Incoming email is forwarded through Cloudflare Email Routing to a Yahoo mailbox managed by the founder, who is initially responsible for support and privacy requests. Please use this email address while website-form delivery and replies from a branded studio address remain unconfirmed.

Report Card gameplay and local storage

Report Card does not require a game account. The reviewed game does not ask for your name, email address, date of birth, or school details. Support and newsletter forms are separate from gameplay and may ask for contact information.

Completed challenges are saved on your device using browser or native WebView localStorage. Records include the challenge date, a content-generation version where present in older records, score, total number of questions, IDs of correctly answered questions, and completion timestamp. These records support the challenge archive. Question IDs and date-based challenge seeds identify game content, not a player account.

Unfinished answer selections are held in memory. The reviewed first-party game implementation does not provide a gameplay-results upload service, cloud synchronization, leaderboard, or integrated remote analytics or crash-reporting client. These findings do not establish that hosting services, operating systems or third-party software process no information.

Sharing a score

If you choose Share, Report Card passes a summary to your device’s sharing interface or clipboard. It includes the challenge date, score and percentage, grade-result markers and any completed school stage. It does not include question wording or answer choices. Web sharing includes the game’s public origin URL; the reviewed native sharing payload omits the local WebView URL.

The game’s sharing code does not upload the summary to an AMDII Studios server. The recipient or service you select handles the shared information under its own practices. Clipboard contents may also be accessible through device or operating-system features.

Website visits, hosting and third-party services

The website and PWA request files from their hosting services. The PWA can cache app files for offline use. Requests involve ordinary HTTP metadata, which can include IP addresses, request headers and requested URLs. Cloudflare hosts the website and processes website form requests. Hosting and security services may process request information; account-specific logging, access and retention settings have not been verified.

The reviewed Report Card source uses local font assets, and the native configuration bundles game assets and fonts. The deployed PWA may differ from reviewed source or packaged apps. Its current asset version, any external resources and actual native network activity have not been independently verified for the final release.

No first-party website cookie, localStorage, sessionStorage, IndexedDB or separate analytics implementation was found in the reviewed website source. This does not describe all storage or processing by embedded scripts, hosting services or operating systems.

The homepage has a Kit newsletter form and browser-side ConvertKit JavaScript. Submitting that form sends your email address to Kit. Newsletter signup is separate from support; reporting an issue does not enroll you. Kit’s actual account settings, cookies, tracking, confirmation, unsubscribe and deletion behavior have not been independently verified.

General website pages, including the Support Center, load Google AdSense JavaScript for ownership verification. The local contact, issue-reporting and privacy pages omit this loader. No explicit ad placements or Auto Ads initialization were found in the reviewed website code. The verification purpose does not establish that Google performs no processing; account settings, cookies, identifiers, requests and any advertising behavior remain unverified.

Advertising and planned native releases

The initial native Report Card release is planned to be ad-free. AdMob activation is deferred to a separate post-launch review and release. The reviewed app configuration disables advertising and app-driven advertising-consent requests.

Android still includes Google advertising and consent libraries, although the reviewed app blocks app-driven advertising initialization and removes advertising-ID and specified AdServices permissions. The iOS package configuration is intended to exclude Google Mobile Ads and User Messaging Platform SDKs, but final archive contents have not been verified. Installed libraries, disabled ads and packaging settings do not by themselves establish whether SDKs execute or transmit information.

Capacitor and operating-system WebView services support the native app; Android also includes automatic AndroidX startup components. Actual SDK activity, operating-system diagnostics and final release-artifact privacy declarations remain unverified. We do not describe the planned native releases as collecting no information.

Support and issue reports

The unified Report an Issue form requires a released product, subject, description and reply email address. We use these details to identify the product, understand the issue and respond. The general contact form requires a name, email, topic and message to review and respond to your inquiry.

Free-text submissions may contain personal information you choose to provide. Please do not include passwords, authentication tokens, student names or unnecessary personal information. The form code does not automatically attach gameplay records, game-account identifiers, device diagnostics or game authentication tokens. Requests also involve ordinary HTTP metadata and, when enabled, a spam-verification token.

The prepared server-side delivery path sends validated submission content through Resend to [email protected], with AMDII Studios Support <[email protected]> as the fixed sender. Your address appears in the message and its reply-to field. Product and subject also appear in an issue email’s subject line. Cloudflare Email Routing forwards incoming support mail to the receiving Yahoo mailbox. Direct email bypasses the website form and Resend path but still uses the forwarding service and mailbox.

When enabled, the forms use Cloudflare Turnstile to help prevent spam. Your browser communicates with Cloudflare and receives a verification token, which our server sends to Cloudflare for checking. That server request does not explicitly include your issue text or IP address. Cloudflare may still receive browser signals and network metadata. We have not confirmed the full scope of cookies, processing or retention associated with this integration.

The application handler processes submissions in memory, without saving messages in a website database or logging message text. A random per-form submission identifier and a server-generated retry key help limit duplicate sends. They are not a game account or a persistent browser-storage identifier, and they do not guarantee exactly-once delivery.

A form acceptance message means Resend has returned a receipt for the submission; it does not confirm arrival in our receiving inbox. A connection failure can leave it unclear whether a submission was accepted. Successful spam verification and delivery through the complete website-form and email-forwarding path are not yet confirmed. Please email [email protected] if you cannot submit a form or are unsure whether your request reached us.

Resend, Cloudflare, Yahoo and any mail client or recipient may hold separate messages or metadata. Provider-controlled retention, backups and security records are separate from the application’s own logging and storage. Public provider documentation does not establish that records in these particular accounts have been deleted.

Retention, backups and deletion requests

Saved gameplay results have no application-defined expiry or in-app erase control in the reviewed version. An inactive advertising-attempt storage feature is not written by the disabled shipping path, but older test records are not automatically purged. Removing cached PWA app files does not erase gameplay results.

The reviewed Android Release configuration disables backup and specifies cloud-backup and device-transfer exclusions for app storage. Base/Debug settings permit backup and differ from Release. These settings do not prove actual device or manufacturer behavior or remove older backups. iOS WebView backup coverage and actual restore and uninstall effects remain unverified. Clearing app or browser storage may remove local information, but copies in backups or shared summaries may remain.

Our support retention standard is to keep open requests while actively handling them and delete associated personal information from resolved support requests within 90 calendar days after resolution. Longer retention is permitted only when reasonably necessary for unresolved follow-up, documented security or business needs, or applicable legal obligations. Exceptions require a documented reason and review of continued necessity.

The founder is responsible for a private retention ledger and Monday reviews in America/New_York. AMDII Studios LLC has adopted the manual procedure to meet the 90-calendar-day-after-resolution support retention standard, subject to documented exceptions and actual provider limitations. Adopting this procedure does not mean that every deletion has been completed or that every provider record or backup can be removed. We cannot yet confirm the procedure’s execution across all relevant locations or the removal options available in each provider account. Resend records, forwarded mailbox copies, Trash, recoverable items, security and hosting logs, local copies and backups require separate assessment. Removal from one location does not establish removal everywhere.

Send privacy or deletion requests to [email protected]. Requests require review of their scope and appropriate identity verification, using only reasonably necessary additional information. Our privacy-request handling process is not yet confirmed as fully operational. The 90-day support standard does not require you to wait until that period ends to make a request. Any response must distinguish actions that can be verified from retained exceptions or provider-controlled limitations; no universal or permanent erasure capability is represented.

Intended audience

Report Card is intended for people ages 13 and older. We do not intend to market it to children under 13. K–12 labels describe question difficulty, not a player’s age or school grade. The reviewed game does not collect age or date of birth and does not technically block younger users.

Intended audience does not prove who actually uses the game or that children’s information is never processed by hosting, third-party software or voluntary support messages. No age-verification or parental-consent system is represented. Messages that may involve a child under 13 require restricted handling and only necessary information. We cannot yet confirm that these handling safeguards are operating consistently.

Changes to this policy

The effective date identifies the applicable version of this policy. Material changes to products, support processing, third-party services, advertising or audience treatment will be reflected in an updated policy and notice.