Callback Privacy Policy

Last Updated: August 25, 2026

This Privacy Policy describes how Jonathan Atkinson ("we," "us," or "our") handles information through Callback and related products and services, including Callback Connect, Callback Cloud, Callback OnSite, CompOrganizer services used in connection with Callback, OnDeck, competition websites and publishing services, and related competition-management tools (collectively, the "Callback Services").

Callback is software designed to assist dance competition organizers, officials, staff, competitors, and attendees with the operation and publication of dance competitions.

1. Scope of This Policy

This Privacy Policy applies to information processed through the Callback Services. Different parts of the Callback ecosystem serve different purposes and may process different types of information.

In particular:

2. Competition Organizers and Data Ownership

Competition data submitted to or created through Callback generally belongs to, and is controlled by, the competition organizer using the software.

The competition organizer determines what participant information is collected, how long that information is retained, which information is published, and how the information is otherwise used in connection with its event.

Callback and related services act as tools for processing, storing, displaying, transmitting, and publishing that information on behalf of the competition organizer.

If you have a question about information collected from you by a particular competition, including a request to correct or remove competition records, you should ordinarily contact that competition's organizer first.

3. Information We Process

The information processed through Callback depends upon your role and the services used by a particular competition.

3.1 Officials and Staff

Information about competition officials and staff may include:

First and last name are generally the minimum identifying information maintained for an official. Other contact and profile information may be optional and may not be present for every user.

3.2 Competitors and Other Competition Participants

Competition organizers may provide Callback with information about competitors and other participants, including:

The exact information collected is determined by the competition organizer and may vary from one event to another.

3.3 Technical and Network Information

When a device communicates with a Callback server, the server may automatically receive ordinary network and request information such as an IP address, request time, requested resource, and other information normally transmitted as part of an internet or local-network connection.

Callback Connect does not currently use advertising identifiers, location information, cross-app tracking identifiers, or similar technologies for advertising or profiling.

4. How We Use Information

Information processed through the Callback Services may be used to:

5. Callback Connect

Callback Connect is intended for authorized adult competition officials and staff. It does not allow members of the public to create an account within the application.

Users and officials are provisioned through a competition's Callback administration system. Authentication may use a PIN, QR code, authentication key, session cookie, or similar credential supplied by the competition system.

While an official is using Callback Connect, the application may receive information such as the official's identity and assignment, current heat information, competitor names and bib numbers, previously submitted judging information, and other information necessary to perform the official's duties.

Callback Connect may transmit judging information back to the selected Callback server, including marks, placements, recalls, scores, selections, signatures, official identifiers, and related operational information.

6. Local Storage in Callback Connect

Callback Connect is designed so that its primary application data is maintained in memory while the application is running rather than being intentionally stored in a persistent local database.

The application does not currently use its own persistent AsyncStorage, SecureStore, SQLite database, or similar application-managed storage for competition information.

However, the device operating system or underlying networking and image libraries may maintain temporary caches, cookies, or similar technical data outside of Callback's direct application storage. The duration of such storage may depend upon the device and operating system.

7. Camera Access and QR Codes

Callback Connect may request access to a device's camera for the purpose of scanning QR codes. This provides a convenient and secure method of logging an official into a competition system and pairing that official with a particular device.

Callback Connect does not use the camera to take or store photographs or video for this purpose. Camera images used during QR scanning are not intentionally saved or uploaded.

The application reads the information encoded in the QR code and uses that information to authenticate the official with the selected Callback server.

8. Location, Advertising, Analytics, and Tracking

Callback Connect does not currently collect precise or approximate device location.

Callback Connect does not contain advertising and does not currently use advertising SDKs, advertising identifiers, behavioral advertising, cross-app tracking, or marketing profiling.

Callback Connect does not currently include third-party analytics platforms such as Google Analytics, Firebase Analytics, or similar services for monitoring user behavior.

The application also does not currently include third-party crash-reporting platforms such as Firebase Crashlytics, Sentry, or Bugsnag.

If these practices materially change in a future version, this Privacy Policy will be updated as appropriate.

9. Competition Information That May Be Published

Some information processed by Callback is specifically intended to be visible to competitors, officials, staff, spectators, or the public as part of operating and reporting a competition.

