GreenScore Privacy Policy

This Privacy Policy explains how EntertainTech Solutions OOD collects, uses, shares, stores, protects and deletes information when you use the GreenScore app on iPhone (from the App Store) or on Android (from Google Play). Most of it applies to both. Where the two differ, the policy says so.

1. Who we are

GreenScore is developed and operated by EntertainTech Solutions OOD, a company registered in the European Union. It is the controller of the personal data described in this policy. For any privacy question or request, contact us at support@blowy.tech.

2. What GreenScore does

GreenScore estimates the green score of antlers and horns from photos you take or choose. It covers whitetail, mule deer, elk and pronghorn, and it can also recognize blacktail. It includes a manual scoring calculator, a shareable trophy card, a trophy room kept on your device, a map and feed of public statistics and totals from GreenScore users (section 7), and a Hunt Forecast for a U.S. county or a Canadian census division you choose (section 8). Scores are estimates only and are not official scores, and the forecast is an estimate, not a guarantee. The app has no user accounts: it never asks for an email address, a name, or a password, and there is nothing to sign up for.

On iPhone, the map and feed arrived in version 2.1, the forecast in version 2.2 and the additional animals in version 2.3. The Android app includes all of them from its first release.

3. Data at a glance

This table is a summary. The sections below give the details.

Data	Why	Who receives it	How long
Antler and horn photos you submit	To produce an AI estimate	Our server; OpenAI or Google (Gemini)	30 days on our server, then deleted automatically
Estimate records (options, measurements, score, status)	To deliver results and apply the subscription requirement and limits	Our server	Until you ask us to delete them (section 15)
Installation ID, platform, time zone, language, push token	To run estimates, subscriptions and notifications	Our server; Apphud; Firebase	Until you ask us to delete them; third parties under their own policies
Device identifiers (section 9)	Install attribution, campaign measurement, fraud prevention	Adjust; Meta; Apphud; Firebase	Under each service's policy
App activity, crash and performance data	To understand usage and fix problems	Firebase; Meta (app opens and purchases only)	Under each service's policy
Purchases and subscription status	To unlock GreenScore Pro and measure campaigns	Apple or Google; Apphud; our server; Firebase; Meta	Until you ask us to delete our copy; third parties under their own policies
Area you choose: state, province, county or census division	To run the map, feed and forecast	Our server only, never analytics or attribution services	Sections 7 and 8
IP address	Security, abuse prevention, and a suggested forecast area	Our servers; third-party services the app connects to	In access logs, as described in section 6
Forecast check-ins	To improve the forecast model	Our server	Until you ask us to delete them; those without an identifier are not linked to you
Feedback and support emails	To improve the app and help you	Our server; our email provider	Until you ask us to delete feedback; emails only as long as needed
Trophy room, notes and settings	So you can keep and use them	Nobody: they stay on your device	Until you delete them or uninstall the app

4. Antler and horn photos

When you request an AI estimate, the one to three photos you submit are uploaded to our servers over an encrypted connection (HTTPS) solely to produce your estimate, together with the options for that scan (the animal if you picked one, a scale reference, and a point count if you entered one). We access only the photos you explicitly submit, never your whole photo library.

• Processing. Our servers send your photos to our AI service providers, OpenAI and, as a configurable alternative provider, Google (Gemini), which analyze them and return measurements. These providers act on our behalf and process the photos only to deliver the estimate to us. We also run an automated safety check to reject inappropriate images.
• Metadata. Our server re-encodes each photo when it saves it, which removes location and other metadata embedded in the file.
• Retention. Uploaded photos are kept on our servers for 30 days, which also lets you change the animal without scanning again, and are then deleted automatically.
• No other use. We do not use your photos to build advertising profiles, we do not publish or show them to other users, and we do not sell them.
• Please keep people out of the frame. These photos are not intended to contain personal information; avoid including faces, license plates, or documents.

