Last updated:
Hideva processes your images on your device. Some features, such as city search, advertising and purchases, use external services with their own data practices, described below.
1. About Hideva
Hideva provides Privacy Check, Editor and Stitch to identify sensitive details, edit and combine images before sharing them. The app has no user accounts, registration or login, and maintains no personal-profile database of its own on a server. This does not mean no data is collected: certain services and SDKs process data needed for the features described in this policy.
2. Images and screenshots
Images you select or share with Hideva are processed locally on your device. Text recognition (OCR), detection of face regions and QR codes, editing and Stitch composition take place within the app’s local workflows. Hideva does not implement screenshot uploads to its own servers.
The app may handle filenames, paths, dimensions, recognized text and detected regions to provide these features. It does not send this content to AdMob or Google Play Billing.
Hideva sends an image to another app only when you explicitly use Android sharing and choose the recipient. Subsequent processing, including any internet transmission, follows that app’s practices. Images saved to your gallery remain under your control and may be synchronized by photo services according to your settings.
Exporting does not guarantee that all image metadata is removed.
3. ML Kit and local analysis
Privacy Check uses Google ML Kit for Text Recognition, Face Detection and Barcode Scanning. Hideva does not send images or detected results to Google servers for analysis. According to ML Kit documentation, these inputs and results are processed on the device.
This does not mean the SDK makes no network connections. ML Kit may process technical metrics, performance, errors, app and device information, per-installation identifiers and usage information for diagnostics, maintenance and service improvement, according to Google’s documentation.
4. City and time zone
Hideva does not use GPS or request location permissions. You manually type and select a city, which does not necessarily correspond to your current physical location. Your search text is sent over HTTPS to Hideva’s Cloudflare Worker, which also queries Geoapify over HTTPS. No image or screenshot accompanies this query.
The developer has disabled persistent invocation logs and traces for the Worker. This does not prevent technical network processing by Cloudflare infrastructure, including IP addresses and connection metadata, needed to deliver and protect the service.
According to Geoapify’s policy, request data, such as content, headers, IP addresses and timestamps, is processed for usage control and diagnostics. Successful request data is generally retained for up to 24 hours; this period is not a blanket guarantee for all records.
Cloudflare and Geoapify may process IP addresses and normal technical metadata of the connections they receive to operate and protect their services. This does not mean Hideva sends your GPS position or that your device’s IP address is necessarily forwarded to Geoapify.
The selected city, state/region, country, country code, latitude, longitude, time zone and formatted description, when available, are stored locally. The coordinates represent the selected city, not a measurement of your position. This information is used to calculate local times for the weekly ad-free period.
Hideva’s code does not send your configured city, latitude, longitude or time zone to AdMob. The app also reads the time zone reported by the operating system to offer a travel notice. It does not automatically determine where you are or change your city without your choice.
5. Advertising and consent
The Free version uses Google AdMob for interstitial and rewarded ads. According to Google’s documentation and the feature used, Google Mobile Ads and UMP may process IP addresses and approximate location derived from them, Advertising ID, App Set ID or other identifiers, ad/app interactions, diagnostics and technical information, including stack traces and exception reports where applicable. Data may support advertising, measurement/analytics, fraud prevention, security and compliance. IP-based location estimates are independent of the city selected in Hideva.
Google’s User Messaging Platform (UMP) manages consent where applicable. Privacy options allow you to review your choices when made available by the SDK. The current ad configuration uses only the Google AdMob network/ecosystem.
From Friday sunset until Saturday sunset, calculated for your configured city, Hideva blocks ad requests and display. Ads are also blocked when the calculation is indeterminate. Hideva Pro remains ad-free. These advertising rules do not mean all communication from other services or UMP stops.
6. Purchases and Hideva Pro
Hideva Pro purchases and subscriptions are processed through Google Play Billing. The app receives information needed to recognize purchase or subscription status, unlock Pro, restore access and acknowledge transactions, such as the product, purchase status and transaction details supplied by the store.
Hideva does not receive or store payment card numbers, bank account details or payment credentials. Google Play and Google Payments handle information entered in the payment form. The Google account used by the store is not a Hideva account. Subscriptions are managed and canceled through Google Play.
7. Local data, cache and backup
The app may keep your selected city and its coordinates and time zone, preferences, usage and reward counters, ad frequency records and operational state locally. Some preferences and state exist only during the session.
Working images and temporary exports may occupy the cache. The app removes or replaces files in certain workflows but does not guarantee that every temporary file is deleted immediately after each use. Images you save to the gallery are separate from this cache.
Hideva disables Android backup with allowBackup=false and explicitly excludes private app data and local preferences from Android cloud backup and device-transfer rules. This includes the selected city and operational preferences. We do not guarantee the behavior of proprietary manufacturer mechanisms that may not respect these rules. These settings do not control images already exported to the gallery or data sent to external services.
Hideva has no dedicated Firebase Analytics or Crashlytics integration. This does not mean there is no telemetry: SDKs may process metrics, diagnostics and crash data as described above. Development builds may log processing times, dimensions and detection counts for debugging, without logging recognized image content in those logs.
8. Retention, deletion and your choices
Hideva has no user accounts and maintains no personal-profile database of its own on a server. It does not offer a dedicated mechanism to request account or remote-data deletion. The options below let you manage local data and external services; they are not a promise of remote deletion by email.
- You can change your city in Settings. The new selection replaces the previous configuration.
- Local data can be removed by clearing the app’s data or uninstalling it. This does not cancel subscriptions or erase records held by third parties. Hideva’s current rules disable backup and transfer of this data and exclude it from Android backup and transfer mechanisms. Any copies that may exist in proprietary manufacturer mechanisms or external services must be managed within those services.
- You must delete exported images from the gallery yourself. Shared or synchronized copies must be managed in the respective apps or services.
- Data processed by Google, Cloudflare or Geoapify follows those providers’ policies, retention periods and controls. We do not promise specific remote deletion deadlines that we do not control.
This policy does not limit rights under applicable law. The contact below is available for privacy questions and information. For data held by external providers, consult their channels and retention and deletion policies.
9. Security and this page
External transmissions identified in the app audit use HTTPS/TLS, including the app’s query to the Worker. The Worker’s query to Geoapify also uses HTTPS. No transmission or storage method provides absolute security.
This is a static page with no scripts, analytics, cookies or trackers included. When hosted on Cloudflare Pages, the infrastructure may process IP addresses and technical access metadata to deliver and protect the page according to Cloudflare’s policy. External links are accessed only when you open them.
10. Third-party services
Review the providers’ information. The links below open in a new tab.
- Google Privacy Policy
- Google AdMob — data disclosure
- Google UMP — consent and privacy options
- Google ML Kit — terms and privacy · data disclosure
- Google Play — terms of service
- Cloudflare Privacy Policy
- Geoapify Privacy Policy
11. Policy updates
This policy may be updated to reflect changes to the app, services used or applicable obligations. The updated version will be published on this page with a revised update date.
12. Responsible party and contact
Hideva operator and privacy contact:
