Picardo
Legal

Privacy Policy

Applies to the Android application Picardo Course Maker (package com.oleksa.aimentor).
Effective 25 August 2026. Last updated 27 September 2026.

The short version

1. Who is responsible

Picardo Course Maker is developed and operated by Oleksa Kozak, an individual developer based in Ukraine, acting as the data controller for the limited processing described below. Contact: oleksa.kozak2013@gmail.com.

2. What stays on your device and never leaves it

The following is stored in the app's private storage on your phone. It is not uploaded, backed up to us, or shared with anyone:

Uninstalling the app, or using Android's Clear storage, deletes all of it permanently. We cannot recover it, because we never had it.

3. What is sent off your device, and why

Picardo has one server, operated by us on Railway infrastructure. The app talks to nothing else on the internet — it never loads content directly from third-party hosts, so no other company sees your IP address through this app.

WhenWhat is sentWhere it goes after our server
Creating or extending a course, generating a lesson, checking a spoken or written answer The subject and goal you typed, and the lesson context needed for the request. Nothing that identifies you or your device. Google Gemini API, which returns the generated text.
Reading a lesson aloud The text of the lesson to be spoken, plus the chosen voice and language. Microsoft Edge text-to-speech, or a self-hosted Piper voice running on our own server.
Illustrating a lesson The lesson topic and course goal, used as a search query. Openverse, a search index of openly licensed images. The image is fetched by our server and passed to you, so the image host never sees your device.

Requests contain no account, no device identifier, no advertising ID and no location. Our server writes no request log tying content to a person, and we do not build a profile of you. As with any internet service, your IP address is visible to the server at the moment of the request as an unavoidable part of how the network works.

4. The microphone

The app asks for microphone access only when you open a practice exercise that needs it, and Android will show you that prompt. You can refuse; the rest of the app works normally. There are two separate uses, and they behave very differently:

Pitch and rhythm practice — audio never leaves your phone

For the tuner, note recognition, ear training and metronome exercises, the app analyses the sound directly on the device to work out the frequency you played. No audio is recorded to a file, and none of it is transmitted anywhere. It exists only in memory, for milliseconds at a time.

Speaking exercises — handled by your device's speech recognition

Please read this one. When an exercise asks you to say something in words, the app uses Android's built-in speech recognition service. On most phones that service is provided by Google, and depending on your device and settings it may send the audio to Google's servers to be transcribed. That processing is governed by Google's privacy policy and by your Android settings, not by us. We receive only the resulting text, and we never receive or store the audio itself.

If you would rather that never happen, do not use the speaking exercises, or deny the microphone permission. Some Android versions can perform recognition entirely on the device; whether yours does is a system setting outside the app's control.

5. What we do not do

6. Permissions the app requests

PermissionWhy it is needed
InternetTo generate lessons, audio and illustrations. Without it the app still opens lessons already saved on your device.
MicrophoneOnly for practice exercises, as described in section 4. Requested at the moment you start such an exercise.
NotificationsOnly for the study reminder you switch on yourself. Reminders are scheduled on your phone; no server is involved and no push service is used.

7. Legal basis and retention

Where the GDPR applies, our legal basis for sending your text to the services in section 3 is performance of a contract — it is the service you asked for, and the app cannot generate a lesson without it. Microphone use for speaking exercises rests on your consent, given through the Android permission prompt and withdrawable at any time in system settings.

We retain nothing. Content is passed through our server to fulfil the request and is not stored afterwards. Our processors keep data only as long as their own policies require to deliver and secure their service.

8. Processors we rely on

9. Children

Picardo is not directed at children under 13, and we do not knowingly collect personal information from them. Because the app has no accounts and collects no identifiers, it holds no children's data to disclose or delete. A lesson is generated by a language model from whatever subject is typed in; parents should supervise use accordingly.

10. Your rights

Depending on where you live, you may have rights to access, correct, delete, or export your personal data, and to object to processing. In this app those rights are largely self-service, because everything personal lives on your phone: uninstalling the app or clearing its storage erases all of it immediately, and there is no account for us to look up. If you believe we hold something about you, write to oleksa.kozak2013@gmail.com and we will answer within 30 days. You may also complain to your national data protection authority.

11. Changes to this policy

If the app starts doing something materially different — accounts, for example, which we are considering — this page will be updated before that version ships, and the date at the top will change. Significant changes will also be noted in the app's release notes on Google Play.

12. Contact

Questions about this policy, or about anything the app does with data: oleksa.kozak2013@gmail.com.