Privacy Policy

Information you give us

• Account details — your email address, a display name and a password, or the basic profile returned by Google or Apple when you choose their sign-in option. Apple may supply a private relay email address if you choose to hide your email. Your display name and email address can be seen by other members of a workspace you join. A nickname does not hide your email address from those members.
• Team data — events, vehicles, checklists, tune-up templates and history, race sessions, notes, reports, photographs and debrief data files you attach.
• Community activity — templates your workspace deliberately publishes, the workspace name and template reference/version shown as attribution, copies, star ratings, optional written reviews, and safety or content reports submitted for moderation. Your account identity is not displayed with a public rating or review.
• Weather readings — values you enter manually, values read from a connected Bluetooth sensor, or readings derived from your device location when you allow location access.
• Invitation codes — recognisable code names, assigned access type, acceptance status and the accepting account.

Passwords and authentication

Sign-up, sign-in, email confirmation and password reset are handled by the authentication service in TeamTuna-managed Supabase projects. Your password is submitted directly to that service, which stores it in hashed form. TeamTuna does not receive, display or store a readable copy of your password. If you sign in with Google or Apple, authentication happens with that provider and TeamTuna receives only the basic profile information returned by that sign-in.

Account verification, password reset and other authentication emails are delivered by Resend. The email recipient and message content, including the relevant verification link or code, are supplied to Resend for delivery. Your password is not sent to Resend.

Age and information about younger racers

People aged 16 or older may use a normal TeamTuna account. We collect and use the account and workspace information described in this policy for eligible users aged 16–17 as well as adults. Location-based weather, photos and file attachments are optional. You or your parent or guardian can contact support@teamtuna.app about privacy questions or rights requests. We may need to confirm identity and legal authority before responding to a request concerning another person's account.

If you enter information about another person, including a younger racer who does not hold an account, you must have the right and any required permission to share it. Enter only information your team needs. Do not publish a child’s identifying information in Community templates, ratings or reviews.

How we use it

Your information is used to operate the app: to sign you in, to show your team’s race data, to keep tune-up and weather history, to send account emails such as sign-up confirmation and password reset, and to deliver team invitations.

Location and weather lookups

Settings → Weather offers Manual GPS and Automatic GPS. Manual GPS captures location only when you tap a GPS capture action; Manual Entry means typing values without GPS. Unconfigured GPS uses Manual. Existing explicit automatic choices are preserved. Automatic GPS uses the selected location weather source at race-workflow capture points after location permission is allowed. A location indicator appears during capture. New shared weather readings retain measurements and weather-grid distance without phone or grid coordinates. Existing weather history and its team visibility are retained.

Location access is optional and is only requested when you use a weather feature that needs it. When you request location-based weather or an elevation lookup, your device’s latitude and longitude are sent to TeamTuna’s authenticated weather service hosted on Supabase. This service verifies your sign-in and sends the coordinates to the Open-Meteo customer API (open-meteo.com) using TeamTuna’s commercial service credential, which stays on the server. No TeamTuna account identifier or sign-in token is sent to Open-Meteo. Open-Meteo returns the centre coordinates of the forecast grid cell it used. TeamTuna calculates the distance using these coordinates during the lookup, then saves that distance with the weather measurements. New weather records, including queued captures and their imported values, omit phone and grid coordinates. Coordinates in previously saved weather history remain unchanged.

If you decline location access you can still record weather manually, and you can change the decision at any time from Settings → Weather. Location is used to capture conditions for a weather record; it is not used for advertising.

Photos and camera

Adding a debrief photo is optional. The system picker lets you choose specific photos or files; TeamTuna does not scan your photo library. If you choose to take a new photo, camera access is used for that capture. Selected photos are uploaded to your workspace so authorised members can view them. You can cancel the picker or decline camera access and continue using other app features.

Bluetooth weather sensors

TeamTuna can read temperature, humidity and barometric pressure directly from a supported Bluetooth weather sensor. The Bluetooth connection is made by your device to the sensor; the readings are decoded on your device and are only sent to our backend when they are saved as a weather record in your workspace. Bluetooth permission is requested only when you use this feature, and the sensor manufacturer’s cloud service is not involved in this direct connection.

Who can see your data

Your race data is scoped to your team workspace. Other members of that workspace can see it; people outside it cannot. Access is enforced by row-level security rules on the database, not only in the app interface.

Referrals and subscription rewards

If you open or share a TeamTuna referral, TeamTuna records the referral code, the referring workspace, the new account and its first owned workspace. Verified billing events are used to record whether the promised introductory benefit was supplied, whether the payment has passed the refund period, whether it was refunded, and whether the referring workspace earned or received a reward. Team owners see aggregate progress, not the referred customer’s payment details. Payment-card details are not stored by TeamTuna.

Referral records are used to deliver the offer, prevent duplicate or self-referrals, reverse refunded conversions and administer earned subscription months.

Service providers

Based on the current implementation, TeamTuna relies on these service providers:

• Lovable Cloud — hosting and delivery of the web version. This is separate from TeamTuna-managed Supabase backend services.
• Supabase — TeamTuna-managed database, authentication, private photo and file storage, and server-side services including authenticated weather lookups.
• Resend — delivery of authentication emails such as sign-up confirmation and password reset.
• Open-Meteo — weather and elevation lookups from coordinates, only when you use a location-based weather feature.
• Google — authentication when you choose Google sign-in. The web app also loads fonts from Google Fonts, which receives browser requests even when you have not signed in. Installed mobile builds bundle these fonts instead.
• Apple — only if you choose Apple sign-in or use Apple store services.
• RevenueCat — coordinates subscription purchase validation and verified billing events across supported stores.
• Apple App Store / Google Play — only if you install TeamTuna from a store or purchase a subscription through a supported store.

International processing

TeamTuna is operated from Australia and is available internationally. Our service providers operate infrastructure in multiple countries, so your information may be stored or processed outside the country you use the app from.

Cookies and browser storage

TeamTuna stores a small amount of functional information in your browser so the app works correctly:

• Authentication session — your signed-in session token, so you stay signed in between visits.
• Remembered email — your email address, only if you tick “Remember me” on the sign-in screen.
• Selected team — which workspace you are currently working in.
• Invitation state — a pending invitation token held for the duration of the browser session while you sign in or sign up.
• Referral state — a pending referral code retained for up to seven days while you sign in, confirm your email or create an account.
• Race progress — which race session you have started, so the workflow survives a refresh or a lost connection.
• Interface cookie — a functional cookie remembering whether the navigation sidebar is expanded or collapsed.

These are functional: they are needed for sign-in, workspace selection and the race workflow, and they are not used for advertising profiles.

Retention and deletion

Your data is kept while your account and workspace exist. You can delete events, vehicles, templates and other records from within the app, and you can export a full backup at any time from Settings.

To request deletion of your entire account while signed in, open Settings → Delete account and submit the in-app request. Our deletion team processes it manually and emails you when it is complete. If you cannot sign in, contact support from the address on the account so we can verify ownership.

Your rights and contact

You can access and correct most of your information directly in the app, and you can initiate entire-account deletion in Settings without contacting support. If you cannot sign in, or for any other privacy request, contact support@teamtuna.app.