Skip to content

Privacy Policy

Effective: March 16, 2026 · Last updated: November 17, 2026

Harrisey Labs, LLC ("FIDA," "we," "us") operates the FIDA platform for dance event discovery and community connection. This Privacy Policy explains how we collect, use, share, and protect personal information when you use our website, mobile application, and related services (the "Service"). By using the Service, you acknowledge this Policy.

1. Information We Collect

Information You Provide

  • Account and profile data: name, username, email, password, profile photo, bio, city, country, dance styles, dance role, skill level, optional gender, notification and privacy preferences, and other profile fields. Optional fields such as gender appear on your public profile if you choose to provide them. For organizers and organizations, we also store public handles, including handles first taken from an existing username or organization address, and their ownership history.
  • Photos and media you upload: profile photos and showcase media on your profile, and images attached to event listings. Uploaded profile, event, and organizer images are served from publicly accessible storage, so anyone with the link can view them.
  • Event data: event listings you create or interact with (including venue names and addresses provided by organizers), RSVPs, saved events, event attendance history, and event feedback
  • Connections: when you connect with another dancer or organizer (including by scanning their QR code), we record who connected with whom, when, the event context if any, and any note you attach
  • Codes of conduct: organizers can publish a code of conduct for their events. Its current version is public while the code is active and the organizer or organization is publicly available. When you agree to a code, we record your account, the code version and event, when you agreed, whether it was a first agreement or a re-agreement, the version of the agreement screen wording, and your app version, platform and app language. When an editor accepts FIDA's rules for publishing codes, we record their account, the rules version and when they accepted.
  • Communications: messages, feedback, and support requests you send us

Information Collected Automatically

  • Usage data: we run our own first-party analytics on platform activity such as app opens, sign-ups, event views, event creation, RSVPs, reminders, shares, and completed purchases. These records are linked to your account and are filtered before storage to exclude fields like email addresses and venue addresses.
  • Device and network data: device type, operating system, browser type, unique device identifiers, IP address, and approximate location derived from IP.
  • Push notification tokens: when you enable push notifications, your device registers a push token and a device identifier with our push delivery provider (Expo), and notifications are delivered through Apple Push Notification service on iPhone. Push notifications are not yet available in the Android app. We also store the language you use FIDA in with your device's token, so notifications such as feedback requests reach you in that language. You can turn off delivery at any time in the app or in your device settings, and tokens are removed when a device reports them invalid.
  • Log, error, and crash data: server logs, error reports, performance data, and timestamps. Crash reports may include device identifiers, IP address, stack traces, and operational context at the time of a crash.
  • Cookies and similar technologies: see our Cookie Policy

Location Information

  • City you choose: your selected city, search radius, and any additional cities you follow are stored with your profile and power event discovery
  • Device location (optional, with your permission): if you grant location access, the app uses your device's location while you are using it to show events near you, calculate distances, and position the map. Your coordinates are used on your device to filter and sort events. To find the city and country you are in, your device may send them to its operating system's geocoding service, and the app remembers that city and country for your account on your device only. We never store your precise coordinates on our servers, and we never collect location in the background. You can revoke access at any time in your device settings.
  • Approximate location from IP: like most services, we and our infrastructure providers derive a rough location from your IP address for security and logging

Information from Third Parties

We may receive information from other users who interact with you on the platform, and, if you purchase a subscription, confirmation of your transaction from Apple or Google and our subscription management provider. We do not currently offer sign-in through third-party social accounts; if that changes, we will update this Policy.

On Android, FIDA can receive a shared FIDA event identifier through Google Play's install referrer so it can reopen that event after installation. We keep installation and first-open markers on your device and may remember the event there while you finish sign-in or setup. If you view or interact with the event while signed in, the event identifier and share-link source may be recorded in account-linked usage analytics.

2. How We Use Your Information

Service Operation

  • Creating and managing your account
  • Displaying events and organizers
  • Processing RSVPs and event interactions
  • Facilitating connections between users, including QR-based connections
  • Delivering notifications you have enabled
  • Sending transactional emails (such as confirmations and reports you request)

Calendar export

If you choose Add to calendar, FIDA opens your system browser with the event's title, dates, venue and address or online link, and its FIDA link. On iPhone, a public calendar file lets you add the event. On Android, these details are sent to Google Calendar to fill in an event form; you may need to sign in to Google before saving it. FIDA does not read your calendar. Copies saved outside FIDA are managed by the app or service you choose and do not update automatically when the event changes in FIDA.

Payments and Subscriptions

