Privacy

Privacy Policy

How we handle information when you visit runup.app, sign up a club, or use the product with your flying club.

Draft for legal review. This page was written by the engineering team as a working placeholder. It is not final counsel-approved language. Contact us if you need a signed copy or have questions before relying on it.

Last updated: August 12, 2026 (draft)

Who we are

RunUp is a multi-tenant flight club operations product. In this policy, “RunUp,” “we,” and “us” mean the operator of the RunUp service (JR Aviation). “You” means a visitor to our public site, a club officer requesting a trial, or a member or admin using a club workspace.

Privacy requests: [email protected]

What we collect

Account and identity

Name, email, and authentication data through our identity provider (Clerk). We do not store your password. Social sign-in (for example Google, Apple, or Facebook) is handled by Clerk and the provider you choose.

Club and operations data

Membership, aircraft, reservations, dispatch/closeout records, documents, billing and ledger activity, maintenance items, and similar club operations data that your club enters into RunUp. Each club’s data is scoped to that club.

Payments

Platform subscription billing and member payments run through Stripe (including Stripe Connect for clubs). Card and bank details are processed by Stripe; RunUp stores payment references and status, not full card numbers.

Communications

Email and (where enabled) SMS delivery for operational notices and member messaging, including consent/opt-out records where required. Each club's SMS program has its own public privacy and terms pages under that club's workspace URL (for example /c/your-club/sms-privacy).

Technical and usage data

Server logs, device/browser metadata, and error diagnostics. When configured, server-side error reporting may use Sentry. Optional marketing funnel events on the public site run only if you allow Analytics in cookie preferences (off by default; no third-party analytics provider is loaded today).

How we use information

  • Provide and secure the RunUp service for your club
  • Authenticate users and enforce roles and permissions
  • Process trials, subscriptions, and member payments
  • Send operational and account-related communications
  • Improve reliability (including diagnosing errors)
  • Measure public-site funnel performance only when Analytics is allowed

Who we share with

We use vendors to operate the product. Primary processors include Clerk (authentication), Stripe (payments), email/SMS providers for delivery, hosting providers for the application and database, and Sentry for server-side error diagnostics when enabled. We do not sell personal information. We do not run third-party advertising pixels on the marketing site today.

Text messaging

When a flying club enables SMS, members opt in from Communication preferences after signing in. The club is the sender. RunUp and Twilio process mobile numbers only to deliver those messages and honor STOP/HELP.

Mobile information will not be shared with third parties or affiliates for marketing or promotional purposes.

Message frequency varies; typically a few messages per month when aircraft or field status changes. Message and data rates may apply. Reply STOP to opt out. Reply HELP for help.

Club-specific SMS privacy and terms are published without a login at /c/{club-slug}/sms-privacy and /c/{club-slug}/sms-terms. Those pages are the policies submitted for carrier registration.

Cookies and similar technologies

Essential cookies and local storage keep the product working. Optional Analytics is controlled from Cookie preferences in the site footer (preference cookie: fo_cookie_consent). Authenticated club cookies are essential for product features and are not gated by a consent wall inside /c/….

NameCategoryWherePurpose
Clerk session cookies (__session, __client*, __clerk_*)EssentialSign-in and authenticated appAuthenticate the user and keep the session secure.
fo_view_as_{clubSlug}EssentialAuthenticated club app (/c/{slug})Remember an admin’s temporary VIEWING AS role for that club.
mx-dash-visit-{clubSlug}EssentialAuthenticated maintenance dashboardRemember last visit time for “since last visit” activity.
fo_cookie_consentEssentialMarketing siteStore your cookie / analytics preference.
Stripe.js / Elements cookies (when paying)EssentialMember payment flowsProcess card or bank payments securely via Stripe.
runup-signup-draft (localStorage)Local storageClub signup wizardResume an in-progress signup draft in this browser.
fo.aircraftBrowseView (localStorage)Local storageAuthenticated fleet browseRemember list vs card view preference.

Retention

We retain account and club operations data for as long as the club uses RunUp and as needed for legitimate business, security, and legal obligations afterward. Clubs may export data; inactive or closed clubs may be deleted or anonymized on a schedule we document with the club. Marketing funnel events (if enabled) are kept only as long as needed for product analytics.

Your privacy rights (US)

Depending on where you live, you may have rights to request access, correction, deletion, or a copy of personal information, and to opt out of certain sharing for targeted advertising. RunUp does not sell personal information and does not currently share it for cross-context behavioral advertising. To exercise a request, email [email protected]. We will verify your request as required by applicable law.

Club members should also contact their club administrators for club-managed roster data; we process that data on behalf of the club.

Children

RunUp is directed at flying clubs and adult operators. We do not knowingly collect personal information from children under 13.

Changes

We may update this policy. We will change the “Last updated” date above and, for material changes, provide additional notice where appropriate. Continued use of the public site or product after an update means you acknowledge the revised policy.

Related

See also our Terms of Service and Security overview.