Privacy policy

We collect only what we need to run REPZ:

• Account information. When you create an account we collect your email address and a username. If you use Sign in with Apple, we receive the identifier (and, if you choose to share it, the name and relay email) that Apple provides. You may also add an optional profile photo.
• Workout data. The exercises, sets, reps, weights, durations, and notes you log, plus any progress and statistics derived from them.
• Health & fitness data. With your permission, REPZ reads data from Apple Health (HealthKit) in a few ways. During a workout, it reads your heart rate and related metrics to show live stats on your iPhone and Apple Watch. In the Activity section, it imports your completed Apple Watch and Apple Fitness workouts — including the activity type, duration, distance, active calories, heart rate, pace, elevation gain, effort rating, and, when your device recorded one, the GPS route of the workout and the name of the town or city where it started — so all of your training appears in one place. Imported workouts, route and heart rate included, are saved to your account and shown to your friends unless you turn off Share Activities (see Apple Health below). If you use the Nutrition Tracker, REPZ also reads your daily activity totals so that, on days you move more than your plan expects, your calorie target for that day can grow to match — and can read your weight and height to pre-fill your nutrition profile and estimate progress toward your weight goal. REPZ can also write the workouts you complete in the app, and the water you log, back to Apple Health. With your permission, REPZ also reads your sleep, resting heart rate and heart rate variability (HRV) to show daily readiness, your rest-day recovery and your recovery history. Resting heart rate and HRV usually come from an Apple Watch, or from another device that saves them to Apple Health. These readings are compared with your own recent history on your iPhone only: they are never uploaded to REPZ servers, never stored in our database, never shared with friends, and never sent to an AI provider. On a day readiness suggests taking it easier, REPZ keeps your targets at last time’s numbers instead of raising them. An AI feature that receives your targets (the workout generator and planner, planning a session from REPZ Coach, or an exercise swap) gets those numbers, never the readings behind them. Starting with REPZ 1.6.3, a target held for readiness reads exactly like any other held target (“match last time”); earlier versions add that recovery looks lower than usual. Readiness is a guide for training, not a medical reading.
• Microphone & speech recognition. If you use Log by Voice in Add Food, REPZ listens only after you tap the mic, and stops when you tap it again or finish. Your speech is turned into text on your device by Apple’s on-device speech recognition. Your voice is never recorded, stored or sent anywhere. Only the resulting text is sent to our AI provider to find the foods you named, the same as if you had typed it, and you review the foods before anything is logged. Each use counts as one AI food scan.
• Siri. If you star foods as favorites, REPZ makes their names (with each one’s brand, serving and calories) available to Siri on your iPhone and your paired Apple Watch, so you can say, for example, “Hey Siri, log my coffee in REPZ”, or say “Hey Siri, log some coffee in REPZ” and answer with an amount such as “48 grams”. When you use Siri on Apple Watch, the request goes to your paired iPhone, which logs the food to your account. The only thing saved is the food entry itself, as if you had logged it in the app. REPZ receives only the food Siri matched and, for an amount, the words Siri heard as text; it never receives recordings of what you say to Siri. You can turn this off in REPZ Settings → Log Food with Siri. Apple’s handling of Siri requests is governed by Apple’s privacy policy.
• Photos & moments. REPZ never asks to read your photo library. When you choose a photo — a profile photo, a meal or nutrition label to scan, screenshots to import a workout, or a photo to share with friends as a moment — iOS’s photo picker gives REPZ only the photos you pick. Meal and label photos and import screenshots are sent to Google’s Gemini AI to be read and are never stored by REPZ (see AI Features & What They Send). A moment (the photo, its caption and any place name you tag) is stored on our servers and shown to your friends until you delete it; its photo, like your profile photo, is checked automatically by Google Cloud Vision (see How Information Is Shared). If you choose Save Image when sharing a PR card, REPZ asks for permission to add that image to your photo library; it cannot read or browse your library through this permission.
• Location. If you use gym search, nearby-restaurant discovery in the Nutrition Tracker, or the places REPZ suggests to tag on a moment, your location is used on your device with Apple Maps to list places around you. Your current location is never saved, and never sent to REPZ servers. A gym or place you choose is saved, by name, with that workout or moment. Routes of workouts you import from Apple Health, and the town or city each one started in, are covered under Health & fitness data above. Location is used only while you’re using the app; we do not track your location in the background, and these features work without location (search by name instead).
• Device & push tokens. To deliver notifications (such as friend activity), we store a push notification token associated with your device. We also store your notification preferences, meaning which kinds of notification you want (friend requests, friends’ workouts, Reps & comments, friends’ photos, workout invites, challenges, hype), so our servers send only those. Training-day reminders and the Sunday check-in reminder are scheduled on your device as local notifications, built from the training days saved in your profile and the workouts you’ve logged; the reminder time, and whether reminders are on, stay on your device.
• Nutrition data. If you use the Nutrition Tracker, we store the foods you log — names, serving sizes, calories, and macronutrients — plus your nutrition goals and, if you complete the goals questionnaire, the profile behind them (weight, goal weight, height, age, sex, workouts per week, training style, any other activities you describe, and pregnancy or breastfeeding if you set it). Your individual food entries are private to your account.
• Food searches & barcodes. When you search foods, search a restaurant’s menu, or scan a product barcode, the search text (including any restaurant name) or barcode number is sent through our servers to nutrition-data providers to return nutrition facts. These requests are not tied to your name or profile by those providers.
• Community menu items. If you add a menu item to a restaurant’s shared menu, the item itself (name, serving, and nutrition values) becomes part of the community database visible to all REPZ users. Your name and profile are never shown with it. Submissions are reviewed by an AI check before publishing, and AI-estimated values are labeled as estimates.
• Community products. If you share a product you log by its barcode (Share is on by default when you type in a product’s details or scan its label), its barcode, name, brand, serving and nutrition values can become visible to all REPZ users. Its name, brand and serving are checked by AI when they’re new or changed (see AI Features & What They Send). Your account is stored with it, and with any product you confirm or flag as the wrong product, but other users don’t see who added, confirmed or flagged it. If you delete your account, the product stays in the database without your account attached.
• Anti-fraud install identifier. To prevent abuse of the free trial (for example, creating repeated accounts to claim it again and again), the app stores a randomly generated identifier securely on your device and sends it to our servers with your subscription status. It contains no personal data, is not derived from any hardware identifier, and is used only for fraud prevention and security — never for advertising or tracking across other apps.
• Progress, levels & achievements. We calculate and store your XP total, level, streak, weekly progress, and the achievements you have unlocked, derived from the workouts, activities and meals you log. This is what the friends leaderboard reads.
• Reactions & comments. If you react to or comment on a friend’s workout or activity, we store that reaction or the text of your comment along with your username and profile photo, so it can be shown to the people who can see that post.
• Training together. When you train live with a friend from a workout invite, the sets you tick off (exercise, weight, reps, set type and how far into the session) and the workout’s name are shared with that friend as you go. Starting with REPZ 1.6.3, when the person who sent the invite swaps an exercise, the swap (the old and new exercise names and the new one’s body part) is shared the same way, so the friend’s workout can follow it. Only the two of you can read these live records; each one expires 12 hours after it was last updated and is then deleted automatically, usually within a day. The workout you save afterwards records the friend you trained with (their account ID, username and name).
• AI inputs. Several features send data to Google’s Gemini model (via Firebase AI Logic or Google Cloud Vertex AI) and return a result. Each one, and what it sends, is listed in AI Features & What They Send below; starting with REPZ 1.6.3, the app asks before any of them first sends anything. In short: a summary of your training, progress, nutrition and profile (age, sex, bodyweight and goal weight, and pregnancy or breastfeeding if you set it, plus today’s activity calorie credit from Apple Health if you use the Nutrition Tracker) for REPZ Coach and AI Insights; your recent workouts, exercise notes and REPZ’s targets for workout planning, exercise swaps and Coach’s Take; the name, equipment and classification of a custom exercise for exercise review; a day’s food names and nutrient totals for the nutrient rundown; a weekly summary for the Sunday check-in; the meal and label photos, screenshots, descriptions and corrections you choose to send; the text of what you said for Log by Voice; the foods and menu items you add to the shared database; and the name, brand and serving of a barcode product you share. AI food scans (photo, label, or a typed or spoken description) are limited to 15 per day, the Sunday check-in to one per week, and Coach conversations are capped per day; we keep simple counters (numbers, not content) to enforce those limits.

