Privacy policy

When you connect your RunSignup account, RaceSync stores:

• Your RunSignup user ID, and the email address and display name on that account.
• Your race registrations: race and event name, start time and time zone, the event address, the race's web page, your bib number, and the distance.

When you connect a calendar, RaceSync additionally stores:

• An access token and refresh token for that calendar provider. Both are encrypted before they are written down, under a key the database does not hold.
• The identifier and name of the calendar RaceSync creates, and the identifiers of the events it creates on it, so it can update them later instead of making duplicates.

RaceSync does not ask for, and cannot see, your payment details, your location, your contacts, or the contents of any calendar it did not create.

• RunSignup — rsu_api_read. Read-only. RaceSync cannot change anything in your RunSignup account, including registering or withdrawing you from a race.
• Google Calendar — calendar.app.created. This grants access only to calendars RaceSync itself creates. Your existing calendars and their events are not visible to it.
• Outlook / Microsoft — Calendars.ReadWrite. Microsoft offers no equivalent app-created-only permission, so the access you grant is broader than what RaceSync uses. It writes only to the calendar it created, and never reads or alters your other calendars, but we would rather state the difference than let the narrower description stand for both.

Your data is not sold, rented, or shared for advertising. It is sent to exactly the services needed to do the job:

• RunSignup, to read your registrations.
• Google or Microsoft, to create and update your race calendar.
• DigitalOcean, which hosts the servers and the database.

RaceSync's use and transfer of information received from Google APIs to any other app will adhere to the Google API Services User Data Policy, including the Limited Use requirements.

Your registrations and tokens are kept while your account is connected, because that is what lets the calendar stay current. Disconnecting a calendar deletes the tokens for it. Signing out ends that session on the server, so the signed-out device cannot use it again.

Email support@raceapi.com from the address on your RunSignup account and ask. Everything tied to your account — profile, registrations, calendar links, and tokens — is removed together; none of it outlives the account record. The full process, and what stays on your own calendar afterwards, is on the account deletion page.

Deleting your data does not remove events already written to your own calendar. Those are yours, on your provider, and you can delete the calendar RaceSync created at any time from Google Calendar or Outlook directly.

RaceSync is not directed at children under 13 and does not knowingly collect their data.

If this policy changes, the date at the top changes with it.

support@raceapi.com