1. Introduction and Scope

This Privacy Policy ("Policy") describes the data practices of FieldGain ("Application," "Service," or "we") developed and operated by Mehmet BAŞCI ("Developer," "we," "us," or "our").

This Policy applies to personal information collected through the FieldGain mobile application, including profile data, calculation history, and information collected through third-party services integrated into the Application (Firebase, RevenueCat, Google AdMob).

FieldGain's current product policy is to target professional and vocational users aged 16 and over; it is not directed at children under 16. Applicable mandatory age, parental-consent, or consumer-protection requirements are not replaced by this product policy.

2. Information We Collect

We collect different types of information to provide, maintain, improve, and secure the Application. The table below summarizes what is collected, where it is stored, and for which product access level.

Identity fields: Your internal account identifier is randomly generated and pseudonymous; it is used to operate the account and is not your public identity. Pseudonymous does not mean anonymous: the UID and records linked to it may constitute personal data. A username is a unique public handle used where FieldGain presents an account identity. A display name is a nullable, non-unique profile field that may be present if a provider-linked account flow is made available. The current default account flow uses the pseudonymous username/handle as the public identity.

Authentication note: During sign-in, authentication credentials or tokens may be processed transiently to complete authentication. FieldGain does not store those credentials as profile or database fields.

Where a personal display name is present, it is intended for private Home, Profile, and Account personalization. It is not the username, is not used for username search or username reservations, and is not automatically used as the public account identity.

Where the Application presents an account identity, the username/handle rather than a personal display name is used as the public identity.

How information is collected: Some information is provided directly by you, such as consent choices, username or applicable profile changes, support messages, formula issue reports, and purchase or restore actions. Some information is generated automatically through application and backend operation, such as internal account identifiers, account/progression state, request and technical metadata, notification delivery identifiers, and analytics or diagnostics when enabled. Some information is received through integrated providers, such as provider-linked account data where such a flow is made available and RevenueCat or app-store subscription lifecycle data.

3. Local Storage (On-Device Data)

In addition to cloud data, the Application stores certain data locally on your device using a local database. This includes:

• Formula cache: Engineering formula definitions loaded from application assets, stored locally for offline use.
• Calculation history (Free): Your last 10 calculation-history entries, stored locally. These local Free history entries are not automatically archived to the Premium cloud-history collection merely because they exist on the device.
• Local onboarding and consent state: On-device onboarding and legal/consent state used to continue the onboarding flow and account consent handling.
• Cached account state: Cached account and subscription-tier state used for startup and offline continuity.
• Local quest state: Active quest progress and related local quest state used before claim or audit projection is reflected remotely where applicable.
• Calculation processing: Where required, certain formula/category, conditional-input, result, or request/version metadata may be transmitted to backend services for validation, reward handling, synchronization, duplicate prevention, or abuse protection.
• Offline intent queue: Pending synchronization and reward/progression intent metadata may remain locally until delivery resumes. These intents are securely signed and processed once connectivity is restored.
• User preferences: UI settings, selected language, and display preferences.

Some device-local data may be permanently lost if you delete the Application, clear app data, or reset your device. Accounts using the current pseudonymous account-access method receive normal Free product capabilities unless Premium is active, including the device-local Free calculation-history limit described above. A temporary state with no active account does not receive persistent calculation-history storage. Some device-local cache and preferences can be lost when application data is cleared or the application is removed.

4. How We Use Your Information

We use the collected information for the following purposes, as applicable:

• Provide and Maintain the Service: To create accounts, save your username and personal profile display name when applicable, save your Formula Area and preferences, manage your XP/Gear/streak progression, manage virtual economy and inventory state, save your selected character or avatar appearance, synchronize your Premium subscription status, and deliver calculation results.
• Profile Personalization: To present your personal profile display name in private Home, Profile, and Account surfaces. Where the Application presents an account identity, the public username/handle is used.
• Cloud Sync for Premium Users: To archive eligible calculation-history entries created while Premium access is active to FieldGain cloud services, enabling cloud-backed history and restoration of those archived entries after reinstalling the Application or switching devices.
• Security and Fraud Prevention: To verify reward and purchase-related activity through server-side integrity checks, enforce access and rate controls, and prevent abuse of the in-app economy.
• Application Improvement: When analytics consent is enabled, to use pseudonymous usage analytics and diagnostic/crash reporting to understand feature and formula usage, inform product and quality improvements, and diagnose failures. The documented FieldGain analytics event mapping does not intentionally include account email, personal display name, or raw calculation inputs or results; technical and error values may be processed where generated by the application. This includes the optional RevenueCat Ads ad-measurement path described below.
• Subscription Management: To process purchases via RevenueCat, validate and transfer Premium entitlements, apply grace periods, and maintain a single canonical owner per subscription.
• Customer Support and Formula Reports: To respond to support requests and investigate formula issue reports submitted through in-app reporting or email.
• Notifications and Messaging: To manage notification delivery and provide application or product announcements when notifications are enabled.
• Presence: To maintain online/presence and last-seen state where presence functionality is active.
• Advertising: To initialize the Google Mobile Ads SDK and, when permitted by consent/privacy controls, request and display banner or rewarded advertisements to non-Premium users. While Premium access is active, FieldGain does not request or display advertisements. When analytics consent is enabled, a separate RevenueCat Ads path may optionally receive ad-measurement metadata; it does not serve ads, verify rewards, or determine Loyalty.

