LEGAL / TERMINAL
SerialFlow Privacy Policy
Effective date: 2026-08-31Last updated: 2026-08-31
1. Who we are
SerialFlow is an Android serial-monitoring application provided by 郭逸超 (the “Service Provider” or “we”).
Privacy contact: [email protected].
2. Scope
This policy explains how SerialFlow accesses, stores, uses, and shares data when you use the Android application. SerialFlow can be used without signing in. Some account, purchase, advertising, map, and diagnostic services are provided by third parties.
3. Data we process
| Category | Examples | Why it is used |
|---|---|---|
| Google account data | Firebase user ID, email address, display name, and profile photo URL when you choose Google Sign-In. | Optional sign-in, account identification, and purchase migration or restoration. |
| Purchase and entitlement data | RevenueCat app-user ID, product and entitlement identifiers, purchase or subscription status, store and transaction metadata, and account attributes such as email or display name when supplied after sign-in. | Process purchases, restore purchases, verify entitlements, prevent fraud, and provide Pro features. |
| Advertising and consent data | Ad request and delivery information, advertising or app-set identifiers where available, IP address and approximate general location, device/app information, ad interactions, diagnostics, and your UMP consent status and related consent signals. | Request and measure ads, provide personalized or non-personalized ads according to applicable law and your choices, and protect advertising services from fraud and abuse. |
| Analytics and crash data | App and installation identifiers, app version, Android/device information, session information, feature and screen interactions, connection outcomes, USB vendor/product identifiers, serial configuration metadata, purchase/paywall/rewarded-ad events, region code, crash traces, stack traces, exception information, and related diagnostics. | Measure usage, improve stability, diagnose errors, and improve the application. |
| Serial and local application data | USB device name, USB vendor/product identifiers, connection settings, commands, received serial data, decoded values, logs, quick commands, display preferences, and other application settings. | Operate the serial monitor and provide local display, search, decoding, export, and customization features. |
Raw serial contents and serial commands are stored locally in the application’s private storage during normal use. SerialFlow does not upload raw serial log contents to its analytics or advertising services as part of normal operation. If you export or share a log, it is sent to the destination you choose and that destination’s privacy policy applies.
SerialFlow does not request precise GPS location permission. If you use the map view, it requests map tiles from OpenStreetMap. The tile request can expose your IP address and the approximate map area being viewed to the map service. GPS/NMEA values received from a serial device are processed locally by SerialFlow and are not intentionally uploaded as raw serial data.
4. How we use data and legal bases
We use the data described above to:
- provide and maintain SerialFlow’s serial-monitoring and local features;
- provide optional Google sign-in, purchase processing, entitlement verification, and purchase restoration;
- diagnose crashes, monitor reliability, and understand feature usage;
- serve, measure, and protect advertising where enabled; and
- respond to support requests, prevent abuse or fraud, comply with law, and protect our rights.
Where the GDPR, UK GDPR, or a similar law applies, the legal basis may be performance of a contract or steps requested before a contract, consent where consent is required (including applicable advertising choices), our legitimate interests in security and service improvement, or compliance with a legal obligation. The applicable basis depends on the data and purpose. This notice is not a blanket consent to every processing activity.
5. Advertising and privacy choices
SerialFlow uses Google Mobile Ads (AdMob) and Google’s User Messaging Platform (UMP). Depending on your location, device settings, ad availability, and consent choices, ads may be personalized, non-personalized, limited, or unavailable. Where required, UMP presents a consent form before eligible advertising requests are made.
You can review or change available advertising choices in Settings > Ad privacy settings. Changing an advertising choice does not necessarily delete information already processed by Google; Google’s policies and retention rules also apply.
The application’s “Enable Usage Statistics” setting controls Firebase Analytics collection on the device. It does not disable crash reporting, authentication, purchase processing, or advertising consent requirements.
6. Service providers and sharing
We share data with service providers only as needed for the purposes above. These providers may process data on our behalf and may also process certain data under their own terms:
- Google Firebase — Authentication, Analytics, Crashlytics, and Remote Config. See Firebase Privacy and Security.
- Google Sign-In, Google Play Services, and Google Play Billing — sign-in and purchase processing. See Google Privacy Policy.
- Google Mobile Ads and UMP — advertising, measurement, fraud prevention, and consent management. See Google advertising technologies.
- RevenueCat — purchase, subscription, customer, and entitlement management. See RevenueCat Privacy Policy.
- OpenStreetMap Foundation services — map tiles when the map view is used. See the OSMF Privacy Policy.
We may disclose data when required by law, to respond to valid legal process, to protect users or the public, to investigate fraud or abuse, or during a business transfer. We do not sell personal data directly.
Yandex Mobile Ads is included in the Android build but is not currently enabled for ad serving. If that changes, this policy and the consent flow will be updated before Yandex is enabled.
7. International transfers
Our service providers may process data in countries other than your own, including countries where Google or RevenueCat operate infrastructure. When required, we rely on applicable contractual, adequacy, or other lawful transfer safeguards. Contact us if you need more information about the safeguards applicable to your request.
8. Retention, access, and deletion
Local settings and serial logs remain on your device until you clear them, delete them using an available in-app control, clear the application’s data, or uninstall SerialFlow. Exported copies are controlled by you and may remain wherever you choose to save or share them.
Provider-held data is retained according to the provider’s settings and policies, and for as long as reasonably necessary for the purposes in this policy. We may retain limited purchase, security, fraud-prevention, tax, or legal records when a lawfully documented reason requires it.
You may request account and associated-data deletion by using Delete Account in SerialFlow’s Account screen or by emailing [email protected] with the subject “SerialFlow account deletion”. We will verify the request where reasonably necessary and delete or request deletion of associated data, except data that must be retained for a stated legal, security, fraud-prevention, or transaction reason. Any retained data will be isolated and kept only for the required period.
9. Your rights
Depending on where you live, you may have rights to access, correct, delete, restrict, object to, or receive a copy of your personal data, and to withdraw consent where processing is based on consent. You may also complain to your local data-protection authority. Contact us to exercise a right or ask a privacy question.
10. Children
SerialFlow is not directed to children under 13, or the equivalent minimum age in the applicable jurisdiction, and we do not knowingly collect their personal data. If you believe a child has provided personal data, contact us so we can review and take appropriate action.
11. Security
We use reasonable technical and organizational measures appropriate to the data and service, including encrypted network communication where supported by our service providers and limiting access to authorized systems and personnel. No method of storage or transmission is completely secure.
12. Changes
We may update this policy when the application, providers, or legal requirements change. We will post the revised policy with a new “Last updated” date. Material changes will be communicated through the application or another reasonable channel where required. Continued use of SerialFlow is not treated as blanket consent to processing that requires separate consent.
13. Contact
For privacy questions, rights requests, or account-deletion requests, contact [email protected].