Rocket Surgeon, Inc.

Span / Privacy

Span privacy policy

Last updated November 6, 2026

Rocket Surgeon, Inc. operates Span. This policy explains how we handle information when you use Span, visit our company website, or contact us. Span is currently in development.

Information we collect

  • Account and profile information. When you accept an invitation, sign in, or edit your profile, we receive account identifiers, your sign-in email address, authentication and recovery information, your display name, the pillars you choose, and any profile image or biography you provide. Older profiles may still contain previously supplied age, gender, height, weight, or image-description information even though those fields are no longer offered for editing.
  • Information you put in Span. This includes practices, steps, routines, schedules, activity records, notes, sharing choices, invitations, uploaded photos and videos, and the prompts and reference images you choose for AI features. What you enter can reveal information about your health, activities, appearance, or other people.
  • Technical information. Our hosting, authentication, media, and update services receive information as your device connects, such as IP addresses, request details, device or app version information, session identifiers, and errors. Until October 27, 2026, our backend also exported exception events to PostHog for troubleshooting. These could include account identifiers and failed-request details, not just information sent when your device connects. We turned that export off and no longer send new exception events. We also keep operational records of generation attempts, usage, access changes, recovery, and deletion requests.
  • Correspondence. If you email us, we receive your email address, message, and any attachments. Please do not send passwords, sign-in codes, or medical records.
  • Information stored on your device. The app keeps your sign-in session and pending invitation details in your device's secure storage. It may also keep practice records that have not synced yet, temporary copies of photos and videos you select, and cached images on your device, along with an identifier for your app installation that it uses for app updates. The embedded YouTube player can store information on your device under Google's policies. Span does not use advertising or analytics cookies.

We collect information you submit, information created by your use of Span, authentication events from our sign-in provider, and technical information from the services that deliver the app and website. Access to your camera, microphone, or photo library uses your device permissions. Selecting media for upload sends that media to our storage or video provider. Photos and videos can contain embedded details, such as where they were taken. Span does not separately remove those details, so they may remain in what we store and in what people you share with can access.

How we use information

We use information to create and secure accounts, manage invitations and recovery, save and display your content, organize schedules and activity records, deliver media, and apply your sharing choices. AI features send prompts, relevant library content, and selected reference images to OpenAI. We keep generation and usage records to operate those features, track costs, and limit abuse.

Creating a Step without an explicit representative image or usable guidance can automatically start image generation without a separate generation request. This can send the Step's content and selected Character and Background reference photos to OpenAI. AI processing is not limited to features where you press a separate generate button.

We also use information to deliver app updates, diagnose failures, protect the service, answer support and privacy requests, and meet legal obligations. We do not sell your personal information or use it for targeted advertising.

Who receives information

We use service providers, including their software development kits or SDKs, to operate Span. The information a provider receives depends on the feature you use:

  • Clerk handles sign-in, account email, sessions, invitations, and recovery.
  • Convex hosts application data, backend functions, generation conversations and usage records, and some stored files.
  • Cloudflare delivers web traffic and stores and serves uploaded or generated images through R2.
  • Mux receives uploaded video and serves video playback. When a video plays, it can receive your IP address, device or app details, approximate location based on your IP address, and which video was viewed.
  • OpenAI receives AI requests. Practice generation sends your prompt and relevant readable step-library content. Image generation sends image instructions and any selected source images, Character, or Background references.
  • Expo delivers app updates and receives update-request technical information, including an identifier for your app installation. Expo's privacy policy also allows it to use information it collects, which can include this information, for purposes such as analytics, research, and improving its services.
  • PostHog received exported backend exception events for troubleshooting and operator alerts until October 27, 2026, when we turned that export off. It receives no new exception events from Span. Events it already received remain stored until deleted. These can include an authenticated account identifier, error messages, stack traces, and function, deployment, and request details. Error details may include information present in a failed request. An observed exception event also contained IP and country enrichment. We have not established whose IP address or country those fields represented. Provider-added event properties can vary.
  • GitHub runs authorized account-recovery and maintenance workflows. Recovery workflows receive account identifiers and replacement email addresses. Maintenance workflows can process application data in maintenance snapshots and retain operational evidence. These workflows are separate from normal use of the app.
  • Proton Mail handles messages sent to our company email address.
  • OpenAI Sites and its hosting infrastructure host the company website and process website request information. Website hosting is separate from Span's AI generation.

