Privacy Policy

Account and gameplay

Apple or Google sign-in, through Supabase, provides an account identifier and the identity information supplied by your sign-in provider, such as a name or email address. Session information keeps you signed in. We do not ask you to send us your Apple or Google password.

If you use Sign in with Apple, our backend also keeps the tokens Apple issues for your sign-in, encrypted and linked to your Apple account identifier. We use them to confirm that your Apple sign-in is still valid and, when you delete your account, to revoke FiTama's access with Apple. We also process the account notifications Apple sends about your sign-in, such as withdrawn consent, a deleted Apple account or email-relay changes.

When the iPhone app opens, it checks Expo's update service and may download a newer version of FiTama's app code and artwork. The check sends the app version, update runtime, platform, update channel and a random installation identifier created by the update system. It does not include your account, Health or game data.

We process your username, display name, friend code and optional profile photo to identify your account. Selected profile images are uploaded to account storage. Height, weight, preferred activities and About Me are stored in the device's account-scoped save in the current implementation; they are not fields in the shared social profile.

Companion identity and appearance, levels, XP, Tama Power (TP), quests, inventory, equipment, currency, check-ins, dungeon actions and reward records operate the game and preserve progress. Records are stored on your device and, where supported, synchronized to Supabase. This is not a promise that every device-only record is backed up.

We process account and game information to provide the features you request, and use relevant action records to maintain security, apply game rules and prevent duplicate rewards or abuse. Permissions and consent are requested separately where needed; this policy is a notice, not a substitute for those choices. Game rules automatically calculate TP, XP, quest completion, rankings and reward eligibility from relevant activity and action records. Contact support if you believe a calculation is wrong.

Apple Health and activity

With your permission, the iPhone app reads supported Apple Health categories: active energy, workouts, steps, walking and running distance, and sleep. We use them for movement-based TP, activity history, activity-specific quests and sleep quests.

Some Health-derived information leaves your phone. Activity summaries synchronized to Supabase can include activity type, start and end times, duration, steps, distance, active calories, source labels, record fingerprints and TP contribution. Sleep imports can include record identifiers, source-app identifiers, sleep stages, start and end times and manual-entry status. Quest evidence and calculated progress support synchronization, duplicate handling and reward verification.

Individual activity and sleep records are not shown as a public Health feed. However, activity-derived game totals, including TP and ranking scores, can be visible through social and group-play features. We do not use Health information for advertising or send it as ad-targeting information.

You can change access in Apple Health at any time. Revoking access affects future reads and dependent features; it does not itself delete information already synchronized to FiTama. You can request deletion as described below. Deleting FiTama does not delete the original records in Apple Health. Manage Health access and data with Apple.

Social features

Other signed-in players can find shared identity details using an exact username or friend code. Shared details include your username, display name, avatar, friend code, companion information and level. Confirmed friends can also see today's synchronized TP. Player cards can show companion appearance, level, rank and resting status.

Rankings display usernames and aggregate game scores. Group dungeon participants can see party members, companion information and battle contributions. We store friendships, requests, invitations, party membership, battle actions and timestamps to operate these features. Mail stores friend-request and dungeon-invite notifications, sender and recipient identifiers, request status, timestamps and read status.

With Invite Friends, a new player can enter your friend code or username before their egg hatches. We record which account invited which, and when, so we can make you friends and send referral rewards to both of you in Mail. Your Invite Friends list shows the invited player's username, companion and whether their egg has hatched. To allow one friend code per sign-in, we also keep a one-way hash of the sign-in provider and provider account identifier. It is not linked to a FiTama account and players cannot read it.

Removing a friendship does not remove your identity from every ranking, party or shared battle record. Shared dungeons may continue for remaining players after an account is deleted; their history may retain an anonymous replacement participant.

Dungeon chat

Players in the same Group dungeon battle can chat. There is no direct-message inbox, global chat, Lobby chat or Solo/Training chat. Chat processes message text and emoji, selected sticker identifiers, sender and battle identifiers, companion display details, order and timestamps. Read progress, room closure, request identifiers and account-reset version identifiers support access checks, unread counts, reliable delivery and send limits.

Players in the battle can see messages and sender details available to them. Chat is not end-to-end encrypted: the backend processes message content. Do not send passwords, sensitive Health details or anything you do not want to share with the party.

Before accepting a message, FiTama's server checks its text against a word filter. The filter can miss harmful content and can reject harmless wording; it is not a substitute for Report and Block. A rejected message is not delivered, and the record of a rejected attempt does not keep its text.