The manual calculator does not upload anything: measurements you enter are scored on your device.

5. What stays on your device

• Your trophy room: saved trophies, their photos, scores, measurements, dates, the state or province you select, and your notes.
• Trophy cards you create, until you share or save them yourself.
• Your app settings, including the area you chose for the Hunt Forecast (a U.S. state and county, or a Canadian province and census division; section 8) and your home state for the Feed.
• Hunt Forecast notifications, if you turn them on: they are scheduled on your device (section 8).
• A cached copy of the latest map and feed, so they can load offline, and any scans or map changes still waiting to be sent.

This data lives locally in the app's private storage on your phone. We do not receive it, and it is removed when you delete it or uninstall the app. Trophies do not move between iPhone and Android. On Android, the app is excluded from Android's automatic backup, so this data is not copied to your Google account. On iPhone, it can be included in device backups you make yourself.

The exceptions are the optional map entry described in section 7 and the Hunt Forecast described in section 8, which sends the code of the area you chose to get a forecast and, only if you submit one, a check-in. GreenScore does not use GPS or your device's location. Any state, province, county or census division is one you chose or confirmed yourself (the forecast may suggest one based on your IP address, section 8).

6. What we send to our servers

Besides the photos described in section 4, the app registers your installation with our service so that estimates, subscriptions and notifications work. GreenScore has no accounts, so this is the record we hold for your installation. Our server receives and keeps:

• Your installation ID. This is the user identifier created by our subscription provider, Apphud. It is tied to your installation of the app, not to your name or email address. In the support email draft it appears as "User ID".
• Your platform (iOS or Android), your device's time zone, the language your device reports, if any, and when the record was created and last active.
• Your push notification token, so we can tell you when an estimate is ready if you allow notifications.
• Your subscription status, which reaches us from Apphud, so that AI estimates can be unlocked.
• A record of the estimates you request: time, status, the options for the scan, the resulting measurements and score, the country of the request if our infrastructure supplies one, and a statistics entry with your installation ID, the score and technical details such as which AI engine ran and how long it took. We use it to deliver results and to apply the subscription requirement and fair-use limits. On iPhone it can also include the Apple DeviceCheck token described in section 12.
• Feedback you choose to send in the app: your rating, the reason you pick, anything you type, your platform and your installation ID.
• If you use the community map or feed: the map entry and the home state described in section 7.
• If you use the Hunt Forecast: the county or census division code in forecast requests, a request for a suggested area if you have not chosen one yet, and any check-ins you choose to send, described in section 8.