These providers handle this information to provide their services to us. Most of the data-processing agreements or terms that apply to them limit how they can use it and commit them to security measures to protect it. Some allow other uses, such as using aggregated or de-identified data to improve their products. These commitments vary by provider. The YouTube features described below work differently.

Span uses YouTube API Services to show YouTube thumbnails and play YouTube videos. Thumbnails and the embedded player can send your IP address and request or playback information to Google, including when a thumbnail is displayed before you play a video. Google handles that information under the Google Privacy Policy. By watching YouTube videos in Span, you agree to the YouTube Terms of Service. Opening an external link also connects you to that service under its own terms.

Other Span users can see content you make public or share with them, together with the author information displayed for that content. Once you complete registration, other signed-in Span users can find your display name and profile image through search and can view your profile, including any biography and the pillars you choose, even if you have not shared anything. If another user borrows a Step you share, its released name and description can be included in their AI practice-generation request to OpenAI. Think carefully before including sensitive information or another person's image. Authorized company personnel may access information when needed for support, security, or operating the service. We may also disclose information when required by law or necessary to protect people or the service.

Retention and deletion

We retain account information, content, activity records, and operational records while needed to provide Span, handle requests, maintain security, or meet legal obligations. Signing out, uninstalling the app, removing device permission, or deleting a sign-in account does not automatically erase all application data or provider copies.

The current account-retirement path blocks account access after our sign-in provider notifies us that the sign-in account was deleted. It does not carry out application-data cleanup or provider deletion. Account and profile records remain stored. The development version does not yet have a completed account-retirement cleanup path.

To request account or personal-data deletion, email contact@rocketsurgeon.co. Emailing us is a request, not a completed deletion or an automatic change to your account access. We may need to verify the request and explain the current limits. We do not promise a deletion completion date. A seven-day safety hold after account recovery is not a promise that deletion happens when the hold ends.

PostHog no longer receives new exception events, but events it already received remain stored. PostHog may delete events after its event-retention period ends, but not necessarily as soon as they expire, so older events can remain stored. PostHog also keeps issue names and descriptions separately from those events. Deleting your sign-in account does not automatically remove this information. Removing matching error information can require a support-assisted event deletion and separate changes to issue names and descriptions.

Shared content may have dependencies in another person's practices or records. Future cleanup may need to preserve some content without your author identity rather than remove it. Security and deletion-audit records, backups, provider logs, and data held by providers without per-user deletion support have separate retention limits. Removing an item in the app is not proof that those copies have been erased. Their retention and deletion limits depend on the provider and the record; there is no single guaranteed purge period for all copies. We will explain the applicable limits in response to your request and will not describe retained information as deleted.

Your choices

You can edit available profile fields, choose what to share, decline optional uploads, and change camera, microphone, and photo-library permissions in your device settings. AI features include the automatic generation described above. Source-image and reusable-reference generation use the consent recorded for those features.

You can remove a reusable Character or Background reference from your library and clear your Default Character in profile settings. Removing a reference prevents it from being resolved for new generation requests. Clearing your default changes future default selection; it does not change references already saved on Steps or Practices. These controls do not guarantee cancellation of work already in progress and do not erase stored reference versions, source images, completed outputs, or provider copies.

To request withdrawal of consent for future processing, or ask about access, correction, a copy of your information, or deletion, contact us at the address below. Emailing us does not itself stop processing. Withdrawing consent does not undo processing already performed. Some features cannot work without the information they need.

Age

Span is for people 16 and older. We do not knowingly collect personal information from anyone under 16. If you believe someone under 16 has given us information, contact us at contact@rocketsurgeon.co. We will review it and handle the information as described in Retention and deletion.

Contact and changes

Send privacy questions and requests to Rocket Surgeon, Inc. at contact@rocketsurgeon.co. For help using Span, visit Span support. We update this page when our practices change and revise the date above.