Report preserves the selected message's server-confirmed content and metadata, report reason, reporter identifier, related identifiers and time for authorized abuse review. FiTama's support mailbox receives a notice with the report identifier, time and reason only, not the message. Reports are not public and do not notify the reported player. Report evidence is separate from ordinary messages and may remain after an account or message is deleted.

Block stores the blocking and blocked accounts, selected display details, timestamps and request records. It hides that player's messages from your view in every dungeon; it does not remove party members, prevent invitations or stop them seeing your messages. It does not copy message content into block records.

Authorized operators can review preserved report evidence, remove a message from ordinary chat and pause an account's chat sending for 24 hours. A chat pause does not change equipment, TP, rewards or Fitama progress. Removing a message hides its body from later server responses; offline devices and copies already received cannot be recalled instantly.

Notifications

When enabled, FiTama associates an Expo push token, installation identifier, device platform and notification preferences with your account. Expo and the platform notification service deliver friend-request, dungeon-invite and battle updates. Payloads contain routing identifiers and update text; previews may appear on your lock screen.

Manage notification categories in Account Settings and permissions in your phone settings. Disabling notifications does not delete your account or Mail history.

Optional rewarded ads

FiTama integrates Google AdMob for Hermitanyo's optional rewarded ads. The app requests non-personalized ads and uses Google's consent tools before permitted ad requests. Ad availability and consent options depend on your app version, device, region and Google's configuration. Where available, use Ad privacy options in Hermitanyo to review your choices.

Non-personalized does not mean no data is processed. Google's Mobile Ads SDK may process IP addresses, device identifiers, ad views and interactions, diagnostic information and performance data. See Google's iOS ad-data disclosure and Google's Privacy Policy.

FiTama stores account-linked reward requests and verified transactions, including request and transaction identifiers, ad unit and reward details, and timestamps, to grant rewards and prevent duplicate claims. Our ad-reward integration supplies an opaque reward-request identifier for server verification, not Health records or profile content. That identifier is pseudonymous, not anonymous: our backend associates it with your account.

You can choose not to request rewarded ads. This policy is not itself consent to tracking or advertising.

Tama-Coin purchases

When you buy a Tama-Coin pack in the iPhone app, Apple processes the payment. We do not receive your card or other payment details.

Apple gives the app a signed record of the purchase. Our backend checks it and stores it with your account: the transaction identifiers, the pack and quantity, the App Store country, whether it was a test purchase, and when it was bought and credited. We use these records to add the Tama-Coins once, prevent duplicate credits and answer support questions.

Website and support

The website uses locally hosted artwork and fonts. We have not added analytics scripts, advertising or third-party embeds. The Android waitlist and contact form send the details described below to Google only when you submit them. GitHub Pages hosts the website and logs visitor IP addresses for security, including for visitors who are not signed in to GitHub. See GitHub Pages data collection.

You can contact us by email or through the website contact form. If you send an email, we receive the address, message, attachments and other information you include. We use these to respond, troubleshoot and handle privacy or safety requests. Our support mailbox uses GoDaddy Professional Email powered by Titan. Do not email passwords, verification codes or your full Health history.

The contact form sends your email address, selected topic and message through Google Apps Script to our support inbox so we can respond. It does not add you to the Android waitlist or a marketing list. Google processes the submission and email delivery. Request identifiers, hashed email/message fingerprints, counts and expiry times help prevent duplicate sends and limit abuse; these records expire within 24 hours and are removed on the next submission. The form does not accept attachments. Please share only what is needed to explain your request.

Android waitlist

When you submit the Android waitlist form, we collect your email address, signup time, signup source and the version of the consent notice. We use these details to manage your request and email you when Fitama is released on Android. Joining is optional, does not create a Fitama account and does not provide access to Apple Health or your game progress.

Google Apps Script receives the submission and saves it in a private Google Sheet accessible to the people managing the waitlist. Google also processes the technical information needed to operate its services. The public signup endpoint accepts submissions; it does not make the email list public. We do not use this list for unrelated marketing.

You can withdraw your signup or request correction or deletion at any time by emailing support@fitama.app from the address you registered, with the subject “Android waitlist request”. You do not need a game account or username. Joining does not guarantee a release date, early access or a particular Android device’s compatibility.

Providers and overseas processing

Service providers process information needed for their roles: Supabase for authentication, database records, avatar storage and backend functions; Apple or Google for sign-in; Apple for in-app purchases; Expo and platform push services for notifications and app updates; Google AdMob for optional ads; GitHub Pages for this website; Google Apps Script for the contact form and Android waitlist, Google Sheets for waitlist storage; and GoDaddy/Titan for support email and domain services.