Organizer subscriptions are purchased through the Apple App Store on iPhone or Google Play on Android. Apple or Google processes the payment; we never receive your payment card details. We and our subscription management provider (RevenueCat) receive and store subscription status, plan, platform, product identifiers, and App Store or Google Play transaction identifiers linked to your account so we can activate and manage your subscription.

Personalization

We personalize your experience using inputs you control: your city and search radius, the cities and organizers you follow, your dance style preferences, and your activity such as saved events and RSVPs. We may in the future use usage data to test features, rank content, and improve recommendations; if we begin materially new processing, we will update this Policy first. We do not make automated decisions about you that have legal or similarly significant effects.

Analytics, Error Monitoring, and Product Development

We analyze platform activity to understand usage patterns, measure feature performance, and improve the Service. Our in-app analytics are collected first-party and stored in our own database; we do not embed third-party advertising or analytics SDKs in the app. On the website we use Vercel Analytics, a cookieless, aggregate analytics service. When a connection link opens in a browser, the page is general, FIDA does not look up whose code it is, and the code is not recorded in website analytics. We use Sentry for error monitoring and crash reporting (which may collect device identifiers, IP address, stack traces, and operational context at the time of a crash).

"Aggregated Data" means data derived from platform activity that has been combined, summarized, anonymized, or de-identified so that it cannot reasonably be used to identify you. We may use Aggregated Data for purposes including platform analytics, product development, business intelligence, investor reporting, and commercial partnerships. We do not share aggregates computed over groups small enough to identify individuals, and we do not attempt to re-identify de-identified data.

Email Communications

We use your email address for transactional and operational messages, such as account and security emails and reports you request. If we introduce marketing emails (for example, product announcements or event recommendations), every marketing email will include an unsubscribe link and you will be able to opt out at any time. Transactional messages related to your account cannot be opted out of while your account is active.

Safety and Enforcement

We use data, including reports you submit and moderation records, to detect fraud, abuse, spam, and violations of our Terms and Community Guidelines, and to enforce our policies.

3. How We Share Your Information

  • Other users: profiles are visible to other users of the Service. Your public profile includes your name, username, photo, bio, city, dance styles, skill level, dance role, and optional fields like gender if you provide them; showcase media, event listings, and certain RSVP and connection activity may also be visible depending on your settings. Organizer and organization information is publicly available, including to people who are not signed in: name, profile or organization images, bio, city, dance styles, website and Instagram links, follower count, public handles where assigned, and current or upcoming public events.
  • Organizers: if you RSVP to an event, the organizer may see your attendance depending on your settings. Organizers can view, and receive by email, reports containing the attendance information they are permitted to see under your settings, plus aggregate statistics about their events (for example, attendance and view counts, how many dancers are new or returning, and dance role, level, gender or home-city splits). Where a group is very small, even aggregate statistics may allow inference. Organizers and their active organization team see reports sent through the new feedback form as soon as they are sent, with no name, photo, author identifier or exact submission time. Reports from older app versions keep the grouped rule described under "Event feedback" below. For an event with an active code of conduct requirement, the event organizer and active organization team members who can access its guest list can see each attendee's agreement status, the version agreed to and when they agreed. Organizers' use of information you share with them is governed by their own practices.
  • Service providers: vendors who process data on our behalf under contractual data protection terms: Supabase (database, authentication, and file storage), Vercel (website hosting and analytics), Expo (push notification delivery), Sentry (error and crash reporting), RevenueCat (subscription management), and our email delivery provider
  • Address lookup services: to put an event on the map, we turn the address an organizer enters into map coordinates. An event address is part of the public event listing: the organizer chooses what to enter, and anyone using FIDA can see it. We send only the event's address, City and country (and, for an event in the United Kingdom, its postcode), never anyone's name, account details or device location. If an organizer enters a private home address, it is published and sent the same way.
    • United States events go to Geocodio. Organizers can enter a neighborhood or nearby cross streets instead; without a house number, nothing is sent to Geocodio and the event has no map pin. Geocodio processes these addresses under its own terms of use and privacy policy, which state that it encrypts data in transit and at rest, limits access to it, and does not sell personal information; we do not have a separate data protection agreement with Geocodio.
    • United Kingdom and European Union events, when supported, go to Geoapify (run by KEPTAGO LTD, Cyprus), whose results are built on OpenStreetMap data. We also send Geoapify the event's City on its own, to check the pin is in the right town. If Geoapify can't confirm the building (or, in the UK, the postcode), the event has no map pin. Geoapify processes these requests under its own terms and privacy policy.
  • Independent services: Apple (App Store billing, push notification delivery, and operating system services such as maps and geocoding that your device calls directly) and Google (Google Play billing, Google Play install-link recovery, the map in the Android app) handle data under their own privacy policies
  • Business transfers: in a merger, acquisition, or asset sale, your information may transfer to the acquiring entity under equivalent privacy protections
  • Legal requirements: we may disclose information when required by law, court order, or government request, or to protect our rights or users' safety
  • Aggregate data: we may share Aggregated Data (as described in Section 2) with partners, investors, and researchers

