English
Leor privacy policy
How Leor uses data on the website and in the Android app, which categories may be processed, and how users can manage access-related requests.
What this page covers
This page applies to the leorapp.com website and the Leor Android app.
The Google Play package is com.buga.leor; the RuStore build is distributed as com.buga.flash.cards.
When the website, app, and store flows live on different surfaces, we still aim to keep one understandable privacy policy instead of hiding key limits inside internal tooling or store-only forms.
Developer: BugaContact: leor.support@gmail.comWebsite: leorapp.comLast updated: May 28, 2026
Data-handling principles
- We do not sell personal data or pass it to ad resellers.
- The microphone is used only for voice flows that the user explicitly starts.
- We try to collect only what is genuinely needed for speaking practice, access, payment, and product stability.
- If a sensitive Leor data flow changes, we should explain it in plain language.
Control and user rights
- Users can revoke permissions in Android settings.
- Users can delete the app and local data on the device.
- Privacy and access questions can be sent to leor.support@gmail.com.
- If the request is about paid access or deletion, include the relevant account email and a short description of the issue.
What data may be processed
Email and access data
When a user signs in, confirms email, restores access, or starts checkout on the website.
Voice, text, and rehearsal content
When a user explicitly starts voice or text rehearsal with the AI partner, including prompts, speech fragments, and related replies.
Technical identifiers and access state
For example deviceId, trial/access state, and the technical context needed to restore access between the website and the Android app.
Diagnostics, analytics, and configuration data
Usage events, crash diagnostics, and remote-config data used to understand stability and product behavior.
Payment and support context
Data needed to start checkout, restore access, answer support requests, and investigate billing or access issues.
Why it is used
To make Leor work as a speaking product
Generate replies, transcribe or synthesize speech, show scenarios, and return the user to a usable rehearsal context.
To grant and restore access without manual confusion
Link the website and app through email, verify entitlement state, and help the user return to paid access.
To improve stability
Understand where the product breaks, which steps stall, and which surfaces are actually used.
To support payment and access requests
Check checkout starts, access restoration, and user-facing support issues tied to billing or access.
Permissions
Microphone
Required for voice rehearsal and speech capture. After recording stops, Leor should not keep listening as a background always-on service.
Internet
Required for AI responses, sign-in, checkout and access flows, analytics, diagnostics, and remote configuration.
Account or data deletion request
For a dedicated user-facing request to delete a Leor account and related cloud data, or to request data-only deletion, use the public account-deletion page.
Contact
Email for privacy and access requests: leor.support@gmail.com
Public product website: https://leorapp.com
If the question is about paid access, use the same email that was used on the website and inside Leor.