Depending upon the organizer's choices, published or displayed information may include:

This information may be shown on competition displays, including on-deck or ballroom displays, or may be made available through competition websites, published heat lists and schedules, OnDeck, or other Callback publishing services.

The competition organizer controls what information it elects to publish.

10. Children and Minors

Callback Connect is intended for use by authorized adult competition officials and staff and is not intended for use by children.

However, dance competitions may include competitors who are minors. As a result, Callback may process competition records concerning minors when that information is supplied by a competition organizer.

Such information may include a minor competitor's name, bib number, competition entries, schedule, heat assignments, partner or team information, placements, scores, and results. Some of this information may be displayed or published as part of the normal operation of the competition.

Competition organizers are responsible for determining what information they collect concerning minors and for obtaining any permissions or consents required by applicable law or by their own policies.

Services intended for competitors or the general public, such as published heat lists, competition websites, results, or OnDeck, may be accessed by minors. These services are primarily intended to provide competition information and do not require a minor to operate Callback Connect.

11. Sharing and Disclosure of Information

Callback does not sell personal information.

Information may be disclosed or made available in the following circumstances:

12. CompOrganizer Services

Competition organizers may choose to use CompOrganizer services in connection with Callback. These services may process or store competition information on systems operated by Jonathan Atkinson.

Examples include:

Information processed through these services remains associated with the competition for which it was supplied.

13. Data Transmission and Security

We take reasonable technical and organizational measures to protect information processed through Callback against unauthorized access, loss, misuse, alteration, or disclosure.

Callback Cloud and Callback-hosted internet services generally use HTTPS encryption for information transmitted over the public internet.

Callback also supports local competition installations, including Callback OnSite. A local installation may communicate with devices over a private event network using HTTP rather than HTTPS. In such cases, network traffic is not encrypted by HTTPS and the security of the connection also depends upon the security and physical control of the local competition network.

Competition organizers may also configure Callback Connect to communicate with other compatible servers or custom server addresses. Whether those connections use encryption depends upon the server and configuration selected by the organizer.

No method of electronic storage or transmission can be guaranteed to be completely secure.

14. Data Retention

There is no single retention period that applies to all competition information processed through Callback.

Competition organizers control their competition data and may retain their records for as long as they consider appropriate or as required by their own policies or applicable law.

Information stored through CompOrganizer or other Callback-hosted services may remain available for backup, publishing, historical results, schedules, or other organizer-selected purposes for as long as the organizer chooses to maintain those services or records.

Operational information that is no longer reasonably required may be deleted or replaced as part of the normal operation and maintenance of the Callback Services.

15. Access, Correction, and Deletion Requests

If your personal information was supplied to Callback by a competition organizer, you should generally contact that organizer to request access, correction, or deletion. The organizer is best positioned to determine what information it controls and whether particular competition records must be retained.

If information is stored directly through a Callback or CompOrganizer service, or if you are unsure whom to contact, you may contact us at info@callback.dance.

We may need sufficient information to identify the relevant competition and record before we can assist with a request.

Some information may need to be retained where reasonably necessary for legitimate competition records, security, dispute resolution, legal compliance, or other lawful purposes.

16. Accounts

Callback Connect does not currently permit users to create an account within the application. Official and staff access is established by the competition organizer through Callback's administrative systems.

Because Callback Connect does not provide in-app account creation, there is no separate Callback Connect consumer account that must be deleted from within the application.

17. Third-Party Websites and Services

Callback may display or link to information hosted by a competition organizer or another service. Competition organizers may also publish Callback-generated information through their own websites or other platforms.

This Privacy Policy does not govern independent websites, applications, or services operated by third parties. Their own privacy policies and practices apply to information they independently collect or control.

18. Changes to This Privacy Policy

We may update this Privacy Policy as Callback and its related services evolve, or when changes are necessary to reflect legal, technical, or operational requirements.

When this policy is materially revised, the "Last Updated" date at the top of this page will be changed.

19. Contact

If you have questions about this Privacy Policy or the privacy practices of Callback, you may contact:

Jonathan Atkinson
Callback
Email: info@callback.dance