Privacy Policy
1. Introduction
Flower ("app", "we", "our") is a mobile app that helps users practice dance with their own videos while storing most app data locally on the user's device. This Privacy Policy explains what information Flower collects, how it is used, how it is stored, and how it is protected.
We take user privacy seriously. Flower is designed so that most data remains on your device. The app does not currently include advertising networks, analytics trackers, or third-party tracking pixels.
This policy applies from the moment you download or use Flower. By using the app, you acknowledge the data practices described in this policy. If you have questions, contact us using the details below.
This policy is prepared with consideration for applicable privacy rules, including Turkish Personal Data Protection Law No. 6698 and the European Union General Data Protection Regulation where applicable.
2. Information We Collect
Flower collects limited categories of information needed to provide app features and personalize the experience. The data may include profile information such as a name or nickname, support contact information provided by the user, body measurements used for calorie estimation, practice duration, video watch time, app open days, and streak data.
Flower may also process subscription status, purchase verification information, offer interactions, profile photo, uploaded videos, video thumbnails, device model, iOS version, and app version.
Unless this policy says otherwise, this information is stored locally on your device and is not sent to Flower servers.
3. Profile and Performance Data
When users create a profile, they may provide a name, profile photo, weight, height, age, date of birth, gender, dance level, goals, and practice frequency. This information is used to personalize the app experience.
Calorie estimates are calculated using the Mifflin-St Jeor basal metabolic rate formula. The estimate uses weight, height, age, gender, session duration, and practice intensity. The result is informational and is not medical advice.
Dance level, goals, and practice frequency may be used to provide app feedback, motivation, and statistics. This information stays on the device unless otherwise stated. Users can update or delete profile information in the app.
4. Videos and User Content
Flower allows users to add videos from the device gallery or file system. Uploaded videos are stored locally in the app's flower-media directory. Videos are not uploaded to Flower servers or third-party services by Flower.
Video metadata, including video name, duration, thumbnail, and markers added by the user, is stored locally to organize the video library and display practice history.
When users pick media through iOS system interfaces, Flower receives access only to the items the user selects. Users are responsible for making sure they have the rights needed to use any videos they add to the app.
5. Practice and Usage Data
Flower records practice activity to show personal statistics. A practice session is generally recorded when a video is watched or practiced for at least 5 seconds.
For each session, Flower may store the video practiced, session duration, session date and time, and estimated calories. The app also tracks daily practice time, app open days, streaks, total practice count, and video selection counts.
Practice and usage data is stored locally on the device. When the user deletes local account data, this information is permanently removed from the device.
6. Subscription and Payment Data
Flower uses RevenueCat to manage subscriptions purchased through the Apple App Store. RevenueCat helps verify App Store receipts, subscription status, plan type, trial status, and purchase restoration.
Flower does not collect, store, or process credit card numbers, bank account details, or other sensitive payment credentials. Payment processing is handled by Apple's App Store payment system.
RevenueCat is used only to verify subscription access and determine whether the app should unlock Free or Pro features. RevenueCat's own privacy policy applies to data processed by RevenueCat.
7. Onboarding Information
Flower includes an onboarding flow to personalize the app. During onboarding, users may answer questions about dance goals, dance level, practice barriers, and preferences for motivational tone.
This onboarding data may be used to classify a local tone segment, such as junior, genz, adult, or pro_focused. Tone segmentation helps choose app messaging and notification style.
Onboarding data is processed and stored locally on the device. Users can restart onboarding or update preferences from inside the app where available.
8. Device and Technical Data
Flower may use limited technical information such as device model, iOS version, app version, and app performance context to support compatibility and troubleshooting.
The app may contain settings related to crash reporting or analytics preferences. At the time of this policy, Flower does not include a crash reporting SDK or analytics SDK that sends such data to a third-party analytics provider.
If analytics or crash reporting services are added in the future, users will be informed as required by applicable law.
9. Notifications
Flower uses local notifications. Local notifications are created and managed on the user's device without using an external push notification server.
Notification categories may include reminders, motivation, streak reminders, feature announcements, practice suggestions, goal reminders, community-style prompts, and special day messages.
Notifications are limited by quiet hours and rate limits. Users can manage notification preferences in the app and through iOS settings.
10. Widget Data
Flower provides iOS widgets such as Motivation, Heatmap, Stats Small, and Stats Medium. Widgets show selected practice and motivation information on the iOS home screen.
Widget data is shared locally between the app and widgets using Apple's App Group mechanism. It may include today's practice minutes, streak, weekly practice days, heatmap data, and motivational quotes.
Widgets do not display video content, email, or payment details. Widget data remains on the device.
11. How We Use Data
Flower uses personal data only for app-related purposes, including providing app features, storing videos locally, showing practice history, personalizing the user experience, estimating calories, verifying subscription status, responding to support requests, improving app behavior based on feedback, sending local notifications, and meeting legal obligations.
We aim to process only the data needed for each purpose. Flower does not sell personal data.
12. Third-Party Services
Flower uses RevenueCat for subscription management and verification. RevenueCat may process App Store receipt and subscription information needed to confirm access.
Apple App Store services are used for app distribution, subscription billing, purchases, cancellation, and refund flows. Apple policies apply to those transactions.
Flower does not use advertising networks, social media tracking pixels, or third-party data brokers in the app.
13. Data Retention
Most Flower data is kept on the user's device for as long as the user keeps using the app and does not delete local account data. When the user deletes local account data, personal data, videos, and practice data controlled by the app are permanently removed from the device.
If the app is removed without using the in-app deletion flow, some device-level storage behavior may depend on iOS. Users who want to remove Flower data should use the in-app account deletion flow or clear app data through device settings where available.
Subscription transaction records handled by Apple or RevenueCat may be retained according to those providers' policies and legal requirements.
14. Data Security
Flower stores most user data locally using iOS app storage and the app documents directory. iOS sandboxing helps isolate app data from other apps.
Technical protections include iOS data protection, app sandboxing, and local file isolation. Administrative practices include data minimization and limiting access to user support information to legitimate support purposes.
No method of storage is completely risk-free. Users should protect their device with appropriate passcodes, biometric protection, and system updates.
15. User Rights
Depending on applicable law, users may have rights to access, correct, delete, restrict, object to processing, or request portability of personal data. Because most Flower data is stored locally, many rights can be exercised directly in the app by editing or deleting local information.
For support or privacy requests, contact us by email. We may request information needed to verify and process the request.
16. Children's Privacy
Flower is not intended for children under 13 and does not knowingly collect personal data from children under 13. Users must be at least 13 years old to use the app.
If we learn that a child under 13 provided personal data, we will take appropriate steps to delete that information. Parents or guardians may contact us to request deletion.
Users aged 13 to 18 should use the app with permission from a parent or legal guardian where required.
17. International Transfers
Because most Flower data remains on the user's device, international transfers are limited. Subscription verification through RevenueCat may involve processing by a service provider based outside the user's country.
RevenueCat and Apple process subscription-related information according to their own policies and applicable safeguards. Other local app data is not intentionally transferred by Flower to external servers.
18. Changes
Flower may update this Privacy Policy from time to time. Changes may be published in the app or on the website. The date at the top of the policy shows the latest update date.
If users do not agree with changes, they should stop using the app and may delete local app data.
19. Contact
If you have questions, concerns, or requests about this Privacy Policy or personal data, contact us:
Email: flowerdanceapp@gmail.com
We aim to respond within the timeframes required by applicable law.