REPZ’s AI features run on Google’s Gemini model, reached through Google Firebase (Firebase AI Logic, which uses Google Cloud Vertex AI) or, for the shared food database, shared barcode products and restaurant menu items, through Vertex AI from our servers. Each feature sends only what it needs, listed below. The prompts REPZ builds don’t include your name, username or email address, though each request from the app carries your REPZ sign-in token, so Firebase can verify which account sent it. What you type, the text of what you say, and the photos you choose (downscaled) are sent as they are. AI output is a suggestion: you can review, change or remove anything an AI feature adds.

REPZ asks first. Starting with REPZ 1.6.3, before any AI feature first sends anything to Google, REPZ shows a screen that names Google, lists what can be sent, and asks. Nothing is sent unless you tap Allow; Not Now cancels that action, sends nothing and doesn’t use up a scan or any other allowance. Features that would otherwise run on their own — Coach’s Take after a workout, the Sunday check-in and the opening swap suggestions — show a button instead until you allow AI features. If you tap Allow, REPZ remembers that for your account on that device; after Not Now, the next AI feature you use asks again. You can turn AI features off at any time with the AI Features switch in Settings (tap your profile picture) → Privacy & Legal; after that nothing more is sent, and each AI feature asks again before it’s used. Sharing a barcode product is included: in REPZ 1.6.3, if you haven’t allowed AI features, the product is logged for you but not shared. Earlier versions of REPZ don’t show this screen: using an AI feature in them sends what’s listed below.

