Privacy Policy

1. Who We Are

This policy applies to Gnomia, operated by Webagent. If you have privacy questions or requests, contact us at gnomia@webagent.eu, or Webagent (postal address available on written request).

2. Privacy Summary

• GPS logs stay on your device unless you explicitly choose to upload a specific adventure for support review.
• We upload game state files and limited technical diagnostics, linked to a uniquely generated user ID.
• We do not sell your personal data.
• We do not share your personal data with third parties for advertising or data brokerage.
• If you install Gnomia through one of our ads or links, we record which campaign led to the install so we can measure our own advertising. We do not use this for targeted advertising.

3. Data We Access and Collect

• Health and Physical Activity Data: We access and process location data to calculate your physical activity, specifically distance walked, as a core part of our gameplay (e.g., to track session progress and manage in-game companion exhaustion mechanics).
• On-device location data (GPS): used in-app for location-based gameplay features (such as placing and interacting with your garden in the real world) and ordinarily kept on device. A selected adventure is uploaded only after the player explicitly confirms a support report.
• Generated user ID: a random app-generated identifier used to associate cloud save snapshots. It is not based on your name or email unless you provide those in support communication.
• Website and gameplay analytics: we store a random first-party browser identifier for aggregate website visits and app-store badge clicks. Separately, the generated game user ID is used to record the first game open, onboarding completion, each level reached, the first day you walked at least 500 m and whether you walked on a second day within your first week (derived from the daily walking distance in your save), and failed cooking experiments (the cooking station plus selected ingredient types, item identifiers, and amounts). We use failed experiment data to understand aggregate recipe demand. We do not use these identifiers for targeted advertising.
• Install source (attribution): once per install, the app reports where it was installed from. On iOS, the app creates an attribution token with Apple's AdServices framework, which we send to Apple's attribution service. Apple tells us whether the install followed a tap on an Apple Search Ads ad and, if so, the campaign, ad group, keyword, ad, country or region, and whether it was a new download or a redownload. On Android, the app reads the Google Play install referrer, which contains the campaign parameters of the link that led to Google Play (for example a Google Ads click identifier or a click identifier from our website). The result is stored with your generated user ID. This does not use the iOS advertising identifier (IDFA) or the Android advertising ID, and no App Tracking Transparency permission is requested because no cross-app tracking takes place.
• Tracked links: when you open one of our campaign links on our website (for example from an ad or a creator's video), we store the campaign name, the time, the device type derived from your browser's user agent (Android, iPhone, or desktop), the random first-party browser identifier, a random click identifier, and the Facebook click identifier (fbclid) if the link was opened from Facebook or Instagram. On Android, the click identifier is passed to Google Play so the installed app can report it back as described above.
• In-app purchase details: for each purchase we store the product, purchase time, price, currency, and the store country. On iOS these come from Apple's signed transaction; on Android the app sends the price and currency shown by Google Play.
• Unity services and analytics: enabled Unity services may process pseudonymous device identifiers, IP-derived country, device and app information, session and gameplay interaction data, and information about in-app purchases and entitlements. We use this information to operate the purchase service and understand and improve the game, not for targeted advertising. See Unity's Game Player and App User Privacy Policy.
• Game state files: save data uploaded by the app to support backup/restore features.
• Optional support diagnostics: if a player chooses to send diagnostics, uploaded logs and save files may include technical details needed for troubleshooting. A player-initiated adventure report also includes the selected adventure's GPS session data and device information disclosed in its confirmation prompt.
• Automatic exception diagnostics: when the game records a software exception, it automatically sends the exception message, stack trace, up to 50 nearby log events before and after it, app and Unity versions, device platform and model, timestamp, and generated user ID. Full log and save files are not included in this automatic report.

4. How We Collect Data

• Location and Physical Activity permissions are requested through operating system runtime prompts.
• Where required by store policy, we show an in-app disclosure before requesting location permission explaining that Gnomia uses your location and physical activity data to power location-based gameplay, track distance walked, and that GPS logs are not uploaded as location history during normal gameplay.
• The generated user ID is created by the app and sent with save uploads.
• A random browser identifier is stored in a first-party cookie when the website is visited and reused when an app-store badge or campaign link is clicked.
• The install source is sent once, the first time the app connects to our server after installation or after this feature was added in an app update.
• Game state is uploaded when cloud backup features are used.
• Full support logs, save files, and selected GPS adventure data are uploaded only when the player explicitly initiates the corresponding support upload.
• A limited automatic exception report is uploaded when the game records a software exception. The client and server limit these reports to one per generated user ID every five minutes.

5. Why We Use Data

• Provide core location-based gameplay, which relies on calculating distance walked (Health and Physical Activity Data) to compute session progress and manage companion exhaustion mechanics.
• Store and restore cloud save snapshots tied to the generated user ID.
• Measure the aggregate path from website visits through app-store interest and gameplay progression so we can improve onboarding and retention.
• Measure the effectiveness of our own advertising: for each ad channel and campaign we compare aggregate numbers of installs, players who start walking, purchases, and revenue with what we spent.
• Diagnose software exceptions automatically and investigate support issues when players request help.
• Comply with legal obligations and enforce security protections.

6. Data Sharing and Third Parties

We do not sell personal data.

We do not share personal data with third parties for marketing, advertising, or data brokerage.

Unity Technologies processes limited app, device, analytics, and in-app purchase service data as described above. Apple and Google process purchases made through their respective app stores under their own account and payment privacy terms. To determine the install source on iOS, the attribution token is sent to Apple, which processes it under Apple's privacy policy. We do not send install, gameplay, or purchase data to advertising networks such as Meta or Google Ads.

If applicable, infrastructure providers acting only as processors to host or secure the service: backend hosting providers (to store cloud save snapshots and optional support diagnostics) and security/network providers (to protect service availability and integrity).

We may disclose limited data when required by law, court order, or to protect the rights, safety, and security of users and services.

7. Data Retention and Deletion

• On-device GPS logs: retained on device until app data is removed by the user or the app is uninstalled.
• Cloud save snapshots: retained until replaced by newer uploads or deleted upon request.
• Support diagnostics: retained for troubleshooting until deleted as part of routine maintenance or upon a valid deletion request.
• Automatic exception diagnostics: retained for bug diagnosis until deleted as part of routine maintenance or upon a valid deletion request.
• Install source and purchase details: retained together with your server-side profile and deleted with it upon a valid deletion request.
• Tracked link clicks: retained for advertising measurement until deleted as part of routine maintenance.

To request deletion of server-side data associated with your generated user ID, email gnomia@webagent.eu and include your generated user ID.

8. Security

We use reasonable administrative, technical, and organizational safeguards. Data sent between the app and backend is transmitted over encrypted channels (for example, HTTPS).

9. Your Choices and Rights

• You can control location permissions in your device settings at any time.
• You can request access, correction, or deletion by emailing gnomia@webagent.eu.
• You can delete local app data directly from your device settings.

10. Children and Age Requirements

Gnomia is not directed to children under 13 (or the minimum age required in your country). If you believe a child provided personal data, contact gnomia@webagent.eu so we can review and delete the data where required.

11. International Data Transfers

Data may be processed in the country where our backend infrastructure is located and in other jurisdictions where service providers operate. Where required, we apply appropriate safeguards under applicable law for cross-border transfers.

12. Changes to This Policy

We may update this policy from time to time. Updates will be posted on this page with a revised "Last updated" date.

13. Contact

Privacy contact: gnomia@webagent.eu
Contact form: mailto:gnomia@webagent.eu
Postal address: Webagent (postal address available on written request)

14. Store-Policy Consistency

Our App Store privacy information and Google Play Data safety declarations are intended to match this policy and our in-app disclosures. If practices change, this policy and store declarations are updated.