These services can process information outside the Philippines. We do not promise Philippine-only storage. Supabase hosts core project data in the selected project region and describes additional overseas processing for operations, support, logs and content delivery. Provider processing locations and retention can differ by service and configuration.

For provider handling, see Supabase's Privacy Policy, its Data Processing Addendum for application data and data residency information, Expo's Privacy Policy, GitHub's Privacy Statement, and Titan's Privacy Policy. See also Google’s Privacy Policy for its services. Their notices do not replace our responsibility for FiTama's processing. Contact us about a specific transfer or provider-handling question.

We may disclose relevant information when required by law or necessary to address a specific security incident, abuse report or legal claim. We do not make your private Health records available to other players or supply them for ad targeting.

How long we keep information

Account, gameplay and synchronized Health-derived records

We keep account-linked records while the account remains active, until account deletion or an applicable deletion request, subject to the exceptions below. Some records may be removed sooner when no longer needed. Signing out, uninstalling or restarting gameplay is not account deletion.

Tama-Coin purchase records

We keep purchase records while the account remains active. They are deleted with the account, subject to the legal exceptions below.

Android waitlist

We keep the entry for the Android launch notification, or until you withdraw your signup or request deletion. Once the notification has been sent, or if the launch is cancelled, we remove entries that are no longer needed. Any specific legal or security exception is limited to that purpose. This is separate from your game account: deleting a game account does not automatically identify and remove a waitlist entry registered with another address.

Support emails

We retain support correspondence for up to 12 months after the issue is resolved, then delete it from the active support mailbox, unless a specific legal requirement or unresolved security dispute requires relevant material to be kept longer.

Chat messages and reports

Ordinary chat messages become eligible for deletion seven days after the earlier of battle resolution or scheduled expiry. Report evidence, rejected-attempt records and moderation records become eligible 30 days after they were created. An hourly cleanup job deletes eligible records in batches, so deletion can follow eligibility by some time. Closing results removes your access to that chat, not every stored copy immediately; provider backups and copies already on players’ devices can last longer.

Sign-in records kept after deletion

After account deletion we keep two one-way hashes, neither linked to a FiTama account. The first, of the sign-in provider and account identifier used with a friend code, stops the same sign-in from redeeming another friend code. The second, of the Apple account identifier with the time FiTama's Apple access was revoked, stops a revoked Apple sign-in from being reused. The encrypted Apple tokens are removed with the account.

Shared records, legal exceptions and provider copies

Shared battle history can remain for other players without your former account identity. Separately preserved report evidence, or relevant records required for a specific legal obligation or unresolved security matter, may remain beyond an account deletion; their use is limited to that purpose. Provider backups and security or operational logs can also remain after active-system deletion until the provider's applicable retention cycle ends. We do not promise instant erasure from every backup, log or recipient's copy, or a universal expiry for provider copies. Contact support for information about your request and any applicable exception.

Your choices and rights

You can edit available profile fields, revoke Health access, manage notifications and review available ad privacy choices. Account Settings → Delete account requests permanent deletion of the signed-in account and linked personal records, removes uploaded avatars, and clears that account's local save. If the app reports an incomplete deletion or cleanup, retry or contact support. A gameplay restart is not a substitute for deletion.

Under applicable Philippine privacy law, you may have rights to information, access, correction, objection, erasure or blocking, and data portability, subject to the law's conditions and exceptions. You can withdraw consent for consent-based processing. This affects future processing and may limit the relevant feature; it does not automatically undo earlier processing or erase synchronized data.

Email support@fitama.app with the subject “Privacy request”, your FiTama username if you have one and what you want us to do. For a waitlist-only request, use the email address you registered; no game account or username is required. Redpots Games handles these requests. We may ask for proportionate account verification before disclosing or changing personal information. Do not send your password or a verification code. If we need more information or cannot fulfill part of a request, we will explain the next step or relevant reason.

You can also raise a concern with the Philippine National Privacy Commission. Contacting support first is not a condition of the rights provided by law.

Security, age eligibility and updates

FiTama uses authenticated services and access checks to restrict account and battle information. No system can guarantee absolute security. Dungeon chat is not end-to-end encrypted, and authorized operators may review preserved report evidence.

FiTama's initial service is intended for people aged 16 and older in the Philippines, not children under 16. If you believe an underage person has supplied personal information, contact support so we can investigate and address the account.

We will update this policy when our handling changes. The date above identifies the current version. Changes requiring additional permission will not be treated as permission merely because this page has changed. Any material change in chat, advertising or website data collection requires a fresh review of this notice and the relevant in-app disclosures.