Each third party with whom we share user data is required, by contract or by its own published privacy commitments, to provide the same or equal protection of your data as stated in this Privacy Policy. This applies to any parent, subsidiary, or related entity that has access to user data.

We do not sell your personal information, and we do not share it with third parties for cross-context behavioral advertising. The Service contains no third-party ad networks and does not track you across other companies' apps or websites.

Event feedback

After an event you were Going to, FIDA may ask how it went. You can give a rating, pick topics that went well or need work, add an optional comment, or say you didn't go.

  • What organizers see: reports sent through the new form appear as soon as they are sent. The form says "Your feedback is anonymous." Each report shows its rating from 1 to 10 or that the dancer did not go, selected topics, any comment that is not hidden, and a coarse time such as "just now", "earlier today" or a calendar day. It shows no name, photo, username, author identifier or exact submission time. A per-event summary appears after the 7-day answer window closes, even with only one report. That summary includes only reports sent through the new form. At a small event, or from details in a comment, an organizer may still be able to guess who wrote a report. For an organization's event, its active team sees the same reports and summary. Organizers and team members can receive a notification when a report arrives, subject to their notification settings.
  • Reports from older app versions: these keep the grouped rule shown when they were sent. A date's results appear after its 7-day answer window closes, and only if at least 5 different dancers rated it. Dates of a repeating event that do not reach 5 on their own are grouped by month, and appear only if at least 5 different dancers rated across that month. Counts of fewer than 3 dancers are not shown. Comments appear only once at least 10 dancers have rated, in random order and without dates. These answers do not appear in the new individual report list or its per-event summary. Existing Insight comparisons and history continue to use the legacy grouped results and never include comments.
  • Comment protection: before organizers can see a comment, the names and usernames of the organizer and of dancers marked Going are replaced with "(name)" (dance words such as "salsa" and small words such as "the" are left as they are). Comments with handles, email addresses, phone numbers or links are not accepted. Other details can still identify you or others, so keep comments general.
  • Our private link to your answer: we keep which account gave each answer, only to allow one answer per date and to act on reports, until about 90 days after the answer window closes or until you delete your account, whichever comes first. Organizers never see it. While it exists, we may disclose it if required by law.
  • Reported comments: an organizer or their active team can report a comment, including a new report visible before the summary is ready. It is hidden at once, and FIDA staff review it. Staff can keep it hidden or show it again and, while the private link exists, stop the account that wrote it from leaving feedback comments, for a time or for good. Nothing else about that account changes. The organizer is never told who wrote it.

4. Data Retention and Deletion

  • Account data: retained while your account is active; removed promptly when you delete your account in the app, and in any case within 90 days of a verified deletion request, except for the retained records described below
  • Usage records and logs: retained for as long as reasonably necessary for the purposes described in this Policy, then deleted or de-identified
  • Support and email correspondence: retained as long as needed to handle the matter and for our records, or as required by law
  • Error and crash reports: retained up to 90 days by our error monitoring provider
  • Reminder records: when we create an event reminder, we keep a record linking your account and the event so we do not send the reminder twice. Deleting a notification does not remove this record. It is deleted when your account or the event is deleted.
  • Push tokens: removed when a device reports its token invalid; you can turn off delivery at any time
  • Event feedback: about 90 days after a date's answer window closes, we remove the private link between each answer and its account, and our record of whom we asked. Individual answers and comments, including reported ones, are deleted about 12 months after the answer window closes; legacy answers grouped by month are deleted together. Per-event summaries and legacy grouped results remain so organizers can follow their history. A thank-you note for a legacy result is deleted 24 months after the result appears. Feedback notifications stay like other notifications. If you delete your account, new-form reports already visible to the organizer stay, with every link to your account removed at once, and are deleted on this schedule. This also applies to legacy answers already in released results. Legacy answers not yet in released results and our record of whom we asked are deleted with your account. Keeping visible reports avoids revealing which report was yours through its disappearance. Once an answer is cut from your account, we can no longer find it to delete it sooner. When an organizer deletes their account, their feedback reports and results are deleted. A thank-you note is deleted with the account that sent it, including copies in dancers' notifications.
  • Insight history: we keep event and monthly totals, including views, attendance and returning-dancer statistics, with no set deletion date so organizers can follow their history. These totals contain no dancer account identifiers and may still include a dancer's contribution after that dancer deletes their account. They are deleted with the organizer's account or organization, and an event's totals are also deleted with the event.
  • Code of conduct agreements: your agreements are deleted with your account. While an agreement exists, you can read the exact version you agreed to. Deleting the organizer's account or the organization also deletes its code versions and the agreements linked to them. Earlier versions are not public: the organizer and active organization team members can read them, you can read versions you agreed to, and authorized FIDA moderators can read versions reported for review. Only the current version of an active code is public while its organizer or organization remains publicly available.
  • Organizer handles: we keep current and previous handles, the account or organization they belong to, when they were created and retired, and records of administrative changes, with no set deletion date, including after account deletion. These records manage link ownership and stop a handle being reused automatically. Public organizer lookups no longer return a deleted organizer's profile.
  • Safety records: reports, moderation, and enforcement records may be retained longer where reasonably necessary for safety, security, or legal compliance

