Privacy Policy

At a glance

RePasito does not sell personal data, show advertising, use the advertising identifier, or track you across apps or websites owned by other companies. Your recordings, imported media, Apple Music selections, practice settings, and search history are not uploaded to the developer.

Camera, microphone, and media

With your permission, RePasito uses the camera and microphone to record your takes. You may also choose an audio file, a reference video, a YouTube video, or, on iPhone, an Apple Music track for practice. Recordings, imported media, practice settings, and recent searches are processed and stored locally on your device. They are not uploaded to us.

When you save a finished take, RePasito adds it to your Photos library on iPhone, or to the Movies/RePasito folder of your device’s gallery on Android. It remains there until you delete it.

YouTube

RePasito uses YouTube API Services to let you search for, select, and play YouTube videos. When you search, your search terms are sent to YouTube to return results. When you play a video, it is streamed in YouTube’s embedded player, which is operated by Google and may collect information, including through cookies or similar technologies, under Google’s privacy policy. RePasito does not sign you in to YouTube, does not access your YouTube or Google account, and does not download or record YouTube audio or video. Takes recorded with a YouTube video contain only your camera and microphone recording. Recent searches are stored only on your device, and you can clear them on the search screen.

By using the YouTube features in RePasito, you agree to the YouTube Terms of Service. Google’s handling of your information is described in the Google Privacy Policy.

Product analytics

RePasito uses Firebase Analytics to understand broad product usage and improve the app. Analytics may collect a random app-instance identifier, device and operating-system information, app version, approximate location derived from network information, and product-interaction events such as starting a practice, completing a capture, opening the paywall, completing a purchase flow, saving a take, or using the feedback feature.

Analytics events do not include song titles, video titles or links, imported media identifiers, recordings, gesture frames, feedback text, your name, email address, or payment details. Advertising personalization signals are disabled. On iPhone, RePasito does not link the advertising-support framework. On Android, RePasito does not use the advertising ID, and advertising storage, advertising user data, and ad personalization consent are denied.

Acquisition and purchase analytics (iPhone)

This section applies to RePasito for iPhone. RePasito for Android does not collect install attribution or advertising-campaign data. To understand how people discover RePasito and how our Apple Ads campaigns perform, we collect a random installation identifier, app and iOS versions, App Store country, and the time we first observe an installation. We associate available Apple Ads attribution, such as campaign, ad group, keyword, ad, and interaction information, with App Store purchase, renewal, refund, and auto-renewal information for internal analysis. Firebase anonymous authentication and device attestation protect these requests. We do not collect the advertising identifier (IDFA), payment-card details, or Apple Account credentials, and do not use these records to track you across other companies’ apps or websites.

We keep acquisition records for 24 months after first-observed launch, extended by associated purchases, subscription expiries, or refunds. Each purchase and related event is kept for 24 months after its latest relevant purchase, expiry, refund, or subscription activity. Expired records stop appearing in reports and are removed by routine cleanup, normally within 24 hours. Operational status logs are retained for 30 days; short-lived attribution abuse-limit records expire after two days.

To request deletion of these acquisition and purchase analytics, open Settings → Privacy data request and email leontopodi@proton.me with the private installation reference shown there. We use that reference and associated purchase records to locate and honor your request. We retain minimal hashed technical markers separately from analytics to prevent deleted history from being imported again. Deletion does not cancel an App Store subscription or delete your recordings. Deleting the app does not itself delete server-side records or stop subscription notifications from Apple; its Keychain identifier may remain on the device. Reinstalling creates a new installation reference.

Google Play purchases (Android)

On Android, Google Play processes your payment for RePasito Pro. The developer does not receive your payment-card details or Google Account credentials. To unlock Pro, the app sends the purchase token issued by Google Play to a protected Firebase service. That service asks Google Play for the subscription’s current state, acknowledges new purchases, and stores a one-way hash of the token together with the product, subscription state, expiry time, and verification time. The raw purchase token is not stored. Google Play also sends the service real-time notifications about subscription changes, such as renewals, cancellations, and refunds. The service then checks the subscription state with Google again. Firebase anonymous authentication and Firebase App Check, using Google Play Integrity, verify that these requests come from a genuine copy of the app.

The app keeps the verified subscription state on the device for at most 12 hours or until the subscription expires, whichever comes first, and does not include it in Android backups. Purchase verification records are kept while they are needed to restore and verify your subscription. To delete them, contact the developer as described below. Deleting these records does not cancel a Google Play subscription; manage or cancel it in the Google Play Store. Verification rate-limit records expire after about 24 hours.

Optional feedback

If you choose to send feedback in the app, RePasito sends your feedback category and message, a random submission identifier, app version and build, and iOS or Android version to a protected Firebase service. Firebase creates an anonymous user identifier and uses Firebase App Check to verify that the request comes from a genuine copy of the app. On iPhone, App Check uses Apple App Attest. On Android, it uses Google Play Integrity.

The feedback message and technical context are delivered to a private GitHub issue used by the developer to respond to bugs and product requests. Do not include information in the message that you do not want the developer to receive. The anonymous Firebase user identifier is not included in the GitHub issue.

Apple services and purchases (iPhone)

If you choose Apple Music, Apple processes your authorization, search, and playback requests under Apple’s privacy policy. If you view or purchase RePasito Pro, Apple processes the transaction and provides StoreKit product, transaction, and entitlement information to the app. RePasito uses that information to show localized offers and unlock Pro features. The developer does not receive your payment-card or Apple Account credentials.

Storage and deletion

App settings and imported practice media remain in RePasito on your device until you remove them or delete the app. On iPhone, deleting the app removes its app-local files; some Keychain values may remain on the device. On Android, uninstalling the app removes its app data, and RePasito’s app data is not included in Android backups or device transfers. Clips previously saved to Photos (iPhone) or Movies/RePasito (Android) must be deleted separately from your gallery.

You can revoke camera, microphone, Photos, or Apple Music access at any time in iOS Settings. On Android, you can revoke camera and microphone access in Settings → Apps → RePasito → Permissions.

Backend rate-limit records derived from the anonymous Firebase identifier expire after approximately 25 hours. Feedback audit records, which contain category, app and iOS versions, delivery status, and the created issue reference—but not the feedback text or Firebase identifier—expire after approximately 30 days. Private GitHub feedback issues are retained while needed to investigate and act on the feedback. Firebase Analytics event-level retention is controlled by the Firebase/Google Analytics project settings; aggregated reports may be retained longer.

To request deletion of submitted feedback, purchase verification records, or associated service data, contact the developer using the method below and provide enough detail to locate the submission or purchase. Deleting the app stops app-originated requests but does not automatically delete feedback you previously chose to submit, and it does not stop subscription notifications from Apple or Google Play.

Service providers and international processing

Google Firebase provides analytics, anonymous authentication, App Check, cloud functions, and backend storage. Google Play provides billing, subscription notifications, and Play Integrity on Android. YouTube provides video search and playback. GitHub hosts private feedback issues. Apple provides StoreKit, Apple Ads attribution, subscription notifications, Apple Music, and device attestation on iPhone. These providers process data under their own privacy terms, and service data may be processed in the United States or other countries where they operate.

Learn more in the Google Privacy Policy, YouTube Terms of Service, GitHub General Privacy Statement, and Apple Privacy Policy.

Children’s privacy

RePasito is not directed to children and does not knowingly collect personal information from children. If you believe a child has submitted personal information through feedback, contact the developer to request deletion.

Changes to this policy

If the app’s data practices change, this policy and the App Store and Google Play privacy disclosures will be updated before the change is released.