Privacy Policy

1. Who is responsible

Daniil Bystrov, an individual developer trading as AppStudioHub, operates FlowRadar and is the controller of information processed for the service. Contact daniil.bystrov@gmail.com for privacy questions or requests.

FlowRadar is independent of Meta and Facebook. External marketplaces, Apple and other services have their own privacy policies for information they handle independently.

2. Information we use

• Account information: email, optional display name, account identifier, password hash when you use email sign-in, session credentials and password-reset records. Where quick sign-in is available, Firebase Authentication and your chosen Google or Apple provider supply a verified email, optional name, authentication identifier and sign-in proof. We map that identity to your FlowRadar account without automatically merging existing accounts that share an email. We use these to provide and secure access. The mobile app stores its session in private device Keychain storage.
• Saved searches: Radar names, search and excluded words, budget, distance, filters, schedule and active state. A selected place or postal code is resolved into location details, coordinates and a time zone. The mobile app does not request GPS access or follow your live location.
• Listings and activity: listing titles, photos, descriptions, prices and changes, source links, seller display information and listing locations when available; which Radars a listing matches; alert history; and viewed state. Listing photos can load directly from the source image host. We also keep fixed image copies for selected content reviews; not every displayed image has been reviewed or copied by us. Some source content relates to people who posted it publicly.
• Subscriptions: your account ID, product and entitlement IDs, purchase and renewal status, expiry and verification records. Apple processes iOS payments. RevenueCat receives the account ID and purchase-related information needed to verify access. We do not receive your complete payment-card details from Apple. Separate web billing, when used, is processed by Stripe.
• Notifications: if you enable push, an installation identifier, platform, messaging token, server session association and delivery status. Notification payloads can contain a listing or Radar identifier and an alert message. Your device settings control whether notification previews appear on the lock screen.
• Security and technical records: IP address, user agent, request times, authentication events, rate-limit state and technical errors needed to operate and protect the service.
• Optional advertising measurement: when you allow measurement, configured versions of our website and mobile app use AppsFlyer and Meta to measure campaign visits, app installs, registration, Radar creation and subscription outcomes. This can include campaign and ad identifiers, a Meta click identifier, device and attribution identifiers, IP address, user agent, event times and an opaque FlowRadar account identifier. AppsFlyer uses the IP address to estimate an approximate location, such as a city or region, for campaign analytics and advertising measurement. Subscription measurement can include product, transaction, currency and revenue information from RevenueCat. Where available, a configured native version can also send Meta a SHA-256 hash of your verified account email for matching subscription events, after you allow the account-matching measurement choice and the iOS tracking permission. Earlier measurement choices do not automatically allow this additional email matching. We do not put your raw email into custom advertising SDK event parameters. Passwords, session or reset credentials, Radar search text, selected search location and listing contents are excluded from advertising event payloads.
• Website account source: after an explicit website measurement choice, a short-lived, HTTP-only cookie can connect selected campaign IDs from a landing visit to registration or login through our own API. This records a declared campaign source for your FlowRadar account; it is not proof of a particular ad click or app installation. We do not use email or a device fingerprint to perform this match. Registration and downloads also work without optional measurement. Account and plan pages do not load advertising SDKs.
• Apple aggregate ad measurement: configured iOS versions can use Apple’s SKAdNetwork to report coarse conversion milestones such as a new registration or a verified purchase. This separate Apple mechanism may operate when personal advertising measurement is off or ATT permission is denied. FlowRadar supplies only numeric conversion values to Apple, without account, device or transaction identifiers, purchase amounts or search content. Apple controls attribution, privacy thresholds and delayed postbacks, which can be received by the advertising network and AppsFlyer for aggregate reporting. We do not use device fingerprinting to identify people who declined tracking.
• Content safety: reports and their reasons, optional details, hidden listing identifiers and blocked seller identifiers are associated with your account so that we can investigate reports and apply your controls. Account deletion removes your reports and personal controls. Separately, we keep source identifiers, content fingerprints, image-copy references, review decisions, reasons and timestamps for the shared catalogue. Global listing removals retain source identifiers without reporter linkage.
• Support: contact details, messages and attachments you send to us, plus information needed to investigate your request. Please do not send passwords, payment-card details or unnecessary sensitive information.

3. Why we process information

