Privacy.

Who operates RAKK

RAKK is built by Verity Engine and operated by Doug Hamaker. For privacy questions or requests, contact verityengine@gmail.com.

Information you provide

We use your email address, profile name, account identifier and athlete or coach relationship to provide your account. Sign-in uses email verification or a supported sign-in provider when available; RAKK does not receive your provider password.

The app stores the information you choose to enter: training plans, assignments, sets, weights, reps, cardio, session dates, notes, targets and Daily entries such as sleep, body weight, heart rate and nutrition totals. Where meal logging is available, it also stores the meal details you enter. Coaches provide programs, targets, invitations and coaching notes.

We also keep consent choices, read markers, synchronization and revision records needed to operate the app and recover edits. Security controls may process account identifiers and IP addresses, for example to limit repeated invite attempts.

How we use it

We use this information to provide sign-in, save and synchronize your work, display training history and progress, support coaching, process your chosen imports and respond to support requests. RAKK does not sell personal information or use training and health data for advertising.

What your coach can see

Your current coach can access your assigned training, recorded sessions, cardio, Daily values and shared Notes. Other athletes do not receive access to your records. Individual meal details have a separate sharing choice; your saved Daily nutrition totals remain visible to your coach.

Your AI chat is not a coaching Notes thread and is not shown to your coach. Private Apple Health import candidates are also excluded from coach access. Information you accept into Daily or explicitly add to a workout can become coach-visible.

Optional Apple Health access

When you enable Apple Health import and grant access, RAKK can read steps, resting heart rate, heart-rate variability, sleep, body weight, active energy, workouts and workout heart-rate samples. It does not write to Apple Health.

Read Daily values are stored in your RAKK account as private import candidates. Values you accept into Daily, including source information, can be seen by your coach. Read workouts remain on the iPhone until you explicitly add them to training. No workout is automatically logged.

You can stop new imports in RAKK and change permissions in Apple Health or iPhone Settings. Turning access off does not delete previously stored candidates, accepted Daily entries, workouts or pending local imports. Clearing a Daily field does not remove its private import candidate.

Optional AI features

AI chat requires a separate choice to enable it. With your permission, your question and relevant program, training history, heart-rate settings and Daily context are sent through RAKK’s service to Anthropic’s Claude API. Your coaching Notes thread, individual meal details and photos are excluded from this chat context.

Smart import has a separate permission step. If you choose it, the selected program source text is sent to Anthropic to produce a proposal for your review. Ordinary local import readers and Quick log do not require AI.

You can turn AI chat off in its settings. Chat history is kept on your device; content already sent to Anthropic is subject to its API data handling. See Anthropic’s Privacy Center. AI suggestions do not automatically change your program or confirm proposed sets.

Garmin Connect — planned integration

Garmin Connect integration is planned and is not currently available in RAKK. RAKK does not currently receive data through the Garmin Connect API. The following describes our intended approach, subject to Garmin approval and implementation.

Connecting Garmin would be optional. Before connection, we would explain the activity and health information requested and how it would be used for your training history, progress and Daily context. We would also explain which imported records could be shared with your connected coach. We would use Garmin’s authorization process; RAKK would not ask for your Garmin password.

Connecting Garmin would not by itself enable AI use. A separate, optional consent would be required before sending relevant Garmin-derived information with your question to Anthropic’s Claude API for an Ask RAKK answer. The proposed use is to generate answers for you, not to train AI models. We would limit the information sent to what is relevant to the question and keep Garmin access credentials out of AI requests. Declining AI use would not prevent ordinary Garmin syncing.

Before launch, we would provide controls to withdraw Garmin AI consent, stop future syncing and request deletion of imported data. Disconnecting and deleting are different actions; the final notice would explain what happens to previously saved records and provider copies. We would publish the actual data categories, retention details and controls before enabling the integration. Any future transfer of plans or workouts from RAKK to Garmin would have its own notice and authorization. See Garmin’s privacy policy for Garmin’s own practices.

Storage and service providers

Supabase provides account authentication and database services. Cloudflare serves the website and web application. Anthropic processes selected content when you use the optional AI features described above. Apple or Google may process sign-in when you choose a supported provider. Email services process sign-in and support messages.

RAKK uses HTTPS for data sent to its services. The app keeps account-specific local copies and pending entries to support offline use. Signing out can leave unsent work on the device so it is not lost; use care on shared devices.

Our providers may process information in countries other than where you live, under their applicable service arrangements and data-protection requirements.

Retention and deletion

Account data and saved revision history are retained to provide the service while your account exists. You can request deletion in Account settings, with fresh identity verification. If you cannot access the account, contact us from the account’s email address.

Deleting an athlete account removes that athlete’s account records and logs. A coach may retain their own authored programs and notes under the app’s retention rules. Deleting a coach account does not remove athletes’ own records or the training and notes already provided to them. Local copies on another device may not update until it reconnects.

Service-provider backups and security or legally required records may remain for their applicable retention periods. Turning off a connection or AI feature alone does not delete data already saved or previously sent to a provider.

Your choices and requests

You can edit your entries, manage optional Health and AI permissions, and request account deletion. You may also contact us to ask for access, correction, a copy of your information or deletion, and to exercise privacy rights available where you live. We may verify your identity before responding.

The private beta is not directed at children. Contact us if you believe a child has provided personal information without appropriate authorization.

This website

The marketing website does not use advertising trackers or an analytics script. Hosting services still process technical request data needed to deliver and protect the site. Product screenshots use fictional sample data, and the Ask RAKK demonstration is scripted; it does not send a question to AI.

Changes

We will update this page and its date when the policy changes. Where a change requires a new permission or notice, we will provide it before relying on that change.