MeterRound Privacy Policy

Updated: October 7, 2026. This policy describes the MeterRound 0.4.3 Android app, this website at meterround.com and our communications, including the optional MEA NETZE chat at support.meanetze.com. App work records, technical data from Google services and website data are explained separately below. An app that works locally does not mean that the website, Google Play or integrated SDKs process no data.

1. Controller and contact

MEA NETZE, proprietor Franjo Pehar
Industriestraße 7
63165 Mühlheim am Main
Germany
Email for privacy and support: [email protected]

We are responsible for website and support data processing within our control. MeterRound does not give us remote access to your work records. If you record personal information about tenants, customers or other people for your organisation, your organisation decides the purpose, legal basis, authorised users and retention. Direct privacy requests about records held exclusively locally to the relevant controller.

2. Work records in the Android app

MeterRound stores the information you enter or select in local app storage: properties and addresses, spaces, contacts and access instructions, meter identifiers and locations, readings, times, notes, drafts, reading history, photos and reports. An optional profile may include your name, organisation and logo; settings are also stored locally. These records may be personal data when they can be linked to people or households. Record only information necessary for your purpose.

Field work operates without a separate MeterRound account and without app cloud synchronisation. Work records are not automatically uploaded to us. The app does not request location permission or continuously record GPS positions. Manually entered addresses and selected images can nevertheless contain location information. The app does not read your address book.

3. Text recognition, barcodes and Google ML Kit

OCR and barcode recognition use Google ML Kit models included in the app. The selected image is processed on your device; we do not use a cloud image-recognition service for it. A recognition image is not automatically saved as a work photo. Temporary processing copies are cleaned up. Check recognised identifiers and readings before accepting them.

Google nevertheless discloses technical data collection by its Android ML Kit SDKs: device manufacturer and model, operating system, app package and version, installation identifiers, performance data, configuration such as image format and resolution, input/output sizes, feature events and error codes. Google uses these data for diagnostics and usage statistics. Technical transmission can take place through Google Play services. The app's lack of its own INTERNET permission does not exclude this SDK processing. Transmitted technical sizes are not the image content of your reading.

We use ML Kit to provide the recognition feature you request. To the extent we process personal data for this purpose, Article 6(1)(b) GDPR applies to the requested service; necessary technical protection relies on Article 6(1)(f) GDPR. Google's own processing is explained in its Privacy Policy and ML Kit data disclosure. MeterRound has no separate switch for this SDK telemetry. This website's cookie choice does not control it. You can choose not to use OCR or barcode recognition and enter readings manually.

4. Google Play, Pro subscriptions and optional reviews

MeterRound integrates Google Play Billing for monthly and annual Pro subscriptions. Google Play processes the purchase, payment and account data, restoration and subscription management. The app receives purchase data such as product identifier, purchase token, purchase status and signature to check Pro entitlement, but no payment card details. Verified purchase and verification data are cached locally separately from the work database; offline Pro entitlement lasts up to seven days after a successful check. Purchase, restoration and regular checks require Google Play and internet. We do not operate our own subscription server. Processing to provide and verify your Pro service relies on Article 6(1)(b) GDPR; legal duties rely on point (c).

An optionally entered reviewer access code is verified and stored locally. It is separate from a Play purchase and excluded from work-data backups. Removing it does not delete work records or cancel a Play subscription.

The app can also offer an optional Google Play review. Your rating and entered text go to Google Play and can appear there publicly with your Play profile information. We can see the published review; the app does not receive its text from the review dialog. You may decline and manage or delete published reviews through your Google account or Google Play. Providing a voluntarily requested review feature is part of the service; publication follows your decision and Google's terms. MeterRound does not use its own advertising or website-tracking SDK in the app. The ML Kit collection described above remains separate.

At launch or when returning to the app, it queries Google Play for available offers and existing purchase entitlement. To space optional review prompts, the app locally records use dates, counts of app entries and saved photos, and the last attempt. These control records are excluded from work-data backups and are not sent to us as a separate analytics report.

5. Photos, permissions, PDF/CSV and sharing

You can open a camera app or grant access to individual images through Android's picker. Access serves the capture or file you select. Older Android versions may require storage permission for an optional gallery copy. Work photos are stored internally; an additional gallery copy is a separate setting. Original images may contain metadata such as capture time, device or location. We do not guarantee removal of all metadata. Your camera, gallery or chosen file service may use its own backup or cloud features.

