Arc Privacy Notice

Our approach

We believe information you provide to Arc should serve your coaching—not become the product.

Arc does not sell your personal information.

Arc's Beta release does not include third-party advertising, advertising pixels, or behavioral-advertising integrations.

We also design Arc so that important uses of coaching context have defined purposes and boundaries, with meaningful visibility and control for the athlete where those controls are supported.

1. Information Arc Handles

The information Arc handles depends on how you use the product.

Account and profile information

We handle information needed to create, authenticate, maintain, and support your Arc account.

This can include your:

• email address;
• Arc account identifiers;
• authentication and session information;
• profile information you choose to provide.

Arc's Beta release uses an external identity provider to support account authentication.

Goals, plans, and training information

Arc handles information about the training you choose to manage through the product.

This can include:

• running goals and races;
• training plans;
• planned workouts;
• completed activities;
• distance, duration, pace, splits, and related activity information;
• plan changes and training decisions;
• training history maintained within Arc.

Activities you log or import

You can enter training directly into Arc or upload supported activity files.

Arc's Beta release supports Garmin-compatible CSV and FIT file imports. These are file-based imports: uploading a file that originated from Garmin does not create an automatic Garmin connection or cause Arc to continuously receive information from Garmin.

Readiness and context you provide

You can provide information that you believe is relevant to a coaching decision.

Depending on the feature, this may include information about:

• readiness;
• sleep;
• soreness or pain;
• stress;
• schedule and availability;
• travel;
• how training felt;
• other circumstances affecting your training.

Some of this information can be sensitive because it relates to how you are feeling physically or mentally.

You choose what context to provide.

Arc uses this information for fitness and running coaching. Arc does not use it to diagnose or treat a medical condition.

Coaching conversations and reviews

When you use Coach, Activity Review, or other coaching and review features, Arc may handle:

• questions and messages you submit;
• relevant goal, plan, activity, readiness, and training context;
• coaching responses;
• generated reviews;
• your confirmations, disagreements, or follow-up information;
• recent coaching context relevant to the interaction.

Personalization information

Arc distinguishes retained personalization from ordinary account and training records.

Eligible retained personalization can include coaching preferences, availability constraints, temporary context, or confirmed information about how you prefer Arc to coach you.

When retained personalization exists, Arc's Beta experience supports controls that can allow you to:

• see eligible retained context;
• confirm or reject eligible proposed context;
• reconfirm information;
• suppress its future use;
• retire information that is no longer relevant;
• remove eligible retained personalization;
• export information specifically associated with retained personalization.

The personalization export is not a complete export of all information in your Arc account.

For the initial Beta release, retained personalization is not enabled to automatically influence planning decisions. Arc may still maintain personalization records and make the associated visibility and control tools available to you.

Feedback and communications

If you send us feedback or contact us, we may handle the information contained in your message and information needed to respond.

This can include:

• product feedback;
• support questions;
• privacy requests;
• related correspondence.

Technical and operational information

Arc and the services used to operate it create limited technical and operational records needed to authenticate users, operate the service, diagnose failures, maintain reliability, and support product governance.

Arc is designed to limit unnecessary content in operational telemetry and certain governance records.

The exact information generated by infrastructure providers may depend on the services used to host and operate Arc.

2. How Arc Uses Information

We use information for defined purposes related to operating and providing Arc.

To provide your Arc account and product experience

We use information to authenticate your account and provide Arc features such as Today, Plan, Coach, Activity Review, and Trajectory.

To provide coaching in context

Relevant goals, plans, recent training, completed activities, and context you provide may be assembled for a supported coaching or review decision.

Not every piece of information is used in every interaction.

To plan and review training

Arc uses training information to create and display plans, review completed training, evaluate supported changes, and maintain your current training state.

Some meaningful plan changes are designed to enter a review or confirmation process rather than being applied silently.

To maintain useful continuity

Arc maintains account, training, and coaching information so that supported later interactions can reflect relevant information already maintained within the product.

This does not mean that Arc continuously monitors you or treats every interaction as permanent personalization.

To provide user-controlled personalization

