Privacy Policy

What We Collect

When you use Repair Mate, the following data is processed:

• Repair content you provide. Photos, voice recordings (audio files, sent to the AI provider as audio rather than transcribed on your device), and text descriptions you submit to get a verdict, plus any follow-up messages you send. These are sent over HTTPS to our backend and forwarded to our AI inference provider so a fix can be generated. Your repair history is stored on your device only.
• A device identifier. We read your device's Identifier for Vendor (IDFV) — a value Apple resets if you uninstall the app — and send it with each request so we can rate-limit abuse. We do not link this to your name, email, or any contact information.
• Subscription status. When you subscribe, RevenueCat (our subscription management provider) records the purchase against an anonymous RevenueCat user id and tells our backend whether you have an active entitlement. We do not see your Apple ID, billing details, or card information at any point.
• Crash reports. If the app crashes, Sentry collects a stack trace, the iOS version, the device model, and the app build number so we can fix the bug. Crash reports do not include your repair content.
• Install attribution data, when you install Repair Mate from a Meta (Facebook / Instagram) ad. The Meta Business SDK embedded in the app reads your device's IDFV and basic app-launch events (app opened, version installed) and sends them to Meta so Meta can credit the install to the ad you tapped. The SDK does not read your repair content, photos, voice notes, contacts, or location. We do not request the IDFA (Apple's cross-app advertising identifier), and the app does not log in-app purchases through the Meta SDK, so Meta does not receive the products you bought, the price, or the renewal status. We also do not show Apple's App Tracking Transparency prompt, which means Meta also receives Apple's SKAdNetwork postbacks (aggregated and per-campaign, with no per-user identifier) in addition to the SDK-level IDFV signal.
• Anonymous product-usage events, via PostHog. The PostHog SDK embedded in the app records anonymous events about how the app is used (for example: app opened, onboarding step viewed, paywall viewed, trial started, verdict received). Each event is tagged with your anonymous RevenueCat user id (a random UUID — not your name, email, Apple ID, or IDFA), the app version, and the iOS version. PostHog does not receive the contents of your repair submissions (photos, voice notes, prompt text, or the AI's reply). We use these events to understand which screens cause people to drop out and to improve the app; we do not link them to any external identity and we do not use them for advertising.

We do not collect:

• Your name, email address, phone number, postal address, or any other contact information.
• Your location, contacts, calendar, photos library beyond what you explicitly attach, microphone audio outside an active recording, health data, or browsing history.
• The IDFA (Apple's cross-app advertising identifier). Repair Mate does not request the App Tracking Transparency permission and so cannot read the IDFA.
• The contents of your repair submissions in the product-usage events described above. PostHog only sees that an event occurred (for example: "verdictReceived"), not what you asked the AI or what it replied.

How We Use It

• Repair content is used solely to generate the verdict and step-by-step fix you asked for, and to render your repair history in-app.
• The IDFV is used to apply per-device rate limits at our backend so a single device cannot flood the AI inference provider.
• Subscription status is used to grant or deny access to the paid features (the unlocked verdict, the fix steps, and the follow-up coach).
• Crash reports are used to find and fix bugs.
• Install attribution data is used by Meta to confirm to us that an install we paid for actually happened, and by Meta to optimize which ad creatives are shown to people similar to those who installed. We do not see per-user data from Meta — we see aggregated campaign-level reports.

We do not sell your data, share it with data brokers, or use it for advertising other than the install-attribution role described above (telling Meta that an install we paid for happened).

Data Storage

• On your device. Your repair history (text, photos, voice notes, AI verdicts, fix steps, your "fixed" / "still broken" / "different problem" outcome answers) is stored locally in Core Data. We do not back this up to our servers, and it is not synced across devices.
• Our backend. Each request to generate a verdict or follow-up passes through our Cloudflare Worker. We do not persist your repair content there — the worker forwards your request to the AI provider and returns the response. Cloudflare keeps standard short-lived access logs (timestamps, IP, response codes) for operational purposes — typically up to 30 days on Cloudflare's standard schedule — and these are not associated with the contents of your repair submissions.
• Subscription records. RevenueCat stores a record of your subscription against an anonymous user id so that "Restore Purchases" works.
• Logs of AI requests. Our routing provider, OpenRouter, retains operational logs of API requests in line with their privacy policy. We have configured our OpenRouter account so that paid endpoints that might train on request data are disabled (see *AI Training and Your Data* below).

In-App Disclosure and Consent

Before any repair content leaves your device, Repair Mate shows an in-app disclosure that names the third-party AI service that will receive your submission (Google Gemini, accessed through OpenRouter and our Cloudflare Workers backend) and asks you to tap Continue to agree. We do not send your repair content to any third-party AI service before you have tapped Continue on that screen.

Third Parties

We rely on a small set of vendors. Each is contractually bound by their own privacy commitments and only receives the data described. We require these providers to maintain confidentiality and security protections that are at least equivalent to those described in this Privacy Policy.

We do not use any data brokers. The attribution and analytics SDKs we run are the Meta Business SDK (install attribution) and PostHog (anonymous product-usage analytics) described above.

AI Training and Your Data

Repair Mate does not use your repair content to train any AI model.

The underlying AI model that generates your verdict and fix steps is Google Gemini, accessed through Google's paid API. Google's paid Gemini API does not use prompts or responses to train Google's models — Google retains paid-API content only transiently for safety and abuse-prevention purposes (see Google's Gemini API terms).

The routing provider that sits in front of the model — OpenRouter — has an account-level setting that controls whether requests can be sent to paid endpoints that may train on request data. We have disabled that setting on our OpenRouter account, so requests are only sent to providers that do not train on your data.

We do not persist your repair content on our own servers beyond the time needed to return a response.

International Data Transfers

Some of the providers we rely on (Cloudflare, OpenRouter, Google, RevenueCat, Sentry) operate from the United States. When your repair content or technical data is transferred outside the European Economic Area, we rely on the EU Standard Contractual Clauses and, where applicable, the EU–US Data Privacy Framework, which our providers have committed to under their own privacy commitments.

Legal Bases (GDPR)

Where the GDPR applies to you (you are in the EU, EEA, or UK), our legal bases for processing are:

• Performance of a contract (Art. 6(1)(b) GDPR) — for processing your repair content to generate the verdict and fix steps you asked for, and for managing your subscription state.
• Legitimate interests (Art. 6(1)(f) GDPR) — for the per-device rate-limit using your IDFV (preventing abuse of our AI provider) and for crash reporting via Sentry (fixing bugs).

Your Rights

In the app, today:

• View your data. Your repair history is visible in-app on the Chat tab.
• Delete a single repair. Long-press a repair on the Chat tab and tap the delete option.
• Erase all your data. Open the You tab and tap Erase all data to remove every repair from your device.
• Uninstall. Deleting the app removes all locally stored repair content. Your subscription is tied to your Apple ID and is not deleted by uninstalling — manage it under Settings → [Your Name] → Subscriptions on your iPhone.
• Subscription record deletion. To request deletion of your RevenueCat record, email us at hello@tryrepairmate.com.
• Crash reports. To request deletion of any crash reports tied to your device, email us with the date and approximate time of the crash.

Under the GDPR (EU / EEA / UK users): you have the rights to access, rectify, erase, restrict, port, and object to processing of your personal data. You also have the right to lodge a complaint with the Lithuanian data protection authority — *Valstybinė duomenų apsaugos inspekcija* (vdai.lrv.lt) — or with the supervisory authority of your country of residence. To exercise any of these rights, email us at hello@tryrepairmate.com.

California Residents

If you are a California resident: we do not sell your personal information, and we do not share it for cross-context behavioural advertising. You have the right to know what personal information we hold about you, to request its deletion, and to request correction. We will not discriminate against you for exercising these rights. To make a request, email us at hello@tryrepairmate.com.

Children's Privacy

Repair Mate is not directed at children under 13, and we do not knowingly collect personal information from anyone under 13. If you believe we have, contact us at hello@tryrepairmate.com and we will delete it.

Changes to This Policy

We may update this policy from time to time. If we make material changes, we'll notify you through the app and update the Last updated date above.

Contact

Questions? hello@tryrepairmate.com