PDF/CSV reports and backups are created or saved on your action. When sharing, you choose the receiving app and destination. They may process or upload data under their own rules. Check contents and destination before sharing. Under the intended export model, external reports exclude structured contact and access instructions; freely entered text and selected photos can nevertheless contain sensitive information. Selected exports, gallery copies and backups are independent copies outside our access.

6. Device protection and backups

The app uses Android app storage. Automatic Android cloud backup and Android device-to-device transfer of app data are excluded in the app configuration. Manual backup starts only on your action and saves to the location you select. Backup encryption is optional and must be selected. Without that choice, the backup is not protected by app backup encryption. When encryption is used, the backup password is not stored; keep it safe yourself. Restoration replaces the work dataset rather than automatically merging it.

The optional access lock uses your existing Android device authentication. Your device PIN is not transmitted to us. This lock and protection against screen captures do not promise additional encryption of the work database or previously exported files. Protect your device, backups and recipient access yourself; absolute security cannot be promised.

7. Keeping and deleting local app data

Work data remain on your device until you remove them using the provided features, replace them through restoration or clear local app data. Historical records may be preserved for traceability; archiving is not deletion. The delete-all-work-data feature removes work records and internal work photos/reports while retaining your profile and settings. For a full reset, clear app data through Android; uninstalling can also remove local app data. Back up documents you need first.

Externally saved PDF/CSV files, backups, gallery copies, files already sent, support messages and Google Play purchases/reviews are not deleted by this action. Delete those copies at the relevant storage location, recipient or service. Your organisation determines necessary retention and legal evidence duties. We cannot remotely delete work data stored exclusively on your device.

8. Website, hosting and technical connection data

meterround.com and the central support service use the existing Namecheap shared hosting. Access to the services processes technical connection data for delivery, operation, troubleshooting and protection, including IP address, time, requested address, response status and browser/device information. Hosting and security logs are separate from support conversation contents. Namecheap receives the data necessary for hosting and protection; authorised administrators may process them to carry out those tasks.

The legal basis is Article 6(1)(f) GDPR: our interest in an operational, secure website and prevention of abuse. Technical data are needed only for as long as operation, investigation of faults/security incidents and any legal duties require. This policy does not promise an unverified fixed log-retention period.

This website uses no optional website analytics, advertising trackers or automatically loaded Google Maps/video embeds. Its own fonts, images and presentation files are served through the hosting. External links lead to the relevant provider when you open them; that provider's rules then apply. Google service processing in the Android app is explained in sections 3 and 4.

The meterround.com website also uses Cloudflare, Inc., United States, as a proxy for delivery and security. Cloudflare processes IP addresses, connection and request data and may maintain technical security/network logs. The basis is Article 6(1)(f) GDPR for reliable delivery and protection from attacks. Cloudflare explains its own processing purposes and processing on behalf of customers in its Privacy Policy.

9. Email, contact form and support

If you contact us voluntarily, we process your contact details, message, supplied app/device version, problem description and deliberately attached files to answer and handle your request. An email address or necessary follow-up details are needed if you want a personal response; without a message your issue cannot be handled. The ordinary contact route remains available without consent to optional chat. A form you submit is communication you expressly request, not consent to analytics or the chat widget.

Contractual and pre-contractual requests rely on Article 6(1)(b) GDPR; other requests on point (f), reflecting our interest in useful, secure customer communication. Legally required documentation relies on point (c). Hosting, the email services used for correspondence and recipients you select process the necessary data. Opening your email app alone does not send a message. Do not send passwords, access codes, full backups or unnecessary personal business data; anonymise examples where possible.

10. Optional MEA NETZE support chat

Chat uses our own platform at support.meanetze.com. The widget and restoration of its browser access start only after you explicitly allow Contact/Chat in Cookie settings. This category is off by default.

When you submit a chat, we process your name, email address, messages, product/website, language, source-page origin and path without query parameters or URL fragment, and handling status. Conversations are stored in the protected MySQL Inbox. Deliberately selected JPEG, PNG, WebP or PDF attachments are stored in private directories. Chat does not access local app work records. Files transfer only after you expressly select and send them; they may contain original metadata.

Origin checks, a protective field, size limits and time-windowed HMAC values for request limits protect the service. The IP address is not a conversation field; hosting/security logs may include it separately. Requesting Help transmits product, language and any search text to retrieve published articles. A read status reflects our marking a message as seen. Chat has no automatic AI replies or advertising trackers.