Arc may maintain eligible retained personalization and provide visibility, correction, suppression, retirement, removal, and export controls around that information.

For the initial Beta release, retained personalization is not enabled to actively influence planning.

To operate, troubleshoot, and improve Arc

We may use appropriate product records, content-minimized operational information, and voluntary feedback to:

• diagnose problems;
• maintain reliability;
• evaluate product behavior;
• investigate defects;
• improve the Arc experience.

Ordinary use of Arc is not treated by Run With Arc LLC as consent to use your information for unrelated advertising, data brokerage, or generalized research purposes.

To respond to you and protect the service

We may use information as reasonably necessary to:

• respond to support or privacy requests;
• protect accounts and the service from misuse;
• investigate reliability or security problems;
• comply with applicable legal obligations;
• protect the rights and safety of users, Run With Arc LLC, or others where appropriate.

3. AI-Enabled Features

Arc uses artificial intelligence in supported Beta workflows, including portions of coaching, planning, daily recommendations, activity interpretation, reviews, weekly coaching workflows, and observation interpretation.

Not every Arc action or recommendation is generated by AI.

Arc also uses structured software rules, validation, safety checks, user-review flows, and deterministic fallback behavior.

When an AI-enabled feature is invoked, Arc may provide its AI service provider with the information assembled for that specific workflow.

Depending on the feature, that information may include relevant portions of:

• your question or message;
• goals;
• current training plan;
• recent training;
• activity information;
• readiness or pain-related context you provided;
• coaching history;
• eligible retained context.

Different workflows intentionally use different amounts of context.

Arc also uses safeguards designed to limit unnecessary provider context in supported workflows. For example, some provider-context processes remove credentials, session information, and raw GPS or route-coordinate information.

Arc's intended Beta AI provider is OpenAI.

4. Weather and Location

Arc can provide optional local weather context.

If you choose to allow location access for this feature, your browser may send approximate location coordinates to Arc's weather provider so that local weather can be returned.

Arc does not intentionally include your Arc account identifier, training history, or coaching conversations in that weather request.

Location access for this feature is optional.

5. Information From Other Services

Some information you choose to provide to Arc may have originated with another service.

For example, you may upload a Garmin-compatible CSV or FIT file.

In that situation:

• you choose whether to obtain and upload the file;
• Arc receives the information contained in the file;
• Arc processes the supported file as part of your activity record;
• this does not create an automatic or ongoing Garmin connection.

The initial Beta release does not include connected Garmin synchronization, Terra connectivity, or RunSignup race discovery.

6. Service Providers

Arc relies on service providers for functions needed to operate the product.

For the intended Beta release, these functions include categories such as:

• account authentication;
• hosting and infrastructure;
• AI-enabled inference;
• optional weather information.

Arc provides a service provider only with information needed for the function it performs.

The intended Beta configuration uses Auth0 for account authentication, OpenAI for supported AI-enabled workflows, and Open-Meteo for optional weather information.

Hosting and infrastructure providers may also process or store Arc information as needed to operate the service.

We do not treat a provider's availability in development code as evidence that the provider is active in the released product.

7. Sale, Advertising, and Data Monetization

Arc does not sell your personal information.

The Arc Beta release does not include:

• third-party advertising;
• advertising pixels;
• retargeting integrations;
• advertising-audience creation;
• data-broker integrations;
• external behavioral-advertising analytics.

Run With Arc LLC does not treat user information as an advertising asset.

Introducing advertising, data-sale or licensing practices, cross-context behavioral tracking, or a materially different secondary use of Arc information would require a deliberate product and privacy review rather than being treated as an ordinary extension of the coaching service.

8. Cookies and Session Technology

The authenticated Arc application uses session technology necessary to keep you signed in and associate requests with the correct Arc account.

Arc's Beta authentication architecture is designed around Auth0 authentication and an Arc-managed authenticated session.

The public website at “runwitharc.com” does not require an Arc user session to display its normal public content.

Arc's initial public site is not designed around advertising or behavioral-tracking cookies.

9. How Long Arc Keeps Information

