Privacy Policy | Samzoka Studios

Samzoka Studios — Privacy Policy Version: studio-2026-10-30-r3 Status: Published Published: October 30, 2026 Effective date: October 30, 2026 1. Scope and contact Samzoka Studios, based in California, USA, is responsible for the information handling described here. This Policy applies to our games, apps and related services that display or link to it. CYRALITHRA: The Starbound Sorceress is one of our products. Contact our monitored privacy mailbox at privacy@samzoka.com with privacy questions or requests. The studio-wide sections explain our approach. The product section below identifies CYRALITHRA's current features and providers and distinguishes planned features. Future products and new collection require their own information before collection starts. This Policy does not authorize undisclosed accounts, advertising, social features or tracking. 2. Information and purposes We collect information for the purposes explained below, depending on the product, the features you use and your choices. • Local game information: saves, settings, cosmetic selections, progress, gameplay statistics and privacy preferences held on your device. Keeping this information locally does not itself mean it is uploaded to us. Device backup and restore behavior also depends on your operating system. • Optional gameplay information: sessions, run starts and outcomes, monsters defeated, player-character deaths and reasons for run endings, attempts and retries, floors and acts reached, completion and elapsed-play times, upgrades and equipment, menu and cosmetic interactions, and story engagement. We use the events available in the relevant release to understand usage, evaluate difficulty and reliability, and identify places where players encounter problems. Not every event or parameter is sent to every provider. • Technical diagnostics: app version, device and operating-system characteristics, crash traces, performance measurements and related identifiers, used to investigate failures and improve reliability. Gameplay and crash reporting share the current reporting control described below. • Support information: your contact details, message and attachments you choose to send, used to answer requests and investigate reported problems. Please avoid sending sensitive information unnecessarily. • Service and security information: network information such as IP addresses and request metadata, and proportionate security or abuse-prevention records, used to communicate, operate requested online features and protect our services. • Store and testing information: information a distribution platform makes available to us, such as Beta feedback, tester contact details or purchase confirmations when relevant. That platform's own privacy terms also apply. Some events are associated with random installation or player identifiers. These let us distinguish installations or adventures and compare activity over time without asking for a real name or email address. We describe this information as pseudonymous, not guaranteed anonymous. An identifier need not contain a name to be personal information. Reinstallation, another device or an identifier reset may be counted separately. We use reports to examine observed totals and averages, such as monsters defeated, Brell deaths, kills per run, retries after a death, successful ascents and completion times. Reports may also compare versions, stages, equipment and performance. These are product-improvement measurements, not claims about an individual's identity, personality or reading comprehension. Reports reflect the activity we actually receive; they do not necessarily represent every player or every run. Preparing an aggregate report does not make the source events anonymous. 3. Choices and legal grounds Gameplay analytics requires an affirmative choice before it is enabled. Where a game displays a distinct reporting notice, its Accept & Play action can accept the Terms and allow the reporting described in that notice. CYRALITHRA displays its acceptance notice after New Game or Continue and before save selection, rather than on initial launch. You can change your reporting choice in Settings. Refusing analytics does not remove local progress or ordinary access to the game. Accepting this Policy is not blanket consent to all processing, and accepting the Terms is not consent to optional analytics. We do not switch refused optional analytics to a different legal basis in order to continue collecting it. Where European Economic Area or United Kingdom data-protection law applies, the purposes and legal grounds are: • Optional gameplay analytics, optional crash reporting, and optional website analytics: your consent, subject to applicable age and device-storage/access requirements. You may withdraw consent at any time; withdrawal does not make earlier lawful processing unlawful. • Responding to support requests: steps you ask us to take in connection with the game or performance of our agreement where that basis applies; otherwise our legitimate interest in answering questions and resolving problems. Separate legal duties apply to handling statutory privacy requests. • Necessary service operation and limited security/abuse prevention: our legitimate interests in providing reliable, secure services and diagnosing faults, where processing is necessary and proportionate and those interests are not overridden by your rights. Where a law requires consent for a particular collection or device access, that collection must instead wait for valid consent. Calling information diagnostic or pseudonymous does not itself create an exemption. • Compliance with a legal obligation and handling legal claims: the applicable legal obligation or our legitimate interests in establishing, exercising or defending claims, as appropriate to the particular processing. • A future leaderboard result you choose to submit: providing the requested competitive feature where a contractual basis is appropriate, with proportionate validation and security processing on the applicable basis. Its detailed notice and eligibility controls must be provided before the feature is enabled. Submission is separate from optional gameplay analytics. Only processing actually carried out for a disclosed purpose uses the relevant basis. If an activity cannot lawfully use that basis in your circumstances, it must be limited, disabled or offered with any additional lawful choice needed. We do not use gameplay analytics for decisions producing legal or similarly significant effects about you. 4. Privacy requests and rights Contact privacy@samzoka.com to make a request or raise a concern. Depending on the law that applies and the relevant processing, you may have rights to know about or access information, receive a portable copy, correct inaccurate information, request deletion, restrict processing, object to processing based on legitimate interests, withdraw consent, and complain to a privacy regulator. These rights can have legal limits and exceptions. We will explain a refusal or limitation and any available review or appeal process where required. Exercising an applicable right will not be used to penalize you. An email address or the game's version/build Support ID does not necessarily locate an installation's telemetry. We may ask for proportionate information reasonably needed to verify a request and locate records, such as relevant installation information and the service involved. We do not require unnecessary sensitive identity documents. We may be unable to associate some records with you after an identifier reset or without additional information; we will explain the limitation and consider information you provide rather than promise that records can always be located. We respond within applicable legal deadlines and explain permitted extensions where needed. Turning off analytics stops future optional usage collection. It is different from requesting deletion of previously uploaded information. Removing the app or local saves does not automatically delete provider-held records. Information that has been genuinely anonymized so it can no longer reasonably be associated with a person may not be recoverable as an individual's record. If you are in the EEA, you may complain to your competent data-protection authority, including the authority where you live, work or believe an infringement occurred. In the UK you may complain to the Information Commissioner's Office. In Canada you may contact the applicable federal or provincial privacy regulator. Contacting us first is welcome but does not prevent a complaint to a regulator. 5. Providers, disclosures and international processing We use service providers for hosting, analytics, diagnostics and support as described for each product. We limit disclosures to the relevant purpose and select contractual and technical protections appropriate to the information. Providers acting on our behalf must protect it consistently with our commitments and applicable law. A provider's independent processing, or a store's handling of its own information, is also subject to its own notice and applicable responsibilities. We do not sell CYRALITHRA gameplay information or share it for cross-context behavioral advertising in the current Beta. Advertising identifiers, ad personalization and Google Signals are disabled in the current gameplay analytics configuration. A future change to advertising or data use requires appropriate notice and any permission legally required; this Policy does not preauthorize it. We may disclose information when required by law or as reasonably necessary to address fraud, security threats or legal claims. If a business transfer affects information, applicable privacy duties and notice requirements continue to apply. We operate in the United States. The current Supabase project's primary database is in Canada (Central). This is not a promise that all processing, logs, backups or support access remain in Canada. Google and other providers may process information in the United States and other countries. Different laws and lawful government-access rules may apply. Where international-transfer restrictions apply, an appropriate transfer arrangement must cover the relevant transfer, such as an applicable adequacy decision or approved contractual safeguards with any additional measures required. You may contact privacy@samzoka.com for information about the safeguards applicable to your data and how to obtain a copy or description, subject to lawful redactions. This Policy does not assert that any particular provider certification or transfer mechanism covers every processing activity. 6. Retention and security We keep identifiable or pseudonymous information only for as long as reasonably necessary for its disclosed purpose or a legal obligation. The criteria include the observation period needed to assess a release or repeated attempts, the need to resolve an active support or security issue, applicable legal time limits and whether less detailed information can serve the purpose. Records should be deleted or genuinely anonymized when no longer needed; local, active-service, log and backup copies can have different removal processes. Local saves and preferences remain until removed or replaced by the game, you or your device's storage controls. Uploaded records are separate. For the 13+ release, raw Supabase gameplay records expire after 14 calendar months from server receipt, submission audit records after 30 days, expired challenge tokens after seven further days, and application security rate-limit records after seven days. A daily bounded cleanup applies those schedules; activity does not restart a raw event's retention period. An exceptional backlog or failed cleanup requires investigation rather than a claim that deletion has already completed. These cleanup controls are deployed for the current Supabase service. These are historical raw-record schedules; current aggregate-count and Google reporting are described in the product section below. Installing a revised build and making its reporting choice are separate from this publication. Routine resolved privacy correspondence and minimal request audit records are scheduled for removal after 12 months, unless a specific legal hold requires longer. We retain limited, protected revocation proof to prevent an old installation credential or restored backup from recreating deleted records. Credentials cannot upload indefinitely: their upload permission expires after 14 months. Revocation proof is retained through the required recovery period; it is not used for gameplay reporting. Where a backup recovery window has not yet been verified, we preserve suppression rather than risk deleted information reappearing. After a database recovery, restored gameplay reporting is discarded and restored reporting credentials are revoked before uploads resume. Service logs and provider backups have separate removal processes and are reviewed for release; no universal seven-day backup promise is made. We use safeguards appropriate to the information, including restricted access and service security controls, but cannot guarantee that a device, network or service is completely secure. Necessary preservation for legal obligations or claims may limit a deletion request; we will explain an applicable exception. 7. Younger players CYRALITHRA is intended for people aged 13 and older and is not directed to children under 13. A higher local age or parental-authorization requirement may apply to a particular feature or processing activity. Being old enough to play is not necessarily being old enough to consent independently to optional analytics or public result submission. Current CYRALITHRA builds offer the gameplay reporting described below in the US and Canada, based on the device's country/region setting. The reporting flow does not request an age range, exact birth date, country or province. The device preference does not verify residence. Reporting is unavailable in other or unknown regions. A known-under-13 restriction is preserved on the device; an unanswered age is not a statement of adulthood. This release does not offer parental verification. Contact privacy@samzoka.com about a younger player's information or an applicable local restriction. Older installed Beta builds used local age-range and region rules: Canada 16+, US 18+, UK 13+ and EU 16+, with reassessment after region changes or 12 months. Those older controls and historical records are distinct from the current count-reporting flow. Publication does not change an installed older build or renew a previous refusal. If you believe we have collected a child's information contrary to applicable requirements, contact privacy@samzoka.com. We will investigate and take appropriate steps, which may include stopping collection and deleting information subject to applicable law. A store age rating or the absence of an age prompt does not create an exemption from children's privacy protections. 8. Changes and future products The published Policy is available at https://samzoka.com/privacy/. This revision describes the updated 13+ app candidate. Older installed Beta builds may still use the earlier controls and Google services described below; publication does not update an installed app. The current reporting notice and controls apply when you install a build containing them. We identify revisions by version and effective date, give notice of material changes, and obtain renewed consent where required before new optional collection. An updated notice does not by itself authorize undisclosed new processing. Planned features described below are conditional and require their own complete notices and controls before activation. CYRALITHRA — current Beta product information A. Local play The current Beta does not require a Samzoka account. Saves, cosmetic selections, settings and document acceptance are held locally. A player-selected name is not included in Firebase usage events. We do not send player-entered free text or a shared cross-service User ID to Firebase. We do not request contacts, precise location, camera or microphone access for the analytics described here. B. Gameplay reporting After the distinct reporting notice and Accept & Play, eligible current US and Canadian builds use Google Analytics for Firebase and Supabase to understand gameplay and balance. You can turn reporting off through Privacy & reporting in Settings. A previous refusal is preserved; an old analytics permission does not authorize the revised notice automatically. The new build presents the revised notice before enabling this reporting. The game's reports contain bounded act and campaign outcomes; first, repeat or unknown local-adventure attempt classes; completion-time ranges and timing-quality indicators; and one randomly sampled charm's presence, offer and selection counts per act. Incomplete or interrupted timing is marked unknown. Reports include game, release and build labels. They do not include player-entered text, our stable installation ID, exact gameplay durations or full equipment builds. These are observations and local adventures, not a count of unique people or proof that a charm caused an outcome. Supabase receives short-lived delivery receipts to avoid duplicate counting, then stores aggregate count cells without an installation-linked gameplay history. Pending local observations expire after 24 hours; delivery receipts after 48 hours; network-derived security subjects after two hours. Aggregate cells expire 14 calendar months after creation; new contributions do not extend old cells. A scheduled cleanup applies these expiries. Requests also involve IP addresses and provider network/log metadata; the count schema alone does not make the whole collection path anonymous. Google Analytics for Firebase is one Google analytics service. It receives the bounded gameplay events and the SDK's automatic app/session and device information. Google generates an app-instance identifier and may process app/device characteristics, operating system, approximate country, network information and event timestamps. The Google records are pseudonymous and can associate activity over time. We do not send our Supabase installation credential, a shared cross-service User ID, a player-entered name or full builds to Google. Advertising identifiers, advertising storage, advertising user data and advertising personalization remain disabled in the current configuration. Turning reporting off disables future gameplay and crash reporting, clears pending Supabase count uploads, requests deletion of cached Crashlytics reports and resets the local Google analytics data. Resetting locally is not a remote deletion of Google's historical records. Contact privacy@samzoka.com for access or deletion requests; locating Google data may require available app-instance information. The app's Delete uploaded data action continues to request deletion of historical installation-linked Supabase reporting records. Count cells that cannot reasonably be associated with an individual cannot be retrieved as that individual's contribution. Google retention, logs, backups and deletion follow the applicable provider settings and request process; we do not promise that an app reset erases provider-held data. Earlier Beta versions could upload installation-linked Supabase events under their own separate permission and eligibility controls. A protected installation credential authenticated those reports and supported deletion. Those historical records and pending privacy requests retain their existing handling and are not transferred into the new count pipeline. The current app does not silently reenroll a historical installation identity to send counts. C. Crash diagnostics Current US and Canadian builds also enable Firebase Crashlytics after the distinct reporting notice and Accept & Play. Crash reporting uses the same Privacy & reporting control as gameplay reporting: a previous refusal remains off, you may turn it off in Settings, and known-under-13 and owner exclusions remain. It does not depend on an older Beta age-range answer or separate diagnostics preference. Crashlytics sends crash stack traces, exception information, app/release, device and operating-system details, diagnostic timestamps and Crashlytics installation identifiers to Google to investigate failures and improve reliability. Analytics breadcrumbs may accompany crash reports. We do not set a custom Crashlytics User ID or add player-entered text, full loadouts or gameplay report objects to crash logs. Crash records are diagnostic records, not anonymous aggregate count cells. They are not sent to Supabase by this crash-reporting path. Turning reporting off disables automatic crash-report uploads and requests deletion of cached reports. Reports already queued or in transit may still finish uploading. After Firebase has been initialized, the SDK can continue recording crash information locally while reporting is off. Explicitly turning reporting back on permits pending local crash reports, including reports recorded while reporting was off, to be uploaded. Turning reporting off does not delete crash reports already received by Google. Earlier Beta crash diagnostics used a separate preference. Google's published information describes a 90-day crash-data retention period before removal from live and backup systems begins; this is not guaranteed complete erasure on day 90. Historical crash-report requests must be handled separately from a gameplay analytics reset. D. Planned timed challenge and leaderboard An endgame tower challenge and online leaderboard are planned and are not enabled merely by publishing this Policy. Before activation, the game must explain the result information, public fields, eligibility, validation, retention and request process. A result submission will require a separate choice; an optional-analytics opt-in is not a choice to publish a result. The intended result information includes challenge/ruleset identifiers, ascent time, completion outcome and proportionate integrity evidence needed to validate the result. A competition identifier can distinguish submissions without requiring a real-world identity. A board may display a rank, time, challenge and the display identifier explained before submission. We will not silently publish an email address, real name or private gameplay history. Declining gameplay analytics does not itself authorize public posting, and requesting a leaderboard submission does not enable unrelated analytics. E. Stores, virtual currency and support Apple TestFlight and other distribution platforms handle installation and testing under their own terms. Feedback submitted through them may include information they provide to the developer. Current earned-currency spending is virtual gameplay activity, not a payment-card transaction. If you contact privacy@samzoka.com, we receive your email and the information you send. Provider information: Google Analytics safeguards: https://support.google.com/analytics/answer/6004245 Firebase privacy and diagnostics: https://firebase.google.com/support/privacy Supabase privacy: https://supabase.com/privacy Website analytics The website uses optional Google Analytics 4 to understand page visits, engagement and contact-link clicks. Google's tag loads only after you accept analytics. Declining keeps it off. Advertising storage, advertising personalization and Google Signals are disabled in the website tag. When enabled, Google processes page and device/browser information, network information and cookie identifiers to measure visits. The page configuration omits URL query strings and fragments, and the contact event does not include your email address or message. Google's handling is described at https://policies.google.com/technologies/partner-sites. The website remembers your choice in this browser for up to 180 days using local storage. Analytics cookies are configured for up to 180 days and may refresh with visits. Different browsers and domains have separate choices. Use Analytics preferences in the footer to change your choice. Declining later stops future website analytics and removes accessible Google Analytics cookies on that domain; it does not delete information already sent to Google. This website choice is separate from the game's privacy settings. Contact privacy@samzoka.com for questions or requests. Samzoka Studios • California, USA • privacy@samzoka.com