Pulse

Privacy policy

Last updated: September 2, 2026

This privacy policy explains how Pulse processes personal data when you use the Pulse application and related services available through pulse-dance.com.

1. Data controller

Pulse is published in France by Idris Zekri, under the developer name Pulse Dance.

For any question about your personal data or to exercise your rights, you can contact us at:

contact@pulse-dance.com

2. Using Pulse without an account

Some Pulse features can be used without creating an account.

In that case, certain preferences needed for the app to work may be stored locally on your device, including:

  • your discovery filters;
  • your selected area or city;
  • your selected dances;
  • certain app settings.

Using online services may also involve the processing by the relevant technical providers of technical data required for network communications, such as IP addresses.

3. Creating and managing an account

If you create a Pulse account, we process in particular:

  • your email address;
  • a technical user identifier;
  • information required for your session and authentication;
  • your preferred dances;
  • your dance level;
  • your preferred discovery city or area;
  • events you save;
  • items added to your Pulse calendar;
  • organizer profiles you follow.

This information enables us to provide the features linked to your account.

Pulse does not currently ask dancers for their first name, last name, age, date of birth or gender.

Dancers do not have a public profile.

Their favorites, follows and calendar items are not publicly displayed to other users.

4. Authentication and password

Pulse account authentication is provided by Supabase Auth.

When creating or signing in to an account, the password is sent to the authentication service.

Pulse does not directly store your password in plain text in its application database.

Supabase Auth also provides the functions needed to verify email addresses, recover accounts, change email addresses and change passwords.

5. Geolocation

Pulse may offer to use your device’s location to make the map easier to use.

This feature is optional and requires your permission through Android.

In the current version of Pulse:

  • location is requested only after you give permission;
  • coordinates are used locally while using the map;
  • they are not stored in your Pulse account;
  • they are not stored in the Supabase database;
  • Pulse does not create a history of your movements.

You can refuse or withdraw this permission at any time in your device’s Android settings.

When the map is centered on your location, requests needed to load map tiles may allow the map provider to infer the approximate geographic area displayed. The exact GPS coordinates used by Pulse to center the map are not stored in your account or in the Pulse database.

Geographic coordinates associated with venues and events published in Pulse are distinct from a user’s personal location.

6. Android calendar

With your permission, Pulse can access your device calendar so that you can add Pulse events to your Android calendar or remove copies created previously.

This feature is optional.

The app may in particular access calendars available for writing so that you can choose the calendar in which an event is added.

The information needed for this synchronization is mainly processed locally on your device.

You can withdraw the related permissions in Android settings.

7. Data published by organizers

Accounts with organizer access can publish information intended to be visible to Pulse users.

This information may include:

  • the organization’s name;
  • its type or category;
  • its presentation;
  • its address or area;
  • its logo or avatar;
  • its social networks and public links;
  • published events;
  • event titles and descriptions;
  • dates and times;
  • recurrence information;
  • prices;
  • registration links;
  • venues and addresses;
  • images;
  • offered dances.

When an organizer chooses to publish a profile or event, the information concerned may become accessible to other Pulse users.

Organizers should therefore avoid publishing personal information they do not wish to make public.

8. Why do we use this data?

Data processed by Pulse is used in particular to:

  • create and manage your account;
  • authenticate you;
  • provide event discovery features;
  • retain your preferences;
  • personalize certain elements of your experience;
  • manage your favorites, follows and calendar;
  • allow organizers to manage and publish their profiles and events;
  • ensure the service’s operation and security;
  • detect or prevent abuse;
  • receive and process reports;
  • manage account deletion requests;
  • provide user support;
  • comply with applicable legal obligations.

Processing needed to operate an account and requested features is based in particular on providing the service requested by the user.

Processing related to security, abuse prevention and moderation may be based on our legitimate interest in ensuring Pulse’s security and proper operation.

Optional features using permissions on your device, such as geolocation or calendar access, are used only at your request and after obtaining the necessary permissions.

Some processing may also take place where necessary to comply with a legal obligation.

9. Technical providers and recipients

Pulse uses several technical providers needed for certain features to operate.

Supabase

Pulse uses Supabase in particular for:

  • authentication;
  • the PostgreSQL database;
  • storage of certain images;
  • certain server-side functions.

Depending on the features used, Supabase may process your email address, user identifier and data associated with your Pulse account.

OVHcloud

OVHcloud provides the email service used to send certain emails related to Pulse authentication and account management.

Depending on the features used, this includes:

  • email address verification;
  • password recovery or reset;
  • certain other communications related to authentication or account management.

In this context, the recipient’s email address and the technical information needed to deliver the message may be processed by this provider.

Geoapify

Geoapify is used in organizer features for address search and autocomplete.

Requests needed for this feature may include the searched text or address and technical metadata linked to the network connection.

CARTO and OpenStreetMap

Pulse uses map data and services provided in particular by CARTO and OpenStreetMap to display the event map.

Loading map elements involves communications with the relevant servers, which may receive technical metadata such as IP addresses.

Resend