Coaching

• REPZ Coach — a multi-turn chat grounded in your own data. Your messages and the conversation so far are sent with a summary of your training, progress and nutrition: your age, sex, bodyweight, goal weight and training style (and pregnancy or breastfeeding, if you set it); your weekly schedule, planned workouts and today’s date; workout count, consistency, level, streak and days trained this week; 12 weeks of volume, body-part balance and the last 30 days’ muscle coverage; strength trends, plateaus, projections and best estimated one-rep maxes; recent sessions (date, name, body parts, duration, volume and sets — not your notes); your 7-day nutrition averages, targets and today so far; and, if you use the Nutrition Tracker, today’s activity calorie credit from Apple Health. The Coach is instructed to decline medical, injury-diagnosis and supplement-dosing questions and to point you to a professional instead.
• AI Insights — the same summary REPZ Coach uses (your recent training, progress, nutrition and profile), written up as insight cards.
• Coach’s Take — after a workout, that session’s name, date, duration and gym; its volume, set and rep totals, body parts, movement patterns and muscle sets; the PRs you set; each exercise’s sets with last time’s numbers and REPZ’s target for next time; and your exercise notes (up to 500 characters).
• Sunday check-in — once a week, a summary the app computes on your device from that week’s data: the week’s dates, sessions against your weekly target, training time, working volume and its change on the week before, up to five personal records (exercise names and numbers), your top three most-trained areas, how many days you logged food, how many of those days hit your calorie target, and your average protein as a percentage of your target. No individual food entries or profile details are sent. The AI only writes the words. Limited to one per week.

