Privacy policy

Rainge is made by Michael Nguyen, at anicca.ai. In this policy, “we” and “us” mean Michael. You can reach him about anything here at Michael@anicca.ai.

Rainge has no accounts, no ads, and no analytics or advertising code from anyone else. Your buckets, swings, measurements, reports, swing thoughts, notes and golfer profile are stored on your phone, and the analysis runs there, offline.

Information leaves your phone only when you do one of these:

• send feedback (section 04);
• turn on anonymous usage (05);
• ask the hosted coach (06);
• finish setting Rainge up, which gives your install a seat on the hosted coach; redeem an invite code; or tap the price card when you reach the coach’s weekly limit (07).

One small exception: now and then the app asks our server for its settings, such as whether a newer build is needed. That request carries your install ID and the app’s build number, and nothing about you or your swings.

About the install ID. It’s a random code Rainge makes the first time you open it, kept in your phone’s Keychain. It isn’t your name, email, Apple ID or a device identifier, and on its own it doesn’t say who you are. Section 07 explains when it can be linked to you.

Videos you record in Rainge, or pick from Photos or Files, are copied into Rainge’s storage on your phone and analysed there with an on-device pose model. Rainge never uploads video, or the body positions traced from it.

Two things you can choose to send are made from your video:

• when you ask the hosted coach, it receives a few still frames from your swings: single images, not video (section 06);
• a clip you share from Rainge goes wherever you send it.

Your originals in Photos aren’t changed, and deleting Rainge deletes its copies. If your phone backs up to iCloud, Rainge’s data may be part of that backup, under your own Apple account.

You can report a problem or suggest a feature from Settings, by shaking your phone, or with “Report this” on a video or a coach answer that failed. A report contains:

• what you write, and what you expected, if you say;
• your email, only if you add it, so Michael can reply;
• a screenshot of the screen you were on, unless you remove it;
• diagnostics, which you can read before you send: the app version and build, your iPhone model, iOS version, free storage, language and region, how many buckets and swings you have, the app’s recent log, and what failed, if something did. The log can include video file names, like IMG_1234.MOV.

Reports never include video.

Each report becomes an issue in a private GitHub repository. The screenshot is stored with Vercel at a long, random link that only that issue points to. The issue also carries your install ID, so reports can be matched to your coach seat, and so Rainge can tell you when something you reported is fixed. To stop abuse, our server counts how many reports each install sends in a day.

If you’re offline, reports wait on your phone and send when you reconnect.

The first time you open Rainge, it asks: “Share anonymous usage to help improve Rainge?” It stays off unless you turn it on, and you can change your answer in Settings at any time.

Milestones you reach before you turn it on are noted on your phone and sent once you do. If you never turn it on, they never leave your phone.

If you turn it on, the app sends only these six events:

installed

you open Rainge for the first time

first_video_picked

you pick your first video

first_report_seen

you see your first bucket report

coach_asked

you ask the coach a question

key_added

you add your own API key

returned_week2

you come back in your second week

Each event is just its name and the time, sent with your install ID and the app’s build. Our server keeps a count of each event per day, and the first time each install sent each one. No swing data, no screens, no location, nothing else.

If your coach seat carries your name or an invite code, Michael can see which of these milestones your install has reached.

During the beta, every install gets a seat on Rainge’s hosted coach while seats last. It runs on Claude, a model made by Anthropic, and we pay for it during the beta.

When you ask a question or request a full review, the app sends our server:

• your question;
• measurements from your buckets;
• a few still frames from your swings (images, not video);
• your swing thoughts and journal notes;
• your golfer profile: your handedness and your usual miss;
• Rainge’s instructions for the coach.

Our server checks your seat and weekly allowance, sends the request on to Anthropic, and streams the answer back to you. It doesn’t store or log what you asked or what the coach answered. For each answer it records your install ID, whether it was a question or a review, which model answered, how many tokens it used, what it cost, and when. That record is how the coach stays inside its budget.

Anthropic receives the request to produce the answer, and handles it under its commercial terms, which don’t allow it to train its models on this data. Anthropic may keep requests for a limited time, for example to check for misuse. See Anthropic’s privacy policy.

Other ways to ask the coach:

• Apple’s on-device model, on iPhones with Apple Intelligence, runs on your phone. Nothing is sent.
• Your own Anthropic key sends requests straight from your phone to Anthropic, under your account and its terms. They never pass through our server. The key stays in your phone’s Keychain and is never included in feedback.
• Ask in ChatGPT or Claude hands a prompt and stills to the app you pick. That app’s own policy applies.

Your seat. When you finish setting Rainge up, the app asks our server for a seat on the hosted coach. Our server stores a seat code, your install ID, a seat token (also kept in your phone’s Keychain), when the seat was made, and the first name you gave, if you gave one. The name is optional: leave it blank and your seat has none. You can change or clear it any time in Settings › AI coach, and clearing it there removes it from our server too. The beta has a limited number of seats.

Invite codes. Michael may also send you a single-use invite code. When you redeem one, our server stores the code, your install ID, a seat token and when you redeemed it, and Michael keeps a private note of whose code is whose. If your install already had a seat, the invite replaces it, and your first name moves to the invite.

So your seat links your install to you if it carries your name or an invite code. For an install with a seat, Michael can see:

• when the code was redeemed, and the last build of Rainge our server saw from it;
• how many questions and reviews it has used this week, and what the coach has cost this month;
• which usage milestones it has reached, if you turned on anonymous usage;
• the feedback sent from it.

He can’t see what you asked the coach or what it answered. That isn’t stored.

To enforce the weekly allowance, our server counts questions and reviews per install, per week.

The price question. When you reach the weekly limit, Rainge may show a card for a paid coach that might come later. If you tap it, our server stores the price you were shown and your answer to “What would make it worth paying for?”, with your install ID. Nothing is charged; the beta can’t take payments.

The beta comes through Apple’s TestFlight. Apple collects information about your use of TestFlight under its own privacy policy, and shares some of it with us: for example your name and email if you were invited by email, when you installed, your device and iOS version, session and crash counts, and anything you send through TestFlight’s own feedback, including screenshots and comments.

Our server copies TestFlight feedback and crash reports into the same private GitHub repository as in-app feedback, so everything is in one queue. You can stop testing at any time from the TestFlight app.

Anthropic

Runs the hosted coach’s model. Receives coach requests, only when you ask.

Apple

TestFlight. Handles what section 08 describes.

GitHub

The feedback queue. Holds feedback reports in a private repository.

Vercel

Hosts our server and these pages, and stores feedback screenshots. Handles every request to our server, including your IP address, and keeps short-lived technical logs.

Upstash

The database behind our server. Holds coach seats (with your first name, if you gave one), weekly counts, the coach’s cost record, daily usage counts and price-question answers.

We don’t sell data, and we don’t share it with advertisers or data brokers. These companies may handle data in the United States and other countries.

These pages set no cookies and run no analytics. Their typeface, Archivo, loads from Google Fonts, so Google receives your IP address and browser details when you open a page. Vercel hosts the pages.

On your phone. Rainge keeps your data until you delete it. You can delete a bucket or a swing at any time, and deleting the app deletes everything Rainge stored on the phone.

In the app. Settings › Delete all my data erases everything Rainge holds on your phone, and asks our server to erase your install’s records there: your coach seat and the name on it, weekly counts, the coach’s cost record, usage milestones and price answers. If you’re offline, the request waits on your phone and goes when you reconnect. Feedback reports you sent are closed and unlinked from your install, not deleted; to have them deleted too, email Michael (below).

By email. Write to Michael@anicca.ai to delete anything else, such as your feedback reports and their screenshots or a price-question answer, or to ask what we hold about you and get a copy. Include the first name you gave Rainge, or your invite code if you have one; it’s how we find your install. We’ll confirm when it’s done.

How long we keep it. The beta’s server records (seats, weekly counts, the coach’s cost record, usage counts and price answers) are kept while the beta runs and deleted when it ends. Feedback reports are kept while they help fix Rainge, and deleted sooner if you ask.

Rainge isn’t directed at children under 13, and we don’t knowingly collect information from them. If you think a child has sent us information, write to Michael@anicca.ai and we’ll delete it.

This is a beta policy, and it will change as Rainge does. When it changes, we’ll update the date at the top of this page, and say what changed in the next build’s What to Test notes in TestFlight and in Rainge’s What’s new sheet. We won’t start collecting a new kind of information without saying so in the app first.

History. October 2026: first version, for Beta 1. Later in October 2026: every install gets a coach seat, with an optional first name, and Delete all my data reaches our server.

Michael Nguyen
Michael@anicca.ai