Resend is used to send the confirmation email required for the account deletion process.

In this context, your email address and technical information necessary to send the message may be processed by this provider.

Vercel

Vercel is used to host and make available the pulse-dance.com website.

As part of website operation, Vercel may process technical data needed to receive and handle requests, such as IP address, browser or device type, and technical information associated with requests and operational logs.

Google Maps

When you choose to get directions to an event, Pulse may open an external link to Google Maps.

Once Google Maps is opened, use of that service and the data processed there are governed by the applicable terms and policies of the relevant Google service.

Pulse does not sell users’ personal data.

10. Hosting and international data transfers

The main Supabase project used by Pulse is currently configured in the eu-west-1 region, located in Ireland.

The pulse-dance.com website is hosted and made available through Vercel, and Pulse uses several other technical providers.

The location of the Supabase project in Ireland therefore does not necessarily mean that all Pulse technical processing takes place exclusively within the European Union.

Some providers or subcontractors may use infrastructure located in other countries.

Where international transfers of personal data are necessary, they must be governed by the mechanisms provided for by applicable data protection law.

11. Advertising, analytics and tracking

In the current version of Pulse:

  • no third-party advertising SDK is integrated;
  • no third-party behavioral advertising is integrated;
  • no third-party behavioral analytics SDK is integrated;
  • no third-party marketing tracking tool is integrated.

Pulse does not use user geolocation for advertising purposes.

This section describes how the current version of Pulse operates and may be updated if the technologies used evolve.

12. Reports and moderation

Signed-in users can report certain content, including an event or organizer profile.

To process these reports, Pulse may retain in particular:

  • the technical identifier of the account that made the report;
  • the content or profile concerned;
  • the reason for the report;
  • the optional description provided;
  • certain elements needed to preserve the context of reported content;
  • moderation decisions and actions;
  • information needed to follow up on the report’s processing.

Certain reporting and moderation histories may be kept after account deletion where needed for service security, abuse prevention, follow-up on moderation decisions or the defense of rights.

Rules applicable to published content and its moderation are set out separately in Pulse’s terms and publishing rules.

13. Data retention

Data needed to operate your account is retained for the duration of account use and for as long as it is needed for the purposes described in this policy.

When you request deletion of your account, the main personal data associated with it is deleted as part of the deletion process.

Some information may nevertheless be retained where needed in particular for:

  • service security;
  • abuse prevention;
  • the processing and history of reports;
  • follow-up on moderation decisions;
  • retention of the history of certain past events;
  • compliance with a legal obligation;
  • the establishment, exercise or defense of legal claims.

Certain technical logs, backups or data managed by our providers may also be retained according to their own technical cycles, obligations and configurations.

Some technical providers may generate logs needed for operation, security, error diagnosis and abuse prevention. These logs may include technical information relating to requests, devices, browsers or IP addresses.

Pulse therefore does not claim that account deletion necessarily results in the immediate erasure of every trace in all technical systems or backups.

14. Account deletion

You can request deletion of your Pulse account:

  • directly from the app settings;
  • from the dedicated page on the Pulse website:

https://pulse-dance.com/en/delete-account

To prevent fraudulent deletion of someone else’s account, the process includes password verification and email confirmation.

After confirmation, the authentication account and the main personal data associated with it are deleted.

Some data may nevertheless be retained in the situations described in the “Data retention” section, including certain moderation histories or information relating to past events.

Server-side deletion does not necessarily automatically erase certain information already stored locally on your device.

This may include:

  • certain preferences or data stored locally by the app;
  • copies of events you added to your Android calendar.

These items can be deleted directly from your device or calendar.

15. Security

Pulse implements technical and organizational measures intended to limit unauthorized access to data and protect service operation.

These measures include authentication mechanisms, data access controls and separation between certain operations accessible from the app and sensitive server-side operations.

Network communications between the current version of Pulse and its online services use encrypted connections, including HTTPS/TLS.

Particularly sensitive operations, such as account deletion, also include verification mechanisms intended to limit fraudulent requests.

No computer system can, however, guarantee absolute security or the complete absence of risk.

16. Your rights

Under applicable data protection law, you may, depending on your situation, exercise in particular the following rights:

  • right of access to your personal data;
  • right to rectification;
  • right to erasure;
  • right to restriction of certain processing;
  • right to object where applicable;
  • right to data portability where the legal conditions are met;
  • right to withdraw your consent where processing is based on it.

To exercise your rights or ask a question about your personal data:

contact@pulse-dance.com

We may ask for information to verify your identity where verification is necessary to protect your account and data.

You also have the right to lodge a complaint with the Commission nationale de l’informatique et des libertés (CNIL).

17. Changes to this policy

Pulse may evolve.

This policy may be updated when Pulse features, the technologies used or applicable obligations evolve.

The date shown at the top of this page will be updated when a new version of the policy is published.

Where necessary, users may also be informed of significant changes by an appropriate means.

18. Contact

For any question about this policy or the processing of your personal data:

Pulse Dance

contact@pulse-dance.com