Workouts

• Workout generator & planning — the AI workout generator, AI fill in Plan Workout, planning a session from REPZ Coach, and Plan My Week (and refining it). These send what you ask for (up to 500 characters; when planning from REPZ Coach, the Coach’s recommendation), a summary of your 15 most recent sessions (date, name, body parts, each exercise’s set count and top set, and your exercise notes, up to 200 characters each), today’s date, the last 30 days’ muscle coverage, your weekly schedule and whether today is a training day, REPZ’s target for each exercise, and the names of the exercises in your library (including custom ones). Planning a week also sends the dates on offer, the current plan and any change you ask for.
• Exercise swap & ask — the exercise, its equipment and classification, what you type (or, if you just ask for a swap, that the machine is down), the other exercises in the session, today’s sets, last time’s numbers, REPZ’s target for today and why, and the candidate replacements.
• Custom exercise review — when you ask for a second opinion on a custom exercise, its name, body part and equipment, and the classification currently shown, are sent to return a classification.
• Workout import from screenshots — the screenshots you pick (up to six), the names of the exercises in your library (including custom exercises you’ve created) so the AI can match them, and, when planning a week, any note you type for it. Read to build a workout you review before anything is scheduled; exercises the import finds that aren’t in your library yet may be added to it as custom exercises. REPZ never stores the screenshots. Limited to 10 imports per day.

Nutrition

• Nutrient rundown — the day, how many foods you logged and up to 25 of their names, each nutrient’s total, target and percentage (and how many foods reported it), the nutrients with no data, and what your targets are based on (sex and age band, or pregnancy or breastfeeding).
• AI food recognition — the meal photo you take or choose (downscaled), or the photo of a restaurant item you’re adding, to identify foods and estimate portions. REPZ never stores it (see below).
• Describe a meal & Log by Voice — the description you type, or the text your iPhone transcribed from what you said (never audio), to identify foods and estimate portions. Each description, typed or spoken, counts as one AI food scan.
• Fix-it chat — each correction you type, with the photo or description and the estimate it corrects.
• Label scan — the photo of a nutrition label, read to fill in the food’s nutrition facts. REPZ never stores it.
• Restaurant menu items — when you add an item to a restaurant’s shared menu, the restaurant and item names, the serving, any calories and macros you entered, and your description (up to 300 characters) are sent from our servers to check the item, fill in missing values and tidy its name before publishing. Your identity is not sent with it.
• Community foods — when you add a food to the REPZ database by name, the food’s name, brand, serving and nutrition values are checked and normalized by AI before publishing; your identity is not sent to the AI. The food is stored with your account attached (and if you add a food someone else already added, your account is recorded as confirming it); other users don’t see who added or confirmed it. If you delete your account, the food stays in the database without your account attached.
• Barcode products you share — when you log a barcode product with Share on, and its name, brand or serving text is new or changed, our servers send those words to Gemini to check them before the product is shared with everyone. The nutrition numbers and your identity are not sent to the AI. Starting with REPZ 1.6.3, a product is shared (and checked) only after you allow AI features; earlier versions run this check without asking.

Google processes what these features send to produce each result, under the Google Cloud terms that govern Firebase AI Logic and Vertex AI. AI features are never used to build an advertising or marketing profile of you. AI output is a suggestion, not a measurement or medical advice — see our Terms of use.

When you photograph a meal or a nutrition label for AI analysis, the photo is transmitted securely to our AI provider (Google Gemini via Firebase AI Logic) to produce the estimate. REPZ never stores your meal or label photos — not in our database, not in file storage. Google processes the photo to produce the result and may keep it for a limited time under its Google Cloud terms. Only the nutrition estimates you choose to log are saved to your account.

AI-generated nutrition values are estimates based on what is visible in a photo. They are not exact measurements and should not be relied on for medical purposes. The app labels these values as estimates and lets you adjust them before saving.