Different information supports different product and operational purposes, so Arc does not apply one universal retention period to every category of data.

We generally retain information for as long as reasonably necessary to:

• provide Arc and maintain your training history and account;
• preserve appropriate coaching continuity;
• support the purposes described in this Notice;
• respond to requests;
• maintain reliability and service integrity;
• satisfy appropriate legal or operational requirements.

Some information has narrower technical retention rules, while other product records remain associated with your account until they are removed or the account lifecycle requires their deletion.

When information is no longer needed, Arc may delete it, remove its substantive content, or retain only limited records needed to document an action such as a deletion or governance event.

Residual copies may remain temporarily in backups, logs, or other operational systems until they expire, are overwritten, or are otherwise removed through the applicable operational process.

We do not promise a single deletion or retention timeline when different systems have different lifecycle requirements.

10. Your Visibility and Controls

Transparency and user control are important parts of Arc's product design.

Depending on the information and feature involved, Beta controls include:

Training decisions

Supported meaningful plan changes can require your review or confirmation before being applied.

Retained personalization

When eligible retained personalization exists, you can use supported controls to:

• view it;
• confirm or reject proposals;
• reconfirm information;
• suppress future use;
• retire information;
• remove eligible retained personalization;
• export your retained-personalization information.

Feedback

Supported feedback records can be removed through the product where that control is available.

Complete account export

Arc does not currently provide a complete self-service export of all account data.

The available personalization export is limited to retained-personalization information.

11. Account and Data Deletion

Arc contains a governed account-deletion system, but the self-service account-deletion workflow is not enabled for the initial Beta release.

The underlying deletion design includes controls intended to:

• restrict account access when a valid deletion process begins;
• remove Arc-owned account information through a verified deletion workflow;
• handle external identity deletion;
• avoid reporting deletion as complete when required steps have failed;
• preserve only limited evidence where needed to document deletion or protect backup-recovery integrity.

Because the self-service workflow is not active in the initial Beta, Arc does not currently promise an in-product account-deletion completion timeline.

For privacy or deletion questions, contact:

privacy@runwitharc.com

12. Security

Arc uses technical and product safeguards intended to limit inappropriate access and reduce unnecessary exposure of information.

Repository-supported safeguards include:

• authenticated sessions;
• account and user ownership checks;
• session expiry and revocation;
• request-origin and CSRF protections for supported authenticated actions;
• bounded AI-provider context;
• structured validation of supported AI outputs;
• deterministic fallback behavior;
• content minimization in certain telemetry and governance records;
• controlled personalization and deletion workflows.

No online service can eliminate all risk.

We do not make unsupported claims that Arc holds security certifications or complies with a particular security or healthcare standard merely because technical safeguards exist.

Additional infrastructure controls depend on Arc's production hosting and service-provider environment.

13. Fitness Coaching, Not Medical Care

Arc is a running and fitness coaching product.

Arc is not a healthcare provider and does not diagnose, treat, or provide medical clearance for injuries or medical conditions.

Information you provide about pain, soreness, readiness, or similar concerns may be considered within supported fitness-coaching workflows, but Arc should not be relied upon to determine whether you have an injury or medical condition.

Arc coaching is not a substitute for professional medical advice, diagnosis, or treatment.

If you have a medical concern, seek appropriate advice from a qualified healthcare professional.

14. Age and Geographic Availability

Arc's initial Beta is intended for:

• people 18 years of age or older;
• users in the United States.

Access during the controlled Beta is managed operationally through Arc's invitation and account-provisioning process.

Arc is not currently intended for children.

15. Privacy Questions and Requests

If you have a question about how Arc handles information or want to make a privacy-related request, contact:

privacy@runwitharc.com

The specific controls and processes available may depend on the nature of your request, the information involved, and applicable law.

16. Changes to This Notice

Arc will continue to evolve, and this Privacy Notice may change as the product, our practices, or applicable requirements change.

When we update this Notice, we will update the date at the top of the page.

If a change materially affects how we handle personal information, we will determine what additional notice or choice is appropriate before applying the new practice.

17. Contact