Server logs. Like most web services, our servers and the web server in front of them keep standard access logs for security, abuse prevention and troubleshooting. An entry holds your IP address, the time, and the address that was requested. That address can include a state, county or census division code (for a state's map page or a forecast request) and your installation ID (when the app checks on an estimate). Our application's own request log leaves out map, feed and forecast addresses. Your home state for the Feed is not in the web address, so it is not in these logs (section 7). When the app asks for a suggested forecast area, the suggestion itself is not recorded (section 8). These logs are not sent to analytics or attribution services. We keep access logs only as long as we need them for these purposes, and our application's request log is overwritten as it fills up, usually within a few months.

7. Community map and feed

The Map and Feed tabs show public statistics and facts, plus totals from GreenScore users. There are no profiles, posts, comments or user photos: you never see another person's trophy or identity, and nobody sees yours.

• "Count my buck on the map". After an AI estimate of a whitetail, the result screen shows this option with a short explanation. It is on by default for new whitetail AI estimates, and you can switch it off on the result screen or later on the trophy's screen. Other animals and manual-calculator results are never counted, and neither are trophies saved on iPhone before version 2.1. Nothing is sent until the option has been shown to you.
• What we receive when it is on. The U.S. state or Canadian province, and a U.S. county only if you pick one (in Canada we count whole provinces only). The score comes from our own record of that estimate. The state or province is the one you chose for that trophy or, if you have not chosen one, the home state you set in the Feed. We do not use GPS or ask for your location, we do not send the photo or your name, and we do not store coordinates.
• How your entry is stored. The app labels this option "Anonymous" because that describes what other people get: they never see an individual entry, your name or your photo. On our server, however, the entry is linked to your installation. It is stored with the ID of the estimate record, and that record contains your installation ID (section 6). It is also stored with a one-way, salted hash of your installation ID, so that one person is not counted many times. A hash like this is a pseudonym, not anonymity: we can recalculate it from your installation ID. We also keep the time, week and season of the estimate.
• What other people can see. Only totals, never an individual entry. A state's figures appear only when at least 5 different people have counted a buck there in that period, and are shown as AI estimates (about ±15 inches), not official scores; a highest score is shown only when at least 10 people have counted. A county shows only the number of hunters, and only when at least 5 people in that county have counted. Below these thresholds the app simply says that fewer than 5 hunters have been counted. Entries with an unusually high or low score can be held out of the totals. Totals refresh about once a day.
• Home state for the Feed. If you set a home state, the app sends it with feed requests, in a request header rather than in the web address, so the Feed can show cards for your state. We do not keep it in our request logs, and it is not sent to analytics. As described above, it may also be used as the state for a map entry when a trophy has no state of its own.
• Public data and news. The map and feed show public harvest statistics published by state and provincial wildlife agencies, season dates linked to the official regulations, one-line news summaries written by us with a link to the source (for example the National Deer Association and state wildlife agencies), and boundaries from the U.S. Census Bureau and Statistics Canada. The app lists sources and dates. Links open outside the app, and we do not send those sites any information about you; once you open one, that site's own privacy policy applies. Season dates can vary by zone, so check the official regulations.
• How to remove your entry. Switch "Count my buck on the map" off on the result screen or the trophy's screen, or delete the trophy in the app; either removes the entry from the map while it is still linked to the estimate record (see the next point). If you are offline, the removal is sent when you are back online. Deleting the app alone does not remove an entry, so switch the option off first, or ask us to delete it through our GreenScore Data Deletion page. Totals that have already been published update the next time they refresh.
• How long the link lasts. When the hunting season is over (about 30 days after the last state's season closes), and once an entry has gone at least 30 days without a change, we remove the link to the estimate record. From then on the switch in the app can no longer find the entry, but you can still ask us to delete it, because we can find it by the hash. 400 days after an entry was created we also erase the hash. The entry that remains (score, state or province, optional county, and the time, week and season of the estimate) stays in our statistics and no longer carries an identifier.
• Location. The state, province and county are location information that you provide yourself. They are coarse, are used only to run the map and feed, and are not used for advertising or tracking and not shared with analytics or attribution services.

8. Hunt Forecast

The Hunt Forecast is an hour-by-hour "hunt rating" for the next 7 days for a U.S. county or a Canadian census division ("County / region") you choose, based on the time of day, the timing of the rut and the weather. It is a heuristic estimate, not a guarantee and not a prediction of how animals will behave.

• Location. The forecast does not ask for your device's location and does not use GPS. You pick a U.S. state and county, or a Canadian province and census division, yourself. The area's code (a standard FIPS code for a U.S. county, or the Statistics Canada identifier for a census division) is stored on your device and is sent to our server in the web address of a forecast request and in any check-in you send. Our application's request log leaves it out and it is not sent to analytics, but the standard access logs described in section 6 can contain that address. To calibrate the forecast model, our server keeps the ratings it calculates for each area; these contain no user identifier.
• Suggested area (based on IP address). If you have not chosen an area yet, the app asks our server for a suggestion. Our server estimates your approximate location from the IP address of that request, using an offline copy of the DB-IP "IP to City Lite" database (no information is sent to DB-IP), and suggests the nearest county or census division within that state or province. The suggestion is not saved automatically: you confirm it with "Continue" or choose a different area. We do not store the suggestion. The standard access logs described in section 6 keep the IP address, the time and the requested address, without the suggestion. No GPS is used and no location permission is requested.
• Weather. Our server requests the weather forecast from Apple Weather (WeatherKit) for the center of the county or census division, not for your position. This is the same on iPhone and Android. For U.S. counties, if Apple Weather is unavailable, it uses the U.S. National Weather Service (api.weather.gov) instead; for Canada only Apple Weather is used. No personal information is sent to either service. The app shows the Apple Weather attribution with a link to its data sources.
• Rut dates. Rut timing comes from published sources such as state and provincial wildlife agencies, linked in the app. The app does not send those sources any information about you.
• Check-ins (optional). You can send a check-in after you have hunted: the county or census division, the date, the hours you sat (from and to), the animal, the number of animals you saw, and whether you saw a buck or bull. No GPS or coordinates are included. If your installation is registered with our service (section 6) when you send it, the check-in is stored with the same one-way, salted hash of your installation ID as map entries (section 7), which is a pseudonym, not anonymity; otherwise it is stored with no identifier. Check-ins are used only to improve the forecast model. They are not sold and not used for advertising. To have check-ins linked to your installation deleted, use our GreenScore Data Deletion page; check-ins stored without an identifier are not linked to you.
• Forecast notifications (optional). There are two kinds: rut alerts, which do not need a subscription, and great-day reminders such as "tomorrow looks like a good morning", which need GreenScore Pro. They are local notifications scheduled on your device; our server does not use your push token for them. You can turn them off in the app or in your device's notification settings. Great-day reminders are kept up to date by occasional background work on your device: Background App Refresh on iPhone, and scheduled background work about every 6 hours on Android, only while these reminders are on.
• Analytics. We record forecast usage events (for example, viewing the forecast, choosing a day, tapping a locked item, turning on notifications, the fact that a check-in was sent, whether you saw deer or a buck in it (yes or no), or whether you chose your area manually or accepted the suggestion). These events never include the area itself (state, province, county or census division) or the number of animals you saw.

9. Analytics, attribution and identifiers

• Usage and diagnostics. App-usage events (for example, opening a screen, or completing an estimate along with its score and animal) and crash and performance diagnostics, collected through the third-party services listed in section 12, along with general device and app information such as model, system version and app version. We use your installation ID as the user identifier in Firebase Analytics, so these events are linked to your installation. These events never include the state, province, county or census division you choose for the map, feed or forecast, or the number of animals in a forecast check-in.
• Device identifiers on iPhone. The Identifier for Vendor (IDFV), which is specific to our apps on your device, is available to these services. The Identifier for Advertisers (IDFA) is used only if you allow tracking in Apple's App Tracking Transparency prompt; if you decline, it is not collected.
• Device identifiers on Android. The Android advertising ID is available to Adjust, Meta, Apphud and Firebase Analytics for install attribution and campaign measurement, and Google Play's install referrer tells Adjust how the app was installed. Android does not show a tracking prompt for this; section 11 explains how to delete or reset the advertising ID. Apphud may also read the Android ID; we do not use it for advertising. The App Set ID, which is shared by apps from the same developer on your device, may also be available to these services. We use it only for analytics and fraud prevention. We do not use it for ad personalization or ad measurement, and we do not connect it to the advertising ID or to personal data for advertising purposes.
• Attribution data. Apphud also receives the attribution result from Adjust and the Firebase app instance ID, so that subscriptions can be matched to the campaign that brought you to the app. On iPhone, the app also sends an Apple Ads attribution token to Apphud.
• Subscription status and purchases. Whether you hold an active subscription, managed through Apple or Google Play and our subscription provider. Purchase events, with the product, price and currency, go to Firebase and Meta to measure our campaigns. We never receive your payment card details.
• Support information. Anything you voluntarily send us by email.

10. How we use information

• To estimate scores from the photos you submit and notify you when an estimate is ready.
• To show the community map and feed, including totals from users whose estimates are counted, and to personalize the feed to your home state.
• To provide the Hunt Forecast for the area you choose (and, before you choose one, to suggest an area based on your IP address), its notifications if you turn them on, and to improve the forecast model using our calculated ratings for each area and the check-ins users choose to send.
• To operate and improve the app, understand feature usage, read feedback and fix crashes.
• To measure the performance of our marketing and app installs, subject to your choices in section 11.
• To manage subscriptions, unlock premium features, restore purchases, and apply fair-use limits.
• To help prevent abuse and fraud, including automated or repeated misuse of the service.

11. Advertising measurement and your choices

GreenScore does not show ads. We use advertising measurement to understand which campaigns bring people to the app.

• On iPhone. iOS asks, through Apple's App Tracking Transparency prompt, whether you allow tracking across other companies' apps and websites. If you decline, the advertising identifier (IDFA) is not collected or used to track you. Your choice can be changed at any time in Settings → Privacy & Security → Tracking.
• On Android. There is no such prompt. You can delete your advertising ID in Settings → Privacy → Ads → Delete advertising ID; apps then receive a string of zeros instead of the ID. You can also reset it on the same screen. On some older Android versions the setting is Settings → Privacy → Advanced → Ads → Opt out of Ads Personalization. Menu names can vary by device.

12. Third-party services: who receives data

We use the following services, each governed by its own privacy policy:

Both platforms

• OpenAI analyzes the photos you submit to produce your estimate. openai.com/policies/privacy-policy
• Google (Gemini) may be used as an alternative provider to analyze the photos you submit. policies.google.com/privacy
• Google Firebase (Analytics, Crashlytics & Cloud Messaging) provides usage analytics, crash reporting and push notifications. It receives your installation ID, usage and purchase events, crash and performance data, device information, the push token and, where available, the advertising identifier. firebase.google.com/support/privacy
• Adjust provides install attribution and marketing measurement. It receives device and app information, your IP address, and an advertising identifier (on iPhone only if you allow tracking). adjust.com/terms/privacy-policy
• Meta (Facebook SDK) provides attribution and measurement of our ad campaigns on Facebook and Instagram. It receives app opens, purchase events, device and app information, and an advertising identifier (on iPhone only if you allow tracking). facebook.com/privacy/policy
• Apphud provides subscription management on top of Apple's and Google Play's in-app purchases. It creates your installation ID and receives purchase and subscription data, paywall views, device information, device identifiers and attribution data. apphud.com/legal/privacy
• Apple Weather (WeatherKit) provides weather forecasts for the Hunt Forecast. Our server requests them for the center of the county or census division you chose, not for your position, and sends no personal information (section 8).
• U.S. National Weather Service (api.weather.gov) is a backup weather source for the Hunt Forecast in the United States only, used in the same way as Apple Weather; no personal information is sent.
• DB-IP provides IP geolocation for the suggested forecast area. We use an offline copy of the DB-IP "IP to City Lite" database on our own server, so no information is sent to DB-IP (section 8). IP geolocation by DB-IP, licensed under CC BY 4.0.

iPhone only

• Apple provides the App Store, in-app subscriptions and platform services. apple.com/legal/privacy
• Apple DeviceCheck. The app may send an Apple DeviceCheck token with AI-estimate requests, which we may use to help prevent abuse. It stores two bits of state per device with Apple and involves no personal data.

Android only

• Google Play provides app distribution, Google Play Billing for subscriptions, and the install referrer. Google processes your payment; we never receive your payment card details. policies.google.com/privacy

The map and feed also display public information from state and provincial wildlife agencies, the National Deer Association, the U.S. Census Bureau and Statistics Canada (section 7), and the Hunt Forecast uses rut dates from published sources (section 8). These are information sources: the app does not send them any information about you. Statistics Canada data: Contains information licensed under the Open Government Licence – Canada.

13. Permissions

GreenScore asks for a permission only for the feature that needs it. Every permission you are asked for is optional, and you can change your choice at any time in your device's settings. GreenScore does not request access to your location, microphone or contacts on either platform. The area for the map, feed and Hunt Forecast is something you choose in the app, not read from your device; an area suggested from your IP address is used only after you confirm it (section 8).

On iPhone

• Camera: to photograph antlers or horns for an estimate.
• Photos: to pick an existing photo, and to save trophy cards to your library. Only the photos you choose are accessed.
• Notifications: to tell you when an estimate is ready and, only if you turn them on, for Hunt Forecast notifications scheduled on your device (section 8).
• Background App Refresh: used only to keep great-day reminders up to date. You can turn it off in Settings → General → Background App Refresh.
• Tracking: Apple's App Tracking Transparency prompt, so we can measure which ad campaigns brought you to GreenScore (section 11).

On Android

• Camera: to photograph antlers or horns for an estimate. You are asked the first time you use it.
• Photos: the app uses Android's photo picker, so it receives only the photos you choose and does not ask for access to your library. Saving a trophy card adds it to your gallery; older Android versions may ask for storage access for this.
• Notifications: to tell you when an estimate is ready and, only if you turn them on, for Hunt Forecast notifications scheduled on your device. Android 13 and later ask for your permission first.

Android also lists some permissions that do not show a prompt: network access, Google Play Billing, the advertising ID permission (section 11), and running background work and restoring scheduled notifications after your phone restarts (section 8).

14. Sharing of information

We share information only with these types of parties, and only as described in this policy:

• AI providers (OpenAI, Google) receive the photos you submit, to produce your estimate.
• Analytics, attribution and advertising measurement services (Firebase, Adjust, Meta) and our subscription provider (Apphud) receive identifiers, app activity and purchase events.
• Store and payment platforms (Apple, Google Play) handle downloads and subscriptions.
• Weather services receive only the location of the center of the county or census division (section 8).
• Other GreenScore users see only totals that meet the thresholds in section 7, never your individual entry.
• Authorities or others where the law requires it, or where needed to protect our rights and users' safety, or as part of a sale or reorganization of our business.

We do not sell your personal information for money, and we do not share your photos with advertisers or data brokers. We do share identifiers and app activity with Adjust and Meta to measure our ad campaigns. Some U.S. state privacy laws may treat this as "sharing" or "selling" personal information. You can limit it as described in section 11. Forecast check-ins are used only to improve the forecast model and are not sold or used for advertising.

15. Data retention

• Uploaded photos: 30 days on our servers, then deleted automatically.
• Estimate records and their statistics entries, the installation registration and in-app feedback: these have no fixed expiry date today. We keep them so results, limits and subscriptions keep working and so we can improve scoring, and we delete them when you ask (section 16).
• Map entries: as described in section 7. They are removed when you switch the option off or delete the trophy while the link exists, the link is cut after the season, and the hash is erased after 400 days.
• Forecast check-ins: those linked to your installation by the hash have no fixed expiry date today and are deleted on request. Check-ins without an identifier and our calculated area ratings are not linked to any user.
• Server logs: kept only as long as we need them for security, abuse prevention and troubleshooting (section 6). Our application's request log is overwritten as it fills up, usually within a few months.
• Your trophy room and settings: on your device until you delete them or uninstall the app.
• Third-party services: data they handle is retained according to their respective policies. Purchase records are also held by Apple or Google.
• Support emails: kept only as long as needed to help you.
• Legal requirements: we may keep specific records where the law requires it, or where needed for security or to prevent fraud.

16. Deleting your data

You can request deletion of the data we hold for your installation by email. There is no account to close and no deletion screen in the app. In the app, open Settings → Contact Us, and ask us to delete your data, keeping the "User ID" line in the draft: GreenScore has no accounts, so your installation ID is the only way we can find your data. We confirm by email and complete the deletion within 30 days of your request.

The GreenScore Data Deletion page gives the full steps, what is deleted, and what is kept and for how long. Deleting your data does not cancel a subscription: cancel it in the App Store or Google Play.

17. Your choices and rights

• Revoke camera or photo access, or turn off notifications, in your device's settings: on iPhone in Settings → Privacy & Security and Settings → Notifications, and on Android in Settings → Apps → GreenScore.
• Change your tracking choice on iPhone, or delete or reset your advertising ID on Android (section 11).
• Switch off "Count my buck on the map", or delete the trophy, to remove your map entry (section 7).
• Turn Hunt Forecast notifications off in the app or in your device's settings; check-ins are optional (section 8).
• Delete your on-device data by removing trophies or uninstalling the app.
• Depending on where you live (for example under U.S. state privacy laws such as the CCPA, Canada's PIPEDA, or the GDPR), you may have the right to request access to, correction of, or deletion of your personal data. To use these rights, contact us at support@blowy.tech with your installation ID. We will not treat you differently for doing so.

18. Legal bases for processing (GDPR)

EntertainTech Solutions OOD is registered in the European Union. Where the General Data Protection Regulation (GDPR) applies, we rely on these legal bases:

• Contract (Art. 6(1)(b)). Producing estimates from the photos you submit, delivering results and estimate-ready notifications, providing the map, feed and forecast, and managing subscriptions and purchases.
• Legitimate interests (Art. 6(1)(f)). Keeping the service secure and preventing abuse (including access logs and fair-use limits), fixing crashes, understanding usage, reading feedback, improving scoring and the forecast model, counting people on the map once each, and measuring our marketing where consent is not required, including through the advertising ID on Android (section 11). You can object to processing based on legitimate interests at any time.
• Consent (Art. 6(1)(a)). Using the advertising identifier on iPhone, if you allow tracking in Apple's prompt, and the device permissions you grant. You can withdraw consent at any time in your device's settings; this does not affect processing that took place before.
• Legal obligation (Art. 6(1)(c)). Records we must keep by law, and responses to lawful requests.

Where the GDPR applies, you have the right to access your personal data, to have it corrected or erased, to restrict processing, to data portability, and to object. You can use these rights at support@blowy.tech. You also have the right to lodge a complaint with a data protection supervisory authority, in particular where you live or work.

19. Children's privacy

GreenScore is not directed to children under 13, and we do not knowingly collect personal data from children under 13. If you believe a child has provided us with personal data, contact us and we will delete it.

20. How we protect data

• All traffic between the app and our servers uses HTTPS, so it is encrypted in transit.
• An estimate is tied to the installation that requested it and is not available to other users in the app.
• Uploaded photos are re-encoded to remove embedded metadata, stored under generated file names that are not published or shown to other users, and deleted automatically after 30 days.
• Map entries and check-ins do not contain coordinates, and they store a salted hash rather than your installation ID itself (a map entry also links to its estimate record until that link is removed, section 7). The area you choose is kept out of our application's request log and out of analytics.
• Access to our servers, databases and admin tools is limited to the people who need it to run the service.
• On your phone, trophies are kept in the app's private storage.

No system is completely secure, but we work to safeguard the information involved. If you think you have found a security problem, write to support@blowy.tech.

21. International users

Our company is registered in the European Union, and our servers and the third-party services we use may process data in other countries, including the United States. Where required, such transfers rely on safeguards such as standard contractual clauses or the EU-U.S. Data Privacy Framework, as described in those providers' terms and privacy policies.

22. Changes to this policy

We may update this Privacy Policy from time to time. Material updates will be reflected by changing the "Last updated" date on this page.

23. Contact us

For questions about this Privacy Policy or to submit a privacy request, contact EntertainTech Solutions OOD at support@blowy.tech. See also the GreenScore Terms of Use.