11. Confidential chat access and browser storage

Secret conversation access stays by default in memory and, where possible, the browser tab's sessionStorage. Only with your additional Remember on this device choice is it saved in this browser's localStorage for up to 30 days. Expired remembered access is rejected and removed on its next check. Browsers can restore sessions, so closing a tab does not guarantee immediate removal from every recovery mechanism. Use remembering only on a device you control.

A private conversation link contains secret access in its URL fragment. Anyone holding the complete link can read and reply to the conversation. Share it only deliberately. An explicitly opened conversation page at support.meanetze.com can save its own access in that page's sessionStorage. Withdrawal on meterround.com neither clears a separately opened support tab nor invalidates a copied link. Clear that origin's browser data where necessary, or contact us for server-side deletion. The 30 days concern only remembered browser access, not message retention on the server.

13. Reply emails and internal Android notifications

Optional email notifications about replies are available only if our SMTP sending is configured and you additionally choose them in chat. They contain a general notice, product and private conversation link, but no message text or attachment. An encrypted access token is held on the server while this choice is active. You can switch it off again. The email services used for delivery process the address and notice. This optional notification choice relies on Article 6(1)(a) GDPR.

Firebase Cloud Messaging is used for internal notifications on the controller's registered MEA Support Android device. Google processes technical installation/delivery identifiers and general routing information such as conversation identifier and product. The visitor's name/email, message text and attachments are not sent to Firebase. No Firebase push account is created on your visitor device for this purpose. This internal delivery supports handling incoming requests and reliable support organisation under Article 6(1)(b) or (f) GDPR. It is separate from the MeterRound Android app.

14. Retention, recipients and international processing

Support messages, attachments and email correspondence are kept only while needed for handling, necessary follow-up, an open issue, necessary legal claims or legal duties. Data no longer needed are then deleted. Criteria include completion/content of the request, ongoing contractual relationships, specific security incidents and applicable legal retention duties. The protected Inbox allows us to delete conversations no longer needed; automatic deletion after 30 days is not promised. Hosting backups may contain removed data until the relevant backup is replaced. Legally required retention relies on Article 6(1)(c) GDPR.

Recipients are authorised MEA NETZE personnel, hosting, Cloudflare and any email service providers, and Google for the services expressly described. Authorities or legal advisers receive data only where legally necessary. Work files also go to recipients you select. We do not sell support data or use them for personalised advertising.

Hosting and Google services may involve processing outside the European Economic Area, particularly in the United States. Exclusively European processing is not promised. International transfers are subject to Articles 44 et seq. GDPR, such as an applicable adequacy decision or appropriate safeguards including EU standard contractual clauses. Google explains its privacy and transfer mechanisms in the information linked below. No specific server region or particular executed agreement is asserted here without evidence. You can request information about recipients and safeguards relevant to your inquiry at [email protected].

Cloudflare describes US transfers under the EU-US Data Privacy Framework and, where needed, supplementary standard contractual clauses. These provider disclosures do not claim certification of our own organisation.

15. Your rights and further information

Where the GDPR applies and its conditions are met, you have rights of access, correction, erasure, restriction and portability. You may object to processing under Article 6(1)(f) GDPR on grounds relating to your particular situation. You may withdraw consent at any time for the future without affecting earlier lawful processing. Contact [email protected]. Proportionate identity verification may be necessary to handle a request securely. Privacy rights are subject to legal conditions, such as continuing retention duties.

You may complain to a competent data protection authority, particularly where you live, work or where an alleged infringement occurred. The Hessian Commissioner for Data Protection and Freedom of Information is a contact for our location. You can also use Google's privacy tools for data in your Google account. We do not use support data for automated decisions with legal or similarly significant effects or corresponding profiling. You must check and accept OCR suggestions yourself.

Further information: Google Privacy Policy at policies.google.com/privacy; ML Kit Android disclosure at developers.google.com/ml-kit/android-data-disclosure; Google Play In-App Review at developer.android.com/guide/playcore/in-app-review; Firebase privacy at firebase.google.com/support/privacy; Namecheap Privacy Policy at namecheap.com/legal/general/privacy-policy/; Cloudflare Privacy Policy at cloudflare.com/privacypolicy/. We update this policy for material changes and show its date. This policy does not claim certification or replace your responsibility for personal and business information you record.