Privacy Policy

Effective June 3, 2026 · Last updated August 8, 2026

This policy explains what RotorPulse collects, why it is used, which service providers process it, and how you can control or delete your information.

RotorPulse (“RotorPulse,” “we,” “our,” or “us”) provides a website, an iOS app, an Android app, and an Apple Watch companion for RC helicopter pilots. RotorPulse is the data controller for the personal data described here and is operated from the United States. Contact [email protected] for privacy questions or requests.

1. Information we collect or process

• Account and identity: email address, username, RotorPulse user ID, authentication records managed by Supabase, age and policy confirmations, and an Apple or Google provider identifier, email, or name when that provider supplies it. RotorPulse does not receive or store your plaintext password.
• Profile and social data: avatar, bio, user-entered location and country, flying experience, profile color, public-hangar choice, transmitters, followers, following, and favorites.
• Preferences and app activity: saved listings and events, favorite manufacturers and helicopter models, recently viewed helicopter models, catalog search terms and search history, watched content, notification and email preferences, theme and onboarding choices, and other feature state needed to synchronize your experience.
• Community and messages: posts, replies, votes, mentions, watched content, direct-message text and images, participants, timestamps, read state, pins, mutes, blocks, reports, and moderation context.
• Hangar and flight data: helicopter and custom-build details, photos, batteries and cycle counts, flight durations and dates, optional precise or approximate flight coordinates and place names, maintenance logs, notes, and Apple Watch flight transfers.
• Events and marketplace: attendance choices, submitted event details, organizer-claim relationship, evidence links and notes, listing titles, descriptions, price, condition, category, user-entered location, photos, and listing or seller reports.
• Notifications and support: an Apple Push Notification service device token on iOS or Firebase Installation ID and related Firebase Cloud Messaging registration information on Android, notification payloads, preferences and records, watched subscriptions, bug reports, support requests, app and operating-system version, device model, severity, report type, and details you provide.
• Optional iOS tip interaction: StoreKit product availability, localized displayed price, purchase state, and completion status. Apple processes the purchase; RotorPulse does not receive payment-card information.
• Technical and security data: request time, IP address, device or browser type, service logs, authentication events, rate-limit records, and security or moderation signals needed to operate and protect RotorPulse.

An email address, username, authentication record, age confirmation, and agreement to the Terms are required to create an account. Other profile fields and device permissions are optional. Declining an optional permission disables only the related feature. In an Android build configured for push notifications, Firebase may create an app-installation identifier as part of initializing its messaging infrastructure. RotorPulse associates that identifier with a signed-in RotorPulse account only when notification delivery is enabled for that account.

2. Public, shared, and private information

Your username, profile details, profile photo, social connections, public hangar, community content, event attendance where displayed, and marketplace listings may be visible to other RotorPulse users. Direct messages are shared with their participants. Private hangar records, batteries, flight logs, maintenance records, notification settings, and account details are used for your account unless you deliberately share them through a public feature. Reports and the relevant content or context may be reviewed by RotorPulse.

3. Sign-in and device security

Depending on your platform, you may sign in with email and password, Apple, or Google. RotorPulse receives only the identity information the provider supplies and never receives your Apple ID or Google password. Apple may provide a private relay address if you choose Hide My Email.

When a platform-supported convenience sign-in feature is enabled, credentials are protected locally with Apple Keychain or Android Keystore and the device’s security controls. Face ID, Touch ID, fingerprint, and face-matching data remain under the operating system’s control and are not received by RotorPulse.

4. Photos, camera, and automated image safety review

RotorPulse accesses only images you select with the system photo picker or choose to capture with the camera. Images may be used for profiles, posts, replies, direct messages, hangar or custom-build records, and marketplace listings.

Before an image is uploaded, RotorPulse sends the selected image to Google Cloud Vision SafeSearch for automated classification of adult, violent, or otherwise unsafe content. By choosing an image for upload after acknowledging this policy, you instruct RotorPulse to perform this review. Google processes the image as RotorPulse’s service provider. Automated results can be imperfect; an image may be rejected or referred for human moderation. Email [email protected] to request human review. RotorPulse does not use images for advertising or cross-app tracking.

5. Location, maps, directions, and weather

RotorPulse requests foreground location only for a feature you choose. Event-distance sorting may use your current location without saving it to your account. A flight log stores coordinates and a resolved place name only when you choose to attach a flying location. On Android, the operating system may provide precise or approximate location according to your permission choice. RotorPulse does not collect background location. User-entered profile and marketplace locations may be public where displayed.

Apple MapKit, geocoding, and WeatherKit may process coordinates for iOS maps, place names, event distances, and venue weather. On Android, the operating system's location provider supplies the requested coordinates and the device's configured geocoding service may process those coordinates to return a place label. The Android event map loads Leaflet resources from unpkg and map tiles from OpenStreetMap; those services may receive standard network data and the viewed map area. If you open directions in an external maps app, that provider processes the destination and any location information according to its own policy.

6. Calendar integration

When you choose Add to Calendar, RotorPulse supplies the selected event’s title, dates, venue, location, and description to the platform calendar interface. On iOS this uses EventKit; on Android it opens your chosen calendar app’s event screen. RotorPulse does not read or upload your existing calendar events through this feature.

7. Apple Watch companion and local data

If you use the Apple Watch companion, the iPhone app sends a limited Hangar snapshot to your paired watch, including your account identifier, helicopter and battery details, and recent selections. The watch stores it locally for flight timing and sends completed flight details to the iPhone for saving. Account credentials are not sent to the watch. Watch account data is cleared when you sign out, use guest mode, switch accounts, or delete your account, including after a disconnected watch reconnects.

RotorPulse also stores limited settings and caches on your devices, including theme and onboarding choices, recent selections, catalog search history, live-flight state, image caches, and notification state. Supported preferences and catalog search history may also synchronize through your signed-in account. Servers that host an image receive the network request needed to display it; downloaded images may remain in a bounded device cache until refreshed, evicted, app storage is cleared, or the app is removed. Depending on the data and platform, other local information is cleared when you sign out, reset the feature, delete your account, or remove the app.

8. How we use information

• Authenticate users, maintain accounts, synchronize supported devices, and provide requested features.
• Display public profiles and content and deliver private messages to their participants.
• Provide hangar, battery, flight, maintenance, event, marketplace, notification, weather, calendar, and optional tip features.
• Remember saved items, recently viewed helicopter models, catalog searches, and other preferences across supported devices.
• Filter unsafe images, enforce community rules, investigate reports, prevent abuse, and protect users and the service.
• Send authentication, preference, support, bug-report, moderation, and notification communications.
• Diagnose problems, maintain reliability and security, comply with law, and protect legal rights.

9. Website data and external resources

RotorPulse’s website is delivered through Cloudflare Pages. Cloudflare may process standard request information such as IP address, browser or device type, requested page, referring page, and request time for delivery, security, and operational logs.

The public home page requests the Inter typeface from Google Fonts and an affiliate verification resource from AvantLink. Those providers receive the network information needed to serve the resource and handle it under their own policies. RotorPulse does not use these resources to build cross-app profiles or serve targeted advertising.

10. Service providers and data sharing

RotorPulse shares information only as needed for a feature you use, service delivery, security, moderation, support, or legal compliance. Current providers include:

• Supabase: authentication, database, realtime messaging, Edge Functions, and file storage. RotorPulse’s primary Supabase project is hosted in the United States.
• Apple and Google: optional account sign-in, subject to the providers’ Apple Privacy Policy and Google Privacy Policy.
• Apple platform services: APNs, Keychain, biometric APIs, MapKit, geocoding, EventKit, StoreKit, and WeatherKit where the related iOS feature is used.
• Firebase Cloud Messaging and Firebase Installations: Android push-notification registration and delivery, including a Firebase Installation ID, related registration information, and the notification payload. RotorPulse does not enable Firebase advertising or analytics products.
• Google Cloud Vision SafeSearch: automated image safety classification before upload.
• Resend: account, preference, bug-report, support, and moderation email delivery.
• Cloudflare: website hosting, delivery, and security.
• OpenStreetMap and unpkg: Android event-map tiles and code resources.

Providers may process information in the United States and other locations where they or their subprocessors operate, subject to their applicable safeguards. External retailers, manufacturers, event sites, sellers, map apps, and other sites have their own practices after you choose to leave RotorPulse.

11. International data transfers

RotorPulse is operated in the United States, and its primary Supabase project is hosted there. If you use RotorPulse from the European Economic Area, United Kingdom, or another jurisdiction with transfer restrictions, information may be transferred outside your jurisdiction. Where required, RotorPulse relies on safeguards made available by its providers, such as an applicable adequacy decision or standard contractual clauses. Contact RotorPulse for information about the safeguard relevant to a particular transfer.