5. Your Choices and How to Delete Your Data

Deleting your account: you can delete your account directly in the app under Settings. Deletion takes effect immediately and removes your profile, uploaded media, connections, and related records, subject to the retention exceptions in Section 4, including organizer handle records, event feedback, and safety or legal records. Residual copies may persist briefly in backups. The events you own or created and organizer pages you own are deleted. If you have upcoming published events or own organizer pages, the app shows their counts and asks you to type DELETE before confirming. New-form feedback reports already visible to an organizer remain without any link to your account; legacy answers not yet in released results are deleted. See Section 4 for the full feedback retention rules.

Revoking consent: you can turn off push notifications in your device settings. Notifications in FIDA Settings shows the current permission and lets you request permission or open those device settings. You can revoke location access in your device settings and adjust RSVP visibility in the app. Withdrawing permission does not affect processing already carried out.

Access and correction: you can view and edit your profile information in the app at any time. To request a copy of your data, ask us to correct it, or request deletion by email instead of in the app, contact support@fi-da.app. We may verify your identity before processing requests.

6. Security

We implement administrative, technical, and physical security measures. Data is encrypted in transit, and authentication tokens on your device are kept in your device's secure storage. No security system is impenetrable. We cannot guarantee absolute security. If you believe your account has been compromised, contact support@fi-da.app.

7. Minors

The Service is intended for users 18 and older. We do not knowingly collect personal information from anyone under 18. If we discover we hold data from a person under 18, we will promptly delete it.

8. If you are in the United Kingdom or the European Economic Area

Who is responsible. Harrisey Labs, LLC, United States, is the controller of your personal data for the Service. You can reach us at support@fi-da.app. We have not appointed a representative in the UK or the EU; please contact us directly.

Why we use your data (legal bases).

  • To provide the Service you asked for (contract): your account and profile, events, RSVPs, saved events, connections, codes of conduct, event feedback, notifications you turn on, and organizer subscriptions.
  • For our legitimate interests, balanced against yours: keeping FIDA safe and secure, preventing fraud and abuse, handling reports, our own first-party analytics, error monitoring and improving the Service, and aggregated statistics that can't identify you. You can object to this use (see below).
  • With your consent, which you can withdraw at any time: device location, push notifications, and optional profile details you choose to add.
  • To meet legal obligations: for example, keeping records we must keep, or answering lawful requests from authorities.

Your rights. You can ask us for a copy of your data, to correct it, to delete it, to limit how we use it, to receive it in a portable format, or object to processing based on our legitimate interests. Where we rely on consent, you can withdraw it at any time without affecting what we did before. You can delete your account in the app under Settings and edit your profile at any time; for anything else, email support@fi-da.app. We answer within one month, or tell you within that month if a complex request needs up to two more. We may need to confirm your identity first.

Complaints. You can complain to a data protection authority: in the UK, the Information Commissioner's Office (ico.org.uk); in the EU, the authority where you live, work, or where you think the problem happened. We'd appreciate the chance to fix things first at support@fi-da.app.

International transfers. FIDA is run from the United States, and our service providers store and process data in the United States and other countries. When UK or EU law requires a safeguard for this, we rely on our providers' data processing terms, which include the European Commission's standard contractual clauses and the UK's addendum to them, or on a provider's certification under the EU-US Data Privacy Framework and its UK Extension.

How long we keep data. See section 4.

Automated decisions. We do not make decisions about you based solely on automated processing that have legal or similarly significant effects.

9. Changes

We may update this Policy from time to time. Material changes will be communicated via email or prominent notice on the Service. Continued use after changes become effective constitutes acceptance.

Privacy questions: support@fi-da.app