5. Processing Conditions and Consent

We process personal data for the purposes described above only where an applicable legal condition permits that processing. The applicable condition depends on the data, purpose, role, and law; this page does not determine legal sufficiency for a particular activity.

• Service operation and requested functionality: To create and manage accounts, provide calculations, synchronize eligible history, manage subscriptions, and deliver requested service functions where necessary under the applicable law.
• Consent where required: We request separate consent for analytics and diagnostic or crash reporting and, where applicable, a data-abroad choice. Consent is distinct from accepting this Privacy Policy, may be withdrawn for future processing through available controls or by contacting us, and does not by itself determine every legal requirement for an international transfer. The analytics choice also controls optional RevenueCat Ads measurement: analyticsAccepted=true enables that measurement path, and false suppresses it. AdMob ad requests remain governed separately by UMP/ad-request consent and can continue under those rules.
• Security and abuse prevention: To protect the Application, detect abuse, maintain integrity, and maintain service stability where permitted by applicable law.
• Legal obligations and rights: Where processing is necessary for an applicable legal obligation or for the establishment, exercise, or protection of a right.

6. How We Share Your Information

FieldGain uses the third-party providers and platforms described below. Advertising-related processing may be subject to rights and controls under applicable U.S. state privacy laws, as described in Section 10. Their processing is governed by the applicable service terms, data protection terms, privacy controls, and privacy policies.

We may disclose your personal information if required by law, court order, or competent Turkish regulatory authority.

7. International Data Transfers

FieldGain uses external providers, and some processing may take place outside Türkiye. Depending on the feature, this may include pseudonymous account identifiers, technical/device and installation information, account or progression state, eligible Premium cloud history, analytics or diagnostics when enabled, advertising and consent data, subscription or purchase metadata, notifications, and support submissions.

These transfers may support authentication, service operation, security and integrity, cloud functionality, subscription and purchase management, advertising, notifications, analytics or diagnostics when enabled, and support. Some FieldGain backend resources are configured in Europe, including a documented Belgium region, but this does not describe all provider or subprocessor geography. RevenueCat has documented storage in the United States for some services, but that does not describe every part of the provider chain.

We record a separate data-abroad choice where applicable. That product choice is separate from the Privacy Policy and Terms acceptance, and it does not by itself determine every legal requirement for an international transfer. Applicable legal requirements and provider terms are handled separately.

8. Data Retention

We retain your personal data for as long as your account is active or as needed to provide the Service. More specifically:

• Active accounts: Core account, profile, progression, inventory, and applicable account state may be retained for the duration of the account, subject to the shorter retention or cleanup rules described below.
• Calculation history (Free, device): Stored on your device until you delete the Application or clear data; limited to your last 10 entries.
• Calculation history (Premium, cloud): Eligible cloud history is retained while needed for the Premium account service and is included in the FieldGain account-deletion process where applicable.
• Offline intent queue: Retained on device until successfully processed by our servers, after which it is cleared locally.
• Purchase/transaction records: May be retained after account deletion only for as long as necessary for applicable legal, accounting, audit, security, fraud-prevention, transaction-integrity, store or provider requirements. The applicable period depends on the record and the responsible system.
• Deleted accounts: Most personal data, including the root profile username and personal display name, is deleted as part of the account-deletion process. The username reservation is also removed as part of account cleanup. Some technical duplicate-prevention and abuse-prevention records may remain for up to 30 days before cleanup is complete.

9. Your Privacy Rights & Account Deletion

Depending on the law applicable to you, some or all of the following rights may apply regarding your personal data:

• Right of Access: Request a copy of the personal data we hold about you.
• Right to Rectification: Request correction of inaccurate or incomplete data.
• Right to Erasure ("Right to be Forgotten"): Request deletion of your personal data.
• Right to Restriction: Request restriction of processing where provided by applicable law and circumstances.
• Right to Data Portability: Request portability where provided by applicable law and applicable to the relevant data.
• Right to Object: Object where an applicable law provides that right for the relevant processing.
• Right to Withdraw Consent: Withdraw analytics or data transfer consent at any time.

Requesting a Copy of Your Data in FieldGain

Scope: The automatic package may include supported account, progression, eligible Premium cloud-history, subscription and billing-lifecycle, and selected support/request data. The automatic package may also include supported successful Quest claim history; active local Quest progress is not thereby cloud-exported. Free device-local calculation history is stored only on the device and is not included in this automatic cloud-generated package. Certain security, integrity, duplicate-prevention, transaction-reconciliation, or other operational records may also remain outside the automatic package. Third-party providers such as Google/Firebase, RevenueCat, Google Play, or AdMob may hold records in their own systems and retention lifecycles, which are not automatically represented in full.

Automatic Data Access package: A successfully generated in-app automatic Data Access response package is normally available for approximately 30 days. During that availability period, requesting another download uses the existing generated package rather than automatically generating a new copy. This is a product availability window, not a statutory request-frequency limit.

Technical lifecycle: FieldGain's current technical lifecycle may retain a minimal request/audit record for approximately 90 days. When a FieldGain account is successfully deleted, eligible FieldGain-owned automatic Data Access request/package artifacts covered by the deletion flow are deleted as part of that process instead of waiting for their normal technical lifecycle. Provider-side records, billing/legal/security exceptions, and copies already downloaded to the user's own device may follow separate rules.

This product feature does not remove, reduce, or impose a 30-day frequency limit on any privacy right that may apply under applicable law. For requests outside the automatic package, contact us at 24voltapp@gmail.com; identity verification may be required to help prevent disclosure of another person’s data.

Exercising Your Right to Erasure (Delete Account)

When you delete your account, FieldGain deletes eligible FieldGain-owned account, profile, and history data, removes account-scoped local data where applicable, and disconnects the account from connected sign-in, analytics, crash, and subscription services in the app. These account disconnect and reset actions do not by themselves establish deletion of all historical provider-side analytics, crash, subscription, purchase, advertising, or other technical records, which remain subject to provider policies, service terms, and applicable legal obligations.

To exercise any of the above rights, you may also contact us directly at 24voltapp@gmail.com. We respond within the period required by applicable law; for requests governed by KVKK, no later than 30 days.

10. US State Privacy Rights (CCPA)

For residents of California and other applicable US states, applicable privacy laws may provide rights regarding certain uses or disclosures of personal information. Google AdMob may process advertising and technical data as described in Section 6, subject to applicable Google, device, and privacy controls. While Premium access is active, FieldGain does not request or display advertisements.

11. Children's Privacy

FieldGain is not directed at children under the age of 16. We do not knowingly collect personal information from children under 16. If we become aware that we have inadvertently collected personal data from a child under 16 without appropriate consent, we will take steps to delete such data promptly. If you are a parent or guardian and believe your child has provided us with personal information, please contact us at 24voltapp@gmail.com.

12. Security

We implement reasonable technical and organizational measures to protect your personal data against unauthorized access, loss, or disclosure. These include:

• Access and authorization controls that restrict access based on authenticated identity and applicable service rules;
• Integrity checks for reward requests to help prevent tampering;
• Server-verified subscription and Premium status validation;
• Protected management of service secrets.

Selected account, request, or transaction identifiers may appear in operational or security logs for debugging, fraud prevention, duplicate prevention, and incident investigation.

No method of transmission over the internet or electronic storage is risk-free, and this Policy does not promise absolute security.

13. Changes to This Privacy Policy

We may update this Privacy Policy from time to time to reflect changes in our practices, technology, or applicable law. We will notify users of material changes through the Application or by updating the "Last Updated" date at the top of this page. Where a new or changed processing activity requires consent, that consent will be requested separately.

14. Contact Information

If you have any questions, concerns, or requests regarding this Privacy Policy or your personal data, please contact us at:

Developer: Mehmet BAŞCI
Email: 24voltapp@gmail.com
Website: www.24voltapp.com

© 2026 FieldGain — Mehmet BAŞCI. All rights reserved.