We use this information to create and authenticate accounts, run automatic saved searches on Facebook Marketplace, show matching results and price changes, remember viewed listings, deliver requested alerts, verify subscriptions, reset passwords, provide support and prevent abuse. We also use limited records where needed to comply with law or establish, exercise or defend legal claims.

We process reports, personal hides, seller blocks and moderation decisions to investigate concerns and restrict content. Individual review is not required before an ordinary listing appears in results or alerts. Selected content reviews may use fixed image copies, content fingerprints and decision records; these records do not mean that the whole catalogue has been reviewed.

Where a legal basis is required, we rely on performance of our agreement for requested service features, legitimate interests in operating and securing the service, legal obligations, and consent for optional features where required. You can withdraw notification permission in device settings without deleting your account.

Optional campaign measurement helps us understand which ads lead to app installs and useful actions and helps Meta optimise our campaigns. Website advertising measurement starts only after you allow it in Advertising choices. In configured iOS versions it also requires Apple’s App Tracking Transparency permission. Declining does not limit downloads, Radars, subscriptions or other app features. Versions without advertising configuration do not start these measurement SDKs. Firebase Analytics remains disabled. RevenueCat verifies subscriptions regardless of advertising permission; its attribution connection is enabled separately for measurement where you have allowed it. We do not sell personal information or send marketing email without an appropriate legal basis and any consent required by law.

4. Providers and external services

• Apple: App Store purchases, subscription management and Apple Push Notification service. See Apple Privacy.
• RevenueCat: subscription records, purchase restoration, entitlement verification and subscription reporting associated with your FlowRadar account ID. See RevenueCat Privacy.
• AppsFlyer: optional campaign attribution, install and event measurement, deep linking, and subscription event reporting supplied through RevenueCat. Where measurement is enabled with your permission, AppsFlyer can send configured conversion events to Meta. See AppsFlyer Services Privacy.
• Meta: optional Meta Pixel website events, native SDK measurement and AppsFlyer conversion postbacks used to measure and optimise FlowRadar advertising campaigns. Meta can connect permitted measurement information with information it holds under its own policy. See Meta Privacy.
• Firebase Authentication, Google and Sign in with Apple: quick sign-in, identity verification, session security and disconnecting linked sign-in identities when an account is deleted. The selected provider receives the sign-in request and technical information needed to authenticate you. Sign-in credentials and Firebase authentication identifiers are not included in advertising events. Firebase Analytics remains disabled. See Firebase Privacy and Security, Google Privacy and Apple Privacy.
• Google Firebase Cloud Messaging: installation/messaging identifiers and alert payloads for delivery to your device through APNs. Firebase and its supporting libraries also process limited installation, delivery and technical diagnostics to operate and measure the messaging service. See Firebase Privacy and Security.
• OpenStreetMap Nominatim: place or postal-code queries sent from our server to obtain search-location suggestions. See the OpenStreetMap Foundation Privacy Policy.
• Hosting and backups: the service database, saved image copies and operational backups run on our AppStudioHub VPS infrastructure provided through HOSTiQ/Twinservers. Infrastructure providers process data necessary to host and secure the service.
• Support email: support is handled directly by the developer using Google’s email service.
• Stripe: customer and subscription information if you use a separately offered web checkout. See Stripe Privacy.
• Marketplace and image hosts: displaying listing photos can connect your device directly to the source image host, which can receive your IP address and technical request information under its own policies. When our server fetches an image for a selected content review, that host receives the server’s network address and request information instead. We may serve a saved copy for reviewed content. Opening an original listing also connects your device to the third-party marketplace. We do not add your FlowRadar password or session credential to a marketplace link.

We disclose information to providers as needed for these purposes, at your direction, or where legally required. We may disclose limited information to protect rights and safety or as part of a lawful business transfer, with appropriate safeguards. We do not use your search text for an external AI service in the current production configuration.

5. Cookies and local storage

The web app uses an essential session cookie to keep you signed in and local browser storage for app state and preferences. A service worker supports the installed web app and web notifications. The native app uses private local storage and Keychain for installation and session state. Configured public marketing pages can load Meta Pixel and AppsFlyer OneLink Smart Script after you allow advertising measurement. They can use advertising cookies and campaign storage for attribution. Advertising choices are stored so that we can respect your selection; clearing that choice does not enable measurement automatically.

