Privacy Policy
FlowSet DJ Privacy Policy
- Effective date
- October 27, 2026
FlowSet DJ is designed to keep your music workflow private. Optional app and website analytics are off until you allow them separately. The app uses Firebase Analytics only with your permission; the website uses Google Analytics 4 only with your permission. App Store campaign links may include the campaign identifier described below whether or not you allow website analytics. FlowSet DJ does not sell your data.
This Privacy Policy explains what information is processed when you use the FlowSet DJ app or website.
Data Stored on Your Device
FlowSet DJ stores the following app data locally on your device:
- Smart Sets, saved sets, queue settings, and playback preferences.
- Flagged songs and playlist assignment information.
- Local Files folder settings, local playlist references, and local track metadata.
- BPM analysis, waveform data, tempo settings, and other playback metadata for local tracks and FlowSet Samples.
- Downloaded FlowSet Samples packs and sample playlists.
- Your saved FlowSet Samples Grid/List display choice and cached playlist cover images.
- Local feedback-offer bookkeeping, questionnaire-scoped feedback identifiers, and a saved answer awaiting your retry, as described below.
This data is used to provide the app's features. FlowSet DJ does not upload your Smart Sets, saved sets, local audio files, local playlists, BPM metadata, flagged song lists, or generated queues to FlowSet servers.
Apple Music
If you connect Apple Music, FlowSet DJ uses Apple-provided frameworks and services to request permission, read your Apple Music playlists, play Apple Music tracks through your Apple Music account, and perform Apple Music actions you choose, such as adding a track to a playlist.
Apple Music library and playback data is handled through Apple services. FlowSet DJ does not upload your Apple Music library to FlowSet servers.
Local Files
If you configure Local Files, FlowSet DJ accesses the folders you choose so it can read supported audio files and .m3u or .m3u8 playlists. Local file data remains on your device and in the folders you selected, except when iOS or Apple services process device backups or system-level storage according to your own Apple settings.
FlowSet DJ does not upload your local audio files or local playlist files to FlowSet servers.
FlowSet Samples
FlowSet Samples lets you download sample packs and sample playlists provided for use inside FlowSet DJ. To provide this feature, the app contacts FlowSet's sample service to:
- Fetch the available sample catalog.
- Retrieve and cache playlist cover images while browsing, including in Add More Samples before you download audio.
- Request download information for selected sample packs or playlists.
- Download selected sample pack files.
Limited server request data may be processed for delivery, security, and troubleshooting. This may include technical request information such as IP address, user agent, request time, requested catalog, image, or sample pack identifiers, response status, and similar server log information.
These service requests do not depend on optional app analytics consent. FlowSet DJ does not use FlowSet Samples server request data for advertising or tracking.
Subscriptions and Offer Codes
FlowSet DJ uses Apple's in-app purchase system for subscriptions and offer-code redemption. Payment information is handled directly by Apple and is not accessible to FlowSet DJ.
The app receives subscription entitlement information from StoreKit so it can unlock Pro features. FlowSet DJ does not receive your payment card details.
If you allow app analytics, privacy-limited subscription events can include the paywall entry point and blocked feature category, whether plans loaded or a trial was eligible, monthly or annual plan choice, immediate purchase result, and changes between Free, paid Pro, Pro trial, and Pro obtained with an App Store offer code. FlowSet does not send prices, receipts, offer codes, transaction identifiers, product IDs, or raw StoreKit errors in its custom events. Apple and StoreKit remain the authority for purchases and access.
App Store Update Checks
FlowSet DJ may contact Apple's App Store lookup service to check whether an app update is available. This request is handled by Apple.
Apple Watch
If you use the Apple Watch companion app, playback state and control messages are exchanged between your iPhone and Apple Watch using Apple's WatchConnectivity framework. FlowSet DJ does not send this watch playback state to FlowSet servers.
Support
If you contact FlowSet DJ support by email, your email address and any information you choose to include in your message will be used to respond to your request. Support messages may be retained as needed to handle the request and maintain support records.
Do not send sensitive personal information, payment details, Apple account credentials, or private app-store redemption codes in support messages.
Optional Feedback
FlowSet DJ may offer native, optional questionnaires. Only choosing Send answer starts feedback transmission. Choosing No thanks or closing an unsent form sends no feedback and discards its draft. No reason is preselected. Feedback can be sent while app analytics is off; sending it does not enable analytics or change your analytics choice. Questionnaire offers, drafts and refusals are not sent to Google Analytics.
A submitted answer contains fixed answer codes, questionnaire and question identifiers, questionnaire and submission-format versions, a random submission identifier reused for retries, and a random feedback participant identifier. Submitted answers also include the displayed app version and platform category (iPhone, iPad or Mac), even when Analytics is off. The service adds its receipt time. If you choose Something else, you may include an optional written comment of up to 500 Unicode scalar values, with no minimum length. The app does not add account or contact details, music or playlist identifiers, filenames, paths or file contents. Please do not include personal or sensitive information, music or file details in a comment.
The participant identifier is created on your first Send for that questionnaire in that app installation. It links later submitted answers to the same questionnaire, including across questionnaire versions, so FlowSet can understand reported reasons and changes over time. It is not an anonymous response. This feedback identifier is random and is not derived from an account, Apple or advertising identifier, device attributes, or an analytics identifier. Separately, if Analytics is enabled when you send and when transmission starts, the app may include the existing pseudonymous Firebase app-instance identifier to associate that answer with measured usage from the same app instance. Feedback can be sent without this association when Analytics is off or the identifier is unavailable. Sending feedback does not turn Analytics on or change your choice.
The app keeps its feedback identity and offer records in local storage excluded from backup and sync. The feedback identifier is replaced after reinstallation, a local feedback-data reset, loss of the installation marker, or 12 calendar months without Send for that questionnaire. Resetting analytics does not reset feedback identity. Later offers depend on local setup-attempt counts and time since the previous offer; these counts and times are not submitted. An unfinished deliberately started setup or reconfiguration may offer this questionnaire. Completing a setup does not permanently prevent offers after a later unfinished attempt.
On Send, the app uses HTTPS to submit to a Google Firebase Cloud Function, which validates the answer and commits it to Firestore before confirming acceptance. Structured answers, optional comments and optional analytics associations are stored separately with restricted access; app clients cannot read the database. Closing the questionnaire after Send does not cancel an active request. The app may keep one protected, backup-excluded pending answer, with its original optional analytics-association candidate, for up to 24 hours after Send. You can review it in Local Files Settings and explicitly retry or discard it; it is not automatically resent in the background. Retries preserve the answer and feedback identifiers to avoid duplicate acceptance. A retry omits the analytics identifier if Analytics has been turned off or the app-instance identifier has changed, and cannot add or replace an association already accepted. Discarding a saved answer cannot undo a server acceptance whose confirmation was lost.
Firebase App Check and Apple’s App Attest, or an explicitly configured supported DeviceCheck provider, verify app requests to resist abuse. The feedback Firebase service is separate from the analytics service and is initialized on Send with automatic token refresh disabled; each explicit retry obtains a fresh verification token. Google, Apple and network infrastructure may process operational information such as IP address, user agent, request time and status, app or device verification data and provider-issued tokens or identifiers. These are service and security processing, separate from the answer payload; they are not joined to Google Analytics or feedback reports. An unsupported or unconfigured verification service does not fall back to unverified delivery.
FlowSet uses answers to improve specific features within FlowSet DJ. Authorized processing can compare submitted answers within the questionnaire’s participant scope and prepare reports by submitted app version and platform. For answers associated with Analytics, restricted processing compares reasons with measured Local Files setup completion and qualifying Local Files, Apple Music and FlowSet Samples use in the 168 hours before and after the service accepted the answer. Initial setup and reconfiguration are reported separately. Reports use the latest linked answer for each measured app instance, questionnaire edition and calendar month. They do not link devices, analytics reset scopes or questionnaires, and do not establish causality or prove that missing observations mean no use. Reports contain only aggregates with small groups suppressed, describing contributing installations or app instances rather than people or all setup attempts. Written comments are restricted to authorized human review. Comments, analytics and feedback identifiers, individual answers and usage histories are excluded from aggregate reports and AI inputs.
Optional App Analytics
App analytics stays off until you choose Accept in the app or enable Share Analytics in Settings. With permission, Firebase Analytics records broad app-use events, such as music-source categories including Apple Music and Local Files, Smart Set configuration outcomes, playback modes and engagement, feature-use categories, paywall and subscription steps, and successfully handled Apple Watch control categories. Firebase may also provide standard app events such as first open, app update, session, and engagement. The Watch app has no separate analytics SDK.
With permission, app analytics may record deliberate starts and observed results of initial Apple Music or Local Files setup, reconnection or reconfiguration, and optional FlowSet Samples downloads. Results can include completion, explicit cancellation or technical failure; Apple Music results can also indicate denied or restricted access or an unavailable account. These events record broad categories, with no account details, configuration contents, raw errors or custom attempt identifiers. Bundled Samples do not create setup events; an unobserved result is not recorded as cancellation or abandonment.
Source engagement may be recorded after 60 cumulative seconds of verified playback of Apple Music, Local Files or FlowSet Samples across playback sessions in a UTC day, at most once per source category per app instance per UTC day. This signal identifies the source category without track, file, playlist or sample-pack identifiers or exact listening durations. The app keeps capped current-day counters and qualification markers locally to apply this limit, replacing them as the UTC date advances.
Playback and setup activity from before consent is not replayed. Withdrawal clears these local source counters, markers and pending setup observations; allowing analytics again starts fresh after the provider reset. Aggregated reports help understand source use, recurring engagement and observed setup completion. App instances are not individual people, and FlowSet does not link these measurements across devices or analytics resets.
With your permission, app analytics may record the Grid or List layout visible while browsing FlowSet Samples playlists, whether it is the default or your saved choice, and successful switches between layouts. Broad browsing-screen and device-platform categories help assess display choices in aggregated reports. Your layout choice is saved on your device even when analytics is off; changes and visits from before consent are not replayed. This display measurement includes no playlist or track names or identifiers, search text, local paths, artwork URLs, revisions or hashes, user content, precise playback history, or configuration contents.
With your permission, pseudonymous app usage data is collected, including limited engagement signals for default FlowSet Samples playlists. Aggregated reports help improve FlowSet DJ, fix problems, guide future releases, and understand interest in sample content. This measurement excludes Apple Music and Local Files content, as well as the names and contents of files and playlists you create.
This Samples measurement identifies an approved official default playlist using a controlled key. A signal qualifies after 60 seconds of accumulated verified playback in a UTC day, with at most one signal per official playlist per app instance per UTC day. User-created playlists are excluded, even if they contain FlowSet Samples tracks. The signal contains no playlist names, track details, exact playback positions or durations, listening sequences, or custom-playlist contents. Aggregated reports show breadth and recurring engagement, not exact listening histories. This optional measurement is separate from the Samples delivery and security server request data described above.
When you create, update, or play a Smart Set, app analytics may include its number of structural actions in broad ranges: 0, 1–5, 6–10, 11–20, or 21 or more, or an indication that the size was not measured. Playback analytics may record reaching 5, 15, or 20 minutes of active playback. Free-limit events record the feature category and whether a playback or section-practice allowance ran out or a requested action was blocked. These measurements help FlowSet understand arrangement use, playback engagement, and demand beyond Free limits. They do not include exact action counts, arrangement contents, exact listening durations, or Smart Set or playback-session identifiers. Listening time and limit encounters from before consent are not replayed when you allow analytics.
App analytics may include a pseudonymous app-instance identifier and provider-supplied app version, device category, operating system, language, and approximate geography. FlowSet does not set a custom analytics user ID. Only the controlled keys described above identify official default playlists; arbitrary playlist or sample-pack identifiers are excluded. Its custom events do not contain music or playlist names, Apple Music or local-file identifiers, paths, queue contents, precise playback history or position, user-entered text, prices, receipts, offer codes, or transaction identifiers. Advertising identifiers and ad personalization are disabled; FlowSet does not use this data to track you across other companies' apps or websites.
Optional Website Analytics
The FlowSet DJ website uses Google Analytics 4 only after you select "Allow analytics." Before that choice, the website does not load Google Analytics or send analytics data to Google. App and website choices are separate.
Website analytics covers general website-use events such as page and session activity, plus FlowSet-specific App Store and FAQ events. The app_store_click event contains only the destination platform (iOS or Mac), the website placement, and a permitted campaign ID when a valid one is present. FAQ events record a repository-controlled question ID and topic when an answer is opened, and a result-count range, selected topic scope, and optional repository-controlled top-result ID after a search. The website does not send the words you type into FAQ search. These events do not contain contact-form values, music information, an account identifier, or other user-provided text.
FlowSet uses this information to understand website use, check whether install links are useful, and maintain the website. Google Analytics may process a pseudonymous browser identifier, basic browser and device information, approximate geography, referral context, and the event information described above. FlowSet does not set a custom user ID or use this data to identify an app installation.
If you arrive through a campaign link, the website validates utm_source, utm_medium, utm_campaign, utm_content, and utm_id. If you allow analytics, valid values are sent to Google Analytics as campaign source, medium, name, content, and ID. Sources are not restricted to a predefined list. Only a syntactically valid utm_id permitted by the configured campaign policy is used as the short campaign ID; that policy can allow named IDs or every valid ID.
A current permitted utm_id may also be added to an App Store destination as Apple's ct campaign parameter, together with FlowSet's public provider token and mt=8. This happens when the link is formed even if you decline Google Analytics. Before analytics consent, the campaign ID is kept only in the current page's memory and is not placed in browser storage or sent to Google by FlowSet. When you activate the App Store link, Apple receives the campaign ID as part of the destination URL and may use it for App Store campaign attribution under Apple's own terms and privacy practices. No other UTM value or arbitrary page query parameter is copied to the App Store link. The website does not join a website visitor or App Store click to a person or installed app.
This implementation does not include advertising pixels, remarketing, Google Signals, ads personalization, user-provided-data features, advertising identifiers, data brokers, or unrelated trackers. FlowSet DJ does not use it to track you across apps or websites owned by other companies.
Data Sharing
FlowSet DJ does not sell your data. FlowSet DJ does not share your data with advertisers or data brokers.
Data may be processed by Apple when you use Apple Music, StoreKit, App Store services, iCloud/device backup features, or other Apple platform services. If you activate an App Store campaign link, its permitted campaign ID and FlowSet's public provider token are included in the URL sent to Apple. Those services are provided by Apple and are subject to Apple's own terms and privacy policies.
FlowSet Samples server infrastructure may process limited request data as described in the "FlowSet Samples" section.
If you allow optional app or website analytics, Google processes the analytics data described above to provide Firebase Analytics and Google Analytics 4 to FlowSet. The app and website use separate analytics properties. FlowSet does not share this data with advertisers or data brokers.
When you deliberately send feedback, Google processes it through Firebase Cloud Functions and Firestore in a dedicated feedback project with EU storage. Firebase App Check and Apple app-verification services also process the operational information described in Optional Feedback. This processing does not require permission for ongoing analytics and does not send feedback to Firebase Analytics or Google Analytics 4.
Retention
App data stored on your device remains there until you delete it in the app, remove downloaded content, change your local file configuration, or uninstall the app.
Support emails may be retained as needed to respond to and manage support requests.
Limited server request data for FlowSet Samples may be retained as reasonably necessary for delivery, security, troubleshooting, abuse prevention, and service maintenance.
Accepted structured feedback and any associated analytics identifier are retained for up to 12 calendar months from acceptance; optional comments for up to 90 days; aggregate feedback reports for up to 24 calendar months. Restricted structured exports exclude comments and analytics identifiers. Separate restricted analytics-association and usage projections also expire within 24 hours or earlier when a source record expires. Exported copies, downloaded files, caches and reports follow their own expiry and deletion process and do not restart source retention. Retry receipts expire after 24 hours and abuse counters after two days. Expired records are excluded from processing immediately; physical deletion uses asynchronous database expiry and scheduled cleanup and may take longer.
Ordinary feedback request and application logs have a retention limit of 30 days. Cloud-provider mandatory audit and security records may have longer required retention. App-verification and network providers also process service metadata under their applicable retention practices. FlowSet restricts operational access and does not deliberately log answer contents, comments, feedback identifiers or verification tokens.
Turning Analytics off stops future feedback associations and resets local analytics data; it does not automatically remove associations already accepted. Clearing local feedback data, discarding a pending answer, resetting analytics or uninstalling the app does not delete feedback already accepted by the service. You can contact support to request deletion. When a request can be verified and the relevant questionnaire participant records located, deletion covers accepted answers, associated comments, analytics associations, retry receipts and known restricted copies. Aggregate reports are withdrawn or recomputed when required by the erasure process. If the local feedback identifier has been lost, FlowSet may be unable to locate your earlier answers; it does not create an account or use analytics associations as a support identity lookup. Do not send identifiers in an ordinary support message; support must arrange a restricted process if needed.
App and website analytics choices are stored separately on your device and in your browser. A decline may be followed by one non-blocking new invitation on a later app launch or website visit after at least 180 days; another decline restarts that interval. Turning analytics off yourself in app Settings or the website's manual Analytics choices control prevents automatic invitations until you choose to allow it. A grant remains in effect until you withdraw it. Data already collected is subject to the configured Google Analytics and BigQuery retention and deletion settings; before an analytics-enabled app release, FlowSet will verify a 24-month limit for BigQuery raw-event exports. Withdrawing consent stops future collection and resets locally stored app analytics data or clears accessible website analytics cookies, but does not automatically delete data already transmitted. A permitted campaign ID is stored only for the current browser-tab visit after website consent; without it, a current permitted ID is held only in page memory until the page closes or reloads without the ID.
Your Choices
You can:
- Revoke Apple Music permission in iOS Settings.
- Remove Local Files access by changing or clearing the configured folders in FlowSet DJ.
- Delete downloaded FlowSet Samples packs or playlists in the app.
- Delete app data by uninstalling FlowSet DJ from your device.
- Allow, decline, or later withdraw optional app analytics in FlowSet DJ Settings, and optional website analytics using the Analytics choices control in the website footer. Withdrawing website consent disables future Google Analytics events, clears the stored visit campaign ID, and removes Google Analytics cookies that the website can access. A permitted utm_id present on the current page can still be included in an App Store campaign link as described above.
- Choose No thanks or close an unsent questionnaire without sending feedback. Later offers are governed by local setup-attempt and timing rules, including after a dismissal.
- Review a saved feedback answer in Local Files Settings and explicitly retry or discard it within its 24-hour lifetime. Discarding it stops further retry; deletion of accepted feedback requires the separate support process described above.
- Use browser controls to block or delete cookies and site storage.
- Contact support using the contact link below.
Children's Privacy
FlowSet DJ is not directed to children. The app does not knowingly collect personal information from children.
Changes to This Policy
This Privacy Policy may be updated from time to time. If the policy changes, the updated version will be made available through the app, website, or App Store listing.
Contact
If you have questions about this Privacy Policy, contact: