Privacy Policy

Who we are

Feisly is operated by DeadBeet LLC. This Privacy Policy explains how Feisly handles information in the Feisly iOS, iPadOS, and Android apps, the Feisly website, and related support and correction request tools.

Contact us at [email protected] or through the correction/removal request form.

What Feisly is

Feisly helps Irish dance families, dancers, schools, and instructors find feiseanna, save events, follow dancers and schools, review public competition results, track registration deadlines, and receive optional notifications.

Feisly aggregates public feis schedules and public result information posted by organizers and tabulators. Feisly is not the official source for any feis, registration window, competition, dancer result, or tabulator posting.

Information you provide directly

If you email us, join the launch list, or submit a correction or removal request, we collect the information you choose to provide. This may include your name, email address, relationship to the request, feis names, dancer names, school names, source links, request details, requested action, and any screenshot or image you attach.

We use this information to respond, review the request, correct or remove information where appropriate, send requested launch updates, and maintain a record of support and correction work.

Information that stays on your device

Feisly stores your followed dancers, saved feiseanna, followed schools, settings, recent result matches, and notification preferences locally on your device. If you choose to enter a dancer birth year or birth month, Feisly uses that information for local age estimates and better result matching.

Selected local data syncs between your own Apple devices using Apple's iCloud Key-Value Store. DeadBeet LLC does not operate a server that can read your private iCloud Key-Value Store data. Apple processes iCloud data under Apple's own privacy terms and settings.

Optional Feisly accounts

You can use Feisly without an account. If you choose to create one, Feisly uses Sign in with Apple or Google Sign-In through Firebase Authentication. Apple, Google, and Firebase may process your provider account identifier, authentication tokens, name, email address, and related sign-in information under their own privacy terms. Feisly may display the name or email returned by your sign-in provider on your device.

Feisly's separate account database stores a Firebase user identifier, an opaque Feisly account identifier, an opaque family-space identifier, family role, and account timestamps. It does not store your Apple or Google password, tabulator credentials, followed dancer list, saved feiseanna, Scorebook results, judge comments, or precise location. Feisly does not use Firebase Analytics or Firebase Ads.

A family space is created as account infrastructure, but family invites and shared Scorebooks are not available yet. Creating an account does not share private app data with another person.

Scorebook and tabulator connections

Scorebook can import personal results and feedback that you choose to access through a supported tabulator connection. Tabulator usernames, passwords, and website sessions remain inside that tabulator's website session on your device. Feisly does not receive or store those passwords on its servers, and Feisly Support will not ask you to send a password.

Imported Scorebook data is stored in protected, backup-excluded app storage on your device and is kept separate from Feisly's public results database. It is not uploaded by creating or using a Feisly account. Deleting a Feisly account does not delete local Scorebook imports; those can be deleted separately in the app.

Location

If you grant location access, Feisly uses your location on-device to show nearby feiseanna and distance estimates. Your precise location is not sent to Feisly's backend.

If you enable nearby new-feis notifications, Feisly may send coarse region codes to the backend so the app can receive alerts for new events in a broad area. These region codes are not precise GPS coordinates.

Notifications

If you enable notifications, Feisly may register your app installation with the Feisly backend and Apple Push Notification service or Firebase Cloud Messaging. The registration can include an anonymous installation ID, platform, bundle ID, app version, build number, push environment, push device token, enabled state, saved feis IDs, notification preferences, optional coarse nearby-region codes, and dancer-result watch keys.

For paid dancer-result alerts, Feisly sends deterministic hashed watch keys derived from followed dancer names and, when available, school names. Feisly does not send exact location, birth years, birth months, plain followed dancer names, or plain followed school names for this feature.

Subscriptions and purchases

Feisly uses Apple and Google in-app purchase systems and RevenueCat to offer and manage Feisly Plus monthly and annual subscriptions and previously purchased Lifetime Unlock access. Purchase processing may involve purchase history, product identifiers, entitlement status, receipt validation, subscription lifecycle events, transaction amounts, and an app-specific RevenueCat customer identifier.

Feisly does not send followed dancer names, saved feiseanna, precise location, birth details, or private support request contents to RevenueCat. When you sign in to Feisly, RevenueCat receives the opaque Feisly account identifier so purchase access can follow that account. RevenueCat does not receive your Scorebook data or tabulator credentials from Feisly. Apple, Google, and RevenueCat process purchase-related data under their own terms and privacy policies.

No cross-company advertising tracking

Feisly does not request App Tracking Transparency permission and does not track you across other companies' apps or websites. The current app does not include the Meta SDK, Firebase Analytics, Firebase Ads, or an Android advertising-ID permission.

Feisly does not send followed dancers, saved feiseanna, followed schools, birth details, precise location, Scorebook data, or support and correction contents to an advertising attribution service.

Diagnostics and app stability

Feisly uses Sentry for crash and non-fatal error reporting when the app is configured with a Sentry project. These reports help us diagnose backend errors, purchase errors, crashes, and app stability issues.

Feisly configures Sentry with default personally identifying data disabled, network breadcrumbs disabled, failed-request capture disabled, and sanitized route labels for backend errors. Reports may still include technical details such as app version, build number, operating system, device model, error category, stack traces, and sanitized error descriptions.

Backend requests, search, and logs

Feisly's backend provides public feis schedules, public results, dancer suggestions, school data, recaps, status information, optional account bootstrap and deletion, push registration, and correction request handling. When you use app features that require backend data, the app sends the request needed to provide that feature. For example, dancer or school search text may be sent to the backend so Feisly can return search results.

The Feisly backend and website run on Cloudflare. Like most internet services, Cloudflare and the Feisly backend may process request metadata such as IP address, user agent, URL, route, request time, status code, and traffic routing data for security, operations, debugging, and service reliability.

Website measurement

The Feisly website does not load Google Ads or third-party analytics tags and does not send App Store or Google Play link clicks to an advertising measurement service.

Cloudflare may still process the limited technical request metadata described above to deliver, secure, and operate the website.

Public feis and result data

Feisly displays public information from organizer and tabulator sources, including FeisWorx, iFeis, FeisWeb, QuickFeis, FeisInfo, and similar public sources. This may include feis names, dates, locations, registration status, source links, competition information, adjudicator names, dancer names, school names, placements, and other public result context.

Feisly's backend is designed to minimize sensitive competitor data. It does not intentionally store date of birth, gender, score sheets, or other rich private competitor details from upstream placement responses.

How we use information

• Provide app features such as saved feiseanna, dancer history, school views, maps, search, results, and notifications.
• Authenticate optional accounts and maintain their opaque account and family-space records.
• Process purchases, restore purchases, and manage paid entitlements.
• Respond to support, launch-list, correction, and removal requests.
• Improve reliability, debug errors, protect the service, and maintain source accuracy.
• Comply with legal obligations, enforce terms, and protect users, sources, and Feisly.

What we do not do

• We do not sell personal data.
• We do not track you across other companies' apps or websites.
• We do not use followed dancer data for advertising.
• We do not use saved feiseanna, followed schools, birth details, or precise location for advertising.
• We do not send precise location to the Feisly backend.
• We do not intentionally collect score sheets, date of birth, gender, or rich competitor profiles from public result sources.

How we share information

We share information with service providers only as needed to operate Feisly. These providers include Apple for iCloud, App Store purchases, push notifications, and optional authentication; Google for Google Play purchases, Firebase Authentication, Google Sign-In, and Firebase Cloud Messaging; Cloudflare for website, backend, account records, storage, and operational infrastructure; RevenueCat for purchases and entitlements; and Sentry for crash and error diagnostics.

We may also disclose information if required by law, to protect rights and safety, to investigate misuse, or in connection with a merger, acquisition, financing, reorganization, or sale of assets, subject to applicable law.

Retention

Local app data remains on your device until you delete it, clear it in the app, remove the app, or your Apple/iCloud settings remove it. Push registration data is retained while needed to provide notifications, manage preferences, prevent duplicate sends, and operate the service.

Support, launch-list, correction, and removal requests are retained as long as reasonably needed to review, respond, maintain records, prevent repeat errors, and protect the service. Diagnostic information is retained according to our Sentry project settings and operational needs.

Optional account records are retained while the account exists. Using Delete Feisly Account removes the Feisly account and family-space records controlled by Feisly and requests deletion of the Firebase Authentication identity. Service providers may retain limited security, transaction, or operational records under their own policies and legal obligations.

Your choices

• You can disable location access in your device settings.
• You can disable notifications in the app or in your device settings.
• You can remove saved feiseanna, followed dancers, and followed schools in the app.
• You can use Feisly as a guest, sign out, or delete an optional Feisly account in the app.
• You can separately delete local Scorebook imports in the app.
• You can restore purchases through the App Store or Google Play and Feisly's restore flow.
• You can request correction, removal, or review of public data shown in Feisly.
• You can contact us about support records or launch-list email removal.

Children and public result data

Feisly is intended for parents, dancers, schools, instructors, and other Irish dance community members. Feisly is not directed to children under 13 as a child-focused online service, and we do not knowingly collect private personal information directly from children under 13.

A parent or guardian should create and manage an optional Feisly account for a child who is not old enough to manage an account under applicable law or the sign-in provider's terms.

Public feis results may include names of dancers who are minors because those results were publicly posted by organizers or tabulators. If you are a parent, guardian, dancer, school, organizer, or tabulator and you believe information should be corrected, removed, or blocked, contact us and we will review it.

Security

We use reasonable technical and organizational measures designed to protect information. No method of transmission or storage is perfectly secure, and we cannot guarantee absolute security.

International users

Feisly is operated from the United States. If you use Feisly from outside the United States, information may be processed in the United States and other locations where our service providers operate.

Changes

We may update this Privacy Policy from time to time. The date at the top shows when it was last updated. If we make material changes, we will update this page and may provide additional notice where appropriate.