12. Legal bases where applicable

• Performance of a contract: creating and maintaining your account and providing the community, messaging, hangar, flight, event, marketplace, notification, support, and optional features you request.
• Legitimate interests: securing and operating RotorPulse, moderating content, reviewing image safety, preventing fraud and abuse, supporting users, diagnosing faults, and protecting legal rights. RotorPulse balances these interests against your rights and expectations.
• Consent: optional permissions or choices where consent is required. You may withdraw consent through the applicable iOS or Android settings, an in-app control, or by contacting RotorPulse without affecting earlier lawful processing.
• Legal obligations: retaining or disclosing limited information when required by applicable law, valid legal process, or protection of legal claims.

13. Notifications, marketplace, and optional tips

If you enable supported push notifications, RotorPulse stores an iOS device token or associates an Android Firebase Installation ID and related registration information with your account, together with the preferences and context needed to deliver alerts. Notification payloads may contain the alert text and identifiers needed to open the relevant post, forum section, profile, or notification screen. You can disable notifications in your device settings and manage available preferences in RotorPulse. Signing out or deleting your account removes the account's server-side push registration; Firebase or the operating system may retain installation-level information according to their own lifecycle until app data is reset or the app is removed. Marketplace is a classifieds service only: RotorPulse does not process private-deal payments, shipping, escrow, or transaction disputes. Optional tips are offered only where shown on iOS, are processed by Apple through StoreKit, and do not unlock features.

14. Retention and account deletion

Account information and user content are generally kept while your account is active or until you delete the applicable content. Reports, delivery audits, security records, and support context are kept only as long as reasonably needed to investigate issues, enforce the Terms, prevent repeat abuse, comply with law, or protect legal claims.

You can permanently delete your account in RotorPulse. On Android, choose More → Delete Account. On iOS, choose More → Profile → Account Controls → Delete Account. If you cannot access the app, use the public RotorPulse Account Deletion page to submit a request without reinstalling the app.

Account deletion removes or anonymizes the account and associated personal content, including profile data, provider identity, stored images, posts and replies, direct messages attributable to the account, marketplace listings, hangar and flight records, notifications, server-side device-token or installation-ID registrations, catalog search history, preferences, and social references.

Limited information may remain where required for legal compliance, safety, moderation, abuse prevention, or legal claims; in another user’s records after you are no longer identifiable; or in protected backups until overwritten during the provider’s normal backup cycle. Deleting a conversation from your own message list is different from deleting your account and does not delete another participant’s copy.

15. Your choices and rights

You can edit profile data, control public-hangar visibility, decide whether to save a flight location, manage supported notifications and email preferences, manage watched content, block users, delete conversations and listings, report safety issues, sign out, and delete your account. Camera, photo, location, calendar, biometric, and notification access can be changed in iOS or Android system settings.

Depending on where you live, you may request access, correction, deletion, restriction, objection, or portability; withdraw consent; or appeal a decision about a request. European Economic Area and United Kingdom users may complain to the data-protection authority where they live, work, or believe an infringement occurred. RotorPulse may verify your identity and will normally respond within one month, subject to extensions permitted by law. RotorPulse will not discriminate against you for exercising an applicable privacy right.

California notice: RotorPulse does not sell personal information and does not share personal information for cross-context behavioral advertising as those terms are defined by California law.

16. Automated decisions and human review

Google Cloud Vision SafeSearch may automatically prevent a selected image from being uploaded. That screening does not make a decision with legal or similarly significant effects. Contact [email protected] to request human review of an image result or appeal a moderation action.

17. Children

RotorPulse is intended for people age 13 and older. We do not knowingly collect personal data from a child under 13. If local law requires parental or guardian authorization to enter the Terms or use an optional feature based on consent, the feature may be used only with that authorization. Contact us if you believe a child under 13 created an account so we can investigate and delete it.

18. Security

RotorPulse uses reasonable technical and organizational safeguards, including encrypted transport, secure authentication, database row-level access controls, least-privilege service access, authenticated provider functions, rate limits, and Apple or Android platform protections. No internet service can guarantee absolute security.

19. Changes to this policy

We may update this policy as features, providers, or legal requirements change. We will update the date above and provide additional notice or request a new acknowledgement when appropriate.

20. Contact

Data controller: RotorPulse
Privacy or data request: [email protected]
Support: rotorpulseapp.com/support
Account deletion: rotorpulseapp.com/delete-account
Terms: rotorpulseapp.com/terms