Privacy Policy
Reverse Flow Privacy Policy
Effective date: July 28, 2026
Introduction
Reverse Flow consists of the Reverse Flow: Fire Hydraulics mobile applications and the Reverse Flow public website. This Privacy Policy explains what information may be collected when you use either platform.
Mobile App Information
Reverse Flow does not require an account or login to use its calculators. Calculator settings, saved calculations, and the last confirmed Supporter state are stored on the device. Anonymous operational diagnostics may be produced when needed to investigate failures and improve reliability; routine diagnostics are designed to exclude full email addresses, receipts, purchase tokens, transaction identifiers, and calculator content.
Calculator inputs and fireground calculations remain on your device. Reverse Flow does not transmit or upload them.
Supporter Participation and Eligibility
Joining the Supporter Community is voluntary and is separate from making a payment. A one-time purchase or subscription is not required to claim or retain Supporter status. A purchase does not create, change, prioritize, or revoke Supporter eligibility, and does not automatically create, prioritize, or guarantee public recognition, a Supporter Number, placement, or another non-purchase benefit. Apple, Google, and Stripe payments are optional ways to sustain the project.
When you voluntarily join, update, or recover Supporter status, Reverse Flow collects the name and email address you provide, a lowercase version of the email used to prevent duplicate identities, the Supporter record creation or earliest verified participation date, and a permanent Supporter Number. The current system does not define a payment-based eligibility tier or financial rank.
Before you submit the supporter form, Reverse Flow discloses that the submitted name will be added to the public Supporter Registry. You affirmatively join through the supporter submission action after seeing that disclosure; a separate public-listing checkbox is not required. You may request removal of your name from the public registry at any time.
Some historical or provider-verified registration paths may retain limited private evidence such as a payment source, product identifier, transaction reference or purchase token, relevant purchase dates, verification time, and recurring status. Those records support verification, reconciliation, fraud prevention, and transaction administration; they do not make payment a requirement for Supporter participation.
Public Recognition and Supporter Numbers
After an intentional supporter submission, the public Supporter Registry displays the submitted public name, permanent Supporter Number, and Supporting Since date. It does not display email addresses, purchase history, provider account information, billing details, transaction references, purchase tokens, payment source, contribution amounts, or recurring-support status.
A Supporter Number is assigned in sequence when a Supporter identity is first created. It is permanent and does not represent a contribution amount, purchase order, subscription tier, payment status, Supporter ranking, or financial priority. To request removal of your name from the public registry, contact support@reverse-flow.app.
Supporter Contributions to Resources
A verified Supporter may choose to publish information and evidence to a Reverse Flow Resources library. Verification for this limited workflow compares the submitted name, email, and Supporter Number with one existing Supporter record and creates a short-lived session. The public contribution form does not display email addresses or reveal which identity field did not match.
Before publication, the Supporter must confirm permission to share the contribution and evidence. A published contribution may display the Supporter’s first name, last initial, permanent Supporter Number, submitted information, evidence note or source link, and an intentionally uploaded image, PDF, or document. Email addresses, complete private Supporter records, payment information, and raw upload-storage paths are not published. Contributions are labeled Supporter Submitted and are not automatically Reverse Flow Verified.
During the same limited Supporter session, a Supporter may share whether published information matches their experience or send a report for administrator review. Community responses are counted publicly but are not displayed with the responding Supporter’s name, number, or email. Reports are visible only to authorized administrators, do not automatically hide information, and include a short explanation only when the Supporter selects Other.
Community Confidence is a derived, versioned summary of visible community responses and supporting facts such as independent contributors, evidence, manufacturer origin, and Reverse Flow verification. It describes the available community feedback and supporting record for published Resources information.
Optional Payments and Subscriptions
In-app purchases are processed by Apple App Store on iOS devices and Google Play on Android devices. Reverse Flow does not receive or store complete payment-card information for those purchases. Stripe processes optional website payments and subscriptions and handles payment-card information for those transactions; Reverse Flow does not directly receive or store complete payment-card details.
The current Apple or Google store account determines mobile purchase availability, active monthly support, restoration, and subscription changes. The Reverse Flow backend does not override store billing state. Website billing records may include a name and email supplied through Stripe, Stripe customer and checkout identifiers, product or price identifiers, subscription, invoice and payment identifiers, amounts, currency, status, and transaction timestamps. These financial records are maintained separately from Supporter eligibility and public recognition.
Email Notifications
Reverse Flow uses Resend to deliver a welcome email associated with a Supporter claim. When a genuinely new Supporter identity is created, Resend may also deliver a limited internal notification to the project owner stating that the named person claimed Supporter status. Payment platforms may send their own required purchase, receipt, billing, or fraud-prevention communications under their policies.
Service Providers and Data Sharing
Reverse Flow uses Supabase for protected Supporter, Resources contribution, file-storage, and billing infrastructure, Resend for the email notifications described above, Apple App Store and Google Play Billing for mobile transactions, Stripe for optional website transactions, and Vercel for website hosting and website analytics. Each provider receives information needed for its role. Reverse Flow does not sell personal information.
Website Meta Pixel
The public Reverse Flow website uses the Meta Pixel to measure visits to public pages, understand interactions such as app-download button clicks, evaluate advertising performance, and improve our website and marketing efforts. Meta may receive information such as the page visited, configured interaction events, and limited browser or device information used to provide these measurement and advertising services.
This browser-based website measurement is separate from the mobile applications. The native Reverse Flow mobile applications do not include the Meta SDK, request App Tracking Transparency permission, access IDFA for advertising, or transmit mobile usage events to Meta. The website Pixel is not intentionally enabled on authenticated organization-management areas, administrative interfaces, the Website Editor, draft or review previews, /apps/** pages, or the Percent Pal website.
How We Use Information
Reverse Flow uses information to operate the calculators and website, maintain Supporter identity and public recognition, verify and attribute optional Resources contributions, preserve supporting evidence and contribution history, summarize community experience, route reports for administrator review, prevent duplicate or fraudulent claims, assign permanent Supporter Numbers, reconcile optional transactions, deliver notifications, respond to support requests, investigate reliability problems, measure public website use, and comply with transaction-record and legal obligations.
Information We Do Not Collect
Reverse Flow does not intentionally collect precise location, contacts, health or fitness data, text messages, payment card details, mobile advertising identifiers, calculator inputs, fireground calculations, or other sensitive personal information. Photos and documents are collected only when a Supporter intentionally uploads them as public Resources evidence after seeing the publication disclosure. Supporter Numbers, email addresses, raw contribution text, evidence filenames, uploaded source URLs, report explanations, and session identifiers are not intentionally sent to Meta or public analytics. Website measurement may include visits to public Reverse Flow pages and configured high-level interaction events, but it is not intended to track a user's general web browsing or search history.
Retention, Deletion, and Security
Supporter identities, Supporter Numbers, contribution history, contributor attribution snapshots, and published evidence are designed as durable records, while public visibility may be removed when appropriate. Private verification and transaction records may be retained as needed for accounting, fraud prevention, platform reconciliation, legal compliance, dispute handling, record integrity, and permanent-number administration. Contribution sessions expire within 24 hours. Only hashed session credentials and hashed rate-limit bucket identifiers are stored; operational rate-limit information and unpublished staged uploads are temporary.
You may contact support@reverse-flow.app to request correction, removal from the public Supporter Registry, or deletion of personal information. Removing a public listing does not cancel, alter, or delete payment or subscription records that must be retained for transaction, security, accounting, legal, platform, or dispute-handling requirements. Reasonable safeguards are used for information handled by Reverse Flow and its service providers.
User Choices
Every calculator remains available without purchasing, subscribing, or joining the Supporter Community. You may join without paying, pay without joining, do both, or do neither. Public recognition is optional. Website visitors may use browser privacy controls and Meta privacy settings to manage website measurement preferences.
Children's Privacy
Reverse Flow is not directed toward children under 13 years of age.
Changes to This Policy
Reverse Flow may update this policy when app features, analytics, measurement tools, or privacy practices change. The effective date above shows when this policy was last updated.