The website does not use your camera. App workout analysis is designed to run on your device.
Sign-in is required in the current iPhone release build. Eligible profile and session data can sync. Normal sync excludes workout video.
Additional age and permission rules may apply where you live.
1. Who we are and what this covers
Nathan and Adrian operate the HoopArc project. This policy covers the public website at tryhooparc.com and the app features described here. Contact support@tryhooparc.com about how we handle your information. The app remains in development, and your installed build and its permissions determine which features you can use.
We aim to collect only what a feature needs, explain that purpose and keep camera processing on your device. If we introduce a new category of data, cloud processing or a child-account service, we will update this notice before asking people to use that feature.
2. Visiting our website
You can browse the site without an account or camera access. The site does not collect workout video or use advertising trackers. Browsing does not subscribe you to email updates.
The website’s illustrations respond to vertical scrolling automatically. The website respects your device’s Reduce Motion setting. Animated scroll scenes become a static explanation with manual stage controls. We do not change that device setting, store a website-animation preference or send scroll positions to our backend.
Cloudflare hosts and protects the site. It may process IP addresses, requested pages, timestamps and browser headers. It may use security cookies to deliver pages and protect against abuse. Cloudflare may insert a performance measurement script into page responses. The site’s current security policy blocks that script from running.
If you email support or ask about early access, we use your email address, message and any files you choose to send to respond. An early-access inquiry does not enroll you in a mailing list. Please leave out information we do not need, especially details about children.
3. Camera and information on your device
- Camera processing: the app analyses camera frames on the device during a session. We do not require workout video, photos, body-pose coordinates or ball-detection tensors to be uploaded for normal training.
- Optional session recordings: when you enable training-video recording, silent video is saved in the app’s local storage for later playback and scrubbing. Recording uses device storage and must finish saving before a replay is available. Workout footage is not included in normal account/session sync. Local files can be removed through recording-storage controls or lost when the app/device data is removed.
- Session history: training mode, start/end time, attempt outcomes and available session information are stored locally first. An uncertain or unmeasured result should remain uncertain rather than be presented as a confirmed measurement.
- Profile: development onboarding asks for a display name, birthday, height, weight, basketball position, shooting hand, weekly training frequency and experience. These answers are saved locally; eligible profile details can sync with your account. An optional profile photo stays on the device and is not included in profile-summary sync. Use a nickname if you prefer.
- Files you choose: a development or replay feature may process a video or other file you deliberately select. Selecting a file does not, by itself, authorize uploading it. Read the relevant build's prompt before using a diagnostic export or sending files to support.
4. Accounts and cloud sync
The current iPhone release build requires sign-in. Available methods depend on the build and service configuration. We use an internal account ID, your email address when available, and the account identifier from Apple or Google if you use one of those providers. Apple may share a relay address. Where email sign-in is enabled, we use your email to create, verify and manage your account.
When signed in, eligible profile and completed session data may sync. That can include your display name, username, birthday, physical measurements and training preferences, along with session IDs, modes, timestamps, attempt outcomes and goal progress. Normal sync excludes workout videos, camera frames, profile photos, body-pose coordinates and raw detection data. It also excludes demo sessions.
A server-side session and a protected device credential keep an account signed in. The device credential belongs in protected device storage (Keychain on Apple devices), not a public page or a log. The backend does not keep Google access or refresh tokens. For Apple accounts, an encrypted Apple token may be kept to support authorization revocation when the account is deleted. If an account feature is not configured, this policy does not imply that it already works.
5. Why we use information
Account information is used to authenticate you, protect your account, sync eligible results, restore your profile/history and process your requests. Limited security information helps prevent abuse. We do not sell personal information, use workout footage for advertising, or require a video upload to train. No permission to train an external AI model on your private workout files is granted merely by using HoopArc.
6. Children, parental permission and supervision
The current iPhone release build requires an account. Children under 13 should wait to use the app. Players aged 13 and older who are minors need parent or guardian permission where required by applicable law.
HoopArc does not offer accounts for children under 13 or a process for verifying parental consent. Do not create an account for a child under 13 or submit their identifying information through another person’s account.
Parental supervision does not replace verifiable parental consent where the law requires it. Any future service for children would need to address the applicable notice, consent, access and deletion requirements before launch.
If you believe a child has created an account or submitted identifying information, email support@tryhooparc.com. Do not attach a child's photo, ID or full birthdate. We will use proportionate checks to identify the affected account, stop unauthorized use and handle removal requests. See our guide for parents.
7. Providers and disclosure
Cloudflare provides website hosting, security, backend infrastructure and database services. Apple and Google handle sign-in if you choose those options when available. We may disclose information where reasonably necessary to comply with a valid legal requirement, protect people or investigate abuse.
8. Storage, retention and deletion
- On-device data: training history and recordings stay on your device until you remove them or delete the app. Device backups follow your device settings.
- Cloud account data: we keep your account, profile and live synced records while your account is active, subject to deletion and any applicable legal retention obligations.
- Security data and recovery copies: these follow separate expiry and recovery schedules based on the active infrastructure configuration.
- Support messages: we keep correspondence as needed to handle the request and related follow-up or legal obligations.
Account deletion removes your account and its associated live synced records and ends your sign-in sessions. Database recovery copies may remain until they expire. Account deletion and sign-out leave on-device history and recordings in place. See Data & deletion for separate instructions on cloud and device data.
9. Your choices and requests
- Change camera permissions in your device settings. Disabling permission prevents camera-based analysis.
- Review and edit profile fields exposed by your build.
- See Data & deletion for account and recording controls.
- Email support to request access, correction or deletion. Depending on your location, you may also be able to request a copy, restrict or object to processing, withdraw consent for consent-based processing, or complain to your privacy regulator.
- We may need to verify that the request concerns you or a child for whom you are responsible.
10. Security and international services
We use HTTPS, account-scoped access and protected credentials/encryption where applicable. No service can promise perfect security. You should protect your device and provider account, and avoid sharing credentials. Hosting/provider systems may operate in multiple locations; applicable safeguards and rights depend on the service and your jurisdiction.
11. Changes to this notice
The date above identifies this version. Material changes to data collection or child-account practices require updated notice before those features are offered. We will not treat a wording update as permission to collect data that needs a separate consent step.
12. Contact
Privacy questions, parent requests and account concerns: support@tryhooparc.com. Include only what is necessary to explain the request. See Support for account help and About HoopArc for our engineering approach.