AI food scans are limited to 15 per day, shared by photos, labels and described meals (typed or spoken), resetting at your local midnight. The app shows how many scans you have left and when new scans become available.

• To provide and operate the app and your account.
• To save your workouts and show your progress, history, and live stats.
• To enable social features you opt into, such as friends and activity notifications.
• To track your nutrition and show your calorie and macro progress, if you use the Nutrition Tracker.
• To calculate your XP, level, streak and achievements, and to rank you against friends who are also sharing progress.
• To produce suggestions when you use an AI feature, as described above.
• To keep the community safe — acting on reports, honoring blocks, and preventing abuse of the free trial.
• To respond to your support requests.
• To maintain the security and reliability of the service.

We do not sell your personal information, and we do not use your Apple Health data for advertising or marketing.

Health data accessed through HealthKit is used to provide REPZ’s fitness features — showing your live stats during a workout, displaying the Apple Watch and Apple Fitness activities you import in the Activity section, and adjusting your daily calorie target on days your activity exceeds what your plan already budgets. That adjustment is computed on your device; what REPZ stores is the resulting calorie target, not your underlying activity readings. If you use REPZ Coach or AI Insights, that day’s activity calorie credit (a single number) is part of the summary sent to Google’s Gemini, as listed above. We never use HealthKit data for advertising, and we never share it with third parties for their own purposes.

Sleep, resting heart rate and HRV are read only to show readiness and recovery and, on a “take it easier” day, to keep your training targets at last time’s numbers. They are processed on your device and are never uploaded, stored on our servers, shared with friends or sent to an AI provider. (An AI feature you use on a “take it easier” day receives only the held target. Starting with REPZ 1.6.3 it reads like any other held target; earlier versions add that recovery looks lower than usual. See above.)

If you connect Apple Health, the activities you import are saved to your account and, if you have accepted friends in REPZ, shared with those friends as part of the activity feed unless you turn off Share Activities (it is on by default). This includes each activity’s summary and details — type, duration, distance, active calories, heart rate, pace, elevation, effort rating, and, when your device recorded one, the name of the town or city where it started and the GPS route of the workout, which a friend can view on a map. Only friends you have accepted can see this. To stop sharing, turn off Share Activities in Settings (tap your profile picture) → Privacy & Legal, which hides all of your imported activities from friends, new and old (they still count toward your own XP); you can also remove the friend, or revoke REPZ’s access to Apple Health, which stops new activities from importing.

You can review or revoke REPZ’s access at any time in the iOS Settings → Health → Data Access & Devices.

We use trusted infrastructure providers to run REPZ and share data with them only to deliver the service:

• Google Firebase (authentication, database, and push notifications) stores your account, workout, and imported activity data on our behalf.
• Apple provides Sign in with Apple and push notification delivery.
• Google AI (Gemini), via Firebase AI Logic or Google Cloud Vertex AI, processes the inputs you submit to REPZ’s AI features, as itemized in AI Features & What They Send above (starting with REPZ 1.6.3, only after you allow AI features). REPZ never stores the meal and label photos or import screenshots you send; Google processes them to produce the result and may keep them for a limited time under its Google Cloud terms.
• Google Cloud Vision automatically checks each profile photo and moment you upload for explicit or violent content; a photo it flags is removed and recorded for us to review.
• Nutrition-data providers (fatsecret, USDA FoodData Central, and Open Food Facts) receive only your food search text or a scanned barcode number — routed through our servers, never with your identity — and return nutrition facts. We cache those results on our servers keyed by the search term or barcode (up to 7 days for searches, 30 for barcodes) so common lookups are fast — the cache is shared by everyone and records nothing about who searched.
• Cloudflare hosts this website and relays the reports you file in the app, and the feature requests you send from this website, to our inbox.