The getting-started preview can keep keywords, a category, an optional city or ZIP and a budget in session storage in your browser tab for up to two hours. This functional draft has no account, campaign or sign-in token fields and does not activate a search. After sign-in you can review the draft, confirm a location and save a Radar; it is cleared after a confirmed save or account deletion. Browsers that block this storage can still continue to account creation or download. Quick sign-in uses Firebase Authentication with in-memory browser authentication state; the FlowRadar session is stored separately in its HTTP-only cookie.

You can change Advertising choices on the website and Advertising measurement in the mobile Profile. Turning measurement off stops subsequent SDK reporting from that client and clears its campaign association where supported; it does not recall events already delivered to providers. You can also revoke iOS tracking permission in Settings. Website and app permissions are separate, and website consent does not override an iOS refusal.

You can remove local data through your browser or device settings. Clearing local data or uninstalling the app does not delete your server account or cancel a store subscription.

6. Retention and deletion

Website acquisition contexts and their cookies expire after two hours. Attached account-source records are retained for up to 90 days, and the account advertising-choice record for up to 180 days; an hourly cleanup removes expired records. Withdrawing the website account choice removes the source and pending contexts held by our API. It does not change the separate advertising choice on every installed device or erase reports already held by an external provider.

We keep account and search information while it is needed to provide the service to your account. You can remove Radars and their account-specific history through the app. In the iPhone app, Profile → Delete account removes your account and associated Radars, listing history, alerts, sessions and device registrations from the active service after confirmation.

Shared catalogue review records and saved source-image copies are stored separately from individual accounts. Deleting an account does not automatically delete those shared records or copies. We retain them to serve reviewed content, maintain safety decisions and investigate content concerns. They currently have no automatic expiry; source-content and privacy removal requests can be sent to Support. Quarantining a listing or withdrawing its approval stops further public access to its saved review copy unless that copy is also part of another approved listing. Content already downloaded or delivered to a device cannot be recalled.

Deletion also starts cleanup of associated provider customer records. A limited identifier can remain in a restricted retry queue until that cleanup succeeds. For Firebase identity cleanup, a project-scoped one-way hash blocks concurrent sign-in for fifteen minutes after the deletion receipt, preventing that request from recreating a deleted account. The raw identifier is removed at the receipt; the expired hash is cleared on a subsequent cleanup run. Billing providers may retain transaction records under their own legal obligations. Deleting a FlowRadar account does not cancel an Apple subscription; use Apple subscription settings to stop future renewals.

Historical backups are kept separately for disaster recovery and can contain records removed from the active system until those backups are overwritten or removed. Technical logs, support correspondence and records needed for security, a dispute or a legal obligation may be retained separately for those purposes. Retention depends on the purpose, recovery needs and applicable legal requirements; it does not give us permission to use deleted account information for marketing.

For access, deletion or retention questions, or if you cannot access your account, contact support. We may request enough information to verify that the request concerns your account. Do not send your password.

7. Security and international processing

We use encrypted network connections, password hashing, access controls and separate storage for service credentials. Push registrations are associated with an authenticated account and server session. No internet service can guarantee absolute security.

Our providers operate internationally, so information may be processed outside your country. Where applicable law requires safeguards for a transfer, we rely on an appropriate legal transfer mechanism, such as an adequacy decision or contractual safeguards, as applicable to the provider and service. Contact us for information about processing relevant to your account.

8. Your choices and rights

Depending on your location, you may request access, correction, deletion, restriction or a portable copy of your information, object to certain processing, and withdraw consent without affecting processing already performed lawfully. You can also complain to your local data-protection authority. We will handle requests under applicable law and will not penalise you for exercising protected privacy rights.

Manage search settings in the app, notification permissions in device settings, and subscriptions with the store or billing provider that charged you. Use Advertising choices or the mobile Profile to withdraw optional measurement permission. For access or deletion of attribution records already held by AppsFlyer or Meta, contact us so that we can coordinate the request with the relevant provider. Account deletion and local withdrawal do not automatically erase every historical provider report. You can contact us at the email address in this policy.

9. Children and policy changes

FlowRadar is a general-audience automated-search utility and is not specifically directed at children. We do not knowingly collect personal information from children. If you believe we have collected a child’s personal information, contact daniil.bystrov@gmail.com so that we can investigate, stop further collection and delete the information where required by applicable law.

We may update this policy when features, providers or legal requirements change. The effective date identifies the current version. Material changes will be communicated through the service or another suitable channel; we will request consent where required.