Privacy Policy
OpenFlo is published by Pocket Lab Essentials LLC, an Ohio limited liability company in the United States. Here, "we" and "our" mean Pocket Lab Essentials LLC. This policy explains what information the OpenFlo phone apps (Android and iPhone, store title "OpenFlo: Flow Cytometry"), the OpenFlo desktop application and this website collect, how it is used, and the choices you have. The Terms of Use govern your use of OpenFlo.
1. Summary
- Your files stay on your device. OpenFlo has no server that receives, stores or routes your files, gates or results. We do not have access to them.
- The free phone app shows ads supplied by Google AdMob. We request non-personalized ads only. Google collects some device and ad information to deliver and measure them (Section 4). There is no tracking prompt on iPhone because OpenFlo does not track you across other companies' apps and websites.
- Ads can be removed with a purchase made through Google Play or the App Store. We never receive your payment details (Section 5).
- The phone app has no sign-in and no OpenFlo account. We do not collect your name or email address unless you choose to send us a report and type a reply address (Section 6).
- Usage counts are optional and anonymous. The phone apps send anonymous usage counts only if you turn them on, with no identifier and nothing from your files (Section 3). No third-party analytics service receives them, and we use no advertising cookies in OpenFlo or on this website. In the free phone app, Google's ad library may use the data it collects for its own measurement and analytics (Section 4).
- Nearby send stays on your network. Files you send between your own devices go directly from one to the other and never through us (Section 3).
- Not for children under 13. OpenFlo is a research tool and is not directed to children (Section 10).
This policy is a standard commercial-style document written to match how OpenFlo works. It has not yet been reviewed by a lawyer, and we may revise it after that review.
2. Information we do not collect
OpenFlo processes the files you open (for example FCS files, workspaces and sessions) on your own device. In the phone apps, files you open are copied into the app's private storage on your device; the original is not changed. We do not collect, upload, view or analyze your files, sample names, gates, statistics or exports. You decide where a saved or exported file goes and with whom you share it. Apart from optional anonymous usage counts, optional problem reports you send, and the data Google's ad library and the stores' billing handle (Sections 3 to 6), the apps do not collect data from your device. We do not run an account system, we do not use crash-reporting services of our own, and we do not build profiles of users.
Data files can carry identifying text in their metadata (such as sample names, specimen identifiers or operator names). That text stays on your device with the file, but you are responsible for what you open and share; see the Terms of Use.
3. Information we receive, by source
Phone apps (Android and iPhone)
- Ads (free version). The Google Mobile Ads SDK runs in the app and exchanges information with Google. See Section 4.
- Ad-free purchases. The app asks the Google Play or App Store service on your phone whether your store account owns an ad-free purchase. See Section 5.
- Reports you send. If you use Settings, Report a problem, the app sends what you typed to our website. See Section 6.
- Anonymous usage counts, only if you turn them on. See "Anonymous usage counts" below.
- Nearby send. Files you send to your own devices never reach us. See "Nearby send" below.
- Stored on your device only: your settings, your recent files, the time of the last ad, whether you have seen the tutorial, your ad-free status, your usage-counts choice and any counts not yet sent, and for Nearby send this device's keys and its list of paired devices. These stay in the app's storage and are removed when you uninstall the app.
Desktop application
- The desktop application is open-source software that runs on your computer and sends no analytics or usage data to us.
- Unless you turn it off in Preferences, it makes a quiet request to GitHub when it starts to see whether a newer release exists. If you choose Update, it downloads the new version from GitHub or the Python Package Index (PyPI), which see your IP address under their own policies. GitHub receives your IP address and the request, under GitHub's own privacy statement. Nothing about your files is sent.
- Nearby send (File > Nearby send…) works as described under "Nearby send" below. Receiving is off until you turn it on. The computer's Nearby name ("Computer" plus four characters unless you rename it), its keys and its list of paired devices are kept in your user folder and never sent to us.
- Reports you choose to send from the app work as described in Section 6.
This website
- The site is hosted by Vercel Inc. As with any web host, the server and its network handle your IP address, browser type and the pages requested, and may keep standard server logs for security and operation. We do not use analytics scripts, advertising trackers or cookies for tracking on this website.
- The feedback form is described in Section 6.
Anonymous usage counts (optional, phone apps)
The phone apps can send anonymous usage counts; the desktop application sends none. This is off until you choose "Share anonymous usage counts" on the card shown after the first-run tutorial, and you can turn it off at any time in Settings > Privacy. Turning it off deletes any counts not yet sent and sends nothing further. Choosing "No thanks" is remembered, and nothing is sent.
- What is counted. Whole-number counters for things such as: which tool was opened, whether a file you opened matched a tool, which purchase screen steps were reached (shown, started, completed, canceled, restored), which export format was used, which allow-listed feature was used, whether an ad was shown or skipped, how often a known error or a recovery from a problem occurred, whether the first-run tour was finished or skipped, and how often a result was shared and by which channel (for example email, text, image, PDF, file or Nearby send). Each counter uses fixed labels built into the app, never text you type.
- What is sent with the counts. The app version, platform (Android or iOS), major operating system version, interface language (for example "en", never region), the month you first ran the app (for example "2026-11"), the date, and the counters. The country is worked out by our server from the connection when the counts arrive; the address is used briefly in memory to limit abuse, and we do not store the IP address.
- What is never sent. File names, file paths, file contents, file sizes, row counts, sample or gate names, any text you type, advertising identifiers, device identifiers, user identifiers, purchase receipts, email addresses, or location. Only extensions from a fixed list of about 200 known laboratory and engineering formats are ever counted; any other extension is counted as "other".
- No identifier. The app has no account and creates no install, device, user or session identifier for these counts. Each daily batch carries a random value that is used only to discard duplicates for 48 hours. Because of this, we cannot tell which counts came from the same person, and we cannot look up or delete the counts of one person.
- Who processes it. Our own server, hosted by Vercel Inc. (this website's host); the counts are stored in a database run for us by Upstash, Inc. No third-party analytics service receives the counts. The host's routine server logs may briefly keep connection details such as IP addresses; we do not use them for these counts.
- Retention. Daily counters are kept for 25 months, then deleted.
- What we do with it. Plan which tools and fixes matter, and understand whether the app is working. Reports show only combined numbers; small groups (fewer than 5) are not shown. We do not sell the counts, use them for advertising, or combine them with other data.
- Crash reports. We do not send crash text from the app. If you allow it in your device settings, Google Play and the Apple App Store give us their own aggregate crash and performance reports.
- Choice and legal bases. Sending is opt-in everywhere. Where the law requires consent (for example in the European Economic Area, the UK and Switzerland), this setting is that consent, and you can withdraw it at any time in Settings > Privacy. "See what would be sent" shows the exact counts waiting to go.
Sending files to your own devices (Nearby send)
Nearby send moves a file directly between your own devices that are on the same local network (for example your phone and your computer). It does not go through our servers, and we never receive the file or the fact that you sent it. While the Receive screen is open (in the desktop application, while receiving is turned on in File > Nearby send…), your device announces itself on the local network with a generic device name (such as "Android phone" plus four characters, which you can rename; it never contains your account or personal name), the app name, and a short code derived from the device's identity key. Other devices on the same network that run our apps can see that announcement while the screen is open. The first time two devices connect, you compare a 6-digit code on both screens to pair them. The devices then remember each other by a public key (a "paired devices" list in Settings, where you can choose Forget). Each device keeps a private key made on first use; it never leaves the device. The transfer is encrypted between the two devices, and the receiving person is asked to accept each file before it is saved. Your device may ask for permission to find devices on your local network (iPhone and recent versions of Android); it uses this only for Nearby send, and the apps do not read other information about your network. The optional share count described above records only that a share happened and by which channel (for example "nearby"), and only if you turned usage counts on.
4. Advertising (Google AdMob)
The free version of the phone app shows full-screen (interstitial) ads from Google AdMob when you open files or export. At most one ad is shown every 15 minutes. No ad is shown on the first start of the app, during the tutorial or in the ad-free version.
- Non-personalized. We request non-personalized ads, which are based on general information such as the app and your approximate location rather than on your past activity across apps. On iPhone, OpenFlo does not show Apple's App Tracking Transparency prompt and does not use the advertising identifier for tracking.
- What Google may collect. To deliver, limit the frequency of, measure and protect against fraud in ads, the Google Mobile Ads SDK and Google's consent tool (User Messaging Platform) may collect device and ad information: IP address and approximate location derived from it, device and app identifiers (which may include the Android advertising ID where your device and settings allow it), device and operating-system details, ad interactions (such as impressions and taps), and crash and performance data. This information is collected by Google directly from your device. We do not receive it and cannot identify you from it. Google acts under its own terms and privacy policy; see How Google uses information from sites or apps that use its services and the Google Privacy Policy.
- Your consent choices. Where the law requires consent for ads (for example in the European Economic Area and the United Kingdom), the app shows Google's consent form before any ad is requested, and no ad is requested without it. You can change your choice at any time in Settings under "Ad privacy choices" (shown where the form applies to you). The consent form is first shown on the second start of the app.
- Device controls. You can reset or delete the advertising ID in your device's settings (on Android, Settings > Privacy > Ads; on iPhone, Settings > Privacy & Security > Tracking), and you can remove ads by buying the ad-free option.
- Not directed to children. We do not request ads for children and do not treat the app as child-directed (Section 10).
5. Purchases and subscriptions
The ad-free option is sold through the Google Play Store or the Apple App Store as a monthly or yearly subscription (the yearly plan may start with a free trial) or as a one-time purchase. The store handles the payment, your payment details, receipts, renewals, cancellations and refunds under its own terms and privacy policy. We do not receive your name, email address or payment details, and there is no OpenFlo server involved. On your phone, the app asks the store whether your store account owns the purchase and keeps the answer on the device so it works offline. Billing terms are in Section 8 of the Terms of Use.
6. Reports and feedback
If you send a report or idea from the apps (Settings, Report a problem) or from the form on this website, we receive what you typed: the kind (bug or idea), a title, the details, which app you used (Android, iPhone or other), its version, and a reply email address if you choose to give one. We use it only to work on OpenFlo and to answer you if you gave an address. Please do not include confidential or personal information in a report.
In the desktop application you may also tick "Attach the error report". The report then includes the application's error log with file paths, sample names and email addresses replaced by placeholders, and it is sent only if you tick that option. Each report is filed as a private issue in our development tracker on GitHub (GitHub, Inc., acting as our service provider), where only we can read it. Reports are kept for as long as needed to work on the problem or idea and a reasonable time after, and are then deleted or kept without the reply address. The website briefly uses your network address in memory to limit abuse; it is not stored with the report. Email us (Section 12) and we will find and delete a report you sent.
7. Donations
If a donation option is offered on this website, the payment is handled by our payment provider on its own page. We do not see or store your card details. We receive only what the provider tells us about the payment (such as the amount, and an email address if you give one).
8. How we use information, and our legal bases
We use the information in Section 3 to provide and secure OpenFlo, to show and measure ads (through Google), to recognize ad-free purchases (through the store), to answer reports and fix problems, and to meet legal obligations. If the General Data Protection Regulation (GDPR) or the UK GDPR applies to you, our legal bases are:
- Consent for ads that need it (your choice in Google's consent form, which you can withdraw at any time in Settings under "Ad privacy choices", without affecting earlier use);
- Consent for anonymous usage counts, which are off until you turn them on and which you can turn off at any time in Settings > Privacy;
- Contract, to provide a purchase you made through the store;
- Legitimate interests, to answer reports, keep the website and its feedback form secure and prevent abuse, and improve OpenFlo, balanced against your rights; and
- Legal obligation, where the law requires us to keep or give out information.
We do not use automated decision-making that has legal or similarly significant effects on you.
9. Who we share information with
We do not sell personal information. We do not receive the ad information Section 4 describes. We use these providers, each under its own terms:
- Google LLC (AdMob, User Messaging Platform; Google Play Billing on Android), which collects ad data from the phone app as described in Section 4.
- Apple Inc. (App Store, in-app purchases on iPhone).
- GitHub, Inc. (private issue tracker for reports; release information for the desktop update check).
- Vercel Inc. (website hosting, and the server that receives anonymous usage counts).
- Upstash, Inc. (the database that stores the anonymous usage counts for us).
- Our payment provider (donations, if offered).
- Professional advisers and authorities, where needed to protect our rights or comply with law, and a successor if our business is sold or reorganized.
We require, or rely on the terms of, each provider to protect information at least as well as this policy describes. These providers are based in, or may process information in, the United States and other countries. Where GDPR or UK GDPR applies, transfers outside the EEA or the UK rely on a safeguard such as the EU–U.S. Data Privacy Framework or standard contractual clauses.
10. Children
OpenFlo is a research and education tool, is not directed to children under 13 (or under 16 where the law of your country sets that age for consent to data processing), and we do not knowingly collect personal information from them. We do not request ads for children, and we do not treat the app as child-directed under the U.S. Children's Online Privacy Protection Act (COPPA). If you believe a child has sent us personal information (for example in a report), contact us (Section 12) and we will delete it.
11. Your rights and choices
Everyone
You can change your ad consent choice in Settings ("Ad privacy choices"), reset your advertising ID in your device settings, remove ads by buying the ad-free option, uninstall the app to delete everything it stores on your device, turn off the desktop update check in Preferences, turn anonymous usage counts off in Settings > Privacy, and forget a paired device in Nearby send. You can ask us to delete a report you sent.
European Economic Area, United Kingdom and similar laws
Subject to the law that applies to you, you may ask us for access to, correction of, deletion of, restriction of or a portable copy of your personal information, object to processing based on legitimate interests, and withdraw consent at any time. You may complain to your local data protection authority (in the United Kingdom, the Information Commissioner's Office). Because we hold very little information about you and do not receive ad data, we may be unable to find information you ask about unless you give us the email address or details of the report concerned.
California and other U.S. states
Under the California Consumer Privacy Act as amended by the California Privacy Rights Act (CCPA/CPRA) and similar laws in other states, residents may have the right to know what personal information we collect, use and disclose, to access and correct it, to delete it, to opt out of its sale or sharing, to limit the use of sensitive personal information, and not to be treated unfairly for using these rights. In the last 12 months, the personal information we collected (and only when you chose to send a report) was: identifiers (an email address, if you gave one), and the content of the report you typed. We collected it from you, to answer you and work on OpenFlo, and disclosed it only to our service providers (GitHub and the website host). We do not collect sensitive personal information. Anonymous usage counts (Section 3) carry no identifier and cannot be linked to you.
We do not sell personal information, and we do not share it for cross-context behavioral advertising. Ads are non-personalized. Google collects ad-related information from your device under its own terms. To the extent California or another state law treats that as a sale or sharing, you can opt out through your device's advertising settings, by buying the ad-free option, or by emailing us (Section 12). Where Google's consent tool offers a privacy-choices form for your state, it is available in Settings under "Ad privacy choices". We do not knowingly sell or share the personal information of anyone under 16.
To use a right, email us (Section 12). We may need to confirm that a request relates to you, for example by asking you to confirm details of a report you sent, and we aim to answer within 45 days (or sooner where the law requires). You may use an authorized agent. If we decline a request, you may appeal by replying to our answer, and may then contact your state attorney general.
12. Contact
Pocket Lab Essentials LLC
303 Conant St, Apt 2, Maumee, Ohio 43537
Email: support@getopenflo.com
13. Security and retention
We keep little information, and what we keep is held in access-controlled services and sent over encrypted connections. No method of transmission or storage is completely secure. Information in the phone app stays on your device under the protections of your operating system; a screen lock and device encryption are your best protection. Reports are kept as described in Section 6. Anonymous usage counts are kept as described in Section 3. We do not keep other personal information about you.
14. Changes to this policy
We may update this policy, for example when OpenFlo or its ad or purchase providers change. The date at the top shows when it was last changed. If a change materially affects how we handle your information, we will give notice in the app or on this page before it takes effect, and ask for consent where the law requires it.