If you use the Nutrition Tracker, friends you have accepted in REPZ can see a daily summary of your nutrition — total calories, protein, carbs, fat, and goal progress — for friendly accountability. They never see your individual foods or meals. Sharing is on by default; you can turn it off at any time in Nutrition Settings, which immediately stops access.

If you connect Apple Health, friends you have accepted can also see the Apple Watch and Apple Fitness activities you import — such as runs, rides, swims, and hikes — including their details and, when your device recorded one, the workout’s GPS route shown on a map. Only accepted friends can see this, and turning off Share Activities hides it from them; revoking REPZ’s access to Apple Health stops new activities from importing.

We may also disclose information if required by law or to protect the rights, safety, and security of REPZ and its users.

REPZ turns what you log into XP, a level, a streak and achievements. Friends you have accepted can see those numbers on a shared leaderboard that resets weekly.

You can turn this off with Show My Progress in Account Settings. Turning it off is mutual — you disappear from your friends’ leaderboards and they disappear from yours — and it is enforced on our servers, not just hidden in the app: with it off, your progress record is genuinely unreadable to other accounts. Your own tracking continues normally.

Friends who can see one of your workouts or activities can react to it or leave a comment. Comments are free text written by other people; your username and profile photo appear next to anything you write. Comments cannot be edited after posting, you can delete your own, and the owner of a post can delete any comment on it.

Friends can also send you “hype” — a short encouragement notification. These are fixed messages chosen from a list; nobody can type their own text into one, and they are limited to once a day per friend. You can turn them off with Allow Hype From Friends in Account Settings, which stops the notifications without notifying the sender.

When you delete your account, the reactions and comments you left on other people’s posts are deleted too — your username and your words do not stay on anyone else’s screen.

You can block another user from their profile. Blocking stops them from sending you friend requests, seeing your shared data, and reacting to or commenting on your posts; it is enforced on our servers. Blocked accounts are listed in Account Settings, where you can unblock them.

You can also report a user for objectionable behavior. A report sends us the reported account, the reason you select and any details you add, and we review it. We may remove content, restrict or remove accounts, or take other action in response. Blocking and reporting are independent — blocking someone does not require reporting them.

Other signed-in REPZ users can find you by searching your username, which shows your username, display name, and profile photo. Your workout details and nutrition summaries are only ever visible to friends you have accepted.

If you prefer not to be discoverable, turn on Private Profile (Ghost Mode) in Account Settings. While it’s on, your account does not appear in user search and no one new can send you friend requests — new friendships can only be started by you. Your existing friends keep exactly the access they already had, and anything you share with them (like nutrition summaries) is controlled by its own separate setting.

REPZ offers a paid subscription (REPZ Pro) with an introductory free trial. Subscriptions are sold and processed by Apple through your App Store account.

• We never see your payment details. All billing is handled by Apple. We do not collect or store your credit card, debit card, or bank account information.
• Subscription status. To unlock paid features, we receive only whether your subscription is active or inactive — never your payment information.
• Managing your subscription. You can view, change, or cancel your subscription at any time in your App Store account settings. Apple’s handling of your purchase is governed by Apple’s own privacy policy.
• Free-trial integrity. To keep the free trial available for genuine new users, we associate the random install identifier described above with the accounts and subscription transaction identifiers seen on that device. If a device has already used a free trial under a different account, the app may not advertise a new trial. Apple alone decides actual trial eligibility at purchase.

We keep your information for as long as your account is active. You can delete your account at any time from within the app (Settings → Delete Account). Deleting your account permanently removes your profile, workouts, nutrition entries, progress and achievements, and the reactions and comments you left on other people’s posts, and revokes any Sign in with Apple token associated with your account. It is a deletion, not a deactivation — there is no waiting period and no email required.

You can export your data at any time: Settings (tap your profile picture) → Privacy & Legal → Export My Data produces a machine-readable JSON file you can save or share from your device. Starting with REPZ 1.6.3, our servers build it from everything REPZ stores about you: your account email and sign-in details; your profile, settings and training schedule; your workouts, saved and planned workouts and custom exercises; your food diary, saved meals and favorites, nutrition goals and body stats; the Apple Health activities you imported, with their routes; your moments; the Reps and comments you left, and those on your own posts; your inbox; your XP and progress; your challenges, workout invites, friend requests and blocks; reports you filed; your community food and menu contributions (with other contributors’ accounts removed); your subscription status and AI scan count; and a list of your photo files (where each one is stored, not the images). Your friends list holds only each friend’s account ID and username. Left out, and listed in the file itself: what belongs to other people (whether someone has blocked you, and reports others filed about you), abuse-prevention counters, the free-trial device record, and Apple’s billing notifications. If our servers can’t be reached, the app builds the file on your phone from what your account can read, and the file says what that copy is missing. Earlier versions of REPZ export only your profile, workouts, saved workouts, custom exercises and friends list. For a copy of anything else, such as the photo files themselves, email [email protected] and we will send it.

One narrow exception: minimal fraud-prevention records — the random install identifier, associated internal account identifiers, and subscription transaction identifiers — may be retained after account deletion. Without this, deleting and recreating accounts would defeat free-trial protections entirely. These records contain no name, email, or other profile data, and are used solely for fraud prevention and security.

We protect your data in transit and at rest using industry-standard encryption, and we restrict access to it. No method of transmission or storage is perfectly secure, but we work to safeguard your information and to limit what we collect in the first place.

REPZ is not directed to children under 13, and we do not knowingly collect personal information from them. If you believe a child has provided us information, please contact us and we will remove it.

In the app you can, at any time:

• Update your account details, username, and profile photo.
• Control Health, camera, notification, location, microphone, speech recognition, Siri and Photos permissions in iOS Settings.
• Turn individual notification types on or off (Settings → Notification Types); set or turn off training reminders, which include the Sunday check-in reminder (Settings → Training Reminders); and turn off Log Food with Siri (Settings → Log Food with Siri).
• Turn nutrition sharing on or off (it is on by default), and turn Share Activities, Show My Progress or Allow Hype From Friends off in Account Settings.
• Turn AI features off (Settings → Privacy & Legal → AI Features, starting with REPZ 1.6.3).
• Hide your account from search with Private Profile (Ghost Mode).
• Block or report another user, and manage your block list.
• Export your data (Settings → Privacy & Legal → Export My Data) or delete your account (Settings → Delete Account).

Depending on where you live, you may have rights to access, correct, delete, or receive a portable copy of your personal information, to object to or restrict certain processing, and to withdraw consent. The in-app delete control satisfies the deletion right directly and immediately, and the in-app export gives you the data listed above at once. For a copy of anything else, or any other request, email us and we will respond within the time your law allows.

If you are in the EEA or UK: we process your data to perform our contract with you (running your account and the features you use), on your consent (Apple Health, location, microphone, notifications, AI features from REPZ 1.6.3 on, and optional sharing — each withdrawable in iOS or in-app Settings), and on our legitimate interest in keeping the Service secure, checking what is shared with other users (uploaded photos and shared barcode products), and preventing fraud.

If you are in California: we do not sell or share your personal information, and we have not done so in the preceding twelve months. We do not use it for cross-context behavioral advertising, and we will never discriminate against you for exercising a privacy right.

Where your data lives:REPZ is operated from the United States, and our infrastructure providers store data on servers in the United States. Requests to REPZ’s AI features go to Google’s global Vertex AI endpoint, and the automatic check on photos you upload to Google Cloud Vision’s global endpoint; both may be processed in Google data centers outside the United States. If you use REPZ from elsewhere, your information is transferred to the United States.

We may update this Privacy Policy from time to time. When we do, we will revise the “Effective” date above and, where appropriate, notify you in the app.

Questions about this policy or your data? Email us at [email protected].